MIVR Log indicates Prompt File Failure

Answered Question
Aug 6th, 2009
User Badges:

Anyone seen errors in the MIVR log indicating a prompt file failure but yet the prompts are playing fine?


UCCX 7.01_SR3



6819: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-PROMPT_FILE_SUPPORT_FAILURE:Prompt file support failure: Exception=java.lang.IllegalArgumentException: invalid directory: \\SC\

486820: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION:java.lang.IllegalArgumentException: invalid directory: \\SC\

486821: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.file.File.<init>(File.java:885)

486822: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.file.File.<init>(File.java:724)

486823: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.prompt.impl.PromptManagerImpl.findPrompt(PromptManagerImpl.java:1145)

486824: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.prompt.impl.PromptManagerImpl.resolve0(PromptManagerImpl.java:2121)

486825: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.prompt.impl.PromptManagerImpl.resolve(PromptManagerImpl.java:2463)

486826: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.prompt.NamePrompt.appendTo(NamePrompt.java:438)

486827: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wf.cmt.dialogs.CMTDialogImpl.appendPrompt(CMTDialogImpl.java:165)

486828: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wf.cmt.dialogs.CMTPlayPromptDialogImpl.run(CMTPlayPromptDialogImpl.java:129)

486829: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.app.impl.ApplicationManagerImpl$TaskImpl$ActionImpl.run(ApplicationManagerImpl.java:7713)

486830: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.app.impl.ApplicationManagerImpl$TaskImpl.doInterruptible(ApplicationManagerImpl.java:7516)

486831: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wf.dialog.DialogObjectImpl.invoke(DialogObjectImpl.java:632)

486832: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wf.cmt.dialogs.CMTPlayPromptDialogImpl.invoke(CMTPlayPromptDialogImpl.java:77)

486833: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wf.steps.ivr.OutputStep.myExecute(OutputStep.java:247)

486834: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wf.steps.ivr.OutputStep.execute(OutputStep.java:132)

486835: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wfframework.obj.WFBeanStep.executeImpl(WFBeanStep.java:141)

486836: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wfframework.obj.WFStep.execute(WFStep.java:174)

486837: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wfframework.obj.WFWorkflowTask.executeStep(WFWorkflowTask.java:494)

486838: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wfframework.engine.core.WFEngineWorkflowTask.executeStep(WFEngineWorkflowTask.java:122)

486839: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.app.impl.WFWorkflowAppDebugTaskWrapper.executeStep(WFWorkflowAppDebugTaskWrapper.java:382)

486840: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wfframework.obj.WFWorkflowTask.execute(WFWorkflowTask.java:360)

486841: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wfframework.engine.core.WFEngineWorkflowTask.execute(WFEngineWorkflowTask.java:77)

486842: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.app.impl.WFWorkflowAppDebugTaskWrapper.execute(WFWorkflowAppDebugTaskWrapper.java:702)

486843: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wfframework.engine.core.TaskManager.runTaskNormally(TaskManager.java:416)

486844: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wfframework.engine.core.TaskManager.runTask(TaskManager.java:371)

486845: Aug 06 09:50:40.314 EDT %MIVR-PROMPT_MGR-3-EXCEPTION: at com.cisco.wfframework.engine.core.TaskManager$RunnableTask.run(TaskManager.java:589)


Correct Answer by Jonathan Schulenberg about 7 years 10 months ago

Sure; this is happening because the path specified is invalid:

Exception=java.lang.IllegalArgumentException: invalid directory: \\SC\


If the engine fails to play a prompt in the defined directory, it will automatically fall back the system default language directory. This is typically English depending where you are located (defined in System Parameters).

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Jonathan Schulenberg Thu, 08/06/2009 - 09:01
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 IP Telephony

Sure; this is happening because the path specified is invalid:

Exception=java.lang.IllegalArgumentException: invalid directory: \\SC\


If the engine fails to play a prompt in the defined directory, it will automatically fall back the system default language directory. This is typically English depending where you are located (defined in System Parameters).

Actions

This Discussion