Using WWWC 4.68, one application suddenly will not run in com mode no matter what. In the task manager you can see the .exe file load, but then it always stops at a memory count lower than expected and stays there. Any attempt by WWWC to call it results in All Servers are Busy.
wcerrors.txt shows All Servers are Busy error 1008
The com object can be instantiated from a VFP session, and a server display window indicates the server has loaded, but any attempt to call any process fails in the same manner, so it is some sort of com problem it seems. It seems odd that it loads and shows the exe running but chokes somehow. Literally nothing has changed on the server configuration that I can find.
File mode is fine.
Have tried:
- unregister and reregister exe
- verify dcom permissions
- verify user rights
?
Sounds like missing access permissions or the server hangs in the process of loading.
Make sure the account the server is running under (verify in Task Manager) a) is configured properly in DCOM Config, and b) can do what it needs to to load data and whatever other resources.
If possible try testing the server from VFP (or a shell script) using the same account you are using when it runs in IIS.
+++ Rick ---
The server hangs would seem to be the problem. Given that it runs in file mode OK, not sure what it could be looking for that makes it hang.
Most likely you're hanging on a file open dialog. Since you're running in COM at the very beginning of your load handler in the startup use unattended mode SYS(2335,0) which avoids hangs, but will throw instead - that's not going to fix your problem but might produce different results that perhaps are more traceable.
You can also wrap the entire OnInit() and OnLoad() handlers into TRY/CATCH blocks and log out when you hit an exception.
FWIW, Web Connection 6 and later has a number of improvements that makes this much easier by automatically running the load handlers in trapped exception handlers and displaying errors. If it's a code error those things capture these startup errors and log them into a trace file.
If it's DCOM access rights error - that's obviously harder to fix, but for that scenario try running under SYSTEM or an ADMIN account to see if that works. If it does you can start dialing back security as needed.
+++ Rick ---
sys(2335)! I forgot all about using that. Will try.
Tuvia - did you have any luck trapping these errors?
ps: I have this issue from time to time with properly configured servers ,that seem to 'break' for no reason. I suspect it is from windows updates.
I did, but I do not recall the details except that it did have to do with a missing or misplaced file. VFP interactively could get the file so file mode worked, but the COM server could not get the file. I do not recall the details, sorry. Have not had it again.