SharePoint 2016 WSP Deployment Error

Question

SharePoint 2016 WSP Deployment Error

Krishna Sandeep Sangani 61

Hi Team,

When I deploy solution using update-spsolution, getting an error below. It started coming recently and it was working fine earlier. It is SP2016 environment.

Appreciated your thoughts here.

User's image

Ling Zhou_MSFT 23,620 Reputation points Microsoft External Staff

2023-07-17T01:20:01.9266667+00:00

Thank you for your question.

We are currently looking into this issue and will give you an update as soon as possible.

Thank you for your understanding and support.

Accepted answer

1 additional answer

Your answer

Ling Zhou_MSFT 23,620 Reputation points Microsoft External Staff

2023-07-17T01:20:01.9266667+00:00

Thank you for your question.

We are currently looking into this issue and will give you an update as soon as possible.

Thank you for your understanding and support.

Answer 1

Hi @Krishna,

Thank you for posting in this community.

The problem seems to have arisen because the name of the solution was duplicated.

Since we can't reproduce your situation, we need to narrow down the problem and try some things.

Rename the name of the solution.
Start SharePoint Administration->Go to Operation > Solution Management (Global Configuration). Retract the problematic solution and remove it after that. Finally, redeploying the solution.
If the problem persists, try restarting the IIS server and redeploying the solution.

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.

Answer 2

Krishna Sandeep Sangani 61

After retract and removing the solution from solution management, can I use update-solution command or I need use add-spsolution then install solution? What are all steps need to be followed if rename wsp solution? Will there be any impact on existing solution?

Ling Zhou_MSFT 23,620 Reputation points Microsoft External Staff

2023-07-17T05:19:09.0833333+00:00
Hi @Krishna

You need use add-spsolution then install solution after retract and removing the solution from solution management.

The WSP name for a solution is defined within the Package\Package.package file of the solution as the “name” property inside the element. You need to open the code/project using Visual Studio, go to the Package file and then change the "name" attribute value to the desired modified name, and rebuild it. Reference: VS2010: Changing the SharePoint wsp file name

After renaming, all sites using this solution may be affected. If there are a lot of sites using this solution, then it's better to redeploy this solution with the same name.
Krishna Sandeep Sangani 61 Reputation points

2023-07-17T05:55:22.62+00:00

Thanks for your response. With this approach I might need to reactivate the features where it will create some lists and libraries. There are production lists which has data, it might impact them as well.

That's why I always use update-spsolution. so that it will only deploy changes which are made in the code. Is there a way I can overcome this duplicate solution problem? Why this duplicate solution issue is coming which never came earlier? Is there a way to identify duplicates in the server and remove them so that update-spsolution command will work as it is.
Ling Zhou_MSFT 23,620 Reputation points Microsoft External Staff

2023-07-17T07:44:56.15+00:00

Hi @Krishna,

I do understand how frustrated you are now.

However, I feel regretful to inform you that the only solution at this point is to redeploy the solution. The problem seems to be that your updated solution and your old solution are considered two solutions, which then leads to renaming. This is an incidental occurrence with SharePoint and there is no particular solution.

The way to minimize the risk is to retract and remove the original solution and keep the original name to redeploy the solution. This probably will not affect sites that have used the solution before, since the name is the same.
Krishna Sandeep Sangani 61 Reputation points

2023-07-17T14:16:37.65+00:00

Thanks for all your inputs. I was able to deploy solution with few tweaks.

Share via

SharePoint 2016 WSP Deployment Error

1 additional answer

Your answer