Voice Notification Module Faulted in Ignition 7.9.0 Win7 x64

Hello again.

I’ve purchased myself an Atcom IP02 SIP to analog module and I’m attempting to get the voice notification working with it.

In preparation to do so, I have updated the Voice Notification module to the latest and greatest(3.8.2-rc1 (b2016022218)) version, and installed the corresponding Salli profile V7.8. Java version on the gateway is Java 8 v101.

My issue is that the module is reporting it’s faulted. The output from the status page is here:

[code]java.lang.Exception: Exception while starting up module “com.inductiveautomation.phone-notification”.
at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl$LoadedModule.startup(ModuleManagerImpl.java:2116)
at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl.startupModule(ModuleManagerImpl.java:1016)
at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl$6.call(ModuleManagerImpl.java:752)
at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl.executeModuleOperation(ModuleManagerImpl.java:799)
at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl.restartModuleInternal(ModuleManagerImpl.java:736)
at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl.restartModule(ModuleManagerImpl.java:728)
at com.inductiveautomation.ignition.gateway.web.pages.config.ModulePage$RestartAction.execute(ModulePage.java:553)
at com.inductiveautomation.ignition.gateway.web.components.ConfirmationPanel$1.onClick(ConfirmationPanel.java:49)
at org.apache.wicket.markup.html.link.Link.onLinkClicked(Link.java:189)
at sun.reflect.GeneratedMethodAccessor202.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
at org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:216)
at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:240)
at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:226)
at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:814)
at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:253)
at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:210)
at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:281)
at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:188)
at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:245)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1160)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1092)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.HandlerList.handle(HandlerList.java:52)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.server.Server.handle(Server.java:518)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:308)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:244)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceAndRun(ExecuteProduceConsume.java:246)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:156)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:654)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:572)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: Error initializing tts engine. This engine will not be available for use.
at com.inductiveautomation.services.tts.ivona.IvonaSystem.startup(IvonaSystem.java:194)
at com.inductiveautomation.alarming.notification.phone.PhoneNotificationModuleHook.startup(PhoneNotificationModuleHook.java:66)
at com.inductiveautomation.ignition.gateway.modules.ModuleManagerImpl$LoadedModule.startup(ModuleManagerImpl.java:2110)
… 45 more
Caused by: java.io.FileNotFoundException: temp\tts_engine.dll (The process cannot access the file because it is being used by another process)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(Unknown Source)
at java.io.FileOutputStream.(Unknown Source)
at java.io.FileOutputStream.(Unknown Source)
at com.inductiveautomation.services.tts.ivona.IvonaSystem.copyFile(IvonaSystem.java:172)
at com.inductiveautomation.services.tts.ivona.IvonaSystem.setupNativeFiles(IvonaSystem.java:93)
at com.inductiveautomation.services.tts.ivona.IvonaSystem.startup(IvonaSystem.java:191)
… 47 more

7.9.0 (b2016101208)
Oracle Corporation 1.8.0_101[/code]

Any ideas on what is causing this? It appears something is attempting to use some files belonging to the module so it cannot initialize properly? Here’s what I’ve tried so far:

  • Restarting the Module
  • Deleting the module completely and reinstalling
  • Disabling the voice alarm notification profile
  • Removing the only user account I had set up with a phone number
  • Removing any alarm pipelines using the voice alarm profile

After this I tried reinstalling the module with the same results. :scratch:

Any suggestions are appreciated.

Did you try restarting the gateway after installing the new module (not that you should have to, just asking).

I have not yet.

I will have to wait for Saturday to do so, however I can make arrangements and hopefully get a window in which I can knock things down to restart and report back.

Kevin,

I got a chance to swing in a touch early and restart this morning.

That seems to have done it. It’s the first time we’ve had to restart the gateway after installing a new module but we’re glad it’s cleared it up.

The help is much appreciated.