↧
From: | Tuvia Vinitsky |
To: | Rick Strahl |
Other issue could be the install isn't running as an administrator - you need admin rights in order to manipulate IIS. Normally this should be automatic since the name of the program is SETUP which auto-elevates. However if you're running Console.exe then it won't auto-elevate (except in the latest versions which has a manifest to request elevation).
+++ Rick ---
Did that originally, know about that. I will reinstall though and see what happens.
Moniker cannot be found means the IIS Metabase configuration classes aren't installed. Make sure you install IIS and all the required components:
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