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 ...


0

Sequences and actions are events that occur when you upgrade Microsoft SharePoint Products and Technologies. The upgrade process consists primarily of sequences and actions. A sequence may be repeated if there are multiple items of the same type. For example, a sequence may be repeated if there are multiple content databases, multiple Web Applications, or ...


1

you need to change the dll reference! goto here: C:\Windows\Microsoft.NET\assembly\GAC_MSIL look for each one and change accordingly. should look somthing like this: <%@ Page Language="C#" Inherits="Microsoft.SharePoint.Publishing,Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" meta:progid="SharePoint.WebPartPage.Document" %> ...


0

To overcome the problem, you can developed a feature receiver in C# which updates the Page Layouts and Master pages upon feature activations. The feature activation event goes through every single module which is to be provisioned via that specific feature and update the Page Layouts and Master Pages. here is the link in how to implement: ...


0

You can update the assembly references to point to version 15 for SP2013 however, it may be ideal to take a copy of your current solution and upgrade it to 2013 using Visual Studio. This process should be automatic if you use VS2012+ and will update most references to 2013 from 2010. For more info, see here


2

it makes no difference. When migrating from 2007 to 2010, the content db is migrated and so is the ui settings as it resides within the content db.... i think its just xml and xslt content. The only reason that i could see to change the UI would be for UI testing to make sure everything from 2007 to 2010 is properly migrated over (custom UI wise). You ...


1

I can confirm that the (not-so-good) behaviour you are experiencing is indeed the default one. Whoever wrote the Visual Studio template though that using the web part class name inside the namespace was a good idea - probably this was done to avoid name collisions. That said, unless you find or write an alternate template afaik you are pretty stuck with ...



Top 50 recent answers are included