Troubleshooting Event ID: 333

-

 Issue

With Microsoft Windows Server 2003, you get the following events and the server performance may be degraded:
Type: ErrorDate: DateTime: TimeEvent ID: 333Source: Application PopupUser: N/AComputer: MachineNameDescription:An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.
Additional symptoms that you might see with this event are the following:
  • Performance issues with the SQL databases.
  • Issues with cluster resources going offline.
  • File/Print server performance issues.
  • Login issues where you get insufficient memory errors and profile load issues.
  • Complete server hang.
  • SQL server error logs may report I/O related errors.

Solution

The Event ID 333s are written to the system event log if the Microsoft Windows operating system is not able to flush and write to the registry hive.
Event ID 333s can occur due to the following causes:
  • Cause 1 : There is a memory contention (Page pool/Non-page pool depletion, low system PTEs, and so on).
  • Cause 2 : An older filter/kernel driver is keeping the registry from being flushed.
  • Cause 3 : The disk subsystem is not able to handle the load (example: high disk queue lengths).
The first step towards solving the issue is to collect the required logs to be able to identify the exact cause. Nothing can be concluded by just looking at the events in the event viewer and by observing the symptom.
The following logs are required:
  • Performance Monitor (PerfMon ) logs with shorter sample intervals.
  • MemSnap/Poolmon Logs.
  • In extreme cases, a manually generated memory dump would also be required.
Troubleshooting for Cause 1:
Update to the latest kernel using Microsoft Knowledge Base Article 935926, A Windows Server 2003-based computer stops responding when the registry is in heavy use :
 
Click here to go to Microsoft Knowledge Base Article 935926 (http://support.microsoft.com/kb/935926) .
 
Update the SRV.SYS file using Microsoft Knowledge Base Article 955280, When you use a file handle for FileStream access in a SQL Server 2008 transaction, the transaction may randomly fail to commit in Windows Server 2003 or in Windows XP Professional x64 Edition :
 
Click here to go to Microsoft Knowledge Base Article 955280 (http://support.microsoft.com/kb/955280) .
 
Update the VOLSNAP.SYS file using Microsoft Knowledge Base Article 940349, Availability of a Volume Shadow Copy Service (VSS) update rollup package for Windows Server 2003 to resolve some VSS snapshot issues :
 
Click here to go to Microsoft Knowledge Base Article 940349 (http://support.microsoft.com/kb/940349) .
 
NOTE: At the time this article was written, the previously mentioned Microsoft Knowledge Base articles were the latest for the corresponding components. Check Microsoft’s support site to see if any newer versions of the respective files are available.
 
Troubleshooting for Cause 2:
From the HPS report, look at the SERVERNAME_PSTAT.txt file and see if you have any older filter drivers. Filter drivers are usually the drivers from anti-virus and backup software. Check the respective vendor’s sites.
 
Troubleshooting for Cause 3:
If you have identified the cause as a disk latency issue, then complete the following steps:
  1. Update Microsoft STORPORT.SYS to the latest version using Microsoft Knowledge Base Article 950903, The system may not detect that a logical unit was replaced on a Windows Server 2003-based computer .
  2. Identify the miniport driver version for the storage device that is configured on the server, and then update that by contacting the respective vendor.
    IMPORTANT : Before installing the STORPORT.SYS update, it is extremely important to engage the storage vendor first to ask which version of the Microsoft’s STORPORT.SYS that they approve and provide the update based on that. The storage vendor will not support all the versions of Microsoft’s STORPORT.SYS .
    It’s also important to maintain the order of the installation as specified.
     
    Source :

    http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&dlc=en&docname=c01682687&lc=en&jumpid=reg_r1002_usen_c-001_title_r0001

Comments

Post a Comment

Popular posts from this blog

Python reference Interview questions

-
1)HCL Python scripting developer Interview questions:- 1) How do you check list of files in the given path in python ?? 2) How do you check whether file is exist or not in python 3) How do you perform copy file cmd in python ?? 4) What is d use of setup.py in python 5) What is d use of __init__=__main__: condition in python?? 6) What is d type of *args and **kargs ?? 7) sys.path use in python ??   2) CES Limited Python developer Interview Face2Face Interview questions:- 1.Basic questions on oops:   *.Implement Base class using Instance, static and Abstract method     instance method - takes two arguments to add operation     static method - takes two args to multiply operation     abstract method - takes two args to div operation   *. Implement child class using 3 instance methods     instance - takes three args for add operation     instance - takes two args for...
Read more

[SOLVED]* Please wait for the system Event Notification service

-
Image
There are different ways to solve this issue , Few of them are mentioned below .A permanent fix for this issue is yet to find. Solution : 1 Remove "Windows Live Messenger" from their terminal server resolved logout issues. Solution : 2 Start "Remote Desktop Services Manager" Identify the user ID in the Users tab In the Processes tab sort by ID Go down to the user ID and end the winlogon.exe process the user session will be logged off Solution : 3 From: mikefrobbins.com by graham ross From a command prompt on my PC or another computer on the domain I ran this to find out the PID of the svchost.exe associated with SENS sc \servername queryex SENS Note down the PID of that process and kill that process using PID. taskkill /S servername /PID xxxx /F Solution: 4 From : Windows Sever Forum The COM+ Event System timed out attempting to fire the Logoff method on event class {D5978650-5B9F-11D1-8DD2-00AA004ABD5E} for publisher and subscriber . The subscriber failed ...
Read more

Rebuild the initial ramdisk image in Red Hat Enterprise Linux

-
How to rebuild the initial ramdisk image in Red Hat Enterprise Linux  SOLUTION VERIFIED  - Updated  April 12 2016 at 10:15 AM  -  English  Environment Red Hat Enterprise Linux (RHEL) 3 Red Hat Enterprise Linux (RHEL) 4 Red Hat Enterprise Linux (RHEL) 5 Red Hat Enterprise Linux (RHEL) 6 Red Hat Enterprise Linux (RHEL) 7 initrd / initramfs image Issue How to rebuild the initial ramdisk image in Red Hat Enterprise Linux How to remake or recreate the initrd or initramfs The  /etc/lvm/lvm.conf  and root file system resides on a logical volume. How to ensure the changes are applied upon rebooting? The  /etc/multipath.conf  and my root file system resides on a multipath device. How to ensure the changes are applied upon rebooting? The module options in  /etc/modprobe.conf  or  /etc/modprobe.d/  have been modified. How to ensure the changes are applied upon rebooting? Resolution When adding new ha...
Read more