FAQ #: 137
Error 3000 - System/Server/Network/Interference Error

An error 3000 indicates some form of hardware or networking problem. Unix Servers have historically given a hint as to the type of error using the last 2 digits, such as out of disk space, out of memory, etc. making troubleshooting theses easier and giving a hint as to where to go to fix the problem. Windows Server unfortuneately do not, making Error 3000's very difficult to troubleshoot. Micro Focus (the developlers of AcuCobol - the language in which Answers is written) have provided the following suggestions when encountering error 3000's.

1. Turn off Windows Opportunistic Locking. Refer to the following Microsoft KB article: http://support.microsoft.com/default.aspx?scid=kb;en-us;296264

2. Configure auto-sensing network cards (10/100) to a single speed.

3. Configure anti-virus, anti-spyware, and backup software so your Answers data files and programs are not scanned while they are in use.

4. Troubleshoot the network with a standard sniffer and resolve any problems revealed.

5. Set 'V_READ_AHEAD 0’ in the runtime configuration file.

6. Implement AcuServer for file access which also enhances performance especially in larger batch oriented jobs or searches.

7. Upgrade to the newest AcuCobol Runtime such as 10.00.01 which has some improvements to help reduce Error 3000's coming from Windows networks.

8. Run the following command as an Administrator on the server and any client PC's having this error: net config server /autodisconnect: -1

9. If you are mapping a drive letter on the client PC back to the server via Group Policy insure the mapping policy properties is set to "Update" as opposed to "Replace". Apparently in Windows 10 the "Replace" option disconnects the mapped drive and recreates it every time the Group Policy is applied which can occur several times per day.