SAP DI-API Error "-132 - Error during SBO user authentication" [SBO 9.3 or Higher Only] – Boyum Help Center

New to B1 Usability Package? Check this 5-minute overview for easy SAP Business One Automation, Reporting, Screen Customization, and more!

What is the reason for this error and how to fix it?

There can be multiple reasons for this Error as this is SAP's general Di-API error in SAP 9.3 (In SAP 9.2 This error is instead reported back as error code "-10" or "-4008"]

Possible Reason	How to Solve
Wrong username/password You entered a wrong SAP username and/or Password (or the user do not exist anymore)	Re-run server-component and double-check that user exists and username/password is entered in the right casing (if in doubt try and log into the SAP B1 Client with the same credentials)
IP-Adress Instead of given name or vice versa As servername, you have entered an IP Address but in the SAP System Landscape Directory (SLD) it is entered with a given name (or vice versa)	Log into the SLD and note down the method used (IP or given name). Then re-run the server-component and entered the server name in exactly the same manner as SLD
The Server name is wrong Server name of where the SAP Server Tools are installed is incorrect (most often cause of this is rename of the server)	Re-run the server component so it can know the new Servername
Server name without a port [HANA Only] When you enter the server name for a HANA System you need to include the port (normally 30015)	Re-enter the server name with the port in the server-component
Incorrect Server name casing [HANA Only] HANA Only: When you enter the server name for a HANA System the server name is case-sensitive	Double-check that you have the right server name casing
Incorrect Database casing SAP Database names are case-sensitive so if your database is called 'SboDemoUS' you change the name of it to example 'SboDEMOus' (different casing) you can get this error from the DI-API	Re-run the server component so it can know the new database name
Windows Service "SAP Business One Server Tools Service" is not running This service runs the SLD, and if not running you can't connect to the SLD	Check Windows Services that the service is running on the machine running the server-component
Wrong configuration of Tomcat Server This is due to a misconfiguration of the Apache Tomcat Server.	Please see SAP note: https://launchpad.support.sap.com/#/notes/2526992 on how to fix it
OBServer folder content is incorrect. (mix of Dlls or missing DLL's) This could occur if the OBServer content is downloaded to the temp folder or OBServer not updated as per the SBO-COMMON version.	Please follow this link in order to troubleshoot the problem
No access to the OBServer folder When the company connection is made, access to the %temp% or the SAP\SAP Business One DI API\OBServer is required for the user running the application.	Check that the permissions to the folder structures are set properly.
Slow File I/O When the company connection is made, access to the temp or the SAP\SAP Business One DI API\OBServer is required for the user running the application.	Monitor the system performance while creating the connection.

Video how to fix:

Related articles