I am profiling an ASP.NET web application through IIS. The application is configured to use a local instance of SQL Server 2005 Standard. The instance name is SQLSTD.
When I profile the application and enable SQL profiling, it never collects SQL data and complains about SQLEXPRESS. I do have SQL 2008 express and 2008 R2 express installed as well. Maybe this is confusing it?
I also confirmed that the trace provider is enabled for my SQLSTD instance by running 'logman query provider' and seeing a line for SQLSTD Trace.
Note: SQL 2005 Standard was installed *after* ANTS Profiler. Maybe that's the issue?
It's probably nothing to do with SQLEXPRESS and more to do with trace not being configured correctly. The Profiler tries to be "helpful" and misidentifies the issue as being related to SQL Express if it finds an instance of SQL Express on the server.