This project is read-only.
1
Vote

BLG file import broken in Windows 7

description

Hi,
 
It looks like the BLG file import is broken in Windows 7 (and Win 2008 R2). The error message is about a failed connection to SQL Server from the Performance Data Helper (PDH) so I'm guessing they changed the way relog works from the previous OS versions. Could someone have a look to see if its a quick fix?
 
Thanks,
 
Christian

file attachments

comments

amitban wrote Apr 28, 2010 at 7:00 PM

Can you attach the SQL Nexus log file? This should be available in %temp% folder.

wrote Jun 3, 2010 at 11:25 PM

kdixon wrote Jun 3, 2010 at 11:26 PM

I'm having the same problem. I have attached the SQL Nexus log file.

amitban wrote Jun 23, 2010 at 2:14 AM

This is what I see in the SQL Nexus log file. No errors for the Perfmon load. Could you post a screenshot or the error text so that I can look into this further?

SQLNexus Information: 0 : Loading SQLDIAG2.BLG
DateTime=2010-06-03T22:03:00.3839243Z
SQLNexus Information: 0 : Done. (45 sec), 0 lines processed; 0 rows inserted.

Are you able to process the BLG files manually using RELOG.EXE?

wrote Nov 4, 2010 at 12:51 AM

christianbolton wrote Nov 4, 2010 at 12:51 AM

Hi amitban, the error shows up in the Application Event Log, not the SQLNexus log: Call to SQLAllocConnect failed with [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.

Screenshot attached.

amitban wrote Nov 5, 2010 at 12:06 AM

This is not an error with SQLNexus. The PDH dll which is invoked to load data into a SQL database is not able to locate the SQL instance using an ODBC connection to which the data needs to be loaded. ODBC traces need to be collected and analyzed to make further progress regarding the root cause of this issue. This is outside the scope of this discussion forum as this doesn't look to be an issue with SQL Nexus. If the same error occurs while trying to load Perfmon data into a SQL Server database on the same box using Windows Performance Monitor, then you could open a support incident with CSS. Or as a workaround, you could try loading the data into another server where this issue doesn't exist.

rich_mccloud wrote Jan 26, 2012 at 4:17 PM

I also ran into this issue in Win7 x64...the problem was resolved by starting SQL Nexus using the 'Run as Administrator' option...obviously UAC is getting in the way of the BLG import proces.. Hope this helps.

wrote Feb 22, 2013 at 12:49 AM