Error while connection: state

Showing posts with label state. Show all posts

Monday, March 26, 2012

Error: 9003, Severity: 20, State: 1

Hi All,

I'm stuck with "Error: 9003, Severity: 20, State: 1" in MS-SQL Server 2000..I dont want to re-install the sql server ..since..i have other dependent s/w..!
I guess..the Master DB is corrupted...!!

When I tried to rebuild the Master db, i dont find the exe for rebuilding...it...!!

================================================== =======
Error log:
---

C:\Program Files\Microsoft SQL Server\MSSQL\Binn>sqlservr -c -T3608
2005-12-05 09:56:50.81 server Microsoft SQL Server 2000 - 8.00.760 (Intel X8
6)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

2005-12-05 09:56:50.82 server Copyright (C) 1988-2002 Microsoft Corporation.

2005-12-05 09:56:50.82 server All rights reserved.
2005-12-05 09:56:50.82 server Server Process ID is 5548.
2005-12-05 09:56:50.82 server Logging SQL Server messages in file 'C:\Program
Files\Microsoft SQL Server\MSSQL\log\ERRORLOG'.
2005-12-05 09:56:50.84 server SQL Server is starting at priority class 'norma
l'(2 CPUs detected).
2005-12-05 09:56:50.88 server SQL Server configured for thread mode processin
g.
2005-12-05 09:56:50.90 server Using dynamic lock allocation. [2500] Lock Bloc
ks, [5000] Lock Owner Blocks.
2005-12-05 09:56:50.90 server Attempting to initialize Distributed Transactio
n Coordinator.
2005-12-05 09:56:52.93 spid4 Recovering only master database
2005-12-05 09:56:52.95 spid4 Starting up database 'master'.
2005-12-05 09:56:53.07 spid4 Error: 9003, Severity: 20, State: 1.
2005-12-05 09:56:53.07 spid4 Cannot recover the master database. Exiting.Issue resolved...!!

Just the way i wanted..!Thanks Rashmi..!!

Refer to this Post by rashmi (http://dbforums.com/t389015.html)...!

Cheers,
Prakash

Resolution is mentioned below:
================================================== ========
Rashmi -Lsqms]
Guest Posts: n/a

Re: Urgent help needed!

------------------------

Even though the SQL Server is installed on D: the default location of the databases
seems to be set to C:, so its looking in 'C:\Program Files\Microsoft SQL
Server\MSSQL\data\ folder for model.mdf' and modellog.ldf. You would have to make
sure that these are in the right location for the server to start.

Otherwise you can start the server from command prompt by

sqlservr -c -T3608

This will prevent recovery of all databases except model.

Usually the resolution is to rebuild the master databases

To rebuild the master database 1. Shutdown SQL Server; then run Rebuildm.exe in the
Program Files\Microsoft SQL Server\ MSSQL\ Binn directory. 2. Click Browse. 3. Select
the \Data folder on the Microsoft SQL Server? compact disc or in the shared network
directory from which SQL Server was installed; then click OK. 4. Click Settings.
Verify or change the character set, sort order, and Unicode collation used for the
master database and all other databases. 5. The default character set, sort order,
and Unicode collation are shown initially, which may not be the values selected
during SQL Server Setup. You can select the same combination used earlier or select a
new combination; then click OK. 6. Click Rebuild. The Rebuild Master utility
reinstalls the master database.

In the process you can make sure the data folder is set to D

Later , after rebuilding master you will have to re-attach all the user databases
using sp_attach_db

You also will lose all the logins and will have to recreate them , and then relink
the database users using sp_change_users_login

Regards,

Rashmi

This posting is provided "AS IS" with no warranties, and confers no rights.

Get Secure! - www.microsoft.com/security

Error: 8646, Severity: 21, State: 1

We are seeing this error. It has only happened one time. Does anyone
know what could be causing this other than a Latin1_General_BIN collation.
TIA,
-Ben
The index entry for row ID was not found in index ID 3, of table
1285579618, in database 'db'..
Error: 8646, Severity: 21, State: 1Run a DBCC CHECKDB against your database and fix any errors
"Ben" <bmilliron@.gmail.com> wrote in message
news:eiRDobEZEHA.3892@.TK2MSFTNGP09.phx.gbl...
> We are seeing this error. It has only happened one time. Does anyone
> know what could be causing this other than a Latin1_General_BIN collation.
> TIA,
> -Ben
> The index entry for row ID was not found in index ID 3, of table
> 1285579618, in database 'db'..
> Error: 8646, Severity: 21, State: 1

Error: 8646, Severity: 21, State: 1

We are seeing this error. It has only happened one time. Does anyone
know what could be causing this other than a Latin1_General_BIN collation.
TIA,
-Ben
The index entry for row ID was not found in index ID 3, of table
1285579618, in database 'db'..
Error: 8646, Severity: 21, State: 1
Run a DBCC CHECKDB against your database and fix any errors
"Ben" <bmilliron@.gmail.com> wrote in message
news:eiRDobEZEHA.3892@.TK2MSFTNGP09.phx.gbl...
> We are seeing this error. It has only happened one time. Does anyone
> know what could be causing this other than a Latin1_General_BIN collation.
> TIA,
> -Ben
> The index entry for row ID was not found in index ID 3, of table
> 1285579618, in database 'db'..
> Error: 8646, Severity: 21, State: 1

Error: 8624 Internal Query Processor Error: The query processor could not produce a query plan.

SQL Server 2005 9.0.3161 on Win 2k3 R2

I receive the following error:

"Error: 8624, Severity: 16, State: 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services."

I have traced this to an insert statement that executes as part of a stored procedure.

INSERT INTO ledger (journal__id, account__id,account_recv_info__id,amount)

VALUES (@.journal_id, @.acct_id, @.acct_recv_id, @.amount)

There is also an auto-increment column called id. There are FK contraints on all of the columns ending in "__id". I have found that if I remove the contraint on account__id the procedure will execute without error. None of the other constraints seem to make a difference. Of course I don't want to remove this key because it is important to the database integrity and should not be causing problems, but apparently it confuses the optimizer.

Also, the strange thing is that I can get the procedure to execute without error when I run it directly through management studio, but I receive the error when executing from .NET code or anything using ODBC (Access).

I'd suggest calling PSS. It does sound like a bug here.

|||

I ran into this exact problem today, and it turned out to be related to a catalog being inconsistent, when we performed a migration from a SQL 2000 server to a SQL 2005 server, by restoring a backup . There was a foreign key constraint that was not functioning correctly following the migration and that was causing the error to show up.

We had restored the SQL 2000 backup to a 2005 server, then changed the compatability mode from 80 to 90, then updated statistics. We did not however, run the DBCC following all of that. We had run tests prior to the migration, but this hadn't showed up as an issue until the day of the migration. As a matter of fact, we had run DBCC's on the SQL 2000 database and things were fine. We checked the backup file, and that was fine. The problem was in some part of the page migrations that happen within the engine itself. Maybe this was a page alignment issue, whereby a given catalog page was in a decent state for migration when we were testing, but changed it's alignment on a given page between the time we tested and the time that we migrated. Who know....that's just my speculation.

The error from running a simple insert statement looks like this:

Msg 8624, Level 16, State 1, Line 1

Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

The error from the DBCC CHECKDB looks like this:

Msg 8992, Level 16, State 1, Line 1

Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=238623893,key_index_id=3) of row (object_id=951674438) in sys.foreign_keys does not have a matching row (object_id=238623893,index_id=3) in sys.indexes.

CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

This lead us to the conclusion that we could drop the FK and recreate it, and have everything work. And, it did.

The moral of the story, like it's been said many times...run DBCC's after restores when going from SQL 2000 to SQL 2005.

Hope this helps someone else in the future.

-- Don

|||

I consulted tech support. It was finally classified as a bug. The database was in 80 compatibility and changing it to 90 made the problem go away. The other work around was to set arithabort on. This explained why it worked from management studio and not anywhere else. Apparently management studio has arithabort set to on by default. The following is the case closure confirmation from the MS engineer:

PROBLEM:

=======

An insert query to a table that has foreign key references cannot generate a plan with error 8624 when arithabort is set to be off.

Server: Msg 8624, Level 16, State 1, Line 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

AGREED UPON CRITERIA FOR RESOLUTION:

===========================

Investigate root cause

CAUSE:

=====

This issue appears to be related to the fact database compatibility is set to 80.I have filed a product bug for tracking purpose

RESOLUTION:

===========

Setting database compatibility to be 90 resolved the issue

Error: 8624 Internal Query Processor Error: The query processor could not produce a query plan.

SQL Server 2005 9.0.3161 on Win 2k3 R2

I receive the following error:

"Error: 8624, Severity: 16, State: 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services."

I have traced this to an insert statement that executes as part of a stored procedure.

INSERTINTO ledger (journal__id, account__id,account_recv_info__id,amount)

VALUES(@.journal_id, @.acct_id, @.acct_recv_id, @.amount)

I'd suggest calling PSS. It does sound like a bug here.

|||

The error from running a simple insert statement looks like this:

Msg 8624, Level 16, State 1, Line 1

Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

The error from the DBCC CHECKDB looks like this:

Msg 8992, Level 16, State 1, Line 1

CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.

This lead us to the conclusion that we could drop the FK and recreate it, and have everything work. And, it did.

The moral of the story, like it's been said many times...run DBCC's after restores when going from SQL 2000 to SQL 2005.

Hope this helps someone else in the future.

-- Don

|||

PROBLEM:

=======

An insert query to a table that has foreign key references cannot generate a plan with error 8624 when arithabort is set to be off.

Server: Msg 8624, Level 16, State 1, Line 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.

AGREED UPON CRITERIA FOR RESOLUTION:

===========================

Investigate root cause

CAUSE:

=====

This issue appears to be related to the fact database compatibility is set to 80.I have filed a product bug for tracking purpose

RESOLUTION:

===========

Setting database compatibility to be 90 resolved the issue

Error: 823

Hi,

I am I notice this message on the event logs.

Error: 823, Severity: 24, State: 2
I/O error (bad page ID) detected during read at offset 0x000003182da000 in file 'e:\sqlData\FSDocsOnline.mdf'.

If I was to run:

DBCC CHECKDB
( 'database_name'
[ , NOINDEX
| { REPAIR_ALLOW_DATA_LOSS
| REPAIR_FAST
| REPAIR_REBUILD
} ]
) [ WITH { [ ALL_ERRORMSGS ]
[ , [ NO_INFOMSGS ] ]
[ , [ TABLOCK ] ]
[ , [ ESTIMATEONLY ] ]
[ , [ PHYSICAL_ONLY ] ]
}
]

Will it fix my problem or will I need to restore the database. Which have no backup.

LystraYou might be able to fix the database, but I'd be more comfortable with either restoring a backup, or better yet trying to copy the data out one table at a time (saving the backup for a last resort).

A lot depends on just what is broken and how it broke. I don't have a good way to guess what caused the problem, so I'd assume that it will be tough to fix.

-PatP|||Well there is no Backup for this database. The last time it was backup was in 10/03. And the files have since been deleted.

In order to copy the time out one at a time what would this accomplish. And to do this should I use the bCP out method?

Thanking you in advance.

Lystra|||Brett would say yes to the BCP part.|||The method you use for the copy isn't really significant. You can BCP to flat files, or you can just use an INSERT if both databases are on the same server, or DTS if they are on different servers.

The trick is to copy data until the copy fails (due to the problem with the disk), then find a way to resume the copy just past the problem. The easiest way to do this is using PK values to copy what you can, then move a few PK values higher and start again. If there was only one flaw, then you can copy from the low PK values up, then from the high PK values down and you will have all of the recoverable data. If you have more than one flaw, then you'll have to fuss with the copy a bit, trying to "jump" the flaws.

-PatPsql

Error: 7886, Severity: 20, State: 1.

Hi All

I am seeing this error being logged in my SQL 2005 Ent machine

A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.

It seems to be arising out of a read of a text column.

Any info on this will be appreciated. Thanks

K T

You're not running CTP version, right?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=233339&SiteID=1|||

Its build 9.0.2153

|||

Hi Kts,

Do you use Row versioning in you database?

I waiting for your answer.

Regards,

|||

No !

|||

Hi kts,

What you TRANSACTION ISOLATION LEVEL do you run the code?

Can you post the query here?

Regards,

|||

Like the message says READ UNCOMMITTED . its actually just a select with NO LOCK. The problem is I can only guess which proc it is but not know for sure as I am not able to recreate the problem manually.

|||

Ah, you use 'nolock' hint. There are issues with using such hint. I suggest you take a look at the following KB.

http://search.support.microsoft.com/kb/235880

|||

I'm still having the same problem..

My sql query results about 100Mb of information.

What can I do?

Error: 7886, Severity: 20, State: 1.

Hi All

I am seeing this error being logged in my SQL 2005 Ent machine

It seems to be arising out of a read of a text column.

Any info on this will be appreciated. Thanks

K T

You're not running CTP version, right?

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=233339&SiteID=1|||

Its build 9.0.2153

|||

Hi Kts,

Do you use Row versioning in you database?

I waiting for your answer.

Regards,

|||

No !

|||

Hi kts,

What you TRANSACTION ISOLATION LEVEL do you run the code?

Can you post the query here?

Regards,

|||

Ah, you use 'nolock' hint. There are issues with using such hint. I suggest you take a look at the following KB.

http://search.support.microsoft.com/kb/235880

|||

I'm still having the same problem..

My sql query results about 100Mb of information.

What can I do?

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:...
>

Error: 7105, Severity: 22, State: 6

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.
Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> 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.
>
|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>

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.
>>
>

Error: 7105, Severity: 22, State: 6

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.Make the call, they will tell you up front if it will be a covered (free)
call.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> 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.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>> 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: 7105, Severity: 22, State: 6

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.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:...
>|||Make the call, they will tell you up front if it will be a covered (free)
call.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"ME" <ME@.mail.com> wrote in message
news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
> 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.
>|||Hotfix calls are always free. Issues that are determined to be bugs are
free, even if no hotfix yet exists.
If you call the 800 number with the KB article # ready, tell them you are
looking for the hotfix, they will code it as "professional unpaid" and
transfer you to the support engineer.
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eepBp5T$GHA.1760@.TK2MSFTNGP02.phx.gbl...
> Make the call, they will tell you up front if it will be a covered (free)
> call.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "ME" <ME@.mail.com> wrote in message
> news:%23OovmtT$GHA.3344@.TK2MSFTNGP03.phx.gbl...
>

Error: 70000, Severity: 10, State: 1

do you have any idea about "Error: 70000" ?

By any chance you are hitting this during setup? If so, then most likely the reason is that MS .Net Framework 2.0 is not installed.

If this is not the case, please, let us know and copy the error and a brief description of what were you doing when it happened.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

thank a lot for response.

MS .Net is installed: v1.0.3705 , v1.1.4322, v2.0.50727

we have installed Windows 2000 Server SP4 with application useing DB. for our solution was enough MSDE.

there was 1.time MSDE2000, then we updated to MS SQL2000 Personal and now we made upgrade (because of increase of users and performance) to MS SQL Server 2000 Standard (ver: 2000.8.00.2039)

after this upgrade, we can see this error message. SQL server and application is running correct without any problems.

any other idea ?

SQL server log>

Date Source Message
2007-06-27 14:52:18.60 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) ...
2007-06-27 14:52:18.70 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQ
2007-06-27 14:52:18.70 server Server Process ID is 984.
2007-06-27 14:52:18.70 server All rights reserved.
2007-06-27 14:52:18.70 server Copyright (C) 1988-2002 Microsoft Corporation.
2007-06-27 14:52:18.79 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2007-06-27 14:52:19.87 server SQL Server configured for thread mode processing.
2007-06-27 14:52:19.92 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2007-06-27 14:52:20.73 server Attempting to initialize Distributed Transaction Coordinator.
2007-06-27 14:52:23.62 server Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b
2007-06-27 14:52:23.73 spid4 Starting up database 'master'.
2007-06-27 14:52:25.01 spid5 Starting up database 'model'.
2007-06-27 14:52:25.01 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-06-27 14:52:25.06 spid4 Server name is 'TELEVANTAGE'.
2007-06-27 14:52:25.09 spid8 Starting up database 'TVDB'.
2007-06-27 14:52:25.09 spid9 Starting up database 'msdb'.
2007-06-27 14:52:25.39 server SQL server listening on 127.0.0.1: 1433.
2007-06-27 14:52:25.39 server SQL server listening on 172.16.3.8: 1433.
2007-06-27 14:52:25.56 spid5 Clearing tempdb database.
2007-06-27 14:52:25.81 server SQL Server is ready for client connections
2007-06-27 14:52:25.81 server SQL server listening on TCP, Shared Memory, Named Pipes.
2007-06-27 14:52:26.32 spid8 97 transactions rolled forward in database 'TVDB' (5).
2007-06-27 14:52:26.85 spid8 1 transactions rolled back in database 'TVDB' (5).
2007-06-27 14:52:26.90 spid8 Recovery is checkpointing database 'TVDB' (5)
2007-06-27 14:52:28.18 spid5 Starting up database 'tempdb'.
2007-06-27 14:52:35.73 spid51 Using 'odsole70.dll' version '2000.80.2039' to execute extended stored procedur
2007-06-27 14:52:44.32 spid4 SQL global counter collection task is created.
2007-06-27 14:52:44.32 spid4 Recovery complete.
2007-06-27 14:53:11.98 spid54 DBCC TRACEON 3604, server process ID (SPID) 54.
2007-06-27 14:53:19.51 spid56 Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure
2007-06-27 14:53:22.48 spid58 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedur
2007-06-27 14:53:27.20 spid56 Configuration option 'max server memory (MB)' changed from 1019 to 1019. Run th
2007-06-27 14:53:27.20 spid56 Error: 15457, Severity: 0, State: 1
2007-06-27 14:53:27.32 spid56 Configuration option 'min server memory (MB)' changed from 509 to 509. Run the
2007-06-27 14:53:27.32 spid56 Error: 15457, Severity: 0, State: 1
2007-06-27 14:53:27.45 spid56 Configuration option 'min memory per query (KB)' changed from 512 to 512. Run t
2007-06-27 14:53:27.45 spid56 Error: 15457, Severity: 0, State: 1
2007-06-27 14:54:06.17 spid64 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure
2007-06-27 14:57:09.43 spid59 Configuration option 'show advanced options' changed from 1 to 1. Run the RECON
2007-06-27 14:57:09.43 spid59 Error: 15457, Severity: 0, State: 1
2007-06-27 14:59:46.71 spid615 Configuration option 'show advanced options' changed from 1 to 1. Run the RECON
2007-06-27 14:59:46.71 spid615 Error: 15457, Severity: 0, State: 1
2007-06-27 15:11:00.39 spid653 Input buffer for processes 651: exec sp_dbcmptlevel 'TVDB', 70.
2007-06-27 15:11:00.39 spid653 Error: 70000, Severity: 10, State: 1
2007-06-27 15:11:00.39 spid653 .
2007-06-27 15:11:00.39 spid653 Error: 70000, Severity: 10, State: 1
2007-06-27 15:11:00.62 spid653 Above process will be removed if still blocking on next check.
2007-06-27 15:11:00.62 spid653 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.60 spid619 Blocking process 636 using Permissions table with lock type 6 owned by TVCLIENT
2007-06-27 16:08:00.60 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.68 spid619 Input buffer for processes 636: exec sp_getFolder 1944, 5115.
2007-06-27 16:08:00.68 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.75 spid619 Above process will be removed if still blocking on next check.
2007-06-27 16:08:00.75 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.85 spid619 .
2007-06-27 16:08:00.85 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.89 spid619 Input buffer for processes 663: exec sp_getFolder 1920, 5115.
2007-06-27 16:08:00.89 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 16:08:00.92 spid619 Above process will be removed if still blocking on next check.
2007-06-27 16:08:00.92 spid619 Error: 70000, Severity: 10, State: 1
2007-06-27 21:26:00.37 spid622 Above process will be removed if still blocking on next check.
2007-06-27 21:26:00.37 spid622 Error: 70000, Severity: 10, State: 1
2007-06-27 21:26:00.37 spid622 Input buffer for processes 613: exec sp_addPartyLog 713908, 33, '', 'Unknown',
2007-06-27 21:26:00.37 spid622 Error: 70000, Severity: 10, State: 1
2007-06-27 21:26:00.37 spid622 .

|||Error 70000 should be a custom one, you should contact the person which implemented it. If you are not sure about it run the profiler to see where the error message comes from.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Any updates on that ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

sorry for no response. I have no new messages.. it's probably any internal message in our application what we are using, but developer of this appliaction didn't tell us more info about. there is no problem with functionality... so we are ignoring this message.

thanks

Error: 70000, Severity: 10, State: 1

do you have any idea about "Error: 70000" ?

By any chance you are hitting this during setup? If so, then most likely the reason is that MS .Net Framework 2.0 is not installed.

If this is not the case, please, let us know and copy the error and a brief description of what were you doing when it happened.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

thank a lot for response.

MS .Net is installed: v1.0.3705 , v1.1.4322, v2.0.50727

we have installed Windows 2000 Server SP4 with application useing DB. for our solution was enough MSDE.

there was 1.time MSDE2000, then we updated to MS SQL2000 Personal and now we made upgrade (because of increase of users and performance) to MS SQL Server 2000 Standard (ver: 2000.8.00.2039)

after this upgrade, we can see this error message. SQL server and application is running correct without any problems.

any other idea ?

SQL server log>

|||Error 70000 should be a custom one, you should contact the person which implemented it. If you are not sure about it run the profiler to see where the error message comes from.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Any updates on that ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

thanks

Error: 70000, Severity: 10, State: 1

do you have any idea about "Error: 70000" ?

By any chance you are hitting this during setup? If so, then most likely the reason is that MS .Net Framework 2.0 is not installed.

If this is not the case, please, let us know and copy the error and a brief description of what were you doing when it happened.

Thanks a lot,

-Raul Garcia

SDE/T

SQL Server Engine

|||

thank a lot for response.

MS .Net is installed: v1.0.3705 , v1.1.4322, v2.0.50727

we have installed Windows 2000 Server SP4 with application useing DB. for our solution was enough MSDE.

there was 1.time MSDE2000, then we updated to MS SQL2000 Personal and now we made upgrade (because of increase of users and performance) to MS SQL Server 2000 Standard (ver: 2000.8.00.2039)

after this upgrade, we can see this error message. SQL server and application is running correct without any problems.

any other idea ?

SQL server log>

|||Error 70000 should be a custom one, you should contact the person which implemented it. If you are not sure about it run the profiler to see where the error message comes from.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Any updates on that ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

thanks

Error: 66030

Hi,
On one of our SQL 2000 cluster servers we have been
getting a lot of error messages in our SQL Server log ile.
Error: 66030, Severity: 15, State: 1
Occasionally it also reports
Error: 66040, Severity: 15, State: 1.
I have been unable to find any information on these error
messages. I would be grateful if someone could shed some
light on what these messages actually mean. Thanks.The fact that the error number is > 50000 suggests that this actually an
application specific error message rather than a generic SQL message. Have a
look in master..sysmessages to see the text of the message, it might give
you a clue
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"PaulaC" <anonymous@.discussions.microsoft.com> wrote in message
news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
> Hi,
> On one of our SQL 2000 cluster servers we have been
> getting a lot of error messages in our SQL Server log ile.
> Error: 66030, Severity: 15, State: 1
> Occasionally it also reports
> Error: 66040, Severity: 15, State: 1.
> I have been unable to find any information on these error
> messages. I would be grateful if someone could shed some
> light on what these messages actually mean. Thanks.
>|||Thanks for the suggestion. Unfortunately, I cannot find
anything like my error messages in sysmessages.
Paula.
>--Original Message--
>The fact that the error number is > 50000 suggests that
this actually an
>application specific error message rather than a generic
SQL message. Have a
>look in master..sysmessages to see the text of the
message, it might give
>you a clue
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"PaulaC" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
>> Hi,
>> On one of our SQL 2000 cluster servers we have been
>> getting a lot of error messages in our SQL Server log
ile.
>> Error: 66030, Severity: 15, State: 1
>> Occasionally it also reports
>> Error: 66040, Severity: 15, State: 1.
>> I have been unable to find any information on these
error
>> messages. I would be grateful if someone could shed
some
>> light on what these messages actually mean. Thanks.
>
>.
>sql

Error: 66030

Hi,
On one of our SQL 2000 cluster servers we have been
getting a lot of error messages in our SQL Server log ile.
Error: 66030, Severity: 15, State: 1
Occasionally it also reports
Error: 66040, Severity: 15, State: 1.
I have been unable to find any information on these error
messages. I would be grateful if someone could shed some
light on what these messages actually mean. Thanks.The fact that the error number is > 50000 suggests that this actually an
application specific error message rather than a generic SQL message. Have a
look in master..sysmessages to see the text of the message, it might give
you a clue
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"PaulaC" <anonymous@.discussions.microsoft.com> wrote in message
news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
> Hi,
> On one of our SQL 2000 cluster servers we have been
> getting a lot of error messages in our SQL Server log ile.
> Error: 66030, Severity: 15, State: 1
> Occasionally it also reports
> Error: 66040, Severity: 15, State: 1.
> I have been unable to find any information on these error
> messages. I would be grateful if someone could shed some
> light on what these messages actually mean. Thanks.
>|||Thanks for the suggestion. Unfortunately, I cannot find
anything like my error messages in sysmessages.
Paula.

>--Original Message--
>The fact that the error number is > 50000 suggests that
this actually an
>application specific error message rather than a generic
SQL message. Have a
>look in master..sysmessages to see the text of the
message, it might give
>you a clue
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"PaulaC" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bdac01c4380c$671e2b90$a501280a@.phx.gbl...
ile.[vbcol=seagreen]
error[vbcol=seagreen]
some[vbcol=seagreen]
>
>.
>

Monday, March 26, 2012

Error: 9003, Severity: 20, State: 1

Error: 8646, Severity: 21, State: 1

Error: 8646, Severity: 21, State: 1

Error: 8646, Severity: 21, State: 1

Error: 8624 Internal Query Processor Error: The query processor could not produce a query plan.

Error: 8624 Internal Query Processor Error: The query processor could not produce a query plan.

Error: 823

Error: 7886, Severity: 20, State: 1.

Error: 7886, Severity: 20, State: 1.

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Error: 7105, Severity: 22, State: 6

Error: 70000, Severity: 10, State: 1

Error: 70000, Severity: 10, State: 1

Error: 70000, Severity: 10, State: 1

Error: 66030

Error: 66030

Error while connection

Blog Archive

About Me