This article is an introduction to the common causes of this error and a solution that may help if you are having this problem. Sage 50 occasionally experiences file system error 100, which is also known as Error: “File System Error 100 in file [filename]”, when some files stop responding for unknown reasons. You confirm that an identical file may have been active in the past.
However, there could be a file system issue, a file attribute set to read-only, Pervasive executing as an application rather than a service, a damaged Pervasive file, or an insufficiently large Pervasive cache. In the given post we are going to provide some simple solutions to fix the Sage 50 File system error 100. Thus, read this post carefully so that you get a vivid understanding of the cause of the error and find a better resolution to resolve the error successfully.
What is Sage 50 File System Error 100?
A file system error is a problem with the way data is stored on a computer. It can occur when files or folders are not accessible or when there are errors in the way data is stored.
One of these errors appears on the screen of your computer’s Windows operating system when you attempt to access the specific file on Sage 50:
☛ Error: “File System Error 100 in file [filename].“
☛ Error: “File System Error 100 in file Permiss.dat.“
☛ Error: “File System Error 100 in file Serial.dat.“
☛ Error: “File System Error 100 or 3006 in file [Directory]\JRNLHDR.DAT.” Click help for more information, when attempting to save a transaction.
☛ Unable to open program.
☛ Error: “File System Error 3006 in JRNLHDR.DAT” on a standalone.
Click Here More Information:
Fix Sage 50 Error 3110
Reasons of Sage 50 File System Error 100
Basically, there are a variety of causes behind the error. Consider the following factors carefully, identify the most definite cause of the error, and then take the necessary troubleshootings to fix the error with ease.
Let’s check out the jotted reasons for the Sage 50 File system error 100:
☛ The file attribute has a Read Only setting
☛ Rather than as a service, Pervasive is currently running as an application
☛ Insufficient Pervasive cache or a damaged Pervasive file
☛ The application is unable to alter the damaged file indicated because it is damaged
☛ The application was put in place outside of the 32-bit Windows program path
☛ In a single company directory, damaged files
☛ UAC (User Account Control) is turned on
Solutions to Resolve Sage 50 File System Error 100
Perform the troubleshooting solutions that are suggested below to easily remove the Error: “File System Error 100 in file Permiss.dat”.
Total Time: 40 minutes
File Attribute is Set to Read Only
☛ Go to the URL that was mentioned in the error
☛ To remove the read-only restriction, do a right-click on the file
☛ Then choose Properties from the Attributes section followed by clicking on the Ok button
☛ Open the software once again if you can
☛ Continue to the following section if you are still receiving the issue.
UAC is Enabled
☛ Sage 50—U.S. Edition icon: select it with the right mouse button
☛ Next, click on the “Run as an administrator” option.
Stop and Restart Pervasive Service
☛ Initially, close Sage 50 on all your computers
☛ Next, locate the Taskbar and then do a right-click on the Taskbar
☛ After that, go to the Task Manager tab
☛ Alternatively, you can make use of the Ctrl + Alt + Delete keys from your keyboard to open the Task Manager
☛ Now, move to the Details tab and look for the w3dbsmgr.exe
☛ Once find then select the w3dbsmgr.exe followed by selecting End by clicking on the End Task option that are available at the bottom
☛ Go to the Services tab and sort the services by the name and find the psqlWGE
☛ Finally, do a right-click on the psqlWGE and then click on the Start button.
☛ After done with the above steps, verify you no longer receive the error message.
Restart Your System
☛ Try to launch the program after a restart
☛ Check to see if the error message has disappeared
☛ Continue to the following section if Sage still won’t launch.
Remove Pervasive and Then Reinstall
In this solution, you have to perform two steps:
Step 1: Remove the Pervasive
☛ Close Sage 50 Accounting—U.S. Edition and make sure every user has left Sage 50 Accounting before removing Actian PSQL Workgroup Engine from the server
☛ To access Programs & Features, hit the Windows + R keyboard shortcut, type AppWiz.cpl in the Open box, and then hit the Ok button
☛ Remove Actian PSQL v13 Workgroup R2 from any of the mentioned versions. (The database engine name will appear as Pervasive PSQL Workgroup Engine if using Sage 50—U.S. Edition 2019 or before)
☛ Press the Windows + R keys once again after closing Control Panel
☛ Click Ok after entering C:\
☛ Delete the pvsw and pvswarch folders if they are present
☛ Remove any file named PSQL_v[version number]_Install.log if it is there
☛ Delete pvsw.log by browsing C:\Windows, if it’s there
☛ Navigate to the C:\ProgramData
☛ Rename the Pervasive Software folder, if it exists, to OldPervasive Software
☛ Alternatively, go to the C:\Program Files (x86) or C:\Program Files
☛ If the folder Actian is there, rename it to OLDActian (If using Sage 50 2019 or earlier, rename Pervasive Software as OLDPervasive Software if present)
☛ Look under the C:\Program Files (x86)\Common Files or C:\Program Files\Common Files directory on your computer
☛ If the folder is there, change it to OLDActian (or OLDPervasive Software Shared if you’re using Sage 50—U.S. Edition 2019 or earlier)
☛ After that, close the File Explorer tab
☛ Type regedit once again by pressing Windows + R and then click on the Ok button
☛ Perform a right-click on the Computer, select Export from the menu, and save the Registry backup file to the computer’s desktop
☛ Navigate to the
☛ HKEY_LOCAL_MACHINE\Software or HKEY_LOCAL_MACHINE\Software\Wow6432Node
☛ Remove Pervasive Software and PEYX489ZK if they are there
☛ At last, close the Registry Editor.
Step 2: Reinstall the Pervasive Manually
☛ Go to the C:\Sage\Sage50_[version] to find the installation folder in File Explorer
☛ To open the PeachtreeInstaller20xx folder, open Program Path or click on it
☛ Double-click on the SetupWorkgroup32_x86.exe (for 2020 and higher versions) or PervasivePSQLv11WGE_x86.msi in the PervasiveMin folder to begin the installation process (for 2019.2 and earlier versions)
☛ After that, click on the “Next” button
☛ Once done with that, click “Next” and then accept and agree to the license agreement
☛ Once again click “Next” after choosing Run as a Service
☛ Now, select the Complete button followed by clicking on the Next button
☛ Finally, choose Install and then click on the “Finish” tab.
Rebuild Data Path
☛ Begin with closing your Sage 50 on all systems
☛ Press the Windows Key + R on the PC that is hosting the data
☛ After typing services.msc, click on the Ok button
☛ If the following services are mentioned, right-click on them and choose Stop
☛ Peachtree SmartPosting ####
☛ Sage 50 SmartPosting ####
☛ Pervasive PSQL Workgroup Engine
☛ Navigate to the computer’s data path
☛ After that, rename the data path directory to OLDDATA
☛ Get the Peachtree###.ini file open
☛ To reflect the renamed directory, modify the Datapath= line’s path
☛ Now, you’re supposed to download and install the Database Repair tool for your Sage 50 version
☛ Choose Run if given the option to run or save the downloaded program
☛ When prompted to continue when the utility opens, select “Yes”
☛ To continue, select Agree from the agreement prompt
☛ Select the button for creating a new local datapath
Note: Before continuing, make sure the software is not already operating on any PCs if you’re executing the utility in a multi-user environment on the server hosting the company’s data.
☛ Select the Ok button
☛ Enter the initial datapath mentioned before in the New datapath column
☛ Again, click on the Ok button
☛ Check to see if the Database Repair Utility says the procedure was successful
☛ Database Repair Utility should be closed
☛ Navigate to the OLDDATA folder
The following folders should be copied and pasted into the new data path that the utility has established:
☛ Forms
☛ Sample
☛ Any of your computer directories
☛ Launch the computer again
Note: Stop the w3dbsmgr.exe process in the task management and launch the Pervasive service if restarting the computer is not an option
☛ After done with that, open the Sage 50
☛ If the program’s activation procedure is not initiated immediately, choose Help >>> Sage 50 Activation >>> Licensing and Subscription options and then proceed as directed to activate the program
☛ Select Open Company from the File menu
☛ Check to make sure your companies are open and functioning properly.
Fix Damaged Files
☛ If it is possible to safely remove and regenerate the file
☛ Restore a backup if the file is a company directory file and cannot be deleted
☛ If the file is a data path file and cannot be deleted, delete it and then run repair.
Try to Program Installed in an Incorrect Directory
Important Note: To install the Sage application, go to the C:\Program Files (x86) if the computer has a program files (x86) directory (x86). You will need to remove and reinstall the software to the proper path if you discover it in a different location.
☛ Initially, uninstall the Sage 50 software
☛ Next, Sage 50 should be reinstalled using the default application path mentioned in the above notification
☛ Check to make sure that there are no issues when you open the company by now.
Conclusion
Well, this is all about Sage 50 File system error 100 and hopefully the above discussed solutions will be helpful for you in rectifying the error. In any case, you stuck or having any further queries regarding the Sage 50 File system error 100, you can reach out the Team of Experts via Sage Helpdesk Team.
Frequently Asked Questions ✍
How Do I Stop and Start Actian/Pervasive Through Command Prompt in Sage 50?
You can do it by applying the steps below:
✔ Press the Windows + R keys simultaneously to open the Run window
✔ Next, type the cmd and then press the Ok button
✔ After the command prompt window open, type sc stop psqlwge followed by pressing the Enter key which will stop the service
✔ Now, type sc start psqlwge to start the service and then press the Enter key which restarts the service
✔ In the end, close the command prompt.
Is There Any Other Way to Remove the Sage 50 File System Error 100?
Yes, you can try expandable file cleanup by creating a new data folder for specific company directory.
What are the Steps Involved in Creating a Clean Data Folder and Expendable File Cleanup to Eliminate the Sage 50 File System Error 100?
Always create a backup of your data before you create a clean data folder and expendable file cleanup and then perform the below steps:
✔ Initially, make sure the system is configured to display hidden files and file extensions
✔ Choose a name for and a location for your data directory
✔ Locate the program path and data path
✔ Go to the data path by browsing
✔ Right-click on a empty space inside the data path, choose New, and then Folder from the menu that appears
✔ Rename the new folder by selecting Rename from the context menu when you right-click on it, then enter the new name
✔ Any name that is specific to the folders that are already present there might be used here
Visit Details: Sage 50 Error File System Error 3 or 95 in File
The following files and folders should be copied from the original company data folder and pasted into your new folder:
⚫ .DAT files
⚫ Version.txt
⚫ KMSKeys.xml
⚫ KeysBackup folder
⚫ ATTACHMENTS folder
✔ With the new folder, launch your company (click Browse on the Open an Existing Company screen, or choose File, Open Company)
✔ Finally, confirm that you can open without any problems.
