Skip to main content

Authentication failed because the remote party has closed the transport stream

While trying to configure Search Settings in my new Index Server, I received this error when I clicked "Search Settings" from SSP:



In my farm I was planning to run both Index and Query services on same server. I did some research and found that this could be because of corrupted SSL for the Office Web service. The reason it seems to be .NET Framework 3.5 SP1 !! Yes it seems if we enable search service or configure Index server on a box which has .NET Framework 3.5 SP1 the SSL of the Office web service in IIS would go corrupted.

I had a similar situation; I was replacing the Index server in my MOSS farm version 12.0.0.6219 I brought up this new server with same OS and framework patch level as the existing index server. That was a mistake because my existing Index server was setup in 2008 and that time there was no .NET Framework 3.5 that time. It got installed later during a patching window. But in my case when I made the patch level same on my new server I installed all framework on it, 2.0, 3.0, 3.5, and 3.5 SP1. So on top of that I configured MOSS and setup search service.

I found an article by Brendan Griffin where he discusses about a similar issue:

He was suggesting to reinstall the SSL but I was confused about doing that since this is a production environment. What finally worked for me were these:

1. Remove the server from farm by running PSConfig wizard.
2. Uninstall .NET framework in the order 3.5 SP1, 3.0, and then 2.0.
3. Install .NET framework 2.0, 3.0 and 3.5 - I did not install framework 3.5 SP1
4. Ran PSConfig wizard again the added the server to the farm, configured search, added the new Index server to SSP.

Now there was no issues. The root cause was that I had .NET Framework 3.5 SP1 installed before configuring server as Index server.

Hope this helps someone who face this situation!


Labels:

Comments

Post a Comment

Popular posts from this blog

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007.  Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm.  For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...
5 comments
Read more

SharePoint Designer Workflow Failed to Start - Cancelled by System Account

I was working on a List workflow the other day in SharePoint Designer 2010. This list already had a workflow which was working perfectly fine and I needed another manual workflow in it. No matter what I tried the workflow would fail and would log a message in the history list that Workflow failed to start and it was cancelled by System Account . I observed that the same happened with new workflows in that list, new workflows in other lists and I even tried creating new subsites and workflows were behaving the same way. I googled for a while and there were many suggestions to clear SPD cache which did not help me. I played with SPD 2010 for a while and observed that the workflow xml and xoml files were checked out. I read in some blogs that this could cause this issue as well. I tried to check those files in but then I was greeted with a new error! " Cannot perform this operation. The file is no longer checked out or has been deleted ." I had no clue what was happening...
10 comments
Read more

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more