Hot answers tagged

16

SPContentDatabase.ForceDeleteSite http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spcontentdatabase.forcedeletesite.aspx use this method to force a delete: SPWebApplication spWebApplication = SPWebApplication.Lookup(new Uri("http://mywebapplication")); // insert the webapplication ...


13

Every change you make in that config files have no effect on the web application. You have to go the web.config file that is generated once the web application is created. So edit the web.config file in C:\inetpub\wwwroot\wss\VirtualDirectories\your port number and modify the parameters you have indicated in that web.config file: customErrors mode must ...


13

I would say yes, it's certainly the query string parameter you are using. Check out this post for more details http://blogs.technet.com/b/stefan_gossner/archive/2009/01/30/querystring-parameters-you-should-not-use-in-your-sharepoint-application.aspx


10

Logging to the ULS is the best way IMHO, it's an extensible framework and you can create your own categories. There are good examples of this in the P&P Guidance for SharePoint (spg.codeplex.com).


10

This is a known issue[citation needed] and unfortunately restoring to a new content database is the only workaround (I refuse to call it a solution since you now have a new problem). Once restored, you can't move the site back either; the error it returns is about how the site used to exist in the content database. If you can, avoid deleting site ...


9

In short, there's another web.config file in the LAYOUTS folder in the 14 hive that you need to change, it's set out fairly well here: http://web.archive.org/web/20130909002813/http://www.khamis.net/blog/Lists/Posts/Post.aspx?ID=12


9

This forum article helped me but I have to substitute for the missing "C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server" - C:\Program Files\Windows SharePoint Services\15.0\Data\Analytics_{some guid} Hi All, Recently an issue was reported to me where some of my site admins were facing an issue in setting up a SharePoint 2013 stand ...


8

At the beginning of your FeatureActivated method, put this line of code : System.Diagnostics.Debugger.Break(); Then, try to activate the feature. This will popup an "exception" window that let you to attach the debugger of your choice. After attaching, your code will be pause at this line, and you will be able to walk into your code to find the issue. ...


8

Beside the ULS log that Jaap mentions, you will also find relevant information in the "Application" Event Log. You can find Event Viewer in Administrative Tools or simply write eventvwr.exe in Run. Theres also alot of projects on Codeplex that is helpful for managing the ULS log file. Just search for ULS on Codeplex.com Finally i can recommend using ...


7

Check the size of your export package. There is a default cab size of about 25Mb - this used to be a limit you had to increase with stsadm by setting a parameter. With the PowerShell Export-SPWeb cmdlet it generates multiple files if you hit the limit. You may need to change this limit using the CompressionSize parameter to set the cab size (up to a maximum ...


7

As EStruyf said, you can change the deployment configuration and debug the code for your Feature Event Receivers. But, you can also attach the event receivers after making sure List is created, so put this code after your list is created. public class Feature1EventReceiver : SPFeatureReceiver { public override void ...


7

Append ?contents=1 to the end of your query string to delete broken web parts from the page.


6

Are you running Server 2008? If so, you need to open the command prompt using the "Run as Administrator" option.


5

I would load up Process Monitor http://live.sysinternals.com/Procmon.exe then attempt your re-install again. You should be able to see what files/registry keys it is looking at, and remove or edit the offending entries from there. If it starts to look like you will be spending more than an hour on it, then I would look to just re-install, it will take ...


5

check if the 'Microsoft SharePoint Foundation Sandboxed Code Service' service is started SharePoint 2010 Central Administration -> System Settings -> Manage Services on Server


5

Did you try the solution mentioned over on this post? Activating and deactivating publishing feature breaks SP2010 wikis? I don't know if it will work for you, but it might be worth a try. I didn't have any success with that previous answer though and went the other way and delved into the bowels of SharePoint and found that even though I was ...


5

When you delete a Site Collection, it will still remain in the Content database until the "Gradual Site Delete" Timer job is run (by default, it runs once daily). So, once you delete the site collection and run the timer job, then you can again restore the same site collection in the same content database.


5

Instead, your path should be /_LAYOUTS/1033/STYLES/My/show.jpg


5

Click on your project name in Solution Explorer window. Then, select View -> Properties Window from the main menu. Finally, change Site URL property:


5

Just for starters, I think you have called the ExecuteOrDelayUntilScriptLoaded function in a wrong way.(You have given an extra set of curly braces for the function inside. Try this code: string getJS(string title, string htmlContent) { return (string.Format(@" ExecuteOrDelayUntilScriptLoaded(function () { var options = ...


5

Did you checked that the SharePoint timer and SharePoint Search Service are running? Also have a IISReset (or even go for a full reboot at extremes) and make sure these Services are starting properly. Ocassionally expired/changed passwords could also be the cause of services not starting.


5

Is your production a multi server farm? I think you are facing the following issue: http://blogs.msdn.com/b/calvarro/archive/2011/11/06/sharepoint-2010-amp-visual-studio-2010-error-ocurred-activate-features-feature-with-id-installed-in-this-farm-cannot-be-added-to-this-scope.aspx It turns out that VS 2010 internally implements a call to the method ...


5

Based on your question, there are two areas to address: How to help your particular problem How to handle workflow errors in general with SPD For your particular problem: I see something that may improve your process based on your description. You mention your general workflow as the following steps: item changes workflow reads fields workflow does ...


5

I found the answer on this blog: http://tech-karma.blogspot.be/2013/05/sharepoint-2013-online-app-403-response.html I changed the code so it doesn't download the file to disk but puts it in a MemoryStream public void PutInStream(ClientContext context, string fileNameInDocumentLib, Guid listID) { //Find the file by name ...


5

You only see the last error because Set-Content overwrites the existing content, use Add-Content instead. If you want to have a more encompassing approach, like Robert suggested, there's a more PowerShell'y (?) way of doing this with Start/Stop-Transcript which takes all console output between the Start & Stop cmdlet calls and outputs it to a file.


5

Under the website properties in IIS, GOTO > Traffic > Filtering and disable Verify Normalisation. This setting is preventing your site from displaying pages with escaped characters in the URLs. [update] In later versions of IIS it is in the general tab of the website properties, and not under Traffic.


5

When I've ran C# within PowerShell, I've done the assembly bit differently (I'm in O365, so only use CSOM): $path = "path to folder containing dll's (e.g.,ISAPI folder in 15 Hive)" $assemblies = @( "$path\Microsoft.SharePoint.Client.dll", "$path\Microsoft.SharePoint.Client.Runtime.dll" "System.Core" ) $cSharp = @" using System; using ...


5

You can choose any of the 3 options from below. Option 1: Replace the default PageNotFoundError.aspx in the Page Library – One of the easiest and Convenient way to replace default text in PageNotFoundError.aspx is to either edit the PageNotFoundError.aspx that resides in the Page Library or to delete it and replace it with a Custom error Page that has the ...


4

$siteUrl = "http://ukreddy:3456/" $siteCollection = Get-SPSite $siteUrl Enable-SPFeature "PublishingSite" -Url $siteCollection.Url -force Enable-SPFeature "PublishingWeb" -Url $siteCollection.Url -force http://ukreddysharepoint2010.blogspot.co.uk/2014/05/error-systemargumentexception-value.html Sharepoint was failing to activate the feature PublishingWeb. ...


4

This was exactly our issue. We had extended the Array.prototype and for whatever reason it caused the SP scripts to start failing. We already had another prototype extension that caused no issues. We ended up just moving it into a utility function instead.



Only top voted, non community-wiki answers of a minimum length are eligible