locked
Powershell Install-SPSolution Failed on one server in farm RRS feed

  • Question

  • I am deploying my solution package to test environment consisting of 2 servers (app + wfe) using powershell. While it is able to deploy successfully on one server but failing on other. Don't know why? Here is the exception log:

    Name: xxx.wsp
    Type: Core Solution
    Contains Web Application Resource: Yes
    Contains Global Assembly: Yes
    Contains Code Access Security Policy: No
    Deployment Server Type: Front-end Web server
    Deployment Status: Error
    Deployed To: None
    Last Operation Result: The installation of features failed during deployment of the solution.
    Last Operation Details: SERVERXX1 : http://SERVERXX2:8080/ : The solution was successfully deployed.
    SERVERXX2 : Failed to create receiver object from assembly "SomeAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=XXX", class "SomeNamespace.Features.Lists.ListsEventReceiver" for feature "SomeNamespace_Lists" (ID: {GUID}).: System.ArgumentNullException: Value cannot be null.
    Parameter name: type
       at System.Activator.CreateInstance(Type type, Boolean nonPublic)
       at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()
    SERVERXX2 : Failed to create receiver object from assembly "SomeAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=XXX", class "SomeNamespace.Features.Lists.ListsEventReceiver" for feature "SomeNamespace_Lists" (ID: {GUID}).: System.ArgumentNullException: Value cannot be null.
    Parameter name: type
       at System.Activator.CreateInstance(Type type, Boolean nonPublic)
       at Microsoft.SharePoint.Administration.SPFeatureDefinition.get_ReceiverObject()

    Any help will be highly appriciable.

    Thanks,

    Tuesday, February 1, 2011 7:40 AM

Answers

  • The problem was because the timer service cached the previous dlls. You have to restart timer service on all servers in the farm before starting any new deployment.

    • Marked as answer by spdevshop Sunday, June 5, 2011 6:28 PM
    Sunday, June 5, 2011 6:28 PM

All replies

  • Hi,

    Did you deploy relevant assembly to GAC for both server?

    If not, you can try it again after you deploy the relevant assembly to GAC.


    Microsoft Online Community Support
    • Marked as answer by Wayne Fan Monday, February 7, 2011 7:29 AM
    • Unmarked as answer by spdevshop Sunday, June 5, 2011 6:28 PM
    Wednesday, February 2, 2011 3:17 AM
  • The problem was because the timer service cached the previous dlls. You have to restart timer service on all servers in the farm before starting any new deployment.

    • Marked as answer by spdevshop Sunday, June 5, 2011 6:28 PM
    Sunday, June 5, 2011 6:28 PM
  • Yes, same ptoblem... After restarting Sharepoint Timer feature is succesfull activated

    Thanks

    Monday, June 27, 2011 11:19 AM