› Forums › Operating Systems › Windows Server 2008 › Miscellaneous › Dialup (!) issue
- This topic has 3 replies, 2 voices, and was last updated 16 years, 4 months ago by
Arris.
- AuthorPosts
-
- 4th February 2009 at 22:22 #48176
If I look at the list of services (Start -> Run -> services.msc) at this PC I see the Diagnostic Policy Service with Startup Type Automatic and Status Started so it should run even when you don’t directly use it. You can try to find out why the service directly stops after starting it by taking a look at the Applications log in the Event Viewer (Start -> Run -> eventwvr.msc). Maybe you can find more information about that problem there.
One more thing you can try is to map the guest serial port to an other COM port at the host machine so at least the COM port you want to use isn’t locked or something like that.
Hope this pushes you into the right direction. I can’t think of any other things to try/solutions for this weird problem at the moment…
- 6th February 2009 at 00:26 #48175
@Arris wrote:
You can try to find out why the service directly stops after starting it by taking a look at the Applications log in the Event Viewer (Start -> Run -> eventwvr.msc).
Well, thats where another problem starts…
Event Viewer
Event Log service is unavailable. Verify that the service is running.
@Arris wrote:
One more thing you can try is to map the guest serial port to an other COM port at the host machine so at least the COM port you want to use isn’t locked or something like that.
First thing I have tried – I removed the virtual serial port, but no help…
- 6th February 2009 at 07:53 #48174
Sounds like a really screwed up installation. You can try to find out using Sysinternals Process Monitor what’s wrong when starting the service. As a filter add: Process Name | is | svchost.exe | then | include, but maybe it’s still a lot of data you ‘ll see because lots of services are running under the svchost process.
Another possibility is to use the Last Known Good Configuration (advanced) option in the boot menu. To get there press repeatedly the F8 key on your keyboard before you see the Windows logo when booting up your pc.
If that all doesn’t work, I suggest a reinstallation because when even the Event Log service refuses to start, there is really something wrong.
- AuthorPosts
- You must be logged in to reply to this topic.