B
Benjamin Templeton
Environment:
Win2000 Server Service Pack 4.0
IE 5.0 Service Pack 4.0
hotfixes: KB823980 (loaded Aug 8th), KB824146 (loaded Sep 17th)
Terminal Service Manager 5.0 Service Pack 4.0
windows 2000 compatibility setting on Terminal Services
Application installed on mapped S: drive that is mapped back to the local
C:\shared drive. All registry entries for the COM interface point to the
mapped S: drive. The type library's path in the registry has a UNC path to
the local machine where the COM server was installed. (ex:
HKEY_CLASSES_ROOT\CLSID\{1FC4B66F-3674-11D6-97A1-000058015458}\LocalServer32
points to S:\wincoder\cfextend.exe)
(ex:
HKEY_CLASSES_ROOT\TypeLib\{1FC4B660-3674-11D6-97A1-000058015458}\1.0\0\win32
points to \\local computer name\shared\wincoder\cfextend.exe)
DCOM enabled/disabled doesn't change the behavior at all.
I have a client that is experiencing some problems with an application that
I wrote and I don't know what is causing the problem. I have a COM server
(cfextend.exe) that provides a communication interface to another
application. That application gets an interface
-------
hr = CoCreateInstance(CLSID_CCodefinderLMRPExtension, NULL,
CLSCTX_LOCAL_SERVER,
IID_ICodefinderLMRPExtension, (void**)&g_pICodefinderLMRPExtension);
-------
to my COM server (cfextend.exe) and makes calls to it. The client has been
running problem free for 9 months when all of a sudden they began to
randomly (not all of the time...sometimes no problems for days other times
they have the same problem many times a day). When they would call
CoCreateInstance() it would sit and wait for ~30 seconds and then return the
error CO_E_SERVER_EXEC_FAILURE. In the event viewer you can see that DCOM
has registered an Error event ID 10010 that says "The server {my server info
here} did not register with DCOM within the required timeout."
I have set up a duplicate test environment in house but have NOT been able
to duplicate the problem. I have other clients that are running in the same
setup that have not had any problems. This behavior seems to be random
(sometimes it works sometimes it doesn't) in nature. It doesn't matter if
DCOM is enabled or disabled because the behavior is seen in either case.
Why would a LOCAL COM server be required to register with DCOM if it is
ALWAYS accessed from the local machine and NEVER remotely?
Does anyone know what is causing the behavior above?
Any help or guidance on where to further research this issue would be
greatly appreciated.
Benjamin Templeton
Win2000 Server Service Pack 4.0
IE 5.0 Service Pack 4.0
hotfixes: KB823980 (loaded Aug 8th), KB824146 (loaded Sep 17th)
Terminal Service Manager 5.0 Service Pack 4.0
windows 2000 compatibility setting on Terminal Services
Application installed on mapped S: drive that is mapped back to the local
C:\shared drive. All registry entries for the COM interface point to the
mapped S: drive. The type library's path in the registry has a UNC path to
the local machine where the COM server was installed. (ex:
HKEY_CLASSES_ROOT\CLSID\{1FC4B66F-3674-11D6-97A1-000058015458}\LocalServer32
points to S:\wincoder\cfextend.exe)
(ex:
HKEY_CLASSES_ROOT\TypeLib\{1FC4B660-3674-11D6-97A1-000058015458}\1.0\0\win32
points to \\local computer name\shared\wincoder\cfextend.exe)
DCOM enabled/disabled doesn't change the behavior at all.
I have a client that is experiencing some problems with an application that
I wrote and I don't know what is causing the problem. I have a COM server
(cfextend.exe) that provides a communication interface to another
application. That application gets an interface
-------
hr = CoCreateInstance(CLSID_CCodefinderLMRPExtension, NULL,
CLSCTX_LOCAL_SERVER,
IID_ICodefinderLMRPExtension, (void**)&g_pICodefinderLMRPExtension);
-------
to my COM server (cfextend.exe) and makes calls to it. The client has been
running problem free for 9 months when all of a sudden they began to
randomly (not all of the time...sometimes no problems for days other times
they have the same problem many times a day). When they would call
CoCreateInstance() it would sit and wait for ~30 seconds and then return the
error CO_E_SERVER_EXEC_FAILURE. In the event viewer you can see that DCOM
has registered an Error event ID 10010 that says "The server {my server info
here} did not register with DCOM within the required timeout."
I have set up a duplicate test environment in house but have NOT been able
to duplicate the problem. I have other clients that are running in the same
setup that have not had any problems. This behavior seems to be random
(sometimes it works sometimes it doesn't) in nature. It doesn't matter if
DCOM is enabled or disabled because the behavior is seen in either case.
Why would a LOCAL COM server be required to register with DCOM if it is
ALWAYS accessed from the local machine and NEVER remotely?
Does anyone know what is causing the behavior above?
Any help or guidance on where to further research this issue would be
greatly appreciated.
Benjamin Templeton