Tag Info

Hot answers tagged

12

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


9

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

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


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


8

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


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


6

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


6

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


6

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


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

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

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

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://www.khamis.net/blog/Lists/Posts/Post.aspx?ID=12


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

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.


4

ULS logs are generated by the server in the following folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS You can modify the level of logging through Central Admin e.g. more verbose or less verbose. It's a good idea to add a "12 hive" toolbar to the start bar so you can easily access logs and all the rest of SharePoint ...


4

This is caused by the installation of KB977724 when Office 2007 applications are also installed on the machine. There are further details about this problem on the Office Sustained Engineering site. A hotfix to this hotfix can be downloaded from Microsoft Download Center.


4

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


4

Please, try to add List="116" attribute to your Module element, as it is shown in this MSDN how-to: http://msdn.microsoft.com/en-us/library/ms441170.aspx <Module Name="MasterPages" List="116" Url="_catalogs/masterpage"> <File Path="MasterPages\custom_main.master" Url="custom_main.master" /> </Module>


4

This issue will sometimes pop up if you commonly access your pages with two urls, i.e. http://mysite.company.com and http://machinename. Verify that the user is accessing the site using the URL specified as the primary address for that zone in Alternate Access Mappings. If you are using the http://machinename url convention, I would strongly recommend that ...


4

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


4

Can you check for duplicate SharePoint lists with the same name in each of the Site's within View All Site Content. I have seen those cause problems in Managing Content and Structure. If you get a duplicate list make sure your Recycle Bin is switched on then delete the list and restore using the Recycle Bin. Regards Simon


4

This is all client related, so registry fixes (hacks) should be done to the client machine. I tend to avoid over emphasis on the Explorer view. It is not going to work consistently for a wide range of users based on devices, browsers, and installed software which tends to lead to more support issues.


4

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


4

Your architecture is completely wrong. Event receivers are best for short, non-intensive operations. Anything that requires resources, such as loading an exe into a new process, should be performed outside of the event process. As an example, the event receiver can queue a request that is processed by a service application. This model is how everything ...


4

Feature events are asynchronous. It will execute whenever it has time to execute, you can't control that, thus it can't have a context. If you need data about the site your feature_activated method triggered on, use var web = properties.feature.parent as SPWeb For a web-scoped feature var site = properties.feature.parent as SPSite for a site scoped ...


4

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.



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