Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
when the red log appear,the qvs.exe had been down,any one help me ,thank u very much!
type ,verson
RLS64 | 8.50.6299.0409.10 |
Server Started Timestamp SeverityID EventID Severity Message
2013-10-17 16:28:26 2013-10-17 16:30:27 1 120 Error Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type D, detected.
2013-10-17 16:28:26 2013-10-17 16:30:27 4 500 Information Debug: Done Running
2013-10-17 16:30:33 2013-10-17 16:30:33 4 504 Information WorkingSet: Set up Working Set (70%-90%, 22.393 GB-28.791 GB)
2013-10-17 16:30:33 2013-10-17 16:30:33 4 500 Information Debug: Calling StartServiceCtrlDispatcher()
2013-10-17 16:30:33 2013-10-17 16:30:33 4 500 Information Debug: Entering CNTService::ServiceMain()
2013-10-17 16:30:33 2013-10-17 16:30:33 4 500 Information Debug: CNTService::SetStatus(11445024, 2)
2013-10-17 16:30:33 2013-10-17 16:30:33 4 500 Information Debug: CNTService::SetStatus(11445024, 4)
2013-10-17 16:30:33 2013-10-17 16:30:33 4 500 Information Debug: 16 CPU cores found in 8 CPUs
2013-10-17 16:30:33 2013-10-17 16:30:34 4 301 Information Found Mount at location D:\bidata browsable
server environment
Hi,
This error "Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type D, detected."
means you have a bad QVW. You will need to figure out which one it is and fix the issues. Most of the time if you look at the log, it is the one that is open right before you see the error.
Bill
Thank you bill;
I am monitoring the server all the day
The issue of 'type d' appered more than 100 times the last day
But today it only appered 3 times (from 8:am to 16:30 pm)
The frequency reduce so suddenly but i have done nothing
thanks for your suggestion bill,i'll keep find the cause
ryan