Lync 2013 on Windows 7.  I can initiate conversations with others, but one guy returns the wonderfully descriptive message:

"When contacting your support team, reference error ID 42 (source ID 238).

Troubleshooting information is available online, including best practices for using Lync."

Why did Microsoft stop putting actual English (or whatever your local language may be) in their error messages?  There is an entire generation of users who are used to troubleshooting on our own without having to constantly Google cryptic error messages.  Search for "error ID 42 (source ID 238), and that term does not appear in the results.  102 is there.  28 is there.  1028 is there.  97 is there. 504 is there.  But not error ID 42.  So I came to TechNet, and there is one article that showed up in the search terms.  This article mentioned nothing about error ID 42.

Since it's 42, I feel a need to channel Douglas Adams.

I'm so tired of this.  MS owns the world and acts like a tyrannical l

Hi,

I didn't find anything about the error ID 42 (source ID 238) either. Based on my experience, I would just search the Error message instead of the error ID to troubleshoot the issue. Sometimes even with the same error ID, different issues may be caused by different factors.

As for this issue, I suggest you post the question in the Lync forum below:

https://social.technet.microsoft.com/Forums/azure/en-US/home?category=lync

Regards,

Melon Chen
TechNet Community Su

See, Melon, that's the frustrating thing.  "...just search the Error message instead of the error ID..." - there was no message.  Only the ID.  I put the entire error text in my OP.

Why would MS remove the error text and force us to search for cryptic error codes?

Also, why would I post in Azure when this was installed on my computer along with Office 2013?  I don't have Azure.

I've been working on computers for 35 years.  I've seen them come a very long way.  And I don't like the path they are taking.  I really wish I had a DOS 3.3 machine with WordPerfect 4.0 again.  Those were the best years.  Easy to troubleshoot, simple to maintain.  Kinda like an old car.  Turn the key, replace the distributor cap, clean the carburetor...

Melon - please don't misunderstand my previous reply.  I appreciate you assistance in this matter.  I'm very frustrated with the route Almighty Microsoft has chosen to take.  My real problem isn't with the problem in Lync, it's with the error report itself.

Keep on rockin', amigo.

Also, why would I post in Azure when this was installed on my computer along with Office 2013?  I don't have Azure.

Clay, don't be misled by "azure" in the URL offered by Melon (that's just the MSFT forums platform oddity) - you'll get to the not-related-to-Azure-Lync forums.

Or, this way:

https://social.technet.microsoft.com/Forums/en-US/home?category=lync

Although you're dealing with Lync2013, the dedicated Lync forums (rather than here) are most likely a better bet for your scenario [ you need a Lync guru. they live there].

Maybe. (since weird error messages might, or might not, be resolvable in forums... but it's sure worth a try ;)