Couldn't connect to my server from client

I have a communication error from my client when I try to connect to my SQL
server 2000 SP4 on a Windows 2003 server. Is there any method that I can get
to see if I don't miss something when I have made the installation on the
server part ?
Every help will be welcome
Regards,
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...curity/200609/1I dont believe that SQL server keeps track of that type of information
unless you have C2 auditing enabled. You could also pick that up in a trace
file had you been tracing.
http://www.microsoft.com/technet/pr...tain/sqlc2.mspx
I could be wrong though. Does anyone else have any information?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Silver via droptable.com" <u26873@.uwe> wrote in message
news:669141b5c2b48@.uwe...
>I have a communication error from my client when I try to connect to my SQL
> server 2000 SP4 on a Windows 2003 server. Is there any method that I can
> get
> to see if I don't miss something when I have made the installation on the
> server part ?
> Every help will be welcome
> Regards,
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...curity/200609/1
>sql

Could not set working set size to 1168512 KB

hello,
We're running W2000 sp4 fr/ SQL 2000 SP3 fr and get error 17122 in the
application event log every time SQL is brought up. The error text
reads
"initdata: Warning: Could not set working set size to 1168512 KB".
What does
this really mean, is it harmful and how can I correct it? Thanks for
any info.
Thanks
A.S
Hi,
Not a real problem, this is only a warning due to incompatibility with
PAE/AWE !
Just disable the "reserve physical memory for SQLServer" by :
sp_configure 'set working set size',0
go
reconfigure with override
go
See http://support.microsoft.com/kb/822164/en-us
Guillaume.
"Zizou-Real" wrote:

> hello,
> We're running W2000 sp4 fr/ SQL 2000 SP3 fr and get error 17122 in the
> application event log every time SQL is brought up. The error text
> reads
> "initdata: Warning: Could not set working set size to 1168512 KB".
> What does
> this really mean, is it harmful and how can I correct it? Thanks for
> any info.
>
> Thank’s
> A.S
>
>
sql

could not obtain information about...

I am getting the following message in my event logs since hitting windows up
date and installing, among others SP4 for win2k.
"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Michaels B
ackup Plan'' (0x8E4169EC6E0A93468357CC016A8A9186) - Status: Failed - Invoked
on: 2004-01-19 02:00:00 - Message: The job failed. Unable to determine if
the owner (MYSERVER\mylogin) of job DB Backup Job for DB Maintenance Plan 'M
ichaels Backup Plan' has server access (reason: Could not obtain information
about Windows NT group/user 'MYSERVER\mylogin'. [SQLSTATE 42000] (Error 819
8))."
the only thing that changed was the updates, which can be significant but I
certainly didn't change anything related to my account. I have recreated th
e plan with the same result.
I can open the LOGON section of SQLadmin and see my name there, I can open i
t and close it but if I try to make any changes it says messages similar to
the above on.
KB articles suggested ading the everyone group to the pre2000 users group bu
t that sounds dangerous.
Help? what else can I look at. I am the sysop and should have all the necess
ary rightsIn message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
writes

quote:

---

>I am getting the following message in my event logs since hitting windows
>update_and installing, among others _SP4 for win2k.
>"SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan
>'Michaels Backup Plan'' (0x8E4169EC6E0A93468357CC016A8A9186) -
>Status: Failed - Invoked on: 2004-01-19 02:00:00 - Message: The job
>failed._ Unable to determine if the owner (MYSERVER\mylogin) of job DB
>Backup Job for DB Maintenance Plan 'Michaels Backup Plan' has server
>access (reason: Could not obtain information about Windows NT
>group/user 'MYSERVER\mylogin'. [SQLSTATE 42000] (Error 8198))."
>the only thing that changed was the updates, which can be significant but
>_I certainly didn't change anything related to my account. I have recreated
>the plan with the same result.
>I can open the LOGON section of SQLadmin and see my name there, I
>can open it and close it but if I try to make any changes it says messages
>similar to the above on.
>KB articles suggested ading the everyone group to the pre2000 users
>group but that sounds dangerous.
>Help? what else can I look at. I am the sysop and should have all the
>necessary rights

---

I assume you have seen KB 241643, but have you tried the first
workaround "Change the job owner to a standard SQL Server user or system
administrator (sa)."? I have read this many times, and the second option
has never worked for me, so I go straight for option 1. I suspect there
may be other causes, perhaps network issues between SQL and the DC.
PRB: 8198 Error Message Returned from Job Owned by Windows NT
Authenticated User
http://support.microsoft.com?kbid=241643
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org|||"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...

quote:

---

> In message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
> writes
recreated[QUOTE]
messages[QUOTE]
> I assume you have seen KB 241643, but have you tried the first
> workaround "Change the job owner to a standard SQL Server user or system
> administrator (sa)."? I have read this many times, and the second option
> has never worked for me, so I go straight for option 1. I suspect there
> may be other causes, perhaps network issues between SQL and the DC.
> PRB: 8198 Error Message Returned from Job Owned by Windows NT
> Authenticated User
> http://support.microsoft.com?kbid=241643
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>

---

|||Lets try that again.
I saw the KB article and I couldn't make option 2 work either so that is
encouraging :-?
The DC and the SQL server are the same machine so comms shouldn't be an
issue.
I'll try creating a new backup plan under sa but could you tell me what a
"Standard Sql Server User " is?
"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in message
news:7r2qD3R8WFEAFwOw@.sqldts.com...

quote:

---

> In message <eoafD3t3DHA.2556@.TK2MSFTNGP10.phx.gbl>, mmac <no@.thanks.com>
> writes
recreated[QUOTE]
messages[QUOTE]
> I assume you have seen KB 241643, but have you tried the first
> workaround "Change the job owner to a standard SQL Server user or system
> administrator (sa)."? I have read this many times, and the second option
> has never worked for me, so I go straight for option 1. I suspect there
> may be other causes, perhaps network issues between SQL and the DC.
> PRB: 8198 Error Message Returned from Job Owned by Windows NT
> Authenticated User
> http://support.microsoft.com?kbid=241643
>
> --
> Darren Green (SQL Server MVP)
> DTS - http://www.sqldts.com
> PASS - the definitive, global community for SQL Server professionals
> http://www.sqlpass.org
>

---

|||In message <u1fxN$d4DHA.2612@.tk2msftngp13.phx.gbl>, mmac <no@.thanks.com>
writes

quote:

---

>Lets try that again.
>I saw the KB article and I couldn't make option 2 work either so that is
>encouraging :-?
>The DC and the SQL server are the same machine so comms shouldn't be an
>issue.
>I'll try creating a new backup plan under sa but could you tell me what a
>"Standard Sql Server User " is?
>

---

A standard SQL Server user, or SQL (Server) login, is what you use as
opposed to and integrated or NT authentication login. This option is
only available if the server is set to Mixed Mode security.
sa is a SQL login, but BUILTIN\Administrators is a integrated login.
Make sense?
Darren

quote:

---

>"Darren Green" <darren.green@.reply-to-newsgroup-sqldts.com> wrote in messag
e
>news:7r2qD3R8WFEAFwOw@.sqldts.com...
>recreated
>messages
>

---

Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com
PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Could not obtain information

Hi All,
We've just recently changed/upgraded server boxes and went from Windows 2000
Server to Windows 2003 Server with
SQLServer 2000 sp4 installed on both. The Startup Service Account settings f
or both SQLServer and SQLServer
Agent is 'System Account'. On the original machine backups worked without a
flaw, but with the new machine I
receive the following error:
<<error from SQL Agent Error log>>
[298] SQLServer Error: 8198, Could not obtain information about Windows
NT group/user 'DOMAINNAME\username'.
[SQLSTATE 42000] (ConnIsLoginSysAdmin)
When remoted into the new machine with 'DOMAINNAME\username' and doing an "e
xec xp_logininfo
'DOMAINNAME\username'" in Query Analyzer I get the same error as follows:
<<error from Query Analyzer>>
Server: Msg 8198, Level 16, State 24, Procedure xp_logininfo, Line 58
Could not obtain information about Windows NT group/user 'DOMAINNAME\usernam
e'.
I've looked at kb241643 and kb834124 and realize there is a workaround, but
this same account gets locked by AD
at least a couple of times a day when I try and use it to login to this and/
or other machines I administer (this
account is an admin account used strictly for administration purposes, I hav
e an individual account that I use
for my desktop and laptop). It seems to have began shortly after I had to ch
ange the password for this account.
I believe, the error and the lockout are related (my inexperience shows as I
do not have anything concrete to
make that assumption) so I would really like to know why this is happening a
nd how to correct it.
Thank you.
gdr
--
Gary D. Rezek
University Nerworking Systems and Services
South Dakota State UniversityHi,
Is both SQL box on same Domain ? are they have the same User Account in it ?
Have you set Password Policy for Account Lockout ?if so ,after how many
attempts it locks account ? i suspect that theirs is no such user ..
Regards
--
Andy Davis
Active Crypt Team
---SQL Server Encryption
Decryption Software
http://www.activecrypt.com
"Gary D. Rezek" wrote:

> Hi All,
> We've just recently changed/upgraded server boxes and went from Windows 20
00 Server to Windows 2003 Server with
> SQLServer 2000 sp4 installed on both. The Startup Service Account settings
for both SQLServer and SQLServer
> Agent is 'System Account'. On the original machine backups worked without
a flaw, but with the new machine I
> receive the following error:
> <<error from SQL Agent Error log>>
> [298] SQLServer Error: 8198, Could not obtain information about Window
s NT group/user 'DOMAINNAME\username'.
> [SQLSTATE 42000] (ConnIsLoginSysAdmin)
> When remoted into the new machine with 'DOMAINNAME\username' and doing an
"exec xp_logininfo
> 'DOMAINNAME\username'" in Query Analyzer I get the same error as follows:
> <<error from Query Analyzer>>
> Server: Msg 8198, Level 16, State 24, Procedure xp_logininfo, Line 58
> Could not obtain information about Windows NT group/user 'DOMAINNAME\usern
ame'.
> I've looked at kb241643 and kb834124 and realize there is a workaround, bu
t this same account gets locked by AD
> at least a couple of times a day when I try and use it to login to this an
d/or other machines I administer (this
> account is an admin account used strictly for administration purposes, I h
ave an individual account that I use
> for my desktop and laptop). It seems to have began shortly after I had to
change the password for this account.
> I believe, the error and the lockout are related (my inexperience shows as
I do not have anything concrete to
> make that assumption) so I would really like to know why this is happening
and how to correct it.
> Thank you.
> gdr
> --
> Gary D. Rezek
> university Nerworking Systems and Services
> South Dakota State University
>
>|||Hi Andy,
Yes both boxes are on the same domain and have the same user accounts in the
m. As far as I can tell the 2 boxes
are near identical with their setups. The AD guys have set a lockout policy
of 5 bad logins within 15 minutes
locks the account out for 15 minutes.
Thanks.
gdr
"Andy Davis" <activecrypt@.gmail.com> wrote in message news:873FAFB3-F604-45F4-913F-EAF6D2C0A
CA0@.microsoft.com...[vbcol=seagreen]
> Hi,
> Is both SQL box on same Domain ? are they have the same User Account in it
?
> Have you set Password Policy for Account Lockout ?if so ,after how many
> attempts it locks account ? i suspect that theirs is no such user ..
> Regards
> --
> Andy Davis
> Active Crypt Team
> ---SQL Server Encryption
> Decryption Software
> http://www.activecrypt.com
>
> "Gary D. Rezek" wrote:
>

Could not find xp_sqlagent_proxy_account

Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!
Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:

> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!
|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was either
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
[vbcol=seagreen]
> When you say "change this", can you please explan what you are referring to?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find the
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:

> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was either
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. The
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John
|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/default...b;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
[vbcol=seagreen]
> 1. Could it be deleted by some service patches from EM? But I can still find
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:

> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/default...b;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.
|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
way to get the syntax of these procedures and just create on of our own?
|||Hi
See inline:
"Min" wrote:

> So is it right for SQL Server 7, the only way to reset proxy account is thru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort for
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.

> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clicking
> the "reset proxy" account button in "Job System", it says "successfully" but
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?

> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/default...b;en-us;248391
http://support.microsoft.com/default...b;en-us;253107
John[vbcol=seagreen]
> Thanks again!
> "John Bell" wrote:
|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via droptable.com" wrote:

> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
> way to get the syntax of these procedures and just create on of our own?
>

Could not find xp_sqlagent_proxy_account

Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:
> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
> > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > account. It says successfully, but I cannot find any local account
> > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was either
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
> When you say "change this", can you please explan what you are referring to?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > Have you tried changing this from the Services applet?
> >
> > John
> >
> > "Min" wrote:
> >
> > > Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> > > xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> > > procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> > > account. It says successfully, but I cannot find any local account
> > > "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find the
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:
> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was either
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. The
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
> 1. Could it be deleted by some service patches from EM? But I can still find
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > I don't have a SQL 7 system to check, but the if you can't find the stored
> > procedure in the master database using Enterprise Manager, then it was either
> > deleted for security or does not exist in that version.
> >
> > The local users are accessed through the Server applet in control panel. The
> > services applet in control panel will allow you to select a different user
> > for the service to be run as.
> >
> > John|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:
> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
way to get the syntax of these procedures and just create on of our own?|||Hi
See inline:
"Min" wrote:
> So is it right for SQL Server 7, the only way to reset proxy account is thru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort for
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.
> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clicking
> the "reset proxy" account button in "Job System", it says "successfully" but
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?
> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
John
> Thanks again!
> "John Bell" wrote:
> > Hi
> >
> > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> >
> > If the machine is NT workstation you can manage local users using
> > musrmgr.exe but this is not available on NT Server.
> >
> > What account is the service running under in the services applet? Usually
> > the account would be a domain user with restricted privileges.|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via SQLMonster.com" wrote:
> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there a
> way to get the syntax of these procedures and just create on of our own?
>|||Thanks. I guess my question now is really:
How can I create a proxy account correctly? Thru EM, I unchecked the box,
clicked "reset ..." and message came back saying " successfully". But I am
still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
non-admin account.
Also, there is no utility on NT server to verify the account.
"John Bell" wrote:
> Hi
> See inline:
> "Min" wrote:
> > So is it right for SQL Server 7, the only way to reset proxy account is thru
> > EM, not programatically?
> Probably but I don't have a system to check this. There may be a way to
> write your own process to do this, but whether this is a justified effort for
> a version of the product that is so old, I don't know. You may want to trace
> what happens when you use EM and see what if you can do the same.
> >
> > Does it mean for NT Server, there is no way I can check to verify if the
> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
> > the "reset proxy" account button in "Job System", it says "successfully" but
> > there is an error log entry for agent says "SQLAgentCmdExec password
> > verification failed, required client privilege not held".
> Is there anything in the Event log?
> >
> > We use a domain acount for both SQL and Agent services. It is in local
> > administrator group.
> You may also want to check:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
> John
> >
> > Thanks again!
> >
> > "John Bell" wrote:
> >
> > > Hi
> > >
> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
> > >
> > > If the machine is NT workstation you can manage local users using
> > > musrmgr.exe but this is not available on NT Server.
> > >
> > > What account is the service running under in the services applet? Usually
> > > the account would be a domain user with restricted privileges.|||Yes...use Enterprise Manager and the Reset Proxy on the Job
System tab in SQL Agent Properties. Refer to the following
for more info:
INF: Reset Proxy and the SQLAgentCmdExec Account
http://support.microsoft.com/?id=264155
But your issues are likely related to the service account,
not the proxy account. In regards to the 1314 error, that's
generally related to rights of the MSSQLServer service
account, *not* the proxy account. So it's that account that
is missing the rights of either/both Act as part of
operating system and increase quotas. You could also be
missing Replace process level token based on some of what
you posted earlier. I'm pretty sure there is a Knowledge
base article on this somewhere.
Sounds like you have some issues with the MSSQLServer
service account and that you may have changed it through the
services applet instead of Enterprise Manager. If you change
the service account through Enterprise Manager, the
permissions and rights will be set correctly.
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Okay...and right after I posted, I found the other KB
article I mentioned that has more info on error 1314:
PRB: Error 1314 Raised By xp_cmdshell When Executed as
Non-SA User
http://support.microsoft.com/?id=248391
-Sue
On Wed, 24 Aug 2005 11:45:03 -0700, Min
<Min@.discussions.microsoft.com> wrote:
>Thanks. I guess my question now is really:
>How can I create a proxy account correctly? Thru EM, I unchecked the box,
>clicked "reset ..." and message came back saying " successfully". But I am
>still getting errors: 1314 from LogonUser when I run xp_cmdshell from a
>non-admin account.
>Also, there is no utility on NT server to verify the account.
>"John Bell" wrote:
>> Hi
>> See inline:
>> "Min" wrote:
>> > So is it right for SQL Server 7, the only way to reset proxy account is thru
>> > EM, not programatically?
>> Probably but I don't have a system to check this. There may be a way to
>> write your own process to do this, but whether this is a justified effort for
>> a version of the product that is so old, I don't know. You may want to trace
>> what happens when you use EM and see what if you can do the same.
>> >
>> > Does it mean for NT Server, there is no way I can check to verify if the
>> > local account SQLAgentCmeExec has been created? When I tried EM by clicking
>> > the "reset proxy" account button in "Job System", it says "successfully" but
>> > there is an error log entry for agent says "SQLAgentCmdExec password
>> > verification failed, required client privilege not held".
>> Is there anything in the Event log?
>> >
>> > We use a domain acount for both SQL and Agent services. It is in local
>> > administrator group.
>> You may also want to check:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;248391
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;253107
>> John
>> >
>> > Thanks again!
>> >
>> > "John Bell" wrote:
>> >
>> > > Hi
>> > >
>> > > xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
>> > > http://support.microsoft.com/default.aspx?scid=kb;en-us;889551
>> > >
>> > > If the machine is NT workstation you can manage local users using
>> > > musrmgr.exe but this is not available on NT Server.
>> > >
>> > > What account is the service running under in the services applet? Usually
>> > > the account would be a domain user with restricted privileges.|||Thanks ... I have tried to follow both articles (actually almost every
article online that I can dig out). It is still not working even though EM
says "successfully". I decided to use another technology instead of
XP_cmdshell. My guess is that some kind of security patches blocked it.
"Sue Hoegemeier" wrote:
> Okay...and right after I posted, I found the other KB
> article I mentioned that has more info on error 1314:
> PRB: Error 1314 Raised By xp_cmdshell When Executed as
> Non-SA User
> http://support.microsoft.com/?id=248391

Could not find xp_sqlagent_proxy_account

Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
xp_sqlagent_proxy_account, but here is what I got: Could not find stored
procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
account. It says successfully, but I cannot find any local account
"SQLAgentCmdExec" in user managers. Could you please help? Thanks!Hi
Have you tried changing this from the Services applet?
John
"Min" wrote:

> Our system is windows NT SP6, SQL Server 7 SP4. I tried to run
> xp_sqlagent_proxy_account, but here is what I got: Could not find stored
> procedure 'master.dbo.xp_sqlagent_proxy_account'. I tried to reset proxy
> account. It says successfully, but I cannot find any local account
> "SQLAgentCmdExec" in user managers. Could you please help? Thanks!|||When you say "change this", can you please explan what you are referring to?
We have a domain account for both SQL Server and Agent Services. It seems
that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
find the local account SQLAgentCmdExec. Can you tell me where I can lookup
for the account from a windows NT server? The user manager is only for the
domain. I don't know where to look for the local account for the machine.
Thanks again!
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you tried changing this from the Services applet?
> John
> "Min" wrote:
>|||Hi
I don't have a SQL 7 system to check, but the if you can't find the stored
procedure in the master database using Enterprise Manager, then it was eithe
r
deleted for security or does not exist in that version.
The local users are accessed through the Server applet in control panel. The
services applet in control panel will allow you to select a different user
for the service to be run as.
John
"Min" wrote:
[vbcol=seagreen]
> When you say "change this", can you please explan what you are referring t
o?
> We have a domain account for both SQL Server and Agent Services. It seems
> that we have 2 diferent issues. 1. cannot find the extended SP. 2. cannot
> find the local account SQLAgentCmdExec. Can you tell me where I can lookup
> for the account from a windows NT server? The user manager is only for the
> domain. I don't know where to look for the local account for the machine.
> Thanks again!
> "John Bell" wrote:
>|||1. Could it be deleted by some service patches from EM? But I can still find
xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot have
the XP listed in EM, does it mean I cannot reset proxy account?
2. From server applet, I can only see connected users (resources), not the
local users to the machine. Could you give me more details on how to find th
e
place to check if SQLAgentCmdExec has been created as a local user?
Thanks again!
"John Bell" wrote:

> Hi
> I don't have a SQL 7 system to check, but the if you can't find the stored
> procedure in the master database using Enterprise Manager, then it was eit
her
> deleted for security or does not exist in that version.
> The local users are accessed through the Server applet in control panel. T
he
> services applet in control panel will allow you to select a different user
> for the service to be run as.
> John|||Hi
xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
http://support.microsoft.com/defaul...kb;en-us;889551
If the machine is NT workstation you can manage local users using
musrmgr.exe but this is not available on NT Server.
What account is the service running under in the services applet? Usually
the account would be a domain user with restricted privileges.
John
"Min" wrote:
[vbcol=seagreen]
> 1. Could it be deleted by some service patches from EM? But I can still fi
nd
> xpstar.dll on the drive (our SQL Server is STD edition SP4). If I donot ha
ve
> the XP listed in EM, does it mean I cannot reset proxy account?
> 2. From server applet, I can only see connected users (resources), not the
> local users to the machine. Could you give me more details on how to find
the
> place to check if SQLAgentCmdExec has been created as a local user?
> Thanks again!
> "John Bell" wrote:
>|||So is it right for SQL Server 7, the only way to reset proxy account is thru
EM, not programatically?
Does it mean for NT Server, there is no way I can check to verify if the
local account SQLAgentCmeExec has been created? When I tried EM by clicking
the "reset proxy" account button in "Job System", it says "successfully" but
there is an error log entry for agent says "SQLAgentCmdExec password
verification failed, required client privilege not held".
We use a domain acount for both SQL and Agent services. It is in local
administrator group.
Thanks again!
"John Bell" wrote:

> Hi
> xp_sqlagent_proxy_account was intoduce in sp3 or SQL 2000 see
> http://support.microsoft.com/defaul...kb;en-us;889551
> If the machine is NT workstation you can manage local users using
> musrmgr.exe but this is not available on NT Server.
> What account is the service running under in the services applet? Usually
> the account would be a domain user with restricted privileges.|||I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is there
a
way to get the syntax of these procedures and just create on of our own?|||Hi
See inline:
"Min" wrote:

> So is it right for SQL Server 7, the only way to reset proxy account is th
ru
> EM, not programatically?
Probably but I don't have a system to check this. There may be a way to
write your own process to do this, but whether this is a justified effort fo
r
a version of the product that is so old, I don't know. You may want to trace
what happens when you use EM and see what if you can do the same.

> Does it mean for NT Server, there is no way I can check to verify if the
> local account SQLAgentCmeExec has been created? When I tried EM by clickin
g
> the "reset proxy" account button in "Job System", it says "successfully" b
ut
> there is an error log entry for agent says "SQLAgentCmdExec password
> verification failed, required client privilege not held".
Is there anything in the Event log?

> We use a domain acount for both SQL and Agent services. It is in local
> administrator group.
You may also want to check:
http://support.microsoft.com/defaul...kb;en-us;248391
http://support.microsoft.com/defaul...kb;en-us;253107
John[vbcol=seagreen]
> Thanks again!
> "John Bell" wrote:
>|||Hi
I think xp_Backup_Log may be a SQL Litespeed procedure!
John
"Sara C via droptable.com" wrote:

> I am having the same issue with the "dbo.xp_Backup_Log" procedure. Is ther
e a
> way to get the syntax of these procedures and just create on of our own?
>

could not find table error

Using SS2000 SP4.
When I run DBCC SHOWCONTIG (ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES I
get an error "Server: Msg 2501, Level 16, State 45, Line 1
Could not find a table or object named 'ActionsNeeded'. Check sysobjects."
All objects in the database are owned by "memsym". If I try "DBCC SHOWCONTIG
(memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
"Server: Msg 170, Level 15, State 1, Line 1
Line 1: Incorrect syntax near '.'."
I have a script that checks index fragmentation and it uses the above
command. I get the same error on all tables in the database. Any idea why and
how to fix it?
The tables do exist and I can select from them.
Thanks,
--
Dan D.> All objects in the database are owned by "memsym". If I try "DBCC
> SHOWCONTIG
> (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> "Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '.'."
Try enclosing the object name in quotes:
DBCC SHOWCONTIG ('memsym.ActionsNeeded')
WITH TABLERESULTS, ALL_INDEXES
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Dan D." <DanD@.discussions.microsoft.com> wrote in message
news:AEC3EE22-C7D7-4E81-A29D-36C5B698B241@.microsoft.com...
> Using SS2000 SP4.
> When I run DBCC SHOWCONTIG (ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES
> I
> get an error "Server: Msg 2501, Level 16, State 45, Line 1
> Could not find a table or object named 'ActionsNeeded'. Check sysobjects."
> All objects in the database are owned by "memsym". If I try "DBCC
> SHOWCONTIG
> (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> "Server: Msg 170, Level 15, State 1, Line 1
> Line 1: Incorrect syntax near '.'."
> I have a script that checks index fragmentation and it uses the above
> command. I get the same error on all tables in the database. Any idea why
> and
> how to fix it?
> The tables do exist and I can select from them.
> Thanks,
> --
> Dan D.|||I guess I wasn't thinking this morning. That was too easy.
Thanks,
--
Dan D.
"Dan Guzman" wrote:
> > All objects in the database are owned by "memsym". If I try "DBCC
> > SHOWCONTIG
> > (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> > "Server: Msg 170, Level 15, State 1, Line 1
> > Line 1: Incorrect syntax near '.'."
> Try enclosing the object name in quotes:
> DBCC SHOWCONTIG ('memsym.ActionsNeeded')
> WITH TABLERESULTS, ALL_INDEXES
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Dan D." <DanD@.discussions.microsoft.com> wrote in message
> news:AEC3EE22-C7D7-4E81-A29D-36C5B698B241@.microsoft.com...
> > Using SS2000 SP4.
> >
> > When I run DBCC SHOWCONTIG (ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES
> > I
> > get an error "Server: Msg 2501, Level 16, State 45, Line 1
> > Could not find a table or object named 'ActionsNeeded'. Check sysobjects."
> >
> > All objects in the database are owned by "memsym". If I try "DBCC
> > SHOWCONTIG
> > (memsym.ActionsNeeded) WITH TABLERESULTS, ALL_INDEXES" I get this error -
> > "Server: Msg 170, Level 15, State 1, Line 1
> > Line 1: Incorrect syntax near '.'."
> >
> > I have a script that checks index fragmentation and it uses the above
> > command. I get the same error on all tables in the database. Any idea why
> > and
> > how to fix it?
> > The tables do exist and I can select from them.
> >
> > Thanks,
> > --
> > Dan D.
>

Could not establish secure channel for SSL/TLS.

Hi there. Just installed Reportserver. SP2 on windows 2003. SQL 2000 SP4
The //localhost/reportserver give's me XXX/ReportServer - /
----
Microsoft SQL Server Reporting Services Version 8.00.1038.00
But when connecting to //localhost/reports i get the followwing error.
"
The underlying connection was closed: Could not establish secure channel for
SSL/TLS."
Never installed ssl, and have tried all the security and other ideas so far.
Can anyone help.
Thanks
JohnJohn wrote:
> Hi there. Just installed Reportserver. SP2 on windows 2003. SQL 2000 SP4
> The //localhost/reportserver give's me XXX/ReportServer - /
> ----
> Microsoft SQL Server Reporting Services Version 8.00.1038.00
> But when connecting to //localhost/reports i get the followwing error.
> "
> The underlying connection was closed: Could not establish secure channel for
> SSL/TLS."
> Never installed ssl, and have tried all the security and other ideas so far.
> Can anyone help.
> Thanks
> John
>
if you have certificate from root,then you have to start trusting it
with you server too :)
try to install it under trusted root certification authorities.|||did you find a solution for this issue?
Grego
From http://www.developmentnow.com/g/115_2005_10_0_0_626044/Could-not-establish-secure-channel-for-SSLTLS-.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

could not disable publishing and distribution

hello All,

i am trying to delete publications in SQL 2000, SP4 and getting this
error:

SQL Server Enterprise Manager could not disable publishing and distribution on '<publishername>'.

Error 3724 : cannot drop the procedure
'dbo.sp_sel_F854ED4CD7EA4399EFDB9697F4E24A10_pal' because itis being used for replication.

Thanks and Regards

Kanna

Run sp_removedbreplication in the published database.

Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'?

Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
now BULK INSERT doesn't seem to work.
Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
11:38:51
create table ##Holding_Tank (full_record varchar(500))
BULK INSERT ##Holding_Tank
FROM 'g:\narf.txt'
WITH
(
ROWTERMINATOR = '0x0a',
TABLOCK
)
Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
OLE DB error trace [Non-interface error: CoCreate of DSO for
BULKIMPORTSTREAM returned 0x8007045a].
Any suggestions?
On Mar 2, 11:17 am, bour...@.gmail.com wrote:
> Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
> now BULK INSERT doesn't seem to work.
> Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
> 11:38:51
> create table ##Holding_Tank (full_record varchar(500))
> BULK INSERT ##Holding_Tank
> FROM 'g:\narf.txt'
> WITH
> (
> ROWTERMINATOR = '0x0a',
> TABLOCK
> )
> Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for
> BULKIMPORTSTREAM returned 0x8007045a].
> Any suggestions?
The fix appears to be to re-register the impprov dll, followed by
restarting the service.

Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'?

Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
now BULK INSERT doesn't seem to work.
Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
11:38:51
create table ##Holding_Tank (full_record varchar(500))
BULK INSERT ##Holding_Tank
FROM 'g:\narf.txt'
WITH
(
ROWTERMINATOR = '0x0a',
TABLOCK
)
Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
OLE DB error trace [Non-interface error: CoCreate of DSO for
BULKIMPORTSTREAM returned 0x8007045a].
Any suggestions?On Mar 2, 11:17 am, bour...@.gmail.com wrote:
> Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
> now BULK INSERT doesn't seem to work.
> Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
> 11:38:51
> create table ##Holding_Tank (full_record varchar(500))
> BULK INSERT ##Holding_Tank
> FROM 'g:\narf.txt'
> WITH
> (
> ROWTERMINATOR = '0x0a',
> TABLOCK
> )
> Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for
> BULKIMPORTSTREAM returned 0x8007045a].
> Any suggestions?
The fix appears to be to re-register the impprov dll, followed by
restarting the service.

Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'?

Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
now BULK INSERT doesn't seem to work.
Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
11:38:51
create table ##Holding_Tank (full_record varchar(500))
BULK INSERT ##Holding_Tank
FROM 'g:\narf.txt'
WITH
(
ROWTERMINATOR = '0x0a',
TABLOCK
)
Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
OLE DB error trace [Non-interface error: CoCreate of DSO for
BULKIMPORTSTREAM returned 0x8007045a].
Any suggestions?On Mar 2, 11:17 am, bour...@.gmail.com wrote:
> Just upgraded SQL Server to SP4 (plus hotfixes) this past weekend, and
> now BULK INSERT doesn't seem to work.
> Microsoft SQL Server 2000 - 8.00.2187 (Intel X86) Mar 9 2006
> 11:38:51
> create table ##Holding_Tank (full_record varchar(500))
> BULK INSERT ##Holding_Tank
> FROM 'g:\narf.txt'
> WITH
> (
> ROWTERMINATOR = '0x0a',
> TABLOCK
> )
> Could not create an instance of OLE DB provider 'BULKIMPORTSTREAM'.
> OLE DB error trace [Non-interface error: CoCreate of DSO for
> BULKIMPORTSTREAM returned 0x8007045a].
> Any suggestions?
The fix appears to be to re-register the impprov dll, followed by
restarting the service.

Could not continue scan with NOLOCK due to data movement

I have a client that is continually getting this error message:
Could not continue scan with NOLOCK due to data movement
Intially they were not at SP4 of SQL Server 2000, so per this Microsoft
Document they patched the server
http://support.microsoft.com/default.aspx/kb/815008.
Even after patching, they are continuing to get the error.
The article also mentions a trace flag, but I don't think that flag
should apply. Our software is not trying to "READ UNCOMMITTED"
isolation levels, we are providing a WITH NO LOCK optimizing hint on
the SQL statement.
Any help would be appreciated. If you need additional information, let
me know.
Thank you!
That is usually due to the fact they are running in Read Uncommitted
isolation level or are using the NOLOCK hint. If they are reading a page /
row and another user deletes that row or splits that page they get hosed.
This is usually rare unless you do a lot of scanning which typically
indicates lack of proper tuning and indexes.
Andrew J. Kelly SQL MVP
<KizzyGaul@.gmail.com> wrote in message
news:1167432375.684460.178510@.48g2000cwx.googlegro ups.com...
>I have a client that is continually getting this error message:
> Could not continue scan with NOLOCK due to data movement
> Intially they were not at SP4 of SQL Server 2000, so per this Microsoft
> Document they patched the server
> http://support.microsoft.com/default.aspx/kb/815008.
> Even after patching, they are continuing to get the error.
> The article also mentions a trace flag, but I don't think that flag
> should apply. Our software is not trying to "READ UNCOMMITTED"
> isolation levels, we are providing a WITH NO LOCK optimizing hint on
> the SQL statement.
> Any help would be appreciated. If you need additional information, let
> me know.
> Thank you!
>
|||Read Uncommitted and WITH NOLOCK are equivalent. WITH NOLOCK sets the
isolation level for the individual query while READ UNCOMMITTED does the
same thing for either the connection or the entire database, depending on
where it is used. You are likely using a very active transactional system
to support an analysis type query. The underlying transactional changes
cause the large aggregations or intermediate result sets to fail. You can
try using a replicated or log shipped copy as your source or upgrade to SQL
2005 and try using Snapshot isolation.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<KizzyGaul@.gmail.com> wrote in message
news:1167432375.684460.178510@.48g2000cwx.googlegro ups.com...
>I have a client that is continually getting this error message:
> Could not continue scan with NOLOCK due to data movement
> Intially they were not at SP4 of SQL Server 2000, so per this Microsoft
> Document they patched the server
> http://support.microsoft.com/default.aspx/kb/815008.
> Even after patching, they are continuing to get the error.
> The article also mentions a trace flag, but I don't think that flag
> should apply. Our software is not trying to "READ UNCOMMITTED"
> isolation levels, we are providing a WITH NO LOCK optimizing hint on
> the SQL statement.
> Any help would be appreciated. If you need additional information, let
> me know.
> Thank you!
>

Could not continue scan with NOLOCK due to data movement

I have a client that is continually getting this error message:
Could not continue scan with NOLOCK due to data movement
Intially they were not at SP4 of SQL Server 2000, so per this Microsoft
Document they patched the server
http://support.microsoft.com/default.aspx/kb/815008.
Even after patching, they are continuing to get the error.
The article also mentions a trace flag, but I don't think that flag
should apply. Our software is not trying to "READ UNCOMMITTED"
isolation levels, we are providing a WITH NO LOCK optimizing hint on
the SQL statement.
Any help would be appreciated. If you need additional information, let
me know.
Thank you!That is usually due to the fact they are running in Read Uncommitted
isolation level or are using the NOLOCK hint. If they are reading a page /
row and another user deletes that row or splits that page they get hosed.
This is usually rare unless you do a lot of scanning which typically
indicates lack of proper tuning and indexes.
Andrew J. Kelly SQL MVP
<KizzyGaul@.gmail.com> wrote in message
news:1167432375.684460.178510@.48g2000cwx.googlegroups.com...
>I have a client that is continually getting this error message:
> Could not continue scan with NOLOCK due to data movement
> Intially they were not at SP4 of SQL Server 2000, so per this Microsoft
> Document they patched the server
> http://support.microsoft.com/default.aspx/kb/815008.
> Even after patching, they are continuing to get the error.
> The article also mentions a trace flag, but I don't think that flag
> should apply. Our software is not trying to "READ UNCOMMITTED"
> isolation levels, we are providing a WITH NO LOCK optimizing hint on
> the SQL statement.
> Any help would be appreciated. If you need additional information, let
> me know.
> Thank you!
>|||Read Uncommitted and WITH NOLOCK are equivalent. WITH NOLOCK sets the
isolation level for the individual query while READ UNCOMMITTED does the
same thing for either the connection or the entire database, depending on
where it is used. You are likely using a very active transactional system
to support an analysis type query. The underlying transactional changes
cause the large aggregations or intermediate result sets to fail. You can
try using a replicated or log shipped copy as your source or upgrade to SQL
2005 and try using Snapshot isolation.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<KizzyGaul@.gmail.com> wrote in message
news:1167432375.684460.178510@.48g2000cwx.googlegroups.com...
>I have a client that is continually getting this error message:
> Could not continue scan with NOLOCK due to data movement
> Intially they were not at SP4 of SQL Server 2000, so per this Microsoft
> Document they patched the server
> http://support.microsoft.com/default.aspx/kb/815008.
> Even after patching, they are continuing to get the error.
> The article also mentions a trace flag, but I don't think that flag
> should apply. Our software is not trying to "READ UNCOMMITTED"
> isolation levels, we are providing a WITH NO LOCK optimizing hint on
> the SQL statement.
> Any help would be appreciated. If you need additional information, let
> me know.
> Thank you!
>