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 
  -  [Microsoft][ODBC SQL Server Driver][SQL Server]Data exists in table '[table name]', database '[database name]', that violates CHECK constraint '[constraint name]' being added. ALTER command has been MICROSOFT
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to create constraint. See previous errors. Unable to add constraint. Appears when a new constraint has failed on existing data or your constraint expression contains an error. Compare the ODBC error text that appears in the Save Incomplete dialog box with the error text shown below to determine the appropriate solution. Existing data does not match the check constraint.
• Change the data (for example, by using SQL Server Enterprise Manager) to match the constraint. • Clear the Check existing data on creation check box in the Tables property page for the check constraint in question. • Change the constraint expression in the Tables property page for the check constraint in question.
SQL Server Enterprise Manager Error Messages
Comments
 
31040 and 31041   -  Connection to server failed. Errors occurred while connecting to server name. Server message Do you still want to register this server?  MICROSOFT
A connection to a server can fail for various reasons. The following reasons are common: The user does not have the permissions required to access a server or a database. The repository is located on a remote computer, and the computer name cannot be resolved. The repository has been migrated to a SQL Server database, but the client is missing the necessary SQL Server connectivity components. A client does not have the permissions required to access the instance of SQL Server containing the database. Analysis Manager (or another application using DSO) is attempting to connect to an Analysis server with a later service pack than the Analysis Services service pack on the local host server. Network problems prevent the connection. These messages can also appear when the SQL Server Client Network Utility on the computer running Analysis Manager is configured to use TCP/IP as the default protocol, or if TCP/IP is used for the connection to the instance of SQL Server containing the Analysis Services repository. The error messages then indicate that Analysis Manager cannot make trusted connections with SQL Server using TCP/IP.
Examine the server message text embedded in the message for an indication of the problem. To see if there is a Knowledge Base article about the issue, you can search for the static portion of the server message string (omitting dynamic elements, such as a server name) at Knowledge Base (KB) Search. Ensure that the user or the client application has the permissions required to access the server, the database, and the repository, and that other connectivity problems do not exist between the client, the server, and the repository. If you are attempting to administer an upgraded Analysis server from an Analysis server that has not been upgraded, you can fix this problem by upgrading the server running the older service pack to the same service pack (or later) that is on the upgraded server. For more information, see Microsoft Knowledge Base article 290211, How to Obtain the Latest SQL Server 2000 Service Pack. If trusted connections with SQL Server cannot be made using TCP/IP, take the following steps to eliminate the problem: Use the SQL Server Client Network Utility to change the default protocol to named pipes. Use SQL Server Authentication instead of Windows Authentication to migrate the repository. If you cannot resolve the problem, contact your primary support provider.
SQL Server Analysis Services (SSAS)
Comments
 
-2147221453   -  Unable to connect to the registry on the server computer (<server name>), or you are not a member of the OLAP Administrators group on this server.  MICROSOFT
This error can occur for one of the following reasons: The user account used to connect to the Analysis server, using either Analysis Manager or a Decision Support Objects (DSO) application, is not a member of the OLAP Administrators group. You attempt to remotely administer a server that has been upgraded to Microsoft SQL Server 2000 Analysis Services Service Pack 3 (SP3) from Analysis Manager or from any Decision Support Objects (DSO) application that has not been upgraded to SP3. The Remote Registry service is not started on an Analysis server that is running on Windows 2000.
You can take the following actions to resolve this problem: Obtain the latest service pack for SQL Server 2000. For additional information, see Microsoft Knowledge Base article 290211, How to Obtain the Latest SQL Server 2000 Service Pack. Ensure that the user account used to connect to the Analysis server is a member of the OLAP Administrators group. For additional information, see Microsoft Knowledge Base article 231951, Permissions That You Must Have to Administer an OLAP Server. Note You may receive additional errors if the user account is not a member of the Administrators group. For additional information, see Microsoft Knowledge Base article 293782, Can Only Administer Analysis Server if User is a Member of Administrators Group. Ensure that the Remote Registry service is started if the Analysis server is running on Windows 2000. If you are unable to resolve this problem, contact your primary support provider.
SQL Server Analysis Services (SSAS)
Comments
 
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)
Comments
 
  -  [Microsoft][ODBC SQL Server Driver]Timeout expired.  MICROSOFT
The timeout can occur when you're updating the database with any Transact-SQL changes.
• Try again later to save the diagram or selected tables. • Save a change script and apply it to the database at a later time. • Increase the SQL Query Time-out value and try to save the diagram or selected tables again. To increase the SQL Query Time-out value 1. From the Tools menu, choose Options. 2. In the left pane, click Data Tools, and then click Data View. 3. Type a new value in the SQL query time-out box.
SQL Server Enterprise Manager Error Messages
Comments
 
  -  [Microsoft][ODBC SQL Server Driver][SQL Server]Can't allocate space for object 'Syslogs' in database 'Guest' because the 'logsegment' segment is full. If you ran out of space in Syslogs, dump the tr MICROSOFT
This error occurs because there is insufficient log space to complete the transaction.
• Follow the recommendation in the message and delete the transaction log. (Typically this action will not entirely solve the problem.) • Increase the size of the database to accommodate the change. With large databases, changes that require the recreation of tables (for example, changing a column data type or size) may not be possible using SQL Server Enterprise Manager. You may need to use methods of transferring data that don't require transactions, such as BCP(BulkCopyProgram).
SQL Server Enterprise Manager Error Messages
Comments
 
  -  [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column '[column name]' specified in constraint definition.  MICROSOFT
[Microsoft][ODBC SQL Server Driver][SQL Server]Unable to create constraint. See previous errors. • The text value in the check constraint expression on the Tables property page is not enclosed in single quotation marks ('). • A column that participates in the check constraint has been renamed. For example, if the original constraint had the expression (cityname = 'Paris') and you renamed the column to city, you would see the same error except that 'cityname' would be the invalid column shown in the error message.
Correct the expression and save the table.
SQL Server Enterprise Manager Error Messages
Comments
 
-1071611109 0xC020831B - DTS_E_INCORRECT_SQL_SERVER_VERSION MICROSOFT
The DBMS type or version of "%1" is not supported. A connection to Microsoft SQL Server version 8.0 or later is required. This occurs if IDBProperties on the connection did not return a the correct version.
SQL Server Integration Services (SSIS)
Comments
 
1073832000 0x40016040 - DTS_I_CONFIGFROMSQLSERVER MICROSOFT
The package is attempting to configure from SQL Server using the configuration string "%1".
SQL Server Integration Services (SSIS)
Comments
 
-2147409839 0x80012051 - DTS_W_SQLSERVERFAILEDIMPORT MICROSOFT
Configuration from SQL Server was not successfully imported: "%1".
SQL Server Integration Services (SSIS)
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