Access Denied due to .NET Framework 3.5 SP1
I was doing an install recently and a client happened to have installed the .NET Framework 3.5 SP1 on the servers i was working. The first environment i installed was a two server environment (1 SharePoint, 1 SQL) and everything was working fine. When i moved to a 5 server environment and started the install i started getting access denieds on the search administration page and profile administration page.
I noticed one of the servers was generating issues related to ssl which was very curious because i hadn’t configured ssl. After some sifting through logs i came upon this entry…
05/05/2009 16:38:27.95 OWSTIMER.EXE (0x0C44) 0x0F04 Search Server Common MS Search Administration 86ze High Exception caught in Search Admin web-service proxy (client). System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Authentication failed because the remote party has closed the transport stream. at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallba...
This tells me that MOSS is trying to communicate to Office Shared Services for intra server ssp communication using SSL.
After sifting though support tickets i noticed people were fixing similar issues by fixing the SSL cert assigned to Office Server Shared Services Web Service Web site.
Finally i came upon this support KB which describes how to fix it, apparently .NET 3.5 SP1 breaks the ssl cert. Still curious why SSL is being used if i didn’t configure it.