I created an assembly to access my SSRS web service in a Script task. The package runs fine on my machine but gets the following error from the production box.....
The script threw an exception: Could not load file or assembly 'Microsoft.SqlServer.ReportingServices2005, Version=0.0.0.0, Culture=neutral, PublicKeyToken=3bd4760abc5efbcb' or one of its dependencies. The system cannot find the file specified.
I followed the exact same procedures for creating the .dll on the production box as I did developing on my machine...strong name, load to gac etc....but it still cannot find it.
My production SQL Server is 64 bit so perhaps there is another step I need to take? Anyone have a clue as to what I may be missing?
TIA 
Well, I found the answer to my own question on the following blog.....
http://www.developerdotstar.com/community/node/333
Apparently, the resolution was to open the package/task in BIDS on the production box and save it and then redeploy. Something about the versioning on the assembly, which is beyond a .Net newbie like me. My guess is when I created/moved the new assembly to the production box it put a new version number on it. To pick up the new number I had to open the package/task so it would load the new assembly with the new version number.
Perhaps one of the MS guys could tell me if there is there a better way I should be doing this? Perhaps through the SSIS deployment configurations...which I have admittedly not been using (have just been importing my packages to the msdb folder in SMS)?
No comments:
Post a Comment