Skip to main content

I am searching for a setup document for IIS 7.0 and Net Express 5.1 for web applications.  I am having the following issues

1) I cannot get the "CBL_DEBUGBREAK" to pop the debugger from IIS.  In older versions of IIS, I could just click the "interact with desktop" on the service and it would allow this to work.  Are there updated instructions for IIS debugging with the newer versions of IIS and the more locked down security of IIS in its current state

2) IIS will not automatically identify the system variables we use to set COBSW and other settings.  In older versions of IIS, it inherited all of the environment variables, but it no longer does that.    Are there instructions on how to do this with Net Express 5.1 and IIS 7

3) Is there a best practice document when using IIS that details how to use configuration files to setup parameters in lieu of calling the .exe directly?  In Apache on UNIX we use shell scripts to setup the environment before we call the server express programs.  We don't know what to do on the Windows side to mimic this behavior

Any information would be appreciated.

I am searching for a setup document for IIS 7.0 and Net Express 5.1 for web applications.  I am having the following issues

1) I cannot get the "CBL_DEBUGBREAK" to pop the debugger from IIS.  In older versions of IIS, I could just click the "interact with desktop" on the service and it would allow this to work.  Are there updated instructions for IIS debugging with the newer versions of IIS and the more locked down security of IIS in its current state

2) IIS will not automatically identify the system variables we use to set COBSW and other settings.  In older versions of IIS, it inherited all of the environment variables, but it no longer does that.    Are there instructions on how to do this with Net Express 5.1 and IIS 7

3) Is there a best practice document when using IIS that details how to use configuration files to setup parameters in lieu of calling the .exe directly?  In Apache on UNIX we use shell scripts to setup the environment before we call the server express programs.  We don't know what to do on the Windows side to mimic this behavior

Any information would be appreciated.

This won't be very helpful, but I have never been able to get the debugger to work under IIS, Net Express 5.1 and Windows 7 64bit. Although I was in contact with support, there wasn't any quick solution and I've never gotten around to getting it fixed. Maybe whatever works for you will also work for me, I'll keep following this thread.

I am searching for a setup document for IIS 7.0 and Net Express 5.1 for web applications.  I am having the following issues

1) I cannot get the "CBL_DEBUGBREAK" to pop the debugger from IIS.  In older versions of IIS, I could just click the "interact with desktop" on the service and it would allow this to work.  Are there updated instructions for IIS debugging with the newer versions of IIS and the more locked down security of IIS in its current state

2) IIS will not automatically identify the system variables we use to set COBSW and other settings.  In older versions of IIS, it inherited all of the environment variables, but it no longer does that.    Are there instructions on how to do this with Net Express 5.1 and IIS 7

3) Is there a best practice document when using IIS that details how to use configuration files to setup parameters in lieu of calling the .exe directly?  In Apache on UNIX we use shell scripts to setup the environment before we call the server express programs.  We don't know what to do on the Windows side to mimic this behavior

Any information would be appreciated.

I just tested this here with Net Express 5.1 WP9 under IIS 8.5 on Windows Server 2012 and it worked fine for me.

Windows was changed starting with Windows Vista to not allow Windows services to interact directly with the desktop so using CBL_DEBUGBREAK by itself will no longer work for CGI applications running under IIS.

You can however debug an application running under IIS by starting the Net Express IDE and changing the Animate Settings to Wait for Animatable Attachment and then clicking on Animnate-->Start Animating and then clear the field and press OK.

This will put animator into a wait state.

Then run your application from a web browser and when CBL_DEBUGBREAK is hit it will stop in yoiur program in the debugger.

Instructions for setting up IIS 7.0 and higher for NX CGI apps can be found in the following KB article here:

Environment variables set at the system level should be picked by your application but you may have to reboot the computer so that IIS will pick them up correctly.

Terms & ConditionsAccessibility statement