Windows 2003 Server hangs
Eric Fortin
The server hangs at startup (mys.dll/mys.hta)
I can ping another computer on my network, but I cannot access the internet.
It used to work. I installed PC Anywhere, rebooted (still worked), and then
Nortel Contivity Client. Stopped working after reboot. No error, just
hangs, and hangs, and hangs.
Hanging application mshta.exe version 6.0.3790.0
Steve Parry
can you press F8 at boot up and go in with safe mode then uninstall the Nortel software?
--
Steve Parry BA (Hons) MCP MVP
http://www.gwynfryn.co.uk
http://bmwmotorcycles.tripod.com
Eric Fortin
minutes, I finally get an event log error. The Server service hangs on
startup.
"Steve Parry" <k100r...@hotmailnospam.com> wrote in message
news:eba$kjAEDH...@TK2MSFTNGP09.phx.gbl...
Steven Zhang [MS]
Here is my understanding:
1. Windows Server 2003 hangs at startup.
2. The system will finally start after a long delay. But you cannot access Internet on the system.
3. The problem started happening soon after installing Nortel program. However, Nortel still works when the Windows Server 2003 starts after a long delay.
Could you help to confirm?
In addition, you can let us know the exact error message in the event log.
Have a great day!
Regards,
Steven Zhang
Microsoft Partner Online Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Eric Fortin
"Steven Zhang [MS]" <stev...@online.microsoft.com> wrote in message
news:WrkXtxGE...@cpmsftngxa06.phx.gbl...
> Hi Eric,
>
> Here is my understanding:
>
> 1. Windows Server 2003 hangs at startup.
Yes. Somewhere between 10 and 15 minutes, every time--no internet access
during that time.
> 2. The system will finally start after a long delay. But you cannot access
Internet on the system.
After the 10 - 15 minute delay (once the at least one service driver
failed), Internet is accessable. One note: I can ping another computer on
the network prior to the 10 - 15 minutes (during the initialization).
> 3. The problem started happening soon after installing Nortel program.
However, Nortel still works when the Windows Server 2003 starts after a long
delay.
That's correct. However, I did add the IIS Components (and all the other
windows components that are available for a computer in a workgroup --not a
domain)and the Nortel at the same time. The nortel works, so I think it has
something more to do with something I installed in IIS or the Windows
Components. I should have rebooted after installing the windows components,
but was never prompted to, so I just went along dumb and happy.
Additional Information that may help:
The workstation is part of a workgroup of 2 computers: My desktop and my
laptop.
It does Not have a static IP (although during the install, it said it should
(I even tried to change it, but I'm no networking expert, and I couldn't
figure out what to do.)
In trying to diagnose, all services that started logon
(something...network), I switched to the local system account (I read this
may the problem on groups.google.com). Now I don't know how to change it
back to the network (and it appears that other services also changed to the
logon account, but maybe not...).
>
> Could you help to confirm?
>
> In addition, you can let us know the exact error message in the event log.
The Server service hung on starting.
If I change it to manual, reboot, and start it manually, the computer takes
about a dozen seconds to do its initialization (faster than expected), and
only 10 or so seconds to start the service manually.
>
> Have a great day!
>
> Regards,
> Steven Zhang
> Microsoft Partner Online Support
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
Thanks Steven. Let me know if I can provide more/better information for you
and others.
If there is a more appropriate newsgroup (something Windows 2003) can
someone direct me to it. I couldn't find one. (I saw a post months ago
about connecting directly to the MS news server, but can't find how to do it
anymore--all I know is my news provider doesn't have one with win2003.)
Information That has nothing to do with my problem: Skip if you don't care:
I hate to be a whiner, but if anyone watching this group is from microsoft
and part of the development team, when trying to diagnose the event viewer,
every single time I click the hyperlink to help and support center for more
information, it always comes back with we're sorry, no info etc.. I saw
some kb that ms changed the q prefix, and maybe this is the problem (server
2003 being so new), but it's still very frustrating.
Also, trying to search kb, (say Event ID 7022), I do get results (not in the
best order), but half the time yahoo is a better search tool to get to the
appropriate kb articles than the ms site itself.
I love MS, and I don't usually have too many complaints, but the kb search
from ms can be very hard to find the right info.
Also, it is inconvenient to require me to select the reason for a shutdown
every single time. Perhaps it will, in the long run, help MS better their
product, and if the reason is to better the product in the future, I'll deal
with it. But if it's just for internal use (admins), I'd prefer to just be
able to shut down without selecting from the shutdown box and/or typing
comments.
Thanks.
Eric
Steven Zhang [MS]
Though initially composed for NT system, the following two Microsoft KB articles should provide some hints:
Services Do Not Start and an Event ID 7022 Message Is Logged in the
http://support.microsoft.com/default.aspx?scid=KB;EN-US;319127
Hung Server Service, Event 7022 w/ Many DLC Printers Connected
http://support.microsoft.com/default.aspx?scid=KB;EN-US;137399
Btw: there are quite a few Windows Server 2003 newgroups. You can refer to http://support.microsoft.com/newsgroups/default.aspx for newsgroup setup
instructions.
You can disable Shutdown Event Tracker in this way:
1. Start Registry Editor (Regedt32.exe).
2. Locate the ShutdownReasonUI value under the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Reliability
3. On the Edit menu, click REG_DWORD, type "0" (without the quotation marks), and then click OK.
4. Quit Registry Editor.
Thank you and have a great day!
Eric Fortin
I don't know how I missed those articles. (The second I saw as a hyperlink,
but based on the title disregarded.)
I will try to fix it (it seems like, despite not having specifically and
exactly those problems, the information may will still apply).
Again, thanks for the newsgroup info.
Eric
"Steven Zhang [MS]" <stev...@online.microsoft.com> wrote in message
news:e%23pj8c2E...@cpmsftngxa06.phx.gbl...