"Service Module has encountered a problem and needs to close"

Archive
1

I have seen other users with this problem, but have not found a solution. (The thread below remains unanswered for instance. Does Symantec not look at this board then?):


http://community.norton.com/t5/Other-Norton-Products/Error-quot-Service-Module-has-encountered-a-problem-and-needs-to/td-p/200946

 

Ghost 12 (installed a couple of years ago at least) was working perfectly until this week, when I suddenly started getting this error message at every reboot. Ghost of course now won't work. I did nothing as far as I am aware - no new installations. A system restore doesn't help.

 

After other troubleshooting failed, I decided to use some spare space on another partition to install a new copy of Windows XP (and .NET 2.0) and install a new copy of Ghost 12.0. To my amazement, even in this clean XP setup I get the same error message at boot.

 

So what can be the issue here? Is the software preprogrammed to 'give up the ghost' after two years?! Suggestions welcome. Thanks,

 

Martin

2

Indeed, my initial conclusion, but I don't see that the 'Service Module' is hardware reliant. In any case, the programme worked fine for two years, and nothing has changed; all my other programmes continue to work fine too.

 

Odd, no?

 

Martin

3

I agree that it is very odd but given the set of circumstances that you have conveyed then hardware would seem to be the only realistic possibility even though this would appear to be an odd conclusion.

 

Have you checked through your Windows logs to see if there are any clues in there?

4

Nothing useful I can see. I have uninstalled Ghost so I don't get the error messages.. very annoying!!

 

Martin

5

I have seen other users with this problem, but have not found a solution. (The thread below remains unanswered for instance. Does Symantec not look at this board then?):


http://community.norton.com/t5/Other-Norton-Products/Error-quot-Service-Module-has-encountered-a-problem-and-needs-to/td-p/200946

 

Ghost 12 (installed a couple of years ago at least) was working perfectly until this week, when I suddenly started getting this error message at every reboot. Ghost of course now won't work. I did nothing as far as I am aware - no new installations. A system restore doesn't help.

 

After other troubleshooting failed, I decided to use some spare space on another partition to install a new copy of Windows XP (and .NET 2.0) and install a new copy of Ghost 12.0. To my amazement, even in this clean XP setup I get the same error message at boot.

 

So what can be the issue here? Is the software preprogrammed to 'give up the ghost' after two years?! Suggestions welcome. Thanks,

 

Martin