Saturday, June 29, 2013

Error 5 when deploying Lync - external schema ldf fails

This error typically happens if your logged in an then added to schema admin group. To resolve log off and log back in. Proceed with install.

Monday, June 24, 2013

Lync 2013 crashes on startup

Error looks like this:
Faulting application name: lync.exe, version: 15.0.4454.xxxx
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\lync.exe
Faulting module path: unknown

To fix, try disabling hardware acceleration

Run regedit
Browse to HKEY_CURRENT_USER\Software\Microsoft\Office\15\Common
Create a New Key and name it "Graphics"
Select Graphics, right-click on the right panel and create a New DWORD (32-bit) Value and name it DisableHardwareAcceleration.
Enter Value data as 1
Restart the workstation
Launch Lync

Note: The example I use above “15” is Office 2013, “14” Office 2010, “12” Office 2007. If that does not do the trick, ABBYY-FineReader (Epson) has also been known to cause Office apps to crash. May be worth a try if you have ABBY-Finereader installed on the workstation.

Go to Control Panel
Click on Uninstall a program
Right click on ABBYY-FineReader and click uninstall.
Restart the workstation


Sunday, June 23, 2013

Error code 0xC3F7580A when moving user OCS to Lync

Result Code: 0xC3F7580A
Cannot move user from pool. Error: 0xC3F7580A Cause: The server is not responding. Resolution: Verify the health of the pool. If a load balancer is used, please check to make sure port 135 is enabled. Check product documentation for more information about load balancer configuration.

If you experience this error look up user on the OCS FE server in AD Users and Computers and select Communications Tab. Uncheck box > "Enable user for Office Communications Server > Select apply > ok. Then go back in to Communication's Tab > check box "Enable user for Office Communications Server > Select apply > ok. Try moving user again.