Ошибка odbc sqlstate 01000 номер ошибки 0

mauricio0015

changed the title
SQLSTATE: 01000 Código: 0 Mensaje: [unixODBC] [Driver Manager] No se puede abrir lib ‘Controlador ODBC 13 para SQL Server’: archivo no encontrado

Error information: SQLSTATE: 01000 Code: 0 Message: [unixODBC][Driver Manager]Can’t open lib ‘ODBC Driver 13 for SQL Server’ : file not found

Jan 27, 2018

• Remove From My Forums

Answers

• • Marked as answer by
    HumayunM
    Monday, December 28, 2009 9:49 AM
  • Edited by
    Kalman Toth
    Friday, September 28, 2012 7:28 PM

All replies

• This is a generic message as you have already figured out and should be preceeded by a more detailed error which should be displayed in the SQL Agent job history log. If you have a profiler trace from that time, an additional error should also be present.

  This error message can also pop up when you have some inconsistencies in the database. Could you run a dbcc checktable on the table whose index you were rebuilding and ensure that there are no inconsistencies reported.

  HTH

  ---

  This posting is provided «AS IS» with no warranties, and confers no rights.
  My Blog: Troubleshooting SQL

• The job history log is not complete either. The errorlog also doesn’t state anything
  
  «. …contact your system administrator. [SQLSTATE 01000] (Message 2528)  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528)  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528)  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528)  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528)  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528)  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528)  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] (Message 2528)  DBCC execu…  The step failed.»

  And the good part is, when I ran the proc manually it ran fine. i.e. from sql management studio

  Very perplexing behaviour

• When you create a maintenance plan you have the option to logging the details.
  Can you check your maintenance plan and take the logging path, go to that path and open the last executuion log file to get the error. Else go the maintenance plan and right click on the plan to view the history.

  ---

  Vidhya Sagar. Mark as Answer if it helps!

• Hi VidhyaSagar,
  I am not using maintenance plan. I am using a TSQL proc.

  Thanks

• Hi,

  To troubleshoot the issue, could you provide us the error messages logged in the SQL Server error log files. By default, the error log is located at Program FilesMicrosoft SQL ServerMSSQL.nMSSQLLOGERRORLOG and ERRORLOG.n files.

  If there are any more questions, please let me know.
  Thanks and Merry Christmas.

  ---

  ***Xiao Min Tan***Microsoft Online Community***

• You mention «job history log» so I infer that this is a scheduled job from SQL Agent. 

  If so, you can edit the Advanced Properties of the Job Step.   There you will see options for retaining more log information.  For instance, you can select «Log to table» which will log information from running the job into a table in msdb.

  This may provide details missing from the logs that you are examining.

  After the job runs, you can come back to the Advanced Properties tab and click the View button to see what details were recorded.  Or you can select it out as:

  SELECT j.Name, s.Step_Name, s.Step_id, l.log_size, RIGHT(l.log, 50000) AS recent_log
  FROM msdb.dbo.sysjobs j JOIN msdb.dbo.sysjobsteps s
    ON j.job_id = s.job_id
    JOIN msdb.dbo.sysjobstepslogs l
      ON s.step_uid = l.step_uid

  The RIGHT(l.log, 50000) is just to limit the output, since if you use «Append output to existing entry…» this row can grow to two gigabytes.

  RLF

  • Edited by
    SQLWork
    Friday, December 25, 2009 2:59 PM
    Corrected last line

• Hi Russel,
  I have done that part i.e select Advanced option and log to table and log to a file also. But the error is the same
  like tail of the file is:
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
  The statement has been terminated. [SQLSTATE 01000]

  Hi Xiao-Min,
  There is nothing of importance in errorlog.

  ———-
  But the thing is, I can run the rebuild index proc as a query but it is only giving this error from sql agent.

  Thanks all for contributing your valuable time.

• • Edited by
    Kalman Toth
    Friday, September 28, 2012 7:28 PM

• Hi Kalman,

  I am not using print. I am writing below the code that is used as the TSQL PROC.

  CREATE procedure [dbo].[Usp_osdeDBReIndex_2k5]
  as
  DECLARE @TableName varchar(255)

  DECLARE TableCursor CURSOR FOR
  SELECT table_name FROM information_schema.tables
  WHERE table_type = ‘base table’

  OPEN TableCursor

  FETCH NEXT FROM TableCursor INTO @TableName
  WHILE @@FETCH_STATUS = 0
  BEGIN
  DBCC DBREINDEX(@TableName,’ ‘,90)
  FETCH NEXT FROM TableCursor INTO @TableName
  END

  CLOSE TableCursor

  DEALLOCATE TableCursor

• I was able to recreate it in SQL Server 2008 using your modified sproc.

  DBCC execution completed. If DBCC printed error messages, contact your system administrator. 
  [SQLSTATE 01000] (Message 2528) 

  As some of the links above stated, it can just be ignored.

  You can also open a bug report at Connect:
  https://connect.microsoft.com/SQLServer?wa=wsignin1.0

  Sproc:

  CREATE procedure uspDBreindex
  as 
  DECLARE @TableSchema varchar(127), @TableName varchar(255)
  
  DECLARE TableCursor CURSOR FOR
  SELECT table_schema,table_name FROM information_schema.tables
  WHERE table_type = 'base table'
  
  OPEN TableCursor
  
  FETCH NEXT FROM TableCursor INTO @TableSchema, @TableName
  WHILE @@FETCH_STATUS = 0
  BEGIN
  	SET @TableName=@TableSchema+'.'+@TableName
  	DBCC DBREINDEX(@TableName,' ',90)
  	FETCH NEXT FROM TableCursor INTO  @TableSchema,@TableName
  END
  CLOSE TableCursor
  DEALLOCATE TableCursor
  GO
  

  ---

  Kalman Toth SQL SERVER 2012 & BI TRAINING
  New Book: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2012

  • Edited by
    Kalman Toth
    Friday, September 28, 2012 7:29 PM

• Hi Kalman,
  I can ignore it but the job fails and sends a notification. Isn’t there a way to avoid the failure of job?

  Thanks

• 70 and then I get «The statement has been terminated». Previously I was able to run the proc fine as a query at-least but now I am getting after 70 or so [SQLSTATE 01000] msg  This error message «Msg 0, Level 11, State 0, Line 0 A severe error occurred on the current command. The results, if any, should be discarded.»

  I found one KB article http://support.microsoft.com/kb/938102. It kind of qualifies. I am indeed on SP2.
  But the errorlog doesn’t have anything

  2009-12-27 21:25:45.90 Server      The time stamp counter of CPU on scheduler id 12 is not synchronized with other CPUs.
  2009-12-27 21:33:46.00 Server      The time stamp counter of CPU on scheduler id 2 is not synchronized with other CPUs.
  2009-12-27 21:57:46.03 Server      The time stamp counter of CPU on scheduler id 13 is not synchronized with other CPUs.
  2009-12-27 22:05:46.04 Server      The time stamp counter of CPU on scheduler id 14 is not synchronized with other CPUs.
  2009-12-27 22:33:46.05 Server      The time stamp counter of CPU on scheduler id 11 is not synchronized with other CPUs.
  2009-12-27 22:41:46.05 Server      The time stamp counter of CPU on scheduler id 12 is not synchronized with other CPUs.
  2009-12-27 22:57:46.06 Server      The time stamp counter of CPU on scheduler id 4 is not synchronized with other CPUs.
  2009-12-27 23:09:46.06 Server      The time stamp counter of CPU on scheduler id 14 is not synchronized with other CPUs.
  2009-12-27 23:13:46.06 Server      The time stamp counter of CPU on scheduler id 2 is not synchronized with other CPUs.
  2009-12-27 23:29:46.07 Server      The time stamp counter of CPU on scheduler id 13 is not synchronized with other CPUs.
  2009-12-28 00:00:08.94 spid20s     This instance of SQL Server has been using a process ID of 2824 since 12/10/2009 9:29:36 PM (local) 12/11/2009 2:29:36 AM (UTC). This is an informational message only; no user action is required.
  2009-12-28 00:05:46.08 Server      The time stamp counter of CPU on scheduler id 4 is not synchronized with other CPUs.
  2009-12-28 00:09:46.08 Server      The time stamp counter of CPU on scheduler id 12 is not synchronized with other CPUs.
  2009-12-28 00:21:46.09 Server      The time stamp counter of CPU on scheduler id 2 is not synchronized with other CPUs.
  2009-12-28 00:49:46.10 Server      The time stamp counter of CPU on scheduler id 13 is not synchronized with other CPUs.
  2009-12-28 01:13:46.11 Server      The time stamp counter of CPU on scheduler id 4 is not synchronized with other CPUs.
  2009-12-28 01:17:46.11 Server      The time stamp counter of CPU on scheduler id 14 is not synchronized with other CPUs.
  2009-12-28 01:29:46.11 Server      The time stamp counter of CPU on scheduler id 12 is not synchronized with other CPUs.
  2009-12-28 01:41:46.12 Server      The time stamp counter of CPU on scheduler id 2 is not synchronized with other CPUs.
  2009-12-28 01:53:46.12 Server      The time stamp counter of CPU on scheduler id 13 is not synchronized with other CPUs.
  2009-12-28 02:41:46.14 Server      The time stamp counter of CPU on scheduler id 4 is not synchronized with other CPUs.

  So I am not sure if this is the bug I am hitting for this rebuild index job. How to find out?

• I get the below error.
  ————————————-
  The statement has been terminated.
  Msg 0, Level 11, State 0, Line 0
  A severe error occurred on the current command.  The results, if any, should be discarded.

• • Marked as answer by
    HumayunM
    Monday, December 28, 2009 9:49 AM
  • Edited by
    Kalman Toth
    Friday, September 28, 2012 7:28 PM

• Thanks Kalman. I will work on that.