Workflow - Server Application Unavailable
This issue has been solved. See solution.
Tom Tokarczyk
July 23rd, 2009
Hello!
I'm still new with Workflow and I'm having an issue where after I publish a Workflow I get an error saying: (Below is the screenshot)
Server Application Unavailable
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
The Workflow that I have is VERY simple. It goes from Start to Get Current User to Send Email to End. I'm thinking the issue with IIS or I'm missing a value somewhere in the Project settings. I was able to successfully publish another Workflow after tweaking some settings...
Any thoughts on why I'm getting this error? I've restarted IIS and checked over everything I can think of...
Tom
Check logs and check project properties
I would try the following:
Make sure that you don't have any legacy localhost entries in the project properties from running the project in the lab environment.
Check your W3WC logs on your IIS server for workflow (usually located in Windows\system32)
Check to see if you can browse to the site locally on your IIS box. If so, then it's a site properties issue.
Hope that helps,
Jim
Re: Check logs and check project properties
I ensured that there were no localhost names in the properties...
I checked the W3WC logs for Workflow. The name was peppered all over the logs, so I'm not sure what I should be checking for...?
When I browse to the site locally through IIS I get the same error.
Check Event Viewer - Application Log
Hello Tom,
You might want to check the application log in the event viewer. There's a good chance this is a permissions problem.
Good luck,
John
Any luck?
Tom, did you get it working?
No Luck so Far...
I've been out of the country for a week on vacation, but I plan on getting back on this today. Maybe being relaxed will help me out!
Still nothing...
I published some basic workflows just for testing and they aren't working...still getting the same error as above...anything else I can possibly check over?
Fixed...
I'm not sure how, but the application pool was reset back to the default application pool. That's what ended up causing the issue. I turned it back to the dontnet2 and the pages worked again. I can now publish again.
Would you like to reply?
Login or Register to post your comment.