Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Martijn
Advisor
Advisor
Jump to solution

More than one object named 'Custom' exists

Hi All,

I migrated a SmartCenter from R81.10 (Smart-1 525) to R81.20 (VMWare) with the latest migration tools.
The migration was successful for one small thing.

There was a Violation Error with the name 'Custom'. "More than one object named 'Custom' exists"
That was correct because customer's database contained a Time Object with the name 'Custom' which is also a message type in the GTP Interface Profile. In R81.10 this was not shown, but in R81.20 it is. The initial message contained the word 'Custom' two times.

I renamed the Time Object hoping this would solve the problem, but now I am stuck with this message. Containing 'Custom' only one time.

I can solve this for a brief period bij creating a Time Object named 'Custom' and delete it right away and publich changes. But after a while, this message returns. There is no object anymore with the name 'Custom'. Checked it with SmartConsole and with GuiDBedit.

Any idea where to look? 

Regards,
Martijn

0 Kudos
1 Solution

Accepted Solutions
Martijn
Advisor
Advisor

Hi,

Opened a TAC case and the engineer told me this is a cosmetic issue that happens sometimes.
He gave me a script called 'deleteValidationIncidents.sh' which was the solution.

So if you run into this issue, open an TAC case and they send you the script.
It was fixed in 5 minutes.

Regards,
Martijn

View solution in original post

(1)
5 Replies
PhoneBoy
Admin
Admin

TAC might need to investigate this.

0 Kudos
the_rock
Legend
Legend

Not sure if below sk may apply...its odd that it does not even show up in Guidbedit though.

Andy

https://support.checkpoint.com/results/sk/sk115374

0 Kudos
the_rock
Legend
Legend

One other thing you could try, if you haven't already, is mgmt_cli to search for an object name.

https://sc1.checkpoint.com/documents/latest/APIs/#cli/show-object~v2%20

Andy

0 Kudos
Martijn
Advisor
Advisor

Hi,

Opened a TAC case and the engineer told me this is a cosmetic issue that happens sometimes.
He gave me a script called 'deleteValidationIncidents.sh' which was the solution.

So if you run into this issue, open an TAC case and they send you the script.
It was fixed in 5 minutes.

Regards,
Martijn

(1)
the_rock
Legend
Legend

Thanks for letting us know!

Andy

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events