Please register your software to receive critical software updates
We have received your registration. Thank you.
Your download should start automatically
Please note: Busylight won't start if there no compatible Microsoft Lync or Skype for Business client installed.
If a user is experiencing issues with Busylight (i.e. Busylight does not light up), please ensure the user:
If Busylight does not start or function correctly after Office was installed or updated (and some cases removed), it’s typically because some registry values got messed up - in particular when upgrading to Office 2016/Office365 x64. Please keep this in mind when choosing x32 over x64 of Office.
Running a repair on your Microsoft Office will typically fix the broken registry entries:
Busylight UC for Lync/SfB requires .Net framework 3.5. On some Win8 and Win8.1 machines .NET 3.5 has been deactivated. Please see this guide on how to enable it: http://msdn.microsoft.com/en-us/library/hh506443.aspx
If you are sure you have .Net 3.5 installed, please confirm that the installed version matches the bit-version of your Windows.
When you know you are running the correct version of .Net 3.5 but still having problems, please try a repair of .Net 3.5.
The Busylight Software is using the Microsoft Lync SDK to connect to the running instance of the Microsoft Skype for Business client (aka Lync client).
The LyncSDK uses the Windows Component Object Model (COM) infrastructure, which hides the different Client versions and 32/64 bit instances.
(see https://en.wikipedia.org/wiki/Component_Object_Model for details)
The COM part is implemented and installed with the Microsoft Skype for Business/Lync installation, not with the Busylight software. If there are error messages in the DebugView log like:
They will indicate problems within the COM configuration or the specific DLL or COM files.
Unfortunately, Busylight cannot repair these issues, because they belong to the Skype for Business / Lync or Office setup. Repairing the Office installation can repair the COM issues in most cases.
However, a broken COM configuration sometimes fails to repair with this procedure. In that case, a complete reinstallation of the PC (including Windows) is required.