An error occurred when attempting to detect if LiteSpeed was installed on .... The error message is: Failed to login to SQL Server
Another symptom might be "use LS engine" is greyed out or unavailable.
Also in the event log you might see something like this:
Description:
The COM+ Services DLL (comsvcs.dll) was unable to load because allocation of thread local storage failed.
Process Name: sqlservr.exe
Error Code = 0x80070008 : Not enough storage is available to process this command.
COM+ Services Internals Information:
File: e: ... ... comsvcs.cpp, Line: 334
Comsvcs.dll file version: ENU 2001.12.4720.3959 shp
This usually indicates a memory leak reported as a bug by Microsoft in Windows 2000, but it seems that the bug was not fixed in Windows 2003 as well.
This is the reference link from Microsoft: http://support.microsoft.com/kb/819989 and it is to be applied in a Windows 2000 environment. Unfortunately the issue is present in Windows 2003 as well.
This bug from Microsoft is rarely exposed when using LiteSpeed. The hotfix that Microsoft has offered was designed for 2000, but it seems that this was not fixed in 2003.
If using Windows 2003 when encountering this error, please reboot to fix the issue, or at least fail to the second node on the cluster.
Customer will need to contact the Micrsosoft Helpdesk for the bug fix.
This problem was solved in one of the post -SP2 COM+ 1.5 Hotfix Rollups. You do not have to install Windows Server 2003 R2 SP2 first to apply the latest COM+ Hotfix Rollup (Package 12). This rollup includes fixes from all rollups before that. It is also recommended that you install Windows Server 2003 MS DTC Hotfix Rollup Package 15 after that.
----------
We have seen this same issue caused by File Handle leaks caused by various applications/utilities including DoubleTake i3 and IBM Director. If the Handle Count is >100k for a server there may be an issue.
