01. Sorry. An error occurred while making a connection to the client from the add-on: B1 Usability Package. Contact the supplier if this happens again. Do you want to see a detailed error message?
This is the general error of the B1 Usability Package that indicate that something have gone wrong during startup or use. If you see this error you should always see the detailed error message by pressing "Yes", and act on the error.
***
02. Add-on B1 Usability Package is disconnected
This error can have several causes. Here are the most likely:
- The user does not have correct permission writing to the Add-on folder (This is often a problem in a Citrix Enviroment). Give the correct permission in order to fix this (See system requirements)
- The SAP Client incorrectly assumes that the add-on have stopped responding during a long operation.
- The executeable of the add-on is terminated from the task-manager
***
03. Attempted to read or write protected memory. This is often an indication that other memory is corrupt
The exact reason for the error is currently unknown. It have something to do with an incorrect DI-API, but in some cases the problem lies in the databases and not the client itself… If looking at the SDN people have resolved this issue in many different ways indicating that the error might come from multiple issue.. Here are the different ways I know people have solved the problem:
- Some claim that is the uninstall and reinstall the .Net framework the error goes away
- Some claim going to the %temp% folder and removing the SM_OBS_DLL folder solves the problem
- Some claim you need to reinstall the DI-API
- Some claim that you need to reinstall the client
- Some claim that you need to upgrade to a higher patch-level in order to remove the problem
Also SAP have me the following note (Note 1085699) on the error
04. I get an error containing the wording "The server threw an exception" or "HRESULT"
"The server threw an exception" errors are normally an indication that the SDK is an incorrect version or it is unstable so resetting the DI-API in the temp folder is recommended
- In windows, go to Start > Run
- Type in %temp%. and press OK
- In the window that appear locate the SM_OBS_DLL folder and rename it to oldSM_OBS_DLL
- Restart SAP Business One or if the error persists reinstalling the DI-API
The error can happen in other scenarios, but this is the most common.
Should the above not help the best recommendation is to go to the latest stable SAP Business One patch.
HRESULT errors comes and goes with the SAP Patches. During rampup versions there is tons of them while mature versions have less and less (but never to the point where there are none). For that reason the best we can recommend is working with the latest, most mature, version of SAP (the more mature, the better version it is) and B1UP (B1UP versions are built on what we see as the most stable versions)
- Latest versions of B1UP can be found here: http://www.boyum-it.com/sbo/
- Latest version of SAP can be found here: http://service.sap.com/sbo-swcenter
05. Could not load file or assembly'CrystalDecisions.CrystalReports.Engine, Version=...'
This error indicate that the client machine running the add-on does not have the Crystal report Runtime installed. You can download the runtime from http://www.boyum-it.com/sbo/
06. I get an error with the following text: "Unable to cast COM object of type 'SAPbobsCOM.CompanyClass' to interface type 'SAPbobsCOM.ICompany"
This error can occur if the DI-API has been corrupted. Please do the following:
- In windows, go to Start > Run
- Type in %temp%. and press OK
- In the window that appear locate the SM_OBS_DLL folder and rename it to oldSM_OBS_DLL
- Restart SAP Business One
If this does not solve the issue you should uninstall the DI-API and reinstall it. After that redo the steps above.
If you did not find the answer to your issue, please contact support@boyum-it.com
Please write your support-question in English..
NB: When submitting an issue, please provide the following information:
- SAP Version + Patch level
- Add-on Name
- Add-on Version
- Screenshots of issue
- Description on how to reproduce the issue (if possible)
- Does this affect all clients or only one specific?
