Are you referring to running setup as admin? If so, we did that.The WWWC 4 sample page that calls various examples as well as any other WWWC based exe we run seems to start WWWC (I think wcp3 or something like that). But WWWC never sees any requests. It is not seeing a request and then not able to access, but even if you call the ec.dll directly -- which should produce results or at least an error -- you get nothing.
If you are running on windows 7 ... it might be admin rights. I had similar issues. Eventually, I right mouse clicked on the application and ran as administrator ( even though my account is an administrator) and had sucess there.
Hope this helps
All the IIS options, every one of them, is installed and we still get that message.
Tuvia,
Moniker cannot be found means the IIS Metabase configuration classes aren't installed. Make sure you install IIS and all the required components:
wcdocs:_22f0xkbmq.htm
Pay particular attention to the IIS features figure in this document.
+++ Rick ---
I have installed wc 4 on numerous servers, but I cannot figure what I missed on this server. I ran setup and installed to c:\wconnect. I created my virtual site and script map and verified my ISAPI handlers and permissions.
I cannot use console.exe (in 4 I rarely can with IIS 7) however when I tried I got a message at the end I have never seen : MONIKER cannot be found. I assumed it was becaise I am running older version 4 on the latest IIS.
When I start an wc app, it loads in file mode and everything looks correct. HOwever when I try to access the scriptmap site from the browser, no requests go to WC and we just spin.
I am using FoxInCloud and therefore must use WC 4, which almost always results in me having to do many manual tweaks. I have never successfuly been able to automate site creation.
But I have never had this much trouble before, and I am looking quite bad.
Any help appreciated, either here in the forum or willing to take a look at the server.
Thanks
![]()