Deployment failed. Could not invoke ping

Hello, I'm installing a fresh Outsystems on-premise server, on Microsoft stack.

When running the Service Center Installation I get:

Service Center Installer v9.1.300.0
 
Start installing Service Center v9.1.300.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...
Failed to ping... Will continue deploy anyway...
Message 1
  [Error] Error message from node outdev (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 #p1e.#M1e.#W1e.#P1e(String espaceName, String ptaOrTenantName)
 
Initializing Service Center...
ServiceCenter initialization failed. Failed to get HttpResponse from https://127.0.0.1/ServiceCenter/DoBootstrap.aspx

In Internet Explore I get on https://outdev/ServiceCenter

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Login failed for user 'KOOPMANBDR\OUTDEV$'.

Source Error:


Line 23: 		<sessionState cookieless="false" regenerateExpiredSessionId="true" mode="Custom" customProvider="OutSystemsSessionProvider">
Line 24: 			<providers>
Line 25: 				<add name="OutSystemsSessionProvider" type="OutSystems.HubEdition.RuntimePlatform.SessionState.SqlSessionStateStore" />
Line 26: 			</providers>
Line 27: 		</sessionState>

Source File: C:\Program Files\OutSystems\Platform Server\running\ServiceCenter.1311254663\web.config    Line: 25             


What could be wrong here?
Cheers Patrice Oostermeyer

Hi Patrice,

That error is probably related to a network issue or some existing problems in the server deployment controller.
As your company has subscribed a Customer Success Program our Team can help you directly.

You'll be contacted by our team soon, so we can help you handling that issue.

Cheers!

Hi,


Please share what was the solution.

We are experiencing a similar issue:


Error message from node SERVER (127.0.0.1): Deploy...Deployment failed. Could not invoke ping. Exception: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.GetResponse()
at OutSystems.HubEdition.DeployService.PageInvokes.PageInvoker.DoRequest(String espaceName, String ptaOrTenantName).

I have also having the same issue while using my personal environment. Is there any Solution?


Hi, I'm also having this problem, but only with one application of mine in my personal area. Do you have a solution?

Hi, any solution to the above issue ? 

As I recall (this is an old issue) there was a bug in that specific Platform server version. It was fixed by a later version.

Hi,


A colleague was investigating and issue where he had upgraded some of his espaces and when he created a module and inserted a Chart, the chart was not showing (issue 1). I then started upgrading my espaces and started having the issue described above.


Is it possible to upgrade and publish my entire personal environment to the latest version, hopefully this will solve the problem.


Thanks

Emil


Development - Error Detail            



Error deploying eSpace 'Devcamp2019' (Deployment failed: Deployment failed. Could not invoke ping. Exception: The remote server returned an error: (404) Not Found.
   at System.Net.HttpWebRequest.GetResponse()
   at OutSystems.HubEdition.ServerCommon.PageInvokes.AbstractInvoker.Invoke(String hostname, String espaceName, String testAreaUser, String documentPath, Action`1 validateResponse) (Espace name: Devcamp2019, Test area name: , Is running operation: False, Unique ID: 692d6572-6dad-4cbd-873b-a0b8331a7741, Deploy to separate folder: False, Not using differential Deploy, Previous deployment information wasn't found, Virtual Directory was reused):Internal Error: Deployment failed: Deployment failed. Could not invoke ping. Exception: The remote server returned an error: (404) Not Found.
   at System.Net.HttpWebRequest.GetResponse()
   at OutSystems.HubEdition.ServerCommon.PageInvokes.AbstractInvoker.Invoke(String hostname, String espaceName, String testAreaUser, String documentPath, Action`1 validateResponse) (Espace name: Devcamp2019, Test area name: , Is running operation: False, Unique ID: 692d6572-6dad-4cbd-873b-a0b8331a7741, Deploy to separate folder: False, Not using differential Deploy, Previous deployment information wasn't found, Virtual Directory was reused)
System.InvalidOperationException: Deployment failed: Deployment failed. Could not invoke ping. Exception: The remote server returned an error: (404) Not Found.
   at System.Net.HttpWebRequest.GetResponse()
   at OutSystems.HubEdition.ServerCommon.PageInvokes.AbstractInvoker.Invoke(String hostname, String espaceName, String testAreaUser, String documentPath, Action`1 validateResponse) (Espace name: Devcamp2019, Test area name: , Is running operation: False, Unique ID: 692d6572-6dad-4cbd-873b-a0b8331a7741, Deploy to separate folder: False, Not using differential Deploy, Previous deployment information wasn't found, Virtual Directory was reused) ---> OutSystems.RuntimeCommon.HEMessageException: Deploym


Hi Emil,

Your problem doesn't seem to be related to the topic, although it still related to ping.

You can go to Service Center and create a solution with all your modules, and then you can republish that solution.

Hope this helps

Hello,

I am also having issues with the ping.

Please let me know if you have any updates.

Thanks in advance for your help.

As the error is related to invoking ping. It leads to the network issue rather solution itself.

HI All,


The issue on my side is resolved. I have no idea how it "fixed itself", but I didnt use my environment for a while and then it started working again ...


Regards

Emil

Glad, that it started working. 

It could be the DNS propagation issue, which resolved after TTL expired. Or, maybe just the system cache.

Mine is still not working... :(

I have a case opened with support from a call I made yesterday.



I had this problem. 

On my case I was installing OutSystems 10, on a Windows 2012 R2.

I forgot to add the "Web Server (IIS) Support" in the "Application Server Role Services page". Once I did this, it all started working.

By the way, the error about ping is a request to http://<yourserver>/ServiceCenter/_ping.aspx.