FIX: Error 4305 Loading Log Dump
  
PSS ID Number: Q104117
Article last modified on 10-31-1994
 
4.20
 
OS/2
 

----------------------------------------------------------------------
The information in this article applies to:
 
  - Microsoft SQL Server version 4.2 for OS/2
----------------------------------------------------------------------
 
BUG# OS/2: 1741 (4.2)
 
SYMPTOMS
========
 
Loading a transaction log dump may fail with the following 4305 error:
 
   Specified file <dump file> is out of sequence. Current time stamp
   is <date/time 1> while dump was from <date/time 2>.
   (Msg 4305, Level 16, State 1)
 
CAUSE
=====
 
SQL Server incorrectly allows a DUMP TRANsaction command to be issued
while inside a user-defined transaction. If after dumping the
transaction log, the user-defined transaction is rolled back, any
attempt to later load that transaction log dump will fail with the
3305 error.
 
WORKAROUND
==========
 
Do not issue a DUMP TRANsaction command while you are inside of a
user-defined transaction. To verify this, issue a "select
@@trancount". If this returns any value other than zero, your
connection is inside of a transaction, and the transaction should
either be committed or rolled back before issuing the DUMP TRANsaction
command.
 
STATUS
======
 
Microsoft has confirmed this to be a problem in SQL Server version
4.2 for OS/2. This problem was corrected in SQL Server version
4.2b. For more information, contact your primary support provider.
 
Additional reference words: 4.20
KBCategory: kbprg kberrmsg
KBSubcategory: SSrvServer
 
=============================================================================
 
Copyright Microsoft Corporation 1994.
