IIS 7 and Above
UI & Remote Management
Unable to start WMSVC - or connect - kind of
Last post Dec 03, 2011 02:14 PM by mindaugas
Jul 19, 2007 02:41 AM|OWScott|LINK
I installed the Management Service and successful set everything up. I connected from a Windows Vista machine and life was good.
All of a sudden, after stopping it and changing to port 8173 for testing purposes and then trying to start the service again, I was unable to start the service. I reversed everything but that didn't help. After trying for a bit, I through I would try using
Local System. Using Local System the service started up, but I'm unable to connect to anything remotely. (this is 10 minutes after everything worked perfectly)
The error I get is:
Connect to Site
Could not connect to the specified computer.
Details: The underlying connection was closed: An unexpected error occurred on a send.
Event viewer doesn't offer any suggestions except that the WMSVC service keeps failing and starting again and that it has done this 1 time unexpectantly.
The logs only show logs exactly like this, except for the date:
2007-07-18 03:02:00 ::1 GET /ping.axd - 8172 - ::1 Mozilla/4.0+(compatible;+Win32;+WinHttp.WinHttpRequest.5) 200 0 0
For one, how do I switch back to Local Service when I don't know the password? And, what else can I do to troubleshoot? I tried with my administrator account but it does the same thing as Local System.
Note, this error is when testing on the local server too, and I've tested with windows firewall turned off. Also note that it worked 10 minutes before and I changed virtually nothing in the meantime, so I do know that everything was configured correctly.
Jul 19, 2007 03:00 AM|OWScott|LINK
Further on this. I do see this entry in Event Viewer, but only if I log in using Window auth. If I use IIS Manager auth, it doesn't record anything except that the service failed and started up again.
An account failed to log on.
Security ID: IIS7\Administrator
Account Name: Administrator
Account Domain: IIS7
Logon ID: 0x3f39f
Logon Type: 5
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: -
Account Domain: -
Failure Reason: An Error occured during Logon.
Sub Status: 0xc0000022
Caller Process ID: 0xbc0
Caller Process Name: C:\Windows\System32\inetsrv\WMSvc.exe
Just prior to this are some successful connections for the same administrator user. Also, when the service is stopped, the error message is different, so I know that it's at least touching the service.
Jul 19, 2007 05:14 PM|NitashaV|LINK
It seems that the http bindings for wmsvc are messed up.
Try the following from cmd line window on the server machine "netsh http show sslcert" and see if the correct port /certificate combo are configured for wmsvc.
In order to work around this issue try changing the certificate (along with the port) used for Management Service. The try starting wmsvc.
Jul 19, 2007 05:53 PM|OWScott|LINK
I think you're on to something. "netsh http show sslcert" didn't show anything so I installed a different cert. It was a wildcard cert and didn't work so I tried a 3rd time with a regular cert. It still didn't work. I changed the port to 8173 and in
IIS Manager I use localhost:8173 but it still fails. (when I just use localhost, or localhost:8174 (bogus port) I get an error that it can't find the server, so again, I can tell that it's making it part way there.
"netsh http show sslcert" still shows blank though.
Jul 19, 2007 06:06 PM|NitashaV|LINK
Huh...are you using Server Beta 3 on the server and latest version of RemoteMgr client on Vista? We fixed this issue for Server Beta 3.
Anyways lets fix this issue -
Let me know if this works.
Jul 19, 2007 06:39 PM|OWScott|LINK
Sweet!! That did it.
I wasn't testing using the mismatched versions at the time, but I had before. In fact, it broke after that test, I just didn't realize it was from that.
The last test I did in IIS Manager wasn't with the same bindings so after running this from the command line, the IIS Manager GUI was off. It wouldn't let me put them back, saying that they were already in use. I just updated the registry key (HKLM\software\microsoft\webmanagement\server),
restarting IIS Manager and everything is working perfectly!
Oh, one last question. Is this just a beta issue? Later will mismatched versions play nicely together?
Jul 19, 2007 09:57 PM|NitashaV|LINK
This issue has already been fixed on later builds.
Yes thats the idea :)
Jul 20, 2007 04:54 AM|OWScott|LINK
Cool, I figured you would have it under control. :)
Aug 09, 2007 03:29 AM|OWScott|LINK
I'm running into a similar issue again. I've since updated my server to the latest bits but my Vista client is still the same. (One I downloaded from iis.net about 3 weeks ago)
From the local machine everything works good, but when connecting remotely it allows me to authenticate, then it shows me the certificate warning because it's a self-signed cert. Then it says that the server returned a 404 error. Here's what are in the
2007-08-09 03:15:10 192.168.77.52 GET /Login.axd loginOnly=1&retrieveUrl=1& 8172 - 192.168.77.106 WebManagementShell|184.108.40.206|2.0.50727.312|System.Windows.Forms.Control 404 4 0 203
Any idea what to check for?
Aug 22, 2007 05:12 PM|NitashaV|LINK
An event should also be thrown on the server machine, Can you tell me its details from the eventvwr --> Windows Logs --> Application?
Aug 23, 2007 03:42 PM|OWScott|LINK
Event Viewer doesn't give any clues. There aren't any for the time that I tested. I even did an iisreset, waited a minute and then tried again, just in case there was any caching. Still clean as a whistle.
I can view it from the local box using IIS or Windows credentional, just not from a Vista machine with the Microsoft Web Manager installed.
I still get the 404 Not Found error.
Aug 27, 2007 10:20 PM|NitashaV|LINK
What is the version of the server you are using? The RemoteMgr client on iis.net was supposed to work against Server Beta 3 only. You might have hit a version mismatch issue.
Were you connecting as an iis manager user or windows user? For windows users the events are logged to Security folder instead of Applications.
Dec 03, 2011 02:14 PM|mindaugas|LINK
I know this is a really old thread, but I just had the same issue with a brand new build. I tried the stuff in this post, but it didn't help. So I just created a new self signed cert and deleted the one created with IIS. I reassigned to web management service
and it fixed the issue.