Sage 50 provides an easy and user-friendly interface for businesses to carry out their day-to-day accounting tasks. However, just like any other software, Sage is also not without its fair share of errors and issues. In this blog, we will discuss about two common error codes encountered by the Sage users, namely, sage error 500 and 503.
Causes of Sage Error 500
The most common causes of the Sage Error 500 are as follows–
- The Database portal is not configured properly
- HTTP 500 error
Procedure to Resolve Sage Error 500
Here is a simple procedure to fix the Sage Error 500-
- Click on the Start menu
- Press Windows + R on your keyboard. The Run menu will pop up on your screen
- Write Intemgr in the search box
- Press Enter
- Click to select the CRM website
- Now go to the pages in the IIS category that are having errors
- Rightclick on the Status code 500
- Go to Further Options
- Click on Edit Feature Settings
- Next, click on Detailed Errors
- Click Ok to proceed further
- Next, log into CRM to check if you are still getting the error code
Reasons behind the Sage Error 503?
The most common causes of the Sage Error 503 are–
- Error logging in to the Sage ESS
- The Sage ESS Serviceis notrunning
- Any ongoing updation related to network, database or application
- The server may be overloaded due to spam, virus attacks, network traffic etc
Read Also-: How to Fix Sage 500 Upgrade Utility Fails
Step to Resolve Sage Http Error 503
Here are three simple methods to resolve this issue
Total Time: 35 minutes
Check Sage ESS Maintenance on the Sever
Make sure to check the Sage ESS System Maintenance on the server where ESS has been installed. Also, you need to uncheck the Locked Box and verify that the user name, databases, server name and password are correct. If you are still getting the issue, carry out the following steps-
🔷 Go to Sage ESS server
🔷 Navigate to the Administrative Tools and open Component Services
🔷 Verify if both the World Wide Web Publishing and IIS Admin Services are running
🔷 Start the IIS Manager
🔷 Click to open the Sites folder,
🔷 Go to the Default Web Site
🔷 Right click on the Self Service tab
🔷 Navigate to Manage Applications and then to Advanced Settings
🔷 Ensure that the default Application Pool name is set to AbraAWCAppPool
🔷 Close Advanced Settings
🔷 Go to Application Pools
Ensure that the Status is set to Started, the Managed Pipeline Mode is set to Classic and .Net is set to v2.0
Activate Application Pools
Here are the steps to follow-
🔷 Click on Administrative Tools
🔷 Click IIS Manager
🔷 Locate Application Pools in the list of applications and click on it
🔷 Now search for MobileClientPool and WebClientPool
🔷 Right click on them
🔷 From the list of actions, click Start
Check the Physical Path Used by Your Website
Please follow the steps below-
🔷 Navigate to the Path Start>
🔷 Click on Administrative Tools
🔷 Click IIS
🔷 From the list, click Sites and expand it
🔷 Click Default Web Site from the list of sites
🔷 Navigate to Advanced Settings
🔷 Browse to the physical path and verify if the line reads %SystemDrive% \inetpub\wwwroot\webclient
🔷 Click OK if the path is found to be correct. If not, set the proper path
🔷 Once complete, restart the site.
Final Words
We hope the discussion above would help you fix the Sage Error 500 and 503. If you are still not able to fix this issue, or, if you have any more related queries, you may speak to some of the experienced Sage experts.
🔔Frequently Asked Questions
What are the Instances when the Sage Error 503 can Appear?
You may encounter the Sage Error 503 at the following instances-
▪ While trying to install the SEI (Sage Enterprize Intelligence)
▪ After the SEI gets installed and you want to navigate to the localhost, to visit your log in page
▪ While accessing the ESS
What is the Most Common Reason of the “Sage HTTP Error 503: Service Unavailable” Error?
The most common reason of occurrence of the Sage HTTP 503 error is a sudden communication breakdown between the Sage server and the website it supports. It makes the website unable to handle any request coming from browser of an user.
