Error 954: Database has invalid schema - SQL2000

I'm restoring a database on another server, the restore from disk goes
through successfully, until I try to click on tables or views I get the
message below:
Error 954: Database 'dbname' has invalid schema
Thanks in advance for any help.ITDUDE27,
Are you using SharePoint and Small Business Server? If so, here are a
couple of links:
http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
I do have one weird thought: it sounds as if the file location for the files
in the database does not match the actual file locations of the mdf and/or
ldf. Did you use the MOVE option during the RESTORE in order to position
the files properly?
Other than that, I have no really useful suggestions.
RLF
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> I'm restoring a database on another server, the restore from disk goes
> through successfully, until I try to click on tables or views I get the
> message below:
> Error 954: Database 'dbname' has invalid schema
> Thanks in advance for any help.
>|||Thanks Russ.
I'am running SP on SBS 2003. my Live sharepoint site is running fine and I
was able to install SP 2.0 on another server and it came up fine. I trying to
restore a copy of the live db as test and that is what is causing the error.
I had seen the second link you refered too, it was not help full. The point
of this exercise is to restore the sp database using Enterprize manager and
query it and then map it as my SP content database.
I've tried the move command using osql with no success. I think you are
absoluty correct about the Move, I'm just not having any luck, which ever way
I restore the SP db I get the same message.
Thanks in advance for any other feedback.
"Russell Fields" wrote:
> ITDUDE27,
> Are you using SharePoint and Small Business Server? If so, here are a
> couple of links:
> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
> I do have one weird thought: it sounds as if the file location for the files
> in the database does not match the actual file locations of the mdf and/or
> ldf. Did you use the MOVE option during the RESTORE in order to position
> the files properly?
> Other than that, I have no really useful suggestions.
> RLF
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > Thanks in advance for any help.
> >
> >
>
>|||Russell,
Can you comfirm the syntax for me.
Current location: N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche.bak from other server
New location: N:\Program Files\Microsoft SQL Server\MSSQL\Data
RESTORE DATABASE avalanche_new FROM DISK = 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche.bak'
WITH
MOVE 'northwind' TO 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche_new.mdf'
MOVE 'northwind_log' TO 'N:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\avalanche_log.ldf'
Thanks in advance.
"Russell Fields" wrote:
> ITDUDE27,
> Are you using SharePoint and Small Business Server? If so, here are a
> couple of links:
> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
> I do have one weird thought: it sounds as if the file location for the files
> in the database does not match the actual file locations of the mdf and/or
> ldf. Did you use the MOVE option during the RESTORE in order to position
> the files properly?
> Other than that, I have no really useful suggestions.
> RLF
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > Thanks in advance for any help.
> >
> >
>
>|||ITDUDE27,
Syntax looks correct, but the code does not match your spec. Compare:
N:\Program Files\Microsoft SQL Server\MSSQL\Data
N:\Program Files\Microsoft SQL Server\MSSQL\BACKUP\avalanche_new.mdf
If N:\ is a network drive that is not a supported configuration for SQL
Server databases. You will need to place the database files on locally
attached storage or on your SAN.
And, of course, I assume that the 'northwind%' logical names are correct.
I also usually specify a couple of things that should not be necessary in my
RESTORE command. Habit, you know, but I include the options:
RECOVERY, REPLACE
FWIW,
RLF
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:F7C1965F-448C-44F1-8DEF-9860E15E1A86@.microsoft.com...
> Russell,
> Can you comfirm the syntax for me.
> Current location: N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche.bak from other server
> New location: N:\Program Files\Microsoft SQL Server\MSSQL\Data
>
> RESTORE DATABASE avalanche_new FROM DISK = 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche.bak'
> WITH
> MOVE 'northwind' TO 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche_new.mdf'
> MOVE 'northwind_log' TO 'N:\Program Files\Microsoft SQL
> Server\MSSQL\BACKUP\avalanche_log.ldf'
> Thanks in advance.
>
> "Russell Fields" wrote:
>> ITDUDE27,
>> Are you using SharePoint and Small Business Server? If so, here are a
>> couple of links:
>> http://blogs.technet.com/edwalt/archive/2006/03/06/421346.aspx
>> http://msmvps.com/blogs/bradley/archive/2005/09/13/66344.aspx
>> I do have one weird thought: it sounds as if the file location for the
>> files
>> in the database does not match the actual file locations of the mdf
>> and/or
>> ldf. Did you use the MOVE option during the RESTORE in order to position
>> the files properly?
>> Other than that, I have no really useful suggestions.
>> RLF
>> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
>> news:DB40C301-EF5E-4664-819C-B251D4F8BE24@.microsoft.com...
>> > I'm restoring a database on another server, the restore from disk goes
>> > through successfully, until I try to click on tables or views I get the
>> > message below:
>> >
>> > Error 954: Database 'dbname' has invalid schema
>> >
>> > Thanks in advance for any help.
>> >
>> >
>>

Error 954: Database 'dbname' has invalid schema

I'm restoring a database on another server, the restore from disk goes
through successfully, until I try to click on tables or views I get the
message below:
Error 954: Database 'dbname' has invalid schema
any thoughts?Hi
Can you provide us with more info? What is the version are you using? Do you
try restore from SS2000 to SS2005?
"ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
news:35AE8C40-3659-44DB-BABB-8B65D1223181@.microsoft.com...
> I'm restoring a database on another server, the restore from disk goes
> through successfully, until I try to click on tables or views I get the
> message below:
> Error 954: Database 'dbname' has invalid schema
> any thoughts?|||Thanks for the response uri.
I'm doing the restore on SS2000 to SS2000. I'm trying to test the install of
WSS3.0 on a test environment but the restore is displaying that error.
Thanks in advance.
"Uri Dimant" wrote:
> Hi
> Can you provide us with more info? What is the version are you using? Do you
> try restore from SS2000 to SS2005?
> "ITDUDE27" <ITDUDE27@.discussions.microsoft.com> wrote in message
> news:35AE8C40-3659-44DB-BABB-8B65D1223181@.microsoft.com...
> >
> > I'm restoring a database on another server, the restore from disk goes
> > through successfully, until I try to click on tables or views I get the
> > message below:
> >
> > Error 954: Database 'dbname' has invalid schema
> >
> > any thoughts?
>
>

Error 21776 when accessing sa account

I get the 21776 error when I try to view the sa account under
security/logins. I can click past it and still view and change account
details, but how do I get rid of the error. I have read about
out-of-sync users problem and have tried the suggested script:
USE MyDatabase
EXEC sp_addlogin 'TempOwner'
EXEC sp_changedbowner 'TempOwner'
EXEC sp_changedbowner 'sa'
EXEC sp_droplogin 'TempOwner'
GO
However I don't know what to use for MyDatabase. Since I'm changing sa
account details I thought that I should point to master. You can't
change the owner of master. I'm a noob. What am I missing. I'm using
msde2000.
Tom
Error 21776: [SQL-DMO]The name 'dbo' was not found in the Users
Collection. If the name is a qualified name, use [] to seperate various
parts of the name, and try again.The error means that the owner of one or more of your user databases is
out-of-sync, probably due to a restore or attach.
You need to run sp_changedbowner in the context of your user database.
sp_changedbowner was corrected in SP3 so you don't need to temporarily
change ownership to a non-conflicting login.
The script below will change ownership for all user databases to 'sa':
DECLARE @.ChangeDBOwner nvarchar(4000)
DECLARE ChangeDBOwner CURSOR
LOCAL FAST_FORWARD READ_ONLY FOR
SELECT N'USE ' + CATALOG_NAME + N'
EXEC sp_changedbowner ''sa'''
FROM INFORMATION_SCHEMA.SCHEMATA
WHERE CATALOG_NAME NOT IN
(
'master',
'model',
'msdb',
'tempdb',
'distribution'
)
OPEN ChangeDBOwner
WHILE 1 = 1
BEGIN
FETCH NEXT FROM ChangeDBOwner INTO @.ChangeDBOwner
IF @.@.FETCH_STATUS = -1 BREAK
EXEC(@.ChangeDBOwner)
END
CLOSE ChangeDBOwner
DEALLOCATE ChangeDBOwner
GO
--
Hope this helps.
Dan Guzman
SQL Server MVP
--
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
--
"Tom Wells" <noemail@.nowhere.none> wrote in message
news:%23kHB4HWeDHA.3160@.tk2msftngp13.phx.gbl...
> I get the 21776 error when I try to view the sa account under
> security/logins. I can click past it and still view and change account
> details, but how do I get rid of the error. I have read about
> out-of-sync users problem and have tried the suggested script:
> USE MyDatabase
> EXEC sp_addlogin 'TempOwner'
> EXEC sp_changedbowner 'TempOwner'
> EXEC sp_changedbowner 'sa'
> EXEC sp_droplogin 'TempOwner'
> GO
> However I don't know what to use for MyDatabase. Since I'm changing sa
> account details I thought that I should point to master. You can't
> change the owner of master. I'm a noob. What am I missing. I'm using
> msde2000.
> Tom
> Error 21776: [SQL-DMO]The name 'dbo' was not found in the Users
> Collection. If the name is a qualified name, use [] to seperate
various
> parts of the name, and try again.
>|||I wish I understood better what I was doing but it worked. I used the
Query Analyzer and ran the script against each of my user databases.
After running the script the sa user showed up as the dbo of the database.
Thanks
Tom
Dan Guzman wrote:
> The error means that the owner of one or more of your user databases is
> out-of-sync, probably due to a restore or attach.
> You need to run sp_changedbowner in the context of your user database.
> sp_changedbowner was corrected in SP3 so you don't need to temporarily
> change ownership to a non-conflicting login.
> The script below will change ownership for all user databases to 'sa':
> DECLARE @.ChangeDBOwner nvarchar(4000)
> DECLARE ChangeDBOwner CURSOR
> LOCAL FAST_FORWARD READ_ONLY FOR
> SELECT N'USE ' + CATALOG_NAME + N'
> EXEC sp_changedbowner ''sa'''
> FROM INFORMATION_SCHEMA.SCHEMATA
> WHERE CATALOG_NAME NOT IN
> (
> 'master',
> 'model',
> 'msdb',
> 'tempdb',
> 'distribution'
> )
> OPEN ChangeDBOwner
> WHILE 1 = 1
> BEGIN
> FETCH NEXT FROM ChangeDBOwner INTO @.ChangeDBOwner
> IF @.@.FETCH_STATUS = -1 BREAK
> EXEC(@.ChangeDBOwner)
> END
> CLOSE ChangeDBOwner
> DEALLOCATE ChangeDBOwner
> GO
>|||The database owner SID is stored in 2 separate places - sysdatabases
(master database) and the 'dbo' row in the sysusers (user database).
The GUI tools misbehave when these get out of sync due to a restore or
attach. The sp_changedbowner script corrected the mismatch.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tom Wells" <noemail@.nowhere.none> wrote in message
news:euuMXy5eDHA.1056@.TK2MSFTNGP10.phx.gbl...
> I wish I understood better what I was doing but it worked. I used the
> Query Analyzer and ran the script against each of my user databases.
> After running the script the sa user showed up as the dbo of the
database.
> Thanks
> Tom
> Dan Guzman wrote:
> > The error means that the owner of one or more of your user databases
is
> > out-of-sync, probably due to a restore or attach.
> >
> > You need to run sp_changedbowner in the context of your user
database.
> > sp_changedbowner was corrected in SP3 so you don't need to
temporarily
> > change ownership to a non-conflicting login.
> >
> > The script below will change ownership for all user databases to
'sa':
> >
> > DECLARE @.ChangeDBOwner nvarchar(4000)
> > DECLARE ChangeDBOwner CURSOR
> > LOCAL FAST_FORWARD READ_ONLY FOR
> > SELECT N'USE ' + CATALOG_NAME + N'
> > EXEC sp_changedbowner ''sa'''
> > FROM INFORMATION_SCHEMA.SCHEMATA
> > WHERE CATALOG_NAME NOT IN
> > (
> > 'master',
> > 'model',
> > 'msdb',
> > 'tempdb',
> > 'distribution'
> > )
> > OPEN ChangeDBOwner
> > WHILE 1 = 1
> > BEGIN
> > FETCH NEXT FROM ChangeDBOwner INTO @.ChangeDBOwner
> > IF @.@.FETCH_STATUS = -1 BREAK
> > EXEC(@.ChangeDBOwner)
> > END
> > CLOSE ChangeDBOwner
> > DEALLOCATE ChangeDBOwner
> > GO
> >
>

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!
>>.
>>.
>>.
>>.
>>.
>.
>