none
WSP not getting deployed in all servers in our SharePoint 2013 farm. RRS feed

  • Question

  • Hello All,

    We have 2servers(server1,server2) in our farm. WSP file is getting deployed only in 'Server2' and status showing as 'Not Deployed'.

    SharePoint foundation web application service, Timer service, SharePoint admin service running fine in both servers and time zone also same.

    Central admin running in 'Server1' where our solution not getting deployed.

    Below steps i performed but no luck.

    1. Enabled central admin in both servers.
    2. Restarted timer service, SP admin service.
    3. Cleared SharePoint cache and restarted machines.

    I tried to use "Install-SPSolution" with '-local' parameter in the issued server (Server1). This time solution deployed in Server1 only and status showing as Deployed.

    When i remove the '-local' parameter and do "Install-SPSOlution" it is again getting deployed to 'Server2' only.

    Can removing the Server1 from farm and re-join will fix the issue ?? If so what all we need take care.
    Could anybody please share your ideas.

    Thanks


    MD.Liakath ali

    Thursday, February 8, 2018 10:48 AM

Answers

  • Hello,

    Finally I have fixed the deployment issue in my environment by enabling the SPTimerServiceInstace object status with the below script.

    SPTimerServiceInstance is in disabled state and it is affecting all administrative operations that depend on timer jobs to be completed (like depoying..the solution or starting the User Profile Sync Service).

    $farm  = Get-SPFarm
    $disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}
    if ($disabledTimers -ne $null)
    {
        foreach ($timer in $disabledTimers)
        {
            Write-Host "Timer service instance on server " $timer.Server.Name " is not Online. Current status:" $timer.Status
            Write-Host "Attempting to set the status of the service instance to online"
            $timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online
            $timer.Update()
        }
    }
    else
    {
        Write-Host "All Timer Service Instances in the farm are online! No problems found"
    }

    The above script detects SPTimerServiceInstance objects in the farm that are not online, and attempts to update their status to Online.  After running the script.

    Thanks


    MD.Liakath ali

    • Proposed as answer by Ahmed Madany Thursday, February 22, 2018 3:17 PM
    • Marked as answer by Liakath Thursday, April 19, 2018 9:00 AM
    Thursday, February 22, 2018 11:14 AM

All replies

  • Hi Liakath,

    as you described and i understood , your both servers considered as web-front server in the farm, so installing/updating any WSP either on server1 or server 2 will be deployed automatically on the second server coz they are similar , they all have SharePoint foundation web application service enabled on both servers. 

    let me know if you have different situation .


    Best Regrads, Ahmed Madany MCTS @twitter http://twitter.com/ahmed_madany @Blog http://ahmedmadany.wordpress.com @LinkedIn http://eg.linkedin.com/pub/ahmed-madany/35/80/2b6

    Thursday, February 8, 2018 4:21 PM
  • Hello Ahmed Madany,

    Thanks for the response. Can you please share any article which says that solution will be deployed to only one WFE, even if we have another 2,3 WFEs in farm.

    To my knowledge solution should be deployed to all the WFEs where SharePoint foundation web application service is running.

    Thanks



    MD.Liakath ali

    Monday, February 12, 2018 1:19 PM
  • Hi Liakath,

    this is an exceropt of official Microsoft technet articles 

    https://msdn.microsoft.com/en-us/library/aa544500.aspx

    https://stackoverflow.com/questions/1473476/creating-web-application-in-sharepoint-with-multiple-web-front-ends

     


    Best Regrads, Ahmed Madany MCTS @twitter http://twitter.com/ahmed_madany @Blog http://ahmedmadany.wordpress.com @LinkedIn http://eg.linkedin.com/pub/ahmed-madany/35/80/2b6


    Monday, February 12, 2018 2:43 PM
  • Hello Ahmed Madany,

    Thanks for sharing the links. There is a possibility to deploy the solution on only one server using "DeployLOCAL" property. But this is for troubleshooting step and not recommended for Production. If i don't use LOCAL property, then solution should get deployed to all WFEs.

    For ex: Lets say we have 8 severs in our SharePoint farm. Out of 8, SharePoint foundation web application service is running on 5 servers(5WFEs). As you said, if the solution deployed to only one server then it will be a performance issue because of the overload.

    For some reason my solution is not getting deployed to all WFEs.

    Thanks



    MD.Liakath ali

    Tuesday, February 13, 2018 6:14 AM
  • Hi Liakath,

    As your example above, deploying/updating WSP on one of the wfe servers without -deploylocal property will replicate all changes to all other wfe servers and it will definitely do Application pool recycling on all the wfe servers .

    i hope everything is clear now in your case , if you still need any help, don't hesitate to ping me here.


    Best Regrads, Ahmed Madany MCTS @twitter http://twitter.com/ahmed_madany @Blog http://ahmedmadany.wordpress.com @LinkedIn http://eg.linkedin.com/pub/ahmed-madany/35/80/2b6


    Tuesday, February 13, 2018 7:58 PM
  • Request you to please read my post again. Due to some problem my solution not getting deployed to all WFEs. I have tried all the ways like restarting services, servers,clearing the SharePoint cache...etc

    Thanks


    MD.Liakath ali

    Wednesday, February 14, 2018 12:59 PM
  • Hi Liakath,

    let us apply some troubleshooting tips i found while googling about the issue, i don't know if you already have came across or not yet.

    1- did you try to deploy/update WSPs using stsadm (stsadm –o addsolution,stsadm –o deploysolution ) instead of Powershell/CA ?
    2- check if there are any deployment jobs stuck on deployment , if so please delete them and do restart timer job service and redeploy again.
    3- Execute stsadm -o execadmsvcjobs on your Central Administration server.then on other farm servers.

    4- In the Services (service.msc), check if Sharepoint Admin Service and Sharepoint Timer Job service is running.          i hope helping you to resolve your issue.


    Best Regrads, Ahmed Madany MCTS @twitter http://twitter.com/ahmed_madany @Blog http://ahmedmadany.wordpress.com @LinkedIn http://eg.linkedin.com/pub/ahmed-madany/35/80/2b6

    Wednesday, February 14, 2018 3:46 PM
  • Hello Admed Madany,

    Tried but still same issue. I could not see the logs related to this issue.

    Thanks


    MD.Liakath ali

    Monday, February 19, 2018 8:50 AM
  • Hi Liakath,

    You're right, where ever the SharePoint foundation web application service is running - those servers called as WFE, also still few developer write the code to deploy to application specific(i.e for 5 WFE) and global deploy, which results to install the solution in all the servers(i.e 8 server's of your case).

    Since, you said among 5 WFE, one server is in-complete installation. As a work-around install locally for one server, using -local parameter. 

    Then you can check the PS> get-spsolution -identity farm_solution | format-list

    Where you can see the solution status deployed in all the WFE.

    However, you can rejoin the server to the farm pool (I expect some passphrase might be issue), you can use this PS. Check the passphrase in that server, please hold this as last step., someone might help more ease step.

    psconfig.exe -cmd configdb -connect -server "Impacted.wfe5.com" -database 'SharePoint_Config' -passphrase "MyPassSP13" -localserverrole "Custom"

    After rejoin, the service in the server will be reset, take a snap of current and create. 

    Thanks,

    Loganathan M P

    Monday, February 19, 2018 3:16 PM
  • Hello Loganathan,

    -local parameter overwriting everything and it is getting deployed to only that dedicated server.

    Could you please find the below detailed information and share your ideas.

    1. Have two servers: Server01, Server02
    2. In the Initial deployment, Last opertion result showing as: Solution was successfully deployed on 02. But Deployment status showing as "Not Deployed".
    3. When i use -local parameter from 02 server, Deployment status showing as "Deployed" and it is getting deployed to 02 server only.
    4. When i use -local parameter from 01 server, Last operation result showing as : Solution was successfully deployed on 01 server only. Deployment status showing as"Deployed".

    This is really frustrating and am not able to find out the exact root cause or logs for this problem.

    Thank you for any information you are able to provide.


    MD.Liakath ali

    Tuesday, February 20, 2018 12:50 PM
  • Hi Liakath,

    Your need is WSP should be deploy in both the servers. Continue as you mentioned and verify the deployment using below PS.

    PS> get-spsolution -identity farm_solution | format-list

    Where you can see more details, among that

    Farm
    Name
    DeployedServers - which will shows the servers list where it deployed in the farm like Server01 and 02 (this is the proof for you,it deployed in both the servers)
    DeployedWebApplications -- any web 
    LastOperationDetails -- which will shows the servers where the last deployed, (like Server 02)

    Unluckily, the GUI will show only the last deployed servers in the CA, you can verify the bin folder where the WSP deployed in both the servers of date modified.

    Somehow one of the WFE server is being changed, try to stop the Web foundation service and start it. Then try for WSP deploy.

    If that doesn't help, try PSConfig as mentioned above.

    Thanks,

    Loganathan M P

    Wednesday, February 21, 2018 2:02 PM
  • You can try 

    Get-SPProduct -Local

    Wednesday, February 21, 2018 2:06 PM
  • Hello,

    Finally I have fixed the deployment issue in my environment by enabling the SPTimerServiceInstace object status with the below script.

    SPTimerServiceInstance is in disabled state and it is affecting all administrative operations that depend on timer jobs to be completed (like depoying..the solution or starting the User Profile Sync Service).

    $farm  = Get-SPFarm
    $disabledTimers = $farm.TimerService.Instances | where {$_.Status -ne "Online"}
    if ($disabledTimers -ne $null)
    {
        foreach ($timer in $disabledTimers)
        {
            Write-Host "Timer service instance on server " $timer.Server.Name " is not Online. Current status:" $timer.Status
            Write-Host "Attempting to set the status of the service instance to online"
            $timer.Status = [Microsoft.SharePoint.Administration.SPObjectStatus]::Online
            $timer.Update()
        }
    }
    else
    {
        Write-Host "All Timer Service Instances in the farm are online! No problems found"
    }

    The above script detects SPTimerServiceInstance objects in the farm that are not online, and attempts to update their status to Online.  After running the script.

    Thanks


    MD.Liakath ali

    • Proposed as answer by Ahmed Madany Thursday, February 22, 2018 3:17 PM
    • Marked as answer by Liakath Thursday, April 19, 2018 9:00 AM
    Thursday, February 22, 2018 11:14 AM
  • Thanks for sharing the answer on the community.

    Best Regrads, Ahmed Madany MCTS @twitter http://twitter.com/ahmed_madany @Blog http://ahmedmadany.wordpress.com @LinkedIn http://eg.linkedin.com/pub/ahmed-madany/35/80/2b6

    Thursday, February 22, 2018 12:38 PM
  • Excellent and thanks for sharing !

    Regards,

    Loganathan M P

    Friday, February 23, 2018 3:10 PM
  • Thank for this script and thanks to Loganathan for the tips about the deployment state control after use of "-Local" parameter.

    I had the same problem today and this discussion helped me a lot after several hours trying to solve this problem.

    Monday, February 26, 2018 4:34 PM
  • Hi Liakath, 

    Thanks for sharing. 

    Since your issue is solved, please remember to mark your reply as an answers. 

    Have a nice day. 

    Best Regards, 

    Lisa Chen 


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, February 28, 2018 10:06 AM
    Moderator