Hi,
This is a weird one. I came in to work this morning and the our Win2K3 server had installed updates overnight and re-booted itself. I logged on to the server, and as soon as the screen changed to display system clock in the tray and the desktop icons, the machine started doing a double beep every 2 or 3 seconds.
The server seems to be running fine. All the users are connected and accessing their shares and files, SQL server's running fine. Exchange is working fine. IIS is working fine.
I checked the event log and there's nothing unusual in there.
I tried rebooting. As the machine "unloaded" Windows, the beeping stopped. During the BIOS checking part of the reboot, there was no beeping. All the system checks seemed to go through without any problems. The operating system began to load and it reached the login prompt without any beeping. I entered the Username and password and it logged me on (restoring network connections etc)...still no beeping. The screen cleared to display the system clock and the desktop icons etc and all of a sudden the beeping returned.
I had wondered if there was a hardware malfunction on one of the components in the machine, but I wouldn't expect to have to log on to the operating system for the beeping to begin if this was the case.
For now (and for the sake of sanity) I've disabled the beep service so all is quiet, but I'd like to get to the bottom of this.
Has anyone got any ideas what might have caused this?
Thanks in advance,
Richard
This is a weird one. I came in to work this morning and the our Win2K3 server had installed updates overnight and re-booted itself. I logged on to the server, and as soon as the screen changed to display system clock in the tray and the desktop icons, the machine started doing a double beep every 2 or 3 seconds.
The server seems to be running fine. All the users are connected and accessing their shares and files, SQL server's running fine. Exchange is working fine. IIS is working fine.
I checked the event log and there's nothing unusual in there.
I tried rebooting. As the machine "unloaded" Windows, the beeping stopped. During the BIOS checking part of the reboot, there was no beeping. All the system checks seemed to go through without any problems. The operating system began to load and it reached the login prompt without any beeping. I entered the Username and password and it logged me on (restoring network connections etc)...still no beeping. The screen cleared to display the system clock and the desktop icons etc and all of a sudden the beeping returned.
I had wondered if there was a hardware malfunction on one of the components in the machine, but I wouldn't expect to have to log on to the operating system for the beeping to begin if this was the case.
For now (and for the sake of sanity) I've disabled the beep service so all is quiet, but I'd like to get to the bottom of this.
Has anyone got any ideas what might have caused this?
Thanks in advance,
Richard