We are getting a btrieve error #21 on a workstation trying to run a dos accounting app. It has worked fine until we switched to pervasive SQL 2000. We have the app on the netware 5.1 server with patch 2a on it. Have SQL 2000 on the server and pervasive on the client. We get the error when trying to close month end on an accounting app called AMSI. Can the client or server be adjusted to alleviate this error? I have BTRBox95 loaded also.
Also use Bdosstub loaded on the client and not BTrieve or Brequest loaded. RE: Btrieve Error #21 (Instructor) 20 Jul 01 18:14. Basically Pervasive.SQL 2000 SP2a and 3 (i) enforce what's been in the developers manuals for years - that you have to set up your buffers (in this case the key buffer) correctly - but never enforced by the requesters. 21: The key buffer parameter is too short The key buffer parameter is not long enough to accommodate the key field for the requested index path. Verify that the length of the key buffer equals the defined length of the key specified in the key number parameter. This was necessary to address other reported issues and so the application needs to be updated by the vendor to address this. In the meantime you can probably use the Pervasive.SQL 2000 SP1 requesters which don't enforce proper key buffers until the app vendor gets you and update.
Technical FAQ: Btrieve – Microsoft SQL Server Migration and Deployment MERTECH DATA SYSTEMS, INC Contents Introduction What objects are created on MSSQL? Are there recommended database settings?
Please contact Pervasive Support or Sales and explain the situation and that you need SP1 requesters for the status 21 problem and they will give you a link where you can download them to resolve this temporarily. Also please have the application vendor contact Pervasive Software so we can work with them to fix this issue. Regards, Pervasivite RE: Btrieve Error #21 (TechnicalUser) 17 Sep 01 09:38.
Error: 'Sage 50 cannot be started.' Error: 'Sage 50 cannot be started.' Products Sage 50—U.S. Edition Description. Error: 'Sage 50 cannot be started. Please reboot your computer or click Help for more information'.
Error: 'Sage 50 Accounting could not be started. Please try again. If you continue to have problems, call Customer Support at 1-866-747-3888.' . Unable to open program.
Sage 50—U.S. Edition cannot start Sage 50 cannot be started. Sage 50 Accounting could not be started. My computer restarted and now Sage won't start; no other changes were made. My computer had recent Windows Updates and now the program won't start Cause. Section I: Most common fix.
Restart pervasive on the computer that hosts the data. Follow Article ID 29802: Note: If you do not restart or find the Pervasive PSQL Workgroup Engine in Services, follow Article ID 29921: '. Verify the error is resolved on that computer by opening the program. If you are running Sage on a network and the workstation is still getting the error but the server is not, restart pervasive on the workstation.
Section II: Mapped drive has a red 'X' on it. See Article ID 29732: ' ' Section III: Windows 10 or Server 2012 and higher Updates were completed. Some Windows updates will turn the Pervasive Service off and require manual restart of the service.
See Article ID 29802:. Windows updates may also change your network profile from Private to Public, which can cause the firewall to start blocking Pervasive.
See Article ID 77637: ' Section IV: Computer has Windows version 8, 8.1 or 10 installed Operating System is Microsoft Windows version 8, 8.1, or 10; follow Article ID 36377: ' Note: If you are not sure what version of Windows is installed, see Article ID 47480: ' Section V: Run the Sage Advisor Diagnostic Test to identify common causes. Note: Perform these tests on the computer that gets the error. If all computers in the network have the error, perform these tests on the server. Click Start, All Programs, Sage 50 Accounting version, Sage 50 Resources & Help, Technical Support Utilities, Sage Advisor Diagnostic Tool. Click the Agree button. Select the tests listed below, and then select Run Selected Tests.
When the tests finish, compare your results to the list below and follow the corresponding article if a problem is found. Note: If you need help reading the results, call support at 866-747-3888.NET Error Check: Scroll to the bottom of this test to view the results. If you don't find any.NET errors dated today, you can continue to the next test results.