Haldi Ganapati

Haldi Ganapati

TF400324: The underlying connection was closed Faulting application name: w3wp.exe TFS Application Crashes

Server: TFS server 2015 with update 1 

Try to get latest from visual studio
OR
Try to edit code pages from the Browser 


The application crashes and start receiving below errors in Event viewer:

Source Control Explorer
TF400324: Team Foundation services are not available from server {tfs URL}.
Technical information (for administrator):
The underlying connection was closed: A connection that was excepted to be kept alive was close by the server

Faulting application name: w3wp.exe, version: 8.5.9600.16384, time stamp: 0x5215df96
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18007, time stamp: 0x55c4c341
Exception code: 0xe0434352
Fault offset: 0x000000000000871c
Faulting process id: 0xfec
Faulting application start time: 0x01d18413e0bc4575
Faulting application path: c:\windows\system32\inetsrv\w3wp.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 62951f24-f008-11e5-80cd-00155d1c5b09
Faulting package full name: 
Faulting package-relative application ID: 


There are no official fix/Solution from Microsoft for the same

After research we found that the servers had been hardened and Security patches had been installed (VA-BA scan and scripts).

Resolution:

To resolve the error we need to uninstall a Security patch: KB3081320
Or if you decide to keep the security patch you could simply start Windows service “CNG Key Isolation” and the issue is resolved.
Once the service is started all TFS functionalities work as expected.

rsErrorImpersonatingUser

Cannot impersonate user for data source ‘CDRDB’. (rsErrorImpersonatingUser) error


rsErrorImpersonatingUser


While Configuring Lync Server: You get the above error when you click on reports or configure reports.


So what do you do ?


Solution:
Start by checking the following items:
  1. SQL permissions for the user being used for reporting purpose.
  2. AD Groups membership of the User
  3. Permission on SSRS for the User
  4. Permission on LYNC reports
  5. Check Web applications on IIS (if windows auth is enabled)
Finally check if the account had a valid connection from SSRS to DB.

Perform the below steps:

  • Open Reporting Services Configuration Manager
  • Click on Report Manager URL
  • Click Report URL (This will launch IE which I hope if your default browser)
  • Drill into
  • LyncServerReports
  • Reports_Content
Update the username and password: for the Lync report database.(do the same for both the database) as shown below: