Table of Contents
- Office Connector Write
The above applications use the Sage 300 CRE ODBC driver to refresh data in the Sage 300 CRE data set. The Sage 300 ODBC driver works related to the Pervasive data set server to do these activities.
Find-: sage 50 2015 download
When endeavoring to play out the accompanying activities, a mistake is accounted for by the product:
- Office Connector Write – Send Data to Sage 300 CRE
- Figure – Post
- Integrator – Perform Modifications (for Vendors, Commitments, Commitment COs)
After inspecting the mistake log, a section with the accompanying text is shown:
I/O Error. Inescapable status code 46. Admittance to the mentioned document is denied.
At the point when Sage 300 CRE is introduced on a workstation, the Pervasive programming is introduced. With the Pervasive programming introduced, the workstation is fit for working as a Pervasive data set server and is additionally fit for associating with a Pervasive data set server. At the point when a Pervasive data set server gets to the Sage 300 CRE information documents, the records being gets to are locked and viewed as perused as it were. In case the workstation is working as a Pervasive server (and expecting the real Pervasive server is working), the Pervasive server working on the workstation will see that the information documents are perused simply because (they are being gotten to by the real Pervasive server). Any endeavor to compose information will bring about Pervasive status code 46 which shows that a Pervasive information document is perused just and can’t be refreshed.
Read Also-: convert sage 50 to quickbooks desktop 2020
Goal to Cause 1
Accepting the above situation is the thing that is occurring, the issue can be settled by changing the Pervasive setup of the workstation so it works as a workstation and not as a server. To do this, follow these means:
- On the workstation, close all Event 1 and Sage applications (or any applications which may be using Sage information).
- Click the Start menu, explore to the Pervasive PSQL program gathering, and snap PSQL Control Center and Documentation
- In the sheet on the left, explore down to Pervasive SQL/Local Client/Microkernel Router.
- Right-click on Microkernel Router and snap Properties.
- Under Access, uncheck the Use Local MicroKernel Engine box.
- Check the Use Remote MicroKernel Engine box is checked (if not as of now).
- Click OK
Unavoidable status code 46 shows that a document is hailed as perused as it were. If so, clients on different workstations will experience issues composing information from both Sage and Event 1 applications.
Goal to Cause 2
Utilizing Windows Explorer, explore to the organizer containing the Sage 300 CRE information records. Right-click on records in this envelope (and sub-organizers) and affirm that the documents don’t have the Read Only trait checked. Assuming this is the case, uncheck this property.
Unavoidable status code 46 shows that a document is hailed as perused as it were. This can happen assuming that the current client doesn’t have adequate document authorizations to refresh the records..
Goal to Cause 3
Utilizing Windows Explorer, explore to the envelope containing the Sage 300 CRE information documents. Inspect the security settings for the records in this envelope and affirm they are set to permit the client being referred to refresh. Talk with your Sage 300 CRE support agent for help with understanding the necessary record authorizations for Sage information documents.