SBO Menu Help > Self help > Problems with DI API - robinfeng/beashelp GitHub Wiki

For certain operations, especially for each kind of material entry or item change, the SAP Business One data API is required. Thus beas can get terminated for certain actions.

beas connects with the DI API in two different ways:

beas - Standalone

beas connects with the help of user names and when there is no SAP user, it uses the password/user name that is stored in the configuration wizard. See: Configuration wizard - System If one does NOT log in as a SAP Business One user, a DI API logon can be performed if necessary, e.g for material movement, item changes etc.

SAP Business One - Environment beas connects using a reference that is provided by the SAP UI-API

Problems with DI-API can have various effects, for example: issue material: API-Connect-Error ue_fert_tools... issue material: DI-API-Problem: You have not enough rights (...) Error calling external object function getbusiness object

The user needs in beas the same rights as in SAP Business One. If the user has no right to copy items or to do material postings in SAP Business One, this is also not possible in beas, because functions of SAP Business One are used. Problems can arise in case of time receipts, when journal entries need to be created. The authorizations in SAP Business One are required. For additional information see alternative DI-API-connection, user administration

(in case of connection problems and other error messages) Reason What to do if beas does not start within SAP environment: various error messages, license errors, Program crashes ... restart PC restart PC in secured mode as administrator (In domain: use domain administrator) Windows authorizations not sufficient hmtoggle_plus1 Set user account control to "low" Mandatory to restart PC Logon as Administrator and test Insufficient data access on data base server Test data base access with Administrator account Only SAP 8.82 and older Unstable Installation of DI-API Delete DI-API Change Windows -directory %temp% (enter "%temp%" as directory, delete directory sm_obs_dll Restart Error 2038 hmtoggle_plus1 Deadlock problems

Error message -119 "database type not supported" hmtoggle_plus1 Problems with the DI-API-Installation

Error -119, -126, -129,-131 hmtoggle_plus1 Problems in License files

(-119) database type not supported) (-126) Invalid license server address (-129) Connection with license server failed (-131) connection to license server failed

delete or rename the file b1-local-machine.xml on the local machine

cd "C:\Program Files (x86)\SAP\SAP Business One DI API\Conf" rename b1-local-machine.xml b1-local-machine_org.xml

cd "C:\Program Files (x86)\SAP\SAP Business One\Conf" xcopy b1-local-machine.xml "C:\Program Files (x86)\SAP\SAP Business One DI API\Conf" /Y

Message number 1658707, 2015784 and Ticket 000109194620140120025231 Error -131 hmtoggle_plus1 (-131) Connection to license server failed.

there is no disk in the drive. please insert disk into drive e: Uninstall SAP DI-API and re-install Work around: create drive or directory. Currently the reason is unknown

If the problem has not been solved, the DTW seem no to work. Please refer to your partner or directly to SAP. If the problem occurs only at one work station: check, if Windows needs to be re-installed or replace the PC, please regard Hardware requirements

see Self help Hardware requirements alternative DI-API-connection User administration

If it is possible to connect with DTW but not with beas and if all the above-mentioned attempts have been made, then the problem must be investigated further by the beas support team.

返回 上层