SCOM 2012 SP1 CU 3

Lync 2013

SCOM Server : Server 2012

Lync Server:  Server 2012 R2

 

Followed all the instructions in both of the article below.  I know it is at least partially working because when I typed in the wrong addresses (on accident in both the channel setup and the subscription setup) SCOM generated an alert saying that the address was incorrect and it couldnt complete the request when an alert was generated.  But now the only thing that happens is the errors below.

http://lyncuc.blogspot.com/2012/10/system-center-operation-manager-with.html

http://opsmgrunleashed.wordpress.com/2012/02/24/enabling-instant-messaging-notifications-in-system-center-2012-operations-manager/

 

The following errors occur with both UCMA 3.0 & 4.0 installed (I have tried both versions)

 

IM Channel Settings

IM Server:  Server FQDN

Return Address:  sip:OpsMgrLync@domain.com

Protocol: TLS

Authentication:  NTLM

Port:  5061

Format:  Default

 

Steps to Reproduce:

Create Notification Channel

Add IM Notification to Subscriber

Add Subscription

 

Force generate an alert (stopping IIS website on a dev server).  Email alert is generated.  Lync Notification is not.

 

Operations Manager Log

Event ID 4509

The constructor for the managed module type "Microsoft.EnterpriseManagement.HealthService.Modules.Notification.Sip.SipNotificationTransportModule" threw an exception. This module was running in rule "Subscription454d3dbb_0bd6_45eb_83d3_f0f6f45520ec" running for instance "Alert Notification Subscription Server" with id:"{E07E3FAB-53BC-BC14-1634-5A6E949F9230}" in management group "NFM".

 

 The exception text is:

 Microsoft.EnterpriseManagement.HealthService.ModuleException: Could not load file or assembly 'Microsoft.Rtc.Collaboration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. ---> System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Rtc.Collaboration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

   at Microsoft.EnterpriseManagement.HealthService.Modules.Notification.Sip.SipNotificationTransportModule.BuildTransport(XPathNavigator configuration)

   at Microsoft.EnterpriseManagement.HealthService.Modules.Notification.NotificationTransportModuleBase`3.ReadConfiguration(XPathNavigator configuration)

   at Microsoft.EnterpriseManagement.HealthService.Modules.Notification.NotificationModuleBase`1.ReadConfiguration(XmlReader configuration)

   at Microsoft.EnterpriseManagement.HealthService.Modules.Instrumentation.InstrumentedModuleBase`1..ctor(ModuleHost`1 moduleHost, XmlReader& configuration, Byte[] previousState)

   --- End of inner exception stack trace ---

   at Microsoft.EnterpriseManagement.HealthService.Modules.Instrumentation.InstrumentedModuleBase`1.HandleFatalException(ITraceScope traceScope, Exception error)

   at Microsoft.EnterpriseManagement.HealthService.Modules.Instrumentation.InstrumentedModuleBase`1..ctor(ModuleHost`1 moduleHost, XmlReader& configuration, Byte[] previousState)

   at Microsoft.EnterpriseManagement.HealthService.Modules.Notification.NotificationModuleBase`1..ctor(ModuleHost`1 moduleHost, XmlReader& configuration, Byte[] previousState)

   at Microsoft.EnterpriseManagement.HealthService.Modules.Notification.NotificationTransportModuleBase`3..ctor(ModuleHost`1 moduleHost, XmlReader& configuration, Byte[] previousState)

   at Microsoft.EnterpriseManagement.HealthService.Modules.Notification.Sip.SipNotificationTransportModule..ctor(ModuleHost`1 moduleHost, XmlReader configuration, Byte[] previousState)

 

Event ID 1103

Summary: 1 rule(s)/monitor(s) failed and got unloaded, 1 of them reached the failure limit that prevents automatic reload. Management group "NFM". This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s).

 

Running PROCMON on this doesn't find a single thing for that .DLL when using UMCA 4.0

 

However, as described in the article here:  http://social.technet.microsoft.com/Forums/systemcenter/en-US/0dce0c5b-fcec-4ca9-a506-0523088968df/trying-to-send-im-through-scom-2012, if I install UCMA 3.0 and run PROCMON I find the following entries after I take the Steps to Reproduce above. Previously when I had run this I had gotten a ton of PATH NOT FOUND like the one described in that article, but now that I am writing up this article they aren't showing up.  

 

9:33:14.6284984 AM        MonitoringHost.exe        3636        RegOpenKey        HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\v4.0_policy.4.0.Microsoft.Rtc.Collaboration__31bf3856ad364e35        NAME NOT FOUND        Desired Access: Read

9:33:14.6285733 AM        MonitoringHost.exe        3636        RegOpenKey        HKLM\SOFTWARE\Microsoft\Fusion\PublisherPolicy\Default\policy.4.0.Microsoft.Rtc.Collaboration__31bf3856ad364e35        NAME NOT FOUND        Desired Access: Read

 

Thoughts on what I can do to get this working or what might be

Hi,

I suggest you double check your configuration about enabling IM channel notification:

Enabling Instant Messaging Notifications in System Center 2012 Operations Manager

http://opsmgrunleashed.wordpress.com/2012/02/24/enabling-instant-messaging-notifications-in-system-center-2012-operations-manager/

That is not the correct answer, and if you had read my post you will see I already linked to that same article.  I currently have a support case open and when the issue is resolved I will post here with the correct resolution.

I am running into a similar issue. I have setup IM notification from the same article and  I can't get notifications to work with Lync 2013. I am able to get notifications with my Lync 2010 client , so  It will be interesting to see what you comeback with.

 Please update us on you progress or lack of :)

I am running into a similar issue. I have setup IM notification from the same article and  I can't get notifications to work with Lync 2013. I am able to get notifications with my Lync 2010 client , so  It will be interesting to see what you comeback with.

 Please update us on you progress or lack of :)

I was missing two files from my configuration that Microsoft had to send me.  In the Server folder in my SCOM installation directory on both of my Management servers I was missing the Microsoft.RTC.Collaboration.DLL, Microsoft.RTC.Collaboration.XML and the SIPEPS.dll files.  Once those files were placed in the directory everything worked fine.  I am still awaiting word on why those files were missing to begin with.  My 2nd Management Server I just built a week ago (the first was done in March) and was also missing all the files listed above.

Hi Kostantin,

Where are these files? 

Thanks...

After installing the "Unified Communications Managed API 4.0 Runtime" on the SCOM management server from http://www.microsoft.com/en-us/download/details.aspx?id=34992 the below files showed up in child folders of C:\Windows\Microsoft.NET\assembly\

Microsoft.RTC.Collaboration.DLL
SIPEPS.dll

The Microsoft.RTC.Collaboration.XML file can be downloaded from: http://www.getcodesamples.com/download/D23F42EA/6098871E

Copy these three files to: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server

After installing the "Unified Communications Managed API 4.0 Runtime" on the SCOM management server from http://www.microsoft.com/en-us/download/details.aspx?id=34992 the below files showed up in child folders of C:\Windows\Microsoft.NET\assembly\

Microsoft.RTC.Collaboration.DLL
SIPEPS.dll

The Microsoft.RTC.Collaboration.XML file can be downloaded from: http://www.getcodesamples.com/download/D23F42EA/6098871E

Copy these three files to: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server

Hi, I'm experiencing the same issue as discussed here, I installed Unified Comms (and .net 4.5) to facilitate this and copied the three files in question into the Server folder but I'm still getting the error! Did you have to cycle anything to activate the change? Cheers

After installing the "Unified Communications Managed API 4.0 Runtime" on the SCOM management server from http://www.microsoft.com/en-us/download/details.aspx?id=34992 the below files showed up in child folders of C:\Windows\Microsoft.NET\assembly\

Microsoft.RTC.Collaboration.DLL
SIPEPS.dll

The Microsoft.RTC.Collaboration.XML file can be downloaded from: http://www.getcodesamples.com/download/D23F42EA/6098871E

Copy these three files to: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server

Hi, I'm experiencing the same issue as discussed here, I installed Unified Comms (and .net 4.5) to facilitate this and copied the three files in question into the Server folder but I'm still getting the error! Did you have to cycle anything to activate the change? Cheers

Oh, and we're running SCOM 2012 SP1 and Lync 2010....

You need install Unified Communications Managed API 3.0 Runtime

Evren,

Previous posts above from different sources indicate the issue occurs for both 3.0 and 4.0, however Corey's specific fix relates to UC 4.0....hence my query (and the associated quote).

Same thing here

SCOM 2012 R2, Lync 2013

I have installed UCMA4 on SCOM server, copied the 3 files to server folder, but still the same  problem

Hey Benoit,

I know it has been a while but wondered if you got this working?

I managed to get a bit further as I enabled some logging which allowed me to see that Scom was looking for version 4.0 of those 2 files but UCMA4 strange has version 5.

Once I placed the correct versions in the server folder I then get the below alerts.

Exception 'Microsoft.Rtc.Signaling.OperationFailureException': The CollaborationPlatformStartupAsyncResult operation has failed. See the FailureReason property as well as the logs for additional information.  

Hi,
after installing UCMA 4.0 and copying the Microsoft.rtc.Collaboration.dll and the SIPEPS.dll in the Server folder I get the same Error:
Microsoft.Rtc.Signaling.OperationFailureException: The CollaborationPlatformStartupAsyncResult operation has failed. See the FailureReason property as well as the logs for additional information.

Can anybody help us with the IM Notification feature? I think this is a Problem with the v5 of the Microsoft.RTC.Collaboration.dll but where can i configure SCOM to take the version of the UCMA 4.0 and not the old 3.0 Version (=v4 of the Microsoft.RTC.Collaboration.dll).

Same issue after installing UCMA 4.0...

- Copied the following files to SCOM installation root directory

• Microsoft.RTC.Collaboration.DLL (5.0.8308.0)
• SIPEPS.dll
• Microsoft.RTC.Collaboration.XML

- Create the following RegKey as mentioned below
https://social.technet.microsoft.com/Forums/systemcenter/en-US/875a930e-fe78-47ab-839c-6b4b2335690e/problem-with-scom-dont-send-immessages-to-ocs-2007-r2-or-lync?forum=operationsmanagergeneral

Still no luck to get thi