We just upgraded our DB to 2024.1 and we are getting the following error:
The service is unavailable (HTTP status code 503)
This is for our live environment.
we have reinstalled the appserver. Anyone have any suggestions for us?
Our test version was working like a charm so not understanding why our live version is not
Is the test on a different server?
Yes-
I’ve had issues before, try going into the add/remove programs and repair the .net hosting bundle.
we’re going to give this a try next
We are still no further ahead than we were before unfortunately.
Where are you getting the 503 error?
when trying to print a report in the web 2024.1 - the task errors out and gives us the 503 error
I suspect it has to do with the report database being moved to a table instead of the server itself.
we see the error in the event viewer but not in the app server log.
what does that mean? can we use our phone a friend line?
there’s post here about this… I think @Hally posted it… or maybe @klincecum i’m looking for it
Here you go see if this helps any
The question we are asking ourselves now is what should add to the report server tab on the app server setup.
What kicks us is that it has worked through 2023.2 and 2024.1 testing with no issues and today during go live we can’t seem to get this going.
Did you open a system down issue with Epicor? This seems like something they should be able to fix quickly
I tried to do a urgent ticket but it was changed to high.
I will try to do another ticket as this seems silly it should stop us from going live with 2024.1
We finally found the issue. Back years ago we added some task agent rules in 10.2.400 or 10.2.600. They should have been turned off but apparently they were still trying to route reports to the 10.2.600 app server. Some better error messages would have gotten us there sooner.
Moving forward to SME validation first thing this morning.
Sorry have been travelling, @kfierce glad you got it solved.