IIS 6.0 & Windows 2k3 question
-
The scenario is this - a Web Service that was developed on a XP box has been deployed on IIS 6.0 & Win2k3 m/c. The Win2k3 m/c also has VS.NET 2003 installed on it. issue #1. The web service needs to launch a third party process (lets call it abc.exe) to work properly. This step fails on the Win2k3 box. w3wp.exe is running under the default NETWORK SERVICE user privileges. Is there a way to enable/set privileges to the NETWORK SERVICE account so that the ASP.NET worker process has the ability to launch any/specific process? [i tried launching Notepad.exe thru the web service & it seems to launch this successfully.] issue #2 i expected to debug the web service on the Win2k3 m/c via VS.NET but it fails with the message "... Unable to start debugging on web server. The project not configured to be debugged.". I verified the project settings between my XP & Win2k3 m/c & they are identical. Now i'm beginning to suspect that the Win2k3 default lock-down security is the culprit. Any pointers? I even added the user to the "Debugger Users" group as suggested in the docs to no avail. Any help is appreciated. TIA. Chen Venkataraman
-
The scenario is this - a Web Service that was developed on a XP box has been deployed on IIS 6.0 & Win2k3 m/c. The Win2k3 m/c also has VS.NET 2003 installed on it. issue #1. The web service needs to launch a third party process (lets call it abc.exe) to work properly. This step fails on the Win2k3 box. w3wp.exe is running under the default NETWORK SERVICE user privileges. Is there a way to enable/set privileges to the NETWORK SERVICE account so that the ASP.NET worker process has the ability to launch any/specific process? [i tried launching Notepad.exe thru the web service & it seems to launch this successfully.] issue #2 i expected to debug the web service on the Win2k3 m/c via VS.NET but it fails with the message "... Unable to start debugging on web server. The project not configured to be debugged.". I verified the project settings between my XP & Win2k3 m/c & they are identical. Now i'm beginning to suspect that the Win2k3 default lock-down security is the culprit. Any pointers? I even added the user to the "Debugger Users" group as suggested in the docs to no avail. Any help is appreciated. TIA. Chen Venkataraman
In windows server 2003 , it doesn't matter whether you have changes worker proccess startup account in order to get higher privilage, there is some thing new in that, as you can see in the iis there is one Application pools node, the only things you need to do is to create a new pool and set the Local system account for that pool, then you can specify you website to use this pool, in home directory of your web site, and set the application pool property to use that one u created. for issue #2 i think there should be something about server extention 2002 configuration, check it plz. hope it works for u