Hi,
I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
drives and Windows Server 2003 sp1. I'm running a fairly
simple stored proc and I get the following error:
[Microsoft][ODBC SQL Server Driver][Shared Memory]
ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I've tried changing protocols in the client utiltiy (tcp
and named pipes) as suggested elsewhere. There are no
errors in the application log or the sql log.
Any ideas what is happening? The same query doesn't
crash on W2k Server/SQL Server 2k. It happens repeatedly,
but sometimes on the first, second or third execution of
the stored proc.
Thanks for any insight.Fred,
You could try to adjust couple of parameters of your SQL
Server:
network packet size (B):
default 4096, change it to eg. 1024
remote query timeout (s):
default 30 or 60, change it to eg. 600
You can see the current configuration with "sp_configure".
You could also design your procedure to interact
with "the client program" more frequently. One
possibility is to add rows like
PRINT 'Just sending something to the interface'
to your procedure. The idea is to keep the connection
alive.
I've tested these and it helped with some procedures (but
not with everyone).
If anyone has any other ideas, please let us know!
.mika
>--Original Message--
>Hi,
>I'm running SQL 2k SP3a on a 2.2P4 workstation with
250GB
>drives and Windows Server 2003 sp1. I'm running a
fairly
>simple stored proc and I get the following error:
>[Microsoft][ODBC SQL Server Driver][Shared Memory]
>ConnectionCheckForData (CheckforData()).
>Server: Msg 11, Level 16, State 1, Line 0
>General network error. Check your network documentation.
>Connection Broken
>I've tried changing protocols in the client utiltiy (tcp
>and named pipes) as suggested elsewhere. There are no
>errors in the application log or the sql log.
>Any ideas what is happening? The same query doesn't
>crash on W2k Server/SQL Server 2k. It happens
repeatedly,
>but sometimes on the first, second or third execution of
>the stored proc.
>Thanks for any insight.
>.
>|||Hi Fred,
Have had this problem recently, it seems a common error with quite a
few different symptoms. I will tell you our story, which may or may
not help.
For our case, we had this error executing dynamic SQL over ADO.NET,
but could also recreate the problem via Query Analyser using different
protocols.
We were using a complex query and got either your error or the
following:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken
We only got this error under certain conditions but could reproduce it
faithfully under those conditions.
Sniffing around the newsgroups, the general opinion was that if you
changed the query slightly, then in some cases the problem just "went
away".
I found 2 solutions to our problem.
Solution 1
Our query was using a view and by putting a "TOP 100 PERCENT" clause
in the view the problem went away. This is the solution we went with.
Solution 2
By using "OPTION(MERGE JOIN)" or "OPTION(LOOP JOIN)" in the SQL
statement, the problem went away. By forcing "OPTION(HASH JOIN)" the
problem re-appeared.
My theory is that merge joins were causing the problem (possibly in
conjunction with parallel query execution) but can't prove anything
because when you get this problem, you can't even get a query plan.
Looking at the query plan after using "TOP 100 PERCENT" I noticed that
there were no merge joins, although that proves nothing.
I wish you luck.
"Fred Jones" <anonymous@.discussions.microsoft.com> wrote in message news:<98f701c3ea99$2d681e80$a501280a@.phx.gbl>...
> Hi,
> I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
> drives and Windows Server 2003 sp1. I'm running a fairly
> simple stored proc and I get the following error:
> [Microsoft][ODBC SQL Server Driver][Shared Memory]
> ConnectionCheckForData (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I've tried changing protocols in the client utiltiy (tcp
> and named pipes) as suggested elsewhere. There are no
> errors in the application log or the sql log.
> Any ideas what is happening? The same query doesn't
> crash on W2k Server/SQL Server 2k. It happens repeatedly,
> but sometimes on the first, second or third execution of
> the stored proc.
> Thanks for any insight.
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Thursday, March 29, 2012
Error: ConnectionCheckForData (CheckforData())
Hi,
I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
drives and Windows Server 2003 sp1. I'm running a fairly
simple stored proc and I get the following error:
[Microsoft][ODBC SQL Server Driver][Shared Memory]
ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I've tried changing protocols in the client utiltiy (tcp
and named pipes) as suggested elsewhere. There are no
errors in the application log or the sql log.
Any ideas what is happening? The same query doesn't
crash on W2k Server/SQL Server 2k. It happens repeatedly,
but sometimes on the first, second or third execution of
the stored proc.
Thanks for any insight.Hi Fred,
Have had this problem recently, it seems a common error with quite a
few different symptoms. I will tell you our story, which may or may
not help.
For our case, we had this error executing dynamic SQL over ADO.NET,
but could also recreate the problem via Query Analyser using different
protocols.
We were using a complex query and got either your error or the
following:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken
We only got this error under certain conditions but could reproduce it
faithfully under those conditions.
Sniffing around the newsgroups, the general opinion was that if you
changed the query slightly, then in some cases the problem just "went
away".
I found 2 solutions to our problem.
Solution 1
Our query was using a view and by putting a "TOP 100 PERCENT" clause
in the view the problem went away. This is the solution we went with.
Solution 2
By using "OPTION(MERGE JOIN)" or "OPTION(LOOP JOIN)" in the SQL
statement, the problem went away. By forcing "OPTION(HASH JOIN)" the
problem re-appeared.
My theory is that merge joins were causing the problem (possibly in
conjunction with parallel query execution) but can't prove anything
because when you get this problem, you can't even get a query plan.
Looking at the query plan after using "TOP 100 PERCENT" I noticed that
there were no merge joins, although that proves nothing.
I wish you luck.
"Fred Jones" <anonymous@.discussions.microsoft.com> wrote in message news:<98f701c3ea99$2
d681e80$a501280a@.phx.gbl>...
> Hi,
> I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
> drives and Windows Server 2003 sp1. I'm running a fairly
> simple stored proc and I get the following error:
> [Microsoft][ODBC SQL Server Driver][Shared Memory]
> ConnectionCheckForData (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I've tried changing protocols in the client utiltiy (tcp
> and named pipes) as suggested elsewhere. There are no
> errors in the application log or the sql log.
> Any ideas what is happening? The same query doesn't
> crash on W2k Server/SQL Server 2k. It happens repeatedly,
> but sometimes on the first, second or third execution of
> the stored proc.
> Thanks for any insight.sql
I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
drives and Windows Server 2003 sp1. I'm running a fairly
simple stored proc and I get the following error:
[Microsoft][ODBC SQL Server Driver][Shared Memory]
ConnectionCheckForData (CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I've tried changing protocols in the client utiltiy (tcp
and named pipes) as suggested elsewhere. There are no
errors in the application log or the sql log.
Any ideas what is happening? The same query doesn't
crash on W2k Server/SQL Server 2k. It happens repeatedly,
but sometimes on the first, second or third execution of
the stored proc.
Thanks for any insight.Hi Fred,
Have had this problem recently, it seems a common error with quite a
few different symptoms. I will tell you our story, which may or may
not help.
For our case, we had this error executing dynamic SQL over ADO.NET,
but could also recreate the problem via Query Analyser using different
protocols.
We were using a complex query and got either your error or the
following:
ODBC: Msg 0, Level 19, State 1
SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005
EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Connection Broken
We only got this error under certain conditions but could reproduce it
faithfully under those conditions.
Sniffing around the newsgroups, the general opinion was that if you
changed the query slightly, then in some cases the problem just "went
away".
I found 2 solutions to our problem.
Solution 1
Our query was using a view and by putting a "TOP 100 PERCENT" clause
in the view the problem went away. This is the solution we went with.
Solution 2
By using "OPTION(MERGE JOIN)" or "OPTION(LOOP JOIN)" in the SQL
statement, the problem went away. By forcing "OPTION(HASH JOIN)" the
problem re-appeared.
My theory is that merge joins were causing the problem (possibly in
conjunction with parallel query execution) but can't prove anything
because when you get this problem, you can't even get a query plan.
Looking at the query plan after using "TOP 100 PERCENT" I noticed that
there were no merge joins, although that proves nothing.
I wish you luck.
"Fred Jones" <anonymous@.discussions.microsoft.com> wrote in message news:<98f701c3ea99$2
d681e80$a501280a@.phx.gbl>...
> Hi,
> I'm running SQL 2k SP3a on a 2.2P4 workstation with 250GB
> drives and Windows Server 2003 sp1. I'm running a fairly
> simple stored proc and I get the following error:
> [Microsoft][ODBC SQL Server Driver][Shared Memory]
> ConnectionCheckForData (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
> I've tried changing protocols in the client utiltiy (tcp
> and named pipes) as suggested elsewhere. There are no
> errors in the application log or the sql log.
> Any ideas what is happening? The same query doesn't
> crash on W2k Server/SQL Server 2k. It happens repeatedly,
> but sometimes on the first, second or third execution of
> the stored proc.
> Thanks for any insight.sql
Tuesday, March 27, 2012
error: CoCreate of DSO for BULKIMPORTSTREAM
Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.
Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.
Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
error: CoCreate of DSO for BULKIMPORTSTREAM
Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There reall
y
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when usin
g
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but n
ow
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There reall
y
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when usin
g
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but n
ow
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
error: CoCreate of DSO for BULKIMPORTSTREAM
Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There reall
y
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when usin
g
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but n
ow
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>sql
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There reall
y
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when usin
g
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but n
ow
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>sql
error: CoCreate of DSO for BULKIMPORTSTREAM
Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.
Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.
Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
error: CoCreate of DSO for BULKIMPORTSTREAM
Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.
Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.
Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
error: CoCreate of DSO for BULKIMPORTSTREAM
Hi,
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
Sql 2000 SP3a, Windows 2000 Enterprise, SP4
I've extensively searched through most means (google, microsoft,
newsgroups,etc) and really haven't found a definitive answer. There really
isn't any real answers. I run an ASP and most clients on one of the
production servers are experiencing this problem. My problem is when using
bulk insert every once in awhile we'll receive a
CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
error. Restarting the service used to take care of this for awhile, but now
this happens everyday.
Is there any special hotfixes for this or a final fix for this? Or any
other information on it. My next steps are to re-apply sp3a (sp4 hasn't
made it through testing yet), if that fails register the IMPPROV.dll ...
other than that... i'm out of ideas.
Please Please help!!!!
thanks in advance.Hi
This may be a ERR_DLL_INIT_FAILED error, in which case you may want to try
re-installing/updating MDAC, check system resources...
I am not sure if this is relevant! http://www.aspfaq.com/show.asp?id=2388
John
"Chris Trailer" wrote:
> Hi,
> Sql 2000 SP3a, Windows 2000 Enterprise, SP4
> I've extensively searched through most means (google, microsoft,
> newsgroups,etc) and really haven't found a definitive answer. There really
> isn't any real answers. I run an ASP and most clients on one of the
> production servers are experiencing this problem. My problem is when using
> bulk insert every once in awhile we'll receive a
> CoCreate of DSO for BULKIMPORTSTREAM returned 0x8007045a
> error. Restarting the service used to take care of this for awhile, but now
> this happens everyday.
> Is there any special hotfixes for this or a final fix for this? Or any
> other information on it. My next steps are to re-apply sp3a (sp4 hasn't
> made it through testing yet), if that fails register the IMPPROV.dll ...
> other than that... i'm out of ideas.
> Please Please help!!!!
> thanks in advance.
>
>
Monday, March 26, 2012
Error: 7105, Severity: 22, State: 6
it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>
Error: 7105, Severity: 22, State: 6
it is a SQL 2000 with SP4 on Windows server 2003 SP1.
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
>
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
>
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
>The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>> My SQL server logs this in Application log:
>> Error: 7105, Severity: 22, State: 6
>> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
>> for
>> a hot fix for this problem.
>> I believe this call is free because this is a bug. Can anyone confirm
>> this?
>> Thanks.
>>
>
"ME" <ME@.mail.com> wrote in message news:...
> My SQL server logs this in Application log:
>
> Error: 7105, Severity: 22, State: 6
> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>
> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
> for
> a hot fix for this problem.
>
> I believe this call is free because this is a bug. Can anyone confirm
> this?
> Thanks.
>
>The affinity mask is set as default. The server is 2 dual core CPUs. SQL
sees and uses all of 4 CPUs.
"ME" <ME@.mail.com> wrote in message
news:egU%23OuT$GHA.1224@.TK2MSFTNGP04.phx.gbl...
> it is a SQL 2000 with SP4 on Windows server 2003 SP1.
>
> "ME" <ME@.mail.com> wrote in message news:...
>> My SQL server logs this in Application log:
>> Error: 7105, Severity: 22, State: 6
>> Page (1:952446), slot 39 for text, ntext, or image node does not exist.
>> MS KB890755 http://support.microsoft.com/kb/890755 asked to contact MPSS
>> for
>> a hot fix for this problem.
>> I believe this call is free because this is a bug. Can anyone confirm
>> this?
>> Thanks.
>>
>
Error: 605, Severity: 21, State: 1
Environment:
SQL SERVER 2000 sp3 with security patch 818
Cluster environment: active-passive
HP running Windows 2003 with patches
Situation:
A stored procedure is running along with several other BCP
running.
I truned on DBCC TRACEON (818 -1)
I would like help with this error:
ERROR:
DATE/TIME: 10/1/2003 10:16:52 AM
DESCRIPTION: Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:3360903) in
database 'WaveAggDetach' belongs to
object 'aggTradePlanVolume', not to
object 'aggTradePlanVolumeInvoiced'.
COMMENT: (None)
JOB RUN: (None)Does the database come out clean from a DBCC CHECKDB?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Katherine" <kphelps@.oceanspray.com> wrote in message news:01ee01c3883e$1675e1c0$a401280a@.phx.gbl...
> Environment:
> SQL SERVER 2000 sp3 with security patch 818
> Cluster environment: active-passive
> HP running Windows 2003 with patches
> Situation:
> A stored procedure is running along with several other BCP
> running.
> I truned on DBCC TRACEON (818 -1)
> I would like help with this error:
> ERROR:
> DATE/TIME: 10/1/2003 10:16:52 AM
> DESCRIPTION: Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:3360903) in
> database 'WaveAggDetach' belongs to
> object 'aggTradePlanVolume', not to
> object 'aggTradePlanVolumeInvoiced'.
> COMMENT: (None)
> JOB RUN: (None)
>
>|||Does the stored procedure contain a cursor..?
If so try changing the cursor type to INSESNSITIVE.
Have a look at :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q156662
--
HTH
Ryan Waight, MCDBA, MCSE
"Katherine" <kphelps@.oceanspray.com> wrote in message
news:01ee01c3883e$1675e1c0$a401280a@.phx.gbl...
> Environment:
> SQL SERVER 2000 sp3 with security patch 818
> Cluster environment: active-passive
> HP running Windows 2003 with patches
> Situation:
> A stored procedure is running along with several other BCP
> running.
> I truned on DBCC TRACEON (818 -1)
> I would like help with this error:
> ERROR:
> DATE/TIME: 10/1/2003 10:16:52 AM
> DESCRIPTION: Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:3360903) in
> database 'WaveAggDetach' belongs to
> object 'aggTradePlanVolume', not to
> object 'aggTradePlanVolumeInvoiced'.
> COMMENT: (None)
> JOB RUN: (None)
>
>
SQL SERVER 2000 sp3 with security patch 818
Cluster environment: active-passive
HP running Windows 2003 with patches
Situation:
A stored procedure is running along with several other BCP
running.
I truned on DBCC TRACEON (818 -1)
I would like help with this error:
ERROR:
DATE/TIME: 10/1/2003 10:16:52 AM
DESCRIPTION: Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:3360903) in
database 'WaveAggDetach' belongs to
object 'aggTradePlanVolume', not to
object 'aggTradePlanVolumeInvoiced'.
COMMENT: (None)
JOB RUN: (None)Does the database come out clean from a DBCC CHECKDB?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"Katherine" <kphelps@.oceanspray.com> wrote in message news:01ee01c3883e$1675e1c0$a401280a@.phx.gbl...
> Environment:
> SQL SERVER 2000 sp3 with security patch 818
> Cluster environment: active-passive
> HP running Windows 2003 with patches
> Situation:
> A stored procedure is running along with several other BCP
> running.
> I truned on DBCC TRACEON (818 -1)
> I would like help with this error:
> ERROR:
> DATE/TIME: 10/1/2003 10:16:52 AM
> DESCRIPTION: Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:3360903) in
> database 'WaveAggDetach' belongs to
> object 'aggTradePlanVolume', not to
> object 'aggTradePlanVolumeInvoiced'.
> COMMENT: (None)
> JOB RUN: (None)
>
>|||Does the stored procedure contain a cursor..?
If so try changing the cursor type to INSESNSITIVE.
Have a look at :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q156662
--
HTH
Ryan Waight, MCDBA, MCSE
"Katherine" <kphelps@.oceanspray.com> wrote in message
news:01ee01c3883e$1675e1c0$a401280a@.phx.gbl...
> Environment:
> SQL SERVER 2000 sp3 with security patch 818
> Cluster environment: active-passive
> HP running Windows 2003 with patches
> Situation:
> A stored procedure is running along with several other BCP
> running.
> I truned on DBCC TRACEON (818 -1)
> I would like help with this error:
> ERROR:
> DATE/TIME: 10/1/2003 10:16:52 AM
> DESCRIPTION: Error: 605, Severity: 21, State: 1
> Attempt to fetch logical page (1:3360903) in
> database 'WaveAggDetach' belongs to
> object 'aggTradePlanVolume', not to
> object 'aggTradePlanVolumeInvoiced'.
> COMMENT: (None)
> JOB RUN: (None)
>
>
Thursday, March 22, 2012
Error: 3624 and event ID: 17055
We have a problem with our SQL Server.
the server is a windows 2K server SP3, running SQL Server
2K SP2. the problem we have is when we try to view JOBS
under Management. I get the following error.
Error: 3624
Location: rebcase.cpp:1378
Expression: m_offBeginVar < m_SizeRec
SPID: 54
Process ID: 1268
in the Event logs under application we get the following
Errors:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 01/12/2003
Time: 9:09:44:AM
User: MARCRIST\AdamB
Computer: ANIMAL
Description:
17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
---
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 01/12/2003
Time: 9:15:20:AM
User: MARCRIST\AdamB
Computer: ANIMAL
Description:
17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
both these refere to the MSDB, the only change we have
made recently is to install the Veratis SQL Server Agent.
I would be grateful for any help or advice.| We have a problem with our SQL Server.
| the server is a windows 2K server SP3, running SQL Server
| 2K SP2. the problem we have is when we try to view JOBS
| under Management. I get the following error.
|
| Error: 3624
| Location: rebcase.cpp:1378
| Expression: m_offBeginVar < m_SizeRec
| SPID: 54
| Process ID: 1268
|
| in the Event logs under application we get the following
| Errors:
|
| Event Type: Error
| Event Source: MSSQLSERVER
| Event Category: (2)
| Event ID: 17055
| Date: 01/12/2003
| Time: 9:09:44:AM
| User: MARCRIST\AdamB
| Computer: ANIMAL
| Description:
| 17066 :
| SQL Server Assertion: File: <recbase.cpp>, line=1378
| Failed Assertion = 'm_offBeginVar < m_SizeRec'.
|
| ---
|
| Event Type: Error
| Event Source: MSSQLSERVER
| Event Category: (2)
| Event ID: 17055
| Date: 01/12/2003
| Time: 9:15:20:AM
| User: MARCRIST\AdamB
| Computer: ANIMAL
| Description:
| 17066 :
| SQL Server Assertion: File: <recbase.cpp>, line=1378
| Failed Assertion = 'm_offBeginVar < m_SizeRec'.
|
|
| both these refere to the MSDB, the only change we have
| made recently is to install the Veratis SQL Server Agent.
|
| I would be grateful for any help or advice.
--
Hi Adam,
This might help:
FIX: An INSERT May Fail with a 3624 Error Message After a Failed Attempt to
Add New Table Column
http://support.microsoft.com/?id=317852
--
Eric Cárdenas
SQL Server support
the server is a windows 2K server SP3, running SQL Server
2K SP2. the problem we have is when we try to view JOBS
under Management. I get the following error.
Error: 3624
Location: rebcase.cpp:1378
Expression: m_offBeginVar < m_SizeRec
SPID: 54
Process ID: 1268
in the Event logs under application we get the following
Errors:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 01/12/2003
Time: 9:09:44:AM
User: MARCRIST\AdamB
Computer: ANIMAL
Description:
17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
---
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 01/12/2003
Time: 9:15:20:AM
User: MARCRIST\AdamB
Computer: ANIMAL
Description:
17066 :
SQL Server Assertion: File: <recbase.cpp>, line=1378
Failed Assertion = 'm_offBeginVar < m_SizeRec'.
both these refere to the MSDB, the only change we have
made recently is to install the Veratis SQL Server Agent.
I would be grateful for any help or advice.| We have a problem with our SQL Server.
| the server is a windows 2K server SP3, running SQL Server
| 2K SP2. the problem we have is when we try to view JOBS
| under Management. I get the following error.
|
| Error: 3624
| Location: rebcase.cpp:1378
| Expression: m_offBeginVar < m_SizeRec
| SPID: 54
| Process ID: 1268
|
| in the Event logs under application we get the following
| Errors:
|
| Event Type: Error
| Event Source: MSSQLSERVER
| Event Category: (2)
| Event ID: 17055
| Date: 01/12/2003
| Time: 9:09:44:AM
| User: MARCRIST\AdamB
| Computer: ANIMAL
| Description:
| 17066 :
| SQL Server Assertion: File: <recbase.cpp>, line=1378
| Failed Assertion = 'm_offBeginVar < m_SizeRec'.
|
| ---
|
| Event Type: Error
| Event Source: MSSQLSERVER
| Event Category: (2)
| Event ID: 17055
| Date: 01/12/2003
| Time: 9:15:20:AM
| User: MARCRIST\AdamB
| Computer: ANIMAL
| Description:
| 17066 :
| SQL Server Assertion: File: <recbase.cpp>, line=1378
| Failed Assertion = 'm_offBeginVar < m_SizeRec'.
|
|
| both these refere to the MSDB, the only change we have
| made recently is to install the Veratis SQL Server Agent.
|
| I would be grateful for any help or advice.
--
Hi Adam,
This might help:
FIX: An INSERT May Fail with a 3624 Error Message After a Failed Attempt to
Add New Table Column
http://support.microsoft.com/?id=317852
--
Eric Cárdenas
SQL Server support
Wednesday, March 21, 2012
Error: 18456 Severity: 14, State: 11
I have a SQL 2005 SP1 test server running Developer Edition on top of Windows Server 2003 SP1. We're testing out a 3rd party application that is using Windows Authentication to connect to SQL 2005. The SQL Error Log is saturated with the error message listed in the subject line. The text accompanying the message alternates between "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: <named pipe>]" and "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: xxx.xxx.xxx.xxx]".
There are two strange parts to this: 1) The application appears to be working fine on the surface, and, 2) The MYDOMAIN\TESTDA1$ account mentioned in the error text is not the user account that we are using to connect the application to SQL 2005. TESTDA1 is the server name that the 3rd party software is running remotely from.
I've looked up "error state 11" using the following resource:
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
It describes error states 11 and 12 as "Valid login but server access failure" but I'm not sure what that means. Why would SQL care about the computer account hosting the application?
Thanks in advance for any help.
From your description it seems like the 3rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.
Check the 3rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).
Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.
I hope this information helps,
-Raul Garcia
SDE/T
SQL Server Engine
|||
Thanks Raul. You were correct - the software was indeed trying to connect using the "Local System" account. We changed this to a domain account that had permission to login to SQL and now everything is working well. No more errors in the SQL Error Log.
Thanks again!
|||I have the same error message in my logs for SQL Server 2005. I've set up a report, gave both the user and the group she belongs to full access to the reports and Content Manager and Browser. She can go through the folders, but if she gets the report and clicks on the link to open the report (on http://servername/reports etc) she gets the error message "cannot create connection to data source 'databasename' and in the error logs it says: Error: 18456, Severity: 14, State: 11.
Login failed for user 'DOMAIN\User.Name'. [CLIENT: <local machine>]
where domain = an active directory (not local box) domain and User.Name is the actual name of the user who is in that domain.
The error being state 11 means Valid login but server access failure so where do I look to figure out why she can't get into the report? She's trying to access across the network so she's not physically logging onto that computer. Any idea what I need to check?
Thanks!
Linda
|||
Connect to SQL server using a sysadmin account and look if the Windows user has access to SQL Server. You can look first in sys.server_principals for example:
SELECT * FROM sys.server_principals
Go
And look for your Windows principal name directly, or for a group she belongs to and grants permission to connect. If you cannot find the proper entry, you can grant permission to connect to SQL Server by adding a login.
On the other hand, if the login exists, it may be possible that that particular user doesn’t have permissions to connect in the right endpoint. To see all the permissions on the endpoints you can run the following query:
SELECT endpnt.name,
suser_name(perms.grantee_principal_id) as grantee_principal,
perms.permission_name, perms.state_desc
FROM
sys.server_permissions perms,
sys.endpoints endpnt
WHERE
perms.class = 105
AND perms.major_id = endpnt.endpoint_id
go
If there is a permission missing for this principal, just grant the CONNECT permission at the correct endpoint.
-Raul Garcia
SDE/T
SQL Server Engine
|||Raul Garcia - MS wrote:
From your description it seems like the 3rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.
Check the 3rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).
Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.
I hope this information helps,
-Raul Garcia
SDE/T
SQL Server Engine
Hello there,
I got exactly the same scenario. Unfortunately I am not able to change the service account to any other thing than local system.
If I would like to add access to my database for the machine$ accounts, what exactly would I have to do ?
Could anyone give me a hint please ?
Thanks in advance
Gordon
|||You can use the CREATE LOGIN DDL to create the login for the machine account, for example:
CREATE LOGIN [DOMAIN\machine_name$] FROM WINDOWS
Let us know if this information helped and/or if you have any additional questions.
Thanks,
-Raul Garcia
SDE/T
SQL Server Engine
|||Thanks for the hint. This didn't solve my problem. Do I have to grant any special rights after creating those logins ?|||After creating the logins I forgot to map a role to the users for my database.
I just followed the instructions found in another article here :
navigate through Security > Logins > Properties > User Mapping > Choose the Database > Map the user to the database (you will see that he will get the public role by default)
Error: 18456 Severity: 14, State: 11
I have a SQL 2005 SP1 test server running Developer Edition on top of Windows Server 2003 SP1. We're testing out a 3rd party application that is using Windows Authentication to connect to SQL 2005. The SQL Error Log is saturated with the error message listed in the subject line. The text accompanying the message alternates between "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: <named pipe>]" and "Login failed for user 'MYDOMAIN\TESTDA1$'. [CLIENT: xxx.xxx.xxx.xxx]".
There are two strange parts to this: 1) The application appears to be working fine on the surface, and, 2) The MYDOMAIN\TESTDA1$ account mentioned in the error text is not the user account that we are using to connect the application to SQL 2005. TESTDA1 is the server name that the 3rd party software is running remotely from.
I've looked up "error state 11" using the following resource:
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
It describes error states 11 and 12 as "Valid login but server access failure" but I'm not sure what that means. Why would SQL care about the computer account hosting the application?
Thanks in advance for any help.
From your description it seems like the 3rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.
Check the 3rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).
Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.
I hope this information helps,
-Raul Garcia
SDE/T
SQL Server Engine
|||
Thanks Raul. You were correct - the software was indeed trying to connect using the "Local System" account. We changed this to a domain account that had permission to login to SQL and now everything is working well. No more errors in the SQL Error Log.
Thanks again!
|||I have the same error message in my logs for SQL Server 2005. I've set up a report, gave both the user and the group she belongs to full access to the reports and Content Manager and Browser. She can go through the folders, but if she gets the report and clicks on the link to open the report (on http://servername/reports etc) she gets the error message "cannot create connection to data source 'databasename' and in the error logs it says: Error: 18456, Severity: 14, State: 11.
Login failed for user 'DOMAIN\User.Name'. [CLIENT: <local machine>]
where domain = an active directory (not local box) domain and User.Name is the actual name of the user who is in that domain.
The error being state 11 means Valid login but server access failure so where do I look to figure out why she can't get into the report? She's trying to access across the network so she's not physically logging onto that computer. Any idea what I need to check?
Thanks!
Linda
|||
Connect to SQL server using a sysadmin account and look if the Windows user has access to SQL Server. You can look first in sys.server_principals for example:
SELECT * FROM sys.server_principals
Go
And look for your Windows principal name directly, or for a group she belongs to and grants permission to connect. If you cannot find the proper entry, you can grant permission to connect to SQL Server by adding a login.
On the other hand, if the login exists, it may be possible that that particular user doesn’t have permissions to connect in the right endpoint. To see all the permissions on the endpoints you can run the following query:
SELECT endpnt.name,
suser_name(perms.grantee_principal_id) as grantee_principal,
perms.permission_name, perms.state_desc
FROM
sys.server_permissions perms,
sys.endpoints endpnt
WHERE
perms.class = 105
AND perms.major_id = endpnt.endpoint_id
go
If there is a permission missing for this principal, just grant the CONNECT permission at the correct endpoint.
-Raul Garcia
SDE/T
SQL Server Engine
|||
Raul Garcia - MS wrote:
From your description it seems like the 3rd party software is attempting to connect to SQL Server using the service account credentials, it is most likely running under “Network Service”, “Local System” or another local account and that’s why when trying to access resources (in this case connect to SQL Server) it uses the machine account (<domain>\<machine_name>$), and as this account doesn’t have privileges to connect to SQL Server it fails.
Check the 3rd party product documentation, it may be possible that you need to run it using a domain account (I also recommend verifying with your domain administrator regarding your specific environment policies regarding running services under domain accounts).
Another potential workaround would be to grant permission to connect to this machine account, and granting it the minimum permissions required for the software you are testing. Bear in mind than any other service from the same machine will have the same privileges.
I hope this information helps,
-Raul Garcia
SDE/T
SQL Server Engine
Hello there,
I got exactly the same scenario. Unfortunately I am not able to change the service account to any other thing than local system.
If I would like to add access to my database for the machine$ accounts, what exactly would I have to do ?
Could anyone give me a hint please ?
Thanks in advance
Gordon
|||You can use the CREATE LOGIN DDL to create the login for the machine account, for example:
CREATE LOGIN [DOMAIN\machine_name$] FROM WINDOWS
Let us know if this information helped and/or if you have any additional questions.
Thanks,
-Raul Garcia
SDE/T
SQL Server Engine
|||Thanks for the hint. This didn't solve my problem. Do I have to grant any special rights after creating those logins ?|||After creating the logins I forgot to map a role to the users for my database.
I just followed the instructions found in another article here :
navigate through Security > Logins > Properties > User Mapping > Choose the Database > Map the user to the database (you will see that he will get the public role by default)
Error: 18456 Severity: 14, State: 10
I have SQL 2005 Expess installed on Windows Server 2003 SP1.
During Startup my application fails to start because of the unhandled exception thrown from Sql.Client:
My application is running as a service and is set to depend on SQL Server instance...
During the startup my app attempts to connect to the databes and it fails to do so,
after 30 retries (1second appart). SQL Server log has this error msg:
Error: 18456 "Severity: 14, State: 10"
Once the server has started, I cam manually start my application and it then sucesfully
opens a connection to the database.
What does this error mean?
Srdjan
Hi Srdjan,
Looks like you are getting a login failed error:
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
How is your app connecting to your db? If you are using Windows authentication, it could be that the service account you are using when running your app as a service does not have permission to log on to the database.
Sung
|||This error seems to only be reachable when using SQL Authentication, but I'm not sure what could cause it.
You can start SQL Server with "-y 18456", to produce a dump when the error occurs. As the dump will happen during authentication, the login password might appear in it, so you should use a bogus test password for the purpose of the creating this dump, just in case. Once you have the dump, please open a report at https://connect.microsoft.com/feedback/default.aspx?SiteID=68, attach the dump, and mention my name in the report, so it will get assigned to me.
If you can repro this issue with a smaller application that attempts the same connection on startup, you could attach that application as well, so we can attempt to repro the issue in our labs.
Thanks
Laurentiu
|||tried a couple of times to post a bug report...
but getting errors from the web site.
Anyway, new information:
if I run using Windows authentication, error is the ame but
state is now 16.
Still, after loging in - I have no problem starting the same service that failed during automatic startup.
Even the simplest windows servce that just opens connection
behaves the same...
Thanks,
Srdjan|||
State 16 means there was an error in determining the database to be used by the connection. Can you still connect if you start your application manually?
Thanks
Laurentiu
During Startup my application fails to start because of the unhandled exception thrown from Sql.Client:
System.Data.SqlClient.SqlException: Cannot open database "Db_260" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\SYSTEM'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
Also here are couple of lines from the SQL errorlog file during machine startup:
2006-07-15 13:56:39.67 spid8s Clearing tempdb database.
2006-07-15 13:56:39.71 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.71 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:39.95 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.95 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:40.34 spid8s Starting up database 'tempdb'.
2006-07-15 13:56:40.45 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-07-15 13:56:40.46 spid11s The Service Broker protocol transport is disabled or not configured.
2006-07-15 13:56:40.46 spid11s The Database Mirroring protocol transport is disabled or not configured.
2006-07-15 13:56:40.56 spid11s Service Broker manager has started.
2006-07-15 13:56:44.78 spid51 Starting up database 'ReportServer$TRBR'.
2006-07-15 13:56:45.09 spid52 Starting up database 'Db_260'.
2006-07-15 13:57:38.96 Server Server resumed execution after being idle 25 seconds: user activity awakened the server. This is an informational message only. No user action is required.
Srdjan|||
You are trying to connect to database Db_260, but the database has not been started up yet. If you will look in the log, you'll see that the server is accepting connections before starting up the database Db_260, so the requests that you make before the database startup will fail. You should take this into account and retry to connect after a delay, to give time to the server to start up the database.
Thanks
Laurentiu
My code actually retries until it gets connection succesfully.
The problem is that after a couple of failed atempts, I actally get a success, but then it is the the next attempt to connect to database fails with the exception:
Login Failed for user 'NT AUTHORITY SYSTEM'...
Now, I've tried to postpone the first call to database for up to
3 minutes (more is not practical) and nothing really changes,
I get the same behaviour (System.Data.SqlClient.SqlException) on the second call to database...
Srdjan
|||
Are you saying that you get login failure errors after the database is started up? The log excerpt from your previous message doesn't show that. Can you post your errorlog from beginning up to and including the first couple of login failures that you get AFTER the Db_260 database was started up?
Thanks
Laurentiu
I managed to get around this problem...
My original code that was checking if SQL is ready was simply opening a connection but didn't execute any dabase commands.
For some reason at one point one of these attempts would successed, but then on the first real database access, exception was thrown.
So, I now do retries on the first real access to datbase and that seems to work.
I appreciate your help.
Srdjan
|||
Hi Laurentiu,
I am having a similar problem when after programmatically creating a database I try to create a table, if I do not put an arbitrarily large delay before issuing the create table statement, I get this same "Error: 18456, Severity: 14, State: 16."
Is there any way to issue a SQL statement and block on the call until a new database has been fully initialized and started before continuing? Alternatively, is there a way to get a callback once the DB is online?, Finally, if neither of the previous are possible, is there any entry in the master DB that one could poll to see when the new DB is up and running? I've tried the ovbious state in sys.databases, and Database.Status in DMO with no luck.
Any ideas? Thanks in advance!
GDM
|||If you are getting a login failed message, it sounds like you are executing the CREATE DATABASE and CREATE TABLE statements on two different connections. Have you considered executing these statements using the same connection? If you would execute the CREATE TABLE after the CREATE DATABASE, on the same connection, you would not see such a failure.
The state you can query is state_desc in sys.databases - if it is ONLINE, it means the database was started.
Thanks
Laurentiu
Start->Run...->services.msc
Then go to the SQL Server service and stop it. Then Click <Properties> and in the <Start Parameters> field enter -y 18456. You can then click <Start> to restart the server with that parameter and then press cancel to exit without saving the parameter, so that future restarts won't use it. If you press OK, then the server will be restarted with that parameter - you probably don't want that.
Thanks
Laurentiu
Ok I have an issue here....I am trying to do a full system recovery and this is what I am getting...
File/minint/system32/biosinfo.inf could not be loaded the error is code 14 ?
And I do NOT have the Windows XP Disk either...so if theres a way around this please by all means help me .......
can some please help me with this please
Error: 18456 Severity: 14, State: 10
I have SQL 2005 Expess installed on Windows Server 2003 SP1.
During Startup my application fails to start because of the unhandled exception thrown from Sql.Client:
My application is running as a service and is set to depend on SQL Server instance...
During the startup my app attempts to connect to the databes and it fails to do so,
after 30 retries (1second appart). SQL Server log has this error msg:
Error: 18456 "Severity: 14, State: 10"
Once the server has started, I cam manually start my application and it then sucesfully
opens a connection to the database.
What does this error mean?
Srdjan
Hi Srdjan,
Looks like you are getting a login failed error:
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx
How is your app connecting to your db? If you are using Windows authentication, it could be that the service account you are using when running your app as a service does not have permission to log on to the database.
Sung
|||This error seems to only be reachable when using SQL Authentication, but I'm not sure what could cause it.
You can start SQL Server with "-y 18456", to produce a dump when the error occurs. As the dump will happen during authentication, the login password might appear in it, so you should use a bogus test password for the purpose of the creating this dump, just in case. Once you have the dump, please open a report at https://connect.microsoft.com/feedback/default.aspx?SiteID=68, attach the dump, and mention my name in the report, so it will get assigned to me.
If you can repro this issue with a smaller application that attempts the same connection on startup, you could attach that application as well, so we can attempt to repro the issue in our labs.
Thanks
Laurentiu
|||tried a couple of times to post a bug report...
but getting errors from the web site.
Anyway, new information:
if I run using Windows authentication, error is the ame but
state is now 16.
Still, after loging in - I have no problem starting the same service that failed during automatic startup.
Even the simplest windows servce that just opens connection
behaves the same...
Thanks,
Srdjan|||
State 16 means there was an error in determining the database to be used by the connection. Can you still connect if you start your application manually?
Thanks
Laurentiu
During Startup my application fails to start because of the unhandled exception thrown from Sql.Client:
System.Data.SqlClient.SqlException: Cannot open database "Db_260" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\SYSTEM'.
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
Also here are couple of lines from the SQL errorlog file during machine startup:
2006-07-15 13:56:39.67 spid8s Clearing tempdb database.
2006-07-15 13:56:39.71 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.71 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:39.95 Logon Error: 18456, Severity: 14, State: 16.
2006-07-15 13:56:39.95 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-15 13:56:40.34 spid8s Starting up database 'tempdb'.
2006-07-15 13:56:40.45 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-07-15 13:56:40.46 spid11s The Service Broker protocol transport is disabled or not configured.
2006-07-15 13:56:40.46 spid11s The Database Mirroring protocol transport is disabled or not configured.
2006-07-15 13:56:40.56 spid11s Service Broker manager has started.
2006-07-15 13:56:44.78 spid51 Starting up database 'ReportServer$TRBR'.
2006-07-15 13:56:45.09 spid52 Starting up database 'Db_260'.
2006-07-15 13:57:38.96 Server Server resumed execution after being idle 25 seconds: user activity awakened the server. This is an informational message only. No user action is required.
Srdjan|||
You are trying to connect to database Db_260, but the database has not been started up yet. If you will look in the log, you'll see that the server is accepting connections before starting up the database Db_260, so the requests that you make before the database startup will fail. You should take this into account and retry to connect after a delay, to give time to the server to start up the database.
Thanks
Laurentiu
My code actually retries until it gets connection succesfully.
The problem is that after a couple of failed atempts, I actally get a success, but then it is the the next attempt to connect to database fails with the exception:
Login Failed for user 'NT AUTHORITY SYSTEM'...
Now, I've tried to postpone the first call to database for up to
3 minutes (more is not practical) and nothing really changes,
I get the same behaviour (System.Data.SqlClient.SqlException) on the second call to database...
Srdjan
|||
Are you saying that you get login failure errors after the database is started up? The log excerpt from your previous message doesn't show that. Can you post your errorlog from beginning up to and including the first couple of login failures that you get AFTER the Db_260 database was started up?
Thanks
Laurentiu
I managed to get around this problem...
My original code that was checking if SQL is ready was simply opening a connection but didn't execute any dabase commands.
For some reason at one point one of these attempts would successed, but then on the first real database access, exception was thrown.
So, I now do retries on the first real access to datbase and that seems to work.
I appreciate your help.
Srdjan
|||
Hi Laurentiu,
I am having a similar problem when after programmatically creating a database I try to create a table, if I do not put an arbitrarily large delay before issuing the create table statement, I get this same "Error: 18456, Severity: 14, State: 16."
Is there any way to issue a SQL statement and block on the call until a new database has been fully initialized and started before continuing? Alternatively, is there a way to get a callback once the DB is online?, Finally, if neither of the previous are possible, is there any entry in the master DB that one could poll to see when the new DB is up and running? I've tried the ovbious state in sys.databases, and Database.Status in DMO with no luck.
Any ideas? Thanks in advance!
GDM
|||If you are getting a login failed message, it sounds like you are executing the CREATE DATABASE and CREATE TABLE statements on two different connections. Have you considered executing these statements using the same connection? If you would execute the CREATE TABLE after the CREATE DATABASE, on the same connection, you would not see such a failure.
The state you can query is state_desc in sys.databases - if it is ONLINE, it means the database was started.
Thanks
Laurentiu
Start->Run...->services.msc
Then go to the SQL Server service and stop it. Then Click <Properties> and in the <Start Parameters> field enter -y 18456. You can then click <Start> to restart the server with that parameter and then press cancel to exit without saving the parameter, so that future restarts won't use it. If you press OK, then the server will be restarted with that parameter - you probably don't want that.
Thanks
Laurentiu
Ok I have an issue here....I am trying to do a full system recovery and this is what I am getting...
File/minint/system32/biosinfo.inf could not be loaded the error is code 14 ?
And I do NOT have the Windows XP Disk either...so if theres a way around this please by all means help me .......
can some please help me with this please
sql
error: 18452; very urgent
We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethihttp://support.microsoft.com/default.aspx?scid=kb;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegroups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethihttp://support.microsoft.com/default.aspx?scid=kb;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegroups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>
error: 18452; very urgent
We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login fai
led for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethihttp://support.microsoft.com/defaul...kb;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegroups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login f
ailed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login fai
led for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethihttp://support.microsoft.com/defaul...kb;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegroups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login f
ailed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>
error: 18452; very urgent
We have 2 failover servers and one client in our test environment. We
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethi
http://support.microsoft.com/default...b;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegro ups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>
have all the three configured in mixed mode authentication(windows +
sql server authentication). But when we are failing over from 1st
server to 2nd one, we are getting the following error message,
'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'null'. Reason: Not associated with a trusted SQL server
connection.'
I got some clue.
For instance we have ser1 and ser2 as clusters. I registered both in
the client's EM. Now what I did was, I made ser1 to run and stopped sql
service in ser2 (active/passive) through failover. Now in the client's
EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
I failed over to ser2 ( so sql service in ser1 is stopped). But now I
can still be able to access ser1 and also I can access ser2, even I'm
able to open query analyzer in ser1 through EM.But when I try to open
query analyzer directly, it is giving the same error message. ser1 is
the virtual name given to both ser1 and ser2. So I think when
connecting through EM, failover is occuring fine.I'm just wondering why
is this happening only with dsn. Can anybody help me?
Thanks,
Preethi
http://support.microsoft.com/default...b;en-us;555332
"sqldbapree" <mohanpreethi0125@.gmail.com> wrote in message
news:1129898680.495504.25600@.g44g2000cwa.googlegro ups.com...
> We have 2 failover servers and one client in our test environment. We
> have all the three configured in mixed mode authentication(windows +
> sql server authentication). But when we are failing over from 1st
> server to 2nd one, we are getting the following error message,
> 'Unable to connected to server xxxx: Server : Msg 18452, Level 16,
> State 1 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
> user 'null'. Reason: Not associated with a trusted SQL server
> connection.'
> I got some clue.
> For instance we have ser1 and ser2 as clusters. I registered both in
> the client's EM. Now what I did was, I made ser1 to run and stopped sql
> service in ser2 (active/passive) through failover. Now in the client's
> EM I'm able to open ser1 and I cannot access ser2. Now what I did was,
> I failed over to ser2 ( so sql service in ser1 is stopped). But now I
> can still be able to access ser1 and also I can access ser2, even I'm
> able to open query analyzer in ser1 through EM.But when I try to open
> query analyzer directly, it is giving the same error message. ser1 is
> the virtual name given to both ser1 and ser2. So I think when
> connecting through EM, failover is occuring fine.I'm just wondering why
> is this happening only with dsn. Can anybody help me?
> Thanks,
> Preethi
>
Error: 17883 - problem with Scheduler
Hello!
We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
SAN components. Just recently, we got an error message in SQL Server error
log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding on
Scheduler 0.'
I found a couple of articles on MS website:
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/810885
http://support.microsoft.com/kb/890637
One of the articles refers to High-End disk system as possible source. I am
wondering whether anyone had similar problem and had been able to detect the
cause of this type of error message.
Thanks,
Igor
Hi
We had the issue as our SANs are very fast.
Once we identified the problem, we went to hotfix build 818 and then 952 and
as soon as SP4 came out, we applied it.
The problems do not occur anymore.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hello!
> We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
> SAN components. Just recently, we got an error message in SQL Server error
> log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding
> on Scheduler 0.'
> I found a couple of articles on MS website:
> http://support.microsoft.com/kb/319892
> http://support.microsoft.com/kb/810885
> http://support.microsoft.com/kb/890637
> One of the articles refers to High-End disk system as possible source. I
> am wondering whether anyone had similar problem and had been able to
> detect the cause of this type of error message.
>
> Thanks,
> Igor
>
|||Did you happen to remember when exactly problem disappear? We are on hotfix
818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some AWE
related issues with SP4 that's why I am reluctant to install SP4.
Thanks,
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hi
> We had the issue as our SANs are very fast.
> Once we identified the problem, we went to hotfix build 818 and then 952
> and as soon as SP4 came out, we applied it.
> The problems do not occur anymore.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>
|||I think there is a hot fix after SP4 for this issue.
It changes SQL version to 8.00.2040
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Did you happen to remember when exactly problem disappear? We are on
> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
> AWE related issues with SP4 that's why I am reluctant to install SP4.
> Thanks,
> Igor
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>
|||Thanks,Mike!
Igor
"ME" <ME@.hotmail.com> wrote in message
news:%239oT6TLfFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I think there is a hot fix after SP4 for this issue.
> It changes SQL version to 8.00.2040
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
>
We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
SAN components. Just recently, we got an error message in SQL Server error
log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding on
Scheduler 0.'
I found a couple of articles on MS website:
http://support.microsoft.com/kb/319892
http://support.microsoft.com/kb/810885
http://support.microsoft.com/kb/890637
One of the articles refers to High-End disk system as possible source. I am
wondering whether anyone had similar problem and had been able to detect the
cause of this type of error message.
Thanks,
Igor
Hi
We had the issue as our SANs are very fast.
Once we identified the problem, we went to hotfix build 818 and then 952 and
as soon as SP4 came out, we applied it.
The problems do not occur anymore.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
> Hello!
> We are running SQL Server 200 SP Enterprise Edition on Windows 2003 with
> SAN components. Just recently, we got an error message in SQL Server error
> log:'Process 53:0 (ac8) UMS Context 0x11EF2ED8 appears to be non-yielding
> on Scheduler 0.'
> I found a couple of articles on MS website:
> http://support.microsoft.com/kb/319892
> http://support.microsoft.com/kb/810885
> http://support.microsoft.com/kb/890637
> One of the articles refers to High-End disk system as possible source. I
> am wondering whether anyone had similar problem and had been able to
> detect the cause of this type of error message.
>
> Thanks,
> Igor
>
|||Did you happen to remember when exactly problem disappear? We are on hotfix
818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some AWE
related issues with SP4 that's why I am reluctant to install SP4.
Thanks,
Igor
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
> Hi
> We had the issue as our SANs are very fast.
> Once we identified the problem, we went to hotfix build 818 and then 952
> and as soon as SP4 came out, we applied it.
> The problems do not occur anymore.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:eidXJjBfFHA.1416@.TK2MSFTNGP09.phx.gbl...
>
|||I think there is a hot fix after SP4 for this issue.
It changes SQL version to 8.00.2040
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
> Did you happen to remember when exactly problem disappear? We are on
> hotfix 818 (Microsoft SQL Server 2000 - 8.00.818). I know there are some
> AWE related issues with SP4 that's why I am reluctant to install SP4.
> Thanks,
> Igor
>
> "Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
> news:%23P4CI1BfFHA.1148@.TK2MSFTNGP12.phx.gbl...
>
|||Thanks,Mike!
Igor
"ME" <ME@.hotmail.com> wrote in message
news:%239oT6TLfFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I think there is a hot fix after SP4 for this issue.
> It changes SQL version to 8.00.2040
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:%23hTvPqDfFHA.2152@.TK2MSFTNGP14.phx.gbl...
>
Subscribe to:
Posts (Atom)