Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You mention that the solution does not have any problems in another environment, so it's likely that there is a configuration problem.</p> <p>Check the following:</p> <p>** On SQL Server, set some upper memory limit for SQL Server. By default, SQL Server uses whatever it can get and then hangs onto it, so set a reasonable limit so that your system can operate without spending a lot of time paging memory onto and from your hard drive(s).</p> <p>** Ensure that you have available disk space - maybe you are running low - this can lead to all kinds of strange problems. </p> <p>** Try to split up the system's paging file among its physical drives (if you have more than one drive on the system). Also consider using a faster drive, or if you have lots of cash laying around, get a SAN.</p> <p>** In BizTalk, is tracking enabled? If so, are you also tracking message bodies? Disable tacking or message body tracking and see if there is a difference.</p> <p>** Start performance monitor and monitor the following counters when running your solution</p> <ul> <li>Object: BizTalk Messaging </li> <li>Instance: (select the receiving host) %%</li> <li><p>Counter: Documents Received/Sec</p></li> <li><p>Object: BizTalk Messaging</p></li> <li>Instance: (select the transmitting host) %%</li> <li><p>Counter: Documents Sent/Sec</p></li> <li><p>Object: XLANG/s Orchestrations</p></li> <li>Instance: (select the processing host) %%</li> <li>Counter: Orchestrations Completed/Sec.</li> </ul> <p>%% You may have only one host, so just use it. Since BizTalk configurations vary, I am using generic names for hosts.</p> <p>The preceding counters monitor the most basic aspects of your server, but may help to narrow down places to look further. You can, of course, add CPU and Memory too. If you have time (days...maybe weeks) you could monitor for processes that allocate memory and never release it. Use the following counter...</p> <ul> <li>Object: Memory </li> <li>Counter: Pool Nonpaged Bytes</li> </ul> <p>Slow decline of this counter indicates that a process is not releasing memory, which affects everything on the system.</p> <p>Let us know how things turn out!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload