ADO.Net BID tracing, EWT and Logman.exe for dummies

  • Thread starter Thread starter Nick
  • Start date Start date
N

Nick

I'm trying to enable BID tracing of ADO.Net + SQL Server 2005 as described in
http://msdn2.microsoft.com/en-us/library/aa964124.aspx.

I only get an empty out.etl file which contains no events.

My problem I think lies in the setup/config of ewt on my system. When I run
"logman.exe query providers" I get the below output which doesn't seem
healthy. But I can find no sources on the web indicating what might be the
matter.

c:\>logman.exe query providers
**************************************
Provider GUID
-------------------------------------------------------------------------------
SQLOLEDB.1
{C5BFFE2E-9D87-D568-A09E-08FC83D0C7C2}
MSDAPRST.1
{64A552E0-6C60-B907-E59C-10F1DFF76B0D}
SQLSERVER.SNI.1
{AB6D5EEB-0132-74AB-C5F5-B23E1644DADA}
MSADDS.1
{13CD7F92-5BAA-8C7C-3D72-B69FAC139A46}
HTTP Service Trace
{dd5ef90a-6398-47a4-ad34-4dcecdef795f}
SQLSRV32.1
{4B647745-F438-0A42-F870-5DBD29949C99}
WSAT Trace Provider
{7f3fe630-462b-47c5-ab07-67ca84934abd}
MSADCE.1
{76DBA919-5A36-FC80-2CAD-3185532B7CB1}


Error:
Not found
The command completed successfully.
*******************************

So was it successful? did it "Not find" an error? or what?

I held SysInternals procmon against it and discovered that it wasn't finding
the file given by HKLM\Software\Microsoft\BidInterface\Loader\:Path

So I changed it from the suggested
"%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\ADONETDiag.dll" to
"Microsoft.NET\Framework\v2.0.50727\ADONETDiag.dll" and it seemed to at least
find it, but things didn't improve.

So I thought perhaps there was a problem with another collection so I would
delete all the collections and set them up from scratch. But "Logman delete"
of every collection it shows in the list above didn't seem to have any
effect. "Logman query providers" still shows the same output.

Any help appreciated.
 
Back
Top