Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  SQL Server  [ 1000 result(s) ]
CISCO IOS IBM IBM DB2 MICROSOFT ORACLE SAP SYBASE SQL Server 
 1204 Severity Level 19  -  Release 10.0 and Later SQL Server has run out of LOCKS. Re-run your command when there are fewer active users, or contact a user with System Administrator (SA) role to reconfigure SQL Server wit SYBASE SQL Server
This error occurs when SQL Server runs out of locks, as controlled by sp_configure. Following is an example of the output from sp_configure locks, and a brief description of the output related to locks: name minimum maximum config_value run_value ----- ------- ---------- ------------ --------- locks 5000 2147483647 0 5000 • The minimum and maximum column entries represent the minimum and maximum number of configurable locks for SQL Server. • The config_value column contains the value to which the locks configuration parameter has been set with sp_configure. The default value of config_value, which corresponds to the minimum value, is 0 (zero). • The run_value column contains the value SQL Server is using. The default run value in sysconfigures is 5000.
Rerun the command when there are fewer active users, or ask the Sybase System Administrator (“sa”) to reconfigure SQL Server for more locks. Increasing the number of available locks does impact performance and memory requirements. Refer to the table “Current memory requirements of some user-configurable parameters” in the SQL Server Troubleshooting Guide which shows how much overhead is required for each lock. u WARNING! Before making any changes to SQL Server, see “SQL Server Memory Issues” in the SQL Server Troubleshooting Guide or the System Administration Guide sections on memory management for more information about how SQL Server uses memory resources. To increase the number of locks available, complete the following steps: 1. Verify the number of locks currently configured for SQL Server: 1> use master 2> go 1> sp_configure locks 2> go u WARNING! If you increase the number of locks available by too many locks, SQL Server may run out of memory and be unable to restart. See “Cannot Start SQL Server After Altering Configuration” in the SQL Server Troubleshooting Guide if you run out of memory and cannot restart SQL Server. 2. Choose the number of locks you want to configure and issue the following command: 1> sp_configure locks, number_of_locks 2> go 3. Initialize the change with the reconfigure command: 1> reconfigure 2> go 4. Restart SQL Server to operate with the new values. Additional Information See the table “Memory requirements f
Comments
 
 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
Comments
 
 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
Comments
 
 File Already in Use Error  -  basis_dlock: file '%s' already in use by a SQL Server  SYBASE SQL Server
During startup, SQL Server tries to lock the master device. If SQL Server finds that the master device is already locked, the message “basis_dlock: file '%s' already in use by a SQL Server” is written to the error log and SQL Server does not start. %s is the name of the master device file. The most common reasons for this error are: • You are trying to start a SQL Server with a master device that is already being used by another SQL Server. • The SQL Server you are trying to start is already running.
At the operating system level, check the processes that currently exist and determine whether a SQL Server using the master device you specified is already running. If a SQL Server using the master device you specified is already running, and this is not the Server you want to start, determine the correct master device name for the Server you want to start. If you cannot determine whether the master device is already in use, reboot the operating system. If the master device resides on an operating system file system, you can copy the file to another name, modify your runserver file, and start SQL Server with that new file.
Comments
 
 Character Set Error  -  SQL Server doesn't support use of character_set_name character set.  SYBASE SQL Server
This error occurs when the client software default character set has not been installed on the SQL Server to which the client is trying to connect. This happens most often when the client is running on a different operating system from SQL Server.
To allow the client and SQL Server to communicate, do the following: 1. Check to see if the client software character set is installed on SQL Server by executing this query: 1> use master 2> go 1> select name, id, csid from syscharsets 2> go If the client software’s default character set appears in the output, have your primary site contact call Sybase Technical Support. If it does not appear, go to step 2. If the client software’s default character set does not appear in the output, you may be able to set the client software to the character set which SQL Server is using. For example, using the isql -J flag (see the SQL Server Reference Manual entry for isql for more information). If this is not possible, go to step 2. u WARNING! Familiarize yourself with all the instructions in the Installation Guide before completing step 2, in order to make the character set addition a smooth process. 2. Run the installation utility sybinit (or the equivalent for your platform). Choose the additional character set item from the character set menu. If the particular character set you need is not one of the options listed, you must purchase that character set by purchasing a Language Module from Sybase, and install it with sybinit or its equivalent. 3. Try again to connect to SQL Server with the client software. Call Sybase Technical Support if you are still unable to connect to SQL Server.
Comments
 
 701 Severity Level 19  -  Release 10.0.2 and Later There is not enough procedure cache to run this procedure, trigger, or SQL batch. Retry later, or ask your SA to reconfigure SQL Server with more procedure cache. Relea SYBASE SQL Server
This error occurs when there is not enough procedure cache available to execute a stored procedure, trigger, or batch of one or more SQL statements. This can happen when loading a query plan into procedure cache or when resolving or compiling a procedure, trigger or batch. See “Procedure Re-resolution” in the SQL Server Troubleshooting Guide for a description of resolution. The amount of available procedure cache is based on SQL Server use, so this error may occur intermittently as procedure cache is used and released. Also, one or more procedures can repeatedly fail with this error while others complete normally. This is because query plans vary greatly in size. Therefore, while there may not be sufficient space to load a large query plan, several smaller plans may fit.
Correct this error by increasing the size of procedure cache. You can increase the amount of total procedure cache in three ways: • Use the memory configuration parameter to increase the total amount of memory requested by SQL Server. • Use the procedure cache configuration parameter to increase the percentage of total cache space dedicated to procedure cache. • Decrease the amount of memory required for other resources, for example, unneeded user connections. Increasing the memory configuration parameter for SQL Server is the most straightforward method. It increases both the procedure and data caches, although it can waste memory. On some operating systems, especially VMS and most UNIX systems, be sure to make any necessary operating system memory resource adjustments. For example, verify the current kernel value for the maximum size of a shared memory segment, usually SHMMAX, and make sure you have adequate memory and swap space on the system for the additional memory configured for the Server. See your operating system documentation or the SYBASE SQL Server Installation Guide or System Administration Guide Supplement for more information. If your memory resources are limited, you can increase the procedure cache configuration parameter for the SQL Server without changing the value of the memory configuration parameter. This shifts space from the data cache to the procedure cache and may result in performance degradation or other problems if not
Comments
 
 3002 Severity Level 23  -  For SQL Server Releases Up to 4.9.x Attempt to dump database %.*s found logical page %ld when logical page %ld expected.  SYBASE SQL Server
This error occurs when SQL Server finds an unexpected page number during a database dump. This error is fatal and stops the dump from completing. Error 3002 is most likely caused by corruption of a database as a result of either: • Hardware failure • Inadvertently trying to use a raw partition for two separate purposes
Run dbcc checkalloc to determine whether your database has a bad page number or page header. If this is the case, dbcc checkalloc will display Error 2529. In this case, refer to “Error 2529” on page 2-254 to determine how to recover from this error. Hardware Errors • Check the SQL Server error log to see if there are other indications of hardware problems, such as kernel messages reporting I/O errors. • Check the operating system error log or diagnostics utilities for I/O errors. Raw Partition Misuse Refer to “Correct Use of Raw Partitions” in the SQL Server Troubleshooting Guide to determine whether a raw partition is being used incorrectly. Incompatible Drives Some drives which have their read-ahead cache enabled may cause Error 3002. Turning their read-ahead cache off clears the error. If you suspect that this is the cause of your corruption, contact your hardware vendor. In this case, rebooting SQL Server and restarting the dump might clear the error. Additional Information If none of the above actions have solved the 3002 error, call Sybase Technical Support. Before you call, have the following information on hand: • SQL Server release and EBF Rollup Level • SQL Server and Backup Server error logs • Operating system error log • Text of all error messages • Results from dbcc checkdb and dbcc checkalloc if possible
Comments
 
 7227 Severity Level 17  -  Release 10.0 and Later Can't open a connection to site '%S_SRVID' because SQL Server is not configured for remote access. Ask a user with System Administrator (SA) role to reconfigure SQL Server SYBASE SQL Server
This error occurs when you try to execute a remote procedure call (RPC) and the initiating or receiving SQL Server is not configured for remote access.
Configure the local or remote SQL Server for remote access by changing the remote access configuration parameter via sp_configure. 1> sp_configure "remote access", 1 2> go 1> reconfigure 2> go After enabling the remote access variable and restarting SQL Server, the remote logins, remote sites, remote connections, and pre-read packets configuration parameters will be set to their default values. If you determine that the default values for remote logins, remote sites, remote connections, and pre-read packets are not adequate for your needs, then the sp_configure procedure can be used to change these configuration parameters as well. After issuing the above commands, restart SQL Server so that the configuration change can take effect. Additional Information For more information, see remote access in the System Administration Guide and sp_configure in the SQL Server Reference Manual.
Comments
 
 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
Comments
 
 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.
Comments
 
 

 
SQL Server Analysis Services (SSAS) (10)
SQL Server Enterprise Manager Error Messages (125)
INFORMIX (33)
SQL Server System Error Messages  (295)
SQL Server Embedded SQL for C Error Messages (ESQL/C)  (48)
C# .Net Compiler Errors and Warnings (1)
Crystal Reports Print Engine (1)
SQL Server DB-Library Error Messages  (19)
SQL Server Integration Services (SSIS) (151)
SQL Server Reporting Services (SSRS) (29)
Cisco IOS (1)
SQL Server Distributed Queries Error Messages  (1)
 
  Prev   1  2  3  4  5  6  7  8  9  10  Next