Microsoft KB Archive/229636

From BetaArchive Wiki

Article ID: 229636

Article Last Modified on 9/22/2005



APPLIES TO

  • Microsoft SNA Server 3.0 Service Pack 4
  • Microsoft SNA Server 4.0



This article was previously published under Q229636

SYMPTOMS

The NvRunCmd service may terminate unexpectedly when SNA Application internal tracing is enabled. Control Panel Services shows the NvRunCmd service with the status as "Stopped."

CAUSE

NvRunCmd writes a trace line after a particular function call, but before the corresponding GetLastError() function call. Therefore, the value returned by this function call is incorrect and causes the NvRunCmd to terminate. As a result, the NvRunCmd Service receives a shutdown request and the service is stopped.

RESOLUTION

SNA Server 4.0

To resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack



SNA Server 3.0

To resolve this problem, obtain the latest service pack for SNA Server version 3.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

184307 How to Obtain the Latest SNA Server Version 3.0 Service Pack




STATUS

Microsoft has confirmed that this is a problem in Microsoft SNA Server, versions 3.0, 3.0SP1, 3.0SP2, 3.0SP3, 4.0, 4.0SP1, 4.0SP2.. This problem was first corrected in SNA Server version 3.0 Service Pack 4 and SNA Server version 4.0 Service Pack 3.

MORE INFORMATION

The above symptoms can be seen only when the Trace Flag "Debug Conditions" is selected in the SNA Application internal trace property sheet.

If this flag is not enabled, NvRunCmd does not encounter this error, even if all other available flags are selected.


Additional query words: NetView NvrunCmd

Keywords: kbbug kbfix kbsna300sp4fix kbsna400sp3fix kbqfe kbhotfixserver KB229636