The problem you have here is that either the CO was not correctly imported or you have changed your fileserver without copying over all the files correctly. The error message is saying that the following directory does not exist:
To get around this problem, you can do the following:
Delete the latest VMware CO from the Config Object Dictionary
Re-import the CO again. To re-import the CO you can browse to the NSH/br/autoimportcontent/customobjects folder and look for the latest jpavmware.zip.done.xxxxxxxxxx file. Copy this file somewhere else, rename it to jpavmware.zip and import this CO into the appserver from the Config Object Dictionary
Thanks for your valuable reply.
Yes there was a problem with the VMWare config Object. So I deleted that one and re-import the jpavmware.zip
again.Then I executed USP job and DCO Job. IT works perfectly for me.
My error has resolved.But could you please tell me more about the root cause of the issue.
It usually happens when you change your fileserver and don't copy the contents from the earlier file server.
Either that, or there might have been some problem during the import of you config object.
I'm having the same problem in a BL 8.1.0 implementation. Can you be more specific about how to "Delete the latest Vmware CO from the Config Object Dictionary"?. How do I know it's the latest? I see to many Server Objects called Vmware in the CO Dictionary but the delete button is not enabled. Also in the NSH/br/autoimportcontent/customobjects folder y don´t have any file starting with "jpa"... mine is only vmware.zip.done.xxxxx. I moved the file, renamed the other and tried to import but says that the folder "doesn´t contains any importable object".
in 8.2 the co was renamed a bit so it's jpavmware in 8.2 and vmware in < 8.2.
i don't think you need to delete. if you see the directory path the files are missing from, you can do this manually:
- extract the vmware.zip.done.xxx
- look at the 'version' in the xml file in the extracted files
- look in the config object dictionary for the version of the latest vmware CO.
- once you find a match, copy the files you extracted into the path noted.
Thanks for your comments and help. I found an article from BMC Knowledge Base (KA322350) which goes trough this error step by step. I applied the solution procedure and worked good. I'm now able to browse the vCenter from BSA.
Adding the URL in case it helps someone else: https://kb.bmc.com/infocenter/index?page=content&id=KA322350&actp=search&viewlocale=en_US&searchid=1413329262379