[archive] Configuring IIS6 with Wrun32 for 5.2.1

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

What you have to do is to set up an association between the extension .acu and the runtime, you do this via Explorer (NOT internet explorer!) Menu Tools and Folder Options.

In the dialog poping up, you select the File Types tab.

Then follow the instructions in the 5.2.1 documentation, you typically has to had a method, a open method. In this you would type in the runtime and its preferred parameters;

c:\\acucorp\\acucbl521\\acugt\\bin\\wrun32 -c \\etc\\cblconfi

and whatever other parameters you want, remember -f unless you have set A_CGI in the environment to tell the runtime to behave as a cgi application.

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

What you have to do is to set up an association between the extension .acu and the runtime, you do this via Explorer (NOT internet explorer!) Menu Tools and Folder Options.

In the dialog poping up, you select the File Types tab.

Then follow the instructions in the 5.2.1 documentation, you typically has to had a method, a open method. In this you would type in the runtime and its preferred parameters;

c:\\acucorp\\acucbl521\\acugt\\bin\\wrun32 -c \\etc\\cblconfi

and whatever other parameters you want, remember -f unless you have set A_CGI in the environment to tell the runtime to behave as a cgi application.

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

What you have to do is to set up an association between the extension .acu and the runtime, you do this via Explorer (NOT internet explorer!) Menu Tools and Folder Options.

In the dialog poping up, you select the File Types tab.

Then follow the instructions in the 5.2.1 documentation, you typically has to had a method, a open method. In this you would type in the runtime and its preferred parameters;

c:\\acucorp\\acucbl521\\acugt\\bin\\wrun32 -c \\etc\\cblconfi

and whatever other parameters you want, remember -f unless you have set A_CGI in the environment to tell the runtime to behave as a cgi application.

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

I am trying to associate the .acu in IIS6. The association via Explorer will only work for that one workstation where I associate it.

The acuconnect manual describes how to set up the association within Microsoft's IIS and it works for Nt4 and Windows 2000.

Here is the string I have in the IIS5 to associate .acu

C:\\Acucorp\\Acucbl521\\AcuGT\\bin\\WRUN32.exe -c \\\\QA\\D004\\CONFIG\\serverobj.cfg -f -lxe e:\\inetpub\\traces\\cgi-t.log %s

Doing the same things on a windows 2003 Following the same instructions on windows 2003 is where I am having the problem.

I cannot get the wrun32 to execute and produce a log file so I can figure out what is wrong.

Thanks

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

First of all. When referring to Explorer, I meant on the server only. When it comes to cgi objects, it is all executed on the server, so you should not do anything on the client computer.

Now, having said that, there is one thing that concerns me with your association string. You are referring to another machine (I presume QA is not the server you are executing on since you refer to it using the UNC path).
Remember that services under Windows run in the security scheme of the local administrator, with two exceptions:

A) If you force it to run under an alternate account (this is accomplished in the services setup, property of the particular service)

or

B) If is ran under the www server constraints, which has individual settings for security contexts.

I am pretty confident this is the root of the problem here. An easy way to determine this is if you temporarily move your objects into a sub directory of the WWWroot directory of your server, from which the cgi objects should be automatically granted access. Then change the association accordingly. If this works, then we have the cause of the problem.

If this doesn't work, I suggest you contact technical support as it will be necessary to obtain more info / spend more resources than I can afford to here.

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

First of all. When referring to Explorer, I meant on the server only. When it comes to cgi objects, it is all executed on the server, so you should not do anything on the client computer.

Now, having said that, there is one thing that concerns me with your association string. You are referring to another machine (I presume QA is not the server you are executing on since you refer to it using the UNC path).
Remember that services under Windows run in the security scheme of the local administrator, with two exceptions:

A) If you force it to run under an alternate account (this is accomplished in the services setup, property of the particular service)

or

B) If is ran under the www server constraints, which has individual settings for security contexts.

I am pretty confident this is the root of the problem here. An easy way to determine this is if you temporarily move your objects into a sub directory of the WWWroot directory of your server, from which the cgi objects should be automatically granted access. Then change the association accordingly. If this works, then we have the cause of the problem.

If this doesn't work, I suggest you contact technical support as it will be necessary to obtain more info / spend more resources than I can afford to here.

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

Thanks

I moved every thing local to the server and still no luck.

I have contacted support and have an Incident ID 99-015537.

This is the last email I got on this incident.

Hi Pierre,

After discussing this matter with our Quality Assurance Department, I learnt that they never tested with IIS on a Windows 2003 Server. They only tested the CGI runtime version 6.0.0 on our in-house Windows 2000 Server with IIS version 5.0. As I mentioned in my e-mail of December 17, 2003, "Please be advised that Technical Support does not provide support for IIS. As there are many web servers, my Manager has advised that it is outside the scope of Technical Support."

Assuming that you are using IIS version 6.0 and we do not have in-house expertise in this area, recommend contacting the Microsoft Support Group for assistance.

Regards,

I was just hoping someone had figured it out.

Thanks

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

Thanks

I moved every thing local to the server and still no luck.

I have contacted support and have an Incident ID 99-015537.

This is the last email I got on this incident.

Hi Pierre,

After discussing this matter with our Quality Assurance Department, I learnt that they never tested with IIS on a Windows 2003 Server. They only tested the CGI runtime version 6.0.0 on our in-house Windows 2000 Server with IIS version 5.0. As I mentioned in my e-mail of December 17, 2003, "Please be advised that Technical Support does not provide support for IIS. As there are many web servers, my Manager has advised that it is outside the scope of Technical Support."

Assuming that you are using IIS version 6.0 and we do not have in-house expertise in this area, recommend contacting the Microsoft Support Group for assistance.

Regards,

I was just hoping someone had figured it out.

Thanks

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

Thanks

I moved every thing local to the server and still no luck.

I have contacted support and have an Incident ID 99-015537.

This is the last email I got on this incident.

Hi Pierre,

After discussing this matter with our Quality Assurance Department, I learnt that they never tested with IIS on a Windows 2003 Server. They only tested the CGI runtime version 6.0.0 on our in-house Windows 2000 Server with IIS version 5.0. As I mentioned in my e-mail of December 17, 2003, "Please be advised that Technical Support does not provide support for IIS. As there are many web servers, my Manager has advised that it is outside the scope of Technical Support."

Assuming that you are using IIS version 6.0 and we do not have in-house expertise in this area, recommend contacting the Microsoft Support Group for assistance.

Regards,

I was just hoping someone had figured it out.

Thanks

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

Hi,

I have the same problem, right now, when using IIS 6.0 (Server 2003). As in the pverleysen's example the same application configuration works fine in IIS 5.0 (Windows 2000) and even IIS 5.1 (Windows XP).

I use AcuGT 6.0 & 6.2 with identical results.

All the CGI code resides local to the web server and the command in IIS 5.0/5.1 is similar to:

C:\\Inetpub\\wwwroot\\cgi-bin\\nature.exe -x -c C:\\Inetpub\\wwwroot\\etc\\almacen.cfg -f  C:\\Inetpub\\wwwroot\\almacen\\hent.cob %s

But in IIS 6.0 i can't use the same command line (server 2003 extension assignation rejects it).

As pverleysen said, using quotes doesn't solves the problem:

"C:\\Inetpub\\wwwroot\\cgi-bin\\nature.exe" -x -c C:\\Inetpub\\wwwroot\\etc\\almacen.cfg -f  C:\\Inetpub\\wwwroot\\almacen\\hent.cob %s

Are there any news about this behavior ?

if not, someone knows a workaround (perhaps another web server or the new Extend 7) ?

Regards

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

We succesfully use the following application extension mapping command line on Windows 2003 IIS 6:


C:\\acucorp\\wrun32.exe -w -c c:\\acucorp\\cblconfi.nl -f ?%s%s?


We specify the cobol program name in a hyperlink, for example:


[url]webserver/.../cobolprog.obj


Our cobol program is in a virtual folder named scripts. This is the virtual folder that we specify the application extension mapping command line.

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

We succesfully use the following application extension mapping command line on Windows 2003 IIS 6:


C:\\acucorp\\wrun32.exe -w -c c:\\acucorp\\cblconfi.nl -f ?%s%s?


We specify the cobol program name in a hyperlink, for example:


[url]webserver/.../cobolprog.obj


Our cobol program is in a virtual folder named scripts. This is the virtual folder that we specify the application extension mapping command line.

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

Thanks, Dan. Interesting approach.

I was wrong because I was confusing two diferent aspects of the trouble. After a little of research I have discovered part of the problem.

The first issue is the failure associating the ".acu" extension (".cob" in my case) in IIS 6. As comented by pverleysen I can't leave the command as in IIS 5. I need to enclose with quotes the program, leaving the parameters out:

[b]"C:\\Inetpub\\wwwroot\\cgi-bin\\nature.exe"[/b] -x -c
C:\\Inetpub\\wwwroot\\etc\\almacen.cfg -f  C:\\Inetpub\\wwwroot\\almacen\\hent.cob %s

This makes IIS6 to accept the command syntax (perhaps it needs validation of the program file name, although the "Check if the file exists" box is unchecked).

The second one is not yet completely clear for me. In essence let's say II6 is much more restrictive, regarding to security, than IIS 5 is.

First, after a default installation of IIS 6, no active content can be delivered until we configure "Web Service Extensions". Neither asp nor, of course, CGI generated data will be delivered by the server if an apropiate Service Extension is not declared.

The first approach consists in select "allow" for the "all unknown CGI extensions" option. This method is relatively unsecure but, hey, is the very first time i get this thing working.

Really the correct implementation will be creating of a new Web Service Extension which especifies the files CGI runtime needs to work (wrun32.exe, dlls, etc), but I still haven't viewed in detail the IS 6 documentation.

There are some good information here about
Creating Applications and Configuring CGI Applications

is also convenient take care on new security behaviors in IIS 6.

Regards.

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

Thanks, Dan. Interesting approach.

I was wrong because I was confusing two diferent aspects of the trouble. After a little of research I have discovered part of the problem.

The first issue is the failure associating the ".acu" extension (".cob" in my case) in IIS 6. As comented by pverleysen I can't leave the command as in IIS 5. I need to enclose with quotes the program, leaving the parameters out:

[b]"C:\\Inetpub\\wwwroot\\cgi-bin\\nature.exe"[/b] -x -c
C:\\Inetpub\\wwwroot\\etc\\almacen.cfg -f  C:\\Inetpub\\wwwroot\\almacen\\hent.cob %s

This makes IIS6 to accept the command syntax (perhaps it needs validation of the program file name, although the "Check if the file exists" box is unchecked).

The second one is not yet completely clear for me. In essence let's say II6 is much more restrictive, regarding to security, than IIS 5 is.

First, after a default installation of IIS 6, no active content can be delivered until we configure "Web Service Extensions". Neither asp nor, of course, CGI generated data will be delivered by the server if an apropiate Service Extension is not declared.

The first approach consists in select "allow" for the "all unknown CGI extensions" option. This method is relatively unsecure but, hey, is the very first time i get this thing working.

Really the correct implementation will be creating of a new Web Service Extension which especifies the files CGI runtime needs to work (wrun32.exe, dlls, etc), but I still haven't viewed in detail the IS 6 documentation.

There are some good information here about
Creating Applications and Configuring CGI Applications

is also convenient take care on new security behaviors in IIS 6.

Regards.

[Migrated content. Thread originally posted on 13 January 2004]

I have acucobol cgi installed on IIS5 on windows 2000 and now trying to do the same thing on IIS6 windows 2003.

I cannot define the .acu and get it to accept the configuration file.

If I put the string in quotes it will accept is but will not execute.


Any suggestion.


Pierre

Thanks, Dan. Interesting approach.

I was wrong because I was confusing two diferent aspects of the trouble. After a little of research I have discovered part of the problem.

The first issue is the failure associating the ".acu" extension (".cob" in my case) in IIS 6. As comented by pverleysen I can't leave the command as in IIS 5. I need to enclose with quotes the program, leaving the parameters out:

[b]"C:\\Inetpub\\wwwroot\\cgi-bin\\nature.exe"[/b] -x -c
C:\\Inetpub\\wwwroot\\etc\\almacen.cfg -f  C:\\Inetpub\\wwwroot\\almacen\\hent.cob %s

This makes IIS6 to accept the command syntax (perhaps it needs validation of the program file name, although the "Check if the file exists" box is unchecked).

The second one is not yet completely clear for me. In essence let's say II6 is much more restrictive, regarding to security, than IIS 5 is.

First, after a default installation of IIS 6, no active content can be delivered until we configure "Web Service Extensions". Neither asp nor, of course, CGI generated data will be delivered by the server if an apropiate Service Extension is not declared.

The first approach consists in select "allow" for the "all unknown CGI extensions" option. This method is relatively unsecure but, hey, is the very first time i get this thing working.

Really the correct implementation will be creating of a new Web Service Extension which especifies the files CGI runtime needs to work (wrun32.exe, dlls, etc), but I still haven't viewed in detail the IS 6 documentation.

There are some good information here about
Creating Applications and Configuring CGI Applications

is also convenient take care on new security behaviors in IIS 6.

Regards.