SharePoint:Shared Services Error "An indexer is not assigned to the Shared Services Provider 'SharedServices1"

 I was unable to import user profiles, after our development server crashed and fortunately we restored it using the last known back-up of the Virtual machine. All of a sudden our user profiles import and search crawling and indexing services stopped abruptly, throwing a nasty "An indexer is not assigned to the Shared Services Provider 'SharedServices1' error.

Luckily i found a solution for the same:

a. Log in to Central Administration
b. Select your Shared Services provider and choose "Edit Properties" from the drop-down context menu
c. Configure your Index server and it works like a charm...

SharePoint:The search request was unable to connect to the Search Service

Resolution:

There was a SharePoint farm not returning search results. The error it returned was

"The search request was unable to connect to the Search Service"

After looking at it, it was a very simple fix. The server wasn't configure to server search queries. A simple ticking of the box in central admin and it fixed the problem. To fix this:

Go to Central Admin

Operations

Services on Server

Office SharePoint Server Search Service Setting

Make sure "User this server for serving search queries" is checked.

Thats it!!!!!!!!!!

Another thing that could be causing it is the Account used to search might not have the right access needed or the Search services aren't running. Check that

• Office SharePoint Server Search and
• Windows SharePoint Services Search

Should be both running. If you're still having problems, let me know and I'll try to help you out.

SharePoint:filtered lookup field

I have done some investigation for doing a filterd lookup field for SharePoint list/libraries
got some references check this out hope this will help you....

Links:

http://filteredlookup.codeplex.com/
http://dattard.blogspot.com/2007/04/sharepoint-2007-filtered-lookups.html
http://sanjayapdl.wordpress.com/2008/02/21/filtered-lookup-field-in-sharepoint-list/

SharePoint:Exception from HRESULT: 0x80040E14

Issue:

I got this error when i am updating the item in the list and when i create a new item in the list
Error:Exception from HRESULT: 0x80040E14,0x80004004

Resolution:

I have done some investigation and found that the above error message might occur because of SQL transaction logs were full and needed to be truncated. It seems that the SQL Server is running out of the log space.
so clear the log file you will be out of this error!!!!!!! so simple right.

SharePoint:The workbook that you selected cannot be opened.

Issue:

When you open document in the document library if you get this error message "The workbook that you selected cannot be opened.

The workbook may be in an unsupported file format, or it may be corrupt.
Would you like to try and open this file in Excel? "

Resolution:

1. From Administrative Tools, open the SharePoint Central Administration Web application.
2. On the Central Administration home page, click Application Management.
3. On the Application Management page, in the Office SharePoint Server 2007 Shared Services section, click Create or Configure this Farm's Shared Services.
4. On the Manage this Farm's Shared Services page, click SharedServices1 (Default). This is the Shared Services Provider (SSP) that you will configure.
5. On the Shared Services home page, in the Excel Services Settings section, click Trusted file locations.
6. On the Excel Services Trusted File Locations page, click Add Trusted File Location.
7. In the Address section, type the location and name of the SharePoint Office SharePoint Server 2007 document library that you want to add as a trusted file location in Excel Services. If the document library is stored in the Windows SharePoint Services 3.0 content database, ensure that Windows SharePoint Services 3.0 is selected as the Location Type.
8. In the External Data section, select the type of data connections that you will allow workbooks in this trusted file location to contain and click OK.

SharePoint:Editing Profile in SharePoint Site

Issue:

Unable to edit SharePoint Profile

Resolution:

_layouts/editprofile.aspx add this at the end of the url...

SharePoint:object not set to an instance of an object with the webpart

Issue:

This issue is raised by one of the user who is unable to see a particular webpart in Sharepoint he is getting an error message "object not set to an instance of an object". and this is only happening for a particular users....hmmm god dam..

Deploying webpart to SharePoint 2007 using  Visual Studio Extensions for Windows SharePoint Services (VSE WSS) and getting error message “Object reference not set to an instance of an object”.

Resolution:

You need to add the user to the any of the people and groups...simple right.

This is for the second one:

1] Copy the built webpart.dll to c:\windows\assembly (GAC)

2]  In the folder location where webpart VSE solution was created found setup.bat file in bin\Debug, and this is the file which VSE calls when deploying the solution and has instructions to run it. Ran the setup.bat from command prompt as “setup /uninstall” this ran ok, then ran setup /install this ran ok too. Modified the setup.bat file and add the line to remove the webpart.dll from the GAC and add the webpart.dll assembly to GAC as under:

under :LDeploy section before goto :EOF added the following line:

===========================================================

"%programfiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" -if webpartTest.dll

"%programfiles%\Microsoft Visual Studio 8\SDK\v2.0\Bin\gacutil.exe" -uf webpartTest

Thanks for your time and patience in this matter. 

Thank You,