GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- Error can be caused by a corrupt registry or a low...
Windows Server 2003
1846645
Members
1980
Online
110256
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2008 08:18 PM
12-10-2008 08:18 PM
Error can be caused by a corrupt registry or a low memory condition
We recently upgraded our SAS server using HP's SMP (Server Migration Pack); the old server had 32gig of RAM, 2 Dual Core processes, OS:Windows server 2003 SP2-Enterprise Edition and now we are running on 64gig of RAM, 4 Dual processors and same Operating System.
After our upgrade we have experienced more I/O errors along with these errors in our event log: Event Type: Warning
Event Source: Foundation Agents
Event Category: Software Version
Event ID: 3072
Date: 12/3/2008
Time: 2:32:06 PM
User: N/A
Computer: XXXXXXX
Description:
Component: Software Version Agent
Error: Could not read from the registry sub-key.
Cause: This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error.
Data:
0000: 02 00 00 00
Any suggestions, would be helpful.
After our upgrade we have experienced more I/O errors along with these errors in our event log: Event Type: Warning
Event Source: Foundation Agents
Event Category: Software Version
Event ID: 3072
Date: 12/3/2008
Time: 2:32:06 PM
User: N/A
Computer: XXXXXXX
Description:
Component: Software Version Agent
Error: Could not read from the registry sub-key.
Cause: This error can be caused by a corrupt registry or a low memory condition. Rebooting the server may correct this error.
Data:
0000: 02 00 00 00
Any suggestions, would be helpful.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2008 11:48 PM
12-11-2008 11:48 PM
Re: Error can be caused by a corrupt registry or a low memory condition
Did you follow post-migration steps? (update PSP, check for invalid drivers, re-install any network teaming)
Is it x64 version of Windows or 32-bit? The 32 bit version "by design" can get resource shortages (hardcoded nonpaged pool memory limits etc) - especially if running with /3GB switch in boot.ini
In 64-bit it should not be an issue.
Is the registry size (\windows\system32\config) unusually large? (Compare with other servers)
Finally I suppose the error can also be due to missing permissions (permissions can be set on registry subkeys). Any service accounts or domain accounts that perhaps need refreshing passwords ?
Cheers,
Rune
What are the IO errors you see?
Is it x64 version of Windows or 32-bit? The 32 bit version "by design" can get resource shortages (hardcoded nonpaged pool memory limits etc) - especially if running with /3GB switch in boot.ini
In 64-bit it should not be an issue.
Is the registry size (\windows\system32\config) unusually large? (Compare with other servers)
Finally I suppose the error can also be due to missing permissions (permissions can be set on registry subkeys). Any service accounts or domain accounts that perhaps need refreshing passwords ?
Cheers,
Rune
What are the IO errors you see?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP