• 1. SQL Server Agent Stops
    I would run profiler against the server in question during the time your having the issue. >-----Original Message----- >Sorry to repeat this earlier thread. I've given up on the web based >newgroup server and moved over to Outlook Express, but I can't access >anything earlier than a couple of days so... > >At 3:00am every day, SQL Server Agent stops. When I look at the log file it >says Sql Server Error 1115: Cannot generate SSPI context. I have the >checkbox to have the Agent restart itself if it stops checked. I can start >the agent back up again with no error. What's going on? > >Answers to earlier replies: >I don't know of anything going on at 3:00am, but I see now that there must >be. I have looked in Scheduled Tasks; nothing there.I have Maintenance >plans in Enterprise Manager that run on the hour, but they work on all the >other hours. I have attached a log file. Apparently SQL Server is being >restarted every day at 3:00am, but how do I find out what's doing it? > > >
  • 2. Slave (replicated) database to improve SELECT performance?
    Hello, First let me waive the standard disclaimer and say I only partly know what I'm talking about. :) Anyway, I've got a website that runs SQL 2005 (standard) on the backend. Right now I'm doing about 4-5 INSERT/UPDATEs (one or the other) per second at a constant clip... Everything is just fine. As this grows, I'll get more and more INSERT/UPDATEs per second, which potentially could grow upwards of 40-50 per second (God willing). Now I want to allow users to query against this data as well. So I'm wondering if it will be better to replicate the data to a read-only database to do my SELECTs from (so my I/Us don't kill the queries)? The SELECT data doesn't need to be instant, it could be anywhere from 5 to 30 minutes behind with no problems (if that even matters). I read somewhere this is what the Flickr guys did with MySQL... They scaled out to slave databases that handled the SELECTs. Does anyone have any expert advice here that might help? Thanks!!
  • 3. Transaction logs won't backup
    Have a MSSQL 2000 install that refuses to backup transaction logs. Does database backups fine and I've made sure it is not trying to backup the transaction logs during a full db backup. Just tells me the transaction log backup failed, but nothing more.
  • 4. Ability to import Data into SQL Server Express Edition
    I am using SQL Server 2005 Express Edition and Server Mangement Studio Express. I can connect to the server and create databases/tables just fine but I can't seem to fine a way to import data into the table. The Data Transformation wizard does not seem to be in the Management studio. Can anybody give me some help in how to import data into express edition? Thanks,
  • 5. Can't send operator email in SQL Sever 2005
    I have set up Database Mail I have sent a test message successfully I have set up a Operator When I create a test job to send a test message to the operator the TSQL is EXECUTE msdb.dbo.sp_notify_operator @name=N'Chris Auer',@body=N'wewqe' When I run that query I get Msg 14636, Level 16, State 1, Procedure sp_send_dbmail, Line 94 No global profile is configured. Specify a profile name in the @profile_name parameter. In the job log I have this Executing the query "EXECUTE msdb.dbo.sp_notify_operator @name=N'Chris Auer',@body=N'wewqe' " failed with the following error: "No global profile is configured. Specify a profile name in the @profile_name parameter.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. What is a global profile? I have already made the registry change to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\SQLServerAgent I made DatabaseMailProfile my default profile name in Database Mail and I made UseDatabaseMail = 1 Any ideas, thanks. This is driving me up a wall.' Chris Auer


Postby Lucky » Wed, 04 Jun 2008 23:48:57 GMT

Hello All,

While running the below query using openrowset function on SQL 2005
machine.. I am getting the below error..

Insert into myTable
			(serverId,LoginName,isNTName,isNTGroup, isNTuser)
myServer;Trusted_Connection=yes;','SELECT 1, name, isntname,
isntgroup,isntuser from master..syslogins')

Msg 7356, Level 16, State 1, Line 1
The OLE DB provider "SQLNCLI" for linked server "(null)" supplied
inconsistent metadata for a column. The column "(null)" (compile-time
ordinal 1) of object "SELECT 1, name, isntname, isntgroup,isntuser
from master..syslogins" was reported to have a
"DBCOLUMNFLAGS_ISNULLABLE" of 0 at compile time and 32 at run time.

This is not a issue with connectivity.. if I remove that '1' from the
select it works fine....

*this '1' can be replace with any number... this 1 is coming from a

Thanks in advance..



Postby Pawn » Wed, 04 Jun 2008 23:56:00 GMT

hey Lucky,
take a look at this "linked server "(null)" supplied inconsistent
metadata for a column" you're sending dynamic sql into an select from
openrowset(...) query? Try debugging it with a print statement to see
that "1" is indeed "1" and not some null value


Postby Lucky » Thu, 05 Jun 2008 00:08:33 GMT

This is the query that I am running... @sId is fetched from a
cursor... and this is running for more thn 200 instances..

'Insert into myTable
			(serverId,LoginName,isNTName,isNTGroup, isNTuser)
			 SELECT * FROM OPENROWSET(''SQLNCLI'''+',''Server= '+@sInstance
+';Trusted_Connection=yes;'''+','+'''SELECT '+cast(@sId as varchar)+',
name, isntname, isntgroup,isntuser from master..syslogins'')'


Postby Lucky » Thu, 05 Jun 2008 00:10:45 GMT

I am running below query into a cursor.. so @sId is fetched from

'Insert into myTable
(serverId,LoginName,isNTName,isNTGroup, isNTuser)
			 SELECT * FROM OPENROWSET(''SQLNCLI'''+',''Server= '+@sInstance
+';Trusted_Connection=yes;'''+','+'''SELECT '+cast(@sId as varchar)+',
name, isntname, isntgroup,isntuser from master..syslogins'')'


Postby Pawn » Thu, 05 Jun 2008 01:46:54 GMT

You may need to make that all a dynamic sql statement so you can add
your variable than execute your dynamic sql.

DECLARE @SQlSTMT AS nvarchar(8000)
@SQLSTMT = 'instert into mytable...
                       openreset(...' + @sInstance + ')


YRMV just a thought but variable don't always translate correctly into
their values in a string. better to chop then exectue IMHO. Also lets
you debug with PRINT @SQLSTMNT

Similar Threads:

1.Linked Server/OpenRowset errors accessing Access 97 database

I have an Access 97 database which resides on a local drive of a Windows 
Server 2003 that is running SQL Server 2005 Standard Edition.

I have SQL Server 2005 Developer Edition running on my laptop with XP and 
have found the following issues when using either Linked Server to the 
Access 97 database
or executing SELECT * FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0', '<uncpath 
access 97 mdb>';'admin';'',<tablename>)

On Windows 2003 Server
When using MSSMS expanding Tables node under default catalogs in the Linked 
Server using the connection from the same server the following error occurs:
Cannot initialize the data source object of OLE DB provider 
"Microsoft.Jet.OLEDB.4.0" for linked server "<Linked Name>". (Microsoft SQL 
Server, Error: 7303)

When executing openrowset the following error occurs:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" 
returned message "Cannot open database ''. It may not be a database that 
your application recognizes, or the file may be corrupt.".

Cannot initialize the data source object of OLE DB provider 
"Microsoft.Jet.OLEDB.4.0" for linked server "(null)".

However if I create the same Linked Server on my local database on my laptop 
I can successfully browse the tables and run the openrowset command.

So why does the Linked Server fail on the Windows Server 2003 and succeed on 
XP when both point to the same Access database on the Windows Server 2003?
I even installed Access 97 SR-2 on Windows Server 2003 to make sure the 
database was ok and it opened fine. I have scurried through on the net and 
most of the suggestions point to permissions which I can't see how it would 
apply in this instance.


2.OpenRowSet Error

Has anyone ever seen this error?  If so what did you do to fix

Cannot bulk load. Invalid column number in the format file

3.How to catch OPENROWSET error in stored procedure

Hi Steve,

You can't handle this error gracefully in T-SQL. Because the error is in an
external source and SQL Server doesn't know what it means, it goes safety
first and aborts the SQL batch. You have to handle it in your client

Jacco Schalkwijk
SQL Server MVP

"Steve" < XXXX@XXXXX.COM > wrote in message
news:125b01c3a872$0e0e9280$ XXXX@XXXXX.COM ...
> Hello,
> I have a stored procedure that performs an OPENROWSET to
> retrieve data from a dBase III DBF table. The location of
> the table can be different, so I pass the path as a
> parameter.
> The problem I am having is that occasionally the DBF file
> has corrupt records or feilds. This causes the OPENROWSET
> to fail. An example of the error messages I get when this
> happens is given below:
> Server: Msg 7399, Level 16, State 1, Line 1
> OLE DB provider 'MSDASQL' reported an error. The provider
> did not give any information about the error.
> OLE DB error trace [OLE/DB Provider 'MSDASQL'
> IColumnsInfo::GetColumnsInfo returned 0x80004005:  The
> provider did not give any information about the error.].
> I have tried using IF @@ERROR <> 0 but the stored
> procedure bombs out anyway.
> How do I detect this error within my stored procedure and
> handle it gracefully?
> Many thanks,
> Steve

4.OpenRowSet Error 7353

When running the following query:

I get the error:
Server: Msg 7353, Level 16, State 1, Line 1
OLE DB provider 'SQLOLEDB' supplied inconsistent metadata. An extra column 
was supplied during execution that was not found at compile time.

I am testing on 2 servers with 2 databases on both and it will succsefully 
run against the three other database. The query will also succed on the 
problem one when I query another table. 



I am having a strange problem. I have a stored procedure accessing remote 
server using OPENROWSET. When I edit this procedure in VSS.NET, I am getting 
an error 'OLE/DB provider returned message: New transaction cannot enlist in 
the specified transaction coordinator...' Stored procedure is below:

ALTER PROCEDURE dbo.vsp_test1

create table #tmp_pub_adv_agg(year int null,month int null,pubid int 
null,advid int null,impressions money null,

raw_clicks int null,unique_clicks int null,actions int null,

tot_cost money null,tot_revenue money null


INSERT INTO #tmp_pub_adv_agg(year,month,pubid,advid,impressions,




FROM OPENROWSET('SQLOLEDB',';'user_name';'password',

'select top 1 datepart(yy, Date) as year, datepart(mm, Date) as 

sum([Impressions]) as impressions,sum([Raw Clicks]) as 
raw_clicks,sum([Unique Clicks]) as unique_clicks,

sum([Actions]) as actions,sum([Total Cost]) as tot_cost,sum([Total Revenue]) 
as tot_revenue --,COUNT(*) c

from tmpadserv_warehouse.dbo.Accounting_RevenueReport

where datediff(mm,''01/01/2002'', [Date])>=0 AND 


GROUP BY datepart(yy, Date), datepart(mm, Date),pubid,advid

') a

select * from #tmp_pub_adv_agg


   I am able to edit/execute this procedure using Query Analyzer. I suspect 
that it has something to do with SET settings setup at connection level. I 
noticed that VSS.NET doesn't have set arithabort on set on connection level. 
But even if I reset this setting in QA, I am still able to edit this 
procedure. Am I on the right track? Even If I remove INSERT INTO part, I am 
still getting this error. I am not sure why SQL Server is trying to initiate 
distributed transaction when there is only SELECT statement.

    I am running SQL Server 2000 SP3.

Any help is greatly appreciated,


6. openrowset error in query analyzer

7. OPENROWSET error and SQL service restart

8. OpenRowSet error, can not kill hung spid



Who is online

Users browsing this forum: No registered users and 1 guest