- #Lync for mac 2011 the system is unavailable now for mac#
- #Lync for mac 2011 the system is unavailable now update#
- #Lync for mac 2011 the system is unavailable now manual#
“ could not be reached and this message was not delivered” ģ) There *may be* such a user at the recipient’s domain – but they don’t have open Federation and THEY don’t trust YOUR domain. There’s an instance of OCS/Lync there & they have an Edge. There’s an instance of OCS/Lync there, they have an Edge, but you’ve simply nominated an invalid user – or guessed their e-mail naming format wrong.Ģ) There *is* such a user at the recipient’s domain – but they’re not enabled for Federation. I hope they make your life a little easier: Instant Messages “ could not be found and this message was not delivered”ġ) There is no such user at the recipient’s domain. Here are a few and what they might be indicating. I also wanted to thank for my colleague, Lync MCM Aidan Freeman for helping me troubleshoot this issue.Some of Lync’s Client-side error messages don’t really explain the reason for the failure. I find that the default configuration works just fine.
#Lync for mac 2011 the system is unavailable now manual#
With the correct DNS configuration, I haven’t found the need to use manual server configuration as suggested in numerous support articles.
#Lync for mac 2011 the system is unavailable now update#
I have logged the appropriate service request and will update this post once I have tested it.
#Lync for mac 2011 the system is unavailable now for mac#
Unfortunately, this workaround does not persist across reboots or hibernations.Īrticle ID: 2926055 “Description of the Microsoft Lync for Mac 2011 14.0.7 hotfix” describes a hotfix that should resolve this issue, unfortunately you need to contact Microsoft Customer Support Services to obtain this hotfix and I haven’t been able to obtain it yet. Once you have successfully logged in, you can change your time zone back to the correct configuration and you will still be able to log in.
![lync for mac 2011 the system is unavailable now lync for mac 2011 the system is unavailable now](https://i0.wp.com/y0av.me/wp-content/uploads/2015/04/enablenpapi.png)
I was able to confirm this by changing my time zone settings which resulted in my client immediately being able to log in. After a bit of searching around, we found Article ID: 2927775 “Can't sign in or see contact pictures in Lync for Mac 2011 when system time zone is set to UTC+8 or an earlier time zone” which exactly describes the issue which occurs because Lync for Mac 2011 calculates the expiration time of a web ticket based on an incorrect time zone. It seems Lync for Mac 2011 tries to use a web ticket that is expired.
![lync for mac 2011 the system is unavailable now lync for mac 2011 the system is unavailable now](https://images-na.ssl-images-amazon.com/images/I/516fDdMg3CL.jpg)
After digging into the client logs, we saw the following entry: I then tried using a different Mac with Lync for Mac version 14.0.6 and that one was able to log in without any issues. I tried using manual server configuration as suggested in the “ Troubleshoot sign in issues with Lync for Mac 2011 in Lync Online” article, but that didn’t make any difference either. If the problem continues, please contact your support team.” error message. Please verify your logon credentials and try again.
![lync for mac 2011 the system is unavailable now lync for mac 2011 the system is unavailable now](https://venturebeat.com/wp-content/uploads/2017/12/tidal3.jpg)
I tried a couple of other Lync accounts and still kept receiving the “Lync was unable to sign in. At first I thought I’d made a typo with my password but after a couple of attempts I knew something else was wrong. This was a newly installed an updated version of Lync for Mac 2011, version 14.0.7 (131205) to be exact. I recently came across an interesting issue when attempting to log into Lync Online using Lync for Mac 2011. Since writing the post, I have been able to obtain a copy of the hotfix described in KB2926055 and I can confirm that it does fix this issue.