I have a prospective client evaluating our software that uses a SQL backend
and we're struggling with some errors I can't recreate here in our lab.
When he logs into his laptop and tried to access the SQL db, he get's this
error:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection"
However, when he or the SQL admin log into the SQL admin's PC both can
access the SQL db just fine.
This error only happens on the tester's PC. He even re-imaged the PC and it
still fails. He's running WinXP.
They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD and
SQL authentication. In this case they have created users for him in both AD
and SQL for this db.
Suggestions?
make named pipes the priority on the clients.
"smutny" <smutny@.discussions.microsoft.com> wrote in message
news:780B2EEF-7C85-4DCE-854B-25F4409DE61F@.microsoft.com...
>I have a prospective client evaluating our software that uses a SQL backend
> and we're struggling with some errors I can't recreate here in our lab.
> When he logs into his laptop and tried to access the SQL db, he get's this
> error:
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> However, when he or the SQL admin log into the SQL admin's PC both can
> access the SQL db just fine.
> This error only happens on the tester's PC. He even re-imaged the PC and
> it
> still fails. He's running WinXP.
> They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD
> and
> SQL authentication. In this case they have created users for him in both
> AD
> and SQL for this db.
> Suggestions?
Showing posts with label errors. Show all posts
Showing posts with label errors. Show all posts
Friday, March 23, 2012
Frustrating Authentication Errors
I have a prospective client evaluating our software that uses a SQL backend
and we're struggling with some errors I can't recreate here in our lab.
When he logs into his laptop and tried to access the SQL db, he get's this
error:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection"
However, when he or the SQL admin log into the SQL admin's PC both can
access the SQL db just fine.
This error only happens on the tester's PC. He even re-imaged the PC and it
still fails. He's running WinXP.
They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD and
SQL authentication. In this case they have created users for him in both AD
and SQL for this db.
Suggestions'make named pipes the priority on the clients.
"smutny" <smutny@.discussions.microsoft.com> wrote in message
news:780B2EEF-7C85-4DCE-854B-25F4409DE61F@.microsoft.com...
>I have a prospective client evaluating our software that uses a SQL backend
> and we're struggling with some errors I can't recreate here in our lab.
> When he logs into his laptop and tried to access the SQL db, he get's this
> error:
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> However, when he or the SQL admin log into the SQL admin's PC both can
> access the SQL db just fine.
> This error only happens on the tester's PC. He even re-imaged the PC and
> it
> still fails. He's running WinXP.
> They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD
> and
> SQL authentication. In this case they have created users for him in both
> AD
> and SQL for this db.
> Suggestions'
and we're struggling with some errors I can't recreate here in our lab.
When he logs into his laptop and tried to access the SQL db, he get's this
error:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection"
However, when he or the SQL admin log into the SQL admin's PC both can
access the SQL db just fine.
This error only happens on the tester's PC. He even re-imaged the PC and it
still fails. He's running WinXP.
They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD and
SQL authentication. In this case they have created users for him in both AD
and SQL for this db.
Suggestions'make named pipes the priority on the clients.
"smutny" <smutny@.discussions.microsoft.com> wrote in message
news:780B2EEF-7C85-4DCE-854B-25F4409DE61F@.microsoft.com...
>I have a prospective client evaluating our software that uses a SQL backend
> and we're struggling with some errors I can't recreate here in our lab.
> When he logs into his laptop and tried to access the SQL db, he get's this
> error:
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> However, when he or the SQL admin log into the SQL admin's PC both can
> access the SQL db just fine.
> This error only happens on the tester's PC. He even re-imaged the PC and
> it
> still fails. He's running WinXP.
> They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD
> and
> SQL authentication. In this case they have created users for him in both
> AD
> and SQL for this db.
> Suggestions'
Frustrating Authentication Errors
I have a prospective client evaluating our software that uses a SQL backend
and we're struggling with some errors I can't recreate here in our lab.
When he logs into his laptop and tried to access the SQL db, he get's this
error:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection"
However, when he or the SQL admin log into the SQL admin's PC both can
access the SQL db just fine.
This error only happens on the tester's PC. He even re-imaged the PC and it
still fails. He's running WinXP.
They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD and
SQL authentication. In this case they have created users for him in both AD
and SQL for this db.
Suggestions'make named pipes the priority on the clients.
"smutny" <smutny@.discussions.microsoft.com> wrote in message
news:780B2EEF-7C85-4DCE-854B-25F4409DE61F@.microsoft.com...
>I have a prospective client evaluating our software that uses a SQL backend
> and we're struggling with some errors I can't recreate here in our lab.
> When he logs into his laptop and tried to access the SQL db, he get's this
> error:
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> However, when he or the SQL admin log into the SQL admin's PC both can
> access the SQL db just fine.
> This error only happens on the tester's PC. He even re-imaged the PC and
> it
> still fails. He's running WinXP.
> They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD
> and
> SQL authentication. In this case they have created users for him in both
> AD
> and SQL for this db.
> Suggestions'
and we're struggling with some errors I can't recreate here in our lab.
When he logs into his laptop and tried to access the SQL db, he get's this
error:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection"
However, when he or the SQL admin log into the SQL admin's PC both can
access the SQL db just fine.
This error only happens on the tester's PC. He even re-imaged the PC and it
still fails. He's running WinXP.
They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD and
SQL authentication. In this case they have created users for him in both AD
and SQL for this db.
Suggestions'make named pipes the priority on the clients.
"smutny" <smutny@.discussions.microsoft.com> wrote in message
news:780B2EEF-7C85-4DCE-854B-25F4409DE61F@.microsoft.com...
>I have a prospective client evaluating our software that uses a SQL backend
> and we're struggling with some errors I can't recreate here in our lab.
> When he logs into his laptop and tried to access the SQL db, he get's this
> error:
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> However, when he or the SQL admin log into the SQL admin's PC both can
> access the SQL db just fine.
> This error only happens on the tester's PC. He even re-imaged the PC and
> it
> still fails. He's running WinXP.
> They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD
> and
> SQL authentication. In this case they have created users for him in both
> AD
> and SQL for this db.
> Suggestions'
Monday, March 19, 2012
From MDB TO ADP
I am trying to move a database from an MDB to an ADP, but I'm getting some errors. For example
SELECT MachineList.[Machine Number], MachineList.[Serial Number], MachineList.Location, MachineList.[Manuf ID], MachineList.[Game Theme], MachineList.Class, MachineList.Installed, MachineList.Certified, MachineList.[EZ-Pay]
FROM MachineList
WHERE (((MachineList.[Machine Number])=[Please enter the machine number]))
ORDER BY MachineList.Location;
Now I know there is a difference between Jet SQL and MS SQL, I guess I just need to revert this to MSSQL
Heres the Error Message I'm getting
Server: Msg 207, Level 16, State 3, Line 1
Invalid column name 'Enter the installation date'.Never Mind I Figured It Out Its A Function...hoooorrraaaayyyyyyyy
SELECT MachineList.[Machine Number], MachineList.[Serial Number], MachineList.Location, MachineList.[Manuf ID], MachineList.[Game Theme], MachineList.Class, MachineList.Installed, MachineList.Certified, MachineList.[EZ-Pay]
FROM MachineList
WHERE (((MachineList.[Machine Number])=[Please enter the machine number]))
ORDER BY MachineList.Location;
Now I know there is a difference between Jet SQL and MS SQL, I guess I just need to revert this to MSSQL
Heres the Error Message I'm getting
Server: Msg 207, Level 16, State 3, Line 1
Invalid column name 'Enter the installation date'.Never Mind I Figured It Out Its A Function...hoooorrraaaayyyyyyyy
Monday, March 12, 2012
frequent timeouts on SQL Server 2000
I have been receiving timeout errors frequently form our database. Any
suggestions as to the cause?
Thanks.
Usarian
Hi,
Can you try optimizing your SQL's and Stored procedures. Use the Profiler
with CPU / Duration in the display.
Identify the procedures/SQL's taking more duration/CPU. After that using
tune the code using Execution Plans / Index tuning wizard...
Thanks
Hari
SQL Server MVP
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>
|||Blocking.
Run sp_who2 or profiler to see what extent blocking is affecting your
concurrency.
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/
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>
suggestions as to the cause?
Thanks.
Usarian
Hi,
Can you try optimizing your SQL's and Stored procedures. Use the Profiler
with CPU / Duration in the display.
Identify the procedures/SQL's taking more duration/CPU. After that using
tune the code using Execution Plans / Index tuning wizard...
Thanks
Hari
SQL Server MVP
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>
|||Blocking.
Run sp_who2 or profiler to see what extent blocking is affecting your
concurrency.
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/
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>
frequent timeouts on SQL Server 2000
I have been receiving timeout errors frequently form our database. Any
suggestions as to the cause?
Thanks.
UsarianHi,
Can you try optimizing your SQL's and Stored procedures. Use the Profiler
with CPU / Duration in the display.
Identify the procedures/SQL's taking more duration/CPU. After that using
tune the code using Execution Plans / Index tuning wizard...
Thanks
Hari
SQL Server MVP
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>|||Blocking.
Run sp_who2 or profiler to see what extent blocking is affecting your
concurrency.
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/
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>
suggestions as to the cause?
Thanks.
UsarianHi,
Can you try optimizing your SQL's and Stored procedures. Use the Profiler
with CPU / Duration in the display.
Identify the procedures/SQL's taking more duration/CPU. After that using
tune the code using Execution Plans / Index tuning wizard...
Thanks
Hari
SQL Server MVP
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>|||Blocking.
Run sp_who2 or profiler to see what extent blocking is affecting your
concurrency.
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/
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>
frequent timeouts on SQL Server 2000
I have been receiving timeout errors frequently form our database. Any
suggestions as to the cause?
Thanks.
UsarianHi,
Can you try optimizing your SQL's and Stored procedures. Use the Profiler
with CPU / Duration in the display.
Identify the procedures/SQL's taking more duration/CPU. After that using
tune the code using Execution Plans / Index tuning wizard...
Thanks
Hari
SQL Server MVP
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>|||Blocking.
Run sp_who2 or profiler to see what extent blocking is affecting your
concurrency.
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/
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>
suggestions as to the cause?
Thanks.
UsarianHi,
Can you try optimizing your SQL's and Stored procedures. Use the Profiler
with CPU / Duration in the display.
Identify the procedures/SQL's taking more duration/CPU. After that using
tune the code using Execution Plans / Index tuning wizard...
Thanks
Hari
SQL Server MVP
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>|||Blocking.
Run sp_who2 or profiler to see what extent blocking is affecting your
concurrency.
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/
"Usarian Skiff" <usarian.skiff@.servicecentermetals.com> wrote in message
news:%23b8rWl%23hFHA.1248@.TK2MSFTNGP12.phx.gbl...
>I have been receiving timeout errors frequently form our database. Any
> suggestions as to the cause?
> Thanks.
> Usarian
>
Frequent errors in Application Event Viewer
Hi all,
I encounter many of this errors in Application event viewer regarding
SQL server 2005:
Type:Error
Date:07/03/2008
Time:8.54.24
Event:19019
Source:MSSQL$INSTNEW
Category:Failover
User:N/A
Computer:NEW
Description:
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Type:Error
Date:07/03/2008
Time:8.54.24
Event:19019
Source:MSSQL$INSTNEW
Category:Failover
User:N/A
Computer:NEW
Description:
[sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
message = [Microsoft][SQL Native Client]TCP Provider: An existing
connection was
forcibly closed by the remote host.
Type:Error
Date:07/03/2008
Time:8.54.24
Event:19019
Source:MSSQL$INSTNEW
Category:Failover
User:N/A
Computer:NEW
Description:
[sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
message = [Microsoft][SQL Native Client]Communication link failure
Type:Error
Date:07/03/2008
Time:8.54.24
Event:19019
Source:MSSQL$INSTNEW
Category:Failover
User:N/A
Computer:NEW
Description:
[sqsrvres] OnlineThread: QP is not online.
They occours every time in this order. 6-7 times a day.
I've searched but individually, they seem to be generics errors.
Could you help me?
Thanks in advance
Tony
That is the cluster service checking to see if the SQL Server is responsive.
Get enough of those in a row, and cluster serv tries to restart or failover
the sql group
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Tony_da_Roma" <killerloop@.post.com> wrote in message
news:ff950762-ed63-4c69-9e5e-f45a5386b2e4@.n58g2000hsf.googlegroups.com...
> Hi all,
> I encounter many of this errors in Application event viewer regarding
> SQL server 2005:
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
> message = [Microsoft][SQL Native Client]TCP Provider: An existing
> connection was
> forcibly closed by the remote host.
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
> message = [Microsoft][SQL Native Client]Communication link failure
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] OnlineThread: QP is not online.
> They occours every time in this order. 6-7 times a day.
> I've searched but individually, they seem to be generics errors.
> Could you help me?
> Thanks in advance
> Tony
I encounter many of this errors in Application event viewer regarding
SQL server 2005:
Type:Error
Date:07/03/2008
Time:8.54.24
Event:19019
Source:MSSQL$INSTNEW
Category:Failover
User:N/A
Computer:NEW
Description:
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Type:Error
Date:07/03/2008
Time:8.54.24
Event:19019
Source:MSSQL$INSTNEW
Category:Failover
User:N/A
Computer:NEW
Description:
[sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
message = [Microsoft][SQL Native Client]TCP Provider: An existing
connection was
forcibly closed by the remote host.
Type:Error
Date:07/03/2008
Time:8.54.24
Event:19019
Source:MSSQL$INSTNEW
Category:Failover
User:N/A
Computer:NEW
Description:
[sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
message = [Microsoft][SQL Native Client]Communication link failure
Type:Error
Date:07/03/2008
Time:8.54.24
Event:19019
Source:MSSQL$INSTNEW
Category:Failover
User:N/A
Computer:NEW
Description:
[sqsrvres] OnlineThread: QP is not online.
They occours every time in this order. 6-7 times a day.
I've searched but individually, they seem to be generics errors.
Could you help me?
Thanks in advance
Tony
That is the cluster service checking to see if the SQL Server is responsive.
Get enough of those in a row, and cluster serv tries to restart or failover
the sql group
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Tony_da_Roma" <killerloop@.post.com> wrote in message
news:ff950762-ed63-4c69-9e5e-f45a5386b2e4@.n58g2000hsf.googlegroups.com...
> Hi all,
> I encounter many of this errors in Application event viewer regarding
> SQL server 2005:
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
> message = [Microsoft][SQL Native Client]TCP Provider: An existing
> connection was
> forcibly closed by the remote host.
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
> message = [Microsoft][SQL Native Client]Communication link failure
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] OnlineThread: QP is not online.
> They occours every time in this order. 6-7 times a day.
> I've searched but individually, they seem to be generics errors.
> Could you help me?
> Thanks in advance
> Tony
Frequent errors in Application Event Viewer
Hi all,
I encounter many of this errors in Application event viewer regarding
SQL server 2005:
Type: Error
Date: 07/03/2008
Time: 8.54.24
Event: 19019
Source: MSSQL$INSTNEW
Category: Failover
User: N/A
Computer: NEW
Description:
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Type: Error
Date: 07/03/2008
Time: 8.54.24
Event: 19019
Source: MSSQL$INSTNEW
Category: Failover
User: N/A
Computer: NEW
Description:
[sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
message = [Microsoft][SQL Native Client]TCP Provider: An existing
connection was
forcibly closed by the remote host.
Type: Error
Date: 07/03/2008
Time: 8.54.24
Event: 19019
Source: MSSQL$INSTNEW
Category: Failover
User: N/A
Computer: NEW
Description:
[sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
message = [Microsoft][SQL Native Client]Communication link failure
Type: Error
Date: 07/03/2008
Time: 8.54.24
Event: 19019
Source: MSSQL$INSTNEW
Category: Failover
User: N/A
Computer: NEW
Description:
[sqsrvres] OnlineThread: QP is not online.
They occours every time in this order. 6-7 times a day.
I've searched but individually, they seem to be generics errors.
Could you help me?
Thanks in advance
TonyThat is the cluster service checking to see if the SQL Server is responsive.
Get enough of those in a row, and cluster serv tries to restart or failover
the sql group
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Tony_da_Roma" <killerloop@.post.com> wrote in message
news:ff950762-ed63-4c69-9e5e-f45a5386b2e4@.n58g2000hsf.googlegroups.com...
> Hi all,
> I encounter many of this errors in Application event viewer regarding
> SQL server 2005:
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
> message = [Microsoft][SQL Native Client]TCP Provider: An existing
> connection was
> forcibly closed by the remote host.
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
> message = [Microsoft][SQL Native Client]Communication link failure
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] OnlineThread: QP is not online.
> They occours every time in this order. 6-7 times a day.
> I've searched but individually, they seem to be generics errors.
> Could you help me?
> Thanks in advance
> Tony
I encounter many of this errors in Application event viewer regarding
SQL server 2005:
Type: Error
Date: 07/03/2008
Time: 8.54.24
Event: 19019
Source: MSSQL$INSTNEW
Category: Failover
User: N/A
Computer: NEW
Description:
[sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
Type: Error
Date: 07/03/2008
Time: 8.54.24
Event: 19019
Source: MSSQL$INSTNEW
Category: Failover
User: N/A
Computer: NEW
Description:
[sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
message = [Microsoft][SQL Native Client]TCP Provider: An existing
connection was
forcibly closed by the remote host.
Type: Error
Date: 07/03/2008
Time: 8.54.24
Event: 19019
Source: MSSQL$INSTNEW
Category: Failover
User: N/A
Computer: NEW
Description:
[sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
message = [Microsoft][SQL Native Client]Communication link failure
Type: Error
Date: 07/03/2008
Time: 8.54.24
Event: 19019
Source: MSSQL$INSTNEW
Category: Failover
User: N/A
Computer: NEW
Description:
[sqsrvres] OnlineThread: QP is not online.
They occours every time in this order. 6-7 times a day.
I've searched but individually, they seem to be generics errors.
Could you help me?
Thanks in advance
TonyThat is the cluster service checking to see if the SQL Server is responsive.
Get enough of those in a row, and cluster serv tries to restart or failover
the sql group
--
Kevin3NF
SQL Server dude
You want fries with that?
http://kevin3nf.blogspot.com/
I only check the newsgroups during work hours, M-F.
Hit my blog and the contact links if necessary...I may be available.
"Tony_da_Roma" <killerloop@.post.com> wrote in message
news:ff950762-ed63-4c69-9e5e-f45a5386b2e4@.n58g2000hsf.googlegroups.com...
> Hi all,
> I encounter many of this errors in Application event viewer regarding
> SQL server 2005:
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
> message = [Microsoft][SQL Native Client]TCP Provider: An existing
> connection was
> forcibly closed by the remote host.
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746;
> message = [Microsoft][SQL Native Client]Communication link failure
>
> Type: Error
> Date: 07/03/2008
> Time: 8.54.24
> Event: 19019
> Source: MSSQL$INSTNEW
> Category: Failover
> User: N/A
> Computer: NEW
> Description:
> [sqsrvres] OnlineThread: QP is not online.
> They occours every time in this order. 6-7 times a day.
> I've searched but individually, they seem to be generics errors.
> Could you help me?
> Thanks in advance
> Tony
Subscribe to:
Posts (Atom)