Showing results for 
Search instead for 
Did you mean: 

DI Server/API Encounters XCE208 busy and OBServerDLL Errors 2-3 Times Weekly

0 Kudos

My Di server encounters errors quite often, about 2 to 3 times a week.

Error message displayed by DIProxy_0.log
April 17, 2024 8:58:39 AM initialized
Critical: Unable to get HTTPS port, so will try again: Address already in use: bind (port: 2098)
April 17, 2024 8:58:42 AM initialized
Fatal: Unable to get HTTPS port, so will try again: In use: bind (port: 2098)
April 17, 2024 9:31:38 am applyException
Critical: Number of DI errors that have occurred: 0
April 17, 2024 9:31:38 AM applyException
Serious: Abnormal! XCE208 resource is busy


Apr 17, 2024 9:49:14 AM$AbstractPayloadAction getReplyPayload
Serious: Abnormal! COM exception encountered:
When calling: Add
Description: The server threw an exception.

at (native method)
at (unknown source)
at (Unknown source)
Located at (Unknown Source)
Located at (unknown source)
at sun .reflect.NativeMethodAccessorImpl.invoke0(native method)
at sun.reflect.NativeMethodAccessorImpl.invoke( at
Located at
Located at method
at com.


at .b1i.adapter.dia.JCOManager.dispatch(

Apr 17, 2024 9:49:14 AM$AbstractPayloadAction getReplyPayload
Critical: An error occurred while executing the DI call with the payload:

Then my Windows Evenlog
OBServerDLL_1000170.dll ERROR

This situation will cause my data to be unable to be synchronized to sap.

But check the port usage and confirm that no other program is occupying 2098
Or I need to manually restart SAPB1iDIProxy2098 SAPB1iDIProxy both services to fix it immediately.
Data can be synchronized correctly

May I ask what is going on and how to deal with it to reduce the occurrence of di server errors?

View Entire Topic
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi allenzhang

The "XCE208 Resource is busy" means that there's no DI Proxy available to serve a scenario step request. You can increase the number of DI Proxies in a DI Proxy Group to try and reduce this.

For how to setup multiple DI Proxies and DI Groups, please refer to section 9 in NOTE 2130388.

For memory allocate to TOMCAT, you can check Maximum memory pool allocated to B1i (tomcat):  ..\SAP\SAP Business One Integration\IntegrationServer\Tomcat\bin\tomcat8w.exe and find the field on Java tab and increase the Maximum memory pool  value.

Restart SAP Business One Integration service after this.

Kind Regards
Nidhi Singh
SAP Business One Support


0 Kudos
Thank you nidhisingh14 for your reply Then I would like to ask what is the possible reason why OBServerDLL crashes from time to time? Does it have anything to do with the setup multiple DI Proxies and DI Groups and memory allocate to TOMCAT you suggested adjusting? Because I currently have two proxies, this problem often occurs during off-peak hours, so it doesn’t feel like a real busy problem. If you have more ideas, please help me. Thank you.