Web Connection
Unable to retrieve COM Instance
Gravatar is a globally recognized avatar based on your email address. Unable to retrieve COM Instance
  FoxInCloud Support - Thierry N.
  All
  Aug 3, 2015 @ 01:49am
Hi,

Strange problem on a 5,7 (.NET Module) installation under COM mode:

webconnectionModule.dll keeps throwing "Unable to retrieve COM Instance" messages in wcError and loads additional COM instances, up to the point where all is saturated and Windows needs a reboot.

Works perfect in file mode.

Any idea what's happening?

Thanks,


Gravatar is a globally recognized avatar based on your email address. Re: Unable to retrieve COM Instance
  Rick Strahl
  Thierry Nivelet (FoxInCloud)
  Aug 3, 2015 @ 08:05am
Sounds like 1 of 2 things...

If you're running 5.72 the new error logging might shed some more light. Check the wctracelog.txt to see if there is any exception information in there. If you have an error in your server's startup code the COM instance will not be created and that will essentially hang the instance. If you have hard crashes the Windows Application event log will have more information.

The other thing might be COM permissions on the COM server. Make sure your ApplicationPool has the rights to launch the COM server and/or your impersonation on the COM server itself (if any - I recommend not to set any and use the ApplicationPool to set the permissions) has the rights needed to access data.

Watch specifically for mapped netowrk drives which are not available unless you map them yourself as part of the startup code.

+++ Rick ---


Hi,

Strange problem on a 5,7 (.NET Module) installation under COM mode:

webconnectionModule.dll keeps throwing "Unable to retrieve COM Instance" messages in wcError and loads additional COM instances, up to the point where all is saturated and Windows needs a reboot.

Works perfect in file mode.

Any idea what's happening?

Thanks,


Gravatar is a globally recognized avatar based on your email address. Re: Unable to retrieve COM Instance
  FoxInCloud Support - Thierry N.
  Rick Strahl
  Aug 3, 2015 @ 09:04pm
Thanks for your help!

Fixed with a simple "Reindex Web Connection System Files"
wwSession.fpt was bloated
<g>


Sounds like 1 of 2 things...

If you're running 5.72 the new error logging might shed some more light. Check the wctracelog.txt to see if there is any exception information in there. If you have an error in your server's startup code the COM instance will not be created and that will essentially hang the instance. If you have hard crashes the Windows Application event log will have more information.

The other thing might be COM permissions on the COM server. Make sure your ApplicationPool has the rights to launch the COM server and/or your impersonation on the COM server itself (if any - I recommend not to set any and use the ApplicationPool to set the permissions) has the rights needed to access data.

Watch specifically for mapped netowrk drives which are not available unless you map them yourself as part of the startup code.

+++ Rick ---


Hi,

Strange problem on a 5,7 (.NET Module) installation under COM mode:

webconnectionModule.dll keeps throwing "Unable to retrieve COM Instance" messages in wcError and loads additional COM instances, up to the point where all is saturated and Windows needs a reboot.

Works perfect in file mode.

Any idea what's happening?

Thanks,




-- thn (FoxInCloud)

Gravatar is a globally recognized avatar based on your email address. Re: Unable to retrieve COM Instance
  Rick Strahl
  Thierry Nivelet (FoxInCloud)
  Aug 4, 2015 @ 12:27pm
Hmmm... so what was the issue exactly? I would expect a bloated .FPT file to have an effect both on filebased and COM based operation...

+++ Rick ---



Thanks for your help!

Fixed with a simple "Reindex Web Connection System Files"
wwSession.fpt was bloated
<g>


Sounds like 1 of 2 things...

If you're running 5.72 the new error logging might shed some more light. Check the wctracelog.txt to see if there is any exception information in there. If you have an error in your server's startup code the COM instance will not be created and that will essentially hang the instance. If you have hard crashes the Windows Application event log will have more information.

The other thing might be COM permissions on the COM server. Make sure your ApplicationPool has the rights to launch the COM server and/or your impersonation on the COM server itself (if any - I recommend not to set any and use the ApplicationPool to set the permissions) has the rights needed to access data.

Watch specifically for mapped netowrk drives which are not available unless you map them yourself as part of the startup code.

+++ Rick ---


Hi,

Strange problem on a 5,7 (.NET Module) installation under COM mode:

webconnectionModule.dll keeps throwing "Unable to retrieve COM Instance" messages in wcError and loads additional COM instances, up to the point where all is saturated and Windows needs a reboot.

Works perfect in file mode.

Any idea what's happening?

Thanks,





Gravatar is a globally recognized avatar based on your email address. Re: Unable to retrieve COM Instance
  FoxInCloud Support - Thierry N.
  Rick Strahl
  Aug 4, 2015 @ 09:10pm
I agree with, this issue was definitely weird!

More details on what happened:
- running in COM mode, more and more instances loaded and server finally blocked
- switched to file mode, works fine, smile
- one hour later, server blocked as earlier described
- some errors on wwSession.Save() (though much less than the number of additional server instances)
- can only restart Windows Server

My interpretation:
- because of the bloated fpt, some servers get hanged when saving session
- having <add key="AutoStartServers" value="True" />, dll reloads an additional server

a question though,
process.onProcessInit() does:

AddProperty(m.this.oRequest, 'lBotSpider', lBotSpider(m.this.oRequest.getBrowser())) && lBotSpider(): modify command abTxt
IF m.this.oRequest.lBotSpider && request from a search engine bot

STORE CreateObject('wwSession') TO this.oSession, Session
Session.NewSession('BotSpider', 'BotSpider') && reuse the same session for all search engine bot

ELSE
...

note: lBotSpider() identifies search engine bots based on their 'user agent' string

Might be a good idea to never .save() the 'BotSpider' session.

Any thought?


Hmmm... so what was the issue exactly? I would expect a bloated .FPT file to have an effect both on filebased and COM based operation...

+++ Rick ---



Thanks for your help!

Fixed with a simple "Reindex Web Connection System Files"
wwSession.fpt was bloated
<g>


Sounds like 1 of 2 things...

If you're running 5.72 the new error logging might shed some more light. Check the wctracelog.txt to see if there is any exception information in there. If you have an error in your server's startup code the COM instance will not be created and that will essentially hang the instance. If you have hard crashes the Windows Application event log will have more information.

The other thing might be COM permissions on the COM server. Make sure your ApplicationPool has the rights to launch the COM server and/or your impersonation on the COM server itself (if any - I recommend not to set any and use the ApplicationPool to set the permissions) has the rights needed to access data.

Watch specifically for mapped netowrk drives which are not available unless you map them yourself as part of the startup code.

+++ Rick ---


Hi,

Strange problem on a 5,7 (.NET Module) installation under COM mode:

webconnectionModule.dll keeps throwing "Unable to retrieve COM Instance" messages in wcError and loads additional COM instances, up to the point where all is saturated and Windows needs a reboot.

Works perfect in file mode.

Any idea what's happening?

Thanks,







-- thn (FoxInCloud)

© 1996-2024