Warm up your SharePoint Web Applications on Windows 2008 R2 using the IIS 7.5 Application Warm-Up module

I have just recently built a new SharePoint 2007 farm on a complete Windows 2008 R2 server platform and part of my standard build procedure is to implement a warm up routine, usually in the form of a script that is scheduled every morning to launch my SharePoint Web Applications.  Most of you will most likely know what I am referring to here, the slowness that end users experience when loading a SharePoint site for the first time in the morning!?

By default IIS will recycle its worker processes during the night, in my case IIS 7.5 tells me this happens at 1:04 AM.  You can locate this information in IIS Manager / Application Pools / Highlight your application pool in question and select Recycling under Actions / Edit Application Pool.

So what is recycling all about?  Here is a brief primer;

Recycling is all about stopping any current w3wp.exe processes that are running for a particular Web Application Pool and starting a new one.  The purpose of this maintenance routine is to clear the cache and start afresh! This routine obviously causes SharePoint to be quite slow when accessed for the first time after the recycling process.  This is because when accessing a SharePoint Site/Page for the first time, that information needs to be re-compiled and loaded into memory again.

So what can we do about this first time slowness that occurs every morning?  Wake SharePoint up!

There are arrays of scripts that have been developed by 3rd party developers that can be scheduled to run straight after the recycle occurs.  These scripts are usually required to be modified for your Web applications in question.

With the introduction of IIS 7.5 and Windows 2008 R2 however, there is an actual module developed by the IIS team that will integrate directly with IIS allowing you to seamlessly enable your application pools to load your web applications after a recycle occurs.  You can download the extension here; http://www.iis.net/expand/ApplicationWarmUp At the time of this writing, the Application Warm-Up module is still in beta, but I have been using it on our production servers for over a month without any hiccups.

So let’s begin our step by step guide.  Download and launch the executable from the above site.

Click Install and then click Finish.  As you can see, the installation process is quite simple.

Launch IIS Manager and click on one of your SharePoint Sites.  In the middle pane, you will notice a new item listed under IIS titled, Application Warm-Up.

Double Click on Application Warm-Up.

Under Actions located on the far right pane, select Settings

Ensure that both options available are selected and ticked.

We also now need to add a request which is usually the main page of your SharePoint Site.  This is achieved under Actions, Select Add Request and enters the URL of your SharePoint Site.

The last area that you will need to venture into is also located under Actions / Edit User Context.  Here you will need to specify your Authentication settings, otherwise the module will not work and you will receive the below warning message in your Windows Application Even Log.

Log Name:      Application
Source:        IIS Application Warmup Module
Date:          8/03/2010 7:31:43 AM
Event ID:      1003
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      SERVERNAME

Description:
The description for Event ID 1003 from source IIS Application Warmup Module cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

/default.aspx
MACHINE/WEBROOT/APPHOST/SharePoint Central Administration v3/
Unauthorized

Here I have specified “Set Username and Type only” for the mode and “Windows” for the Type.  Lastly, specify an account that has access to load the SharePoint Web Application

That’s all that is to it.  All you need to do now is replicate this for each SharePoint Web application on each of your SharePoint Web Front Ends.

This neat little module has a number of advantages over scheduled scripts as it seamlessly warms up your SharePoint Web applications regardless of when the Application Pool is recycled including when you re-start your servers or re-start IIS.  Please note, this little module also works with all ASP.Net applications!

Before I let you go, if you are after a neat utility for IIS7, Spencer Harbar has developed an Application Pool Recycle Utility which also incorporates a Warm Up tool  You can download it here; http://www.harbar.net/articles/apm.aspx

Resources

IIS.Net – Application Warm up http://www.iis.net/expand/ApplicationWarmUp

IIS.Net – Using the IIS Application Warm-Up Module http://learn.iis.net/page.aspx/688/using-the-iis-application-warm-up-module/

Error: Cannot complete this action.

Error:  Cannot complete this action.
          Please try again.
          Troubleshoot issues with Windows SharePoint Services. 

      

What is the cause of this error? 

The short answer is that the page is trying to access something that doesn’t exist, or thinks does not exist.

Resolution:

1). To check which webpart is having the issue, open the site with SharePoint Designer  and double click on the page. The webpart which shows the ‘server error’ is the culprit one.

2). Right click on the webpart to visit its properties and to find its name.

3). Go to web part maintenance page by using http://xyz.com/sites/default.aspx?contents=1  and

4). Closed the offending web part.

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issue. Thank you

The Managed Metadata Service or Connection is currently not available

A managed metadata service publishes a term store and, optionally, content types; a managed metadata connection consumes these. When you enable managed metadata in your SharePoint Server 2010 application, a managed metadata service and connection are created automatically. The service identifies the database to be used as the term store, and the connection provides access to the service.

I've been trying to create new Managed Metadata services but get this error when trying to manage them:

The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.

Here are the detailed steps that i followed to resolve this issue:

Resolution:

1)  Open Central Administration by going Start--All Programs--Microsoft SharePoint 2010 Products--SharePoint 2010 Central Administration.

2)   Click on Manage Service Application which is available in Application Management section.

3)   When you click on Managed Metadata Service application, sometimes you may get the following error:

The Managed Metadata Service or Connection is currently not available

4)   Go and check whether the Managed Metadata Service has been started.

5)   Click on Application Management in the quick launch.

6)   Click on Manage services on server under Service Applications section.

7)  Check whether the Managed Metadata Web Service is started; if not then click on Start

8)   Do an IISRESET

Now you could be able to see the Managed Metadata Service properties

If you still face the same issue, go to IIS and check whether the Application pool for the metadata service is started

Note: Check the account in which the application pool for the metadata service is running. Sometimes if the password for the account is changed, you will get the same issue

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issue. Thank you :)

How to Create a New Document Library in SharePoint 2010

A library is a container for creating, organizing and managing different types of documents. It allows us to store files and Meta information about the files, so that it can be used among different team members. You can create, store and manage almost every type of file in different kinds of libraries (i.e. Word documents, spreadsheets, presentations, forms etc.)

By default a Shared Library is created when you create a site and additionally you can create as many types of libraries as you want.

1.   Select 'Site Actions', then 'View All Site Content'.

2.   Click 'Create'.

3.   The Popup will ask for Name, Description, Versioning and Template settings. Fill the fields as desired.

SharePoint ULS Log Viewer

Functionalities:

·         Parse and open multiple SharePoint ULS logs (will concatenate them if you select multiple)

·         Reorder and resize columns, sort on any column

·         Filter by Severity, Category, and Process or a custom text filter/search

·         Group multi-line stack traces into single log entries for easy viewing and copy/paste

·         View message easily in separate pane (No more scrolling in notepad)

Complete credit goes to Keir Gordon who is the creator of this utility

·         Great features

·         The interface is very intuitive, simple, and powerful.

·         Very handy to view the complex log files

·         Great tool, much easier to read the logs than Notepad or Text pad

Site Delete Alert, SharePoint Survey and Updating Document Library using Powershell scripts

Guys,

While doing some troubleshooting on one issue, I came across some fine articles which I would like to share with all of you. Complete credit goes to Mark Jones as he is the author of those articles and I want to thanks him for sharing such valuable information.

Let me describe the details as follows:

·         How to create a SharePoint survey:

http://www.collaboris.com/blogs/collaboris-blog/mark-jones/2012/01/22/how-to-create-a-sharepoint-survey-in-under-5-minutes

·         How to update multiple documents in a SharePoint document library with PowerShell:

 http://www.collaboris.com/blogs/collaboris-blog/mark-jones/2012/02/14/update-multiple-documents-with-powershell

·         How to send an email when a SharePoint site or web is deleted:

http://www.collaboris.com/blogs/collaboris-blog/mark-jones/2012/06/01/how-to-send-an-email-when-a-sharepoint-site-or-web-is-deleted

All the above three links are magnificent which consist of development as well as administration work.

In case of any queries/questions then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you J

Outlining SharePoint 2013 Improvements.

Microsoft today demonstrated some improvements in the new SharePoint that are found in the Office 365 previews.

Previews of the various Office 365 applications, served up from Microsoft's Internet cloud for the most part, were made available last month for testing. It's not exactly clear when the service will be rolled out as a final release. During today's demo for the press, Jared Spataro, senior director for SharePoint product management at Microsoft, offered a quick tour of some highlights in the new SharePoint.  

Spataro explained in the Q&A that Microsoft did not change the underlying architecture of SharePoint very much with this release, but it did add some upgrades and I/O performance improvements. However, based on what was shown during the demo, there also are user interface (UI) changes. Users of the new SharePoint see something like the flat, spare "Metro" or "modern" UI, except with a narrow menu bar at the top.

Quite a lot of the demo concerned the collaboration and social networking aspects of SharePoint, which are among the product's top uses, according to a Forrester Research survey. However, nothing was really said during the talk about Microsoft's Yammer acquisition, which will bring Yammer's enterprise social networking technologies across SharePoint, Office 365, Microsoft Dynamics and Skype. 

Better Tagging
In general, Microsoft has improved the metadata aspects in the new SharePoint, allowing users to tag content while posting, Spataro said. People are considered first-class objects in SharePoint. They can be followed, by SharePoint users, but it's also possible to follow documents, sites and tags across a Web site. SharePoint also points users to content based on a "suggested sites" feature. Users can hover over user profiles and get access to their contact cards, which bring in profile information, including info from LinkedIn and Facebook social networking pages.

My Site in the new SharePoint has its functionality split into three hubs: Newsfeed, SkyDrive Pro and Sites, as explained in this SharePoint team blog. The Newsfeed application has a sort of Facebook-like appearance with photos and e-mail threads, as well as a "Like" button. The Sites application is a tracker of site locations that are important to the user. SkyDrive Pro is a cloud-based storage place for files that works with SharePoint. Spataro said that SkyDrive Pro replaces what used to be called "SharePoint Documents" or "My Documents" in earlier editions, adding that it had been renamed to highlight Microsoft's investments in consumer cloud storage. Microsoft also offers a free SkyDrive service for consumers. 

SkyDrive Pro Replacing SharePoint Workspaces
SkyDrive Pro provides storage, synchronization and sharing capabilities for users. Cloud-based apps will sync to the desktop app by just clicking on the desktop. There's also drag-and-drop file uploading capabilities from the desktop to the browser-based app, and even drag-and-drop capabilities within the browser-based app, because of the richness of the applications. SkyDrive Pro works with various Office Web Apps, such as Word, Excel, PowerPoint and OneNote.

SkyDrive Pro has access to all of the new SharePoint capabilities. "All of the content manageable in SharePoint can be managed in SkyDrive Pro," Spataro said.

The fate of SharePoint Workspace (previously known as "Groove") in SharePoint 2013 got cleared up during the Q&A session. Groove was the invention of former Microsoft Chief Software Architect Ray Ozzie, whose retirement was announced in October 2010.

"SharePoint Workspace was the way that we did document sync and offline access with the previous version of SharePoint," Spataro explained. "And in fact, SharePoint Workspace was the evolution of the Groove client. The document store, share and sync capabilities that I showed you are actually based on the next evolution of that SharePoint Workspace. We actually used the underlying component that came from Groove, part of the sync engine, to do it. And going forward, our strategy will be to focus on SkyDrive Pro that I showed you today."

He added that people can still get access to SharePoint Workspace, "but our go-forward strategy investment will be focused on SkyDrive Pro."

Team Site Gets OneNote
The Team Site is considered the "center of gravity for people in SharePoint," Spataro said, and Microsoft has enhanced it by adding a centralized OneNote built into it. OneNote is a Microsoft Office application that lets users store photos and text in a sort of digital scrapbook. The OneNote that's part of Team Site is capable of synchronization, and it can be viewed on various mobile devices with "the same rich view," Spataro contended. The Team Site also has its own newsfeed, which will sync up with a user's main Newsfeed. Users tend to use this newsfeed service as a replacement for e-mail, he added.

Spataro said that the new SharePoint is about task completion and using social interactions to do work, so there's a My Tasks interface that users can plot against a timeline. It's capable of drag-and-drop operations, so users can create a list of tasks in Excel and drop the file into tasks lists. It's possible to edit in real time and assign tasks to different people. The whole timeline is viewable in a "project summary" page. Spataro suggested this approach is an improvement over past SharePoint releases where it was "tough to track things."

There are some SharePoint business intelligence improvements enabled by SQL Server 2012. For instance, the Excel Web App can be used to display a Power View executive dashboard, which graphically displays data. It allows slice-and-dice operations to be performed using the data or the data can be plotted over time. With these capabilities, Spataro said that Microsoft is bringing together social, task management and business insights.

Lastly, Spataro pointed to the Microsoft partner ecosystem and the extra support users can get though SharePoint apps. The apps are available in the SharePoint library or they can be downloaded from the SharePoint Store.

Spataro said he left out a lot in his presentation, noting that FAST search in the new SharePoint now has e-discovery capabilities across SharePoint, Exchange and Lync file shares. Search was one of the SharePoint features that participants in Forrester's survey said they least liked. However, it's apparently improved in the new SharePoint. 

An overview of the new SharePoint features was described earlier in this blog post by Jeff Teper, corporate vice president of SharePoint.

Ref: http://redmondmag.com 

A Step Increase in Productivity via SharePoint and KnowledgeLake

To demonstrate the step change increase in productivity that is made possible through the implementation of the KnowledgeLake’s ECM imaging solution built on the SharePoint platform.  We will explain how an international company eliminated paper documents, automatically indexed documents into SharePoint and dramatically improved the ease of finding the right document.  KnowledgeLake is also one of the very few vendors that support Office 365, Microsoft’s cloud offering. By now many companies have realized the business benefits of the SharePoint platform through the four promises of Enable Collaboration, Find and Use Knowledge, Manage Business Performance and Streamline Processes.  With the implementation of third party tools such as KnowledgeLake, companies are seeing a real increase in productivity that drives real business results in efficiencies and cost savings.

Background

One of our long time customers is an organization that must handle and process a massive amount of documents (up to 500,000 new documents a year).  Until now, all of the documents were stored as paper documents in thousands of file folders.  They actually had a very good process, but it was all paper based.  Even email correspondence was printed and filed.  If someone needed a copy of a document to send to one of their partners, they would have to physically go to the file room, retrieve the document, scan a copy and send the copy to and send the copy to their partner.  This can now be done with a few clicks of the mouse without the person ever leaving their desk. The impetus for looking at an alternative approach was that the company was moving to a new location and they wanted to avoid the need for a high density filing system, plus the wanted an improved process.

The Solution

The solution involved the basic processes for managing the documents:

1. The documents are scanned and or captured electronically
2. The documents are easily indexed into SharePoint
3. Electronic documents (email attachments or Word documents) are effortlessly indexed into SharePoint without opening SharePoint
4. Documents are retrieved via a sophisticated efficient search, retrieval and viewing engine

The KnowledgeLake tools that handle the above are:

KnowledgeLake Connect

Connect for SharePoint allows a user to save a document from Microsoft Outlook or other Microsoft office products directly into SharePoint without ever opening SharePoint.

 

KnowledgeLake Capture

Capture allows for the storing of documents directly from a PC attached scanner or from a network file folder into which scanned documents are placed.  The functionality is improved through the use of Barcode separator pages.  Just like Connect, Capture allows for the entry of the proper attributes for each document and indexes the documents into SharePoint directly without having to open up SharePoint.  Other key features of Capture are:

• Batch Scanning
• OCR for either full text of just part of a document
• Barcode reading to separate documents or define content types

KnowledgeLake Capture Server

Capture Server allows for the scanning of a batch of documents and is intended for high volume scanning.  This tool integrates with multi-function scanners and provides many of the same features as Capture.  Capture Server is great for scanning batches of invoices, contracts or batches of documents that can automatically indexed into SharePoint through barcode integration. 

KnowledgeLake Imaging

A key component of KnowledgeLake is their Imaging product which provides rich search, retrieval and collaboration functionality.

  

With Imaging you can: Search and find documents or list items across the SharePoint farm

• Pre-configure and store save searches
• Perform full-text and column property searches
• View document thumbnails and SharePoint properties within the search results

The image below shows an example of the results of an Imaging search: 

 

Conclusion

Once the project is complete, the company will realize true efficiencies and cost savings by;

• Eliminating the need for the high density filing system and expense of reinforced floor structural support
• Reducing the cost of archiving and retrieving documents from offsite storage
• Reducing the unnecessary scanning and rescanning of the same document for electronic sharing.
• Allow the remote staff to access the documents, eliminating the need for them to call the office and request files to be sent
• Saving countless hours in searching for and retrieving  documents
• Reducing paper cost

Real business solution to real business problems!

Reference: http://www.abelsolutions.com.

                  KnowledgeLake.

How to add a database as a data source with SharePoint Designer 2010.

Before you begin to add a database as a data source, we will discuss about what is a data source.

Data Source:
A data store is a data repository of a set of integrated objects. These objects are modeled using classes defined in database schemas. Data store includes not only data repositories like databases, it is a more general concept that includes also flat files that can store data.

Connect to a database by saving the user name and password

When you connect to a database by saving the user name and password, SharePoint Designer 2010 generates a SQL-based connection string that stores the user name and password in the data source connection (a process known as SQL authentication). If your site is located on a server running Microsoft SharePoint Foundation 2010, this is the preferred option for generating a connection string.

You can also create a database connection by using a custom connection string. 

1. Click Data Sources in the Navigation Pane.
2. On the Data Sources tab in the ribbon, in the New group, click Database Connection.
3. In the Data Source Properties dialog box, on the Source tab, click Configure Database Connection.
4. In the Configure Database Connection dialog box, under Server Information, in the Server Name box, type the name of the server where your database resides.
5. In the Provider Name box, do one of the following:
• If you are connecting to an external Microsoft SQL Server database, click Microsoft .NET Framework Data Provider for SQL Server.
• If you are connecting to an external database that is OLE DB compatible, including versions of SQL other than Microsoft SQL such as MySQL, click Microsoft .NET Framework Data Provider for OLE DB.
6. Under Authentication, click Save this username and password in the data connection.
7. In the User name box, type your user name.
8. In the Password box, type your password.
9. Click Next.

Because SQL authentication saves the user name and password as text in the data connection, any user with permission to open the site in SharePoint Designer 2010 can view these credentials. A security warning informs you that the user name and password are saved as text in the data connection and that other site members can access this data source. If you want other site members to access the database by using the same user name and password, click OK. If you do not want other site members to access the database by using the same user name and password, click Cancel.

10. In the Database list, click the database that you want to use as a data source, and then do one of the following:
• In Select a table or view, click the table or saved view that you want from the list, and then click Finish.

By using this option, you create a default query that selects all records in the table or view. However, after you click Finish, you can modify the default query by clicking Fields, Filter, and Sort in the Data Source Properties dialog box. 

• Click Specify custom Select, Update, Insert, and Delete commands using SQL or stored procedures, and then click Finish.

 Note   This option is available only if your administrator has turned on the Enable Update Query Support option in SharePoint Central Administration.

By using this option, you can create custom SQL commands. When you click Finish, the Edit Custom SQL Commands dialog box opens. In this dialog box, you can create commands and add parameters. After you create a custom SQL command, you can edit the query by clicking Edit Custom Query in the Data Source Properties dialog box. 

11. In the Data Source Properties dialog box, click the General tab, type a name for the data source, and then click OK.

The new database connection now appears in the Data Sources list.

 If you are trying to connect to an external server running SQL Server, make sure that SQL Server authentication is enabled on that server.

Reference: http://office.microsoft.com/en-us/sharepoint-designer-help/add-a-database-as-a-data-source-HA010355745.aspx

How to add a database as a data source: SharePoint 2007

Before you begin to add a database as a data source, we will discuss about what is a data source.

Data Source:
A data store is a data repository of a set of integrated objects. These objects are modeled using classes defined in database schemas. Data store includes not only data repositories like databases, it is a more general concept that includes also flat files that can store data.

Connect to a database by saving the user name and password

When you use Connect to a database by saving the user name and password, Office SharePoint Designer 2007 generates a SQL-based connection string that stores the user name and password in the data source connection (a process known as SQL authentication). If your site is located on a server running Windows SharePoint Services 3.0, this is the preferred option for generating a connection string. You can also create a database connection by using a custom connection string. If the Data Source Library task pane is not visible, on the Task Panes menu, click Data Source Library.

1. In the Data Source Library task pane, under Database Connections, click Connect to a database.

If the Database Connections heading is collapsed, click the plus sign (+) to expand it.

3. In the Data Source Properties dialog box, on the Source tab, click Configure Database Connection.
4. In the Configure Database Connection dialog box, under Server Information, in the Server Name box, type the name of the server where your database resides.
5. In the Provider Name box, do one of the following:
• If you are connecting to an external Microsoft SQL Server 2000 database or an external Microsoft SQL Server 2005 database, click Microsoft .NET Framework Data Provider for SQL Server.
• If you are connecting to an external database that is OLE DB compatible, click Microsoft .NET Framework Data Provider for OLE DB.
6. Under Authentication, click Save this username and password in the data connection.
7. In the User name box, type your user name.
8. In the Password box, type your password.
9. Click Next.

Because SQL authentication saves the user name and password as text in the data connection, any user with permission to open the site in Office SharePoint Designer 2007 can view these credentials. A security warning informs you that the user name and password are saved as text in the data connection and that other site members can access this data source. If you want other site members to access the database by using the same user name and password, click OK. If you do not want other site members to access the database by using the same user name and password, click Cancel.

10. In the Database list, click the database that you want to use as a data source, and then do one of the following:
• Click Select a table or view, click the table or saved view that you want from the list, and then click Finish.
  By using this option, you create a default query that selects all records in the table or view. However, after you click Finish, you can modify the default query by clicking Fields, Filter, and Sort in the Data Source Properties dialog box. 
• Click Specify custom Select, Update, Insert, and Delete commands using SQL or stored procedures, and then click Finish.

This option is available only if your administrator has turned on the Enable Update Query Support option.

 

By using this option, you can create custom SQL commands. When you click Finish, the Edit Custom SQL Commands dialog box opens. In this dialog box, you can create commands and add parameters. After you create a custom SQL command, you can edit the query by clicking Edit Custom Query in the Data Source Properties dialog box. 

11. In the Data Source Properties dialog box, click the General tab, type a name for the data source, and then click OK.

The new database connection now appears in the Data Source Library task pane.

If you are trying to connect to an external server running SQL Server, make sure that SQL Server authentication is enabled on that server.

Reference: http://office.microsoft.com/en-ca/sharepoint-designer-help/add-a-database-as-a-data-source-HA010100908.aspx 

Current Calls may continue, but with reduced functionality

Recently I have seen many cases where a client are facing issues in which MOC reconnecting again and again & goes into loop of Sign in/Sign out with error “Current Calls may continue, but with reduced functionality”. Sometimes users are getting log off continuously and sign-in on MOC or Lync after several reboots.

Causes: The issue occurs because the Office Communicator 2007 R2 users getting moved between different pools servers.

Resolution: 

Basically users who were having this issue may them moved recently between different pool server and their config file was pointing towards OLD pool server.

Most of the times it is resolved by a reboot or multiple reboots, but sometimes (when user is working remotely) it doesn’t get resolve then try to locate the file “EndpointConfiguration.cache” under the location %userprofile\Local Settings\Microsoft\Communicator\Sip_username@domain.com and delete that, client should reboot their workstation and then try.

Details: The Office Communicator 2007 R2 client updates the user's EndpointConfiguration.cache file when the user signs out of the Office Communications Server 2007 R2 pool. If the sign-out process is interrupted, the EndpointConfiguration.cache file cannot be updated with the secondary Office Communications Server 2007 R2 pool’s FQDN and TCP port information. This causes the Office Communicator 2007 R2 client to do the following:

Try to automatically sign in to the Office Communications Server 2007 R2 pool by using the legacy FQDN and TCP port information that is listed in the EndpointConfiguration.cache file

Time out and not connect because the original Office Communications Server 2007 R2 pool front-end servers are offline

Perform a DNS lookup for the SRV records that are configured for the automatic sign-in process

So, please compare the entry in EndpointConfiguration.cache and user’s allocated pool, if difference is found then better delete that else he may face the issue while working remotely.

Full-text index population for table or indexed view: SQL Server 2008

As discussed in the previous article: Full text search in SQL.  We discussed on the some of the issue you can try to resove using the Full-text Search from various MS reference.

In continuation to the same, below are the some of the references you can use to resolve the issue realted to Full text search in SQL 2008. You may get same error meaassge using full-text search.

Error : “Full-text index population for table or indexed view”.

This error may not be sufficent to give you the complete reference to the exact issue you are facing in your problem. So below I am sharing some of the resources to reolve the issue partaining to the above error.

Error : "No appropriate filter was found during full-text index population for table or indexed view"

Use KB artile : http://support.microsoft.com/kb/972650.

Error :  “Error 0x80040e97 occurs when you use integrated full-text search in SQL Server”.

Use KB article : http://support.microsoft.com/kb/2270849.

Error: You receive error messages when you perform a population for a large full-text index in SQL Server 2008

Use KB article : http://support.microsoft.com/kb/963659.

I belive referring to the any of the above KB article will surely resolve your problem. However, if still has problme then rebuilding full-text on table may help or repopulation may also work.   

A good references to troubleshoot Full- Text Indexing: http://msdn.microsoft.com/en-us/library/ms142595.aspx

If you have better solution to be suggested, you are most welcome.

Top 10 most Popular Sessions: VM World 2012.

Enhance your skills & be top of the technology.

The top 10 sessions from VMworld have been posted.
http://www.vmworld.com/community/conference/us/learn/top10

VM learning Portal: http://www.vmworld.com/community/conference/us/learn  

VM World: http://www.vmworld.com/index.jspa 

Switching from SSRS Native Mode to SharePoint Integrated Mode

SharePoint integrated mode enables Reporting Services to integrate with the SharePoint(SP) databases and security model. These features become available when you configure a report server to run within a larger deployment of a SharePoint 3.0 product or technology.

In SP integrated mode, a report server must run within a SP server farm. A SP site provides the front-end access to report server content and operations with  all report processing and rendering. The advantage of integrated mode is a rich level of integration that allows you to access and manage report server content types using the application pages and data stores of a SP Web application.

Reports, data sources, and data models in a SP document library are stored as files in the SP content database for that SP document library. Files are stored in the .rdl, .rsds, and .smdl extensions.

Advantages of SharePoint Integrated Mode:

1)   Uniform UI to access reports – No need to access reports using SP and manage using the SSRS report manager. Everything will be done through SP UI.

2)   An ability to create and manage SSRS reports, SSRS data sources, and SSRS report models from the SP UI.

3)   Reports stored in the document libraries to enable versioning, workflow capabilities, collaboration, and document management features

4)   Shared Storage – Report Catalogs stored in the SP Content DBs

5)   Shared Security – No need to manage security at both SharePoint and Report Manager

6)   Inherited Governance Policy including SLA, Backup and Restore, Support, High Availability, Disaster Recovery, and Redundancy Policies

How to Switch from SSRS Native Mode to SharePoint Integrated Mode:

Steps to switch an existing SSRS server to SharePoint Integrated mode. This does not include any steps for migrating reports—we have to do them separately.

Switching to SSRS Integrated mode:

1.   Open SQL Reporting Services Configuration Manager on your SQL Server

·         Start

·         All Programs

·         Microsoft SQL Server 2008 R2

·         Configuration Tools

·         Reporting Services Configuration Manager

2.   Click on Databases, and note the current “Report Server Mode” is “Native”

3.   Select Change Database

4.   Select “Create a new report server database,” and click “Next”

5.   Enter your server name and credentials, and select “Next”

6.   Select a new “Database Name” and change “Report Server Mode” to “SharePoint Integrated Mode,” and click “Next”

7.   Enter authentication information, and click “Next”

8.   Verify Summary, and ensure “Report Server Mode” is set to SharePoint integrated

9.   Click next and ensure everything gives success status.

10.  In Reporting Services Configuration Manger, click on Web Service URL, and then click the URL link to open

11.  We should get an error that reads something like this:

12.   Reporting Services Error:

The report server has encountered a configuration error. If the report server is configured to use SharePoint integrated mode, verify that the server is joined to a SharePoint farm and that the Report Server service account has been granted access to the SharePoint farm. (rsServerConfigurationError)

13.  This error is expected, because we need to configure Reporting Services Integration in SharePoint.

14. Continue to next step.

15. Open up SharePoint Central Administration:

16. Go to “General Application Settings,” and click “Reporting Services Integration:”

17. Fill out “Report Server Web Service URL,” and your credentials:

18. Note that the Web Service URL should be what was specified in the Report Services Configuration Manager