CLRProfiler (CLR Profiler) waiting for application to start common language runtime - .NET Runtime

Symptom: When you start an application using CLR profiler, it always says [waiting for application to start common language runtime] and wait forever

Resolution

1. Most probably you may be using CLR Profiler 1.1 to profile .NET 2.0 Application. Download CLR Profiler 2.0 from the here
   
2. 
   
   If it is VISTA or Windows XP, may be CLR Profiler doesn't have enough permissions to run. Try running CLR Profiler as an Administrator.
   Right Click on the CLRProfiler.exe -> Run as -> Administrator

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding – Microsoft ADO.NET

Symptom: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Resolution:

1. SqlConnection: If this happen when tries to connecting to SQL Server, then try increasing the timeout of the connection
   Connection String: server=Server;database=Database;uid=Uid;pwd=Pwd;timeout=600 (ConnectionTimeout is read-only)
2. SqlCommand: More interestingly if you manage to connect successfully and although you set a fat timeout value to your connection command object does not inherit the timeout from its connection. It uses its own timeout value. More logically ConnectionTimeout and CommandTimeout.   
   

    So increase the timeout of the command, which is not read-only like SQLConnection

    command.CommandTimeot = 600 (set to 10 minutes)  

Reference: ASP.NET Forums