Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  Server Error  [ 1000 result(s) ]
 3203 Severity Level 16  -  Release 10.0 and Later Backup Server has detected a SQL Server error. Release 4.9.x and Earlier Read on dump device '%.*s' failed, vsn=%ld return=%d status=%ld. Please consult the SQL Server er SYBASE SQL Server
For SQL Server release 10.0 and later, Error 3203 is displayed when a problem occurs with a remote procedure call to the Backup Server. In this case, the error is on the SQL Server side. For SQL Server releases previous to 10.0, this message is displayed when an error occurs when doing a load from a SQL Server dump. The error message output includes: • vsn – the virtual socket number. • return – the return value: 0 means successful; -2 means failure. • status – the ending status, displayed in decimal value. The most common value is 524288 which usually means an I/O error. Some causes are: • Write protect is turned on (it must be off when loading a tape because the device is opened read/write). • No dump exists on the media being accessed (for example, a blank tape or the wrong device specified). • The media that contains the dump is not readable.
Release 10.0 and Later • Check the SQL Server and Backup Server error logs to determine the cause of the error being sent from the SQL Server. • Test the connection between the Backup Server and the SQL Server by logging into the SQL Server through isql and typing: 1> execute backupserver...sp_ps 2> go where backupserver is the name of your Backup Server. This executes sp_ps on the Backup Server. Release 4.9.x and Earlier • Make sure write protect is turned off (it must be off when loading a tape because the device is opened read/write). • At the operating system level, check the contents of the tape. Additional Information If you need to call Technical Support, have the following information on hand: • SQL Server version and EBF Rollup level • Backup Server version • SQL Server and Backup Server error logs • Text of all error messages • Operating system error log
 7205 Severity Level 18  -  Can’t open a connection to site '%S_SRVID'. See the error log file in the SQL Server boot directory.  SYBASE SQL Server
This error occurs when SQL Server is unable to execute a remote procedure call (RPC) on a remote SQL Server, Backup Server, or Open Server application. In this writeup, “Server” is used to indicate a SQL Server, Backup Server, or Open Server application.
To determine why this error is occurring, perform the following steps: 1. Check whether the remote Server is running by issuing an isql statement similar to the following: % isql -Sname_of_remote_server If you receive the following message: Operating-system error: Invalid argument DB_LIBRARY error: Unable to connect: SQL Server is unavailable or does not exist. then the remote Server may not be running. Log in to the remote Server machine and check whether the Server is running. If it is not running, start it. Check whether you receive the following message after issuing the isql statement: Operating-system error: No such file or directory DB_LIBRARY error: Could not open interface file. If you do, this indicates that your SYBASE environment variable (for UNIX, OS/2 and Novell users) or your SYBASE logical name (for OpenVMS users) is not set to the correct directory. The value of the SYBASE parameter has to be set to the full path name of the SYBASE home directory where the interfaces (or sql.ini) file can be found. The value of the SYBASE parameter specifies the device as well as the path for SYBASE home. If you move the SYBASE directory structure to a new device, make sure the device is included in the SYBASE environment variable string (UNIX, OS/2, and Novell) or in the SYBASE logical name string (OpenVMS). 2. Check the error log for both the sending Server and the receiving Server. If other errors exist, refer to the writeups in this manu
 3201 Severity Level 16  -  Release 10.0 and Later No dump device has been specified. SQL Server Releases Up to 4.9.x Can’t open dump device '%.*s', device error or device off line. Please consult the SQL Server error log SYBASE SQL Server
This error occurs when SQL Server is unable to access a dump device during a database dump. This error is fatal and stops the dump from completing. Error 3201 is most likely caused by one of the following: • The device you specified for the dump is offline or otherwise unavailable to SQL Server. • Permissions for the dump device are not set correctly for user “sybase” or the user performing the dump (read and write privileges are required). • A previous dump aborted and SQL Server believes the dump device is still in use. • For SQL Server releases previous to 10.0, you are trying to run more than one dump database command at the same time. You can only do this (for tape devices) if the cntrltype values (defined using sp_addumpdevice) of the devices to which you are dumping are different. For example, only one disk byte stream interface can be active at a time. You cannot dump multiple databases or transaction logs to the same tape device or disk dump. As of SQL Server 10.0, dumps are performed by the Backup Server. During dump and load commands, the Backup Server automatically determines whether a tape or disk device is being used and what its controller type is. It ignores the cntrltype parameters specified with sp_addumpdevice.
1. Check to make sure the device you specified is defined for your SQL Server: 1> select * from master..sysdevices 2> where status = 16 or status = 24 3> go low high status cntrltype name phyname mirrorname --- ------ ------- ---------- ---------- ---------- --------- 0 20000 16 3 tapedump1 /dev/rmt4 NULL 0 20000 16 2 tapedump2 /dev/rst0 NULL If the device is not there, you can use sp_addumpdevice to add it. 2. At the operating system level, check the permissions for the dump device for user “sybase” or the user performing the dump (read and write privileges are required). 3. For SQL Server releases 4.9.x and earlier with the dump database being done to a tape dump device, do this step. Using sp_who and dump device information from the SQL Server error log, check whether SQL Server believes a dump device is still in use from a previous dump that aborted. If this is true, restart SQL Server. This should clear the error and allow you to do your dump. 4. For SQL Server releases previous to 10.0, if you wish to run more than one dump database (to tape) command at the same time and the cntrltype values (as shown above) of the devices to which you are dumping are the same, change the appropriate cntrltype values. For disk and file dump devices and for tape drives to be used as disk dump devices, you can only define one cntrltype value and the controller number parameter must be 2 (byte stream interface). For tape dump devices, the controller number para
 Buffer Mismatch Error  -  server: Buffer "%d" from database "%s" has page number "%d" in the page header and page number "%d" in the buffer header.  SYBASE SQL Server
This error only appears in the error log, and it means that a cache management problem occurred. This can be a very serious error because it is often followed by database corruption, such as 605 errors. Although often a result of hardware failure, this error can also be caused by operating system or SQL Server problems.
If possible, shut down and restart SQL Server immediately after this error occurs. This may prevent the buffer cache error from being flushed to disk. Run complete diagnostics on the machine running SQL Server as well as on all disk drives and controllers attached to the SQL Server machine. Run complete dbcc checks on any databases involved, including dbcc checkalloc and dbcc checkdb. Repair or replace faulty hardware. Then, shut down SQL Server and restart it. If you do not find any hardware problems, call Sybase Technical Support immediately. Before calling Technical Support for assistance, have the following available: • SQL Server release and EBF Rollup level • SQL Server error log • Hardware error log • Text of all the error messages • Reproducible case (if possible)
 2402 Severity Level 16  -  Error converting client characters into server’s character set. Some character(s) could not be converted.  SYBASE SQL Server
This error occurs during insertion of data (insert or bcp) when SQL Server fails to convert a character to the required character set. Error 2402 usually occurs for one of the following reasons: • The character exists in the client character set but it does not exist in the SQL Server character set. • The character exists in both the client and the SQL Server character set, but is represented by a different number of bytes in the client character set than in the SQL Server character set. This error occurs during normal processing and it prevents query execution.
The following options are available for recovering from Error 2402. Change Your Data Modify the incoming data so that it contains characters recognizable by SQL Server. Turn Off Character Set Conversion If the error occurs while you are using isql, bcp, or defncopy, you can use the -J (UNIX and PC) or /clientcharset (OpenVMS) command-line option with no character set name to set the client’s character set to NULL. If you use this command-line option without specifying a character set name, no conversion takes place and no error message is sent. As a result, some characters sent by the client to the SQL Server may not be interpreted correctly by the SQL Server and vice versa. (If only 7-bit characters are being handled, no incorrect interpretation will take place.) Otherwise, you can turn off conversion so that characters are sent and received unchanged with the following command: 1> set char_convert off 2> go Turn Off Character Set Conversion Error Reporting You can turn off the printing of error messages with the following command: 1> set char_convert on with no_error 2> go Bytes which cannot be converted are replaced with an ASCII question mark (“?”). Additional Information Refer to the System Administration Guide for details about character set conversion.
 707 Severity Level 20  -  System error detected during attempt to free memory at address 0x%lx. Please consult the SQL Server error log for more details.  SYBASE SQL Server
The Memory Manager allocates, deallocates, and manages memory for SQL Server. It manages an array of structures in the process header, each of which represents a physical page of memory in procedure cache and the current byte allocation of that page. As part of its memory deallocation process, SQL Server tries to release the pages of memory allocated to a process header when they are no longer needed. When SQL Server is unable to release that section of memory, Error 707 occurs. Error 707 is caused by memory corruption or a SQL Server problem.
Since process headers are stored in procedure cache, restarting SQL Server should clear Error 707. If it does not clear the 707 error or if the 707 error occurs again, contact Sybase Technical Support.
 926 Severity Level 14  -  Release 10.0 and Later Database '%.*s' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the SQL Server errorlog for information as to the cause. Release 4.9.x and Ear SYBASE SQL Server
This error occurs when you attempt to reference a database that has been marked suspect in one of the following circumstances: • During start-up of SQL Server • By the System Administrator as a result of certain critical errors This is a serious error and must be corrected if you want to access your database again. This error may be caused by hardware failure.
Since the 926 error is the result of an earlier error or action, the recommended action is to determine what caused the database to be marked suspect. In order to determine the cause, check the SQL Server error log for error messages for the database in question and try to eliminate those first by using the troubleshooting procedures in this manual. Depending on why the database was marked suspect, you may choose to remove its suspect flag if you are certain that the critical error which caused the database to be marked suspect has been resolved (for example, if one of the database devices was not available when SQL Server was booted and you are sure that the device is available now). If you cannot find any procedures recommended for your specific errors, call Sybase Technical Support for assistance. If the specified database does not contain important data or if you have a known, clean backup of it, you may choose to drop it first, re-create it, and then load the clean database dump into it. Refer to “How to Drop a Database When drop database Fails” in the SQL Server Troubleshooting Guide for information on how to drop a database that has been marked suspect. Before loading the database dump into the newly created database, make sure that the new database and the dumped database have the same data and log mapping, and the same user segment definitions. Refer to “Error 2558” on page 2-274 for information about how to do this. Additional Information
 3414 Severity Level 10  -  Release 10.0 and Later Database '%.*s' (dbid %d): Recovery failed. Check the SQL Server errorlog for further information as to the cause. Release 4.9.x and Earlier Database '%.*s' (dbid %d): Re SYBASE SQL Server
This error occurs when SQL Server could not complete the recovery of the specified database when starting. You cannot use the database until whatever caused the error has been corrected because SQL Server marks the database suspect.
To determine why recovery failed, examine the SQL Server error log for any errors prior to the 3414 error. It is important to identify the errors before the first occurrence of the 3414 error because subsequent attempts to start SQL Server may not give the detailed error information you need to diagnose the problem. If you do not have sufficient information to recover from the previous errors, you can recover from known, clean backups or contact Sybase Technical Support for assistance.
 Read/Write Error  -  kernel: write error on virtual disk %d, block %ld or: kernel: read error on virtual disk %d, block %ld  SYBASE SQL Server
This error occurs when SQL Server failed to read or write to the specified location on disk. This failure is usually a result of a physical disk problem.
1. Identify the device with the problem by selecting the row from sysdevices which has the virtual disk number indicated in the error message: 1> select name, phyname from master..sysdevices 2> where low/power(2,24) = virtual_disk_number 3> go The output from this query should provide the physical name of the damaged disk. Shut down SQL Server and examine the disk as soon as feasible and correct any problems found to prevent further corruption. Then restart SQL Server. The sp_diskblock procedure described below also identifies the device. 2. Use the procedure described below to determine which database (if there is more than one database on the device), table, or index is affected by this error. Use this information to assess the potential severity of the problem quickly and decide on an action which is appropriate for your operating environment. Use the sp_diskblock procedure supplied in “How to Gather Information About Read/Write Errors” in the SQL Server Troubleshooting Guide. The syntax of this procedure is: sp_diskblock virtual_disk, block_number For example, if the read/write error message displays a virtual disk number 4 and a block number 871, the procedure command is: 1> sp_diskblock 4, 871 2> go Virtual disk 4, block 871 corresponds to: Logical page 1895 in the "production" database (dbid=4) on device "main". Use the dbcc page command to determine which object is using that page. Refer to “How to Find an Object Name from a Page Numb
117   -  Unexpected fatal error occurred. Attempting to restart server.%0\r\n  MICROSOFT
The Analysis server has shut down. The application event log will contain a message that resembles the following: Source: MSSQLServerOLAPServices Event ID: 117 Description: Unexpected fatal error occurred. Attempting to restart server. In addition, Analysis Manager or a client application may display a message such as the following: Connection to the server is lost. Possible reasons for the shutdown include: The data files in the Analysis Services Data directory are corrupted. The server has encountered a bug.
To fix corrupted data files, stop the Analysis server if it is running, and then delete all files in the Data directory for Analysis Services. After you delete the files, restart the server and restore your Analysis Services databases from backup files. To correct possible bugs, make sure that your server is running the latest service pack for SQL Server 2000 Analysis Services. For more information, see Microsoft Knowledge Base article 290211, How to Obtain the Latest SQL Server 2000 Service Pack.
SQL Server Analysis Services (SSAS)

SQL Server Analysis Services (SSAS) (5)
SQL Server Enterprise Manager Error Messages (123)
Visual Studio Project Error Messages (1)
Kerberos Errors (5)
SQL Server Reporting Services (SSRS) (10)
Crystal Reports Print Engine (1)
Cisco IOS (12)
LAN Emulation  (3)
SQL Server System Error Messages  (104)
Visual Studio Error Messages (4)
  Prev   1  2  3  4  5  6  7  8  9  10  Next