Messages
Reply
Edit
Delete12:36 am
3TZ01BI5X
| From: | Rick Strahl |
| To: | Jamie Osborn |
It sounds like either COM permissions on hte server (Launch and Access Permissions in DCOMCNFG) or that the server is launching but crashing during launch (ie. in the Init() or Load() methods) most likely.
If you can test this locally, you might want to configure as Interactive User and see if you can see any sort of messages from VFP popping up.
Another thing to do might be to use the DCOMCNFG tools that come with Web Connection which ensure that the right settings are applied. Take a look in the docs for DCOM COM Configuration - this will set the account and launch/access permissions. Make sure that whatever account you configure has rights to do what it needs to.
+++ Rick ---
Apologies in advance if this is WWC 101.
I have a server running fine in file mode but not responding when switching to COM mode.
The situation is:
1. I have manually set up to run in COM mode via DCOMCNFG (I've just always done it manually).
2. I can instantiate the com object in VFP and the ProcessHit() test works fine.
3. I can launch the EXE via COM in the ISAPI config admin page
4. The exe doesn't respond to hits at all in COM mode.
5. If I run another copy of the exe (simply run it from Windows Explorer), this new copy does respond to the hits, even though the virtual is running in COM mode.
Does this mean the virtual is still running in file mode, even though the wc.ini and isapi config page say com mode?
Cheers,
Jamie
Rick Strahl
West Wind Technologies
