I was wondering if someone would be so kind as to tell me if i'm
missing something or just plain dumb:
I am running a 2000 Advanced Server and SQL 2000 Enterprise SP3. I
changed the SQL SERVER SERVICE account to use a Local NT User account
with no enhanced privileges standard user and another account with the
same level of permissions for the SQL SERVER AGENT.
Both services start fine and I configured the SQL server to start using
the service account thru enterprise manager. As well as the
configuration for SQL SERVER AGENT was also done in Enterprise Manager.
The file system and Program files directories are configured with the
default ACL's. There is no GPO dictating who has the "log on as service
right" and both accounts (SERVER & AGENT) have the sysadmin role in
SQL.
HOWEVER: whenever I try to run a job thru SQL SERVER AGENT it does not
run and i get a message stating that the service is not running. This
message dissapears as soon as i make the accounts members of the local
administrators group.
Would there be any way to run these 2 services under the local USER
permissions and have the jobs execute sucessfully?
ANY HELP would be appreciated. I have been doing research for more than
5 days now and can't seem to find an answer.
THANks!
Miguel A. Escalante, MCSEIs the error actually:
Error 22022: SQLServerAgent is not currently running so it
cannot be notified of this action.
Some things to check - Are you running SQL Server in fiber
mode (lightweight pooling)? Have you ensured that SQL Agent
is truly running and not hung up in a starting status? Have
you checked your sqlagent.out file?
In addition to lightweight pooling being enabled, Agent can
also get hung up due to a bad mail profile.
-Sue
On 2 Nov 2005 20:13:15 -0800, miguel.a.escalante@.gmail.com
wrote:
>I was wondering if someone would be so kind as to tell me if i'm
>missing something or just plain dumb:
>I am running a 2000 Advanced Server and SQL 2000 Enterprise SP3. I
>changed the SQL SERVER SERVICE account to use a Local NT User account
>with no enhanced privileges standard user and another account with the
>same level of permissions for the SQL SERVER AGENT.
>Both services start fine and I configured the SQL server to start using
>the service account thru enterprise manager. As well as the
>configuration for SQL SERVER AGENT was also done in Enterprise Manager.
>
>The file system and Program files directories are configured with the
>default ACL's. There is no GPO dictating who has the "log on as service
>right" and both accounts (SERVER & AGENT) have the sysadmin role in
>SQL.
>HOWEVER: whenever I try to run a job thru SQL SERVER AGENT it does not
>run and i get a message stating that the service is not running. This
>message dissapears as soon as i make the accounts members of the local
>administrators group.
>Would there be any way to run these 2 services under the local USER
>permissions and have the jobs execute sucessfully?
>ANY HELP would be appreciated. I have been doing research for more than
>5 days now and can't seem to find an answer.
>THANks!
>Miguel A. Escalante, MCSEsql
Showing posts with label plain. Show all posts
Showing posts with label plain. Show all posts
Monday, March 26, 2012
Friday, February 24, 2012
Help with xp_sendmail needed!
This is a multi-part message in MIME format.
--=_NextPart_000_0006_01C4F641.316CAF50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
I am using xp_sendmail SP to send emails to myself, not to a = distribution list. I receive the error: Server: Msg 18031, Level 16, = State 1, Line 0
xp_sendmail: Could not resolve recipient
The server is a MS Windows 2003 running SQL 2000 and Office XP SP3. The = OS, SQL and Office are fully updated. I do not think that this problem = is related to the bug described in Article ID:315666.
May I ask you for some help?
Thank you,
Ovidiu Tanjala
--=_NextPart_000_0006_01C4F641.316CAF50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hello,
I am using xp_sendmail SP to send emails = to myself, not to a distribution list. I receive the error: Server: Msg 18031, = Level 16, State 1, Line 0
xp_sendmail: Could not resolve = recipient
The server is a MS Windows 2003 running = SQL 2000 and Office XP SP3. The OS, SQL and Office are fully updated. I do not think = that this problem is related to the bug described in Article = ID:315666.
May I ask you for some help?
Thank you,
Ovidiu Tanjala =
--=_NextPart_000_0006_01C4F641.316CAF50--Hi Ovidiu,
Are you able to execute xp_stopmail and xp_startmail successfully? Also
please post your xp_sendmail statement, which resulted in this error.
--
Thanks
Yogish
--=_NextPart_000_0006_01C4F641.316CAF50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
I am using xp_sendmail SP to send emails to myself, not to a = distribution list. I receive the error: Server: Msg 18031, Level 16, = State 1, Line 0
xp_sendmail: Could not resolve recipient
The server is a MS Windows 2003 running SQL 2000 and Office XP SP3. The = OS, SQL and Office are fully updated. I do not think that this problem = is related to the bug described in Article ID:315666.
May I ask you for some help?
Thank you,
Ovidiu Tanjala
--=_NextPart_000_0006_01C4F641.316CAF50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hello,
I am using xp_sendmail SP to send emails = to myself, not to a distribution list. I receive the error: Server: Msg 18031, = Level 16, State 1, Line 0
xp_sendmail: Could not resolve = recipient
The server is a MS Windows 2003 running = SQL 2000 and Office XP SP3. The OS, SQL and Office are fully updated. I do not think = that this problem is related to the bug described in Article = ID:315666.
May I ask you for some help?
Thank you,
Ovidiu Tanjala =
--=_NextPart_000_0006_01C4F641.316CAF50--Hi Ovidiu,
Are you able to execute xp_stopmail and xp_startmail successfully? Also
please post your xp_sendmail statement, which resulted in this error.
--
Thanks
Yogish
Labels:
_nextpart_000_0006_01c4f641,
316caf50,
charset,
content-type,
database,
format,
iso-8859-1,
message,
microsoft,
mime,
multi-part,
mysql,
oracle,
plain,
server,
sql,
text,
xp_sendmail
Sunday, February 19, 2012
help with unusual victum messages
This is a multi-part message in MIME format.
--=_NextPart_000_0058_01C43F8A.9695C150
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am finding some unusual deadlock victum messages in my errorlogs that = I have included in this message. I would appreciate any information = about these messages. I am familiar with the normal deadlock message, = it is the statements in red that I need help with.
thanks
tim
2004-05-21 16:07:58.18 spid4 Deadlock encountered ... Printing deadlock information
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Wait-for graph
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:1
2004-05-21 16:07:58.18 spid4 RID: 5:1:536178:4 = CleanCnt:1 Mode: X Flags: 0x2
2004-05-21 16:07:58.18 spid4 Grant List 3::
2004-05-21 16:07:58.18 spid4 Owner:0x68e15860 Mode: X = Flg:0x0 Ref:0 Life:02000000 SPID:54 ECID:0
2004-05-21 16:07:58.18 spid4 SPID: 54 ECID: 0 Statement Type: = UPDATE Line #: 2
2004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: = dbo.NEXTKEYZZZbIGIp$7;1
2004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: U = SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:2
2004-05-21 16:07:58.18 spid4 KEY: 5:1685581043:2 (6401bf0349e3) = CleanCnt:1 Mode: U Flags: 0x0
2004-05-21 16:07:58.18 spid4 Grant List 2::
2004-05-21 16:07:58.18 spid4 Owner:0x70573a40 Mode: U = Flg:0x0 Ref:1 Life:00000000 SPID:51 ECID:0
2004-05-21 16:07:58.18 spid4 SPID: 51 ECID: 0 Statement Type: = UPDATE Line #: 2
2004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: = dbo.NEXTKEYZZZbIGIp$7;1
2004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: U = SPID:54 ECID:0 Ec:(0x7A6B59B0) Value:0x79f4cac0 Cost:(0/148)
2004-05-21 16:07:58.18 spid4 Victim Resource Owner:
2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: U = SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)
2004-05-21 16:11:50.78 spid4 Victim Resource Owner:
2004-05-21 16:11:50.78 spid4 ResType:ExchangeId Stype:'AND' SPID:69 = ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
2004-05-21 16:11:55.78 spid4 Victim Resource Owner:
2004-05-21 16:11:55.78 spid4 ResType:ExchangeId Stype:'AND' SPID:69 = ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
--=_NextPart_000_0058_01C43F8A.9695C150
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
I am finding some unusual deadlock = victum messages in my errorlogs that I have included in this message. I would = appreciate any information about these messages. I am familiar with the = normal deadlock message, it is the statements in red that I need help with.
thanks
tim
2004-05-21 16:07:58.18 spid4 Deadlock encountered ... Printing = deadlock information2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Wait-for graph2004-05-21 16:07:58.18 spid4 = 2004-05-21 16:07:58.18 spid4 Node:12004-05-21 = 16:07:58.18 spid4 RID: 5:1:536178:4 &= nbsp; CleanCnt:1 Mode: X Flags: 0x22004-05-21 16:07:58.18 spid4 Grant List 3::2004-05-21 = 16:07:58.18 spid4 Owner:0x68e15860 Mode: X Flg:0x0 Ref:0 Life:02000000 = SPID:54 ECID:02004-05-21 16:07:58.18 = spid4 SPID: 54 ECID: 0 Statement Type: UPDATE Line #: 22004-05-21 = 16:07:58.18 spid4 Input Buf: RPC Event: dbo.NEXTKEYZZZbIGIp$7;12004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 = 16:07:58.18 spid4 ResType:LockOwner = Stype:'OR' Mode: U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 = Cost:(0/0)2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:22004-05-21 16:07:58.18 spid4 KEY: 5:1685581043:2 (6401bf0349e3) = CleanCnt:1 Mode: U Flags: 0x02004-05-21 16:07:58.18 = spid4 Grant List 2::2004-05-21 16:07:58.18 spid4 Owner:0x70573a40 Mode: U Flg:0x0 Ref:1 Life:00000000 = SPID:51 ECID:02004-05-21 16:07:58.18 = spid4 SPID: 51 ECID: 0 Statement Type: UPDATE Line #: 22004-05-21 = 16:07:58.18 spid4 Input Buf: RPC Event: dbo.NEXTKEYZZZbIGIp$7;12004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 = 16:07:58.18 spid4 ResType:LockOwner = Stype:'OR' Mode: U SPID:54 ECID:0 Ec:(0x7A6B59B0) Value:0x79f4cac0 Cost:(0/148)2004-05-21 16:07:58.18 spid4 = Victim Resource Owner:2004-05-21 16:07:58.18 = spid4 ResType:LockOwner Stype:'OR' Mode: U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)2004-05-21 = 16:11:50.78 spid4 Victim Resource Owner:2004-05-21 = 16:11:50.78 spid4 ResType:ExchangeId Stype:'AND' = SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)2004-05-21 = 16:11:55.78 spid4 Victim Resource Owner:2004-05-21 = 16:11:55.78 spid4 ResType:ExchangeId Stype:'AND' = SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
--=_NextPart_000_0058_01C43F8A.9695C150--This is a multi-part message in MIME format.
--=_NextPart_000_001F_01C44196.C17DBF40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi
Looks like you may have trace flag 1204 set?
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/trblsq=
l/tr_servdatabse_5xrn.asp
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/trblsq=
l/tr_servdatabse_8v5f.asp
John
"Tim Graham" <tgraham3@.metlife.com> wrote in message =news:OtlW4R7PEHA.2704@.TK2MSFTNGP10.phx.gbl...
I am finding some unusual deadlock victum messages in my errorlogs =that I have included in this message. I would appreciate any =information about these messages. I am familiar with the normal =deadlock message, it is the statements in red that I need help with.
thanks
tim
2004-05-21 16:07:58.18 spid4 Deadlock encountered ... Printing deadlock information
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Wait-for graph
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:1
2004-05-21 16:07:58.18 spid4 RID: 5:1:536178:4 =CleanCnt:1 Mode: X Flags: 0x2
2004-05-21 16:07:58.18 spid4 Grant List 3::
2004-05-21 16:07:58.18 spid4 Owner:0x68e15860 Mode: X =Flg:0x0 Ref:0 Life:02000000 SPID:54 ECID:0
2004-05-21 16:07:58.18 spid4 SPID: 54 ECID: 0 Statement Type: =UPDATE Line #: 2
2004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: =dbo.NEXTKEYZZZbIGIp$7;1
2004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: =U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:2
2004-05-21 16:07:58.18 spid4 KEY: 5:1685581043:2 (6401bf0349e3) =CleanCnt:1 Mode: U Flags: 0x0
2004-05-21 16:07:58.18 spid4 Grant List 2::
2004-05-21 16:07:58.18 spid4 Owner:0x70573a40 Mode: U =Flg:0x0 Ref:1 Life:00000000 SPID:51 ECID:0
2004-05-21 16:07:58.18 spid4 SPID: 51 ECID: 0 Statement Type: =UPDATE Line #: 2
2004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: =dbo.NEXTKEYZZZbIGIp$7;1
2004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: =U SPID:54 ECID:0 Ec:(0x7A6B59B0) Value:0x79f4cac0 Cost:(0/148)
2004-05-21 16:07:58.18 spid4 Victim Resource Owner:
2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: U =SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)
2004-05-21 16:11:50.78 spid4 Victim Resource Owner:
2004-05-21 16:11:50.78 spid4 ResType:ExchangeId Stype:'AND' =SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
2004-05-21 16:11:55.78 spid4 Victim Resource Owner:
2004-05-21 16:11:55.78 spid4 ResType:ExchangeId Stype:'AND' =SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
--=_NextPart_000_001F_01C44196.C17DBF40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi
Looks like you may have trace flag =1204 set?
http://msdn.microsoft.com/library/defa=ult.asp?url=3D/library/en-us/trblsql/tr_servdatabse_5xrn.asp
http://msdn.microsoft.com/library/defa=ult.asp?url=3D/library/en-us/trblsql/tr_servdatabse_8v5f.asp
John
"Tim Graham" =wrote in message news:OtlW4R7PEHA.2704=@.TK2MSFTNGP10.phx.gbl...
I am finding some unusual deadlock =victum messages in my errorlogs that I have included in this message. I =would appreciate any information about these messages. I am familiar =with the normal deadlock message, it is the statements in red that I need help with.
thanks
tim
2004-05-21 16:07:58.18 spid4 Deadlock encountered ... Printing =deadlock information2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Wait-for graph2004-05-21 16:07:58.18 spid4 =2004-05-21 16:07:58.18 spid4 Node:12004-05-21 =16:07:58.18 spid4 RID: =5:1:536178:4 &=nbsp; CleanCnt:1 Mode: X Flags: 0x22004-05-21 16:07:58.18 spid4 Grant List 3::2004-05-21 =16:07:58.18 spid4 Owner:0x68e15860 Mode: = X Flg:0x0 Ref:0 =Life:02000000 SPID:54 ECID:02004-05-21 16:07:58.18 spid4 SPID: 54 ECID: 0 =Statement Type: UPDATE Line #: 22004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: dbo.NEXTKEYZZZbIGIp$7;12004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 =16:07:58.18 spid4 ResType:LockOwner =Stype:'OR' Mode: U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 =Node:22004-05-21 16:07:58.18 spid4 KEY: 5:1685581043:2 =(6401bf0349e3) CleanCnt:1 Mode: U Flags: 0x02004-05-21 16:07:58.18 spid4 Grant List 2::2004-05-21 =16:07:58.18 spid4 Owner:0x70573a40 Mode: = U Flg:0x0 Ref:1 =Life:00000000 SPID:51 ECID:02004-05-21 16:07:58.18 spid4 SPID: 51 ECID: 0 =Statement Type: UPDATE Line #: 22004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: dbo.NEXTKEYZZZbIGIp$7;12004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 =16:07:58.18 spid4 ResType:LockOwner =Stype:'OR' Mode: U SPID:54 ECID:0 Ec:(0x7A6B59B0) Value:0x79f4cac0 Cost:(0/148)2004-05-21 16:07:58.18 spid4 =Victim Resource Owner:2004-05-21 16:07:58.18 =spid4 ResType:LockOwner Stype:'OR' Mode: U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)2004-05-21 =16:11:50.78 spid4 Victim Resource Owner:2004-05-21 =16:11:50.78 spid4 ResType:ExchangeId Stype:'AND' =SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)2004-05-21 16:11:55.78 spid4 Victim Resource =Owner:2004-05-21 16:11:55.78 spid4 ResType:ExchangeId =Stype:'AND' SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
--=_NextPart_000_001F_01C44196.C17DBF40--
--=_NextPart_000_0058_01C43F8A.9695C150
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am finding some unusual deadlock victum messages in my errorlogs that = I have included in this message. I would appreciate any information = about these messages. I am familiar with the normal deadlock message, = it is the statements in red that I need help with.
thanks
tim
2004-05-21 16:07:58.18 spid4 Deadlock encountered ... Printing deadlock information
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Wait-for graph
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:1
2004-05-21 16:07:58.18 spid4 RID: 5:1:536178:4 = CleanCnt:1 Mode: X Flags: 0x2
2004-05-21 16:07:58.18 spid4 Grant List 3::
2004-05-21 16:07:58.18 spid4 Owner:0x68e15860 Mode: X = Flg:0x0 Ref:0 Life:02000000 SPID:54 ECID:0
2004-05-21 16:07:58.18 spid4 SPID: 54 ECID: 0 Statement Type: = UPDATE Line #: 2
2004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: = dbo.NEXTKEYZZZbIGIp$7;1
2004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: U = SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:2
2004-05-21 16:07:58.18 spid4 KEY: 5:1685581043:2 (6401bf0349e3) = CleanCnt:1 Mode: U Flags: 0x0
2004-05-21 16:07:58.18 spid4 Grant List 2::
2004-05-21 16:07:58.18 spid4 Owner:0x70573a40 Mode: U = Flg:0x0 Ref:1 Life:00000000 SPID:51 ECID:0
2004-05-21 16:07:58.18 spid4 SPID: 51 ECID: 0 Statement Type: = UPDATE Line #: 2
2004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: = dbo.NEXTKEYZZZbIGIp$7;1
2004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: U = SPID:54 ECID:0 Ec:(0x7A6B59B0) Value:0x79f4cac0 Cost:(0/148)
2004-05-21 16:07:58.18 spid4 Victim Resource Owner:
2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: U = SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)
2004-05-21 16:11:50.78 spid4 Victim Resource Owner:
2004-05-21 16:11:50.78 spid4 ResType:ExchangeId Stype:'AND' SPID:69 = ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
2004-05-21 16:11:55.78 spid4 Victim Resource Owner:
2004-05-21 16:11:55.78 spid4 ResType:ExchangeId Stype:'AND' SPID:69 = ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
--=_NextPart_000_0058_01C43F8A.9695C150
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
I am finding some unusual deadlock = victum messages in my errorlogs that I have included in this message. I would = appreciate any information about these messages. I am familiar with the = normal deadlock message, it is the statements in red that I need help with.
thanks
tim
2004-05-21 16:07:58.18 spid4 Deadlock encountered ... Printing = deadlock information2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Wait-for graph2004-05-21 16:07:58.18 spid4 = 2004-05-21 16:07:58.18 spid4 Node:12004-05-21 = 16:07:58.18 spid4 RID: 5:1:536178:4 &= nbsp; CleanCnt:1 Mode: X Flags: 0x22004-05-21 16:07:58.18 spid4 Grant List 3::2004-05-21 = 16:07:58.18 spid4 Owner:0x68e15860 Mode: X Flg:0x0 Ref:0 Life:02000000 = SPID:54 ECID:02004-05-21 16:07:58.18 = spid4 SPID: 54 ECID: 0 Statement Type: UPDATE Line #: 22004-05-21 = 16:07:58.18 spid4 Input Buf: RPC Event: dbo.NEXTKEYZZZbIGIp$7;12004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 = 16:07:58.18 spid4 ResType:LockOwner = Stype:'OR' Mode: U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 = Cost:(0/0)2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:22004-05-21 16:07:58.18 spid4 KEY: 5:1685581043:2 (6401bf0349e3) = CleanCnt:1 Mode: U Flags: 0x02004-05-21 16:07:58.18 = spid4 Grant List 2::2004-05-21 16:07:58.18 spid4 Owner:0x70573a40 Mode: U Flg:0x0 Ref:1 Life:00000000 = SPID:51 ECID:02004-05-21 16:07:58.18 = spid4 SPID: 51 ECID: 0 Statement Type: UPDATE Line #: 22004-05-21 = 16:07:58.18 spid4 Input Buf: RPC Event: dbo.NEXTKEYZZZbIGIp$7;12004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 = 16:07:58.18 spid4 ResType:LockOwner = Stype:'OR' Mode: U SPID:54 ECID:0 Ec:(0x7A6B59B0) Value:0x79f4cac0 Cost:(0/148)2004-05-21 16:07:58.18 spid4 = Victim Resource Owner:2004-05-21 16:07:58.18 = spid4 ResType:LockOwner Stype:'OR' Mode: U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)2004-05-21 = 16:11:50.78 spid4 Victim Resource Owner:2004-05-21 = 16:11:50.78 spid4 ResType:ExchangeId Stype:'AND' = SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)2004-05-21 = 16:11:55.78 spid4 Victim Resource Owner:2004-05-21 = 16:11:55.78 spid4 ResType:ExchangeId Stype:'AND' = SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
--=_NextPart_000_0058_01C43F8A.9695C150--This is a multi-part message in MIME format.
--=_NextPart_000_001F_01C44196.C17DBF40
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi
Looks like you may have trace flag 1204 set?
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/trblsq=
l/tr_servdatabse_5xrn.asp
http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/trblsq=
l/tr_servdatabse_8v5f.asp
John
"Tim Graham" <tgraham3@.metlife.com> wrote in message =news:OtlW4R7PEHA.2704@.TK2MSFTNGP10.phx.gbl...
I am finding some unusual deadlock victum messages in my errorlogs =that I have included in this message. I would appreciate any =information about these messages. I am familiar with the normal =deadlock message, it is the statements in red that I need help with.
thanks
tim
2004-05-21 16:07:58.18 spid4 Deadlock encountered ... Printing deadlock information
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Wait-for graph
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:1
2004-05-21 16:07:58.18 spid4 RID: 5:1:536178:4 =CleanCnt:1 Mode: X Flags: 0x2
2004-05-21 16:07:58.18 spid4 Grant List 3::
2004-05-21 16:07:58.18 spid4 Owner:0x68e15860 Mode: X =Flg:0x0 Ref:0 Life:02000000 SPID:54 ECID:0
2004-05-21 16:07:58.18 spid4 SPID: 54 ECID: 0 Statement Type: =UPDATE Line #: 2
2004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: =dbo.NEXTKEYZZZbIGIp$7;1
2004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: =U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)
2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Node:2
2004-05-21 16:07:58.18 spid4 KEY: 5:1685581043:2 (6401bf0349e3) =CleanCnt:1 Mode: U Flags: 0x0
2004-05-21 16:07:58.18 spid4 Grant List 2::
2004-05-21 16:07:58.18 spid4 Owner:0x70573a40 Mode: U =Flg:0x0 Ref:1 Life:00000000 SPID:51 ECID:0
2004-05-21 16:07:58.18 spid4 SPID: 51 ECID: 0 Statement Type: =UPDATE Line #: 2
2004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: =dbo.NEXTKEYZZZbIGIp$7;1
2004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: =U SPID:54 ECID:0 Ec:(0x7A6B59B0) Value:0x79f4cac0 Cost:(0/148)
2004-05-21 16:07:58.18 spid4 Victim Resource Owner:
2004-05-21 16:07:58.18 spid4 ResType:LockOwner Stype:'OR' Mode: U =SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)
2004-05-21 16:11:50.78 spid4 Victim Resource Owner:
2004-05-21 16:11:50.78 spid4 ResType:ExchangeId Stype:'AND' =SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
2004-05-21 16:11:55.78 spid4 Victim Resource Owner:
2004-05-21 16:11:55.78 spid4 ResType:ExchangeId Stype:'AND' =SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
--=_NextPart_000_001F_01C44196.C17DBF40
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi
Looks like you may have trace flag =1204 set?
http://msdn.microsoft.com/library/defa=ult.asp?url=3D/library/en-us/trblsql/tr_servdatabse_5xrn.asp
http://msdn.microsoft.com/library/defa=ult.asp?url=3D/library/en-us/trblsql/tr_servdatabse_8v5f.asp
John
"Tim Graham"
I am finding some unusual deadlock =victum messages in my errorlogs that I have included in this message. I =would appreciate any information about these messages. I am familiar =with the normal deadlock message, it is the statements in red that I need help with.
thanks
tim
2004-05-21 16:07:58.18 spid4 Deadlock encountered ... Printing =deadlock information2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 Wait-for graph2004-05-21 16:07:58.18 spid4 =2004-05-21 16:07:58.18 spid4 Node:12004-05-21 =16:07:58.18 spid4 RID: =5:1:536178:4 &=nbsp; CleanCnt:1 Mode: X Flags: 0x22004-05-21 16:07:58.18 spid4 Grant List 3::2004-05-21 =16:07:58.18 spid4 Owner:0x68e15860 Mode: = X Flg:0x0 Ref:0 =Life:02000000 SPID:54 ECID:02004-05-21 16:07:58.18 spid4 SPID: 54 ECID: 0 =Statement Type: UPDATE Line #: 22004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: dbo.NEXTKEYZZZbIGIp$7;12004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 =16:07:58.18 spid4 ResType:LockOwner =Stype:'OR' Mode: U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)2004-05-21 16:07:58.18 spid4 2004-05-21 16:07:58.18 spid4 =Node:22004-05-21 16:07:58.18 spid4 KEY: 5:1685581043:2 =(6401bf0349e3) CleanCnt:1 Mode: U Flags: 0x02004-05-21 16:07:58.18 spid4 Grant List 2::2004-05-21 =16:07:58.18 spid4 Owner:0x70573a40 Mode: = U Flg:0x0 Ref:1 =Life:00000000 SPID:51 ECID:02004-05-21 16:07:58.18 spid4 SPID: 51 ECID: 0 =Statement Type: UPDATE Line #: 22004-05-21 16:07:58.18 spid4 Input Buf: RPC Event: dbo.NEXTKEYZZZbIGIp$7;12004-05-21 16:07:58.18 spid4 Requested By: 2004-05-21 =16:07:58.18 spid4 ResType:LockOwner =Stype:'OR' Mode: U SPID:54 ECID:0 Ec:(0x7A6B59B0) Value:0x79f4cac0 Cost:(0/148)2004-05-21 16:07:58.18 spid4 =Victim Resource Owner:2004-05-21 16:07:58.18 =spid4 ResType:LockOwner Stype:'OR' Mode: U SPID:51 ECID:0 Ec:(0x7DD3D9B0) Value:0x705729e0 Cost:(0/0)2004-05-21 =16:11:50.78 spid4 Victim Resource Owner:2004-05-21 =16:11:50.78 spid4 ResType:ExchangeId Stype:'AND' =SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)2004-05-21 16:11:55.78 spid4 Victim Resource =Owner:2004-05-21 16:11:55.78 spid4 ResType:ExchangeId =Stype:'AND' SPID:69 ECID:22 Ec:(0x75A58098) Value:0x800f3988 Cost:(0/2710)
--=_NextPart_000_001F_01C44196.C17DBF40--
Labels:
_nextpart_000_0058_01c43f8a,
9695c150,
charset,
content-type,
database,
format,
iso-8859-1,
message,
messages,
microsoft,
mime,
multi-part,
mysql,
oracle,
plain,
server,
sql,
text,
unusual,
victum
Subscribe to:
Posts (Atom)