Home page Home page Home page Home page
Pixel Header R1 C1 Pixel
Pixel Header R2 C1 Pixel
Pixel Header R3 C1 Pixel
By Sprezz | Friday, 24 October 2014 12:03 | 0 Comments
We recently undertook a consultancy exercise on a client's site, where, to cut a long story short, the system started failing with C0000005 exception errors. This was a new development as the system had been stable for some time beforehand so we were at a loss to explain why.

Every other time we'd encountered this error it had been shown to be DEP related so we confidently asserted that this must be the case now. We suggested disabling DEP for OI and rebooting the server. This suggestion was not met with universal acclaim as this was a UDH site and the client wanted 100% up time. Reluctantly a window was scheduled to log everyone out of the system and the modifications were made and the server was cycled...

And the system kept failing with C0000005 exception errors.

At our wit's end we again resorted to installing an oeprofile.log to see what was going on at the time of the crash.
Now a quick caveat - the site was not at 9.4 so the SQL Bond was not as robust as it is now. Examining the log showed that a program used with the bond had become recursive. When this happens the program just keeps getting loaded onto the stack along with the creation of new variable pools until something breaks. 

In this case it was Windows GPFing the engine with C0000005 exception errors.

So next time you see a crash with C0000005 exception errors, don't necessarily assume that it has to be DEP - it could be you!


Post a Comment

Subscribe to Post Comments [Atom]

<< Home

Pixel Footer R1 C1 Pixel