SNA Server Events 94 and 592 Fill Up Application Log

RESOLUTION

To resolve this problem you may obtain an update from Microsoft or work around the problem as described below.

Update

Obtain the update to SNA Server 2.11 which reduces the audit log level of event 94 and event 582. To prevent these events from logging, you must set the default audit log level to Significant System Events in the Logs dialog box by choosing Logs from the Options menu in SNA Admin.

NOTE: When SNA Server is installed, the default audit log level is already set for Significant System Events.These events are still logged if the SNA Server logging level is set for General Information Messages or Detailed Problem Analysis.

Workaround

To work around this problem and prevent the events from being logged, increase the Timeout parameter of the TP within the registry. The Timeout parameter determines the time that a RECEIVE_ALLOCATE waits for an incoming attach message before returning an error. For manually started invokable TPs, the Timeout parameter is configured in the registry under the HKEY_LOCAL_MACHINE subtree. If the TP is written as an application, the Timeout value is found under:

   SYSTEM\CurrentControlSet\Services\SnaBase\Parameters
      \TPs\<tpname>\Parameters
				

where <tpname> is the name of the transaction program. If the TP is written as a Windows NT service, the Timeout value can be found under:

   SYSTEM\CurrentControlSet\Services\<tpname>\Parameters
				

where <tpname> is the name of the transaction program.

   Value Name: Timeout
   Data Type:  REG_DWORD
   Value:      <time in milliseconds>
				

If there is no entry configured, the timeout defaults to infinite, so the RECEIVE_ALLOCATE never times out and Event 94 and 592 do not occur.