Tag Info

New answers tagged

0

Your SQL Server is unsupported, SQL Server 2008 R2 is not supported with SharePoint 2013. You need 64-bit edition of SQL Server 2008 R2 Service Pack 1 min to configure the SharePoint. Check Software requirement from this technet. http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx#section4


0

Simply check Web management service & windows process activation services in IIS, start both if they are set manual,& try then.


0

The SP 2013 exe installer needs a file named servermanagercmd.exe, which is not present in the windows server 2012 R2 OS. So we need to rename the file servermanager.exe, to servermanagercmd.exe which is located in windows\system32 directory. This is what has solved my problem.


1

I've done some extensive research on this issue and I finally have a working solution. I've done the same as @tomvanderhoek, i.e. installed VS 2013 side by side with VS 2012. This is a bad idea if you're developing workflows. For a reason specified on another thread (Retract WSP in VS 2013 - Delete Content Types) I cannot use VS 2013. So I rolled back to VS ...


0

Try this inside the catch block: catch(Exception ex) { SPListItem item = properties.Listitem; item["MultiTextFieldName"] = ex.Message; item.Update(); }


0

Go to another view of the list and try to delete the item from there. It could be an issue with the view


-2

Try SPWeb.Lists[listName] instead of SPWeb.Lists.tryGetList(listName) and this exception will go away.


0

Those people stumbling across this solution by Leeland may be interested in the slightly updated version for SharePoint 2013 below. I have also added a second if statement to distinguish between dynamic sub menus. var hoverMenuItems = document.getElementsByTagName('li'); for (x = 0; x < hoverMenuItems.length; x ++) { if ...


0

This article helped me finding a solution for my case. While creating new sites I kept receiving these errors after each other without any detailed information: The element of type 'ContentType' for feature '<FEATURE-NAME>' (id: <FEATURE-ID>) threw an exception during activation: Feature Activation: Threw an exception, attempting to roll back. ...



Top 50 recent answers are included