0

I am upgrading feature and updating solution only for the wsp solution package I have.

The deployment of 2013 solution is properly getting deployed using Visual Studio but not getting deployed using Management Shell.

The following is continuing as shown in below screenshot and doesn't get completed at all.

enter image description here

Can I please know where the issue is? As there is no issue with the solution. Is there any password change issues as I have updated password for Central admin in IIS and also password at timer service?

2 Answers 2

0

My guess would be the timer service, try restarting the service and clear the config cache.

How did you update the password? If you did not change it through SharePoint you probably need to update the password on your other SP servers.

2
  • I restarted the timer service and cleared the config cache as well. Jan 21, 2022 at 6:47
  • I tried to update the password for the timer service and central admin by selecting Advanced settings-> Logon --> identity and reset the password and Advanced settings --> Identity (Reset the pwd ) respectively Jan 21, 2022 at 6:51
0

It is not a good idea to change farm account password directly in IIS.
You should change it like any other managed account, at SharePoint Central Administration - Security - Configure Managed Accounts.
Here is step-by-step explanation: https://www.sharepointdiary.com/2017/08/change-farm-account-password-in-sharepoint-using-powershell.html


What about your main topic, first you need to look at Central Administration - System settings - Farm solutions for status of your current deploy being stuck, check for details and probably cancel it.
Then restart Timer Service and look at ULS logs for any errors related to process OWSTIMER.EXE.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.