the problem occurs when I want to go here ==> http://localhost/scripts/cgiip.exe/WService=hend/xlogin.w

HTTP 404 error sometimes and sometimes the error is WebSpeed error from messenger process (6019)

Msngr: Failed to connect to the specified WebSpeed named service. Verify that the service has been started. Verify the configuration for the service is correct. (5804): Error -65

the operative system is WIN 7 , the progress is the version 11.3 the IIS is version 7

I have stopped working from yesterday , all because of the problem above

the problem occurs when I want to go here ==> http://localhost/scripts/cgiip.exe/WService=hend/xlogin.w

HTTP 404 error sometimes and sometimes the error is WebSpeed error from messenger process (6019)

Msngr: Failed to connect to the specified WebSpeed named service. Verify that the service has been started. Verify the configuration for the service is correct. (5804): Error -65

the operative system is WIN 7 , the progress is the version 11.3 the IIS is version 7

I have stopped working from yesterday , all because of the problem above

what other meaningful detail? can you say an example please ?

There is no solution , Progress dind't found any solution to this

Can you kindly send the links to get a ticket for this issue , please : your website is very difficult and complex

Is very difficult to find the place in your web to raise a ticket , where is that ?

> I have stopped working from yesterday , all because of the problem above

So it was working yesterday I take it. What has changed ? (on the OS, on the config ….)

> What other meaningful detail? can you say an example please ?

What is your setup like ? All in one machine, including messenger and the webspeed broker or distributed ? Firewall or antivirus with firewall present ?

Answ: Yesterday was the first time I need to get into that link , and found the problem for first time.

Answ: When I state no solution , is because I read your post : refer to you serve administrator if you got this problem , which indicate me that nobody have an idea about this.

In win 7 is not possible add the ASP and .net version that IIS7 is requesting.

Ramon    

I don't know which version is requesting , and that is part of the problem:  my .net framework 4.5.1 is not good and in order to get the webspeed server working I need uninstall this 451 .net framework and install the .net 4.0 or 3.5 , not sure ,l what is sure is the webspeed need and old version of this components , please add to the equation the fact : you can't add features(ASP, CGI, ISAPI , .net )  in WIN7 on this time  because simply : not possible (that's the reason : not possible)  

But then I remember reading the Visual Studio upgrade 4 documentation and found they got by default an ASP components. So once the upgrade 4 was installed , the link work for few seconds , then HTTP 404 again and so on  

now the installation is : fragile  (to use the right term)    

ok Brian,  Trying now....2 mins

no , they dont fully coexist =  3.5 .net coexist with other versions but V4.0 don't like v4.5 and don't like stay with 4.5.1

HTTP 404

Sometimes HTTP 404 sometimes  webspeed generic error

is the 5804 error -65

For what it's worth, -65 means "Connection timed out".

-----------

HTTP 404 error sometimes and sometimes the error is WebSpeed error from messenger process (6019)

Msngr: Failed to connect to the specified WebSpeed named service. Verify that the service has been started. Verify the configuration for the service is correct. (5804): Error -65

And disable antivirus for a minute (are you using karspersky?) and firewall.

***/ 3rd day with the problem /**

Today receiving :

WebSpeed error from messenger process (6019)

Msngr: Failed to connect to the specified WebSpeed named service. Verify that the service has been started. Verify the configuration for the service is correct. (5804): Error -66

webspeed : running

still getting error

Trying Muhammad Akbar's solution adding the CGI....

CGI ISAP selected , yes I can see are there well selected , well present , fiscally there , and still getting error

1)  Make sure CGI and ISAPI Extension features of IIS are installed:

 1.Control Panel -> Program and Features -> Turn Windows features on or off

2.Windows Server 2008: The Server Manager window will open. Navigate to Roles -> Web Server(IIS) -> Roles Services \Application Development and confirm that CGI, ISAPI Extensions are listed as status installed.

OR

1.Windows Vista or Windows 7: Expand Internet Information Services -> World Wide Web Services -> Application Development Features and confirm that CGI and ISAPI Extensions are selected.

2)  Create a virtual directory for the WebSpeed Messenger executables:

1.In the IIS Manager Connections tree, expand Sites.

2.Select Default Web Site

3.In the Actions menu (right side), select View Virtual Directories.

4.In the Virtual Directories Actions menu, select Add Virtual Directory...

5.In the Alias: text box, enter any name for the virtual directory (for example "scripts"; it does not have to be the name of the physical directory).

6.In the Physical path: text box, enter the path to the directory where cgiip.exe and/or wsisa.dll are located (for example "c:\inetpub\scripts"). This needs to be set to the directory where the cgiip.exe or wsisa.dll are located based on when you installed the WebSpeed Messenger.  For information on this, see your installd.ini in your OpenEdge installation directory to identify what path you specified during the installation.

3)  Allow cgiip.exe / wsisa.dll to run on IIS:

1.In the IIS Manager Connections tree (left side), click on the server name.

2.In the server Home pane IIS section, select ISAPI and CGI Restrictions

3.In the Actions menu (right side), click Open Feature

4.In the ISAPI and CGI Restrictions pane Actions menu, click Add...

5.Add the full path to and including the file cgiip.exe and/or wsisa.dll and select "Allow extension path to execute".

6.In the IIS Manager Connections tree, expand Sites -> Default Web Site.

7.Select the virtual directory created in step 2 ("scripts" in this example).

8.In the middle panel IIS section (where the directory path name is displayed), select Handler Mappings.

9.In the Actions menu, select Open Feature.

10.In the Handler Mappings pane, right-click on the CGI-exe or ISAPI-dll handler and select Edit Feature Permissions.

11.Select "Execute".

4)  Create a virtual directory for the WebSpeed images and doc:

1.Follow steps 2a through 2d to access the Add Virtual Directory dialog.

2.In the Alias: text box, enter "webspeed" followed by the version number (for example "webspeed102b").

3.In the Physical path: text box, enter <DLC>\webspeed.

5)  When running 32-bit wsisa.dll on 64-bit Windows, follow the procedure in article 000013763, "How to configure 32-bit webspeed messenger on 64-bit IIS 7 on Windows 2008/Vista" .

6)  The virtual directory you created for the Default Web Site in the IIS Manager (example:  scripts) needs to have a group IIS_IUSRS with read and execute permissions.

In the Connections panel, right click the directory name -> Edit Permissions - Security -> Edit (to change permissions).  Select Add.  Then enter IIS_IUSRS and select Check Names to validate that the group exists on the machine.  Then click OK.  

The IIS_IUSRS group must have read, execute, and list permissions on the WebSpeed Messenger scripts directory, and read, execute, list and write permissions on the directory specified in ubroker.properties for the messenger log files.  Depending on the directories chosen these permissions may already be set based on the step above.  If missing, then add them.

All this done ... the result:

WebSpeed error from messenger process (6019)

Msngr: Failed to connect to the specified WebSpeed named service. Verify that the service has been started. Verify the configuration for the service is correct. (5804): Error -66

Error error error.

Ramon, Have you opened a Support Incident with Progress as Brian recommended yesterday?


-------- [collapse]Original message -----[/collapse]