So this means that:
1°) we have to use the dll from sp2/sp3,
2°) "clean" attribute definition form,
And SyncUI will work ok? Wow...
in my case it helps to fix SyncUI issue.
I'll pass along to collegues who are currently banging their heads against walls
***Dmitry's right...be aware that the CMDBSychronizeUI file has moved!***
We upgraded to ARS v7604sp3 & Atrium v7604sp3 and...................IT WORKED!!!!!
My new attributes as well as the modifications to existing attributes all came thru the upgrade and SyncUI worked perfectly the first time round. So my advice...UPGRADE!
there is another KB which describes the issue. Also a hotfix is provided to fix the issue:
KA358395-"Getting an error in CMDBSynchUI.log while synching extensions of the Comon Data Model (CDM) with the Asset SynchUI utility."
If you did not opened a support ticket - please, open a support case to clarify if this Hotfix is relevant for your issue.
In our environment, that is 7.6.03 SP1, it was not possible to upgrade the install to a newer package or SP (because of customer needs).
We have completed the solution by now; the remaining problem for us were permissions and flow. We were given instructions by BMC on how to change the permissions for fields (we are talking about 60 or 70 fields affected) directly with a database script in order to make it faster.
Once run the script, we can say we have our problem fixed and the CMDB going.
As for the problem with the flex Class Manager Console, we have noticed a significant improvement by increasing the resources of the MidTier server up to 16GB RAM.
Mid-Tier with 16 GB? How many users are connected on the mid-tier?
I've had this same issue with ARS 7.6.04 in that the Sync-UI command will sit in the Application Pending form. and not be processed. I've found that this command would work fine on my DEV and UAT environments, and then when this was run in an upgrade window to production, the command would not run to completion.
What I've found is that a restart of the AR Server service will run this command from the Application Pending form, and the fields will be added from the base class(es) to the asset form(s).
Another alternative that should work would be to delete the command from Application Pending and then manually add the fields to the AST form from the CMDB base class in Dev Studio.
1 of 1 people found this helpful
Generally if you need to resort to an AR Server service/process restart for stuck SyncUI situations, you can get things moving by just killing the AR CMDB process itself, rather than all of AR. ARMONITOR will restart the CMDB process and typically the Application Pending entry for the CMDB Sync will get processed within seconds. It's actually the CMDB process that is stuck/hung, not AR Server.