Showing posts with label weird. Show all posts
Showing posts with label weird. Show all posts

Sunday, February 26, 2012

Error 3013

Got a weird one...
I have 20 databases on one SQL 2000 sp4, .2187 instance.
I also have a backup database and backup log script that I run, which
enumerates the datbase list and runs a backup for each one.
One specific database errors, while the ones before and after it succeed.
It used to work just fine, no changes (especially since I can pinpoint the
failure time to 5:50am, and I know nobody was fooling with the server at
that time).
The error is 3013 - "Backup terminating abnormally" (not the verbatim
error). Error happens for full backup and t-log.
I cannot backup manually through QA or Enterprise manger either. Nor can I
backup to a different location one the same or different drives...
Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
\LOG folder. Plenty of space on the backup drive, running out on the T-Log
drive...
Help?
Thanks,
Kevin Hill
3NF Consulting
http://kevinbhill.powweb.com/NewsGroups.htm
My random SQL Server encounters:
http://kevin3nf.blogspot.com/
Forgot to mention that DBCC CheckAlloc and DBCC CheckDB come up clean
"Kevin3NF" <Kevin@.DontSpamMe3NF-inc.com> wrote in message
news:%23Qybs8kFHHA.1080@.TK2MSFTNGP05.phx.gbl...
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
> I backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
> the \LOG folder. Plenty of space on the backup drive, running out on the
> T-Log drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
|||Kevin3NF wrote:
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can I
> backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
> \LOG folder. Plenty of space on the backup drive, running out on the T-Log
> drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
Anything in the error log?
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||Just backup failed
Customer has since changed the db to Simple, and now we cannot change it
back to FULL (3013 and 5069)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45742818.40402@.realsqlguy.com...
> Kevin3NF wrote:
> Anything in the error log?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Kevin3NF wrote:
> Just backup failed
> Customer has since changed the db to Simple, and now we cannot change it
> back to FULL (3013 and 5069)
>
- Are you able to run queries against this database?
- Are you able to modify data within this database?
- Is something (tape backup, anti-virus software) preventing SQL from
writing to the MDF or LDF file?
- Does the SQL Server service account have proper rights to the MDF and
LDF files?
This sounds to me like something is restricting writes to the
transaction log file...
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||See below...everything appears to be working normally except the backups
This database is a replication publisher and that process is working just
fine..
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
Yes
> - Are you able to modify data within this database?
Yes
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
Not that I am aware of...failures have been happening since 11/30
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
Yes
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
|||Everything else has failed, so we aer using DTS to send everything to a new
database...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
> - Are you able to modify data within this database?
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Error 3013

Got a weird one...
I have 20 databases on one SQL 2000 sp4, .2187 instance.
I also have a backup database and backup log script that I run, which
enumerates the datbase list and runs a backup for each one.
One specific database errors, while the ones before and after it succeed.
It used to work just fine, no changes (especially since I can pinpoint the
failure time to 5:50am, and I know nobody was fooling with the server at
that time).
The error is 3013 - "Backup terminating abnormally" (not the verbatim
error). Error happens for full backup and t-log.
I cannot backup manually through QA or Enterprise manger either. Nor can I
backup to a different location one the same or different drives...
Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
\LOG folder. Plenty of space on the backup drive, running out on the T-Log
drive...
Help?
Thanks,
Kevin Hill
3NF Consulting
http://kevinbhill.powweb.com/NewsGroups.htm
My random SQL Server encounters:
http://kevin3nf.blogspot.com/Forgot to mention that DBCC CheckAlloc and DBCC CheckDB come up clean
"Kevin3NF" <Kevin@.DontSpamMe3NF-inc.com> wrote in message
news:%23Qybs8kFHHA.1080@.TK2MSFTNGP05.phx.gbl...
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
> I backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
> the \LOG folder. Plenty of space on the backup drive, running out on the
> T-Log drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>|||Kevin3NF wrote:
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
I
> backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in t
he
> \LOG folder. Plenty of space on the backup drive, running out on the T-Lo
g
> drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
Anything in the error log?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Just backup failed
Customer has since changed the db to Simple, and now we cannot change it
back to FULL (3013 and 5069)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45742818.40402@.realsqlguy.com...
> Kevin3NF wrote:
> Anything in the error log?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Kevin3NF wrote:
> Just backup failed
> Customer has since changed the db to Simple, and now we cannot change it
> back to FULL (3013 and 5069)
>
- Are you able to run queries against this database?
- Are you able to modify data within this database?
- Is something (tape backup, anti-virus software) preventing SQL from
writing to the MDF or LDF file?
- Does the SQL Server service account have proper rights to the MDF and
LDF files?
This sounds to me like something is restricting writes to the
transaction log file...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||See below...everything appears to be working normally except the backups
This database is a replication publisher and that process is working just
fine..
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
Yes
> - Are you able to modify data within this database?
Yes
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
Not that I am aware of...failures have been happening since 11/30
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
Yes
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Everything else has failed, so we aer using DTS to send everything to a new
database...
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
> - Are you able to run queries against this database?
> - Are you able to modify data within this database?
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Error 3013

Got a weird one...
I have 20 databases on one SQL 2000 sp4, .2187 instance.
I also have a backup database and backup log script that I run, which
enumerates the datbase list and runs a backup for each one.
One specific database errors, while the ones before and after it succeed.
It used to work just fine, no changes (especially since I can pinpoint the
failure time to 5:50am, and I know nobody was fooling with the server at
that time).
The error is 3013 - "Backup terminating abnormally" (not the verbatim
error). Error happens for full backup and t-log.
I cannot backup manually through QA or Enterprise manger either. Nor can I
backup to a different location one the same or different drives...
Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
\LOG folder. Plenty of space on the backup drive, running out on the T-Log
drive...
Help?
Thanks,
Kevin Hill
3NF Consulting
http://kevinbhill.powweb.com/NewsGroups.htm
My random SQL Server encounters:
http://kevin3nf.blogspot.com/Forgot to mention that DBCC CheckAlloc and DBCC CheckDB come up clean
"Kevin3NF" <Kevin@.DontSpamMe3NF-inc.com> wrote in message
news:%23Qybs8kFHHA.1080@.TK2MSFTNGP05.phx.gbl...
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
> I backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
> the \LOG folder. Plenty of space on the backup drive, running out on the
> T-Log drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>|||Kevin3NF wrote:
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can I
> backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
> \LOG folder. Plenty of space on the backup drive, running out on the T-Log
> drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
Anything in the error log?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Just backup failed
Customer has since changed the db to Simple, and now we cannot change it
back to FULL (3013 and 5069)
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45742818.40402@.realsqlguy.com...
> Kevin3NF wrote:
>> Got a weird one...
>> I have 20 databases on one SQL 2000 sp4, .2187 instance.
>> I also have a backup database and backup log script that I run, which
>> enumerates the datbase list and runs a backup for each one.
>> One specific database errors, while the ones before and after it succeed.
>> It used to work just fine, no changes (especially since I can pinpoint
>> the failure time to 5:50am, and I know nobody was fooling with the server
>> at that time).
>> The error is 3013 - "Backup terminating abnormally" (not the verbatim
>> error). Error happens for full backup and t-log.
>> I cannot backup manually through QA or Enterprise manger either. Nor can
>> I backup to a different location one the same or different drives...
>> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
>> the \LOG folder. Plenty of space on the backup drive, running out on the
>> T-Log drive...
>> Help?
>> Thanks,
>> Kevin Hill
>> 3NF Consulting
>> http://kevinbhill.powweb.com/NewsGroups.htm
>> My random SQL Server encounters:
>> http://kevin3nf.blogspot.com/
>>
>>
> Anything in the error log?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Kevin3NF wrote:
> Just backup failed
> Customer has since changed the db to Simple, and now we cannot change it
> back to FULL (3013 and 5069)
>
- Are you able to run queries against this database?
- Are you able to modify data within this database?
- Is something (tape backup, anti-virus software) preventing SQL from
writing to the MDF or LDF file?
- Does the SQL Server service account have proper rights to the MDF and
LDF files?
This sounds to me like something is restricting writes to the
transaction log file...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||See below...everything appears to be working normally except the backups
This database is a replication publisher and that process is working just
fine..
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
>> Just backup failed
>> Customer has since changed the db to Simple, and now we cannot change it
>> back to FULL (3013 and 5069)
> - Are you able to run queries against this database?
Yes
> - Are you able to modify data within this database?
Yes
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
Not that I am aware of...failures have been happening since 11/30
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
Yes
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Everything else has failed, so we aer using DTS to send everything to a new
database...
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
>> Just backup failed
>> Customer has since changed the db to Simple, and now we cannot change it
>> back to FULL (3013 and 5069)
> - Are you able to run queries against this database?
> - Are you able to modify data within this database?
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

Wednesday, February 15, 2012

Error 208 Event ID 17052

Here is a weird one:
Using EM 2000 to connect to a 7.0 SQL Server. As soon as
I click on Management, I receive an error in my SQL Log
and Event Viewer for Error 208, Event ID 17052 stating
Invalid Object Name 'msdb.dbo.log_shipping_provider'
I do not have log shipping configured on any of my
servers. Has anyone ran into this'
Thanks!Here is some more interesting info:
This only happens when using EM 2000, if I use the 7.0 EM
it does not cause the error. Anyone connecting with EM
2000 can make the error occur. Any thoughts'
>--Original Message--
>Here is a weird one:
>Using EM 2000 to connect to a 7.0 SQL Server. As soon as
>I click on Management, I receive an error in my SQL Log
>and Event Viewer for Error 208, Event ID 17052 stating
>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>I do not have log shipping configured on any of my
>servers. Has anyone ran into this'
>Thanks!
>.
>|||Hi,
This error is generally caused if the object ownership is
not properly referenced when accessing that object. You
have to use the fully qualified name i.e
dbname.ObjectOwner.ObjectName.
It seems to me that the owner of
the 'log_shipping_provider' table in the msdb is NOT dbo.
You might want to take a look the ownership of this table.
Also, it is possible that the user connecting SQL Server 7
EM is connecting with the ID that owns that table!
Suppose the above table is owned id 'test'. You could be
trying to connected with 'sa' and the connection will
fail. But if you connect with 'test', it will work fine.
Take a look. hth
DeeJay
>--Original Message--
>Here is some more interesting info:
>This only happens when using EM 2000, if I use the 7.0 EM
>it does not cause the error. Anyone connecting with EM
>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
as
>>I click on Management, I receive an error in my SQL Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>.
>|||The log shipping tables do not exist in 7.0
So ownership wasn't the prob.
>--Original Message--
>Hi,
>This error is generally caused if the object ownership is
>not properly referenced when accessing that object. You
>have to use the fully qualified name i.e
>dbname.ObjectOwner.ObjectName.
>It seems to me that the owner of
>the 'log_shipping_provider' table in the msdb is NOT dbo.
>You might want to take a look the ownership of this table.
>Also, it is possible that the user connecting SQL Server
7
>EM is connecting with the ID that owns that table!
>Suppose the above table is owned id 'test'. You could be
>trying to connected with 'sa' and the connection will
>fail. But if you connect with 'test', it will work fine.
>Take a look. hth
>DeeJay
>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
EM
>>it does not cause the error. Anyone connecting with EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
>as
>>I click on Management, I receive an error in my SQL Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>.
>|||Silly me ... I knew that!
Are you connecting through just the client Tools (from
your workstation) or from a machine where SQL Server
2000/7 is installed?
Eventhough, log shipping is not configured, this table
could still, somehow, exist. You might want to take look
at the msdb database.
I have not found anything else for this error.
hth
DeeJay
>--Original Message--
>The log shipping tables do not exist in 7.0
>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
is
>>not properly referenced when accessing that object. You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
dbo.
>>You might want to take a look the ownership of this
table.
>>Also, it is possible that the user connecting SQL Server
>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
>EM
>>it does not cause the error. Anyone connecting with EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As soon
>>as
>>I click on Management, I receive an error in my SQL
Log
>>and Event Viewer for Error 208, Event ID 17052 stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>.
>|||I'm just connecting through the client tools. I've
checked msdb and haven't found anything that remotely
looks like the log shipping tables.
This is weird!
>--Original Message--
>Silly me ... I knew that!
>Are you connecting through just the client Tools (from
>your workstation) or from a machine where SQL Server
>2000/7 is installed?
>Eventhough, log shipping is not configured, this table
>could still, somehow, exist. You might want to take look
>at the msdb database.
>I have not found anything else for this error.
>hth
>DeeJay
>
>>--Original Message--
>>The log shipping tables do not exist in 7.0
>>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
>is
>>not properly referenced when accessing that object. You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
>dbo.
>>You might want to take a look the ownership of this
>table.
>>Also, it is possible that the user connecting SQL
Server
>>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could
be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the 7.0
>>EM
>>it does not cause the error. Anyone connecting with
EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As
soon
>>as
>>I click on Management, I receive an error in my SQL
>Log
>>and Event Viewer for Error 208, Event ID 17052
stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>>.
>.
>|||Hum...this one got me.
The only documentation for error 208 is for what we have
already talked about
>--Original Message--
>I'm just connecting through the client tools. I've
>checked msdb and haven't found anything that remotely
>looks like the log shipping tables.
>This is weird!
>>--Original Message--
>>Silly me ... I knew that!
>>Are you connecting through just the client Tools (from
>>your workstation) or from a machine where SQL Server
>>2000/7 is installed?
>>Eventhough, log shipping is not configured, this table
>>could still, somehow, exist. You might want to take look
>>at the msdb database.
>>I have not found anything else for this error.
>>hth
>>DeeJay
>>
>>--Original Message--
>>The log shipping tables do not exist in 7.0
>>So ownership wasn't the prob.
>>--Original Message--
>>Hi,
>>This error is generally caused if the object ownership
>>is
>>not properly referenced when accessing that object.
You
>>have to use the fully qualified name i.e
>>dbname.ObjectOwner.ObjectName.
>>It seems to me that the owner of
>>the 'log_shipping_provider' table in the msdb is NOT
>>dbo.
>>You might want to take a look the ownership of this
>>table.
>>Also, it is possible that the user connecting SQL
>Server
>>7
>>EM is connecting with the ID that owns that table!
>>Suppose the above table is owned id 'test'. You could
>be
>>trying to connected with 'sa' and the connection will
>>fail. But if you connect with 'test', it will work
fine.
>>Take a look. hth
>>DeeJay
>>
>>--Original Message--
>>Here is some more interesting info:
>>This only happens when using EM 2000, if I use the
7.0
>>EM
>>it does not cause the error. Anyone connecting with
>EM
>>2000 can make the error occur. Any thoughts'
>>--Original Message--
>>Here is a weird one:
>>Using EM 2000 to connect to a 7.0 SQL Server. As
>soon
>>as
>>I click on Management, I receive an error in my SQL
>>Log
>>and Event Viewer for Error 208, Event ID 17052
>stating
>>Invalid Object Name 'msdb.dbo.log_shipping_provider'
>>I do not have log shipping configured on any of my
>>servers. Has anyone ran into this'
>>Thanks!
>>.
>>.
>>.
>>.
>>.
>.
>