OutSystems Service Center publish failed with error code 110

OutSystems Service Center publish failed with error code 110

  
Dear all

I get the following error message while trying to install OutSystems

Any ideas why ?

Thanks

Tadhg

17.10.2007 14:25:35] IIS Admin was started
[17.10.2007 14:25:36] NET START "W3Svc"
[17.10.2007 14:25:36] The requested service has already been started.

More help is available by typing NET HELPMSG 2182.
[17.10.2007 14:25:36] World Wide Web Publishing was started
[17.10.2007 14:25:37] Checking HTTP port availability...
[17.10.2007 14:25:49] OK. Process 'System' listening on port 80.
[17.10.2007 14:25:49] Publishing OutSystems Service Center 4.1.3.15...
[17.10.2007 14:25:50] Publishing Extension(s)...
[17.10.2007 14:26:00] Reading Service Center oml file information...
[17.10.2007 14:26:02] Adding Service Center eSpace to database...
[17.10.2007 14:26:04] Compiling Service Center eSpace...
[17.10.2007 14:26:51] Preparing Service Center eSpace deployment...
[17.10.2007 14:26:59] Creating Service Center default tenant...
[17.10.2007 14:26:59] Deploying Service Center eSpace...
[17.10.2007 14:27:13] Message 1
[17.10.2007 14:27:13] Id : FailedTenantDeployment_PingAspx
[17.10.2007 14:27:13] Type : Error
[17.10.2007 14:27:13] Message : Error publishing in node WIGBCDF6751 (127.0.0.1): Tenant deployment failed
[17.10.2007 14:27:13] Submitable : True
[17.10.2007 14:27:13] Details :
[17.10.2007 14:27:13] Deployment of tenant Unable to connect to the remote server
[17.10.2007 14:27:13] at System.Net.HttpWebRequest.GetResponse()
[17.10.2007 14:27:13] at OutSystems.HubEdition.DeployService.Deploy.#Hj(String hostname, String espaceName, String ptaOrTenantName) failed. Could not invoke ping. Exception:
[17.10.2007 14:27:13] ExtraInfo :
[17.10.2007 14:27:13] CompModule : Broadcast Message
[17.10.2007 14:27:13] Message 2
[17.10.2007 14:27:13] Id : FailedTenantDeployment_PingAspx
[17.10.2007 14:27:13] Type : Error
[17.10.2007 14:27:13] Message : Error publishing in node WIGBCDF6751 (127.0.0.1): Tenant deployment failed
[17.10.2007 14:27:13] Submitable : True
[17.10.2007 14:27:13] Details :
[17.10.2007 14:27:13] Deployment of tenant Unable to connect to the remote server
[17.10.2007 14:27:13] at System.Net.HttpWebRequest.GetResponse()
[17.10.2007 14:27:13] at OutSystems.HubEdition.DeployService.Deploy.#Hj(String hostname, String espaceName, String ptaOrTenantName) failed. Could not invoke ping. Exception:
[17.10.2007 14:27:13] ExtraInfo :
[17.10.2007 14:27:13] CompModule : Broadcast Message
[17.10.2007 14:27:13] OutSystems Service Center publish failed with error code 110
[17.10.2007 14:27:13] Installation could not be completed!
[17.10.2007 14:27:13] Check 'D:\Program Files\OutSystems\Installer\Logs\ExpressInstall.log' for installation details
[17.10.2007 14:27:13] Installed components:
[17.10.2007 14:27:13] • OutSystems Integration Studio
• OutSystems Service Studio
• .NET Framework Hot Fix KB923028
• Visual C++ 2005 Runtime Libraries SP1

[17.10.2007 14:27:13] Not installed components:
[17.10.2007 14:27:13] • OutSystems Service Center
• IT Asset Manager

[17.10.2007 14:27:18] Notify Action: Id[43202B7D-E1C7-7449-A7EE-EBE8BEA8282A] Version[4.1.3.15] Action[Installation Failed] Details[Installed[OutSystems Integration Studio|OutSystems Service Studio|.NET Framework Hot Fix KB923028|Visual C++ 2005 Runtime Libraries SP1] NotInstalled[OutSystems Service Center|IT Asset Manager] Details[OutSystems Service Center publish failed with error code 110]]
[17.10.2007 14:27:20] RebootFlag was set
[17.10.2007 14:27:20] Installation Failed

Contents of the listbox:

Extract: IntegrationStudio-4.1.3.15.exe
Installing OutSystems Integration Studio 4.1.3.15...
Extract: ServiceStudio-4.1.3.15.exe
Installing OutSystems Service Studio 4.1.3.15...
Configuring Event Log Service...
.NET Framework Hot Fix KB923028 not found...
Extract: NDP20-KB923028-X86.exe
Installing .NET Framework Hot Fix KB923028...
Registering ASP.NET 2.0 in IIS...
Start installing ASP.NET (2.0.50727) without registering the scriptmap. ..............................................
Finished installing ASP.NET (2.0.50727) without registering the scriptmap.
Enabling ASP.NET 2.0 Web Service Extension...
Configuring machine.config...
Visual C++ 2005 Runtime Libraries SP1 not found...
Downloading Visual C++ 2005 Runtime Libraries SP1...
Installing Visual C++ 2005 Runtime Libraries SP1...
Stopping Web Server...
Stopping OutSystems Services...
Removing OutSystems Services...
Extract: ServiceCenter-4.1.3.15.exe
Creating OutSystems Service Center Uninstaller...
Installing OutSystems Service Center 4.1.3.15...
Cleaning Web Server Configuration...
Creating OutSystems Services...
Updating browser capabilities in machine.config...
Browser capabilities from machine.config have been replaced. The old machine.config was saved in 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.20071017012344.old'.
Machine.config was updated successfully.
Starting Database Server...
Configuring ASP.NET SQL Server Session State...
Configuring OutSystems Service Center 4.1.3.15...
Database 'outsystems_express' does not exist and will be created.
There is no SQL Server login named 'OSAdmin'.
Creating a new login with the corresponding password.
Required Admin permissions granted to user 'OSAdmin' on catalog 'outsystems_express'.
There is no SQL Server login named 'OSRuntime'.
Creating a new login with the corresponding password.
Required Runtime permissions granted to user 'OSRuntime' on catalog 'outsystems_express'.
There is no SQL Server login named 'OSLog'.
Creating a new login with the corresponding password.
Required Admin permissions granted to user 'OSLog' on catalog 'outsystems_express'.
Hub Server schema will be created in catalog. This process may take a while.
Hub Server database schema was successfully upgraded.
Starting OutSystems Services...
OK. OutSystems Log Service listening on port 12003.
OK. OutSystems Deployment Controller Service listening on port 12000.
OK. OutSystems Deployment Service listening on port 12001.
OK. OutSystems Scheduler Service listening on port 12002.
Starting Web Server...
Checking HTTP port availability...
OK. Process 'System' listening on port 80.
Publishing OutSystems Service Center 4.1.3.15...
Publishing Extension(s)...
Reading Service Center oml file information...
Adding Service Center eSpace to database...
Compiling Service Center eSpace...
Preparing Service Center eSpace deployment...
Creating Service Center default tenant...
Deploying Service Center eSpace...
Message 1
Id : FailedTenantDeployment_PingAspx
Type : Error
Message : Error publishing in node WIGBCDF6751 (127.0.0.1): Tenant deployment failed
Submitable : True
Details :
Deployment of tenant Unable to connect to the remote server
at System.Net.HttpWebRequest.GetResponse()
at OutSystems.HubEdition.DeployService.Deploy.#Hj(String hostname, String espaceName, String ptaOrTenantName) failed. Could not invoke ping. Exception:
ExtraInfo :
CompModule : Broadcast Message
Message 2
Id : FailedTenantDeployment_PingAspx
Type : Error
Message : Error publishing in node WIGBCDF6751 (127.0.0.1): Tenant deployment failed
Submitable : True
Details :
Deployment of tenant Unable to connect to the remote server
at System.Net.HttpWebRequest.GetResponse()
at OutSystems.HubEdition.DeployService.Deploy.#Hj(String hostname, String espaceName, String ptaOrTenantName) failed. Could not invoke ping. Exception:
ExtraInfo :
CompModule : Broadcast Message
OutSystems Service Center publish failed with error code 110
Installation could not be completed!

Check 'D:\Program Files\OutSystems\Installer\Logs\ExpressInstall.log' for installation details

Installed components:
• OutSystems Integration Studio
• OutSystems Service Studio
• .NET Framework Hot Fix KB923028
• Visual C++ 2005 Runtime Libraries SP1

Not installed components:
• OutSystems Service Center
• IT Asset Manager
Please try to access http://localhost/ServiceCenter and see if you can see the ServiCenter page. If you can, then it's probably your firewall. Have you submitted feedback when the installation failed?

Best Regards,
Gustavo Guerra
I have the same problem.
I've submitted the problem after it failed.

After this error I could not connect to http://localhost/ServiceCenter/

"There was an error processing your request:

Invalid value in OutSystems.HubEdition.SMSConnector.InboundQueue

Invalid value in OutSystems.HubEdition.SMSConnector.InboundQueue
at OutSystems.HubEdition.SMS.SMSInterface.Init()
at ssServiceCenter.Global.Application_Start(Object sender, EventArgs e)

Please rewrite the application URL."
The same happens to me once. I uninstall outsystems, then remove all folders of iis relationed with outsystems and remove all references of the windows registry and i install again outsystems and works fine.

Nelson Inácio