NI Application Web Server refuses to be enabled

[Mads]

I'm trying to deploy a web service made in LabVIEW 2010 and it fails to deploy saying that the NI Application Web service is not running....

So I connect to http://localhost:3580, login as Admin (blank password) and click the web servers page. There I set the port of the Application Web Server to 8080, click the enable checkbox...and hit the apply button - and the only thing that happens is that the browser shows the Error on page symbol in its status bar....There is no "Yes" showing next to the Enable checkbox like for the system web server...

So - if I start from scratch again and do the same, but also click the 32 bit radio button prior to hitting the apply button - what happens? Well, then I get an error dialog:

The service itself (32bit, the 64 bit is listed but not as started) is running according to the services control panel...

I'm stuck....So do anyone know what's missing here, is there something I'm doing wrong, or something that needs to be done prior to activating the application service? 

[Mads · Accepted solution]

Uninstalling and reinstalling 32 bit LabVIEW 2010 on two different machines revealed that the problem only showed up on my 64 bit Vista macine - not the 32 bit Windows 7 macine...

Looking at the services running on the machine with the problem I could see that it was running the 32 bit version of the Web application server, had a 64 bit installed but set to disabled....- but - only the latter was set to depend on the NI Web server service. This looked a bit strange as the 32 bit version on the 32 bit machine was dependant on the NI Web Server....

So - I disabled the 32 bit NI Web Application server service, enabled the 64 bit...and voila - I am now able to configure the Web Application Server to start.

So why is both the 32 and 64 bit Web application services installed, with only the 32 bit one running - but not properly? Is this what happens to everyone, but everyone fixes it by switching to the 64 bit version...or is there something that causes the installation to get messed up?