Call Me, Notify Me not working after reboot

[rejackson]

MM 5.2 was acting slow, pauses in the user interface and messge playback. Restarted last night and that problem went away. But now call me and notify me are not working. Service gv_cmserver was manual so I tried starting it, no good. tried another reboot of the MAS with the service set to auto, no good. Tried to stop the service and it will not stop. Too late for a reboot now (active users). Only thing I see strange is info and error events about the spirit process "Inventory QueueManager Task Run Failed" and "IPS strategy storing delivery label becuase failed to send message. The following is the error message:{0}

Is there a service that needs to be stopped to allow the cmserver to stop?

I have seen posts about SPIRIT being a problem with the MSS not seeing the MAS backup but dont know how to check that and dont know if it would be related to the notify problem.

 

[KenMeans]

How many MAS's do you have and what MAS is running the CallMe service ? if you have more than one MAS you can look in the VMSC to find it. it sounds like it is running but not on the MAS if it was set to manual.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[texeric]

Call Me and MWI service are dependant on the Mailbox Monitor service. Like Ken said, check to see where the service is designated to run (in the VMSC) and see if it is running on that MAS. Those 3 services are designed to run (and function) on only 1 MAS within the VMD (Voice Mail Domain).

 

[rejackson]

Hi Ken,

One MAS. Before I rebooted it the the first time I ran an exe that was on the desktop called StopAllMMServices.exe. Under MM3 we had scripts to stop and start the services in the right order but in 5.2 it has these exe files so I cannot look at them and see the order that the services should stop/start. That might give me a clue to what is keeping the service from stopping now. When I ran the exe it hung trying to stop Call Me but before that it said it was changing it to manual. I closed that window and rebooted. After the boot and it wasnt working I noticed the manual setting and tried starting the service but it didnt help. So I set it to auto and rebooted again. Still no luck. I tried stopping the service and it wont stop. It is day time now so I cannot reboot again just for the notifications but that would be the solution for the service hung in the "stopping" state. But the notifications were not working before that.

Do you know what the events about SPIRIT mean? Until the first reboot in this scenario that last time there were logs like that was 3 months ago.

Thanks,
Richard

 

[KenMeans]

Just FYI if you are going to reboot you don't need to stop the services as they will stop them self and it will not affect anything adversely. if you have just one MAS then you need to make sure that all of the MM services are running as it sounds to me from you first post that some of the other services have not been re enabled or in the running state.

If you ran the StopAllMMServices.exe did you run the script file to re enable them ?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)