Value does not fall within the expected range error while check-in of document

I was getting error while check-in of document from document library into SharePoint interface. Actually I have created Meta data fields and attached to document, I was able to check-in document from office application like word, but if I check-out and check-in same document from document library interface then I was getting error "Value does not fall within the expected range".

I tried looked into event log, but didn't find any good information then I found below error from SharePoint Logs.

Error into log file:

Application error when access /_layouts/Checkin.aspx, Error=Value does not fall within the expected range.   at
Microsoft.SharePoint.SPFieldCollection.GetFieldByInternalName(String strName, Boolean bThrowException)     at
Microsoft.SharePoint.SPFieldCollection.GetFieldByInternalName(String strName)     at Microsoft.SharePoint.SPListItem.get_MissingRequiredFields()     at
Microsoft.SharePoint.ApplicationPages.Checkin.OnLoad(EventArgs e)     at System.Web.UI.Control.LoadRecursive()     at
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 

Solution:

By looking at the error, I thought that issue was only because of meta fields column name and as we know internal name and display name is different for each column, I also found on the internet regarding same error saying that its because of  misspell name attribute into schema.xml file.

Then by looking and comparing each field I have found out that, by mistaken I added one extra equal(=) to end of my field name, by correcting my column name, my problem gets resolved and was able to successfully check-in document from SharePoint interface also.

SharePoint Logs – Tracing service lost trace events

Some time, my SharePoint logging didn’t work properly for some reason, if I looked into my SharePoint Logs directory then in every generated log file, I have found below lines.

Date and time        wsstracing.exe        (0x07E4) 0x1634         ULS Logging  Unified Logging Service uls1        Monitorable              Tracing Service lost trace events.           Current value 8.

Solution:

I need to restart my logging service, SharePoint uses "Windows SharePoint Services Tracing" service for writing logs into ULS logs, so I went to services and restarted my "Windows SharePoint Services Tracing" services, once I did that, a new logs was created into SharePoint logs file. I also found out that might be this errors showed due to upgrade of service pack 1.

Crawling of PDF document from SharePoint search

I had issue while crawling of our SharePoint sites, I was getting error for the outlook message file in which there were embedded PDF document.

Errors which I was getting into crawl log:
1. The filtering process could not be initialized. Verify that the file extension is a known type and is correct
2. Error HRESULT E_FAIL has been returned from a call to a COM component.

I have found on the internet that I have to install extra filter into server which will search and crawl for PDF files, there are 2 free filters available. One is from Adobe Ifilter 6.0 and one from Foxit Filter.

I tried to play with both filter but I was getting error into PDF and message file, I know, I was missing in some little configuration and installation of something.

At the last, I have found one very good and important link, as per that link, Adobe has not created any separate iFilter for PDF file types after Adobe Reader 7 version.

So they suggested us to installed Adobe Reader 8 or reader 9 version into our server, because after reader 7, Adobe package iFilter functionality into same software as plugs-in.

So after doing configuration from below links, I got the success, now I am able to crawl message file and PDF documents from the SharePoint sites.

MAIN IMPORTANT LINK:

http://nhmn.com/blogs/pointedman/PointedPost/08-05-21/How_to_Correctly_Configure_pdf_i-Filter_for_SharePoint_2007.aspx?ReturnURL=%2fblogs%2fpointedman%2fPointedPost%2f08-05-02%2fSharePoint_SSPScopeDeploy_for_MOSS_launched.aspx&BlogTagID=7249c096-182f-4abb-9420-ea7a21659377

Good Reference Links.

http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611&promoid=DNRLI (all about Adobe PDF IFilter v6.0) 

http://www.adobe.com/support/downloads/product.jsp?product=1&platform=Windows (Different products from Adobe)

http://blog.tylerholmes.com/2008/04/walkthrough-installing-adobe-v6-pdf.html ( How to install Adobe filter)

http://downloads.fuxinsoftware.com.cn/pub/foxit/manual/enu/FoxitPDFIFilter10forMOSS_manual.pdf (Manual for Foxit Filter)

Block specific file types while uploading from SharePoint interface

One easy way:

We can block specific type of files from entering file extension into “Blocked File Types” from the SharePoint Central Admin Site -> Operations-> Security Configuration.

We can select specific web application for blocking or not allowed file types/extension list.
 
Other way:

We can also do programming and modify current Upload.aspx page, we can write simple JavaScript by checking file extension and content type when user is uploading any file and then we can give alert to user if its not valid file type or extension type for uploading into SharePoint.

How to add new managed property and customize advanced search page

We can customize search and advanced search page, by adding properties to it, generally all columns which we created into site comes in crawl properties when we do FULL CRAWL of the SSP. So then after we have to create new managed properties from going to SSP->Search Settings, we have to mapped crawl properties to manage properties and we can use those all managed properties into customization of advanced search page by adding “Properties”  into it.

You can find all these stuff from below links

http://jopx.blogspot.com/2006/08/add-document-properties-to-advanced.html

http://www.mosssearch.com/searchcolumn.html

http://www.codeproject.com/KB/sharepoint/MOSS_Advanced_Search.aspx

How to add property into advance result page

MOSS Faceted Search

From last some time, I am working in Search Functionality in SharePoint, we have installed “Search 2.5” into our server, and it gives us more ready to use web part functionality like search facets, caching, stemming and many more.

You can download faceted search 2.5 from codeplex by below link.

http://www.codeplex.com/FacetedSearch

We have also installed SharePoint Infrastructure Upgrade patch, it includes Federated Search like we can easily view and capture our search data from SharePoint SSP Screen.

http://blogs.msdn.com/sharepoint/archive/2008/07/15/announcing-availability-of-infrastructure-updates.aspx

http://blogs.msdn.com/enterprisesearch/archive/2008/07/15/announcing-availability-of-infrastructure-updates.aspx

Till now, I did all things from SharePoint GUI only, not SharePoint Search object model, it has also many search library through which we can code our own specific search functionality, through SharePoint GUI, we can also customize functionality by changing respective web part configuration XML file.

I will give you updates regarding same on regular basis.

Conflict into SharePoint version

One time, I had problem while installation of MOSS 2007, my installation was corrupted due to some problem, so I was not able to repaired, every time I was getting error when I run “SharePoint Products and Configuration Wizard” from the interface.

I find the below solution, If we run below psconfig command from command prompt then will able to install SharePoint successfully without any version confliction.

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN>
psconfig -cmd upgrade -inplace b2b -wait -force

SharePoint Products and Technologies Configuration Wizard version 12.0.6217.1000
Copyright (C) Microsoft Corporation 2005. All rights reserved.

Performing configuration task 1 of 4
Initializing SharePoint Products and Technologies upgrade...

Successfully initialized SharePoint Products and Technologies upgrade.

Performing configuration task 2 of 4
Initiating the upgrade sequence...

Successfully initiated the upgrade sequence.

Performing configuration task 3 of 4
Upgrading SharePoint Products and Technologies...

Successfully upgraded SharePoint Products and Technologies.

Performing configuration task 4 of 4
Finalizing the SharePoint Products and Technologies configuration...

Successfully completed the SharePoint Products and Technologies configuration.

Total number of configuration settings run: 4
Total number of successful configuration settings: 4
Total number of unsuccessful configuration settings: 0
Successfully stopped the configuration of SharePoint Products and Technologies.
Configuration of the SharePoint Products and Technologies has succeeded.

Unable to connect to database. Check database connection information and make sure the database server is running

In the morning, we were getting below production issue in all SharePoint Sites.

Problem: Users getting errors saying that "Unable to connect to database.  Check database connection information and make sure the database server is running"

The SharePoint Farm appeared to have a login issue with the Database Server. The following error was noticed on the Database Server Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 10/27/2008
Time: 9:36:22 AM
User: N/A
Computer: SQL DB Server Name
Description:
This computer was not able to set up a secure session with a domain controller in domain AD due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.

Resolution: one of my colleague just logged into our Database server with SharePoint service account to verify the account was not locked out.  He was able to log in without error.  Almost immediately after logging in, the Database Connectivity issues started to clear up and we were able to open all SharePoint site and central admin site without any the errors.

We didn’t figure out the exact root cause for the issue, because we already looked into SharePoint Log, event log  and database log, but at the last, we found that in some particular time of period there were problem with SharePoint AD service account, and by just logging into server, it gets resolve.

I’ll update you, if we find the root cause for the problem.