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 |
atheijs
Starting Member
1 Post |
Posted - 2009-02-04 : 03:52:56
|
Hi, I do not know whether this is the right forum for my question, but please let me now so I can bring it to the correct forum so my question reached the right people.Thanks for that.We have the following configuration running: MS 2003 server with MS Sql2005 SP1 including MS Reposting Service and several MS XP workstations. On these workstation runs SQL Server Business Intelligence Development Studio to design query’s, reports.Last week we installed – installation was initialized by WSUS – on the workstations MS SQL Server 2005 sp3 (KB955706) where an upgrade was included for MS Reporting Services.This update on the workstation was completed. At two workstation – after the installation – came several errors by starting MS Reporting Services. One of these errors - encountered while loading Business Intelligence Development Studio Designer is:Deserialization failed: Could not load type ‘Microsoft.VisualStudio.Shell.IoleMenuCommand’ from assembly ‘Microsoft.SisualStudio.Shell.Interop.8.0, Version=8.0.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’. Line 2, position2.Search on the Internet has no results. Similarly search at the sites of MicroSoft has also no results. Reinstalling the software (KB955706) also brought no solution. The update cannot by uninstalled – “this update cannot be removed” - and has no restorepoint. Has anyone seen this error before or has any ideas where I can look for a solution to solve this problemThanks for any solution.Kind Regards,Antoon Theijs |
|
vegarda
Starting Member
1 Post |
Posted - 2009-02-06 : 03:22:43
|
We've got the same problem here after applying SP3.Any solution appreciated..V |
|
|
tomf84
Starting Member
2 Posts |
Posted - 2009-02-17 : 06:07:07
|
Same issue. No fix found. |
|
|
panotuco
Starting Member
1 Post |
Posted - 2009-03-17 : 05:34:08
|
HiThe solution is change the DLL in c:\windows\assembly |
|
|
tomf84
Starting Member
2 Posts |
Posted - 2009-03-17 : 05:46:10
|
Please elaborate. |
|
|
rdoi
Starting Member
1 Post |
Posted - 2009-08-04 : 15:59:55
|
Has anyone found a solution to this problem yet? |
|
|
|
|
|