12/12/2009 – Update:
The newly released Update Roll Up for OpsMgr SP1 contains the fix this issue. To be found here.
Got this one from the Microsoft TechNet OpsMgr Forums as well.
When one runs OpsMgr SP1 and wants to apply the Update Rollup (KB971541) all goes well. As stated in this Update Rollup, SQL 2008 is now supported as well. So when one wants to start the upgrade process of SQL 2005 to SQL 2008, a tool for SRS needs to be used as well: SRSUpgradeTool.exe.
But then this error might pop up:
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'SRSUpgradeTool, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
File name: 'SRSUpgradeTool, Version=6.0.4900.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)
The Zone of the assembly that failed was: MyComputer
As it turns out, the SRSUpdateTool.exe in the Update Rollup hasn’t been signed properly. This is the way to solve that issue:
- Run SN -Vr srsupgradetool.exe
- Run the SRSUpgradeTool.exe as required
- Run SN -Vu srsupgradetool.exe when done
When that doesn’t work, try this:
- Run SN -Vr *,31bf3856ad364e35
- Run the SRSUpgradetool.exe as required
- Run SN -Vu *,31bf3856ad364e35
No comments:
Post a Comment