Scott Oseychik

Issue Summary:

While attempting to validate a FAST Search Server SSA (Search Service Application), you may receive an error similar to the following:

Steps to Reproduce:

·         Go to the FAST Search site you have created; for example http://sharepoint2010/fastsearch

·         Click the site actions button and select site settings

·         Click on Site Collection Administration > Go to top level Site setting

·         Locate FAST Search Keyword under Site Collection Administration

·         Click FAST Search Keyword

Additional data further illustrating the failure:

Using the ULS Viewer for SharePoint (see http://code.msdn.microsoft.com/ULSViewer), we can see an exception being raised in the w3wp.exe process:

01/20/2010 16:47:30.22  w3wp.exe (0x0D24)        0x13C0  Office Search Server       Query   dka1      High                SearchServiceApplicationProxy::GetSearchServiceApplicationInfo--Proxy Name:Search Service Application EndPoint: https://sharepoint2010:32844/6f74cf8ccbee4ee091947354884bc791/SearchService.svc             e242b393-f830-41a2-b77b-d5af69bcad8b

01/20/2010 16:47:30.28  w3wp.exe (0x0D24)        0x13C0  Office Search Server       Query   dk8z       High                SearchServiceApplicationProxy::GetChannel--Channel Creation time: 62.5204    e242b393-f830-41a2-b77b-d5af69bcad8b

01/20/2010 16:47:30.30  w3wp.exe (0x0D24)        0x13C0  Office Search Server       Query   dka2      High                SearchServiceApplicationProxy::GetSearchServiceApplicationInfo--Id: Elapsed Time: 78.1505 Proxy Name/ID: Search Service Application/8360cf90-772b-4ce6-957e-6f99f43a30c8 EndPoint: https://sharepoint2010:32844/6f74cf8ccbee4ee091947354884bc791/SearchService.svc  e242b393-f830-41a2-b77b-d5af69bcad8b

01/20/2010 16:47:30.31  w3wp.exe (0x0D24)        0x13C0  Office Search Server       Administration  dml8      Exception                System.UriFormatException: Invalid URI: The format of the URI could not be determined.     at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)     at Microsoft.Office.Server.Search.Administration.AbstractFastAdminFactory`1.GetChannel()     at Microsoft.Office.Server.Search.Administration.AbstractFastAdminFactory`1.CreateService()     at Microsoft.SharePoint.Search.Extended.Administration.Common.AbstractServiceLocator`1.CreateChannel(ServiceFactory`1 serviceFactory)     at Microsoft.SharePoint.Search.Extended.Administration.Common.AbstractServiceLocator`1..ctor(ServiceFactory`1 serviceFactory)     at Microsoft.SharePoint.Search.Extended.Administration.KeywordContext..ctor(ServiceFactory`1 serviceFactory)     at Microsoft.Office.Server.Search.Administration.FASTAdminProxy.get_KeywordContext()     at Microsoft.Office.Server.Search.Extended.Administration.Facade.AdminOMHelperBase..ctor(String siteID)     at Microsoft.Office.Server.Search.Extended.Administration.Facade.KeywordHelper..ctor(String siteId)     at Microsoft.Office.Server.Search.Extended.Administration.Internal.UI.ContextualKeywordManagement.OnLoad(EventArgs e)            e242b393-f830-41a2-b77b-d5af69bcad8b

Cause and Resolution:

This error may manifest itself when FAST Search Server 2010 has been introduced into your SharePoint Server 2010 environment, yet a search site has not been setup for FAST Search Server 2010.

To resolve this issue, please follow these steps:

·         Open a new Internet Explorer instance and browse to Central Administration, or open it from the Start menu.

·         Go to “Application Management,” -> “Service Application Associations.”

·         Click the sharepoint2010:80 web application (http://sharepoint2010 is the name of our SharePoint 2010 Server in this example)

·         Look through the list and locate the “FAST Query.” You will find it grayed out with the text [set as default].

·         Locate the dropdown box on top of the window called “Edit the following group of connections.”

·         Select “custom.”

·         Check all the service applications except “Search Service Application.” Instead, make sure the “FAST Query” is selected.

·         Click OK.

It’s with mixed emotions that I’m announcing my departure from the Unified Communications Escalation Team to pursue an exciting opportunity in the Enterprise Search Group.  Since joining the UC Team, the past two years have unquestionably been the most fulfilling time I’ve had at Microsoft, and I’m sure you’ll understand when I say that this was not an easy decision for me to make.

Helping shape the UC Escalation Team has taught me countless valuable lessons that I will certainly carry forward into my new gig.  Debugging an entirely “foreign” product, building new relationships, fostering a team environment that celebrates rocking out (and having a blast while doing it!) ... words can’t even begin to describe just how amazing it’s been being a part of this team!  It’s been a true honor working with you all, who I consider to be some of the coolest, most talented people both here at Microsoft and beyond.

I’ll be relocating to Boston, Massachusetts (Go Sox!) as a Senior Escalation Engineer in the FAST Enterprise Search Group, with a focus on growing the future Escalation Engineers in that business.  One of my goals is to apply what makes us such a successful team here in the UC Escalation Team, and instill these same virtues of pride, passion, tenacity, and job satisfaction in my future teammates.  That, and I hope they have a decent sense of humor! <g>

Life is what you make it, make it good.

Scott

p.s. Given the current real estate market, I'm likely going to be in Charlotte for a little while longer.  But if you happen to know anybody that’s interested in the baddest townhouse in all of Ballantyne, send ‘em my way!

Summary:

Yahoo will be performing scheduled maintenance on their OCS Gateway Servers during the following maintenance window:

Confirmed Maintenance Start Date: Tuesday, November 17, 2009, 5:00pm Pacific Time

Projected Maintenance End Date: Tuesday, November 17, 2009, 5:30pm Pacific Time

Users may encounter sporadic access service availability, service disruption, and incorrect presence during this maintenance window.

User Action:

No action needs to be taken by your Office Communications Server administrator(s).  Additionally, there will not be any further notification regarding this maintenance activity unless there is a broad disruption of service.  In such cases, we will relay outage communication accordingly.

Summary:

Microsoft's RTC Sustained Engineering Team just released their latest Cumulative Update (“CU3”) for Office Communicator 2007 R2 (as well as Office Communicator Phone Edition), and Office Communications Server 2007 R2.

Notes:

1.      As of 10/29/09, KB 968802 is in the process of being updated (should be completed within 24-48 hours), and will contain additional guidance regarding installation method options available.

2.      The RTC Sustained Engineering Team will deliver the Office Communicator 2007 R2 patch via Microsoft Update.  Office Communications Server 2007 R2 updates will also be posted to Microsoft Update, but due to the dependency on the backend database update in KB 969834, it will only be visible if KB 969834 has already been installed (see http://support.microsoft.com/kb/969834).

Updates:

KB 968802, “List of available updates for Communications Server 2007 R2”

·        http://support.microsoft.com/kb/968802

·        http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b3b02475-150c-41fa-844a-c10a517040f4

KB 975611, “Cumulative Update for Office Communications Server 2007 R2: October 2009”

·        http://support.microsoft.com/kb/975611

·        http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b3b02475-150c-41fa-844a-c10a517040f4(server.msp)

KB 972884, “Cumulative Update for Communicator 2007 R2: Oct 2009”

·        http://support.microsoft.com/kb/972884

·        http://www.microsoft.com/downloads/details.aspx?FamilyID=515d6dba-4c6a-48bb-a06a-d99c5742676d&displaylang=en

KB 977065, “Office Communicator 2007 R2, Phone Edition update: October 2009”

·        http://support.microsoft.com/kb/977065

·        http://www.microsoft.com/downloads/details.aspx?familyid=565595BE-6CF3-4A61-A1E4-12555749CA64&displaylang=en

Credit:

Again, big ups to the entire RTC Sustained Engineering Team!  If you’re on campus, truck on down to Building 30, 2nd floor, and thank them for their hard work (plus, Ken Ewert always welcomes a good Canadian joke)!

Summary:

America Online will be performing scheduled maintenance on their SIP Access Gateways during the following maintenance window:

Confirmed Maintenance Start Date: 10/08/2009 04:00 ET (24 Hour Time)

Projected Maintenance End Date: 10/08/2009 06:00 ET (24 Hour Time)

There may be sporadic access service availability and users may experience service disruption.

User Action:

No action needs to be taken by your Office Communications Server administrator(s).  Additionally, there will not be any further notification regarding this maintenance activity unless there is a broad disruption of service.  In such cases, we will relay outage communication accordingly.

Summary:

When using Microsoft Office Communicator 2007 R2, double-clicking a Contact fails to launch a new conversation window.  However, you are still able to right-click a Contact, and start an IM session by selecting “Send an Instant Message.”

Cause:

When double-clicking a Contact, OC 2007 R2 uses XML to initialize a new conversation window, and we’re finding several customers who have incompatible and/or legacy builds of MSXML.DLL that are encountering these failures.

Example Callstack:

ChildEBP RetAddr 

0006f98c 00475448 communicator!CDUIBase<DirectUI::Button>::InitializeFromXML

0006f9c4 00475309 communicator!CRosterContactView::CreateInstance+0x8b

0006f9e4 004dd544 communicator!CContactManager::CreateElement+0xeb

0006f9fc 004dd563 communicator!VirtualListView::CreateElement+0x30

0006fa14 004dc3af communicator!VirtualListView::FillVisibleLink+0x122

0006fa48 004d57db communicator!VirtualListView::FillViewWithoutRefresh+0xbd

0006fa80 004f347b communicator!VirtualListView::FillView+0xa9

0006fa90 004f3489 communicator!VirtualListView::OnThaw+0x30

0006fa98 00482d69 communicator!Freezable::Thaw+0xf

0006facc 0046cd9c communicator!CContactGroupItemBase::AddItemAtIndex+0xba

0006fadc 0046d13e communicator!CContactGroupItemBase::AddItemLast+0x10

0006fb08 0046d0e3 communicator!CContactManager::AddContact+0x57

0006fb20 004b0d40 communicator!CRosterListView::OnParticipantAdded+0x3f

0006fb60 0046d2b1 communicator!CRosterListView::SetContext+0x10a

0006fb94 0046cf79 communicator!CDUIConversationFrame::InitializeChildren+0xd0

0006fbe0 00479f8b communicator!CDUIConversationFrame::Initialize+0x234

0006fc34 0045cba0 communicator!CDUIConversationFrame::EnsureConversationWindow+0xe3

0006fc60 0045bf6a communicator!CDUIConversationFrame::CreateNewWindow+0x76

0006fcac 0045cb89 communicator!CDUIConversationFrame::FindOrCreateTwoPartyConversationWindow+0xde

0006fcd0 00427ba3 communicator!ConvUI_FindOrCreateTwoPartyConversationWindow+0x1e

0006fd68 0055d909 communicator!CSelectedContacts::StartActionWithSelectedContacts+0x1a3

0006fd88 7e418734 communicator!CSelectedContacts::WndProc+0x4e

0006fdb4 7e418816 user32!InternalCallWinProc+0x28

0006fe1c 7e4189cd user32!UserCallWinProcCheckWow+0x150

0006fe7c 7e418a10 user32!DispatchMessageWorker+0x306

0006fe8c 00505efb user32!DispatchMessageW+0xf

0006fed8 005079ac communicator!COcApp::RunMessageLoop+0xa1

0006fee8 00507b85 communicator!ATL::CAtlExeModuleT<COcApp>::Run+0x1e

0006ff18 00507a9c communicator!COcApp::RunApp+0xed

0006ff30 00507a05 communicator!WinMain+0x7e

0006ffc0 7c817067 communicator!__tmainCRTStartup+0x140

0006fff0 00000000 kernel32!BaseProcessStart+0x23

Example incompatible/legacy version of MSXML.DLL:

0:008> lmvm msxml

start    end        module name

71130000 711b3000   msxml      (export symbols)       msxml.dll

    Loaded symbol image file: msxml.dll

    Image path: c:\windows\system\msxml.dll

    Image name: msxml.dll

    Timestamp:        Fri Nov 05 13:10:21 1999 (38230F7D)

    CheckSum:         000850E5

    ImageSize:        00083000

    File version:     5.0.2919.6303

    Product version:  5.0.2919.6303

    File flags:       0 (Mask 3F)

    File OS:          40004 NT Win32

    File type:        2.0 Dll

    File date:        00000000.00000000

    Translations:     0409.04b0

    CompanyName:      Microsoft Corporation

    ProductName:      Microsoft(R) Windows (R) 2000 Operating System

    InternalName:     MsXML.dll

    OriginalFilename: MsXML.dll

    ProductVersion:   5.00.2919.6303

    FileVersion:      5.00.2919.6303

    FileDescription:  XML OM for Win32

    LegalCopyright:   Copyright (C) Microsoft Corp. 1981-1999

Resolution:

To resolve this issue, please install XML Version 6.0 and XML Version 3.0 SP7.

Microsoft Core XML Services (MSXML) 6.0

http://www.microsoft.com/downloads/details.aspx?FamilyID=993C0BCF-3BCF-4009-BE21-27E85E1857B1&displaylang=en

Microsoft XML Parser (MSXML) 3.0 Service Pack 7 (SP7)

http://www.microsoft.com/downloads/details.aspx?familyid=28494391-052b-42ff-9674-f752bdca9582&displaylang=en

Huge credit goes to Dieter Eckstein for this solution!

Summary:

Yahoo! will be performing maintenance that will affect their OCS gateways.  The outage is scheduled to be brief, but as a precautionary measure, the following maintenance window has been declared:

Maintenance Start Date/Time:  9/24/2009, 10:00pm Pacific Time

Maintenance End Date/Time:  9/25/2009, 1:00am Pacific Time

Impact:

Office Communicator users may notice incorrect presence of their Yahoo! Contacts, or may not be able to communicate via PIC with their their Yahoo! contacts.

User Action:

No action needs to be taken by your Office Communications Server administrator(s).  Additionally, there will not be any further notification regarding this maintenance activity unless there is a broad disruption of service.  In such cases, we will relay additional outage communication accordingly.

Summary:

Installation of the OCS 2007 R2 “Backend” hotfix package (http://support.microsoft.com/kb/969834) may fail, and unfortunately, the error message presented to the Administrator isn’t entirely clear as to what the root cause is.

More Information:

If you find that installation of OCS2009-DBUpgrade.msi is failing against your backend SQL RTC databases, locate and open the resulting QFE_DBSetup.log file.  The following output is generated in the QFE_DBSetup.log, and note the highlighted entry below:

/PoolName: specified FQDN. Assuming /PoolName:R2POOLNAME.contoso.com

Attempting to discover BackEnd SQL instance from AD.

LDAP Query (ConfigurationNamingContext): LDAP://CN=Configuration,DC=contoso,DC=com;((&(objectClass=msRTCSIP-Pool)(msRTCSIP-PoolType:1.2.840.113556.1.4.803:=2)(msRTCSIP-PoolDisplayName=R2POOLNAME.contoso.com)));distinguishedName,msRTCSIP-BackendServer;subTree

Backend Server Instance List: R2BESQL

Backend Server Instance for Pool 'R2POOLNAME.contoso.com' is 'R2BESQL'

Discovered SqlServer R2BESQL

Updating EE server database stored procedures. This will take a while ...

cscript dbsetup.wsf /Verbose /Role:ee /SqlServer:R2BESQL

Microsoft (R) Windows Script Host Version 5.6

Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

Installed SQL Server 2005 Backward Compatibility version is 8.05.2004

Connecting to SQL Server on R2BESQL

Error attempting to validate the SQL server: reconfigure statement failed. This SQL instance has pending configuration changes that need to be resolved before installation can continue.

[Microsoft][ODBC SQL Server Driver][SQL Server]Ad hoc update to system catalogs is not supported.

Workaround:

1.       In SQL Server Management Studio, run the following SQL statement:

sp_configure 'allow updates', '0'

RECONFIGURE WITH OVERRIDE

2.       Re-run OCS2009-DBUpgrade.msi

Credit:

Many thanks to Santhosh K for finding this needle in the haystack while I was busy waking up half of the RTC Dev Team.  :-)

Summary:

As a single point of reference, here are all of the latest updates/releases for our Unified Communications suite of products ...

Office Communicator R2, Office Communications Server R2, Conferencing Attendant R2, and Communicator Mobile R2

KB 968802, "Updates for Communications Server 2007 R2"

http://support.microsoft.com/kb/968802

KB 969695, "Update for Communicator 2007 R2: July 2009"

http://support.microsoft.com/kb/969695

KB 970275, "Office Communicators Server 2007 R2 Attendant hotfix rollup package: July 2009"

http://support.microsoft.com/kb/970275

KB 972398, "Office Communicator 2007 R2 Phone Edition update: July 2009"

http://support.microsoft.com/kb/972398

Live Meeting Console & Conferencing Add-ins for Outlook

KB 969696, "Update for Live Meeting Conferencing Add-in for Outlook: July 2009"

http://support.microsoft.com/kb/969696

KB 969697, "Windows-based Live Meeting 2007 client update package: July 2009"

http://support.microsoft.com/kb/969697

Office Communications Server 2007 R2 Group Chat

KB 969819, "Microsoft Office Communications Server 2007 R2 Group Chat Hotfix"

http://support.microsoft.com/kb/969819

The RTC Sustained Engineering Team has signed off and published the July update packages for R2!

Updates for Communications Server 2007 R2

http://support.microsoft.com/kb/968802

Update for Communicator 2007 R2: July 2009

http://support.microsoft.com/kb/969695

Office Communicators Server 2007 R2 Attendant hotfix rollup package: July 2009

http://support.microsoft.com/kb/970275

Office Communicator 2007 R2 Phone Edition update: July 2009

http://support.microsoft.com/kb/972398

Notes:

1.  The Knowledge Base articles are being published and all should be available within 24 hours.

2.  All of these patches are now available via Microsoft Customer Support Services (specifically, the Unified Communications Support Team), except for the Communicator Phone Edition R2 release, which is available via web download.

3.  We will also have the OC 2007 R2 on Microsoft Update today.  The OCS 2007 R2 (server update) will not be on Microsoft Update due a dependency on the back-end fix that cannot be delivered via Microsoft Update.

4.  KB 968802 is a rollup of all OCS 2007 R2 released patches.  This KB article will be continuously updated as newer patches are released.

Summary: 

Following on the heels of success of the Exchange Remote Connectivity Analyzer (created by Shawn McGrath and Brad Hughes), Premal Gandhi (UC Support Escalation Engineer), Matthew Fresoli (Supportability Program Manager) and Jason Stine (Senior Lead Program Manager) have been busy designing and writing a complimentary tool: The Office Communications Server Remote Connectivity Analyzer.

The tool is available at https://www.TestOcsConnectivity.com

Overview:

The Office Communications Server Remote Connectivity Analyzer is a web site for IT Administrators to validate and diagnose end-to-end Office Communications Server scenarios.  The site simulates multiple Office Communications Server client access scenarios from outside the customer’s infrastructure and reports whether the test was successful.  If the test fails, we inform the IT Admin exactly where in the process it failed as well as provide troubleshooting tips on resolving the issue.

In this beta version, the tool provides the following end-to-end tests:

·         Office Communications Server Remote Connectivity

·         Office Communications Server Remote Connectivity w/AutoDiscover

Coming Soon:

We will be expanding the Office Communications Server scenarios in the next few months to include the following:

·         Deeper level of diagnostic information - MSDiagnostics header

·         More detailed troubleshooting information based on MSDiagnostic header

·         Additional tests

Feedback:

If you have feedback on the tool or suggestions for additional tests or improvements, please use the feedback link provided on the site.

Summary:

America Online ("AOL") uses Global Server Load Balancing ("GSLB") to maintain their SIP gateway farm.  Their configuration uses sub VIPs, one for each of their two datacenters.  Whenever AOL performs maintenance (new code, hardware, etc.), they use GSLB to take one datacenter offline while they update it and point all of the SIP traffic to the secondary datacenter.

As with all GSLB systems, DNS caching on the client side can be an issue.  For example, this past week (July 16th), AOL replaced some hardware at one of their sites.  When doing so, they directed all traffic to their other site around 12am EDT.  It takes a maximum of 30 seconds for these changes to be reflected in DNS. 

Several of our Office Communications Server customers were having issues connecting via PIC to AOL (through their SIP gateways) as late as 6:30am that morning, but that the issue resolved itself in about an hour's time.  This sounds very much like DNS caching at work.  That is, the users began using the system at 6:30am and continued to have issues until their DNS was refreshed.

Action Item:

While it is unclear where the caching took place (local host, ISP DNS, local network, or within the OCS topology itself), a good rule of thumb is that whenever an OCS customer is unable to reach AOL's SIP gateways via PIC, the first troubleshooting step should be to initiate a DNS flush (and that it is best to use the sip.oscar.aol.com FQDN instead of a specific IP address when connecting to AOL).

Summary:

America Online will be performing scheduled maintenance on their SIP Access Gateways during the following maintenance window:

Confirmed Maintenance Start Date : 07/15/2009 22:00 ET (24 Hour Time)

Projected Maintenance End Date : 07/16/2009 00:00 ET (24 Hour Time)

There may be sporadic access service availability and users may experience service disruption.

User Action:

No action needs to be taken by your Office Communications Server administrator(s).  Additionally, there will not be any further notification regarding this maintenance activity unless there is a broad disruption of service.  In such cases, we will relay outage communication accordingly.

Summary:

You may find that OCS 2007 / OCS 2007 R2's Federation and/or PIC fails against partners who do not support Entrust root certificates signed using a 2048-bit public key.

For example, the "broken" certificate chain may resemble the following:

Edge server's certificate -> Entrust L1B chain -> Entrust 2048 Root

Workaround:

For Federated partners who do not support the 2048-bit Root, you can introduce an additional chain certificate which points back to the Entrust 1024-bit root. The chain of authority would then be as follows:

Edge server's certificate -> Entrust L1B chain -> Entrust 2048 chain -> Entrust 1024 Root

To accomplish this, you will be replacing the Entrust 2048 Root certificate with the attached Entrust 2048 chain certificate.

Here are the steps to follow:

1. Start up your MMC console and add the Certificates snap-in for your server's Computer Account.

2. Under "Trusted Root Certification Authorities/Certificates," remove the Entrust.net Certification Authorities (2048) certificate.

3. Ensure you have the Entrust.net Secure Server Certification Authority certificate under the same Trusted Roots folder.

4. Under "Intermediate Certification Authorities/Certificates," import the attached Entrust.net Certification Authorities (2048) chain certificate as follows:

i. Save the attached "2048-to-1024-Cross-Cert.txt" 2048 chain certificate as a *.crt file.

ii. In MMC, expand the Intermediate Certification Authorities folder.

iii. Right-click on Certificates and select All Tasks -> Import

iv. Follow the resulting Certificate Import Wizard to import the 2048 chain certificate into the Intermediate Certification Authorities store.

5. Check to make sure you have two Entrust Certificates under Intermediate Certification Authorities/Certificates: The Entrust Certification Authority - L1B and the Entrust.net Certificate Authority (2048).

Credits:

Many thanks to Jimmy Levesque and Mark Giannotti in ECS Technical Support at Entrust Certificate Services for this information!

Summary:

Using Microsoft Office Communications Server 2007 R2, Federation may fail against organizations that are using Lotus Sametime.

Resolution:

IBM has a hotfix which addresses this issue within Lotus Sametime.

More Information:

Please refer the following IBM support document; Ref #1389588