goldfish Trusted Contributor.
Trusted Contributor.
1253 views

error: connection opening to Webinspect ENT Manager

Hi All ,

 

I  am doing installation for Webinspect Enterprise installation with ssc integration .

After initialization it shows " Connecting to Webinspect Manager "

But fails with error " An Unexpected Error Occurred , Please try again "

 

When i have checked in Programfile/Fortify/Initializer/initializer.log "found out below messages "

 

Please suggest

 

*************************************************

 

2019-05-05 09:56:50,359 INFO [1] Configuring WebInspect Enterprise Task service...
2019-05-05 09:56:50,359 INFO [Database Init] WIE Task service is not currently running
2019-05-05 09:56:50,375 INFO [1] Updating Task service configuration file...
2019-05-05 09:56:50,390 INFO [1] Starting WebInspect Enterprise Task service...
2019-05-05 09:56:53,937 INFO [1] Configuring Scheduler service...
2019-05-05 09:56:53,937 INFO [Database Init] Scheduler service is not currently running
2019-05-05 09:56:53,937 INFO [1] Updating Scheduler service configuration file...
2019-05-05 09:56:53,937 INFO [1] Starting Scheduler service...
2019-05-05 09:56:54,359 INFO [1] Web Service Initialization Succeeded...
2019-05-05 09:56:54,375 INFO [Database Init] Completed
2019-05-05 10:18:14,752 INFO [141] Manager URL is https://WIN-LM7CPLP7TH5/WIE/
2019-05-05 10:18:21,627 WARN [141] Unable to determine SSC connected status.
System.InvalidOperationException: Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>500 - Internal server error.</title>
<style type="text/css">
<!--
body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}
fieldset{padding:0 15px 10px 15px;}
h1{font-size:2.4em;margin:0;color:#FFF;}

 

*********************************

 

 

0 Likes
2 Replies
Micro Focus Contributor
Micro Focus Contributor

Re: error: connection opening to Webinspect ENT Manager

 

Are you able to connect to your SSC server from the WIE server?

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: error: connection opening to Webinspect ENT Manager

You will also want to verify that a browser on the WIE Manager server can reach the SSC Server (and log in), since that is what the error logs indicates.  Be sure that you are using the SSC server URL as you entered it into the WIE Initialization Wizard.

 

For this error <<Client found response content type of 'text/html', but expected 'text/xml'.>>:   Usually when I see this error, it indicates a problem with the IIS set-up and perhaps missing .NET Features for the WIE Manager server.  The immediate meaning here is paraphrased as, "I expected to talk to a web service program (XML) but instead I was provided a server error (TXT)".  So I would review the WIE Manager Implementation Guide for the Installation steps around IIS and .NET.

 

Lastly, be certain that you understand these two separate URLs for WIE Manager.

  • https://wie-host-name/wie/WebConsole - Provided to the human users and their browsers.
  • https://wie-host-name/wie/ - Provided to SSC Server, WIE Initialization, and other connecting clients (WIe Console - thick client, WIE Sensors, WebInspect desktop).

-- Habeas Data
Micro Focus Fortify Customers-Only Forums – https://community.softwaregrp.com/t5/Fortify/ct-p/fortify
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.