topic Re: schema verification failed (application-filter -> nim 'nim' is already in use) in General Topics

schema verification failed (application-filter -> nim 'nim' is already in use)

Oleksandr — Mon, 25 Nov 2013 16:28:17 GMT

Hi There,

I am kind of stuck on a problem for which I am unable to find a resolution ...

When I commit on my device after upgrading "Application and threats database" , I get an alert with the " application-filter -> nim 'nim' is already in use "

But when I do a change back (revert to previous state of database 404-2015) it is OK!

Any thoughts guys???

Regards,

Alex

Re: schema verification failed (application-filter -> nim 'nim' is already in use)

kadak — Mon, 25 Nov 2013 16:52:10 GMT

Hello Alex,

In content version 405, there were two new applications introduced - nim and nimsh

Do have custom application for nim and nimsh created on the PAN? May be since it didn't exist in app-database prior 405, chances are you might have created it.

Couple of things we might check:

1. If created, we can remove the custom application related to nim and nimsh while being on 404 content version

2. Through CLI, configure > commit force. That would parse the configuration from scratch

3. Upgrade to 405 version and see if that helps.

Also, before going to step2, can be delete an application filter called 'nim' and then commit and upgrade?

Let me know if that helps!

Thanks and regards,

Kunal Adak

Re: schema verification failed (application-filter -> nim 'nim' is already in use)

Phoenix — Mon, 25 Nov 2013 16:53:58 GMT

Hello Olek,

Have you tried to change the name of the Application filter to different or new name and test. I suspect the name is matching a predefined name. We may get more logs running the command

"tail follow yes mp-log ms.log" when the commit is happening to identify the issue.

Pls share it here for understanding.

Thanks

Re: schema verification failed (application-filter -> nim 'nim' is already in use)

mbutt — Mon, 25 Nov 2013 16:59:32 GMT

Hi,

1. You can rename the existing custom application to a to lets say nim-custom and nimsh-custom and then commit.

2. Then try to upgrade to the latest content version.

3. Once you have upgraded if you want you can change the application to the latest added application in the content 405.

4. Then do a commit again.

However if you do not want to change them you can leave them on the custom one.

Hope this helps you resolve the issue.

Thank you

Numan

Re: schema verification failed (application-filter -> nim 'nim' is already in use)

Oleksandr — Mon, 25 Nov 2013 17:33:24 GMT

TY!

I created custom application, and forgot about it!

Thank You again!