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.
| Author |
Topic |
|
mkeller
Starting Member
3 Posts |
Posted - 2009-05-28 : 10:07:24
|
| Hi All well I have gotten past issue with installing had a bad disk. now when i go to use the copy database wizard I recieve this message and the proceess is stop can any one shed any lighton this. thank you for your supportWindows 2003 sp2, SQL 2005 SP3error messege is Could not load type 'Microsoft.SqlServer.Management.Smo.Agent.JobBaseCollection' from assembly 'Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'. (Copy Database Wizard)Margaret Keller |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2009-05-28 : 11:58:00
|
Onhttp://www.windows-tech.info/15/6cebd49dc0766994.phpfound this:GoodGuysWin The problem for this and the other errors mentioned here are becuase you still have mismatching Client and Server versions of SQL Server SP2. The version of the SP2 .NET SMO dlls are no longer in sync with the underlying SQL Server system stored procedures. Why is this Becuase SQL Server SP2 was installed on a Windows XP environment that is missing MSDTC (Microsoft Distributed Transaction Coordinator) and the Notification Services and Client Tools portion of the upgrade fails.Cool, I'll just start MSDTC and reinstall you say Not quite. For whatever reason, many Windows XP machines no longer have MSDTC loaded in services (haven't figured out why yet). So the first step is to get MSDTC back, then reinstall SQL Server SP2. Here is the complete steps to solving this error:You will need to reinstall SQL Server SP2, but first do a few tasks:1) Make sure that MSDTC (Microsoft Distributed Transaction Coordinator) service is installed. Go to Control Panel->Administrative Tools->Services and look for Distributed Transaction Coordinator.2) If it's installed, make sure the service is running by clicking on the Start button, then skip to step 4.3) If MSDTC is not installed, you must manually reinstall it. To do this you must carefully - very carefully - follow these instructions: http://support.microsoft.com/default.aspx/kb/891801.4) Now that we know MSDTC is installed and running, reinstall SQL Server 2005 SP2. You should only have to check Client Tools and Notification Services for this 2nd install.5) Finished the install and you should be all set.http://www.windows-tech.info/15/6cebd49dc0766994.phpCopy From: www.windows-tech.info No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
mkeller
Starting Member
3 Posts |
Posted - 2009-06-10 : 12:59:48
|
| Thank you that worked. so now for the next part. I run the copy db wizard it goes thru all the steps and fails on the sqlagent.Event Type: WarningEvent Source: SQLSERVERAGENTEvent Category: Job Engine Event ID: 208Date: 6/10/2009Time: 8:49:01 AMUser: N/AComputer: xxxxxxxxxxxDescription:SQL Server Scheduled Job 'CDW_Server name_Server Name_18' (0xBC488BAA315C754887A5C262876D9F5F) - Status: Failed - Invoked on: 2009-06-10 08:48:29 - Message: The job failed. The Job was invoked by User sa. The last step to run was step 1 (CDW_Server Name_Server name_18_Step).Margaret Keller |
 |
|
|
|
|
|
|
|