Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have a windows service which throws a memory related error and then restarts. Besides trying to fix the error, which is something I'm working on, I need to know how to disable this annoying message:

"The instruction at 0xmmmmmmmm referenced memory at 0xnnnnnnnn. The memory could not be written."

The problem is that the service won't restart until someone clicks the "Accept" button on the server.

In this case, service restarts are tolerable, what is not tolerable is having the service down until someone clicks the button. This message appears on the login screen (user is not logged in).

I need to ensure that the service will restart on error without any human interaction with the server.

share|improve this question
    
I don't think that's normal behaviour. It may be the runtime library doing it; do you know what language the service was written in? –  Harry Johnston Jul 25 '12 at 21:18
    
It's an apache service running php. –  Jbm Jul 26 '12 at 2:53

1 Answer 1

The application needs to handle all windows errors for services and the service should stop. If a service properly throws an error, error recovery can kick in and restart the service (or perform some task to resolve the issue)

share|improve this answer
    
Thanks for the info. So this means that Windows Server expects someone to be next to the machine and click "ok". Even if the service is completely at fault I would expect more of server OS. –  Jbm Jul 25 '12 at 18:39
1  
So this means that Windows Server expects someone to be next to the machine and click "ok" -- No. It it means that the application/service was written by a chimpanzee who can't write proper error handling code. –  RobM Jul 25 '12 at 18:48
    
@jbm, if the server was at fault, it would generate an appcrash, ( and likely a bluescreen)the error you have is specific to code –  Jim B Jul 25 '12 at 22:49
    
I'm not saying that the OS is at fault at code level, but at design level. What purpose serves a sign with an "Ok" button that no one is ever going to see? Wouldn't it be better if I as an admin could choose what to do, like just logging to disk and restarting the service? That would actually be useful. –  Jbm Jul 25 '12 at 23:14
    
@Jbm Right, but it's the coder who wrote the application/service who decided to pop up a dialogue requiring user interaction instead of having the service log an error and restart (or fail or try to continue). Windows is just doing what the code tells it to do. What application/service is this? Maybe if you share that, someone who's used this app/service will be able to share a solution. –  HopelessN00b Jul 26 '12 at 2:35

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.