UCMDB and UD Practitioners Forum (Previously CMS)
cancel

upgrade to 10.01 , package version did not change

SOLVED
Go to solution
Highlighted
SteveCollinP
Trusted Contributor.

upgrade to 10.01 , package version did not change

experts  we upgraded to 10  . But  noticed that the custom adapters are still showing as version 9.05 in list of packages in package resource section . we are on cup 10. 

any ideas , suggestions on additional steps that need to be done to  modify package , scripts and adapters. when we run the jython scripts, we got error- Failed executing script, details: Traceback (most recent call last):

  
 
5 REPLIES
Consultant13
Honored Contributor.

Re: upgrade to 10.01 , package version did not change

Hi Steve ,

Please read carefully HP Deployment guide You might have to redeploy the Custom made adapters when you upgrade

Hope this help

Cheers :)
Ben.Shirley
Outstanding Contributor.

Re: upgrade to 10.01 , package version did not change

Hi,

 

The custom adapters will remain at the version of the uCMDB they were created in. A deployment of a new uCMDB or content pack would not include updating the version numbers of custom adapters, how would they know what people have written?

 

The version number reported should not affect the operation of the adapters, something else must be wrong. Maybe investigate the logs and post any errors.

SteveCollinP
Trusted Contributor.

Re: upgrade to 10.01 , package version did not change

I checked the error message in logs and it was  an invalid object name error in the scripts. we identified that the object was a table after checking cmdb sql tables. Is there a guide  to look up the new object name - table name  ,  for instance , if the table name was dbo.tablex in 9.05 , what is the corresponding new name or new table in 10.01 ?

 

Ben.Shirley
Outstanding Contributor.

Re: upgrade to 10.01 , package version did not change

Probably need a bit more information to go on really. The error messages you have posted are very generic. You have not said what technology your custom script is trying to discover etc..
SteveCollinP
Trusted Contributor.
Solution

Re: upgrade to 10.01 , package version did not change

I was able to fix the issue by changing the new table name used in version 10. thanks