You can ignore the errors about DSO fields:
You should contact BMC support because last time I checked SyncUI was buggy, I think they have a fix for it (cmdb2asset_win64.dll).
Yes, we are managing an issue with BMC because the problem persists after having fixed the bug related to the dll.
I'm dealing with the same issue on the same configuration.
I've had a ticket open for a month on this with BMC and no movement.
We applied the hotfix .dll on DEV and it worked; however, now on UAT it doesn't.
Did you ever get this working?
somehow we are solving this with BMC's help. The origin of the problem seems to be creating classes with the old CMDB:Console instead of creating them with Atrium Core. We had to go to the old Class Manager Console because the Atrium Explorer wouldn't complete any create new class process. That causes that the new classes are created with its instance ID instead of the significant name. Thus, when you create a new class, lets say T_NewClass, in its lookupkeyword in schemanames you won't see T_NewClass but AG000C292038E69MYfTwQPTeAwmVsB. Every query has being designed to look for the significant name, and that's why some processes fail when it comes to synchro. BMC has given us a process (manual process) to look for some tables in which we have to remove the instance ID and write the significant name of the class.
This have solved some problems (like menus that didn't work) but some others are still open such as permission in the fields or relationship creation.
Did you use the old CMDB Console to create your classes? This may be the point.
Yes we are using the "old" console since, as you said (and to BMC, no offense here), the Flex Class application is buggy and, as you said, it's too random... How can you write and give a procedure for a customer when it works like 10-20% of the time?
Other bad point on this flex console is that if you leave it you have no idea if it's finished or not and anyway there is no update status like "change pending" or something
You're right Laurent, as it's not possible to see in the Atrium Core what the status of the changes is in a class or what the error log says for the change, we turned too to a console that worked.
I've not been able to test this in the beta 8 release, but I hope this very feature has been enhanced because it's a problem that will need, in our environment, a hard maintenance work for administrators.
In my case UI sync only creates AST forms but not linking it to workflow. Is any chance to fix it by new cmdb2asset_win64.dll file? All classes are created in flex console.
ARS 7.6.04 SP3
Atrium CMDB 7.6.04 SP2
ITSM Suite SP2
We had mixed success with the new *.dll file. Worked in DEV, but not in UAT (both are ARS sp2 though).
Most of the attributes in DEV were created with the *old* console; however, I created all the UAT with *new* console.
I spent a while on the phone this afternoon with Ken Lee @BMC support. (My ticket got escalated...YEAH!!!)
Atrium v7604 sp3 has been released and supposedly it contains about ~15 SyncUI fixes and ~80 Reconciliation (used by SyncUI) fixes. Also, it can be installed on ARS v7604 sp2.
We will be installing this tomorrow on UAT (which is a clean install with only the new attributes).
We'll probably install ARS sp3 then also.
If the attributes are still there, I'll run SyncUI and see what happens.
One thing BMC team pointed out looking at the logs in our environment was that we experienced time outs during the synchronization process. It was due to the lack of memory of the environment (it had 4Gb for the ARS and full ITSM suite, the minimum recommeded).
So, to ensure a good performance, look that your environment is on the BMC's recommendations for RAM or higher (this is, 8Gb or higher) and that no other memory-consuming processes are running at the same time.
I use 3 separate servers for DB,APP,WEB with 8 GB RAM per server. I think it should be enough.
FYI - We identified this issue on a virtual server that had 12Gb of dedicated (not shared) RAM. Memory use was not a factor in our case.
Working with BMC support, we have also tried the new cmdb2asset_win64.dll - unlike the original DLL that would run the startup and then error out on the field issue, the new DLL wouldn't even start the process (or at least didn't create any log entry).
Still waiting on answers, but have another Webex with BMC support on Wednesday. Will let you know what I find.
Regarding the console used, we started with the Atrium Core console, and also tried with the old console at Column support's direction, same results from both.
Open the Attribute Definition form and sort by Record Status a couple times. Do you have a ReconciliationIdentification Error entry where the Record Status is not "Active"? (Can't remember what it was...something like Change Pending.)
If so, delete it as well as any other entries for ReconciliationIdentification Error. This is a known issue.
I've found wrong entry in Attribute Definition form, delete it and UI Sync works perfect now! It creates custom AST form and links all workflow to this form.
Thank you so much for receipt!
This functionality working with both cmdb2asset_win64.dll files SP2 and SP3.
Note: if you use cmdb2asset_win64.dll SP3 it makes log in different folder - c:\program files\bmc software\atriumcore\logs instead c:\program files\bmc software\ARystem\ARServer\db