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

How to create the DPMRecoveryWebApplication

1.   Open the SharePoint 3.0 Central Administration console from the Start Menu.

2.   Once the SharePoint 3.0 Central Administration console is open, click on the Application Management tab which opens to display all of the various options for managing your SharePoint installation.

3.   Under the SharePoint Web Application Management heading, click on the Create or Extend Web application.

4.   The Create or Extend Web application page appears with two options. Choose Create a new Web application.

5.   After clicking the Create a new Web application link, the Create New Web Application page appears displaying various necessary fields for details about the web application that is being created. Here is a brief summary of the important fields of this page.

o   Chose the Create a new IIS web site and in the description, name it “DPMRecoveryWebApplication”.

o   In the Port field, give it a unique port which is not shared by any other internal application.

o   The Host Header and Path fields can remain unchanged.

o   Scroll down to the radio button Create new application pool and in the Application pool name box, note that the entry name includes the port number and the SharePoint recovery server name.

o   Under the Select a security account for this application pool, select the Configurable radio button and type in a suitable account and password in the fields that follow.

This is the last entry to make before hitting OK to have the web application created. Upon completion of the DPMRecoveryWebApplication web application, Application Created screen appears. At this point, schedule time to run ‘iisreset /noforce’.

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you