Lync 2010: debug SIP issues

Use Lync Server 2010 Logging Tool.
You can run the Lync Server 2010 Logging Tool on the other computer by installing the Lync Server administrative tools on that computer. OCSLogger.exe is the file that runs Logging Tool, which by default is installed to %ProgramFiles%\Common Files\Microsoft Lync Server 2010\Tracing.

In order to best diagnose issues with SIP you must select the above Logging Options Components:

  • S4 -> Level: All and Flags: All_Flags
  • SIPStack -> Level: All and Flags: All_Flags

Start and Analyze log files.

Windows 8 CP: error parsing c:\windows\microsoft.NET\framework\v2.0.50727\config\machine.config parser returned error 0xC00CE556

In Windows 8 DP, .NET 2.0 application running, the following error message:
error parsing c:\windows\microsoft.NEt\framework\v2.0.50727\config\machine.config parser returned error 0xC00CE556

Solution:
Go in the “c:\windows\microsoft.NET\framework\v2.0.50727\config” directory, and renamed the “machine.config” to “machine.config.backup”, and then copied the “machine.config.default” to “machine.config”, worked fine.

Lync 2010: misconfig error, EWS and MAPI config not found (but Lync client connected)

The Autodiscover service in Exchange system is not set correctly.
Set correctly, according to the system.

If you do not necessarily need the service (elsewhere), a DNS entry is sufficient:
A SRV record to EWS Exchange szerver (port 443):

_autodiscover._tcp.yourdomain (eg.:_autodiscover._tcp.contoso.com)

 

SQL server login failed: Login Failed. The login is from an untrusted domain and cannot be used with Windows authentication. (Microsoft SQL Server, Error: 18452)

If the SQL server after we install the server alias (CNAME in DNS), the server can not connect to the name.

Solution:
Disable NTLM reflection protection

Create a new DWORD with the name DisableLoopbackCheck and value 1 in the registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Restart the computer. Done.

Update:
This opens it for Man In The Middle attacks, not use in public machine, only for test!

Update #2: (a correct solution)

Register a SPN for the SQL Service
SetSpn -A MSSQLSvc/_fqdn_name_:1433 DOMAIN\sql_service_account

Lync 2010 error: Multiple pool objects found in Active Directory with the name…

In publish topology, or add a new user to Lync system.

Error: Multiple pool objects found in Active Directory with the name X:X or FQDN _your_fqdn_servername_ . Ensure your deployment does not use conflicting pool information, and clean up any stale entries from deactivated pools to continue.

Solution:

  • Open the ADSIEDIT.MSC tool.
  • Use the Select a well known Naming Context selection to choose Configuration.
  • Expand the Configuration container to browse to CN=Pools,CN=RTC Service,CN=Services,CN=Configuration,DC=Contoso,DC=com.
  • Select CN=Pools and view the Pool entry information in the Details pane.
  • Locate and delete entries that should be listed in the Name column.