none
Error Deploying soluion Package - Cannot add the specified assembly to the global assembly cache RRS feed

  • Question

  • Hi,

    We have a deployment package, which gets deployed in test server farm environment(2 WEFs, 1 App Server, 1 SQL Server) but the same package fails to get deployed in production environment with similar server farm. It throws the error saying that "Error: Cannot add the specified assembly to the global assembly cache" in application server. But it successfully gets deployed in 2 WFEs servers of production env. 

    The only difference between test and production env is, in production the central admin is configured in app server but in test server farm its there in one of the WFE.

    The SharePoint log shows the following error:

    09/21/2009 14:31:25.02 OWSTIMER.EXE (0x0680)                              0x06C4  Windows SharePoint Services   Timer                                         6759       Critical   The Execute method of job definition "SPSolutionDeploymentJobDefinition" (id "695a3e94-969a-430f-94db-10836c9b0d55") threw an exception. Error: Cannot add the specified assembly to the global assembly cache: GAC\SomeWebPart.dll.


    What could be the issue here?

     

    Thanks,

    San


    • Edited by Sanban Monday, September 21, 2009 6:04 PM edited Subject
    Monday, September 21, 2009 6:04 PM

Answers

  • Hi

    Please be sure that you’re running as both a local administrator on the server and an administrator within the SharePoint farm.

    Does this issue disappear after the server is rebooted?
    If so, the reason for this might be that the SharePoint application pool service account did not have appropriate permission to activate IIS REGWAM admin service. You can walk through it by explicitly adding these permissions in the DCOM management console and then restarting IIS and Windows SharePoint Timer Service.

    Best Regards!

    • Marked as answer by Lily Wu Tuesday, September 29, 2009 12:14 AM
    Wednesday, September 23, 2009 3:28 AM

All replies

  • Hello,

    Deploy the solution using the -allowgacdeployment switch:

    http://technet.microsoft.com/en-us/library/cc262459.aspx


    Thanks,


    Aseem Nayar - MSFT
    This posting is provided "AS IS" with no warranties, and confers no rights
    Monday, September 21, 2009 6:56 PM
  • Hi Aseem ..Thanks for your responding to this ..

    We are using the SharePoint Administrator screen to deploy the solution, and already get an alert about the GAC deployment in that screen. So I hope thats not an issue. Also the same package is getting deployed successfully on test server farm with similar farm environment as production.

    Tuesday, September 22, 2009 3:30 PM
  • Hi

    Please be sure that you’re running as both a local administrator on the server and an administrator within the SharePoint farm.

    Does this issue disappear after the server is rebooted?
    If so, the reason for this might be that the SharePoint application pool service account did not have appropriate permission to activate IIS REGWAM admin service. You can walk through it by explicitly adding these permissions in the DCOM management console and then restarting IIS and Windows SharePoint Timer Service.

    Best Regards!

    • Marked as answer by Lily Wu Tuesday, September 29, 2009 12:14 AM
    Wednesday, September 23, 2009 3:28 AM
  • Hi Lily,

              So, you are saying FARM ADMINISTRATOR ACCOUNT should also have local administrator access. Can you please tell me then what's the diferrence between the INSTALL ACCOUNT and FARM ADMINISTRATOR account?

    Best Regards!

    Jas

     

    Friday, November 5, 2010 3:57 PM
  • I got the same issue. Deployments are happening successfully in one server but on the other server we get this error. After some heavy troubleshooting, with the help of eventvwr logs, I figured that the account that is trying to deploy doesn't have admin rights.

    So, I verified and changed the SP administration windows service run under same account as the working server. Issue resolved. Hope this helps.

    • Proposed as answer by Kiran.Raavi Thursday, June 6, 2013 11:16 AM
    Thursday, June 6, 2013 11:16 AM
  • When working on a development environment, close visual studio and try again.
    Tuesday, May 2, 2017 12:01 PM