PowerServer Web APIs may fail to start, due to the following reasons:
-
Port number is being used by another program. For solutions, refer to this section.
-
License is invalid or expired; or the Appeon license server cannot be accessed. For solutions, refer to License errors.
-
(IIS) There is a bitness mismatch between IIS and PowerServer Web APIs, for example, the IIS worker process is 32-bit, while Web APIs is 64-bit. For solutions, refer to "HTTP Error 500.32 - Failed to load .NET Core host".
-
(IIS) The application pool used by the Web APIs is also used by another application. For solutions, refer to "Internal Server Error (HTTP status code: 500)".
-
(IIS) .NET Core Hosting Bundle is not installed on the IIS server. For solutions, refer to "HTTP Error 500.19 - Internal Server Error".
-
(IIS) ASP.NET Core Runtime is not installed on the IIS server. ASP.NET Core Runtime is required if the Web APIs is deployed as a Framework-Dependent package. You can download and install ASP.NET Core Runtime from https://dotnet.microsoft.com/en-us/download/dotnet.
Alternatively, you can also check the following areas for more information about the errors:
-
Check the PowerServer logs (\Logging\logs\powerserver.log by default under the API folder). For more, refer to PowerServer logs (make sure you have permissions to write into the folder).
-
Check the system Event Viewer on the server machine.
-
(IIS) Check the IIS log file (usually located in %SystemDrive%\inetpub\logs\LogFiles).
