Server Error Messages 4300 - 4399


 Database in use.  A user with System Administrator (SA) role must have exclusive use of DB to load transaction.
 Specified file `%.*s' is not in valid dump transaction format.
 Specified file `%.*s' is out of sequence. Current time stamp is %S_DATE while dump was from %S_DATE.
 There was activity on database since last load, unable to load. Must restart load sequence with the load database to continue.
 You must be the DBO of database %.*s or have Operator (OPER) role to run LOAD TRANSACTION.
 Recreate index failed for table %ld, index %d. The table has been left in an inconsistent state, and the index is missing,  so LOAD TRANSACTION errors may result. Run DBCC CHECKTABLE on the table if LOAD TRANSACTION succeeds.
 Cannot find table %ld to recreate index %d.
 Log scan for recreate index failed.
 Can only LOAD TRANsaction in master if SQL Server is in single-user mode.
 Could not read log page %ld for database `%*s'; the DBINFO structure for this database is invalid, or the page chain is corrupt.  Cannot proceed with LOAD TRANSACTION.
 Last log page `next free byte' value is out of range: %ld; should be no greater than %ld.
 Failed to patch the transaction log for database `%.*s'.
 Dump or load commands require a logical dump device name from the sysdevices system table.  Use sp_addumpdevice to add `%.*s' to sysdevices.
 SQL Server can not load this transaction log dump because version information in the dump does not match information in the database. Database: log version=%d, upgrade version=%ld. Dump: log version=%d, upgrade version=%ld.
 SQL Server cannot load a dump of the master database that was dumped from an older version of SQL Server. The current master database upgrade version is %ld, the dump master database upgrade version is %ld.
The specified RID (%d,%d) was not found in the transaction log.  
The transaction log could not be opened for point in time recovery.  
The specified recovery date (%S_DATE_LONG) is not between the start (%S_DATE_LONG ) and end (%S_DATE_LONG) date. 
A load transaction to a point in time will reset the transaction log sequence. A database dump is required to restart the log sequence.  
An early end-of-log has been forced in database ’%.*s’ prior to the end of the loaded transaction log. The load sequence has been broken. Another LOAD TRANSACTION cannot be performed without a preceding LOAD DATABASE. 

Number	Severity	Text and Explanation
4301	16	Database in use. A user with System Administrator (SA) role must have exclusive use of DB to load transaction. Explanation: A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4302	16	Specified file `%.s' is not in valid dump transaction format. Explanation:* A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4305	16	Specified file `%.s' is out of sequence. Current time stamp is %S_DATE while dump was from %S_DATE. Explanation:* Refer to the writeup for this error.
4306	16	There was activity on database since last load, unable to load. Must restart load sequence with the load database to continue. Explanation: If user transactions modify the transaction log between transaction dump loads to a database, Error 4306 occurs and the load fails. Error 4306 would only occur if someone ran the online database command for the database, someone did work in the database, and then you tried to do a load transaction for the database. Begin again with a load database or proceed to use the database without recovering all transactions.
4312	14	You must be the DBO of database %.s or have Operator (OPER) role to run LOAD TRANSACTION. Explanation:* You do not have the permission to execute this command. Have the object owner or a user with the needed role run this command.
4313	16	Recreate index failed for table %ld, index %d. The table has been left in an inconsistent state, and the index is missing, so LOAD TRANSACTION errors may result. Run DBCC CHECKTABLE on the table if LOAD TRANSACTION succeeds. Explanation: A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4314	20	Cannot find table %ld to recreate index %d. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so dbcc diagnostics can be run.
4315	20	Log scan for recreate index failed. Explanation: Adaptive Server encountered an internal error affecting the current process. Reconnect to Adaptive Server. Report the error to your System Administrator so dbcc diagnostics can be run.
4316	16	Can only LOAD TRANsaction in master if SQL Server is in single-user mode. Explanation: A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4317	21	Could not read log page %ld for database `%s'; the DBINFO structure for this database is invalid, or the page chain is corrupt. Cannot proceed with LOAD TRANSACTION. Explanation:* Adaptive Server encountered an internal error affecting all processes in the current database. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
4318	21	Last log page `next free byte' value is out of range: %ld; should be no greater than %ld. Explanation: Adaptive Server encountered an internal error affecting all processes in the current database. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
4319	21	Failed to patch the transaction log for database `%.s'. Explanation:* Adaptive Server encountered an internal error affecting all processes in the current database. Report the error to your System Administrator. Adaptive Server must be restarted and dbcc diagnostics run.
4320	16	Dump or load commands require a logical dump device name from the sysdevices system table. Use sp_addumpdevice to add `%.s' to sysdevices. Explanation:* A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4321	16	SQL Server can not load this transaction log dump because version information in the dump does not match information in the database. Database: log version=%d, upgrade version=%ld. Dump: log version=%d, upgrade version=%ld. Explanation: A database maintenance operation failed. Take any corrective action indicated by the message. Check the Adaptive Server error log.
4322	16	SQL Server cannot load a dump of the master database that was dumped from an older version of SQL Server. The current master database upgrade version is %ld, the dump master database upgrade version is %ld. Explanation: Refer to the writeup for this error.
4323	16	The specified RID (%d,%d) was not found in the transaction log. Explanation: Check command parameters.
4324	20	The transaction log could not be opened for point in time recovery. Explanation: Database log is not available for this maintenance operation.
4325	16	The specified recovery date (%S_DATE_LONG) is not between the start (%S_DATE_LONG ) and end (%S_DATE_LONG) date. Explanation: Check parameters for the point in time recovery command.
4327	10	A load transaction to a point in time will reset the transaction log sequence. A database dump is required to restart the log sequence. Explanation: This is an informational message.
4328	10	An early end-of-log has been forced in database ’%.s’ prior to the end of the loaded transaction log. The load sequence has been broken. Another LOAD TRANSACTION cannot be performed without a preceding LOAD DATABASE. Explanation:* This is an informational message but may require follow-up action. Contact your System Administrator.