x Want to participate? Join the group to interact
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 52 replies
  • Answers 2 answers
  • Subscribers 39 subscribers
  • Views 5111 views
  • Users 0 members are here
Browse Forums
Announcements
579
topics
19
replies
General Discussion UKI
2k
topics
5k
replies
Legislation
11
topics
12
replies
Online services
48
topics
68
replies
Processing your payroll
176
topics
307
replies
Sage 50 P11D General Discussion
121
topics
294
replies
Workplace pensions
53
topics
98
replies
Year End Discussion
111
topics
162
replies
Dean

SBDDesktop.exe has stopped working after new 29.03.485 update

SUGGESTED
Posted By

Hi

We are an accountancy company and use Sage Payroll amongst other Sage products in a Remote Desktop Server (RDS) environment, and all has been fine with this for years. We have recently installed the 29.03.485 Payroll update and since then we are getting crashing with “SBDDesktop.exe has stopped working”  when going to the Employee Details section. Everything else is fine and works as its should be, but everytime this section is clicked in any of the 100 companies it crashes, even as administrator on Demo Data

We have been through everything in this article below along with other potential fixes such as renaming logs; it’s been fine for years after many updates, but this one I was told the SBDDesktop.exe was moved in this release.

https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=231201134045467

We have spoken to Sage support, several times, who give you the same answers and wash their hands with it due to it being on a RDS server, beyond this article above.

Eventvwr output from application crash:

Faulting application name: SBDDesktop.exe, version: 16.0.52.0, time stamp: 0x656f38b8

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc000041d

Fault offset: 0xff7c74db

Faulting process ID: 0xae38

Faulting application start time: 0x01da319e6b8d60b2

Faulting application path: C:Program Files (x86)Sage PayrollSBDDesktop.exe

Faulting module path: unknown

Report ID: 97da8fe1-c567-434e-8503-68b00b8dd83c

Faulting package full name:

Faulting package-relative application ID:

Just seems very strange that this update has caused this and only in this section of the software.

If there are any pointers and suggestions to try knowing the above, then this will be great, but feel we have tried everything known at this time. If any others are having same or similar issues, please chime in also. Thanks.

Dean

Parents
  • 0

    @Sage

    Do we have any progression with this at all ? Its been a few weeks since we started having this issue. We installed the update before the new year and had instant issues, its causing a lot of problems for us, all the staff and our customers. 

    Please update us all.

    Thanks

    Dean

Reply
  • 0

    @Sage

    Do we have any progression with this at all ? Its been a few weeks since we started having this issue. We installed the update before the new year and had instant issues, its causing a lot of problems for us, all the staff and our customers. 

    Please update us all.

    Thanks

    Dean

Children
  • 0 in reply to Dean

    Hi Dean,

    This is being actively investigated by the product team. As soon as there are any developments I'll be sure to post an update here.

    Regards,

    Andy
    Sage UKI

  • 0 in reply to Andy Rickeard

    hi Dean 

    any update on this from development team as i have added my comments as well. All companies including MSP's are getting tired of the Sage reply of "We dont support remote installations" line support are being asked to give out.  customers need Sage to be more proactive on this critical issue 

  • 0 in reply to Rod Brown

    Hi Rod

    Not for a while, we were asked to try copying over some DLLs and it helped once or twice but ultimately still really broken and problematic to affect each day, so we had to start putting other plans in plans, forced by Sage and costing lots of money. If i'm honest I think this "try these dlls" was a diversion tactic to buy more time, only done because people were kicking up a fuss on here. I feel this isnt being taken seriously enough, its outrageous. Getting on for 2 and half months without any resolution or anything near, yet they take your support payments and what for? I suggest everyone start looking elsewhere and change software, as they are really not interested IMHO and them breaking their own software and not knowing how to fix it is real eye opening!

  • 0 in reply to Dean

    Hi, we are in the same boat still as well. We have jumped through the same hoops to try to support Sage in helping us, yet they are not listening to what we are saying - for example that security permissions should not be "Everyone"..... and the supposed DLLs and fixes just do not work. We are at the point of having no option but to go elsewhere - Sage are happy to take our money for support but are not supporting us and we, like everyone else, simply cannot operate like this. 

  • 0 in reply to Claire468

    Hi Claire

    Sage seem to think everyone is on a standalone PC with full admin rights, which couldnt be the further from the truth for the vast majority of users. Businesses lock down and secure their networks and users, and rightly so when done properly. Assuming end users can browse and write to the C drive and install patches themselves is ridiculous. Give full control to everyone they say in may articles, place and run this fix from the desktop they say.... ermmmm NO!

    If you are a business to business company Sage (which you clearly are), start writing and supporting your software for business not home users! 

*Community Hub is the new name for Sage City