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 705 while restoring transaction logs

While in the process of restoring a large number of
transaction logs, I recieved the following error
"There not enough room for process 11 to store PROC_HDR
0x5975000 in Pss.
What doesn't it have room for? The system databases have
plenty of room.
The error occurred on the 14th of about 30 transaction
logs being loaded. I am using SQL 6.5, I am unsure of the
service pack level, it migt be 5a (the build number is
6.50.479).
Any help would be greatly appreciatedDaniel,
PSS here stands for "process status structure" and refers to something SQL
Server keeps in memory. In effect, the message is saying SQL Server ran out
of memory in some buffer area. Were you able to finish the restores?
Ron
--
Ron Talmage
SQL Server MVP
"Daniel Inman" <dwinman.ns@.iqe.com> wrote in message
news:00f401c356cb$73274890$a601280a@.phx.gbl...
> While in the process of restoring a large number of
> transaction logs, I recieved the following error
> "There not enough room for process 11 to store PROC_HDR
> 0x5975000 in Pss.
> What doesn't it have room for? The system databases have
> plenty of room.
> The error occurred on the 14th of about 30 transaction
> logs being loaded. I am using SQL 6.5, I am unsure of the
> service pack level, it migt be 5a (the build number is
> 6.50.479).
> Any help would be greatly appreciated
>|||Thank you for your response, but unfortunately, we
couldn't continue restoring logs. The database was
marked suspect as a result of the error, and in 6.5 it
seems that you can't restore a corrupt database without
dropping it first. My client was getting nervous over
the downtime so we gave upon restoring the transaction
logs and went back to the last full backup. I don't know
what would have happened if I had tried the entire
restore process again - just restoring the full backup
took over five hours - the DB is over 5gb.
I am just concerned that I may encounter the same error
the next time I have to restore transaction logs for this
client. For future reference, do you think this was
related to some attribute of the transaction log it faile
on, such as size or contents? Does it matter that I ran
the load database in the same batch as the load
transaction?
Daniel Inman
>--Original Message--
>Daniel,
>PSS here stands for "process status structure" and
refers to something SQL
>Server keeps in memory. In effect, the message is saying
SQL Server ran out
>of memory in some buffer area. Were you able to finish
the restores?
>Ron
>--
>Ron Talmage
>SQL Server MVP
>
>"Daniel Inman" <dwinman.ns@.iqe.com> wrote in message
>news:00f401c356cb$73274890$a601280a@.phx.gbl...
>> While in the process of restoring a large number of
>> transaction logs, I recieved the following error
>> "There not enough room for process 11 to store PROC_HDR
>> 0x5975000 in Pss.
>> What doesn't it have room for? The system databases
have
>> plenty of room.
>> The error occurred on the 14th of about 30 transaction
>> logs being loaded. I am using SQL 6.5, I am unsure of
the
>> service pack level, it migt be 5a (the build number is
>> 6.50.479).
>> Any help would be greatly appreciated
>
>.
>

Error 3624 after getting to 100% complete, restoring sql2k db to sql2k5?

Hi All,
Was getting 3624 at 0% until I installed sql2k5 sp2. Now a restore of a
sql2k db gets almost all the way thru, shows 100%, and then I get this 3624
error below.
Any ideas and/or suggestions?
The disk is not full.
Is there any way I can say "don't restore the log file" to isolate a bit?
I tried to run DBCC CHECKDB, but it won't allow it as the db is "in the
process of a restore".
I am not a sql dba, just trying to investigate moving from sql2k -> 2k5.
Thanks in advance!
Derrick
===================================
Restore failed for Server 'localhost\sql2005'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
Program Location:
at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
at
Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRes
tore()
===================================
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
Program Location:
at
Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(Strin
g
sqlCommand, ExecutionTypes executionType)
at
Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(Strin
gCollection
sqlCommands, ExecutionTypes executionType)
at
Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCo
llection
queries)
at
Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMessa
ge(StringCollection
queries, ServerMessageEventHandler dbccMessageHandler, Boolean
errorsAsMessages)
at Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server
server, StringCollection queries)
at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
===================================
A system assertion check has failed. Check the SQL Server error log for
details. Typically, an assertion failure is caused by a software bug or data
corruption. To check for database corruption, consider running DBCC CHECKDB.
If you agreed to send dumps to Microsoft during setup, a mini dump will be
sent to Microsoft. An update might be available from Microsoft in the latest
Service Pack or in a QFE from Technical Support. (.Net SqlClient Data
Provider)
For help, click:
http://go.microsoft.com/fwlink?Prod...24&LinkId=20476
Server Name: localhost\sql2005
Error Number: 3624
Severity: 20
State: 1
Line Number: 1
Program Location:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser. ThrowExceptionAndWarning(TdsParserStateO
bjec
t
stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String
methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult
result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(Strin
g
sqlCommand, ExecutionTypes executionType)And here is a little more detail from the event log.
SQL Server Assertion: File: <container.cpp>, line=3380 Failed Assertion =
'pFcb && pFcb->IsOpen ()'. This error may be timing-related. If the error
persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.
"Derrick" <derrick@.noreply.com> wrote in message
news:OTJYC$RgHHA.3388@.TK2MSFTNGP02.phx.gbl...
> Hi All,
> Was getting 3624 at 0% until I installed sql2k5 sp2. Now a restore of a
> sql2k db gets almost all the way thru, shows 100%, and then I get this
> 3624 error below.
> Any ideas and/or suggestions?
> The disk is not full.
> Is there any way I can say "don't restore the log file" to isolate a bit?
> I tried to run DBCC CHECKDB, but it won't allow it as the db is "in the
> process of a restore".
> I am not a sql dba, just trying to investigate moving from sql2k -> 2k5.
> Thanks in advance!
> Derrick
>
>
> ===================================
> Restore failed for Server 'localhost\sql2005'. (Microsoft.SqlServer.Smo)
> --
> For help, click:
> http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
> --
> Program Location:
> at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
> at
> Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunR
estore()
> ===================================
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Program Location:
> at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(Str
ing
> sqlCommand, ExecutionTypes executionType)
> at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(Str
ingCollection
> sqlCommands, ExecutionTypes executionType)
> at
> Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(String
Collection
> queries)
> at
> Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMes
sage(StringCollection
> queries, ServerMessageEventHandler dbccMessageHandler, Boolean
> errorsAsMessages)
> at
> Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server
> server, StringCollection queries)
> at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
> ===================================
> A system assertion check has failed. Check the SQL Server error log for
> details. Typically, an assertion failure is caused by a software bug or
> data corruption. To check for database corruption, consider running DBCC
> CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini
> dump will be sent to Microsoft. An update might be available from
> Microsoft in the latest Service Pack or in a QFE from Technical Support.
> (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?Prod...24&LinkId=20476
> --
> Server Name: localhost\sql2005
> Error Number: 3624
> Severity: 20
> State: 1
> Line Number: 1
>
> --
> Program Location:
> at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
> Boolean breakConnection)
> at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
> exception, Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser. ThrowExceptionAndWarning(TdsParserStateO
bj
ect
> stateObj)
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> bulkCopyHandler, TdsParserStateObject stateObj)
> at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String
> methodName, Boolean async)
> at
> System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult
> result, String methodName, Boolean sendToPipe)
> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(Str
ing
> sqlCommand, ExecutionTypes executionType)
>
>

Error 3624 after getting to 100% complete, restoring sql2k db to sql2k5?

Hi All,
Was getting 3624 at 0% until I installed sql2k5 sp2. Now a restore of a
sql2k db gets almost all the way thru, shows 100%, and then I get this 3624
error below.
Any ideas and/or suggestions?
The disk is not full.
Is there any way I can say "don't restore the log file" to isolate a bit?
I tried to run DBCC CHECKDB, but it won't allow it as the db is "in the
process of a restore".
I am not a sql dba, just trying to investigate moving from sql2k -> 2k5.
Thanks in advance!
Derrick
===================================
Restore failed for Server 'localhost\sql2005'. (Microsoft.SqlServer.Smo)
--
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
--
Program Location:
at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
at
Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRestore()
===================================
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
Program Location:
at
Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
sqlCommand, ExecutionTypes executionType)
at
Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection
sqlCommands, ExecutionTypes executionType)
at
Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection
queries)
at
Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMessage(StringCollection
queries, ServerMessageEventHandler dbccMessageHandler, Boolean
errorsAsMessages)
at Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server
server, StringCollection queries)
at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
===================================
A system assertion check has failed. Check the SQL Server error log for
details. Typically, an assertion failure is caused by a software bug or data
corruption. To check for database corruption, consider running DBCC CHECKDB.
If you agreed to send dumps to Microsoft during setup, a mini dump will be
sent to Microsoft. An update might be available from Microsoft in the latest
Service Pack or in a QFE from Technical Support. (.Net SqlClient Data
Provider)
--
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=3624&LinkId=20476
--
Server Name: localhost\sql2005
Error Number: 3624
Severity: 20
State: 1
Line Number: 1
--
Program Location:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
exception, Boolean breakConnection)
at
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String
methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult
result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
sqlCommand, ExecutionTypes executionType)And here is a little more detail from the event log.
SQL Server Assertion: File: <container.cpp>, line=3380 Failed Assertion ='pFcb && pFcb->IsOpen ()'. This error may be timing-related. If the error
persists after rerunning the statement, use DBCC CHECKDB to check the
database for structural integrity, or restart the server to ensure in-memory
data structures are not corrupted.
"Derrick" <derrick@.noreply.com> wrote in message
news:OTJYC$RgHHA.3388@.TK2MSFTNGP02.phx.gbl...
> Hi All,
> Was getting 3624 at 0% until I installed sql2k5 sp2. Now a restore of a
> sql2k db gets almost all the way thru, shows 100%, and then I get this
> 3624 error below.
> Any ideas and/or suggestions?
> The disk is not full.
> Is there any way I can say "don't restore the log file" to isolate a bit?
> I tried to run DBCC CHECKDB, but it won't allow it as the db is "in the
> process of a restore".
> I am not a sql dba, just trying to investigate moving from sql2k -> 2k5.
> Thanks in advance!
> Derrick
>
>
> ===================================> Restore failed for Server 'localhost\sql2005'. (Microsoft.SqlServer.Smo)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
> --
> Program Location:
> at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
> at
> Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRestore()
> ===================================> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Program Location:
> at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
> sqlCommand, ExecutionTypes executionType)
> at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(StringCollection
> sqlCommands, ExecutionTypes executionType)
> at
> Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(StringCollection
> queries)
> at
> Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMessage(StringCollection
> queries, ServerMessageEventHandler dbccMessageHandler, Boolean
> errorsAsMessages)
> at
> Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server
> server, StringCollection queries)
> at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
> ===================================> A system assertion check has failed. Check the SQL Server error log for
> details. Typically, an assertion failure is caused by a software bug or
> data corruption. To check for database corruption, consider running DBCC
> CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini
> dump will be sent to Microsoft. An update might be available from
> Microsoft in the latest Service Pack or in a QFE from Technical Support.
> (.Net SqlClient Data Provider)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=3624&LinkId=20476
> --
> Server Name: localhost\sql2005
> Error Number: 3624
> Severity: 20
> State: 1
> Line Number: 1
>
> --
> Program Location:
> at System.Data.SqlClient.SqlConnection.OnError(SqlException exception,
> Boolean breakConnection)
> at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException
> exception, Boolean breakConnection)
> at
> System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
> stateObj)
> at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior,
> SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet
> bulkCopyHandler, TdsParserStateObject stateObj)
> at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String
> methodName, Boolean async)
> at
> System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult
> result, String methodName, Boolean sendToPipe)
> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> at
> Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String
> sqlCommand, ExecutionTypes executionType)
>
>

Error 21776 when mapping orphaned users..

When restoring a database to another server (both servers running SQL Server
7) I use the sp_change_users_login procedure ("Update_one" argument) to map
one particular orphaned user to a user on the new server. This orphaned user
happens to be the dbo of the database on the original server.
The procedure exucutes correctly, but when I look in Enterprise Manager
(login properties) I get the Error 21776 message "The name "xxx" was not
found in the users collection..." etc.
Is this only a refresh problem whitin Enterprise Manager? If not, can I just
ignore it anyway, or do I have to take further actions to have it working
the way I want it to (that is, to let the user on the new server access the
restored database)
Thanks for your help!
Per WilliamsonTry to exit EM and start it again, to see if it is a refresh issue.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Per Williamson" <per.williamson@.telia.com> wrote in message
news:G5dEb.42639$dP1.166871@.newsc.telia.net...
> When restoring a database to another server (both servers running SQL Server
> 7) I use the sp_change_users_login procedure ("Update_one" argument) to map
> one particular orphaned user to a user on the new server. This orphaned user
> happens to be the dbo of the database on the original server.
> The procedure exucutes correctly, but when I look in Enterprise Manager
> (login properties) I get the Error 21776 message "The name "xxx" was not
> found in the users collection..." etc.
> Is this only a refresh problem whitin Enterprise Manager? If not, can I just
> ignore it anyway, or do I have to take further actions to have it working
> the way I want it to (that is, to let the user on the new server access the
> restored database)
> Thanks for your help!
> Per Williamson
>

Error 208: Invalid object name 'syspublications'

Hi!
Before reinstalling sql server and restoring old system databases I
forgot to delete and replication that was no longer needed. Now,
Expired Subscriptions Clean Up job fails with the following error:
Error 208: Invalid object name 'syspublications'. I don't need this
replication and would like to delete that completed but everytime I
try I get the same error message.
Please advise how can I delete all manually.
Thank you,
T.
Hi
Have you checked out http://tinyurl.com/33ls84
John
"tolcis" wrote:

> Hi!
> Before reinstalling sql server and restoring old system databases I
> forgot to delete and replication that was no longer needed. Now,
> Expired Subscriptions Clean Up job fails with the following error:
> Error 208: Invalid object name 'syspublications'. I don't need this
> replication and would like to delete that completed but everytime I
> try I get the same error message.
> Please advise how can I delete all manually.
> Thank you,
> T.
>

Error 208: Invalid object name 'syspublications'

Hi!
Before reinstalling sql server and restoring old system databases I
forgot to delete and replication that was no longer needed. Now,
Expired Subscriptions Clean Up job fails with the following error:
Error 208: Invalid object name 'syspublications'. I don't need this
replication and would like to delete that completed but everytime I
try I get the same error message.
Please advise how can I delete all manually.
Thank you,
T.Hi
Have you checked out http://tinyurl.com/33ls84
John
"tolcis" wrote:
> Hi!
> Before reinstalling sql server and restoring old system databases I
> forgot to delete and replication that was no longer needed. Now,
> Expired Subscriptions Clean Up job fails with the following error:
> Error 208: Invalid object name 'syspublications'. I don't need this
> replication and would like to delete that completed but everytime I
> try I get the same error message.
> Please advise how can I delete all manually.
> Thank you,
> T.
>