Tag Info

New answers tagged

1

Looks like some thing in your content database required updates. couple of possibilities: you may restore the site collection in that db upgrade from last time not completed successfully. may be you moved the content/ pages from different version which required upgrade. Solution run upgrade-spcontentdatabase "DB name" and once it completed successfully ...


1

Update-SPSolution command it never works the way it should , Always use the deactivate-retract-delete-add-deploy-activate approach just as if it were a new solution. Update-SPSolution does not Deploy Solution


2

What you are seeing are references in your database after a solution/webpart that was not removed correctly. I assume that you just uninstalled and removed the solution? If you know in which site och sub site the web part and feature was activated, you could add and install the solution again to your farm and follow those steps: Go to the site or sub ...


0

Does the newer version of the solution contain the same set of files/features as the deployed solution? Can you try an update with a few cosmetic changes to confirm Update-SPSolution is working? The Update-SPSolution cmdlet upgrades a deployed SharePoint solution in the farm. Use this cmdlet only if a new solution contains the same set of files and ...


2

there are couple of ways to remove it. Using the powershell script, check this link CodePlex solution SharePoint Feature Administration and Clean Up Tool


-1

If it happens in SharePoint 2013, try an play with your browser compatibility mode.


0

This has been resolved – the issue is caused when migrating from 2010 to 2013. Microsoft’s upgrade process seems to have missed an update required to the Workflow History list, and the following powershell fixes it, with the key being the .SystemUpdate($false) on each item in the workflow history list: $url = 'http://mysite/myweb' #todo: update ...



Top 50 recent answers are included