I have configured nHaystack on a Niagara Station. I initialized the nHaystack and rebuilt my cache after adding my site, equip and point tags. When I try to connect to the URI via http://<my ip address>/haystack, I get the following error:

500: Internal Server Error

workbench:DefaultWbWebProfile

I have seen this on other stations I have configured the exact same way, and after I initialized haystack I was able to access the page without issue. I have attempted to initialize haystack here to no avail. Anybody have any thoughts on what is causing this?

Can you post the server-side stack trace that goes along with this error?

Been awhile since I had this issue. But it just resurfaced. Here is the Stack Trace:

ERROR [16:25:06 22-Feb-16 EST][web] Internal Server Error javax.baja.sys.TypeNotFoundException: workbench:BasicWbWebProfile

at com.tridium.sys.module.NModule.getType(NModule.java)
at javax.baja.util.BTypeSpec.getResolvedType(BTypeSpec.java)
at javax.baja.util.BTypeSpec.getInstance(BTypeSpec.java)
at javax.baja.util.BTypeConfig.make(BTypeConfig.java)
at javax.baja.web.BDefaultClientEnvironment.doGetWebEnv(BDefaultClientEnvironment.java)
at javax.baja.web.BClientEnvironment.getWebEnv(BClientEnvironment.java)
at javax.baja.web.BClientEnvironments.getWebEnv(BClientEnvironments.java)
at javax.baja.web.BWebService.getWebEnv(BWebService.java)
at com.tridium.web.WebEnv.make(WebEnv.java)
at javax.baja.web.WebOp.initWebEnv(WebOp.java)
at com.tridium.web.WebProcess.toWebEnv(WebProcess.java)
at com.tridium.web.WebProcess.service(WebProcess.java)
at com.tridium.web.SysServlet.service(SysServlet.java)
at javax.servlet.http.HttpServlet.service(HttpServlet.java)
at com.tridium.httpd.ServiceThread.handleRequest(ServiceThread.java)
at com.tridium.httpd.ServiceThread.run(ServiceThread.java)

Hi David,

I don't see any mention of the nhaystack module in this stack trace. Is there any other information you can share on the station.

Does this error occur consistently, or is it intermittent?

I assume it's not possible, but if you remove the NHaystackService from the station does it remove the exception?

Is there any noticeable side effect from the error?

Regards, Richard

This is likely an issue with the initial commissioning of the controller. This error usually occurs when the controller is commissioned for runtime only (rt) and not runtime+ui. If ui is not included during commissioning, Workbench will strip UI classes from the modules as they are transferred to the controller.

If this is the issue, you will need to recommision the controller.

Thanks Shawn!

@David: can you check if this is the issue and let us know if it solves the problem.

Cheers,

Richard