Tag Info

New answers tagged

1

I've just had a similar issue: Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION)) at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) The symptoms were similar to above with the issue only happening in test and prod with front and back end servers. The entire page that my web part was on would not display. ...


0

There are two ways which this question could be answered: 1. Fix the problem causing the error so that the .udcx file can be created in the traditional way on our SharePoint 2013 environment, OR 2. Workaround the error and create the needed .udcx file some other way. My answer will be the latter approach, a workaround. 1. Fix the problem causing the ...


0

Make sure you're using the right templates: there are templates for SharePoint 2013 and templates for 2010. You'll get this error if you have 2013 installed but pick the 2010 visual studio project template.


0

Disable debugging, change the following XML in the web.config file: Turn off the call stack (CallStack="false") Enable custom errors in Visual Studio (<customErrors mode="On" />) Disable compilation debugging (<compilation debug="false">)


1

Seems like my problem is fixed. I added .Load() for a list item in the Rename method: try { item["Title"] = newName; item["FileLeafRef"] = newName; item.Update(); _clientContext.Load( item, i => i, i => i.FileSystemObjectType, i ...


0

Solved, was a compatability issue between vs2012 and vs2013.


-1

I was having the same problem. This might help you. http://adrianhenke.wordpress.com/2010/08/20/sharepoint-error-save-conflict-your-changes-conflict-with-those-made-concurrently-by-another-user/


0

Including the scripts after the page has loaded fixed it: var scriptbase = "/_layouts/15/"; $.getScript(scriptbase + "SP.Runtime.js", function () { $.getScript(scriptbase + "SP.js", function(){ $.getScript(scriptbase + "SP.Taxonomy.js", function() { init(); }); }); }); source


1

If the error is with the custom site template, you need to upgrade your SP2010 visual studio olution that contains site definition/templates to visual studio 2012 and deploy your solution in the target SP2013 environment. To be able to use custom site templates in SP2013, it has to be in the 15 HIVE. Also, while doing a visual upgrade from SP2010 to SP2013 ...


0

Please do the following steps :- a) Go to Central Administration b) Select your web application c) Click on Web Part Security under Security tab d) Select the option Allows contributors to add or edit scriptable Web Parts. e) Also validate the other settings. Regards, Anurag



Top 50 recent answers are included