Problem with Sage Payroll 2012 / 2013 v18 on Terminal / Remote Services

Problem with Sage Payroll 2012 / 2013 v18 on...

Didn't find your answer?

Many practices are now using Terminal Services to support remote users.

We have just encountered a problem with the latest Sage Payroll 2012 / 2013 v18 Year End update.

It runs fine on local PCs accessing data from the local hard drive and across a network.

However if you are using Terminal Services you might find the response is so slow that the program is unusable.

Problem

1. You login to the software and are prompted to upgrade the data to the latest version.

The process runs without a problem.

2. You login to the company again and you are returned to the list of companies and the 'egg timer' appears.

3. The program appears to hang, but if you wait for a few minutes it will advance to the next screen. It works, but is virtually unusable.

Solution (Subject to end user this morning)

1. On Terminal Server, go into Control Panel - Administrative Tools - Data Sources (ODBC)

2. On the System DSN Tab look for Payroll32 and press configure

3. Press the Options button and change the buffer size from 2048 to 4096.

4. Depending on your system security, you might need assistance from your Network Administrator.

We tried this twice last night on a number of payrolls and it appears to work, but we will hear from the end users later.

Sage was acknowledging this as a problem on Tuesday and I imagine their helpdesk will start to issue this guidance today and I assume a patch to follow.

I hope that helps someone.

Paul Kelly

www.kellysolutions.co.uk

Replies (3)

Please login or register to join the discussion.

avatar
By JBwho
05th Apr 2012 14:14

Problem with Sage Payroll 2012 / 2013 v18 on Terminal / Remote S

We are having an absolute nightmare with this and Sage seem completely unable to help.  We have been unable to process end of year, have a short week next week with 300 plus staff to pay and Sage have "restored" our system so we now have to rerun the payroll for the last two weeks before we can even begin this one.

We have literally been on the phone to them (or at least holding on the phone) for more than 10 hours over the past few days and we are no further foward.  

Rejoining the dreaded queue after each failed attempt because they refuse to give us a direct line is crazy,  "Go join the Sage queue" has become our semi-polite "f-off"

They haven't mentioned the above solution so I have just asked our IT guy to look at it for me.

If it works, I will be eternally grateful to you and I will demand the coat buttons off Sage Executives for the significant costs I have incurred. 

 

Thanks (0)
avatar
By paul.k2
05th Apr 2012 21:31

Update to my original post

I gave the same information to another colleague in advance of his TS upgrade. However his upgrade was okay, so there might be more to this than my solution.

Since applying the solution we haven't had a problem.

 

Paul

www.kellysolutions.co.uk

 

Thanks (0)
avatar
By paul.k2
26th Apr 2012 15:36

More problems - Internet Submissions

These were taking up to 25 miniutes, had to make the buffers 8192

Thanks (0)