Sanban on Mon, 21 Sep 2009 18:04:23
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?
AseemN on Mon, 21 Sep 2009 18:56:04
Deploy the solution using the -allowgacdeployment switch:
Aseem Nayar - MSFT
Sanban on Tue, 22 Sep 2009 15:30:45
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.
Lily Wu on Wed, 23 Sep 2009 03:28:49
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.
JMARWAHA2010 on Fri, 05 Nov 2010 15:57:16
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?
Kiran.Raavi on Thu, 06 Jun 2013 11:16:43
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.
gideonmulder on Tue, 02 May 2017 12:01:28
When working on a development environment, close visual studio and try again.