Showing posts with label SharePoint. Show all posts
Showing posts with label SharePoint. Show all posts

Jul 8, 2011

Unable to upgrade SharePoint Products and Technologies because an upgrade is already in progress. Upgrade progress can be monitored using the Central Administration Web Application or by monitoring the upgrade log on server...

I got this error while trying to upgrade a SharePoint server with WSS SP2.

It was so that since the visual upgrade using configuration wizard failed, I had started the upgrade using stsadm command line. But that failed too. Then when I again tried the visual upgrade, it said that an upgrade is already in place hence it will not update. So I was in a fix like how to upgrade it then.

Unable to upgrade SharePoint Products and Technologies because an upgrade is already in progress. Upgrade progress can be monitored using the Central Administration Web Application or by monitoring the upgrade log on server...


This link was of a great help, its a failsafe method (and only to be used if nothing else works) : Microsoft Technet link

What you have to do basically is fire this command up using stsadm:

stsadm -o setproperty -pn command-line-upgrade-running -pv No
What it does is basically sets a property to 'No' which will allow the visual Configuration Wizard to continue!

Oct 11, 2010

How to debug filter link data in Performance Point Server

This post shows how one can debug filter links with web page report in Performance Point Server 2007 with minimal coding: http://nickbarclay.blogspot.com/2008/02/debugging-filter-links-with-web-page.html

Sep 27, 2010

This page contains content or formatting that is not valid. You can find more information in the affected sections

You get this error when you are trying to update a SharePoint webpart tool part or something like that and you click on 'Publish' page button. This only happens if you have any Validation Controls on your webpart.

Resolution: As you have validation controls on your webpart UI and you are not filling in anything, it is not letting your page to postback and you need to disable rendering the webpart while you are modifying the toolpart. You can do that by writing down code as below in your 'CreateChildControls method of webpart

protected override void CreateChildControls()


{
...
WebPartManager wp = WebPartManager.GetCurrentWebPartManager(this.Page);
if (wp.DisplayMode == WebPartManager.BrowseDisplayMode)


{

base.CreateChildControls();
//Render your code here
}

}

Once you do this, while you are editing the webpart (toolpart properties that is) your webpart won't load t he required field validators and you can safely publish the page with updated webpart properties

Sep 1, 2010

How To: Programmatically add a List as a webpart in a SharePoint page in WSS 3.0

This post explains exactly what you need to do if you want to add a particular list to a webpart page programatically:
 
http://stackoverflow.com/questions/1588019/programmatically-insert-a-list-as-a-webpart-in-a-webpart-page-in-wss-3-0

Set default page for SharePoint Publishing Site

Just follow the steps shown in the sample function in the post below to set default page from code

http://chrisbarba.wordpress.com/2010/01/11/set-default-page-for-sharepoint-publishing-site/

Aug 27, 2010

Empty SharePoint Recycle bin in one go

It happened that I had around thousands of items in sharepoint site recycle bin and deleting it with sharepoint default delete items button was simply not possible as it would take forever to delete all items.

This nice little hack was very userful to me which deleted all items in a second!
As mentioned in this post
http://itfootprint.wordpress.com/2008/03/14/empty-sharepoint-user-recycle-bin/

you just have to navigate to recycle bin page and type javascript:emptyItems();
which will delete all items.

Jul 2, 2010

EditorPart does not have an ID

Full Error Reads:

EditorPart does not have an ID

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: EditorPart does not have an ID.


Resolution:
Just set the id of the tool part in its constructor to some string!

Jun 9, 2010

Getting Started with SharePoint Server 2010 for IT Pros

Micorosoft technet has this great new learning series for SharePoint 2010.
Check it out here http://technet.microsoft.com/en-us/sharepoint/ee518660.aspx

There are 11 modules which explain you :

1 | What Can SharePoint Server 2010 Do for Me?
This module introduces Microsoft SharePoint Server 2010 capabilities to IT professionals...
2 | How SharePoint Server 2010 Works
This module covers software and hardware requirements, and the basic concepts...
3 | Simple Install for Testing in SharePoint Server 2010
This module explains how to create a single server environment for testing.
4 | Search in SharePoint Server 2010
This module explains the search capabilities in Microsoft SharePoint Server 2010 and more...
5 | Backups in SharePoint Server 2010
This module covers new backup features in Microsoft SharePoint Server 2010 and more.
6 | Creating Your First Web Application, Site Collection and Web in SharePoint Server 2010
This module explains creating the first site on a SharePoint farm by using Microsoft SharePoint Server 2010 and more...
7 | Getting Started with Security in SharePoint Server 2010
This module covers security in Microsoft SharePoint Server 2010.
8 | Windows PowerShell for SharePoint Server 2010 Administrators
This module covers Windows PowerShell basics and SharePoint cmdlets.
9 | Tools to Optmize the Performance of SharePoint Server 2010
This module covers performance-related tools.
10 | Introduction to Upgrade in SharePoint Server 2010
In this module covers upgrade process and more...
11 | Service Applications and Topologies in SharePoint Server 2010
This module explores how SharePoint 2010 provides services in a flexible and scalable architecture

 Once again the link is http://technet.microsoft.com/en-us/sharepoint/ee518660.aspx

May 29, 2010

Content controls are allowed only in content page that references a master page

I was using a custom task edit form when this happened. Actually when I deployed the page to the layouts folder and tried accessing it, the error was displayed.
The full error details reads like:
Content controls are allowed only in content page that references a master page. at System.Web.UI.MasterPage.CreateMaster(TemplateControl owner, HttpContext context, VirtualPath masterPageFile, IDictionary contentTemplateCollection)

at System.Web.UI.Page.get_Master()

at System.Web.UI.Page.ApplyMasterPage()

at System.Web.UI.Page.PerformPreInit()

at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)


Resolution: It is so that you have to use sharepoint website's master page if you have to include the sharepoint chrome. I forgot to set the master page in my custom aspx page deployed to 12 hive. That's why I got the error. If you want to display it that way, put code similar to what I have written below in order to set master page dynamically for your custom page:

using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint;
SPWeb _web;
protected override void OnPreInit(EventArgs e)
{
base.OnPreInit(e);
//Using current SharePoint site's masterpage
this._web = SPControl.GetContextWeb(Context);
this.MasterPageFile = _web.MasterUrl;
}

Mar 19, 2010

Invalid URL Parameter error in WSS 3.0

You get this error when you use custom spcf page and custom layout pages for web parts. In my case, the problem was with custom web part spcf page. The full error read:

http://websiteURLhere:8888/_vti_bin/owssvr.dll?CS=65001

Invalid URL Parameter

The URL provided contains an invalid Command or Value. Please check the URL again.
Troubleshoot issues with Windows SharePoint Services. 

Follow this tutorial to the point, it helped me to identify where I went wrong (it was in the value field of the optio n element of the template list seen on the screen by the way!)

Creating Custom Web Part Page Templates for Microsoft SharePoint Products and Technologies

http://msdn.microsoft.com/en-us/library/dd583147%28office.11%29.aspx

Feb 9, 2010

Unexpected error on server associating the workflow

You get this error when you try to add a custom created activity into a WorkFlow via SharePoint Designer 2007. The error reads like:

Unexpected error on server associating the workflow
Resolution: This is likely because you forgot to add the concerned DLL as safecontrol in the web.config for the concerned web application. Also see that it is added to section as well.

The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled

You get this error when you try to add a wsp into sharepoint using STSADM tool or by doing something similar.
The full error reads something like this:

"The timer job for this operation has been created, but it will fail because the administrative service for this server is not enabled. If the timer job is scheduled to run at a later time, you can run the jobs all at once using stsadm.exe -o execadmsvcjobs. To avoid this problem in the future, enable the Windows SharePoint Services administrative service, or run your operation through the STSADM.exe command line utility."


If you get this, what you need to do is just run this command from commandline having access to stsadm utility like this:

stsadm -o execadmsvcjobs
This will then execute the jobs and all will be well!

Also, in order to stop getting this service related errors, go to the services managment snapin and enable this service: 'Windows SharePoint Services Administration service'

Dec 30, 2009

Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version

You get this error when you try to restore a sharepoint backup using STSADM tool.
The full error will read like:
Your backup is from a different version of Windows SharePoint Services and cannot be restored to a server running the current version. The backup file should be restored to a server with version '12.0.0.6421' or later.

Most probable cause for this would be that you took backup from a sharepoint installation which is latest or is updated using a service pack and where you are trying to restore it (possibly in a different machine/ environment) is lacking the service pack.

Resolution:
In my case backup was taken from MOSS installation which had MOSS SP2 installed but the target machine had no service packs, hence I installed WSS service packs then MOSS service packs and then the error disappeared!

Dec 18, 2009

The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again.

The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again.

You get this error message when you are trying to modify something in a sharepoint website be it either creating a list or adding/modifying items to a list in same or different web application from the one you are running your code.
I got this error when I ran this code from a webpart in one webapplication which tried to create a list in another web application in same farm.

Exact error:
The security validation for this page is invalid. Click Back in your Web browser, refresh the page, and try your operation again.

Resolution:

You need to write two lines of code to resolve this. Basically you need to turn AllowUnsafeUpdates to true before running your code and set it to false after your code executes.

An example code snippet would be:

SPSecurity.RunWithElevatedPrivileges(delegate()
{

SPWeb myWeb = new SPWeb();

myWeb.AllowUnsafeUpdates = true;


//do your code modifications like adding list or list items here

myWeb.AllowUnsafeUpdates = false;

});

Once you do like this, the error should disappear!