CheckQueryProcessorAlive

Please help me determine what could cause the SQL Server 2000 Cluster error
listed below. This is a server with SQL Server 2000 Enterprise Edition as an
Active/Active Cluster and Windows 2003 Server.
Please help me with this error.
Thanks,
00000780.0000149c::2005/01/05-18:22:53.035 INFO [API] User denied access
using default cluster SD. GetLastError() = 0x00000005; dwStatus = 0x00000000.
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 01000; native error = 2746;
message = [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite
(send()).
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = b;
message = [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network
error. Check your network documentation.
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] OnlineThread: QP is not online.
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
(OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
message = [Microsoft][ODBC SQL Server Driver]Communication link failure
00000780.00000e6c::2005/01/05-18:23:22.676 INFO [CP] CppRegNotifyThread
checkpointing key Software\Microsoft\Microsoft SQL Server\OLTP\MSSQLSERVER to
id 4 due to timer
00000780.00000e6c::2005/01/05-18:23:22.676 INFO [Qfs] QfsGetTempFileName
C:\Temp\, CLS, 41268 => C:\Temp\CLSA164.tmp, status 0
00000780.00000e6c::2005/01/05-18:23:22.676 INFO [Qfs] QfsDeleteFile
C:\Temp\CLSA164.tmp, status 0
00000780.00000e6c::2005/01/05-18:23:22.707 INFO [Qfs] QfsRegSaveKey
C:\Temp\CLSA164.tmp, status 0
The cluster is not running with the required access. Pls check the access by
giving the correct user / pass
Regards
Nirvan
"Joe P." wrote:

> Please help me determine what could cause the SQL Server 2000 Cluster error
> listed below. This is a server with SQL Server 2000 Enterprise Edition as an
> Active/Active Cluster and Windows 2003 Server.
> Please help me with this error.
> Thanks,
>
> 00000780.0000149c::2005/01/05-18:22:53.035 INFO [API] User denied access
> using default cluster SD. GetLastError() = 0x00000005; dwStatus = 0x00000000.
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 01000; native error = 2746;
> message = [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite
> (send()).
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = b;
> message = [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network
> error. Check your network documentation.
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] OnlineThread: QP is not online.
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.957 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
> 000008ec.000007e4::2005/01/05-18:23:17.973 ERR SQL Server <SQL Server
> (OLTP)>: [sqsrvres] printODBCError: sqlstate = 08S01; native error = 0;
> message = [Microsoft][ODBC SQL Server Driver]Communication link failure
> 00000780.00000e6c::2005/01/05-18:23:22.676 INFO [CP] CppRegNotifyThread
> checkpointing key Software\Microsoft\Microsoft SQL Server\OLTP\MSSQLSERVER to
> id 4 due to timer
> 00000780.00000e6c::2005/01/05-18:23:22.676 INFO [Qfs] QfsGetTempFileName
> C:\Temp\, CLS, 41268 => C:\Temp\CLSA164.tmp, status 0
> 00000780.00000e6c::2005/01/05-18:23:22.676 INFO [Qfs] QfsDeleteFile
> C:\Temp\CLSA164.tmp, status 0
> 00000780.00000e6c::2005/01/05-18:23:22.707 INFO [Qfs] QfsRegSaveKey
> C:\Temp\CLSA164.tmp, status 0
>
|||This might help explain...
http://support.microsoft.com/default...b;en-us;291255
jg
[quote]Originally posted by Joe P.
[b]Please help me determine what could cause the SQL Server 2000 Cluster error
listed below. This is a server with SQL Server 2000 Enterprise Edition as an
Active/Active Cluster and Windows 2003 Server.
Please help me with this error.
Thanks,|||The service account that MSCS is running under connects to the SQL
instance every 60 seconds by default (configurable in advanced tab of
the SQL Server resource in cluster administrator) and runs
select @.@.server
using its trusted connection. If it's capable of doing that then it's
happy that the SQL instance is alive. It also does a looks alive poll
every 5 seconds (by default) but I'm not sure what it does for a looks
alive poll (probably just a quick check of the status of the MSSQLServer
service on the owner node).
Basically, make sure the cluster service account has a trusted
connection to the SQL server. All it needs is to be a member of the
public role in the master DB (which every login has anyway) so just add
a trusted login for it if it doesn't already exist.
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Nirvan Biswas wrote:
[vbcol=seagreen]
>The cluster is not running with the required access. Pls check the access by
>giving the correct user / pass
>Regards
>Nirvan
>"Joe P." wrote:
>

Checking and Indexing

Hi,
Does running the SQL maintenance tools such as indexing and checking while
users are using the database cause problems?
Thanks
Any maintenance activity such as DBCC CHECKDB and DBREINDEX will have some
effect due to their resource intensive nature. But DBCC CHECKDB can be run
while users are accessing the system without stopping normal access to the
tables. The system may be slower due to the CPU usage of the command but it
will not prevent them altogether. DBCC DBREINDEX on the other hand will
stop any access to the table it is currently working on. From the time it
starts to reindex anything in that table it takes an exclusive table lock
and holds it until it finish's with that table.
Andrew J. Kelly SQL MVP
"Amir Marathonian" <AmirMarathonian@.discussions.microsoft.com> wrote in
message news:193BC0D7-1BF7-415B-8B74-1FBCBC4C649F@.microsoft.com...
> Hi,
> Does running the SQL maintenance tools such as indexing and checking while
> users are using the database cause problems?
> Thanks