Showing posts with label MOSS 2007. Show all posts
Showing posts with label MOSS 2007. Show all posts

Jul 12, 2011

Office SharePoint Server Search service in stopping mode

I got this error when I was trying to get a old system using MOSS 2007 to update. I restarted the 'Office SharePoint Server Search' service but it just froze on stopping mode and won't do anything.

I searched online and most of the posts asked to restart the server, which I was not ready to do as it was a production environment.

I got this nice work around and it worked for me:

The service is basically 'OSearch' so what I did was

* Opened a command prompt on the server and type: tasklist /svc
* From the list, check which one you need to close. I checked it was mssearch.exe for 'OSearch' . (remember there will be two mssearch.exe one for moss and wss I guess.)
* Note down its process id
* Run another command to kill that process from command line: taskkill /PID ABCD /F
(where ABCD is your port number)

Once this is done, run services.msc from run prompt and start your search service, it will not be in a hanged state anymore!

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;
}

A text field contains invalid data. Please check the value and try again

I once entered a paragraph of sample text in my custom task form which submits it to sharepoint list. Now the error surfaced 'A text field contains invalid data. Please check the value and try again'. The problem was that there is basic limit on fields in sharepoint. For text field it was  255. So the moment I add 256 characters or more, it throws this error.

Resolution
255 column limit is there on text field. Ensure that text is entered appropriately

May 7, 2010

Set Task Fields in custom task edit form and access using ExtendedProperties in customWorkflow

I found issue in accessing my custom content type properties set from a custom task edit form back in the workflow. It was so that I was unable to access one of my field in the afterproperties method. It may happen to some of your properties but not all.

Resolution: The trick here is to set the task properties suffixed with some value to ensure that you get it back as it is in the workflow.

Follow this blog post for details:

http://social.msdn.microsoft.com/forums/en-US/sharepointworkflow/thread/f0c66406-7bcb-4f08-b572-5a0bfeac016b/

http://russellmccloy.blogspot.com/2008/04/my-sharepoint-workflow-is-not-seeing-my.html

May 6, 2010

Value cannot be null. Parameter name: s

If you get this error in the workflow activation event while creating sequential or state machine workflow for MOSS 2007, follow the below mentioned steps:

Resolution: You need to bind the workflowProperties object properly. I have mentioned steps below:

In the workflow designer go to your initial state anc clidk on the event driven activity to reach the on workflow activated event

Now in its properties window, notice workflowproperties , it will be empty, from there select the workflowProperties from dropdown. This way it will get binded the next time you try to run the workflow.

Once you do that, it will no longer be null and will give you any serialized data that you require while initiating the workflow.

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'