When you try to Update AssetUI for Base element it modifies all classes below it as its the super class. The synchronisation takes place for a time duration from 3-4 hrs.
So first check Application Pending form-If any entry to Sync-UI is there.If yes delete it- Restart the server and again click on Update UI for Base element.
Go to App Pending form.An entry called Sync-Ui will come .After the entry gets deleted wait for few hours.
Once sync is completed then do for computer system.
You can chek the CMDB Synchronisation log in your db folder
Thanks for your reply.
We have already tried this option as you mentioned in your reply, but we did not get desired result.
In our case the SynchUI process itself is not getting completed.
We are not getting "Asset UI Synch process completed successfully" at the end of the CMDBSynchUI.log
How much time you are waiting?
Didi u see the entry gets deleted from Appllication Pending form?
Are you doing one update asset UI at a time?
Can you check if you see some errors in CMDBSynchUI.log
I have almost waited for a day.
I am able to see the entry getting deleted from Application Pending form.
Yes, I am doing one update Asset UI at a time. Also I tried with "Update ALL" option. But none of option worked.
At the end of the CMDBSynchUI.log file I can see some errors like -
Failed to create field: ActivityType on Form: AST:Activity on server (1st log)
Failed to create field: Integrity on Form: AST:BaseElement on server (2nd log)
Failed to create field: isVirtual on Form: AST:ConcreteCollection on server (3rd log)
But these 3 errors are not from single CMDBSynchUI.log file. It get changes whenever I am trying SynchUI utility.
We did face the same issue. Actually it happens when the first time attribute creation synchronisation fails. So next updates fails. Is it possible for you to delete the fields from class manager recreate again and sync???
We tried by deleting the custom attribute and recreating from Class Manager.
And then tried to synchronize but still the same issue we facing.
in the Release Notes for Atrium Core 7.6.04 is given a workaround for what it's considered a defect (SW00387262); pg 29:
On Windows 64-bit computers, if you create a class and you try to synchronize the class inBMC Atrium CMDB with BMC Remedy Asset Management (Application AdministrationConsole > Custom Configuration > Asset Management > Advanced Options > Sync AssetUI), sometimes the CMDBSynchronizeUI.log is not properly generated. When this log fileis not generated, the AST form for that class is not generated either. This condition isintermittent.
1 Create a folder path (for example, C:\arservdb\arserver\db\) before you run the cmdb2asset utility.
2 Run the cmdb2asset utility to synchronize the UI. The CMDBSyncUI.log file is thenproperly generated in the new folder.
However, we are facing the same issue with Remedy 7.6.03 and we are not able to set the new folder path because the CMDBSynchronizeUI.log is still created in the original folder (we created a new folder and redirected the ar.conf line "Server-directory" to the new path) but it does not work.
Hi Vanessa....can you provide env details (db/os/exact remedy vrsn) and also if the env is a server grouped env...?
we've contacted support and, apparently, the pb is caused by the own cmdb2asset dll. They've provided us a new one (the problem is alive for 7.6.03 and 7.6.04 versions); we've run the tests and, although the new dll complete part of the work, it does not come to an end. BMC is currently working on the issue.
This KB article may help: KA329227. The URL they've provided to fetch the new dll is ftp.bmc.com/outgoing/ISS03907572.
Thanks for your help.
As a matter of fact, we are still facing the synch issue.
We're working together with BMC and, apparently, is mostly a performance problem. We have a test env with 6Gb RAM assigned (it's a VM) and we changed config up to 8Gb following BMC advice.
The result is that, for new classes, the process comes to an end correctly (as seen in the log) but the forms are still not generated correctly. For classes that have different superclasses, we face errors like "not able to create the field -Is Virtual?- no field limits haver been stablished". It happens with different fields.
We are seeing a similar issue here, but it should not be a resource issue - We are on a Win2008 64 bit VM with 12Gb dedicated RAM and 2x2.20 GHz AMD CPUs.
These tests are with new sub-classes of BMC_Equipment, using our own (PQ.UIE) namespace (as opposed to just adding fields, as above).
Running the sync creates a form, but with only some of the fields and the workflow does not attach. The "CMDBSynchronizeUI" logs cut off with:
[2012/06/06 15:53:07.7770] [ ERROR ] [TID: 0000003716] : Failed to create field: Integrity on Form: AST:PQ_TestClass2 on server: AAPQREMEDY05
or they 'complete' but have the following errors
[2012/06/06 15:32:59.1060] [ ERROR ] [TID: 0000003100] : Failed to create reserved system field: DSOUniqueId on Form: AST:PQ_TestClass2 on server: AAPQREMEDY05
[2012/06/06 15:32:59.1060] [ ERROR ] [TID: 0000003100] : Status message: AR System reserved field definition cannot be modified.
[2012/06/06 15:32:59.3400] [ ERROR ] [TID: 0000003100] : Failed to create field: ReconciliationIdentificationError on Form: AST:PQ_TestClass2 on server: AAPQREMEDY05
[2012/06/06 15:32:59.3400] [ ERROR ] [TID: 0000003100] : Status message: Field does not exist on current form
[2012/06/06 15:32:59.3400] [ TRACE ] [TID: 0000003100] : Errors encountered while processing form: AST:PQ_TestClass2
[2012/06/06 15:32:59.3400] [ INFO ] [TID: 0000003100] : Application UI synchronization completed
Is BMC doing anything on this at the moment?
actually there's an important difference between the case you report and ours; in our system, the "CMDBSynchronizeUI" always ends with a "successful" status and no errors are registered (wich I think is worse...).
The issue with BMC is still open: apparently, it's all about the query the application sends to the database because it wouldn't be taking the significant name of the class (say "T_Networking") but the instance ID of the class, what returns NULL values and is not creating the fields.
On the other hand, looking at the logs you send, it seems you are facing problems too when creating reserved fields, such as DSO fields. Have you tried to run the synch letting out the DSO fields? just to see if it goes.
I am running the sync from the 'Schema Names' form, Vanessa. How would I run the sync to not include some of the fields?
I've experienced problems with the DSO fields when they're added to the view. What I meant was to try a new synch having previously removed the DSO fields from the CMDB form you are to trying to synchronize. Just to try.