Throughout this page, Sage 200 would be referred to as Sage and Microsoft SQL Server would be abbreviated to MSSQL.
Sage relies on Microsoft SQL Server to store data entered. In order for the Open Accounting Connector application to retrieve data a connection to the datasource (MSSQL) is required, some IT assistance may be required to acquire these.

Please follow steps below to configure your Sage company to the Open Accounting Connector application.
Click each step below for a pictorial view

Now that the application is installed please double click the Open Accounting Connector desktop shortcut. The Open Accounting Connector may attempt to automatically detect which software you have installed - if installed on a Server you may have to select Sage 200 from a list. As detailed in the Open Accounting Connector Check List section above, particular Microsoft SQL Server (MSSQL) credentials are required to connect successfully. SQL Server name (and instance name if any): This is the Server name that MSSQL is installed on within your network. In addition the instance name should be known. If any of these are unknown, please open Sage 200's "System Administrator" and navigate to the Company page. Please see the Company page to locate the Server name. User / Password: These must be SQL Server authenticated logon details and not Windows Credentials. A default 'sa' user can be used to connect, alternatively a Read Only user can be used (or created) against the Sage 200 Company database. Database Name: If unknown this can be found in the "System Administrator" software installed on the server holding Sage 200. Please see the Company page to locate the Database name. Click 'Test Connection' when the form is complete. The connection would successful if all credentials are correct and will prompt which is incorrect. A connection is now successful to your Company, data can be retrieved. Click the 'Extract' button to submit your first data load.

Your Open Accounting Connector application may be setup to retrieve data automatically at a predefined schedule, this functionality relies to be logged on at the scheduled time. Due to the nature of Servers, it may rarely be logged into. So if the Open Accounting Connector application is installed on a Server, extractions may not always perform automatically. To enable this feature a task scheduler would have to be created.
To create a task scheduler please go to the installation path of Open Accounting Connector, usually held in C:\Open Accounting Connector_xxx\ Open the taskSchedule.bat file and follow the instructions.

An MSSQL user can be created dedicated to the Open Accounting Connector application. This user should be created and mapped to the desired database with db_readonly rights as a minimum requirement.
Click each step below for a pictorial view

Open Microsoft SQL Management Studio and connect to the Database Engine. Now expand the Security folder in the Object Explore and right-click Logins to create a New Login. Within the General page please create a username with SQL Server Authentication Remove the defaulted Enforced password policy (so the user doesn't expire). Now navigate to the User Mapping page to give the user rights to the database. Tick the database name in the top half panel, and give the user db_readonly rights (as a minimum requirement) in the bottom half panel.

If the error below appears, the MSSQL username and/or password is incorrect ? remember the credentials required to Sage 200 is the MSSQL logon user and password not that of Sage 200. Also ensure that if not the sa user, this user has DB_Reader (as a minimum) rights and is mapped to the Company database.

If this error appears the Server isn?t able to be located. This could be due to a number of reasons.

• The server might be turned off
• The server may not be on the same network as the same PC Open Accounting Connector is running from
• The PC Open Accounting Connector is running from may not have access to that server
• The server may have an instance that the database (that Sage 200 is using) is located on.
• The server may be using a different TCP/IP
• There might be spelling error

IT assistance may be required with this type of error.

If the error below appears the database name is incorrect or the instance name is incorrect. Please double check these - additionally Sage 200's System Administration holds this info IT assistance may be required with this type of error.