General Error Messages - InterSystems Documentation

More documents

Recommendations

Info

TSQL Error MessagesError Code51805181518251835184DescriptionCould not open FCB for invalid file ID %d in database '%.*ls'.Could not restart database '%.*ls'. Reverting back to old status.New log file '%.*ls' was created.File '%ls' cannot be created. Use WITH MOVE to specify a usable physical filename.Cannot use file '%.*ls' for clustered server. Only formatted files on which thecluster resource of the server has a dependency can be used.Table 3–45:TSQL Error Codes - 5700 to 5799Error Code570157025703DescriptionChanged database context to '%.*ls'.SQL Server is terminating this process.Changed language setting to %.*ls.Table 3–46:TSQL Error Codes - 5800 to 5899Error Code5803580458055807580858095810581258235828582958305831DescriptionUnknown config number (%d) in sysconfigures.Character set, sort order, or collation cannot be changed because at least onedatabase is not writable.Too few locks specified. Minimum %d.Recovery intervals above %d minutes not recommended. Use the RECONFIGUREWITH OVERRIDE statement to force this configuration.Ad hoc updates to system catalogs not recommended. Use the RECONFIGUREWITH OVERRIDE statement to force this configuration.Average time slices above %d milliseconds not recommended. Use theRECONFIGURE WITH OVERRIDE statement to force this configuration.Valid values for the fill factor are 0 to 100.You do not have permission to run the RECONFIGURE statement.Cannot reconfigure SQL Server to use sort order ID %d, because the row for thatsort order does not exist in syscharsets.User connections are limited to %d.The specified user options value is invalid.The default collation for SQL Server has been reconfigured. Restart SQL Serverto rebuild the table indexes on columns of character data types.Minimum server memory value (%d) must be less than or equal to the maximumvalue (%d).144 Caché Error Reference
TSQL Error MessagesTable 3–47:TSQL Error Codes - 5900 to 5999Error Code5904DescriptionBackground checkpoint process suspended until locks are available.Table 3–48:TSQL Error Codes - 6000 to 6099Error Code600160026004600560066007DescriptionSHUTDOWN is waiting for %d process(es) to complete.SHUTDOWN is in progress. Log off.User does not have permission to perform this action.SHUTDOWN is in progress.Server shut down by request.The SHUTDOWN statement cannot be executed within a transaction or by astored procedure.Table 3–49:TSQL Error Codes - 6100 to 6199Error Code61016102610361046106610761086109611061116112611361146115DescriptionProcess ID %d is not a valid process ID. Choose a number between 1 and %d.User does not have permission to use the KILL statement.Could not do cleanup for the killed process. Received message %d.Cannot use KILL to kill your own process.Process ID %d is not an active process ID.Only user processes can be killed.KILL SPID WITH COMMIT/ABORT is not supported by Microsoft SQL Server2000. Use Microsoft Distributed Transaction Coordinator to resolve distributedtransactions.SPID %d: transaction rollback in progress. Estimated rollback completion: %d%%.Estimated time remaining: %d seconds.The distributed transaction with UOW %s does not exist.Another user has decided a different outcome for the distributed transactionassociated with UOW %s.Distributed transaction with UOW %s is in prepared state. Only MicrosoftDistributed Transaction Coordinator can resolve this transaction. KILL commandfailed.The distributed transaction associated with UOW %s is in PREPARE state. UseKILL UOW WITH COMMIT/ABORT syntax to kill the transaction instead.Distributed transaction with UOW %s is being used by another user. KILLcommand failed.KILL command cannot be used inside user transactions.Caché Error Reference 145
Page 3 and 4:
Table of Contents1 General Error Me
Page 5 and 6:
Table 3-15: TSQL Error Codes - 1600
Page 7 and 8:
1General Error MessagesThis documen
Page 9 and 10:
General Error MessagesError Code686
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
General Error MessagesTable 1-5: Ge
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37:
Page 40:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
General Error MessagesTable 1-28: M
Page 86 and 87:
SQL Error MessagesThe message texts
Page 88 and 89:
SQL Error MessagesError Code-47-48-
Page 90 and 91:
SQL Error MessagesError Code-109-11
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
TSQL Error MessagesError Code114116
Page 98 and 99:
Page 100 and 101: TSQL Error MessagesError Code242243
Page 102 and 103: TSQL Error MessagesTable 3-5:TSQL E
Page 112 and 113: TSQL Error MessagesTable 3-13:TSQL
Page 176 and 177: TSQL Error MessagesError Code8999De
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
TSQL Error MessagesTable 3-82:TSQL
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
TSQL Error MessagesError Code20100D
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 251 and 252:
4System Error MessagesThis document
Page 253 and 254:
General System Error MessagesError
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
M Programming Language Errors4.3 M
Page 263:
IndexSSQLCODE, 79SQLCODE values, 79
show all

General Error Messages - InterSystems Documentation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?