Micros 5.2 Report Viewer not running

[mrmicros]

Win7 pc server

or manager procedures.

From what threads I could find to read checked IIS, Nic card priorities etc

This is getting so tiring....

 

[Moregelen]

Host files? IP address correct? If you try navigating manually in a browser to

http://127.0.0.1/MgrProcedures/Default.aspx

what do you see? When upgrading a database every single (EVERY SINGLE) setting on the new PC has to be right or things won't work.

 

[mrmicros]

ip correct
machine name correct
host file info correct. renamed and reloaded for new and the same.

your address brings this:

 

[Moregelen]

Sounds like it might be an application pool problem.

If you open up IIS Manager, do you see the Micros application pool as running correctly?

 

[mrmicros]

The pool was not running. Started. Reboot. Also mine says using 2.0 .Net

Still same result.

 

[Moregelen]

Check to see if the pool is stopping. If it keeps stopping, you're going to have to dig into the event viewer to find out why. You could also try the bypassreboot and bypassdbupdate keys, and run the patch again. It can sometimes fix issues like that but not always. If the pool stops, you'll get the 503.

This screenshot is from a 5.5 system. Let me try and find one of our 5.2 systems to see what the pool is set to.

Edit: Yes, our 5.2 machines are set to use v2.0. The application pool is set with these settings:

Framework 2.0.50727
Pipeline mode: Integrated
Start application pool immediately checked
Set to use LocalSystem account

 

[Moregelen]

Also does it show the micros applications are assigned to it? You should see 9-10 applications using that pool.

 

[mrmicros]

10 apps

Just looked at a live working server and its the same values.

 

[Moregelen]

Is the application pool staying running or when you check on it is it stopped? If it keeps stopping you might have to do an event viewer dive to try and figure out why.

 

[mrmicros]

No its staying running.

 

[Moregelen]

Staying running and still getting a 503 error huh. If you pull up the page, get a 503, and the pool is still running, I would still suggest taking a look in the event viewer. I haven't seen a 503 except when it was an application pool problem. That doesn't mean it can't be something else, but that has been what it was every time I've seen this.

 

[mrmicros]

Well I'll take a look. But need to park this for today. Thanks for all the input.