Messages
Reply to this message10:09 am
3NH0LRN6V
| From: | Brett Baggott |
| To: | Dan Scott-Raynsford |
First, before doing anything, I put the servers in file mode and make sure that works. You'd be surprised the number of times just doing that has highlighted an issue I was sure wasn't a problem.
Assuming file mode works fine, my next step is somewhat new but it has proven invaluable. That is, I use the new Http Handler Module (I've actually moved to this permanently based on my problems with DCOM).
Assuming the Http Handler Module works, that means we definitely do have a DCOM issue (even though I might "know" this based on the error, I still follow the process).
Next, I double check all my identities and locations making sure my .ini files line up with each other.
Next I do what you said you've done and unreg / re-reg the server, remove all DCOM entries and create them from scratch.
Then, because it's got me SO MANY times, I make sure to IISRESET, _then_ I see if everything starts working.
It sounds like you've covered all this so far but are still having problems. My one final tip to you is to at least try the Http Handler Module. It's made my life so much easier.
Hi Rick,
I've checked that the AppPool is running under Local System (the highest account). This is running on a W2K3 Server SP2.
The WC.DLL is set to Allowed in IIS Web Service Extensions.
Going to the ShowStatus page the Current Login is SYSTEM.
We've unregistered the DCOM servers and re-registered them. We've even deleted the DCOM registry entries for the server (didn't like doing this) and re-registered them.
In DCOM mode the servers start up under the correct account (as per the DCOM identity page) - we can see them in task manager. They sit there using about 6MB memory. They ignore all commands to End Process (e.g. they don't terminate). After about 2-3 minutes the servers seem to end on their own and then the "An internal exception occurred in the call to LoadServers (COM)" browser message appears - although sometimes the message is "An internal exception occurred in the ISAPI application".
We've disabled virus scanners on the servers. The client says that they have changed nothing on these server and no patches or updates have been installed.
We know something must have changed (three independent servers at the same facility don't all of a sudden have their DCOM fail at the same time) but we're at a loss as to what (and the client doesn't seem to know).
I've been using WWC for many years and although I've run into the occasional glitch with DCOM, I've never encountered something like this. Usually re registering the servers and reconfiguring DCOM and restarting IIS does the trick. But this time we've had 4 people working on the issue for 3.5 days now and just can't figure it out! I just hope it's not some obscure MS patch that some how breaks DCOM with VFP/WWC because we've got lots of other clients with this same setup and would hate to think they're one patch away from this.
Any insight you've got here would be greatly appreciated!
Thanks
Dan
Hmmm... this is an unhandled exception that didn't throw back COM error codes in that case, which is odd. LoadServers definitely should only fail if there's a COM error.
Can you make sure that you're running the right module (ie. either ISAPI or .NET Module) and that it's configured properly for the COM server (ie. has right prog ids).
Also make sure the IIS AppPool is running with a high access account and that whatever account that is hasn't changed either. If you go to:
wc.wc?_maintain~ShowStatus (or use whatever scriptmap is configured)
you should see all the actual logon account information that the app is running under. If necessary switch to file mode first if there are problems making it this far if the app gets hit in the meantime.
+++ Rick ---
Correction - the message in the browser is:
An internal exception occurred in the call to LoadServers (COM)
Hi Rick,
Thanks for your response. Our first thoughts were also the AD account changing in some way. So we got a new account created and reset the DCOM security with it - to no avail. I haven't tried setting the default access permissions yet but I'll do that now.
The browser error message that is being shown (I've never seen this before):
Web Connection Error
An internal exception in the call to LoadServers (COM)
Thanks
Dan
Hi Dan,
It sounds like the permissions on the AD account might have changed. If there was a password change or anything else about that account has changed you'll have to re-apply the DCOM Impersonation to make sure the account is still linked.
Other than that it sounds like the Launch permissions are working, but the Access permissions are not. So check your global DCOM settings and make sure that the account in question has rights to access DCOM components (It's in the Computer level COM+ Properties I believe).
To rule out problems it might be useful to launch the servers with SYSTEM or a local ADMIN account rights to see if permissions indeed are the problem. That should tell you right away...
What does the error message say in the browser when this fails? There should be a COM Error code plus a message that shows up in the browser if it's a DCOM load error.
+++ Rick ---
Hi Rick,
We have a client who have 3 servers - each running the same WWC 4.68 intranet servers (on 32-bit W2K3 Servers). There are two live servers and one test server.
About 2 days ago all 3 DCOM servers stopped loading properly or responding. The client _claims_ that no changes have been made to any of the 3 systems or the related databases. The WWC DCOM servers have been operating perfectly there for several months.
The DCOM settings have been completely reset on all 3 servers. The DCOM servers have been /unregistered and then /registered. A new AD account was also created and assigned to the DCOM identity. The Security of the DCOM servers has been set to Everyone has Local+Remote Launch and Everyone has Local+Remote Access permissions.
The servers operate _perfectly_ in File Mode when running under the same AD account that is assigned to the DCOM. In COM mode the servers do appear to start (they show up in Task Manager) - but they have a much smaller than expected memory footprint and do not respond and cannot be terminated using End Process. These unresponsive DCOM servers seem to shut automatically after a while but this appears to be because wc.dll is terminating them because they are timing out.
IIS has been restarted and the servers have been fully rebooted. The servers are 3 separate machines. Currently we have the Live system operating off a single machine running multiple servers in File Mode. The 2nd live machine is available to us for testing/checking.
These exact same servers and setups are in use at about 7 other sites without this issue.
The wcErrors.txt shows:
2012-11-20 07:39:13:888 Web Connection Request timed out. - ?atlas~start - 0
2012-11-20 08:32:28:836 Web Connection Request timed out. - ?atlas~start - 2
2012-11-20 08:32:28:836 Web Connection Request timed out. - ?atlas~start - 0
2012-11-20 08:39:02:138 An exception occurred in WC.DLL: _maintain~Load
Unloading all servers and reloading... - ?_maintain~Load - 0
2012-11-20 09:45:52:488 Exception in Loading Servers (COM) - 1008
2012-11-20 09:49:12:069 An exception occurred in WC.DLL: atlas~worksheetsavedoc~899219
Unloading all servers and reloading... - ?atlas~worksheetsavedoc~899219 - 0
2012-11-20 09:53:13:072 Exception in Loading Servers (COM) - 1008
2012-11-20 09:55:49:121 An exception occurred in WC.DLL: atlas~worksheetsavedoc~899219
Unloading all servers and reloading... - ?atlas~worksheetsavedoc~899219 - 0
2012-11-20 09:57:49:123 An exception occurred in WC.DLL: atlas~ps~platomain
Unloading all servers and reloading... - ?atlas~ps~platomain - 0
We've exhausted all our expertise on this. Do you have any thoughts on this and/or would you be available to assist the client at what ever your normal rates were (assuming you were available to do this)?
Thanks
Dan
~Brett
![Robert Priest - People Like You and Me (2024) [Hi-Res]](http://www.dibpic.com/uploads/posts/2025-07/1751805912_lhttl01vuwv8a_600.jpg)
