I cant figure this out and am stuck!!
About a couple of weeks ago I found out of nowhere that I keep getting event id 333 error
Event Type: Error
Event Source:Application Popup
Event Category:None
Event ID:333
Date:1/24/2008
Time:10:14:25 AM
User:N/A
Computer:SERVER1
Description:
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.
For more information, see Help and Support Center at http://go.microsoft.com/fw
Data:
0000: 00 00 00 00 01 00 6c 00 ......l.
0008: 00 00 00 00 4d 01 00 c0 ....M..À
0010: 00 00 00 00 4d 01 00 c0 ....M..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
and a couple of others such as ID2020. . While this is happening I noticed that on my other server which hosts symantec backupexec 11d Is gettng failure errors that states
Job Completion Status
Job ended: Thursday, January 24, 2008 at 4:35:34 AM
Completed status: Failed
Final error: 0xe000fed1 - A failure occurred querying the Writer status.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-65233
Errors
Click an error below to locate it in the job log
Backup- \\server1.xxx.local\Compan
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Check the Windows Event Viewer for details.
Writer Name: Registry, Writer ID: {AFBAB4A2-367D-4D15-A586-7
I heard that if you stopped APC PowerCute services that would stop the issue and was the culprit so I did what was stated rebooted and it stopped for about 2 days and BAM!! its back. Now Im reading that its due to too many keys being open or such and Im not sure if that is the issue. I am completely baffled, frustrated and desperately looking for an answer to resolve this issue!! PLEASE HELP!!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
PowerChute is designed to help your server shut down in the event your UPS detects it lost power. It is useful, but is very well known as far as causing problems. Just make sure you have the latest version from their web site.
I would hit Trend Micro's web site and see if there is an engine update available for you. Example: You bought version 10....but they could have versions 10.0.2, 10.1.3, and so on. So just make sure you are up to date.
If you see event 2020's that means you are exhausting your paged pool kernel memory. Look at this KB to tune your registry to fix that problem:
http://support.microsoft.c
I would start with this and it'll probably fix your issue.
I had a big problem with the /3GB switch in boot.ini doing similar things. Trend has been pretty stable on all of my servers so I dodn't suspect that it is the problem.
To check the boot.ini file open Notepad and open the file "c:\boot.ini" (assuming that C: is your boot partition). The file will be read-only by default but look for a parameter in the startup entry that reads "/3GB". You're looking for something similar to:
multi(0)disk(0)rdisk(1)par
If you don't have the /3GB parameter then this is not the issue. If you do have that parameter then you'll need to edit the boot.ini file to remove it. To do so:
Close the file in notepad.
Go to a command prompt.
Enter the following:
c: (or use the drive letter that the system boots to if not c:)
cd\
attrib boot.ini -s -h -r
notepad c:\boot.ini
(Make the change to remove the /3GB parameter and save the file)
Exit notepad.
Return to command prompt and enter:
c:
cd\
attrib boot.ini +s +h +r
Reboot the server.
An article discussing why /3GB switch is NOT recommended on SBS can be found here.
http://blogs.technet.com/s
THIS IS WHAT MY BOOT.INI FILE LOOKS LIKE NOW.
[boot loader]
timeout=30
default=multi(0)disk(0)rdi
[operating systems]
multi(0)disk(0)rdisk(0)par
C:\CMDCONS\BOOTSECT.DAT="M
AND IT SHOULD LIKE LIKE THIS AFTER CORRECT?
[boot loader]
timeout=30
default=multi(0)disk(0)rdi
[operating systems]
multi(0)disk(0)rdisk(0)par
C:\CMDCONS\BOOTSECT.DAT="M
IM SORRY I MEAN LIKE THIS:
[boot loader]
timeout=30
default=multi(0)disk(0)rdi
[operating systems]
multi(0)disk(0)rdisk(0)par
C:\CMDCONS\BOOTSECT.DAT="M
I'd also remove the /userva parameter so it ends up as:
[boot loader]
timeout=30
default=multi(0)disk(0)rdi
[operating systems]
multi(0)disk(0)rdisk(0)par
C:\CMDCONS\BOOTSECT.DAT="M
Is Backup Exec using the remote agent to hit the server that has a problem? The agent would consume resources when it is active.
When I recently fought this problem I spent about three weeks with memory tuning etc. and the server was running out of resources every day or two. After removing the /3GB the server's been up for 2 months nonstop.
If you get curious about the memory allocation try using Process Explorer for Microsoft Winternals. It will give you a good idea of what's going on. If you also install debug symbols (as outlined in the Process Explorer help file) you can see real-time paged and nonpaged pool utilization and also a before/after comparison when or if you remove the /3GB parameter.
The version of VSS that SP1 includes has big kernel memory issues. They have released a number of fixes leading up until sp2. If you are not comfortable downloading sp2 and installing on the servers I would considering calling MS and getting the latest rollup package for VSS as a step in this issue.
http://support.microsoft.c
I worked on a similar question:
Since this problem sarted a couple weeks ago, maybe this update is your problem and the answer is on this post as well.
http://support.microsoft.c
Oh, Yah:
Here is the referenced posting in EE:
http://www.experts-exchang
Business Accounts
Answer for Membership
by: PlaceboC6Posted on 2008-01-24 at 07:36:09ID: 20733918
Looks like you are having a kernel memory issue.
You might have event 2019 or 2020 in the system log.
I would suggest removing PowerChute or updating it to the latest version.
If you have /3gb in the boot.ini that could be contributing.
Additionally I would make sure you are running Service Pack 2 so that you have a recent VSS hotfix to ensure VSS isn't hogging all of your kernel memory.
Make sure your antivirus engine is completely up to date (not just the definitions).
Lastly, make sure you are not sharing any network printers with the "HP Tcp/ip" port type per the following KB:
http://support.microsoft.c