Error 037 on GLFSPASS GL Fin Stmnt Pass File
Release Date: 09/17/2020
Version: 7.x & Up
Q - Our company implemented NTFS security with our Elliott folder. Our financial manager is not a Windows system admin so she has minimum rights to the DATA folder. We did the procedure in the following article to grant everyone in the group the modify right to all *.DAT files:
She was able to run a financial statement yesterday. Now, after another user (a Windows system admin) ran the financial statement, our financial manager receives the following error:
Error 037 on GLFSPASS GL Fin Stmnt Pass File
What happened?
A - GLFSPASS is the General Ledger Financial Statement Passing File and is used when printing financial statements. It is a DAT instead of a BTR file. DAT file security is directly handled by the OS, and your financial manager by default has minimum rights to that file. As stated in the above KB article, when you first implemented NTFS security, you used the NTFSSEC.bat DATA at the command prompt to grant all users in the Everyone group the right to modify all DAT files. That allows your financial manager to run financial statements. Each time a user runs financial statements, the GLFSPASS.DAT file is re-created (i.e., the old file is deleted and a new file is created.) As a result, the Everyone user group rights go back to minimum as in the DATA folder. But since this file was created by your financial manager, she is the new owner of this file. The next time she runs the financial statement again, she has sufficient rights to override because she is the owner.
This will be fine until the Windows admin user (e.g., the boss) runs the financial statement. Since it is the Windows admin, he/she can override the GLFSPASS.DAT file. However, when your financial manager wants to run the financial statement again, she is no longer the owner of this GLFSPASS.DAT file. Thus, she receives the "Error 037 File access denied" message.
You can solve this problem in the following ways:
- Use NTFSSEC.bat DATA again as documented in the KB article above. You can also do this manually by using Windows Explorer and browsing to the <ElliottRoot>\DATA folder, then right clicking on GLFSPASS.DAT and granting the "Modify" right to the "Everyone" user group.
- Avoid letting the Windows admin run the financial statement and delegate this task to your financial manager only.
- Grant your financial manager full rights to the DATA folder.
- In Elliott 8.6, you can optionally convert GLFSPASS.DAT to a BTR file, and this issue will be resolved.
The permanent solution is resolved in Elliott 8.5 & up release after 05/05/2021. Please see the following KB article:
EMK
Related Articles
Change - Move GLFSPASS.DAT (GL Financial Passing) File to LOG Folder
Release Date: 05/05/2021 Version: 8.5 The General Ledger Financial Passing File (GLFSPASS.DAT) resides in the Elliott DATA folder and is an ASCII file, and therefore is subject to NTFS security issues. During the setup of NTFS security, all *.DAT ...Btrieve Error USE on COP Lock File
Q - Today, for whatever reason, we experienced a large amount of locking issues in the warehouse. Several times today we ran into the problem with printing invoices where we received a message "Btrieve Error USE on COP Lock File," and it stops ...AP1701 Accounts Payable A/P Account File Maintenance
A/P Account File Maintenance Application Overview Of all the accounts in your General Ledger, only some will be affected by A/P. They are: One or more cash accounts; One or more A/P accounts; A discount taken account (this is a revenue); Several ...ARCUSMNT Accounts Receivable Customer File Maintenance
Customer File Maintenance Application Overview The Customer File is a very important file. It stores the basic information about every customer you do business with. Almost every major application in the A/R package uses the Customer file to ensure ...Btrieve Error 161 on Password File When Starting Up Elliott
Q - We are receiving an Error 161: The maximum number of user count licenses has been reached. This happens to all users when starting up Elliott. We have rebooted all office computers and the PSQL server. There is no one is in Elliott. Yet we are ...