There is a problem with the SM_OBS_DLL folder in the temp folder of the Client Machine (either an upgrade or the user have run window disk cleanup). Do the following to solve the problem:

• 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

See SAP Note 863568 for more information

***

This error can happen for one of two reasons

1:If you by mistake install the add-on on a not supported SAP Business One (Example install B1UP 3.5.0.0 (SBO2007A specific) on a SBO2005A). Please check the install guide / manual of the add-on to determine if the SAP version is supported. If you find that it is not supported you will either need to uninstall and revert to a supported version of Add-on or you need to upgrade SAP Business One to the required version.

2: That you are missing the DI-API - A side effect of missing the DI-API in an installation is that you will see the exact same symptoms from a missing DI as a not correct version. If you determine from the install guide / manual of the add-on that it in fact should be able to run (are supported) then please try to install/reinstall the DI-API on the machine showing the error

This is currently unknown why this error happen. Awaiting SAP Support (Message 471180). The error according to SAP Notes is related to DB2 and Sybase databases, but has only been seen on MSSQL databases. Contact SAP partner or support@(if you can see this please update your browser)boyum-it.com for more information and current status.

***

This is an indication that you tried to run an add-on but the SAP Client failed to register that it started. There can be several reasons for this:

• I get an unexpected error from the .Net Framework during launch. This often indicates an incorrect permission rights. See the "Unexpected error on startup" section for more.
• The add-on was installed on a shared folder (This result in an unexpected Security Exception when running the add-on). Solve this be uninstalling the add-on, and reinstalling on a local drive.
• The machine was simply too slow. Please try again and if running many programs, please try to close all but the SAP Business One Client.

***

UI Connection error that is linked to the user that installed the add-on did not have correct permission to the Windows folder system and the windows Registry. Try the following to solve the problem:

• Log in as a Windows administrator
• Start SAP and go to Administration > Add-ons > Add-on Administration
• Move the B1 Usability Package from the Company Assigned Add-ons to the Available Add-ons
• Restart SAP and re-assign the add-on

If the above does not work try reinstalling the add-on (using a windows administrator).

***

This is often an indication that the add-on has been corrupted or is missing one or more of its files. You should reinstall the add-on to solve this problem.

***

These errors are an indication that the SAP DI-API is not installed or in other ways corrupt. You should try to reinstall the DI-API and 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

***

This error message occurs if an add-on fails in some way before it was able to make the connection it needs to the SAP Business One Client. This is often an indication that there is something with the installed client. You should see the detailed error-message by clicking on Yes (Ja in screenshot) and locate that error in this document. Often a reinstallation of the SAP Client on the machine solves this issue.

This error happens if you try to go to the installation-folder and running the add-ons executable without having a SAP Business One client running. In general you should use the SAP Client to run the add-on (Automatically or start via Administration > Add-ons > Add-on Manager)

DK: Error creating field: fieldname in table: (1 – Intern fejl (1) forekommet)

This error can happen if MS SQL Server 2000 is used and the maximum amount of User defined fields have been added to a table (an MS SQL 2000 limitation). See SAP note 816387 for more detail. You will need to switch to SQL Server 2005 in order to solve this issue or remove other User defined Fields not in use.

***

This error can happen in rare situations during extreme workloads. It can only happen when new metadata are being created (first time installation or activation of and previously inactivated module). Restart the add-on and the problem should disappear (on very slow machines this error can happen 3-4 times in a row)… Keep restarting until the all metadata is created.

In some cases, other add-ons running at the same time can be the cause of this so if restart does not help, then stop all other addons, start our add-on and let it create its data. Once complete you can run the other add-ons as before.

***

This can happen in rare cases where more than one add-on is starting up at the same time. B1 Usability Package version built after March 2007, take special care of this, but if you see it with other add-ons it should be reported to both/all manufacture of the add-ons since this is an indication that SDK guidelines are not followed.

OR

This is a known issue in SBO 8.81 PL05 and PL06… SAP expect it to be fixed in PL07 or 08… See more here: http://www.boyum-it.com/forum/viewtopic.php?f=2&t=272

***

This error occurs if the database logged into does not have a valid posting period. All add-ons need an active posting period, and therefore, you should create a new posting period and restart the SAP client.

***

(DK: Opslagsnøglen, der blev anmodet om, blev ikke fundet I nogen aktiv aktiveringskontekst)

It is currently not known why this error happens. It is in some way related to performance since slow machine tend to get this error more often). The error message is Microsoft Window specific. There is currently no known solution for this error other than restarting (since the error is random and does not happen every time).

This error can occur if you have an incorrect version of the DI-API installed (or not installed at all). You should uninstall the DI-API and reinstall it. After that 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

***

The error can also occur in new a test-addons that was incorrectly not built to x86 (This is not the case for B1UP)

***

This of often an error that follows after another startup error and user has tried to restart the add-on. The problem lies in the SAP License server does not free. After a startup error you should always restart the SAP Client instead of restarting the add-on only.

***

This error happens if an add-on has not been upgraded correctly and the old executeable of the add-on is still in the installation folder. Your should reinstall the add-on. If problem persist please contact the SAP Partner

***

This can happen if you have used a SAP License where the Add-on Compatibility License Component is expired. SAP Have had this component expire two time in the SAP Business One life-cycle (January 2006 and January 2008). If you license is drawn before one of these dates

***

Please see SAP note: 770557 for more information

***

This error indicate that you have an incorrect usage of the SBO_SP_TransactionNotification… We have created this document that helps you find and fix the problem.

SBO_SP_Transactionnotification Problem

This error indicates one of two errors:

1: Running an old B1UP version (lower than 3.5.0.0) in combination with MSSQL Server 2008
If you run a B1UP version lower than 3.5.0.0 and MSSQL server 2008 then this is your problem and 2008 was not supported prior to 3.5.0.0… In such a case you need to upgrade your B1UP to that version or higher. You can download the latest versions here all depending on SAP version and paid maintenance: http://www.boyum-it.com/sbo/

Or

2 : Running MSSQL server 2000 on SBO8.8
If you run MSSQL server 2000 then that is the problem since SBO8.8 does not support running on SQL2000 (Only 2005 and 2008)

If this happen on a Windows XP, Windows Vista, Windows 7 or Windows Server 2003:

• Install the Microsoft .Net Framework 3.5

If this happen on a Windows Server 2008, 2008R2

• In the Server Manager interface, select Add Features to displays a list of possible features
• In the Select Features interface, expand .NET Framework 3.5.1 Features
• Once you expand .NET Framework 3.5.1 Features, you will see two check boxes. One for .NET Framework 3.5.1 and other for WCF Activation. Check the box next to .NET Framework 3.5.1 and click Next.
• In the Confirm Installation Selections interface, review the selections and then click Install.
• Allow the installation process to complete and then click Close.