I have just added my first REST Service PROCESS Class. I followed the install steps very carefully, using the New Process Class wizard. I set up a new process class as a REST API Service process class. I assigned a new virtual and script map, and made sure path names and script maps were different than the main project itself. The install was quick and easy. Then I go to check out the REST service, I get the usual temporary landing page, which shows the usual two links to HelloWorld Test Page or Web Connection Administration.

I click on the Test Page, and the browser times out. I made sure the Main Project was recompiled, and I stopped and started IIS... did everything except re-boot. I noticed the docs explained that browsers need a JSON Viewer plugin for Chrome, so I installed that... and I still get time-outs when attempting the testpage.

To troubleshoot, I added a second testpage named testpage2, with the only code being a response.write("Success"). This tesptpage2 also fails by timing out.

I thought maybe I had somehow screwed up the install of the process class, so I installed two more REST Service Process classes, being very careful with virtuals, paths and script maps. They all fail in the same manner. Incidentally, the main process class (not a REST Service) in this same project, runs fine.

Thanks for any nudge in the right direction. Joel Aiken

If you're getting timeouts that sounds more like your Web Connection server isn't set up properly or you're hitting a different domain than the one you configured - wrong temp path or something along those lines. You should go to the Module admin page and check the temp path and file prefix and compare that to what you have in your app.ini file.

Here's more info:

• Setup Troubleshooting

+++ Rick ---

Rick, Thanks for your reply. Your suggestions are good ones to keep in my trouble-shooting techniques.

Go Figure.... it started working fine.
got over this hurdle, Hope it's clear sailing for a couple days.

Happy Thanksgiving to all