Author Topic: 503 error and Prolaborate pool stopping before getting machine ID  (Read 6906 times)

Tjerk

  • EA User
  • **
  • Posts: 231
  • Karma: +1/-0
    • View Profile
I've installed Pro Cloud Server and got WebEA working.
Now I've bought a license for Prolaborate, but can't get this one properly installed.

I used https://prolaborate.sparxsystems.com/resources/documentation/installation-guide for the installation steps.

I run into a HTTP 503 error when trying to install the license (never have seen any Prolaborate page up and running).
I've checked and performed the fixes the following tips from this forum:

I see the error "The Module DLL C:\Program Files (x86)\Sparx Systems\Cloud Services\ISAPI\SSCSIISHttpLink.dll failed to load.  The data is the error." in the Windows Event log. Tried to find more information on this, but failed to yet find anything then links above.

The server is running Windows server 2016 standard. Prolaborate is version 3.2.4.2. Pro Cloud Server is version 4.0.35.9.

The content of the most recent Prolaborate\Debug file is:
10-01-2020 09:42:48.864: [COMP: MAIN] [MESSAGE: Starting]
10-01-2020 09:42:48.864: [COMP: MAIN] [MESSAGE: Running as --removed--\SYSTEM]
10-01-2020 09:42:48.864: [COMP: MAIN] [MESSAGE: Configuration Directory exists]
10-01-2020 09:42:48.864: [COMP: MAIN] [MESSAGE: Debug Directory exists]
10-01-2020 09:42:48.864: [COMP: MAIN] [MESSAGE: License File is missing]
10-01-2020 09:42:48.879: [COMP: MAIN] [MESSAGE: Config File exists]
10-01-2020 09:42:48.879: [COMP: MAIN] [MESSAGE: Debug Directory Writable: True]
10-01-2020 09:42:48.879: [COMP: MAIN] [MESSAGE: Checking for running instance of Prolaborate]
10-01-2020 09:42:48.879: [COMP: MAIN] [MESSAGE: Checking for running instances of Worker]
10-01-2020 09:42:48.895: [COMP: MAIN] [MESSAGE: Checking for running instance of Socket Server]
10-01-2020 09:42:48.895: [COMP: MAIN] [MESSAGE: Checking for running instance of Socket Client]
10-01-2020 09:42:48.895: [COMP: MAIN] [MESSAGE: EAOptions Registry Template not found]
10-01-2020 09:42:48.911: [COMP: MAIN] [MESSAGE: Checking for running instance of Socket Server]
10-01-2020 09:42:48.911: [COMP: MAIN] [MESSAGE: Trying to start Notification server]
10-01-2020 09:42:48.911: [COMP: MAIN] [MESSAGE: Starting APIS]
10-01-2020 09:42:49.020: [COMP: MAIN] [MESSAGE: APIS Started]
10-01-2020 09:42:49.239: [COMP: MAIN] [MESSAGE: Notification server started]
10-01-2020 09:42:49.286: [COMP: MAIN] [MESSAGE: Checking for running instances of Worker]
10-01-2020 09:42:49.499: [COMP: MAIN] [MESSAGE: Syncing with latest repository list]
10-01-2020 09:42:49.552: [COMP: MAIN] [MESSAGE: Push Notification Started]
« Last Edit: January 10, 2020, 09:46:45 pm by Tjerk »

Prolaborate Support

  • Prolab Moderator
  • EA User
  • *
  • Posts: 241
  • Karma: +15/-0
    • View Profile
    • Visit us
Re: 503 error and Prolaborate pool stopping before getting machine ID
« Reply #1 on: January 16, 2020, 11:01:07 pm »
Can you please check whether Prolaborate's Application pool is configured only for the Prolaborate site in IIS Manager. If no, update and check if you are able to open the site.

If the above-said configuration is fine, try stopping the PCS site in IIS and open the Prolaborate site.

If the Prolaborate site is still not working, please reinstall the window features as per this link. Restart the application server and see if the site opens up fine.

If this issue still exists, please email these details to prolaborate@sparxsystems.com:
1. Screenshot of the issue
2. Name of the browser you are using to visit Prolaborate site
3. Browser console messages when you visit Prolaborate site

Note: This error message is related to Pro Cloud Server and not Prolaborate.
"The Module DLL C:\Program Files (x86)\Sparx Systems\Cloud Services\ISAPI\SSCSIISHttpLink.dll failed to load.  The data is the error."

Tjerk

  • EA User
  • **
  • Posts: 231
  • Karma: +1/-0
    • View Profile
Re: 503 error and Prolaborate pool stopping before getting machine ID
« Reply #2 on: January 18, 2020, 12:54:01 am »
I confirm that the Prolaborate app pool is only configured for 1 application.
After stopping the WebEA website and WebEA app pool and started the Prolaborate website and app pool in IIS again.
I load the Prolaborate site (HTTP) again (in Chrome 79.0.3945.130 (Official Build) (64-bit)). Console shows "GET http://prolaborate.arsinfo.nl/favicon.ico 503 (Service Unavailable)" also shown in the browser and the network request/responses in the developer tools. The Prolaborate app pool is stopped again (happens while loading the site. If site is not loaded the app pool stays running).

Re-verified the features provided in the link (have all but the default IIS site, that I removed earlier when installing WebEA).
Getting the same 503 in the mentioned Chrome browser and in IE.
Same 503 as mentioned above in Chrome. IE console shows (in this test I've removed any bindings and accessed the site localhost via HTTP)
HTML1300: Navigation occurred.
localhost
HTML1420: Unexpected quote after "PUBLIC" or "SYSTEM" keyword. Expected whitespace.
localhost (1,50)

If I start WebEA, that still works. So some parts of PCS still seem to be operational.



Prolaborate Support

  • Prolab Moderator
  • EA User
  • *
  • Posts: 241
  • Karma: +15/-0
    • View Profile
    • Visit us
Re: 503 error and Prolaborate pool stopping before getting machine ID
« Reply #3 on: January 20, 2020, 11:24:09 pm »
We have seen this error only in the following scenarios.

1. Anyone of the points in this
link is not done correctly. So, can you please check once again? If you are sure, let's move to the next point.

2. Although everything looked fine, there was an unknown problem with Windows features installation. Usually reinstalling the features fixed the issue. link. Restart the application server and see if the site opens up fine.

If this issue still exists, please share the following screenshots to prolaborate@sparxsystems.com:
1. Screenshot of the issue
2. Prolaborate Application pool advanced settings page.
3. Prolaborate site advanced settings page.

Tjerk

  • EA User
  • **
  • Posts: 231
  • Karma: +1/-0
    • View Profile
Re: 503 error and Prolaborate pool stopping before getting machine ID
« Reply #4 on: January 23, 2020, 02:37:30 am »
Okay, problem solved.

Have removed all roles and features and reinstalled these.
Removed the Prolaborate IIS site and added it again.
Set the properties for the pool and IIS site again and now it works.
So not sure what was the problem, but possibly an older WebEA installation bugged the IIS configuration?
Now activating the product.

Prolaborate Support

  • Prolab Moderator
  • EA User
  • *
  • Posts: 241
  • Karma: +15/-0
    • View Profile
    • Visit us
Re: 503 error and Prolaborate pool stopping before getting machine ID
« Reply #5 on: January 23, 2020, 10:33:27 pm »
Glad to know the issue got resolved! Thank you for the update.

As far as we know, it should be some bug in the installation of features. As said earlier, reinstalling Windows features mostly fixes this error.