PI Web API 2014 R2 Service will not start

Discussion created by VCampus-METCO on Nov 28, 2014
Latest reply on Aug 31, 2015 by dng

I am upgrading Coresight 2013 to 2014. The coresight site is on a server shared with many other sites. Coresight is installed to use port 8080


At the point at which PIWebAPI is installed, I run under the same account as the coresight app pool identity, and said to create a self-signed certificate.


The service then tries to start, but fails.


The system application log shows an error


Event 15005, HttpEvent


Unable to bind to underlying transport for [::]:443. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.


This causes the coresight install to fail.


There may be another application listening on the same machine on port 443. Can this be changed to allow two applications to work together?