Ivr Service Won't Start

[Guest patrickbassett]

We are running a VoiceGuide version 7 IVR system. We had made a routine

change this afternoon to the config.xml file, and stopped and attempted to

restart the Voice Guide IVR service. However, it came back with an

unhandled exception. We then restarted the server. No difference. We then

started the Dialogic board service, and manually started the VoiceGuide

service. There was no change. The service event errors were:

 

 

NET 2.0 RUNTIME ERROR

=====================

Service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object.

at . .OnStart(String[] args)

at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

 

 

Voice Guide IVR

===============

service cannot be started. System.NullReferenceException: Object reference not set to an instance of an object.

at . .OnStart(String[] args)

at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

1007_ktTel.zip

Traces.zip

[SupportTeam]

The traces supplied only show the service being stopped (on Oct 7, at 16:25). The service shutdown looks fine.

 

There are not traces supplied showing any system startup. If no traces are even created when the service is started then this means that VoiceGuide program has not even been started.

 

VoiceGuide starts creating logs immediately at beginning of startup and a lot of logging is done before VoiceGuide even reads the Config.xml file, so if not logs at all are created then it looks like this is not a Config.xml related issue.

 

This type of error could be caused if one of the .DLLs or Assemblies that VoiceGuide uses is missing, so at this stage we'd probably recommend trying to re-install VoiceGuide as a start (or restoring a previous backup of the system if available).

 

[Guest patrickbassett]

After working a while longer, we uninstalled Voice Guide and upgraded to the latest version, 7.07. That seems to have taken care of the problem.

 

Thank you for your support.