In all my experience with Windows NT, I've never seen this happen before.
One lovely morning, my WinNt 4 server was running in perfect harmony with exchange 5.5. Later that day, I updated the virus definitions of my (Group Shield) antivirus program. Once the update was through, good ol' WinNt was kind enough to ask me if I would like to restart her now or later; To which I opted to restart much later when everybody else had logged off.
Now bear in mind I've done this countless times and this has never been a problem. But the following morning (very early), I restarted the server before anyone had logged on (as usual) and yes, you guessed it, all hell broke lose. Allow me to elaborate:
1. For starters the services console was BLANK, which meant that none of the applications that rely on the services console could run such as Event View to track the problem or User Manager, etc.
2. The server IS the main Domain Controller and is synchronized with another backup WinNT4 server which I tried to promote as the Primary Server but alas, could not FIND the main DC.
3. When I open my Windows NT Diagnostics tool and click on the Services tab, nothing is displayed other than this: "Error 1060 opening Service Controller on \\Servername"
4. I've combed through countless sites (including bill's knowledge base), trying to get answers but nothing solid has addressed my problem.
Dear Tek-Tips.com threadsters, HELP!!!
One lovely morning, my WinNt 4 server was running in perfect harmony with exchange 5.5. Later that day, I updated the virus definitions of my (Group Shield) antivirus program. Once the update was through, good ol' WinNt was kind enough to ask me if I would like to restart her now or later; To which I opted to restart much later when everybody else had logged off.
Now bear in mind I've done this countless times and this has never been a problem. But the following morning (very early), I restarted the server before anyone had logged on (as usual) and yes, you guessed it, all hell broke lose. Allow me to elaborate:
1. For starters the services console was BLANK, which meant that none of the applications that rely on the services console could run such as Event View to track the problem or User Manager, etc.
2. The server IS the main Domain Controller and is synchronized with another backup WinNT4 server which I tried to promote as the Primary Server but alas, could not FIND the main DC.
3. When I open my Windows NT Diagnostics tool and click on the Services tab, nothing is displayed other than this: "Error 1060 opening Service Controller on \\Servername"
4. I've combed through countless sites (including bill's knowledge base), trying to get answers but nothing solid has addressed my problem.
Dear Tek-Tips.com threadsters, HELP!!!