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