Sage 50 UK Troubleshooting

Failed to connect to Sage 50 UK: Username is already in use

This error message indicates that Sage is preventing Zynk from logging in because it believes the Zynk user is already logged in.

This can occur for a number of reasons, such as:

• Another user could be using the same account, such as if Zynk is set to use the MANAGER user account.
• Another instance of the workflow may be running, such as if you are trying to run the workflow manually while an automatic run is taking place.
• A failure of Sage Remote Data Access (RDA) or the Sage Data Services has prevented a previous connection from being disconnected.

Before continuing, it should be investigated whether or not the account is legitimately in use, as forcibly disconnecting a user could have unintended consequences.

Multiple users using the same account

The simplest way to check if someone else in your office could be using the same account as Zynk is to see who else is logged in to Sage 50. If someone else is found to be using the same account, asking them to log out should resolve the issue.

To avoid this situation reoccurring, it's advised to make a Sage 50 User Account exclusively for Zynk's user.

Information on creating a new user account can be found on Sage's Knowledgebase and information on entering the new credentials into Zynk can be found in our Connecting to Sage 50 UK documentation.

Running the workflow manually while a scheduled run is taking place

There are two ways to check if an automatic run is currently taking place.

Windows Task Scheduler

By opening Windows Task Scheduler and navigating to Task Scheduler Library -> Zynk you should be able to see the status of all workflows.

A Status of "Ready" indicates that the workflow is idle and a status of "Running" indicates that a workflow run is currently in progress

Within the Zynk UI

The status of a current run can be determined by accessing Zynk and opening the Workflow(s) in question.

In the history tab, the top record will show the current run and it's status, with a Result of "Unknown" indicating that the workflow is yet to finish.

Data Services and Remote Data Access (RDA) Failures

The most common cause of the Username is in Use error is when either the Sage Data Services or Sage Remote Data Access Service has failed while Zynk is running, preventing the user account from being logged out in a timely fashion.

The biggest indicator of this is a workflow run that is taking an unusually long time to finish, such as a workflow that normally takes 5 minutes taking in excess of an hour. This can also be reliably inferred if you are aware of other users experiencing Sage issue around the same time.

Resolving Username is in Use Error

Once you are confident that no legitimate operations are happening, removing the Zynk user from Sage can be done in one of two ways.

Removing the user manually

The safest and easiest way to remove the user is to remove the user from the Active Sessions list.

This can be done by logging in to Sage as the MANAGER user account and navigating to Settings -> User Management -> Active Sessions which will present a full list of users currently connected to Sage.

Selecting the user account that Zynk uses and pressing "Remove" will allow Zynk to connect anew the next time the workflow runs.

Logging in as the effected user

If you no longer have access to the MANAGER account in Sage, you can log the Zynk user out by logging in to Sage as the same user.

After entering the log in details, you will receive a dialogue box stating that the user account is already logged in at ZYNK_SAGE_APP and if you would like to terminate the previous session.

Confirming this dialogue will end the previous session and allow new connections to be initiated.

Task Scheduler

If your are receiving the Username is in Use error because the Sage Data Services or Remote Data Access failed, you may also need to inform Windows Task Scheduler that the previous run has finished.

This can be done by opening Window Task Scheduler, navigating to Task Scheduler Library -> Zynk and ending any invalid runs by right clicking on the Workflow entry and choosing "End"

What does the Exclusive Mode error mean

If you receive the below error in Zynk, this indicates that one of your Sage users is in an "Exclusive Area" of Sage 50.

Program is in exclusive mode. Log on cannot proceed
at System.RuntimeType.ForwardCallToInvokeMember(String memberName,
BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData&
msgData) at SageDataObject120.IWorkSpace.Connect(String Path, String Usr,
String Psw, String Unique) at Zynk.Sage.Sage50.Sage50Base.Connect()

Most often this is due to a restore or backup taking place, but can be caused by a number of different Sage processes, outlined in the Sage Help Article for Exclusive Program Areas

This error can be resolved by either waiting for the operation to finish, or asking the user accessing this area to log out temporarily.

What do I do if my Sage 50 information changes

If you have changed the location, version or login information (username or password) of your Sage 50 data you will have to update these settings in Zynk.

Instructions for entering the new information can be found in our Connecting to Sage 50 UK article.

Using ODBC driver with Microsoft Office applications

More information on linking the ODBC driver to Microsoft Office applications can be found on Ask Sage