One of the causes of the Sie Update Db not being able to create the objects for the Point and PPCL Editors is if the station cannot bind to the webserver.

To determine if this is happening, navigate to Platform > Application Director and search for an error message similar to the following:

INFO [08:32:30 01-Aug-16 CDT][javax.baja.web.BWebServer] Scheduling restart in 5 seconds.
INFO [08:32:30 01-Aug-16 CDT][fox] FOX server started on port [1911]
INFO [08:32:30 01-Aug-16 CDT][fox] FOXS server started on port [4911]
INFO [08:32:30 01-Aug-16 CDT][sys] Niagara Runtime Environment: 4.1.27.20
INFO [08:32:30 01-Aug-16 CDT][sys] *** Station Started (1295ms) [6948ms total] ***
niagara>INFO [08:32:31 01-Aug-16 CDT][history.db] Starting async warmup of history config index...
INFO [08:32:31 01-Aug-16 CDT][history.db] Async history config index warmup completed in 16 ms.
INFO [08:32:35 01-Aug-16 CDT][web] Jetty stopped.
SEVERE [08:32:35 01-Aug-16 CDT][javax.baja.web.BWebServer] failed: java.net.BindException: Failed to bind to https port [443], http port [80], or both
java.net.BindException: Failed to bind to https port [443], http port [80], or both
 at com.tridium.jetty.BJettyWebServer.doStartWebServer(BJettyWebServer.java:618)
 at javax.baja.web.BWebServer.startWebServer(BWebServer.java:228)
 at javax.baja.web.BWebServer.doRestart(BWebServer.java:291)
 at auto.com_tridium_jetty_BJettyWebServer.invoke(AutoGenerated)
 at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1871)
 at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:61)
 at javax.baja.sys.BComponent.doInvoke(BComponent.java:1206)
 at javax.baja.util.Invocation.run(Invocation.java:46)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at java.lang.Thread.run(Thread.java:745)

To address this, open the Station and navigate to Station > Config > Services > WebService and set the Http Port and Https port to different port numbers. For example, try setting the Http Port to 81 and the Https port to 500.

If you need to troubleshoot further to determine if a specific port is in use, and which program is using it, use the following procedure:

  1. Run a command prompt as an Administrator.
  1. Create and select a location to store a text file. For example, C:\N4_TS
  1. Type the following commands and press Enter:
  1. Netstat –a –n –p tcp –b > C:\N4_TS\tcpport01.txt
  1. Netstat –ano > C:\N4_TS\tcpport_PID02.txt

Both text files will give you list of ports used for example in the line from tcpport01.txt

TCP    0.0.0.0:443            0.0.0.0:0              LISTENING

[vmware-hostd.exe]

This indicates that port 443 is taken by vmware-host.exe.

The other file lists file by PID (process ID), which is useful if the port shows “Cannot obtain ownership information” rather than the name of an executable.

You can determine which process owns the process by looking in Task Manager. To view PIDs, right click the Name column and selecting PID.

If you need to use a specific port that has a conflict, you will need to either stop the program that is using the port or reconfigure that program to use a different port.