Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Pages Menu
TwitterRssFacebook

Posted by on Apr 16, 2014 in Skype for Business® (Lync®)

UCMA Application: This message was not delivered to [user name] because the service is not available.

UCMA Application: This message was not delivered to [user name] because the service is not available.

We spent far too long today looking at this, so I’m documenting it in the hope that it can help someone else.

The Problem

You’ve set up a UCMA Application. The application starts fine, provisions fine and generally seems to be running. However, when you attempt to send it an IM, it immediately fails with this message:

This message was not delivered to [user name]because the service is not available.

(on Lync 2010 clients, we actually just see a red cross with no supporting error message)

Digging In

We tore apart the installation of the application, the application server, the Lync server and the environment. We tested that IMs could be sent on the system – even putting a client on the application server to see if IMs could be sent there (they could). Looking at the logging we had on the application we could see that the message just wasn’t ever reaching the application.

Looking at the SIP traffic, this was the error we saw:

Lync500Error

 

The Message start-line is: SIP/2.0 500 Internal Server Error and the ms-diagnostics error includes the cryptic message: No component handler.

On the Case

We finally resolved this when we went back to check the Trusted Application Endpoint settings. When they were created the SIPAddress value was set like “Sip:abc@domain.com” rather than the more standard “sip:abc@domain.com” (notice the capital S in the first example).

The single upper case S caused all incoming messages to fail. We simply changed the SipAddress property of the endpoint to a lower case s and everything started working.

So the rules are that you can only ever use lower case sip: as the SipAddress prefix!

@Microsoft: puuurlease! This stuff is hard enough already: if you’re not going to sanitize your PowerShell input, at least return a sensible error message. #NeverGettingThatTimeBack

Written by Tom Morgan

Tom is a Microsoft Teams Platform developer and Microsoft MVP who has been blogging for over a decade. Find out more.
Buy the book: Building and Developing Apps & Bots for Microsoft Teams. Now available to purchase online with free updates.

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share to Microsoft Teams