Skip to Content
Nov 02, 2018 at 06:57 AM


934 Views Last edit Nov 02, 2018 at 08:45 AM 2 rev

Dear All,

About by Application:

We have developed & deployed a WEB-Application (using ASP.NET), which interact with DI Server for concurrent POSTING of SAP B1 transactions (See below).

1. Goods Receipt

2. Goods Issue.

3. Goods Receipt PO.

4. Goods Return

5. Inventory Transactions (BIN & Warehouse).

6. Delivery.

7. Sales Picking.

A part from above, we are updating many UDOs via DI SERVER.

My web application is used by many SAP B1 users (around 60 Users), Who submits above transactions at periodical interval of 4 to 5 minutes (Approx.).


My application works perfectly well, if number of users are less (around 20 to 30) if logon via DI SERVER. If more 30 user’s logons via DI SERVER, then the memory consumption increases (around 1600 to 1700 MB of DI Server) & DI server Crashes automatically. Here we need to restart the Windows service again & again, which is what my customer does not prefer & they threatened to leave this solution for future use.

In addition to above, we have checked so many parameters like: H/w Configuration [Windows Server 2016 (Datacenter) (64 bit Operating system) Intel (R) Xeon(R) CPU E5-2686 v4 @ 2.30 GHz, RAM:60 GB], Our code, Other exercise (Reinstall of SAP Server Tools) etc, but still DI Server hangs when number of users exceeds from 30 to 60 users and doing above transactions at a periodical interval of 4 to 5 minutes.

Note: In our solution, we are doing logon for each transaction & immediately logout after successful transaction assuming that DI Server release the occupied memory.

Kindly suggest solution against this issue.


Divyanshu Vyas