when I restore the database from a backup file.I failed
the code is "SQLstate 42000
because my sql server is chines
the message means
database "xxx" has 2 family members,but now provide 1
I think there is miss the log
how can I do?From the error msg it sounds like you striped your backup across multiple
devices and you have only specified 1 for the restore.
Provide all file locations that you backed up for that set when restoring.
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:30617EBA-03E3-492F-986A-C85E94F15F72@.microsoft.com...
> when I restore the database from a backup file.I failed.
> the code is "SQLstate 42000"
> because my sql server is chinese
> the message means:
> database "xxx" has 2 family members,but now provide 1.
> I think there is miss the log.
> how can I do?|||but the file is my friend gave me
and now cannot backup again from original database
how can I do?|||> but the file is my friend gave me.
Can you re-phrase that?
> and now cannot backup again from original database.
> how can I do?
By original, do you mean the database you tried to restore into or the one that the backup was
produced on?
Can you explain a little bit more details what happened?
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:6486E3F3-83D8-4506-91E7-F3B3B2344045@.microsoft.com...
> but the file is my friend gave me.
> and now cannot backup again from original database.
> how can I do?|||because the computer's hard disk was broken
so the data was los
he gave me the backup file is the only file.|||Just read about the RESTORE command in Books Online and do the restore based on your backup file
(from Query analyzer).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:A1A4F50B-4ED9-4634-BD25-AB89D21C2729@.microsoft.com...
> because the computer's hard disk was broken.
> so the data was lost
> he gave me the backup file is the only file.|||which topic can I found?
can you type the command for me?
thank you!
-- Tibor Karaszi wrote: --
Just read about the RESTORE command in Books Online and do the restore based on your backup file
(from Query analyzer).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Silence" <anonymous@.discussions.microsoft.com> wrote in message
news:A1A4F50B-4ED9-4634-BD25-AB89D21C2729@.microsoft.com...
> because the computer's hard disk was broken.
> so the data was lost
> he gave me the backup file is the only file.|||The exact command to type depends on a lot of factors (the path to the backup file, the path to the
database files etc etc). In Books Online, you find the Transact-SQL Reference. Here you find the
RESTORE command documented.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"silence" <zjflyer@.hotmail.com> wrote in message
news:D32AE25A-E164-4B87-BD77-EE3B9E7C054C@.microsoft.com...
> which topic can I found?
> can you type the command for me?
> thank you!
> -- Tibor Karaszi wrote: --
> Just read about the RESTORE command in Books Online and do the restore based on your backup
file
> (from Query analyzer).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Silence" <anonymous@.discussions.microsoft.com> wrote in message
> news:A1A4F50B-4ED9-4634-BD25-AB89D21C2729@.microsoft.com...
> > because the computer's hard disk was broken.
> > so the data was lost
> > he gave me the backup file is the only file.
>
>
Showing posts with label message. Show all posts
Showing posts with label message. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
HELP! Server Error in '/Reports' Application.
Infrequently I get the following error message when trying to access the
report manager.
Server Error in '/Reports' Application.
----
Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: Assembly microsoft.crm.platform.types.dll security
permission grant set is incompatible between appdomains.
Source Error:
Line 5: <assemblies>
Line 6: <add assembly="Microsoft.Crm.Platform.ComProxy,
Version=1.0.0000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
Line 7: <add assembly="Microsoft.Crm.Platform.Types,
Version=1.2.3297.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
Line 8: </assemblies>
Line 9: </compilation>
Source File: d:\inetpub\wwwroot\web.config Line: 7
----
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573You likely have a Code Access Security issue. This can be a complex issue to
describe, but Reporting Services is very fussy over code security. Basically
the default permissions of any code running in Reporting Services (RS) is
in-memory execution. Perhaps your assembly is trying to do something beyond
this. In that case you need to configure security in the files
rspreviewpolicy.config and rssrvpolicy.config. I would start by debugging
your assembly as you debug run your report from Visual Studio.
Look at the following msdn article:
http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/dngrfCodeAccessSecurityInSQLServer2000ReportingServices.asp?frame=true
The bottom line is that you need to fully understand code access security to
deploy any custom assembly. It would be very difficult to troubleshoot what
your problem is without looking closely at your code.
Charles Kangai, MCT, MCDBA
"SAcanuck" wrote:
> Infrequently I get the following error message when trying to access the
> report manager.
>
> Server Error in '/Reports' Application.
> ----
> Configuration Error
> Description: An error occurred during the processing of a configuration file
> required to service this request. Please review the specific error details
> below and modify your configuration file appropriately.
> Parser Error Message: Assembly microsoft.crm.platform.types.dll security
> permission grant set is incompatible between appdomains.
> Source Error:
>
> Line 5: <assemblies>
> Line 6: <add assembly="Microsoft.Crm.Platform.ComProxy,
> Version=1.0.0000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> Line 7: <add assembly="Microsoft.Crm.Platform.Types,
> Version=1.2.3297.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> Line 8: </assemblies>
> Line 9: </compilation>
>
> Source File: d:\inetpub\wwwroot\web.config Line: 7
>
> ----
> Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
> Version:1.1.4322.573|||Hi Charles:
Maybe Im just not understanding you...but we are using Reporting Services as
is...with no customized security. The problem is that we have MS CRM and
Reporting Services on the same server and we occassionally get the error
message.
"Charles Kangai" wrote:
> You likely have a Code Access Security issue. This can be a complex issue to
> describe, but Reporting Services is very fussy over code security. Basically
> the default permissions of any code running in Reporting Services (RS) is
> in-memory execution. Perhaps your assembly is trying to do something beyond
> this. In that case you need to configure security in the files
> rspreviewpolicy.config and rssrvpolicy.config. I would start by debugging
> your assembly as you debug run your report from Visual Studio.
> Look at the following msdn article:
> http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/dngrfCodeAccessSecurityInSQLServer2000ReportingServices.asp?frame=true
> The bottom line is that you need to fully understand code access security to
> deploy any custom assembly. It would be very difficult to troubleshoot what
> your problem is without looking closely at your code.
> Charles Kangai, MCT, MCDBA
>
> "SAcanuck" wrote:
> > Infrequently I get the following error message when trying to access the
> > report manager.
> >
> >
> > Server Error in '/Reports' Application.
> > ----
> >
> > Configuration Error
> > Description: An error occurred during the processing of a configuration file
> > required to service this request. Please review the specific error details
> > below and modify your configuration file appropriately.
> >
> > Parser Error Message: Assembly microsoft.crm.platform.types.dll security
> > permission grant set is incompatible between appdomains.
> >
> > Source Error:
> >
> >
> > Line 5: <assemblies>
> > Line 6: <add assembly="Microsoft.Crm.Platform.ComProxy,
> > Version=1.0.0000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> > Line 7: <add assembly="Microsoft.Crm.Platform.Types,
> > Version=1.2.3297.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> > Line 8: </assemblies>
> > Line 9: </compilation>
> >
> >
> > Source File: d:\inetpub\wwwroot\web.config Line: 7
> >
> >
> > ----
> > Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
> > Version:1.1.4322.573|||Greetings,
I had installed the SQL Reporting Services and then I installed the
microsoft CRM. I am facing the same error which SAcanuck is also facing.
I will really appreciate if any of you guys can help us out here.
Regards
"SAcanuck" wrote:
> Hi Charles:
> Maybe Im just not understanding you...but we are using Reporting Services as
> is...with no customized security. The problem is that we have MS CRM and
> Reporting Services on the same server and we occassionally get the error
> message.
> "Charles Kangai" wrote:
> > You likely have a Code Access Security issue. This can be a complex issue to
> > describe, but Reporting Services is very fussy over code security. Basically
> > the default permissions of any code running in Reporting Services (RS) is
> > in-memory execution. Perhaps your assembly is trying to do something beyond
> > this. In that case you need to configure security in the files
> > rspreviewpolicy.config and rssrvpolicy.config. I would start by debugging
> > your assembly as you debug run your report from Visual Studio.
> >
> > Look at the following msdn article:
> > http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/dngrfCodeAccessSecurityInSQLServer2000ReportingServices.asp?frame=true
> >
> > The bottom line is that you need to fully understand code access security to
> > deploy any custom assembly. It would be very difficult to troubleshoot what
> > your problem is without looking closely at your code.
> >
> > Charles Kangai, MCT, MCDBA
> >
> >
> > "SAcanuck" wrote:
> >
> > > Infrequently I get the following error message when trying to access the
> > > report manager.
> > >
> > >
> > > Server Error in '/Reports' Application.
> > > ----
> > >
> > > Configuration Error
> > > Description: An error occurred during the processing of a configuration file
> > > required to service this request. Please review the specific error details
> > > below and modify your configuration file appropriately.
> > >
> > > Parser Error Message: Assembly microsoft.crm.platform.types.dll security
> > > permission grant set is incompatible between appdomains.
> > >
> > > Source Error:
> > >
> > >
> > > Line 5: <assemblies>
> > > Line 6: <add assembly="Microsoft.Crm.Platform.ComProxy,
> > > Version=1.0.0000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> > > Line 7: <add assembly="Microsoft.Crm.Platform.Types,
> > > Version=1.2.3297.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> > > Line 8: </assemblies>
> > > Line 9: </compilation>
> > >
> > >
> > > Source File: d:\inetpub\wwwroot\web.config Line: 7
> > >
> > >
> > > ----
> > > Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
> > > Version:1.1.4322.573
report manager.
Server Error in '/Reports' Application.
----
Configuration Error
Description: An error occurred during the processing of a configuration file
required to service this request. Please review the specific error details
below and modify your configuration file appropriately.
Parser Error Message: Assembly microsoft.crm.platform.types.dll security
permission grant set is incompatible between appdomains.
Source Error:
Line 5: <assemblies>
Line 6: <add assembly="Microsoft.Crm.Platform.ComProxy,
Version=1.0.0000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
Line 7: <add assembly="Microsoft.Crm.Platform.Types,
Version=1.2.3297.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
Line 8: </assemblies>
Line 9: </compilation>
Source File: d:\inetpub\wwwroot\web.config Line: 7
----
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573You likely have a Code Access Security issue. This can be a complex issue to
describe, but Reporting Services is very fussy over code security. Basically
the default permissions of any code running in Reporting Services (RS) is
in-memory execution. Perhaps your assembly is trying to do something beyond
this. In that case you need to configure security in the files
rspreviewpolicy.config and rssrvpolicy.config. I would start by debugging
your assembly as you debug run your report from Visual Studio.
Look at the following msdn article:
http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/dngrfCodeAccessSecurityInSQLServer2000ReportingServices.asp?frame=true
The bottom line is that you need to fully understand code access security to
deploy any custom assembly. It would be very difficult to troubleshoot what
your problem is without looking closely at your code.
Charles Kangai, MCT, MCDBA
"SAcanuck" wrote:
> Infrequently I get the following error message when trying to access the
> report manager.
>
> Server Error in '/Reports' Application.
> ----
> Configuration Error
> Description: An error occurred during the processing of a configuration file
> required to service this request. Please review the specific error details
> below and modify your configuration file appropriately.
> Parser Error Message: Assembly microsoft.crm.platform.types.dll security
> permission grant set is incompatible between appdomains.
> Source Error:
>
> Line 5: <assemblies>
> Line 6: <add assembly="Microsoft.Crm.Platform.ComProxy,
> Version=1.0.0000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> Line 7: <add assembly="Microsoft.Crm.Platform.Types,
> Version=1.2.3297.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> Line 8: </assemblies>
> Line 9: </compilation>
>
> Source File: d:\inetpub\wwwroot\web.config Line: 7
>
> ----
> Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
> Version:1.1.4322.573|||Hi Charles:
Maybe Im just not understanding you...but we are using Reporting Services as
is...with no customized security. The problem is that we have MS CRM and
Reporting Services on the same server and we occassionally get the error
message.
"Charles Kangai" wrote:
> You likely have a Code Access Security issue. This can be a complex issue to
> describe, but Reporting Services is very fussy over code security. Basically
> the default permissions of any code running in Reporting Services (RS) is
> in-memory execution. Perhaps your assembly is trying to do something beyond
> this. In that case you need to configure security in the files
> rspreviewpolicy.config and rssrvpolicy.config. I would start by debugging
> your assembly as you debug run your report from Visual Studio.
> Look at the following msdn article:
> http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/dngrfCodeAccessSecurityInSQLServer2000ReportingServices.asp?frame=true
> The bottom line is that you need to fully understand code access security to
> deploy any custom assembly. It would be very difficult to troubleshoot what
> your problem is without looking closely at your code.
> Charles Kangai, MCT, MCDBA
>
> "SAcanuck" wrote:
> > Infrequently I get the following error message when trying to access the
> > report manager.
> >
> >
> > Server Error in '/Reports' Application.
> > ----
> >
> > Configuration Error
> > Description: An error occurred during the processing of a configuration file
> > required to service this request. Please review the specific error details
> > below and modify your configuration file appropriately.
> >
> > Parser Error Message: Assembly microsoft.crm.platform.types.dll security
> > permission grant set is incompatible between appdomains.
> >
> > Source Error:
> >
> >
> > Line 5: <assemblies>
> > Line 6: <add assembly="Microsoft.Crm.Platform.ComProxy,
> > Version=1.0.0000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> > Line 7: <add assembly="Microsoft.Crm.Platform.Types,
> > Version=1.2.3297.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> > Line 8: </assemblies>
> > Line 9: </compilation>
> >
> >
> > Source File: d:\inetpub\wwwroot\web.config Line: 7
> >
> >
> > ----
> > Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
> > Version:1.1.4322.573|||Greetings,
I had installed the SQL Reporting Services and then I installed the
microsoft CRM. I am facing the same error which SAcanuck is also facing.
I will really appreciate if any of you guys can help us out here.
Regards
"SAcanuck" wrote:
> Hi Charles:
> Maybe Im just not understanding you...but we are using Reporting Services as
> is...with no customized security. The problem is that we have MS CRM and
> Reporting Services on the same server and we occassionally get the error
> message.
> "Charles Kangai" wrote:
> > You likely have a Code Access Security issue. This can be a complex issue to
> > describe, but Reporting Services is very fussy over code security. Basically
> > the default permissions of any code running in Reporting Services (RS) is
> > in-memory execution. Perhaps your assembly is trying to do something beyond
> > this. In that case you need to configure security in the files
> > rspreviewpolicy.config and rssrvpolicy.config. I would start by debugging
> > your assembly as you debug run your report from Visual Studio.
> >
> > Look at the following msdn article:
> > http://msdn.microsoft.com/library/?url=/library/en-us/dnsql2k/html/dngrfCodeAccessSecurityInSQLServer2000ReportingServices.asp?frame=true
> >
> > The bottom line is that you need to fully understand code access security to
> > deploy any custom assembly. It would be very difficult to troubleshoot what
> > your problem is without looking closely at your code.
> >
> > Charles Kangai, MCT, MCDBA
> >
> >
> > "SAcanuck" wrote:
> >
> > > Infrequently I get the following error message when trying to access the
> > > report manager.
> > >
> > >
> > > Server Error in '/Reports' Application.
> > > ----
> > >
> > > Configuration Error
> > > Description: An error occurred during the processing of a configuration file
> > > required to service this request. Please review the specific error details
> > > below and modify your configuration file appropriately.
> > >
> > > Parser Error Message: Assembly microsoft.crm.platform.types.dll security
> > > permission grant set is incompatible between appdomains.
> > >
> > > Source Error:
> > >
> > >
> > > Line 5: <assemblies>
> > > Line 6: <add assembly="Microsoft.Crm.Platform.ComProxy,
> > > Version=1.0.0000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> > > Line 7: <add assembly="Microsoft.Crm.Platform.Types,
> > > Version=1.2.3297.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
> > > Line 8: </assemblies>
> > > Line 9: </compilation>
> > >
> > >
> > > Source File: d:\inetpub\wwwroot\web.config Line: 7
> > >
> > >
> > > ----
> > > Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
> > > Version:1.1.4322.573
Friday, March 9, 2012
HELP! Cannot connect !
While I am connecting to SQL server 2000 EE from a
different client machine using Query Analyzer it gives me
the following error message .
Unable to connect to server >
Server : MSG 18452 Level 16 state 1
[Microsoft ODBC ][SQL Server Driver][SQL server] Login
failed for user '(null)' Reason , not associated with a
trusted SQL server connection.
I can connect to two other SQL servers in the same domain
just fine with QueryAnalyzer. The machine that I cannot
connect to is also my PDC. It is running Win2KSP4, the
client is WinXPSP1. I've added and removed the machine
from the domain (at my wits end) just to make sure the
accounts are not cached. This is the only computer I'm
having these client problems with, no matter who logs in.
SQL Server I cannot connect to using Windows Login is
also my PDC (Development environment)
I can connect to two other SQL servers that are member
servers on the same domain. All servers are running
SQL2000EE/SP3a MDAC 2.7SP1 on Win2K, including domain
controller.
I can log into the SQL server in question using sa
account from the client (which is running
XPSP1/SQL2000Tools/MDAC2.7FOR XP.
If I try to add databases using Enterprise Manager from
the client, I can add the other two DB servers, however I
get the same error when trying to add the SQL server in
question.
I'm stumped as the Windows Domain account has to be
working as I can authenticate to connect to the domain as
well as the other two SQL servers. (I've tried this with
a regular user account with SQL rights as well as my
domain admin account which has SQL rights.
I can connect to the server in question from any other
client in the office using the two windows domain
accounts that do not work on the client.
I'd rather not reformat te client and start over as there
are other tools (Rational) installed whose license is a
real pain to get redone. BTW, all other clients have
identical configurations (Rational, etc) which work.
I've tried uninstalling/resinstalling the SQL tools/SP3a,
reset the computer domain account (doesn't matter as I
can connect to the other two servers), something in the
registry etc must have got trashed is all I can figure.
Tried removing TCP and readding using client network
utility. Tried setting up an alias in same tool. Same
result. Can connect just fine as sa.
Thanks for any suggsetions!The login failed for user NULL indicates a problem with authenticating on
the DC when attempting the connection. It could also indicate that the user
who is attempting to logon to the SQL Server does not have permission to
access the server itself. Verify that the user can map to a share on the
SQL Server machine. If he can then check the NT Security log on the DC
where he is validated and see if there are any errors generated when he
attempts to connect to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I tried this with my domain admin account as well. Can
map shares on that server ok. Can login to server using
sa or Windows login fine over Named Pipes (server set to
both auth). When I try to login over TCP, can only login
using sa, Windows Login won't work. This server is also
the single PDC (development net).. get this, can log into
two other SQL servers (member servers only) from same
client using Named Pipes AND TCP using sa or Windows
Login.
I've un-installed TCP, removed/readded machine from
domain, it has to be something on this client...|||You get that error when the sa account hasn't been set on the server. Expand
the sql server => management folder => right click sql server agent
properties =>. last tab is connection .You would see that the sql server
connection is set to use 'windows NT authentication', you would need to
change it to SQL authentication
hope that helps
Ayo Coker
"Phil" <anonymous@.discussions.microsoft.com> wrote in message
news:fa4a01c3f1a9$47689870$a501280a@.phx.gbl...
> I tried this with my domain admin account as well. Can
> map shares on that server ok. Can login to server using
> sa or Windows login fine over Named Pipes (server set to
> both auth). When I try to login over TCP, can only login
> using sa, Windows Login won't work. This server is also
> the single PDC (development net).. get this, can log into
> two other SQL servers (member servers only) from same
> client using Named Pipes AND TCP using sa or Windows
> Login.
> I've un-installed TCP, removed/readded machine from
> domain, it has to be something on this client...
>
different client machine using Query Analyzer it gives me
the following error message .
Unable to connect to server >
Server : MSG 18452 Level 16 state 1
[Microsoft ODBC ][SQL Server Driver][SQL server] Login
failed for user '(null)' Reason , not associated with a
trusted SQL server connection.
I can connect to two other SQL servers in the same domain
just fine with QueryAnalyzer. The machine that I cannot
connect to is also my PDC. It is running Win2KSP4, the
client is WinXPSP1. I've added and removed the machine
from the domain (at my wits end) just to make sure the
accounts are not cached. This is the only computer I'm
having these client problems with, no matter who logs in.
SQL Server I cannot connect to using Windows Login is
also my PDC (Development environment)
I can connect to two other SQL servers that are member
servers on the same domain. All servers are running
SQL2000EE/SP3a MDAC 2.7SP1 on Win2K, including domain
controller.
I can log into the SQL server in question using sa
account from the client (which is running
XPSP1/SQL2000Tools/MDAC2.7FOR XP.
If I try to add databases using Enterprise Manager from
the client, I can add the other two DB servers, however I
get the same error when trying to add the SQL server in
question.
I'm stumped as the Windows Domain account has to be
working as I can authenticate to connect to the domain as
well as the other two SQL servers. (I've tried this with
a regular user account with SQL rights as well as my
domain admin account which has SQL rights.
I can connect to the server in question from any other
client in the office using the two windows domain
accounts that do not work on the client.
I'd rather not reformat te client and start over as there
are other tools (Rational) installed whose license is a
real pain to get redone. BTW, all other clients have
identical configurations (Rational, etc) which work.
I've tried uninstalling/resinstalling the SQL tools/SP3a,
reset the computer domain account (doesn't matter as I
can connect to the other two servers), something in the
registry etc must have got trashed is all I can figure.
Tried removing TCP and readding using client network
utility. Tried setting up an alias in same tool. Same
result. Can connect just fine as sa.
Thanks for any suggsetions!The login failed for user NULL indicates a problem with authenticating on
the DC when attempting the connection. It could also indicate that the user
who is attempting to logon to the SQL Server does not have permission to
access the server itself. Verify that the user can map to a share on the
SQL Server machine. If he can then check the NT Security log on the DC
where he is validated and see if there are any errors generated when he
attempts to connect to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I tried this with my domain admin account as well. Can
map shares on that server ok. Can login to server using
sa or Windows login fine over Named Pipes (server set to
both auth). When I try to login over TCP, can only login
using sa, Windows Login won't work. This server is also
the single PDC (development net).. get this, can log into
two other SQL servers (member servers only) from same
client using Named Pipes AND TCP using sa or Windows
Login.
I've un-installed TCP, removed/readded machine from
domain, it has to be something on this client...|||You get that error when the sa account hasn't been set on the server. Expand
the sql server => management folder => right click sql server agent
properties =>. last tab is connection .You would see that the sql server
connection is set to use 'windows NT authentication', you would need to
change it to SQL authentication
hope that helps
Ayo Coker
"Phil" <anonymous@.discussions.microsoft.com> wrote in message
news:fa4a01c3f1a9$47689870$a501280a@.phx.gbl...
> I tried this with my domain admin account as well. Can
> map shares on that server ok. Can login to server using
> sa or Windows login fine over Named Pipes (server set to
> both auth). When I try to login over TCP, can only login
> using sa, Windows Login won't work. This server is also
> the single PDC (development net).. get this, can log into
> two other SQL servers (member servers only) from same
> client using Named Pipes AND TCP using sa or Windows
> Login.
> I've un-installed TCP, removed/readded machine from
> domain, it has to be something on this client...
>
Help! a database can not be backed up!
Hi,
I have a 80 GB database. The backup can not be completed.
The error message were:
1. BackupMedium::ReportIoError: write failure on backup
device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.).
2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
m_actualBytes: 0, m_errcode: 33, BackupFile:
d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
3. BACKUP failed to complete the command BACKUP DATABASE
[DistribuGIS] TO DISK = N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
NOSKIP , STATS = 10, NOFORMAT
I checked the disk were working fine.
I checked the database by using dbcc checkdb with
repair_rebuild option. It reported me no error found.
Please help if anything could be wrong/what should I do.
Thank you in advance.try backing up the database to a different machine that
has enough space for the database. This way you can verify
if there is something wrong with the local disk array.
>--Original Message--
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>
>.
>|||Unfortunately, since this database is big I can not try
backing up the database to a different machine.
But I have other databases in the same machine and they
all could be backed up successfully. Since this, can I say
the local disk array is ok?
Do you think this is because that the database files are
damaged?
Thank you.
>--Original Message--
>try backing up the database to a different machine that
>has enough space for the database. This way you can
verify
>if there is something wrong with the local disk array.
>
>>--Original Message--
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.
>.
>|||It's the .bak backup file that's the issue, not your
database. Something else is accessing the file - are you
also running NT backup at the same time? That puts a lock on
the file. If you are always hitting the error, try just
backing up to another file name.
Filemon from www.sysinternals.com should tell you what
process has a lock on the file.
-Sue
On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>|||To ensure the database is in a good state run DBCC CHECKDB against it
--
HTH
Ryan Waight, MCDBA, MCSE
"Juan" <juan_wu@.hotmail.com> wrote in message
news:192401c3884a$93780660$a001280a@.phx.gbl...
> Unfortunately, since this database is big I can not try
> backing up the database to a different machine.
> But I have other databases in the same machine and they
> all could be backed up successfully. Since this, can I say
> the local disk array is ok?
> Do you think this is because that the database files are
> damaged?
> Thank you.
> >--Original Message--
> >try backing up the database to a different machine that
> >has enough space for the database. This way you can
> verify
> >if there is something wrong with the local disk array.
> >
> >
> >>--Original Message--
> >>Hi,
> >>
> >>I have a 80 GB database. The backup can not be
> completed.
> >>The error message were:
> >>1. BackupMedium::ReportIoError: write failure on backup
> >>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
> >>Operating system error 33(The process cannot access the
> >>file because another process has locked a portion of the
> >>file.).
> >>
> >>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
> >>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
> >>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
> >>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
> >>m_actualBytes: 0, m_errcode: 33, BackupFile:
> >>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
> >>
> >>3. BACKUP failed to complete the command BACKUP DATABASE
> >>[DistribuGIS] TO DISK => >>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
> >>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
> >>NOSKIP , STATS = 10, NOFORMAT
> >>
> >>I checked the disk were working fine.
> >>I checked the database by using dbcc checkdb with
> >>repair_rebuild option. It reported me no error found.
> >>
> >>
> >>Please help if anything could be wrong/what should I do.
> >>
> >>Thank you in advance.
> >>
> >>
> >>.
> >>
> >.
> >|||Hi,
It got backed up successfully to a different folder. But
in the meantime, I used to back it up as compressed file
since the shortage of my disk and this time I backed it up
as normal file. Do you think the compression also possibly
cause problem?
I will try the Filemon once I got a chance.
Thank you so much for your help.
--Juan
>--Original Message--
>It's the .bak backup file that's the issue, not your
>database. Something else is accessing the file - are you
>also running NT backup at the same time? That puts a lock
on
>the file. If you are always hitting the error, try just
>backing up to another file name.
>Filemon from www.sysinternals.com should tell you what
>process has a lock on the file.
>-Sue
>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>.
>|||I'm not sure Juan - I've never messed with compression for
database backups. Filemon should show you what's locking the
file though and if it's a system process, you'll see that.
It's a good tool to have and pretty easy to use.
-Sue
On Thu, 2 Oct 2003 14:01:20 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>It got backed up successfully to a different folder. But
>in the meantime, I used to back it up as compressed file
>since the shortage of my disk and this time I backed it up
>as normal file. Do you think the compression also possibly
>cause problem?
>I will try the Filemon once I got a chance.
>Thank you so much for your help.
>--Juan
>>--Original Message--
>>It's the .bak backup file that's the issue, not your
>>database. Something else is accessing the file - are you
>>also running NT backup at the same time? That puts a lock
>on
>>the file. If you are always hitting the error, try just
>>backing up to another file name.
>>Filemon from www.sysinternals.com should tell you what
>>process has a lock on the file.
>>-Sue
>>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
>><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
>completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.
I have a 80 GB database. The backup can not be completed.
The error message were:
1. BackupMedium::ReportIoError: write failure on backup
device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.).
2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
m_actualBytes: 0, m_errcode: 33, BackupFile:
d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
3. BACKUP failed to complete the command BACKUP DATABASE
[DistribuGIS] TO DISK = N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
NOSKIP , STATS = 10, NOFORMAT
I checked the disk were working fine.
I checked the database by using dbcc checkdb with
repair_rebuild option. It reported me no error found.
Please help if anything could be wrong/what should I do.
Thank you in advance.try backing up the database to a different machine that
has enough space for the database. This way you can verify
if there is something wrong with the local disk array.
>--Original Message--
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>
>.
>|||Unfortunately, since this database is big I can not try
backing up the database to a different machine.
But I have other databases in the same machine and they
all could be backed up successfully. Since this, can I say
the local disk array is ok?
Do you think this is because that the database files are
damaged?
Thank you.
>--Original Message--
>try backing up the database to a different machine that
>has enough space for the database. This way you can
verify
>if there is something wrong with the local disk array.
>
>>--Original Message--
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.
>.
>|||It's the .bak backup file that's the issue, not your
database. Something else is accessing the file - are you
also running NT backup at the same time? That puts a lock on
the file. If you are always hitting the error, try just
backing up to another file name.
Filemon from www.sysinternals.com should tell you what
process has a lock on the file.
-Sue
On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>I have a 80 GB database. The backup can not be completed.
>The error message were:
>1. BackupMedium::ReportIoError: write failure on backup
>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>Operating system error 33(The process cannot access the
>file because another process has locked a portion of the
>file.).
>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>m_actualBytes: 0, m_errcode: 33, BackupFile:
>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>3. BACKUP failed to complete the command BACKUP DATABASE
>[DistribuGIS] TO DISK =>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>NOSKIP , STATS = 10, NOFORMAT
>I checked the disk were working fine.
>I checked the database by using dbcc checkdb with
>repair_rebuild option. It reported me no error found.
>
>Please help if anything could be wrong/what should I do.
>Thank you in advance.
>|||To ensure the database is in a good state run DBCC CHECKDB against it
--
HTH
Ryan Waight, MCDBA, MCSE
"Juan" <juan_wu@.hotmail.com> wrote in message
news:192401c3884a$93780660$a001280a@.phx.gbl...
> Unfortunately, since this database is big I can not try
> backing up the database to a different machine.
> But I have other databases in the same machine and they
> all could be backed up successfully. Since this, can I say
> the local disk array is ok?
> Do you think this is because that the database files are
> damaged?
> Thank you.
> >--Original Message--
> >try backing up the database to a different machine that
> >has enough space for the database. This way you can
> verify
> >if there is something wrong with the local disk array.
> >
> >
> >>--Original Message--
> >>Hi,
> >>
> >>I have a 80 GB database. The backup can not be
> completed.
> >>The error message were:
> >>1. BackupMedium::ReportIoError: write failure on backup
> >>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
> >>Operating system error 33(The process cannot access the
> >>file because another process has locked a portion of the
> >>file.).
> >>
> >>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
> >>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
> >>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
> >>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
> >>m_actualBytes: 0, m_errcode: 33, BackupFile:
> >>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
> >>
> >>3. BACKUP failed to complete the command BACKUP DATABASE
> >>[DistribuGIS] TO DISK => >>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
> >>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
> >>NOSKIP , STATS = 10, NOFORMAT
> >>
> >>I checked the disk were working fine.
> >>I checked the database by using dbcc checkdb with
> >>repair_rebuild option. It reported me no error found.
> >>
> >>
> >>Please help if anything could be wrong/what should I do.
> >>
> >>Thank you in advance.
> >>
> >>
> >>.
> >>
> >.
> >|||Hi,
It got backed up successfully to a different folder. But
in the meantime, I used to back it up as compressed file
since the shortage of my disk and this time I backed it up
as normal file. Do you think the compression also possibly
cause problem?
I will try the Filemon once I got a chance.
Thank you so much for your help.
--Juan
>--Original Message--
>It's the .bak backup file that's the issue, not your
>database. Something else is accessing the file - are you
>also running NT backup at the same time? That puts a lock
on
>the file. If you are always hitting the error, try just
>backing up to another file name.
>Filemon from www.sysinternals.com should tell you what
>process has a lock on the file.
>-Sue
>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>.
>|||I'm not sure Juan - I've never messed with compression for
database backups. Filemon should show you what's locking the
file though and if it's a system process, you'll see that.
It's a good tool to have and pretty easy to use.
-Sue
On Thu, 2 Oct 2003 14:01:20 -0700, "Juan"
<juan_wu@.hotmail.com> wrote:
>Hi,
>It got backed up successfully to a different folder. But
>in the meantime, I used to back it up as compressed file
>since the shortage of my disk and this time I backed it up
>as normal file. Do you think the compression also possibly
>cause problem?
>I will try the Filemon once I got a chance.
>Thank you so much for your help.
>--Juan
>>--Original Message--
>>It's the .bak backup file that's the issue, not your
>>database. Something else is accessing the file - are you
>>also running NT backup at the same time? That puts a lock
>on
>>the file. If you are always hitting the error, try just
>>backing up to another file name.
>>Filemon from www.sysinternals.com should tell you what
>>process has a lock on the file.
>>-Sue
>>On Wed, 1 Oct 2003 09:51:23 -0700, "Juan"
>><juan_wu@.hotmail.com> wrote:
>>Hi,
>>I have a 80 GB database. The backup can not be
>completed.
>>The error message were:
>>1. BackupMedium::ReportIoError: write failure on backup
>>device 'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK'.
>>Operating system error 33(The process cannot access the
>>file because another process has locked a portion of the
>>file.).
>>2. Internal I/O request 0x06614E20: Op: Write, pBuffer:
>>0x0A0D0000, Size: 983040, Position: 43656813056, UMS:
>>Internal: 0x103, InternalHigh: 0x0, Offset: 0x2A261A00,
>>OffsetHigh: 0xA, m_buf: 0x0A0D0000, m_len: 983040,
>>m_actualBytes: 0, m_errcode: 33, BackupFile:
>>d:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK
>>3. BACKUP failed to complete the command BACKUP DATABASE
>>[DistribuGIS] TO DISK =>>N'd:\gisdata\MSSQL\BACKUP\DistribuGIS_backup.BAK' WITH
>>INIT , NOUNLOAD , NAME = N'DistribuGIS_backup',
>>NOSKIP , STATS = 10, NOFORMAT
>>I checked the disk were working fine.
>>I checked the database by using dbcc checkdb with
>>repair_rebuild option. It reported me no error found.
>>
>>Please help if anything could be wrong/what should I do.
>>Thank you in advance.
>>
>>.
Wednesday, March 7, 2012
help! - could not execute sp_replcmds
I have been getting this message in the past couple of hours. I rebooted
publisher and subscriber. Even if I restart the agent - it doesn't help. I
rebuilt transactional replication from scratch and I still got this error
message. I set for the agent to output to the file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of this
agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds' on
'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of this
agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds' on
'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of this
agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
As you can see you are getting a timeout. Set querytimeout on your logreader
agent to something large and stop the distribution clean up task. You might
also want to stop the distribution agents as well.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"T" <T@.discussions.microsoft.com> wrote in message
news:C612E192-E828-4715-9A5C-5368D2719223@.microsoft.com...
>I have been getting this message in the past couple of hours. I rebooted
> publisher and subscriber. Even if I restart the agent - it doesn't help.
> I
> rebuilt transactional replication from scratch and I still got this error
> message. I set for the agent to output to the file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of this
> agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds' on
> 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a later
> time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of this
> agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds' on
> 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a later
> time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of this
> agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
>
publisher and subscriber. Even if I restart the agent - it doesn't help. I
rebuilt transactional replication from scratch and I still got this error
message. I set for the agent to output to the file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of this
agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds' on
'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of this
agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds' on
'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of this
agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
As you can see you are getting a timeout. Set querytimeout on your logreader
agent to something large and stop the distribution clean up task. You might
also want to stop the distribution agents as well.
http://www.zetainteractive.com - Shift Happens!
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"T" <T@.discussions.microsoft.com> wrote in message
news:C612E192-E828-4715-9A5C-5368D2719223@.microsoft.com...
>I have been getting this message in the past couple of hours. I rebooted
> publisher and subscriber. Even if I restart the agent - it doesn't help.
> I
> rebuilt transactional replication from scratch and I still got this error
> message. I set for the agent to output to the file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of this
> agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds' on
> 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a later
> time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of this
> agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds' on
> 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a later
> time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of this
> agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
>
Help!
Message cannot be sent whith Outlook Express! Why?
Do you use Outlook Express stand alone or do you try to send mails from within SQL Server? What did you configure how? What error did you get?
--
SvenC
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
Sunday, February 19, 2012
help with unusual victum messages
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 Cost0/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 Ec0x7A6B59B0) Value:0x79f4cac0 Cost0/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 Ec0x7DD3D9B0) Value:0x705729e0 Cost0/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 Ec0x75A58098) Value:0x800f3988 Cost0/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 Ec0x75A58098) Value:0x800f3988 Cost0/2710)
Hi
Looks like you may have trace flag 1204 set?
http://msdn.microsoft.com/library/de...tabse_5xrn.asp
http://msdn.microsoft.com/library/de...tabse_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 Ec0x7DD3D9B0) Value:0x705729e0 Cost0/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 Ec0x7A6B59B0) Value:0x79f4cac0 Cost0/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 Ec0x7DD3D9B0) Value:0x705729e0 Cost0/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 Ec0x75A58098) Value:0x800f3988 Cost0/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 Ec0x75A58098) Value:0x800f3988 Cost0/2710)
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 Cost0/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 Cost0/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 Cost0/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 Cost0/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 Cost0/2710)Hi
Looks like you may have trace flag 1204 set?
http://msdn.microsoft.com/library/de...tabse_5xrn.asp
http://msdn.microsoft.com/library/de...tabse_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 Cost0/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 Cost0/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 Cost0/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 Cost0/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 Cost0/2710)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--
help with unusual victum messages
I am finding some unusual deadlock victum messages in my errorlogs that I ha
ve included in this message. I would appreciate any information about these
messages. I am familiar with the normal deadlock message, it is the statem
ents 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 M
ode: 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.NEXTKEYZZZbIGI
p$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 SPI
D:51 ECID:0 Ec0x7DD3D9B0) Value:0x705729e0 Cost0/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.NEXTKEYZZZbIGI
p$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 SPI
D:54 ECID:0 Ec0x7A6B59B0) Value:0x79f4cac0 Cost0/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 Ec0x7DD3D9B0) Value:0x705729e0 Cost0/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 ECI
D:22 Ec0x75A58098) Value:0x800f3988 Cost0/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 ECI
D:22 Ec0x75A58098) Value:0x800f3988 Cost0/2710)Hi
Looks like you may have trace flag 1204 set?
tabse_5xrn.asp" target="_blank">http://msdn.microsoft.com/library/d...
tabse_5xrn.asp
tabse_8v5f.asp" target="_blank">http://msdn.microsoft.com/library/d...
tabse_8v5f.asp
John
"Tim Graham" <tgraham3@.metlife.com> wrote in message news:OtlW4R7PEHA.2704@.T
K2MSFTNGP10.phx.gbl...
I am finding some unusual deadlock victum messages in my errorlogs that I ha
ve included in this message. I would appreciate any information about these
messages. I am familiar with the normal deadlock message, it is the statem
ents 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 M
ode: 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.NEXTKEYZZZbIGI
p$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 SPI
D:51 ECID:0 Ec0x7DD3D9B0) Value:0x705729e0 Cost0/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.NEXTKEYZZZbIGI
p$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 SPI
D:54 ECID:0 Ec0x7A6B59B0) Value:0x79f4cac0 Cost0/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 Ec0x7DD3D9B0) Value:0x705729e0 Cost0/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 ECI
D:22 Ec0x75A58098) Value:0x800f3988 Cost0/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 ECI
D:22 Ec0x75A58098) Value:0x800f3988 Cost0/2710)
ve included in this message. I would appreciate any information about these
messages. I am familiar with the normal deadlock message, it is the statem
ents 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 M
ode: 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.NEXTKEYZZZbIGI
p$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 SPI
D:51 ECID:0 Ec
0x7DD3D9B0) Value:0x705729e0 Cost0/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.NEXTKEYZZZbIGI
p$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 SPI
D:54 ECID:0 Ec
0x7A6B59B0) Value:0x79f4cac0 Cost0/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 Cost0/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 ECI
D:22 Ec
0x75A58098) Value:0x800f3988 Cost0/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 ECI
D:22 Ec
0x75A58098) Value:0x800f3988 Cost0/2710)HiLooks like you may have trace flag 1204 set?
tabse_5xrn.asp" target="_blank">http://msdn.microsoft.com/library/d...
tabse_5xrn.asp
tabse_8v5f.asp" target="_blank">http://msdn.microsoft.com/library/d...
tabse_8v5f.asp
John
"Tim Graham" <tgraham3@.metlife.com> wrote in message news:OtlW4R7PEHA.2704@.T
K2MSFTNGP10.phx.gbl...
I am finding some unusual deadlock victum messages in my errorlogs that I ha
ve included in this message. I would appreciate any information about these
messages. I am familiar with the normal deadlock message, it is the statem
ents 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 M
ode: 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.NEXTKEYZZZbIGI
p$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 SPI
D:51 ECID:0 Ec
0x7DD3D9B0) Value:0x705729e0 Cost0/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.NEXTKEYZZZbIGI
p$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 SPI
D:54 ECID:0 Ec
0x7A6B59B0) Value:0x79f4cac0 Cost0/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 Cost0/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 ECI
D:22 Ec
0x75A58098) Value:0x800f3988 Cost0/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 ECI
D:22 Ec
0x75A58098) Value:0x800f3988 Cost0/2710)
Subscribe to:
Posts (Atom)