Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Moving Db To Another Server (Errors)

Author  Topic 

mcfly1204
Starting Member

10 Posts

Posted - 2008-04-21 : 09:14:37
I moved an instance of SQL Server 2005 Express to a different server and now receive the following error:

System.Data.SqlClient.SqlException: An error occurred in the Microsoft .NET Framework while trying to load assembly id 65538. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:
System.IO.FileLoadException: Could not load file or assembly 'xmpdbif, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An error relating to security occurred.

I have read about a resolution that requires you to change the db owner on select databases; I have contacted the software provider to see what users own what databases. I wanted to see if anyone had suggestions on this as well.

sodeep
Master Smack Fu Yak Hacker

7174 Posts

Posted - 2008-04-21 : 11:58:11
How did you move?
Go to Top of Page

mcfly1204
Starting Member

10 Posts

Posted - 2008-04-21 : 12:14:44
I backed up all databases to be precautious, but in actuality I detached the databases and temporarily stored them in a secured directory. I then uninstalled SQL Server 2005 Express. I then installed SQL Server 2005 Express again, restored the master database, and then attached the databases mentioned previously.
Go to Top of Page

mcfly1204
Starting Member

10 Posts

Posted - 2008-04-21 : 15:25:03
Solution:

ALTER DATABASE 'db in question*' SET TRUSTWORTHY ON
GO


*in this case it was the assembly referenced above, XMPDBIF.
Go to Top of Page

c0d3gr1
Starting Member

1 Post

Posted - 2008-06-13 : 15:52:05
quote:
Originally posted by mcfly1204

*in this case it was the assembly referenced above, XMPDBIF.



I'm working on solving this too... (dh)
Go to Top of Page
   

- Advertisement -