Results 1 to 5 of 5
-
02-11-2013, 02:13 AM #1
Niagara AX issue - Connecting to local station
Hey guys,
We have recently taken over a site with two Vykon JACE 2 controllers. They are using the local station to pass Global points, however the station has fallen over.
Error log when trying to connect:
javax.baja.naming.UnresolvedException: fox:
at com.tridium.fox.sys.BFoxScheme.resolve(BFoxScheme. java:94)
at javax.baja.naming.BOrd.resolve(BOrd.java:255)
at javax.baja.naming.BOrd.resolve(BOrd.java:209)
at com.tridium.workbench.shell.BNiagaraWbShell.resolv e(BNiagaraWbShell.java:468)
at com.tridium.workbench.shell.NHyperlinkInfo.resolve (NHyperlinkInfo.java:235)
at com.tridium.workbench.shell.NHyperlinkInfo.hyperli nk(NHyperlinkInfo.java:88)
at com.tridium.workbench.shell.BNiagaraWbShell.doHype rlink(BNiagaraWbShell.java:374)
at com.tridium.workbench.shell.BNiagaraWbShell.hyperl ink(BNiagaraWbShell.java:332)
at javax.baja.workbench.nav.tree.NavTreeController.no deDoubleClicked(NavTreeController.java:74)
at javax.baja.ui.tree.TreeController.mousePressed(Tre eController.java:227)
at javax.baja.ui.tree.BTree.mousePressed(BTree.java:5 76)
at javax.baja.ui.BWidget.fireMouseEvent(BWidget.java: 1134)
at com.tridium.ui.awt.MouseManager.fire(MouseManager. java:305)
at com.tridium.ui.awt.MouseManager.fire(MouseManager. java:279)
at com.tridium.ui.awt.MouseManager.pressed(MouseManag er.java:106)
at com.tridium.ui.awt.MouseManager.process(MouseManag er.java:87)
at com.tridium.ui.awt.AwtShellManager.processMouseEve nt(AwtShellManager.java:512)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknow n Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at javax.baja.naming.BIpHost$WorkaroundSocketFactory. open(BIpHost.java:422)
at javax.baja.naming.BIpHost.openSocket(BIpHost.java: 284)
at com.tridium.fox.sys.BFoxClientConnection.connect(B FoxClientConnection.java:497)
at com.tridium.fox.sys.BFoxSession.connect(BFoxSessio n.java:247)
at com.tridium.fox.sys.BFoxScheme.resolve(BFoxScheme. java:81)
at javax.baja.naming.BOrd.resolve(BOrd.java:255)
at javax.baja.naming.BOrd.resolve(BOrd.java:209)
at com.tridium.workbench.shell.BNiagaraWbShell.resolv e(BNiagaraWbShell.java:468)
at com.tridium.workbench.shell.NHyperlinkInfo.resolve (NHyperlinkInfo.java:235)
at com.tridium.workbench.shell.NHyperlinkInfo.hyperli nk(NHyperlinkInfo.java:88)
We have searched this site and taken on some of the recommendations. We have tried to run the Daemon platform and it installed and started okay. The issue is still present.
We're under a bit of urgency as one of the Global points it passes is for the Cooling Call, so no Chiller.
Any help is much appreciated.
- Adrian
-
02-11-2013, 02:14 AM #2
Forgot to mention: Ports are not blocked.
-
02-11-2013, 07:28 AM #3
"at com.tridium.workbench.shell.BNiagaraWbShell.doHype rlink(BNiagaraWbShell.java:374)"
Looks like its in shell mode. Check the serial shell jumper.Build it and it will break. Fix it and it will work. Ignore it and will cost more. Patch it and it will get worse. Cross the bridge before the flood.
-
02-11-2013, 08:09 AM #4
I don't think it is in shell mode. I had this same problem before and never figured out what caused it. I assumed it was something network related since it cleared on it's own.
https://www.niagara-central.com/ord?...onThread/11827
Go Rangers!
-
02-11-2013, 11:04 AM #5
java.net.ConnectException: Connection refused: connect
The connection refused tells me it's likely an issue with the fox port not being open, or the incorrect port # being used.
If it were a version mismatch, you'd see "Access Denied" or if incorrect credentials, you'd see "Authentication Failed"
Lane's post looks similar, but was just a connection timeout issue.


Reply With Quote