Sorry Update Version 2024Update2 on a Terminal Server 

Yes I have the same issue - only one user can login at time to payroll - the second user gets the same error message.  We are also using Terminal Server with 2 users needing to do payroll.

Hi Natascha Booyens  & Delza Heering ,

Can I ask you to test something?  Please log in with the user that can log in at the moment.

Then navigate to Setup, Company Parameters.  Uncheck Employee Verification check box.   Click on OK.

Check if the other users can now log in.

Let me know if it makes a difference?

Daurayne
Beyond Payroll 365
Tel: 010 822 7799
Email: [email protected] 
www.beyondpayroll365.co.za

Daurayne, thank you I will test it just now and let you know. 

I have tried but this is per company and did not work. 

I am looking to do this next fix. I think it have something to do with the SAGE connected services. I have been working with SAGE support for the past 6 hours and no one can fix this. When I get it fixed, I will let you know. 

1.  Close Payroll 

     2. Stop Sage connected services through task manager

     3. Zip up the SCServices.vdb4 file and delete the SCServices.vdb4 file which can be located in the following locations -   C:\Users\Username(User that is logged in at that time)\AppData\Local\Sage Connected Services\Data

     4. Uninstall and reinstall Sage Connected Services.

Open Payroll 

Daurayne_Bp365 Delza Heering 

It could definitely be SCS.

But the -214 error is pretty broad.  When does the error pop up?  Is it after the enter Password screen or before it?  

 After the we enter the Password when payroll is open, and you open the company you would like to work in enter the password and everything stops working. 

Delza Heering Daurayne_Bp365 I fixed the problem. The Problem is that the SAGE Connected Services don't run on all the profiles on the Terminal Server, so you have to manually start the SAGE Connected Services on each user server profile then they log in to work. So, you have to create a shortcut to SAGE Connected Services on each user profile on the Server they must run the program before they open Pastel then everything works 100% Delza Heering I will help you to fix this just reply to this message. I will not charge you it will be for free. 

Thanks guys thought it might be that - Will try this thank you!!!

I have tested it on my Servers, and it is working 100%. If you need help let me know. Please let me know. Thanks

Hi,

I feel like your solution is not a permanent fix, so I will post a permanent fix.

Stop all Sage Notification Service processes

Delete folder Sage Connected Services(will not delete if all Sage Connected Notification processes are not killed) for each user who uses Payroll under Appdata>Local.

Uninstall Sage Connected Services.

Download a fresh copy of Sage Connected Services payrollupdate.sagesouthafrica.co.za/.../
Install Sage Connected Services

Reboot Server(Optional)

Log in with one of the users who use Payroll.

Open Payroll(No need to start Sage Service, it will start after reboot or reinstallation)

Payroll will run longer at 50% as it recreates the Sage Connected Services Folder under Appdata>Local

Payroll and Sage Connected Services are now 100% after this.

Second Run of Payroll will run faster and not sit at 50%.

No need to start the Sage Connected services(this will be an administration and User nightmare for them to start when they log in)

Hope this helps anyone with this issue.

Tried this - still the same issue

Hey Delza Heering 

Our community has offered several solutions, but it appears that none of them have resolved your problem. I recommend reaching out to the support team for Pastel Payroll at [email protected] for further investigation.

Sharon

Hi Delza,

Please use Sage Connected Services 2.3, do not use 3.0.6.

Let me know if you need a link, you can also use Program data to find previous msi packages for Sage.

This also works 100%.