Deploying a sharepoint 2019 solution stuck on deploying, no failure, no success using Powersheel command

Noman Soofi 1 Reputation point
2022-05-25T08:18:52.123+00:00

I am trying to deploy a SharePoint solution using following power-shell commands, i tried both commands:

Install-SPSolution -Identity solutionname.wsp -AllwebApplications -GACDeployment -Force
stsadm -o deploysolution -name solutionname.wsp -url <myurl> -immediate -force -allowgacdeployment

before to run these commands, I restarted the admin and timer services on both servers because there are 2 servers on farm.

it creates a job and shows the status Deploying, When I can see the in Job definition and when I try to run this by click on Run Now button, it does not run.

Please help, I already wasted too much time to deploy the solution.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,470 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,356 questions
SharePoint Server Development
SharePoint Server Development
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Development: The process of researching, productizing, and refining new or existing technologies.
1,575 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Tong Zhang_MSFT 9,116 Reputation points
    2022-05-26T07:10:03.73+00:00

    Hi @Noman Soofi ,

    Per my research and testing, please try to follow the steps in the following article to deploy WSP SharePoint 2019 Solutions using PowerShell:

    https://spgeeks.devoworx.com/install-deploy-wsp-sharepoint-2019-powershell/#install-and-deploy-wsp-sharepoint-2019-solutions-using-powershell

    Hope it can help you .Thanks for your understanding and support.

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



  2. Noman Soofi 1 Reputation point
    2022-05-26T10:41:00.597+00:00

    thanks for your reply and research friend... let me check this solution and apply then will back to you soon as I have asked the IT team to apply some upgrade patches on server.

    Meanwhile, can you tell me how can I retrieve the history of custom fields value defined in project server using c#?

    0 comments No comments

  3. Limitless Technology 43,951 Reputation points
    2022-05-26T15:23:24.503+00:00

    Hello NomanSoofi,

    Since there is no errors, I would recommend a holistic approach, following the guidelines in the next Microsoft Article:

    https://social.technet.microsoft.com/wiki/contents/articles/21350.sharepoint-2010-troubleshooting-solution-deployment-stuck-on-deploying.aspx

    At the same time, the issue may be produced, not only by the Administrator and Timer services but also the "World Wide Web publishing service". All in all, after the restart of services, always check the they are running correctly and they haven't stop again for any reason. Also search for the OWSTIMER.EXE.CONFIG file on your server, and verify that the syntaxis through the file is correct.

    Last but not least, in last case scenario, you can try the next:
    1.Restart server
    2.Remove wsp from SP farm
    3.Stop SPTimer
    4.Clear SP Cache
    5.5Start SPTimer
    6.Add and install wsp


    --If the reply is helpful, please Upvote and Accept as answer--


  4. sadomovalex 3,626 Reputation points
    2022-05-31T14:56:30.237+00:00

    try to restart both servers. Farm solutions (wsps) are installed via timer service and if it stuck something may be wrong with timer service. Check under which permission it is running. Also try to check ULS logs (search by wsp name) - may be you will find some details there.