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


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

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


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

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

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


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

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


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

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

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.


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

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


4

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


4

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


4

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.


3

Interesting - I used this very scenario (upgrading a field from text to note) in a demo recently in a conference talk, to show off SharePoint 2010's new upgradable Features framework. In both SP2007 and SP2010, changing the type of fields which are in use is unsuppported, as you've discovered. My recommendation would be: Take a backup in case rolling ...


3

Be aware that SPSite also has an AllowUnsafeUpdates property that you can try. If you change this, do it inside a try/finally so that you are sure not to make your site vounerable to cross-side scripting attacks (it would seem from your code sample that you already have bypassed the XSS protection from all your sub-sites, so you might want to enable that ...


3

The two main tools for dealing with upgrade problems on your SharePoint 2010 farm are the Test-SPContentDatabase Powershell command and the stsadm command enumallwebs. The Test-SPContentDatabase tool will check the content db against a specific site collection. It can be safely run either before or after the database is attached, as often as required. I ...


3

I used the Process Monitor as suggested by Jesus Shelby and it helped me identify the registry key I needed to delete. I deleted the following registry entries: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server After I deleted these two entries, the setup asked me to enter the product key. Although, ...


3

We are using the SharePoint Guidance Library from MS Patterns & Practices - both for 2007 and 2010 projects. The SPG Library contains an excellent interface implementation of a Logging framework which is decoupled from your custom code by a Service Locator pattern making the unit testing so much easier. The SPG Library delivers a configuration framework ...


3

Try opening your page in web part management mode by adding ?contents=1 to the end of your url If your webpart page URL is http://myportal/pages/default.aspx Browse to http://myportal/pages/default.aspx?contents=1 This will list all webparts, and allow you to delete some of them. By the way, how many webparts do you have per zone and in total?


3

make sure that when your go new -> project -> event receiver , then paste in your url for debugging http://site.com/sitetest/Home.aspx delete the "Home.aspx" or what ever it may be named, so it ends up as "http://site.com/sitetest/"... also, I'm sure that you have SharePoint installed on the machine, but make sure your permissions are correct.


3

There is one generic error in SharePoint that will throw the file xxxx has been modified by SHAREPOINT\system And that is when you don't have web.AllowUnsafeUpdates = true; But that error is old, really old IIRC. But the likely reason is that you may be performing more than one update in the same request, so the second update will throw that error ...



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