Sage 50 Error 1020 Access Denied

Sage 50 error 1020 access denied is one of the several error messages that users frequently encounter. The article discusses how to troubleshoot the common causes and possible solutions for this error message. You attempt to directly access a protected endpoint, and your connection request is denied?

Many Sage 50 customers have experienced some connectivity problems when using websites or systems that employ the Cloud flare proxy server. The Sage Error 1020 Access Denied is one of the several error messages that users frequently encounter.

If you too are stuck with Sage Error 1020, then you are on the right page. In this article, you will get a complete guide on Sage Error 1020, along with the causes and resolutions to fix this error.

Table of Contents

Toggle

What is Sage Error 1020?

If yes, then you don’t need to worry.

The Sage Error 1020 is a very common error that can occur when using the Sage accounting software. This error usually occurs when trying to access or save a file.

There are a few reasons why this error might occur, but the most common reason is that the file you are trying to access is corrupt or damaged. This can happen if the file was not properly closed before being reopened, or if it was damaged in some other way.

If you are encountering this error, there are a few things you can try to fix it. First, try restarting your computer and then opening Sage again. If that does not work, try uninstalling and then reinstalling Sage.

If neither of those options work, you may need to contact Sage customer support for further assistance.

How to Fix Sage 50 Cannot be Started Error Message

What are Causes Behind Sage Error 1020?

You can get stuck with Sage Error due to many reasons.

Here is the list of the causes behind this error Sage Error 1020:

The data folder has been allocated the wrong permissions.

From a backup file with an earlier version of Sage, the Organization Folder has been transferred.

Running without administrative rights is the software

On the same computer, many versions of Sage have been installed.

The Workstation and the Server are unable to ping one another.

There is either inadequate space on a network disc or none at all.

The Network Drive has been unplugged.

Missing or damaged files on the data path

On the server, User Account Control (UAC) has been activated.

What are Steps to Resolve Sage Error 1020?

Check Whether Browser Permits Use of Cookies

As previously stated, Cloud flare regulates user access to the website via cookies. It is crucial to confirm whether using this function is permitted in the browser’s settings. Access to the website can be restricted if use is not enabled.

If you use Chrome then you can follow these steps:
First, go to google chrome.
Then go to Settings.
After that, you need to choose the option Privacy and Security.
Once you choose that, go to the Site Settings.
Finally, go to the option Cookies and Site Data.

Note: Please be aware that the option to allow cookie storage must be turned on.

Modifying Permissions to Peachtree240.ini File

To modify the permissions of the Peachtree240.ini File, follow these steps:
First, you need to choose C:/ Common Files/Program Files (X86)/Peach from the list of locations.
Then right-click on the Peachtree240.ini file.
After that, select Properties
Once done go to Security.
Now select advanced, then select the Owner tab.
Then select Edit
The following step is to select the Change Owner checkbox.
Now choose your login, then click “Apply“
On each screen, click the message that is being presented to close it.
After that, Change Permissions by clicking.
The Users (Users/computer name) tab should be selected.
Once done, select Edit.
Now click OK to give users total control.
Then replicate the prior actions as admin and System
Finally, if you want to close each screen, click OK.

Editing .INI File in a Different Location

To edit the. INI File in a Different Location, follow these steps:
First, you need to place the INI File in a convenient place, like the window desktop.
After that, make the necessary adjustments.
Finally, save the changed document, and you are done.

Verify your DNS Settings

To verify your DNS settings, follow these steps:
First, on the server, simultaneously press the Windows and R keys.
You’ll see the Run command prompt on your screen.
After that enter CMD.
Once you enter CMD, press OK.
Enter the ipconfig command.
The following step is to click enter. Make a note of the IPv4 address for future use.
Now you need to enter the host Rename here.
The following step is to click enter.  Make a note of the computer’s name for future use.
Repeat the previous actions at the workstation now.
After that type Ping
Then you need to press Enter. If the Workstation receives a response from the server, note it.
Use the name of the workstation to access the server once more.
While the DNS problem is being resolved, add a host file to the system where the error message is being received.

Changing Administrator Settings

To change the administrator settings, you need to follow the steps given below:
First, you need to select a company
Then visit the Setup Users and Passwords page.
Now Set Up Users.
Then choose a person to operate as administrator. Select a person who frequently works by your office.
After that, select a company
Establishing Users and Passwords Now
Now Set Up Users.
After that go to the User List window.
Name the person who will serve as administrator.
The following step is to choose a challenge question by clicking the drop-down arrow next to it.
Then type your response in the Challenge Answer box.
Finally, click Finish.

The Cache of Your Browser

The computer stores a number of files each time a webpage is loaded. Not all changes are likely to be made automatically when viewing the page again. This will result in out-of-date files being present on your machine, especially for items like scripts, cookies, and stylesheets that don’t update regularly.

The presence of out-of-date cookies on the local computer makes this circumstance ideal for the appearance of the access forbidden error. As a result, you must clear your browser’s cache and visit the page again. In this manner, all required files will be fully reloaded, causing them to be updated and enabling the website to run.

A browser, such as Chrome, stores certain information from websites in its cache and cookies when you use it. Certain difficulties, such as slow site loading or improper site formatting, are resolved by clearing them.

To Cache Of Your Browser, follow these steps:
First, you need to go to the Tools menu (three dotted lines in the upper-right corner).
After that, choose History.
Choosing Clear Browsing Data may be found on the left side.
All Time should be selected as the Time Range.
Finally, close Chrome and reopen it if you’re using a Windows computer to save your modifications.

Last Words

When running Sage, you may encounter a message stating “Sage Error 1020”. One of the most common errors you may get when using Sage 50 is the 1020 Access Denied message. The message shows up in relation to websites or systems that employ the Cloud flare proxy server. The error happens when a user violates a firewall rule by trying to access an endpoint that is protected by Cloud flare.

Any errors starting with 1xxx are related to connection problems on sites that use the Cloud flare proxy. Now that you have a complete guide on Sage Error 1020, you can easily resolve this error and get back to running your business smoothly. However, if you are still stuck or have any queries then you can reach out to the customer helpdesk for quick and easy assistance.

Read More Information:

How to Fix Sage 50 Error Printer Not Activated Error Code 30

FAQ’s