Re: PAE problem question (KB834628)
From: Yuan Shao (v-yshao_at_online.microsoft.com)
Date: 03/24/04
- Next message: Brian Moran: "Re: Running profiler on busy 8-cpu Sql Server"
- Previous message: Tenaya: "Re: Import Errors from MS Access"
- In reply to: frankm: "Re: PAE problem question (KB834628)"
- Next in thread: frankm: "Re: PAE problem question (KB834628)"
- Reply: frankm: "Re: PAE problem question (KB834628)"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 24 Mar 2004 03:05:10 GMT
Hi Frankm,
I agreed with Geoff N that it seems this problem is not mostly related the
problem in KB834628. Based on my experience, 823 errors are mostly hardware
related. Specially this error 823 on bad page ID is raised when the page ID
is invalid. When the error occurred, you can try to perform the following
steps to troubleshoot.
1. Check for error in the system and application from NT even viewer
2. Run DBCC checkdb on databse
a. IF it's sql 7.0, use "-y823" to start sql server and capture the dump
when the error is raised again
b. IF it's sql 2k, user DBCC Dumptrigger('SET', 823) to enable the dump
(this will NOT require the sql to be recycled!)
When the error 823 happens, it will catch the dump on it in sql errorlog,
3. Please also contact hardware vendor to run hardware diagnostic.
If the problem is very complex and you are unable to narrow down, you can
contact our PSS with the above information to continue working with a
dedicated Support Professional.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
- Next message: Brian Moran: "Re: Running profiler on busy 8-cpu Sql Server"
- Previous message: Tenaya: "Re: Import Errors from MS Access"
- In reply to: frankm: "Re: PAE problem question (KB834628)"
- Next in thread: frankm: "Re: PAE problem question (KB834628)"
- Reply: frankm: "Re: PAE problem question (KB834628)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|