Hello, 


For a troubled (cloned) development server, an on-premise reinstall was needed of an Outsystems 9 platform version.


The original pre-clone is still working smoothly with everything Outsystems installed and working.

Every part that was to do with Outsystems on the cloned machine was uninstalled cleanly.

Windows Server 2012 RD2 configuration settings were left in place due to it being a cloned virtual machine, to ease configuration.

The original install and configuration was not done by me, and the original installer could not give me more than the parameters for the configuration tool.


Checklist for pre-install run through 100% and all was in order for installation.

Platform server installed without any issue, and the configuration tool ran smoothly also.

Database connection successfully tested, etcetera.

On installation of Service Center afterward, i received the following error as below.

In another thread the suggestion was to check the ISS bindings, to make sure a binding to 127.0.0.1 was accepted - this was configured properly in ISS same as it is for the original machine..


https://SERVER/ServiceCenter is not accessible.


Is there something else to try to re-try this installation? 

Could this be due to the machine being cloned, can there be a later configuration that prevents the install despite the pre-install checklist being completed fully?

Any other ideas how we can tackle this, barring a full re-install of windows?


Thanks in advance,


Carina


Error message:

Service Center Installer v9.1.605.0


Start installing Service Center v9.1.605.0...

This operation may take a few minutes to complete...


Publishing Extension(s)...

Publishing Extension 'OMLProcessor'...

Publishing Extension 'IntegrationStudio'...

Reading ServiceCenter.oml oml file information...

Adding ServiceCenter eSpace to database...

Compiling ServiceCenter eSpace...

Preparing ServiceCenter eSpace deployment...

Deploying ServiceCenter eSpace...

Creating ServiceCenter default tenant...

Message 1

  [Error] Error message from node SERVER (127.0.0.1): Deployment failed

Deployment failed. Could not invoke ping. Exception: The underlying connection was closed: An unexpected error occurred on a send.

   at System.Net.HttpWebRequest.GetResponse()

   at #k3e.#H3e.#R3e.#K3e(String espaceName, String ptaOrTenantName)


Message 2

  [Error] Error message from node SERVER (127.0.0.1): Deployment failed

Deployment failed. Could not invoke ping. Exception: The underlying connection was closed: An unexpected error occurred on a send.

   at System.Net.HttpWebRequest.GetResponse()

   at #k3e.#H3e.#R3e.#K3e(String espaceName, String ptaOrTenantName)

Hi Carina,

  1. You mean the IIS binding right? Can you access https://SERVER/ instead of https://SERVER/ServiceCenter ? Does it show the default IIS landing page?
  2. Check if 127.0.0.1 is accepted by IIS
  3. Which version of IIS are you using?
  4. Atleast with OutSystems 11 there are few post-installation steps. Not sure with O9. Check if it is there.
  5. Are the communication ports reachable?

Regards,

Swatantra


Swatantra Kumar wrote:

Hi Carina,

  1. You mean the IIS binding right? Can you access https://SERVER/ instead of https://SERVER/ServiceCenter ? Does it show the default IIS landing page?
  2. Check if 127.0.0.1 is accepted by IIS
  3. Which version of IIS are you using?
  4. Atleast with OutSystems 11 there are few post-installation steps. Not sure with O9. Check if it is there.
  5. Are the communication ports reachable?

Regards,

Swatantra


Good morning Swatantra,

1. Yes, i mean the ISS binding. http://SERVER/ is accessable and show the ISS landing page. https is not accessible.

2. 127.0.0.1 is linked to localhost inside ISS and in the browser http://127.0.0.1/ shows the same ISS landing page as http://SERVER/.

3. Internet Information Services Version 8.5.9600.16384

4. There are post-installation steps for 9.1 also. These are configured as needed by the guide except for anything to do with service center such as licenses, system components and lifetime, because service center cannot be accessed. 

The ISS post-installation checkpoints to do with service center and lifetime are also not relevant without them installed, but i did try configuring them and then re-installing service center. Same error as a result.

5. ports 80 for http and 443 for https are open in the firewall. As I can see all other ports are configured for inbound/outbound similar to the original server also. database does not have a port configured inside outsystems config tool on either the original or the clone box, as is on the same machine as the platform server. 


Regards,


Carina


Hi Carina,

Any log entry in MS Deploy IIS Log [HEAD/POST]?

It's worth checking IIS manager and Web Deploy settings

maybe this is the issue https://support.microsoft.com/en-us/help/3206898/enabling-iis-manager-and-web-deploy-after-disabling-ssl3-and-tls-1-0

From further testing we know that it was connected twofold to the ISS instances, and to the write-rights on the machine associated with the users involved.

Resetting all the ISS applications to the default (removing all applications and application pools created in previous installation attempts) solved the first issue.

Assigning the correct write-rights to the folders used for ISS for the user(s) involved with the database as well as the user executing the installer fixed the second issue.

To make sure the whole process was as tidy as we could make it, a clean re-install of SQL server was done also.

This particular issue has now been solved. Thank you for thinking with me.

Glad it worked. And thanks for providing explanation for future readers.