FIX: RPC from SQL NT Fails After 60 Seconds
  
PSS ID Number: Q112697
Article last modified on 12-02-1994
 
4.20
 
WINDOWS
 

----------------------------------------------------------------------
The information in this article applies to:
 
  - Microsoft SQL Server version 4.2
----------------------------------------------------------------------
 
BUG# NT: 694 (4.2)
 
SYMPTOMS
========
 
When executing a remote procedure call from a local SQL Server for Windows
NT to a remote server or ODS application, the RPC execution fails. The
client process receives either a nonsensical error message or is
disconnected due to an access violation. The stored procedure will execute
correctly if it is run directly on the remote server using a client
application.
 
Possible errors include:
 
   Access violations causing the client process to be disconnected
   Msg 7221 Message too long.  Length = < very large number >
   Msg 7221, login to site '' failed
   results never returned to front end, query must be canceled
 
CAUSE
=====
 
An RPC execution issued from NT SQL Server will timeout after 60 seconds of
execution. This failure can result in a variety of error messages and
behaviors depending on the number and timing of results ( if any ) being
returned from the remote procedure.
 
WORKAROUND
==========
 
Ensure that the total execution time of any remote stored procedure
executed by a NT SQL Server is under 60 seconds.
 
STATUS
======
 
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 4.2. This problem was corrected in SQL Server version 4.21a. For
more information, contact your primary support provider.
 
Additional reference words: 4.20 calls proc Windows NT
KBCategory: kbother
KBSubcategory: SSrvWinNT
 
=============================================================================
 
Copyright Microsoft Corporation 1994.
