*** UPDATE: A hotfix for this regression is now available for both SM 2012 SP1 and R2. The hotfix however is a limited distribution release for now, so you will have to create a case with support to get access to it. We intend to make this fix generally available in the coming UR in July. ***
As noted on the posts announcing the availability of UR2 and UR6 for Service Manager 2012 R2 and SP1 respectively, there is a bug which impacts SCCM connector synchronization on both versions. This blog explains the issue in some detail, and includes information on systems impacted, possible workarounds, and the expected timeline on the fix. Read on for more information.
Who's impactedThis bug impacts only those customers who:
The bugApril 2014 URs for Service Manager included a check in SCCM connector to ensure consistency of software install counts across SM and CM. This fix included some additional logic to compare the software version information as reported by CM against the data already stored in the SM database. This was done to appropriate handle updates to the DeviceHasSoftwareItemInstalled property. However, if the version information reported by SCCM does not follow standard versioning practices the equality check fails causing SCCM connector synchronization to abort. Per our investigation this issue does not impact any other functionality in SM.
If you are impacted by this issue, SCCM connector synchronization will fail with the following error information logged to the event log.
Exception type:ArgumentExceptionException message:Version string portion was too short or too long..StackTrace: at System.Version.TryParseVersion(String version, VersionResult& result)
The workaroundYou can get SCCM connector synchronization going again by rolling back the assembly named Microsoft.EnterpriseManagement.ServiceManager.Linking.Consumer.OperationalStore.dll to the RTM version. This workaround ensures that SCCM connector synchronization does not break without impacting any of the other fixes delivered in this UR. See table below for versioning information.
Scenario 1If you haven't yet installed this UR, ensure that you take a backup of the existing assembly in your Service Manager install folder by copying it to a different location. Once installed, replace the new assembly installed by the UR with the previous version.
Scenario 2If you've already installed the UR, and do not have access to the RTM version of the assembly, you have a couple of options:
Fix availabilityWe have a fix for this issue in the works and expect to release it as a hotifx soon. You can either keep an eye out on this post, or follow us on Twitter @servicemanager to stay up to date on the hotfix’s availability. Additionally, the fix will be included in the next UR for SM 2012 R2.
Hello I 've change the .dll SP1 from RTM but nothing changed error continues.... do I need to do something more?
Maybe a Computer restart or SDK restart?
Thanks in advance
reverted back to the old dll on R2 here. like vangelis i've still the same error.
Yep, thanks for pointing that out... the services do need to be restarted once the assembly has been rolled back. Let me know if that doesn't work.
thanks for the feedback and detailed description
In my case, the procedure was:
- Verify no SCSM Connector is running.
- Stop "Microsoft Monitoring Agent" service.
- Replace dll.
- Start "Microsoft Monitoring Agent" service.
- Restart SCSM services.
Does the dll need to be replaced on both the management server and the data warehouse server?
I did the work around above and all it did was break my AD Connector. When will the hotfix be published for this issue?
I did spilt the configmgr 2012 connection up in one pr. Collection, and it works with the
7.5.3079.61 file. I did just disabled the original connection with 3 Collections.
Folks, a hotfix for this issue is now available. More information on this in the update to the blog post.
What if you don't have a support contract? I need to get the hotfix...
@DC-1234 We will make the fix for this issue generally available in the next UR. In the meanwhile please use the workaround mentioned in the blog.
Hi, I have the same error... where I can get the Fix??
This fixed my CM connector. But like Jackson said, it broke my AD connector. So its not a very good "fix".