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

"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

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:
Post a Comment
Read more

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er
3 comments
Read more