# Sage 50 SBD Desktop Error

The Sage 50 SBD Desktop Error is a tough choice to make as the issue could arise for different users under different circumstances. There are several ways that the users who are facing the SBD Desktop error in Sage 50 can follow to fix the issue easily.

Usually, this issue occurs not because of anything that the user has done purposefully, but because of any configurations on the user’s workstation, any issues in the company files, or because of any security tools that the user might have installed on their workstation.

## Possible Causes that Cause the SBD Desktop Error in Sage 50

Several reasons would cause the SBD Desktop error to arise in Sage 50.

• When some of the Sage account files need to be refreshed. If the Sage account files are not refreshed, then this issue might arise for users.
• Another cause Sage 50 is that it could be that the user is using the Bitdefender Total Security 2015 or the Security Defender antivirus software on their workstation.

## Resolution of Sage 50 SBD Desktop Error

None of these ways requires the users to have any kind of technical fluency, as these methods are straightforward to comprehend and follow. That is the reason that this article contains more than one method that the user can use to be able to fix the Sage 50 SBD Desktop Error. Following are the ways the user can fix the SBD Desktop error in Sage 50.

### Solution 1- Run As Administrator

This is the most basic way that has proved to fix the Sage 50 SBD Desktop Error. To conduct this process successfully, the only thing that the user needs to do.

• That the user needs to right-click on the Sage application shortcut that is on the user’s workstation’s desktop.
• After right-clicking on the shortcut, the user will see a small menu open up in front of them.
• From that menu, the user is required to select the option titled ‘Run as administrator.
• Clicking on this option will run the Sage application on the user’s workstation with administrator privileges. It should fix the SBD Desktop error in Sage.

### Solution 2- Logging in with a different username

The second method that the user can make use of is that they can try logging into the user’s company data by making use of a different username-password combination.

• For instance, the user can log in using the manager’s credentials.
• This typically fixes the SBD Desktop error in Sage.
• If it does fix the error, then the user should also either create a new username, or the user must delete the criteria files of the user that has been affected because of this error.

### Solution 3 – Renaming the Sage.ini File

Another thing the user can try so they can fix the Sage 50 SBD Desktop Error is that the user can try renaming the ‘sage.ini’ file. Here’s how the user can rename the ‘sage.ini’ file.

• The user needs to press the Windows key and the ‘E’ key together. Doing this will open the File Explorer application on the user’s workstation.
• After opening the File Explorer on the workstation, the user must navigate to the following data path: C:\ProgramData\Sage\Accounts.
• After the user finds themselves in the C:\ProgramData\Sage\Accounts data path, the next thing that the user needs to do is that the user needs to locate the file titled ‘sage.ini’, and once found, the user must right-click on the file.
• From that menu, the user needs to select the option titled ‘Rename’. The user will need to rename the file as ‘sage.old’.
• Once the user has successfully renamed the file, the user will need to reopen the software to see if the issue still persists.

### Solution 3- Renaming the Sage.usr File to Sage.old

Before the user can proceed to rename the sage.usr file to sage. old, it must be kept in mind that the sage.usr file must be renamed if and only if the user has their serial number and activation key to hand. Here’s how the user can rename the ‘sage.usr’ file to ‘sage.old’.

• The user needs to press the Windows key and the ‘E’ key together.
• After opening the File Explorer on the workstation, the user must navigate to the following data path: C:\ProgramData\Sage\Accounts\xxxx. Here, ‘xxxx’ denotes which year’s version of Sage the user has installed on their workstation. For instance, if a user has the 2019 version of Sage, then the corresponding data path would be C:\ProgramData\Sage\Accounts\2019.
• After the user finds themselves in the C:\ProgramData\Sage\Accounts\xxxx data path, the next thing that the user needs to do is that the user needs to locate the file titled ‘sage.usr’, and once found, the user must right-click on the file.
• From that menu, the user needs to select the option titled ‘Rename’. The user will need to rename the file as ‘sage.old’.
• Once the user has successfully renamed the file, the user will need to reopen the software to see if the issue persists.

### Solution 4 – Renaming the License Files

This solution pushes the user in the direction of renaming the license files on the user’s workstation. The user will find the license files if and only if the user has run the software on that workstation. Here’s how the users can proceed to renaming the license files.

• That the user needs to close the Sage Accounting application.
• Now, the user must rename the SDK Licence folder. The data path to the folder will be along the lines of C:\Program Data\Sage\SDK Licence. Once the user has navigated to the data path, the user is required to change the name of the folder so that the data path now looks like C:\Program Data\Sage\SDK Licence OLD.
• After renaming the folder, the next thing that the user needs to do is that the user needs to browse to the following location on their workstation: C:\Program Data\Sage\Accounts\<>
• Once the user has navigated to the aforementioned data path, the user must look for the sage.usr file, and once found, the user should delete this file from the folder.

It should be noted here that the user might also be required to delete the account number from the registry. Here’s how users can proceed if they have to delete the account number from the registry.

• The first thing user needs to press the Windows key and the ‘R’ key together. Doing this will open the Run command application on the user’s workstation.
• In the Run command application, the user needs to type in Regedit, and then the user needs to press the ‘OK’ button.
• Now, the user will have to locate the HKEY_CURRENT_USER\Software\Sage\Line 50 from the pane on the left side.
• After locating KEY_CURRENT_USER\Software\Sage\Line 50 from the pane on the left side, the next thing that the user must do is that the user must double-click on the AccountNumber, and then the user must delete all of its contents and press ‘OK’.
• Now, the user can press ‘File’, and then they can press ‘OK’.
• Once the user has successfully deleted the contents, the user will need to reopen the software to see if the issue persists.

## Preventing the SBD Desktop Error in Sage 50 from reoccurring in Bitdefender

This solution can be applied to prevent the SBD Desktop Error from reoccurring in Bitdefender. It can also be applied if the user is getting the same error message even while they are using a different antivirus or antimalware software. Here’s how users can prevent the SBD Desktop Error from reoccurring in Bitdefender:

• The first thing that the user needs to must open the Bitdefender application.
• The user then needs to click on ‘Protection’, followed by clicking on ‘Antivirus’, and finally, ‘Exclusions’.
• After that, the user needs to click on ‘Excluded Processes’. In the ‘Excluded Processes’ section, the user must further click ‘Add’.
• Now, the user must browse a particular file. The data path to the file and the filename may be different according to the version of Bitdefender that the user is using. Here are the names of the files and the data path concerning the different versions of Bitdefender:
• V27 (32 bit): [Sage Accounts program directory]\SBDDesktop.exe.
• C:\ProgramFiles\Sage\AccountsServiceV27\sg50svc_v27.exe;
• C:\Program Files\Sage\AccountsServiceV27\sg50CtrlSvc_v27.exe
• V27 (64 bit): [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV27\sg50svc_v27.exe
• C:\Program Files (x86)\Sage\AccountsServiceV27\sg50CtrlSvc_v27.exe
• V26 32 bit: [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV26\sg50svc_v26.exe
• C:\Program Files\Sage\AccountsServiceV26\sg50CtrlSvc_v26.exe
• V26 (64 bit): [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV26\sg50svc_v26.exe
• C:\Program Files (x86)\Sage\AccountsServiceV26\sg50CtrlSvc_v26.exe
• V25 (32 bit): [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV25\sg50svc_v25.exe
• C:\Program Files\Sage\AccountsServiceV25\sg50CtrlSvc_v25.exe
• V25 (64 bit): [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV25\sg50svc_v25.exe
• C:\Program Files (x86)\Sage\AccountsServiceV25\sg50CtrlSvc_v25.exe
• V24 (32-bit):
• C:\Program Files\Common Files\Sage SBD\SBDDesktop\v14\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV24\sg50svc_v24.exe
• C:\Program Files\Sage\AccountsServiceV24\sg50CtrlSvc_v24.exe
• V24 (64-bit):
• C:\Program Files (x86)\Common Files\Sage SBD\SBDDesktop\v14\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV24\sg50svc_v24.exe
• C:\Program Files (x86)\Sage\AccountsServiceV24\sg50CtrlSvc_v24.exe
• V23 (32 bit):
• C:\Program Files\Common Files\Sage SBD\SBDDesktop\v14\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV23\sg50svc_v23.exe
• C:\Program Files\Sage\AccountsServiceV23\sg50CtrlSvc_v23.exe
• V23 (64 bit):
• C:\Program Files (x86)\Common Files\Sage SBD\SBDDesktop\v14\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV23\sg50svc_v23.exe
• C:\Program Files (x86)\Sage\AccountsServiceV23\sg50CtrlSvc_v23.exe
• V22 (32 bit):
• C:\Program Files\Common Files\Sage SBD\SBDDesktop\v12\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV22\sg50svc_v22.exe
• C:\Program Files\Sage\AccountsServiceV22\sg50CtrlSvc_v22.exe
• V22 (64 bit):
• C:\Program Files (x86)\Common Files\Sage SBD\SBDDesktop\v12\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV22\sg50svc_v22.exe
• C:\Program Files (x86)\Sage\AccountsServiceV22\sg50CtrlSvc_v22.exe
• V21 (32 bit):
• C:\Program Files\Common Files\Sage SBD\SBDDesktop\v12\SBDDesktop.exe
• [Sage Accounts program directory]\sg50svc.exe
• [Sage Accounts program directory]\sg50CtrlSvc.exe
• V21 (64 bit):
• C:\Program Files (x86)\Common Files\Sage SBD\SBDDesktop\v12\SBDDesktop.exe

[Sage Accounts program directory]\sg50svc.exe

[Sage Accounts program directory]\sg50CtrlSvc.exe

• After successfully finding the file, the user can press on the option titled ‘Exclude Program’.

## Preventing the SBD Desktop Error from Reoccurring in Security Defender

• The first thing that the user needs to do to prevent the BD Desktop Error from reoccurring in Bitdefender is that the user must open the Bitdefender application.
• After opening the application, the user will need to add the following files to the list of exclusions based on the version of Security Defender that they have:
• V27 (32 bit): [Sage Accounts program directory]\SBDDesktop.exe.

C:\ProgramFiles\Sage\AccountsServiceV27\sg50svc_v27.exe;

C:\Program Files\Sage\AccountsServiceV27\sg50CtrlSvc_v27.exe

• V27 (64 bit): [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV27\sg50svc_v27.exe
• C:\Program Files (x86)\Sage\AccountsServiceV27\sg50CtrlSvc_v27.exe
• V26 32 bit: [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV26\sg50svc_v26.exe
• C:\Program
• Files\Sage\AccountsServiceV26\sg50CtrlSvc_v26.exe
• V26 (64 bit): [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV26\sg50svc_v26.exe
• C:\Program Files (x86)\Sage\AccountsServiceV26\sg50CtrlSvc_v26.exe
• V25 (32 bit): [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV25\sg50svc_v25.exe
• C:\Program Files\Sage\AccountsServiceV25\sg50CtrlSvc_v25.exe
• V25 (64 bit): [Sage Accounts program directory]\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV25\sg50svc_v25.exe
• C:\Program Files (x86)\Sage\AccountsServiceV25\sg50CtrlSvc_v25.exe
• V24 (32-bit):
• C:\Program Files\Common Files\Sage SBD\SBDDesktop\v14\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV24\sg50svc_v24.exe
• C:\Program Files\Sage\AccountsServiceV24\sg50CtrlSvc_v24.exe
• V24 (64-bit):
• C:\Program Files (x86)\Common Files\Sage SBD\SBDDesktop\v14\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV24\sg50svc_v24.exe
• C:\Program Files (x86)\Sage\AccountsServiceV24\sg50CtrlSvc_v24.exe
• V23 (32 bit):
• C:\Program Files\Common Files\Sage SBD\SBDDesktop\v14\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV23\sg50svc_v23.exe
• C:\Program Files\Sage\AccountsServiceV23\sg50CtrlSvc_v23.exe
• V23 (64-bit):
• C:\Program Files (x86)\Common Files\Sage SBD\SBDDesktop\v14\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV23\sg50svc_v23.exe
• C:\Program Files (x86)\Sage\AccountsServiceV23\sg50CtrlSvc_v23.exe
• V22 (32 bit):
• C:\Program Files\Common Files\Sage SBD\SBDDesktop\v12\SBDDesktop.exe
• C:\Program Files\Sage\AccountsServiceV22\sg50svc_v22.exe
• C:\Program Files\Sage\AccountsServiceV22\sg50CtrlSvc_v22.exe
• V22 (64-bit):
• C:\Program Files (x86)\Common Files\Sage SBD\SBDDesktop\v12\SBDDesktop.exe
• C:\Program Files (x86)\Sage\AccountsServiceV22\sg50svc_v22.exe
• C:\Program Files (x86)\Sage\AccountsServiceV22\sg50CtrlSvc_v22.exe
• V21 (32 bit):
• C:\Program Files\Common Files\Sage SBD\SBDDesktop\v12\SBDDesktop.exe

[Sage Accounts program directory]\sg50svc.exe

[Sage Accounts program directory]\sg50CtrlSvc.exe

• V21 (64-bit):
• C:\Program Files (x86)\Common Files\Sage SBD\SBDDesktop\v12\SBDDesktop.exe

[Sage Accounts program directory]\sg50svc.exe

[Sage Accounts program directory]\sg50CtrlSvc.exe