Comments on: Cannot add the specified assembly to the global assembly cache http://powerpivotgeek.com/2010/02/12/cannot-add-the-specified-assembly-to-the-global-assembly-cache/ An adventure in managed self-service computing Sun, 22 Jan 2012 01:58:55 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: marrisa http://powerpivotgeek.com/2010/02/12/cannot-add-the-specified-assembly-to-the-global-assembly-cache/comment-page-1/#comment-2566 marrisa Sun, 24 Oct 2010 10:10:54 +0000 http://powerpivotgeek.com/2010/02/12/cannot-add-the-specified-assembly-to-the-global-assembly-cache/#comment-2566 Good. don’t forget to check out <a>the other articles</a> if you haven’t already Good. don’t forget to check out the other articles if you haven’t already

]]> By: Andrew Maisey http://powerpivotgeek.com/2010/02/12/cannot-add-the-specified-assembly-to-the-global-assembly-cache/comment-page-1/#comment-1447 Andrew Maisey Wed, 30 Jun 2010 10:56:05 +0000 http://powerpivotgeek.com/2010/02/12/cannot-add-the-specified-assembly-to-the-global-assembly-cache/#comment-1447 Be sure to run stsadm as a SharePoint admin account. You could do this by right clicking the CMD command prompt and selecting Run As.... The process account will need access to your assembly directory, 12 hive etc. ...the error will be the result of a failed file copy (missing DLL in the GAC) as you should see in Central Administration under the Solution Management. Hence dropping the DLLs to the application BIN directory as mentioned in other blog posts get around this but is not the most ideal solution. I would also suggest the following stsadm deployment command for a good manual deploy: stsadm -o addsolution -filename c:\yyy\xxx.wsp stsadm -o deploysolution -name xxx.wsp -url http://xxx -immediate -allowgacdeployment -force then follow this up with an: stsadm -o execadmsvcjobs Then go back into Central Administration and check your solution deployment there. Make sure there are no red error messages against your solution. Then re-load your SharePoint web application instance and after a short compile time, all should be well again. Be sure to run stsadm as a SharePoint admin account. You could do this by right clicking the CMD command prompt and selecting Run As…. The process account will need access to your assembly directory, 12 hive etc.

…the error will be the result of a failed file copy (missing DLL in the GAC) as you should see in Central Administration under the Solution Management. Hence dropping the DLLs to the application BIN directory as mentioned in other blog posts get around this but is not the most ideal solution.

I would also suggest the following stsadm deployment command for a good manual deploy:

stsadm -o addsolution -filename c:\yyy\xxx.wsp
stsadm -o deploysolution -name xxx.wsp -url http://xxx -immediate -allowgacdeployment -force
then follow this up with an:

stsadm -o execadmsvcjobs
Then go back into Central Administration and check your solution deployment there. Make sure there are no red error messages against your solution. Then re-load your SharePoint web application instance and after a short compile time, all should be well again.

]]> By: Cannot add the specified assembly to the global assembly cache « PowerPivot Twins! http://powerpivotgeek.com/2010/02/12/cannot-add-the-specified-assembly-to-the-global-assembly-cache/comment-page-1/#comment-391 Cannot add the specified assembly to the global assembly cache « PowerPivot Twins! Sun, 14 Feb 2010 05:19:01 +0000 http://powerpivotgeek.com/2010/02/12/cannot-add-the-specified-assembly-to-the-global-assembly-cache/#comment-391 [...] Read more… [...] [...] Read more… [...]

]]>