Hello all,

we have the latest FIM R2 SP1 installed and configured in our environment.

Unfortunatelly, we still experience following "performance issue", which we also had in FIM 2010.

The initial requests against the FIM Portal takes several seconds. After the initial request the portal response ultimatelty to the requests.

This happens the first time and is faster once you "active in the page", but if you leave the page then return 2 minutes later...its again very slow for the first request.

Any ideas?

Thomas Vuylsteke has a good post about this 

http://setspn.blogspot.co.uk/2011/06/fim-2010-warm-up-your-portal-iis.html

Dave

Is this in a isolated environment, no internet connection?

yes it is isolated!

The warmup script mentioned above is good, but I assume the real problem is with crl checking against internet from the isolated network, thus the portal does some timeouts.

Enable CAPI2 log from the eventviewer and check for errorid 53, it should tell you which processes do the checking, this way you can create a custom program.exe.config -file next to the .exe that does the callings and configure it there not to do so. More on this can be found here: http://blogs.msdn.com/b/spses/archive/2012/08/29/crl-verification-failure-sharepoint.aspx and here: http://blogs.msdn.com/b/chaun/archive/2014/05/01/best-practices-for-crl-checking-on-sharepoint-servers.aspx

Did my suggestions work for you?

Yes, thanks. You provided us a good direction to investigate and troubleshoot.

It helps us a lot. Many Thanks again.

More info on this can be found on this KB article: http://support.microsoft.com/kb/936707, do the configuration change on the %windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet.config and test the performance again.

And as I mentioned in the previous post, enable CAPI2 log and see what executables are doing the CRL checking and create your own customized application.exe.config -file next to the executable, with the configuration described in the KB article above.