Web Service deployment failed

[MarkBlack]

Hi pltrogon, 

Do you have a support contact?  I'd like you to contact NI directly so we can better support you and provide resources to address this and some of the other issues you have been facing.

Thanks,

Mark 

[MarkBlack]

pltrogon,

Can you also point your browser to http://localhost:3580/dumpinfo and post the resulting text in this thread?  We are curious if a component called the Service Locator is able to find the Application web service.

Also, please correct me if I am wrong but you mentioned that currently deployed web services are operating as expected.  If that is not the case can you ensure you don't have any other web servers running on your system that might be occupying post 8080?  An easy test for this is to point your browser to http://localhost:8080/.  If you are really savy you can use a the developer tools built into Safari or Chrome to see exactly what server is running by looking at the response headers. On my machine this looked like:  

1. Connection:
   keep-alive
2. Content-Type:
   text/html
3. Content-length:
   126
4. Date:
   Fri, 14 Oct 2011 21:39:26 GMT
5. Keep-Alive:
   timeout=60000, max=100
6. Server:
   Mbedthis-Appweb/2.5.0

The last line is what is important.  

[pltrogon]

Wow! You guys are awesome.

OK, it looks like Justin-D's suggestion is the right direction. Several weeks ago I had followed these instructions to serve a default file. It worked fine, so I didn't consider that this might be the source of the issue. Reverting to the original version, I restarted the service and redeployed with no problem.

BUT... editing the NIWebAppServer.conf file again caused the service to crash on restart, and the crash persisted even after I reverted back to the original .conf. This time, however, the windows service manager immediately attempts a second restart and this time it succeeds and I can deploy. When I boot, the service starts without problem, so at this point, any problem is essentially invisible. My old .conf file and the new one only differ in that the old one didn't have the entry "LimitRequestBody 50000000" and the modules were added in a slightly different order. 

I've included the .conf file in case anybody can identify something glaringly wrong with it. Otherwise, I'm totally content ignoring this mysterious exception on service restart since it doesn't disable the web service. 

Thanks for the help!

[MarkBlack]

Awesome. Props to Justin D.