dsasidhar
asked on
Event ID 1076 Source User32
Operating System is WIndows 2003 R2 Enterprise x64bit edition and its configured with NOD32 Antivirus and Microsoft Virtual Server for testing. The server gets restarted automatcially.
When i checked the even log i found as
Source: USER32 , Event ID: 1076, Type Warning.
The reason supplied by user SERVER\Administrator for the last unexpected shutdown of this computer is: Other Failure: System Unresponsive
Reason Code: 0x8000005
Bug ID:
Bugcheck String:
Comment:
Can some one help me in this how to resolve the issue.
error-msg-on-server.jpg
When i checked the even log i found as
Source: USER32 , Event ID: 1076, Type Warning.
The reason supplied by user SERVER\Administrator for the last unexpected shutdown of this computer is: Other Failure: System Unresponsive
Reason Code: 0x8000005
Bug ID:
Bugcheck String:
Comment:
Can some one help me in this how to resolve the issue.
error-msg-on-server.jpg
ASKER
Thanks for your reply Dan, Power Supply is working fine and all other Hardware and what could be the reason for this error.
Is your server configured to do memory dumps? If yes you can analyse this dumps to see what is happening. If not then configure the server to do that (right click on my computer, properties, advance, startup and recovery settings, check all.
If you have physiscal acces to the server you can disable automatic restarting, then you can see the BSoD and get more info from him.
Dan
If you have physiscal acces to the server you can disable automatic restarting, then you can see the BSoD and get more info from him.
Dan
ASKER
My server is configured to do Memory Dumps. Some time the server get restarted and some times it get shutdowned completely.
I haved checked all related but no result and when checked in the event viewer i get the error log event: 1076 and Source: USER32.
I haved checked all related but no result and when checked in the event viewer i get the error log event: 1076 and Source: USER32.
ASKER
My server is configured to do Memory Dumps. Some time the server get restarted and some times it get shutdowned completely.
I haved checked all related options by scanning virus and spam but nothing is effected and i found no spam or virus. When the server gets restarted or shutdown completely it genertes log event: 1076 and Source: USER32 in the event viewer.
I haved checked all related options by scanning virus and spam but nothing is effected and i found no spam or virus. When the server gets restarted or shutdown completely it genertes log event: 1076 and Source: USER32 in the event viewer.
The eventid.net say:
Error: Other (Unplanned), reason code: 0xa000000 - This event refers to the failure indicated by the previous EventLog 6008 event. The User32 1076 event is written when the first user with shutdown privileges logs on to the computer after an unexpected restart or shutdown and supplies a reason for the occurrence. An unexpected restart or shutdown is one that the system cannot anticipate, such as when the user pushes the computer''s reset button or unplugs the power cord.
A member of the Administrators security group can also log the reason for a remote computer's unexpected restart or shutdown using the Shutdown.exe tool. If many remote computers are unexpectedly shut down, as in the case of a power outage, Shutdown.exe provides a way for the administrator to remotely log the same shutdown reason on all the affected computers.
The User32 1076 event is written to the system log only when the Shutdown Event Tracker group policy setting is enabled or not configured on a computer running a Windows Server 2003 operating system. For more information about Shutdown Event Tracker group policy settings, see Help and Support.
No user action is required.
Do you have other errors in the log or that is the only error?
The server is restarting when the error ocurs?
Error: Other (Unplanned), reason code: 0xa000000 - This event refers to the failure indicated by the previous EventLog 6008 event. The User32 1076 event is written when the first user with shutdown privileges logs on to the computer after an unexpected restart or shutdown and supplies a reason for the occurrence. An unexpected restart or shutdown is one that the system cannot anticipate, such as when the user pushes the computer''s reset button or unplugs the power cord.
A member of the Administrators security group can also log the reason for a remote computer's unexpected restart or shutdown using the Shutdown.exe tool. If many remote computers are unexpectedly shut down, as in the case of a power outage, Shutdown.exe provides a way for the administrator to remotely log the same shutdown reason on all the affected computers.
The User32 1076 event is written to the system log only when the Shutdown Event Tracker group policy setting is enabled or not configured on a computer running a Windows Server 2003 operating system. For more information about Shutdown Event Tracker group policy settings, see Help and Support.
No user action is required.
Do you have other errors in the log or that is the only error?
The server is restarting when the error ocurs?
ASKER
Checked there are no other error logs. I am getting the same error frequently. Checked no problem in the memory.
Can any one help me out with some solution
Can any one help me out with some solution
ASKER
Supected as memory problem and replaced with new Memory Modules. It workded for a day with out any problem.
Still i it genertes log event: 1076 and Source: USER32 in the event viewer.
The reason supplied by user SERVER\Administrator for the last unexpected shutdown of this computer is: Other Failure: System Unresponsive
Reason Code: 0x8000005
Bug ID:
Bugcheck String:
Comment:
can any one suggest me what need to be done.
Still i it genertes log event: 1076 and Source: USER32 in the event viewer.
The reason supplied by user SERVER\Administrator for the last unexpected shutdown of this computer is: Other Failure: System Unresponsive
Reason Code: 0x8000005
Bug ID:
Bugcheck String:
Comment:
can any one suggest me what need to be done.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Well, thanks for sharing the solution...
For folks looking for answers, you might want to look at this article.
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=1076&EvtSrc=USER32&LCID=1033
If you have an unexptected reboot of the system or are continually rebooting, you might have to investigate further and post your own personal question. Look in event logs, and memory dumps. Also perform a sweep of your computer using an antispyware application.
Many things can reboot a server. This includes, but is not limited to,: Spyware, drivers, Windows updates, Windows installer, bad code, ect.... So, most likely, an unexpected reboot is will require more information than just event 1076. Troubleshooting is best on a case-by-case basis for this event.
I hope this helps the folks looking for answers.
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=1076&EvtSrc=USER32&LCID=1033
If you have an unexptected reboot of the system or are continually rebooting, you might have to investigate further and post your own personal question. Look in event logs, and memory dumps. Also perform a sweep of your computer using an antispyware application.
Many things can reboot a server. This includes, but is not limited to,: Spyware, drivers, Windows updates, Windows installer, bad code, ect.... So, most likely, an unexpected reboot is will require more information than just event 1076. Troubleshooting is best on a case-by-case basis for this event.
I hope this helps the folks looking for answers.
dsasidhar:
How did you resolve this issue, can you please update us on this,.
thanks
mc.
How did you resolve this issue, can you please update us on this,.
thanks
mc.
Well, usually this is wha you are selected when the server ask you what was happening with the unexpected shutdown earlier. So look again if you don't have more erreors in the log, then check the power suplly.
Dan