Web Connection
COM issue
Gravatar is a globally recognized avatar based on your email address. COM issue
  Stein Goering
  All
  Sep 6, 2017 @ 08:54pm

Attempting to set up our app on a Win 2016 Server using the ISAPI protocols. It works in File Mode but we're getting this error when we try to switch to COM:

'Unable to retrieve a server instance from the server pool'

Not sure what our next step should be. Any suggestions would be appreciated.

--stein

Gravatar is a globally recognized avatar based on your email address. re: COM issue
  FoxInCloud Support - Thierry N.
  Stein Goering
  Sep 6, 2017 @ 10:24pm

did you check in Windows task manager if your exe is running?

Gravatar is a globally recognized avatar based on your email address. re: COM issue
  Stein Goering
  FoxInCloud Support - Thierry N.
  Sep 7, 2017 @ 07:32am

Thanks. I will have them do that.

Gravatar is a globally recognized avatar based on your email address. re: COM issue
  Stein Goering
  Stein Goering
  Sep 8, 2017 @ 10:07am

The problem was they were running under the .NET Managed Handler on this new server but were used to ISAPI on their old system. So they were trying to configure wc.ini instead of web.config.

--stein

Gravatar is a globally recognized avatar based on your email address. re: COM issue
  Rick Strahl
  Stein Goering
  Sep 8, 2017 @ 12:24pm

As they should, as they should ??

If I recall you have some specific issues that require you to use wc.dll, right? If not you really should consider moving to the .NET module for improved stability and performance.

+++ Rick ---

Gravatar is a globally recognized avatar based on your email address. re: COM issue
  Stein Goering
  Rick Strahl
  Sep 8, 2017 @ 10:25pm

No, I've got our app running on our development system under .NET and it's working fine. The only reason our customers continue to run the ISAPI module is simply inertia. It's working and they don't want to change. For the same reason, our tech support staff does not encourage them to make the switch.

In this case, the customer was moving to a new server so they did a fresh install and picked the .NET Handler from the setup wizard dropdown since it was the "preferred" choice, without realizing it was configured differently. They had copied wc.ini from their old server and thought it would pick up that configuration. Also, they set up a West Wind app pool but somehow didn't get it connected to their virtual directory (which caused the "unable to retrieve server instance" error. I sent them the text from my web.config to paste into their copy, and got them connected to the right app pool, so they are up and running. And now that I finally have a client running the .NET handler, I can use them as an example to encourage other customers to make the change.

--stein

© 1996-2017