10/24/2022 0 Comments Lync for mac 2011 conversation historySo I’d received the message OK, but no acknowledgement had gone back to Lync. In this scenario, I had switched tasks on my iPhone to another application and ignored the push message that had come through. This is a Mobility message – but not necessarily an error. “This message may not have been delivered to because the server sent the message to this person but it timed out.” This occurs because if you initiate, your establishing IM goes to the remote Edge’s Next-hop server, which IS known to the remote end’s Edge, and from there it’s on forwarded to their registrar). (This scenario will manifest itself as “1-way IMs” – you can start an IM conversation with the remote party all OK, but if THEY initiate a conversation to you, YOUR IMs will always receive a 504/239 – but you’ll still receive their messages. (This is an ongoing drama at the time of writing, as it seems very few Lync Edge servers trust this new intermediate cert).Ħ) The Edge at the far end doesn’t have a Hosts file entry for that user’s front-End or SBA. Error 14428 on the recipient’s Edge server confirms this issue – “The certificate chain was issued by an authority that is not trusted”. In a recent example, one of the intermediate certificates in the initiating party’s cert chain had been renewed, and this new cert wasn’t trusted by the remote end. Look for wrong or mis-configured DNS or NAT in the Topology.ĥ) Check ALL the certificates in the chain between you and the other end. If you can receive IM’s from someone and get this error when you reply, check their system’s external DNS or Edge config. (All the instances of Error 14502 in the Event Log on the new Lync server are a giveaway too!)Ĥ) Asynchronous routing / bad config. (Try a different Federated partner to check this).ģ) If you’re trying to contact a Federated party, this might be because you’ve added a new SBA or Front-End server to your Lync deployment but you’re still using an OCS Edge, and you haven’t added the new server to the Edge’s “trusted servers” list. (Try a different Federated partner to check this).Ģ) If you’re trying to contact a Federated party, then their Edge server is down. “When contacting your support team, reference error ID 504 (source ID 239)”ġ) If you’re trying to contact a Federated party, your Edge server is down. You’ve found a valid Lync/OCS user, but they’re not allowed to talk to you. Please don’t contact your support team with this information! Error 403 The domain is invalid, is not Lync/OCS, has no Edge/Federation, or your domain is blocked. Please contact your support team with this information” :-p “This message was not delivered to because the address is outside of your organization and is not federated with your company, or the address is incorrect. Slightly different to the above: could not be reached, rather than could not be found.ġ) Run “Get-CsArchivingConfiguration” and check you’re not set to block IM’s if Archiving fails. “ 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. Some of Lync’s Client-side error messages don’t really explain the reason for the failure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |