MySQL Export - Report Automatic Update Status is empty

May 20, 2014 at 11:03 AM
Edited May 20, 2014 at 12:19 PM
Hi,
great software and great work so, first of all, thank You very much.
By the way, I'm missing something in MySQL export
The specified driver is invalid.

Application: WinAudit Freeware v3.0
Error Type: System
Error Number: 2001
Location: OdbcExportDialog::ShowAdminDialog
Details: MySqlDriver=NULL

Obviously I have MySQL 5.6 Up&Running on the same machine, the ODBC driver (working, test succesfull).
Can You help me ?!?
P.S. win 7 x64 SP1 Latest patches and the Database Export "Drop Down" menu is empty.
Thank You in advance.

Solved 'cause of ODBC Manager pointing to 32bit instead of 64
http://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation-binary-windows.html

All reports seem to have data but not Automatic Update Status

Red.
Coordinator
Jun 16, 2014 at 12:29 PM
Edited Jun 17, 2014 at 9:00 AM
Hi RedErik,

I overslept boss, it won't happen again, honest. I've set the alarm clock (e-mail notifications). Replies should be a bit more timely from now on.

Good, it looks like you sorted the ODBC issue. For the automatic updates, I just posted a bug-fix release (v3.0.8) it should be fine now. If there any other problems let me know.

If you get that I'm-being-ignored feeling again, go to http://www.parmavex.co.uk/contact.php and put WinAudit in the subject.

oldbury
Jun 20, 2014 at 7:44 AM
Hi Olbury,
thank you for your answer.
By the way, I have a couple of problems:

1) The report format is correct and present but is always empty (every report). No error in export function

2) It would be fine to have a checkbox to remember the database password and when I open the export functionality
or database task, the popup populate the server name field with "localhost via TCP/IP" and I have always to delete
"via TCP/IP" to correctly connect.

Regards.

Red.
Coordinator
Jun 20, 2014 at 1:31 PM
Hi Red

always empty (every report)....
WinAudit has a logger, on the menu select Help -> Start Logging. Show the Admin dialog, then run the report. Close the dialog then go to the logger tab. Near the end of the messages, you should see the ODBC SqlExecuteDirect statement. Do you see any errors or warnings? If not, run that SQL statement in your favourite UI against the database, are you getting records back?

Password....
Here we are just following recommended development guidelines for password managment, see:
http://msdn.microsoft.com/en-gb/library/windows/desktop/ms717799%28v=vs.85%29.aspx
In particular, "because storing passwords and encryption keys in a software system can never be completely secure, it is recommended that they not be stored in a software system", so that's what WinAudit does. In all cases, the dialog prompt for credentials is created by the database's ODBC driver. So WinAudit has no immediate access to the password. Additionally, the ODBC interface provisions for the the calling process not to have a password so it seemed reasonable to follow that design as well. Of course, recommendations are just that, in fact this point is mentioned later in the document. So WinAudit adopts a middle ground, while the dialog is showing you do not need to re-enter a password to perform multiple operations. Once closed, the ODBC driver will prompt you for a new password on the next DB operation.

localhost via TCP/IP....
Yes, that really irritating, but its the MySQL ODBC itself that populating that text field and its alway appending "via TCP/IP" when it shows its connection dialog. This happend regardless of whatever data the calling process passes in to the ODBC driver. This was looked at a while ago, but a fix wasn't found. Other databses ODBC drivers do not do this. Suggestions for a fix/workaround welcome.

Oldbury
Jun 20, 2014 at 2:53 PM
Hi Oldbury,

From the logger:
2014-06-20 16:42:50 Information Application 0 Application name : WinAudit Freeware v3.0.8
2014-06-20 16:42:50 Information Application 0 Application version : 3.0.8.0
2014-06-20 16:42:50 Information Application 0 Executable Path : D:\Download\WinAudit\WinAudit 3.0.8.exe
2014-06-20 16:42:50 Information Application 0 Time stamp : 2014-06-20 16:42:50
2014-06-20 16:42:50 Information Application 0 Executable's MD5 : 92ADE3B6212B1E6EC3EE3A140CBF80AC
2014-06-20 16:42:50 Information Application 0 ANSI code-page identifier: 1252
2014-06-20 16:42:50 Information Application 0 User default language ID : 0x0409
2014-06-20 16:42:50 Information Application 0 Operating system version : 6.1.7601
2014-06-20 16:42:50 Information Application 0 Operating system edition : Enterprise Edition
2014-06-20 16:42:50 Information Application 0 Service pack version : 1.0
2014-06-20 16:42:50 Information Application 0 Product suite : 0x0100
2014-06-20 16:42:50 Information Application 0 Product type : 0x01
2014-06-20 16:42:50 Information Application 0 Product type (Vista+) : 0x00000004
2014-06-20 16:42:50 Information Application 0 Administrator : Yes
2014-06-20 16:42:50 Information Application 0 Processors (logical) : 8
2014-06-20 16:42:50 Information Application 0 Processor architecture : 0
2014-06-20 16:42:50 Information Application 0 Active processor mask : 0000000000000000000000000000000000000000000000000000000011111111
2014-06-20 16:42:50 Information Application 0 64-bit processor : Yes
2014-06-20 16:42:50 Information Application 0 Emulating 32-bit (WOW64) : Yes
2014-06-20 16:42:50 Information Application 0 Pre-install environment : No
2014-06-20 16:42:50 Information Application 0 Terminal services client : No
2014-06-20 16:42:50 Information Application 0 Remotely controlled : No
2014-06-20 16:42:50 Information Application 0 Session name : Console
2014-06-20 16:42:50 Information Application 0 Executable on drive type : Fixed
2014-06-20 16:42:58 Information Application 0 SMBIOS table length : 2374
2014-06-20 16:42:58 Information Application 0 SMBIOS major version : 2
2014-06-20 16:42:58 Information Application 0 SMBIOS minor version : 6
2014-06-20 16:42:58 Information Application 0 SMBIOS BCD/DMI Revision: 38
2014-06-20 16:42:58 Information Application 0 Connecting to WMI namespace 'root\cimv2'.
2014-06-20 16:42:58 Warning System 2 RegOpenKeyEx for 'Software\Parmavex\WinAudit' in 'Registry::GetStringValue'. The system cannot find the file specified.
2014-06-20 16:42:58 Information Application 0 Invalid WinAuditGUID ''.
2014-06-20 16:43:03 Information Application 0 In connection string: 'DRIVER={MySQL ODBC 5.3 Unicode Driver};SERVER=localhost via TCP/IP;DATABASE=audit;OPTION=1048579;UID=root;'
2014-06-20 16:43:14 Information Application 0 Completion connection string (-PWD): 'Driver=MySQL ODBC 5.3 Unicode Driver;SERVER=localhost;UID=root;PWD=JohnLuke68;DATABASE=audit;PORT=3306;FOUND_ROWS=1;NO_CACHE=1Driver=MySQL ODBC 5.3 Unicode Driver;SERVER=localhost;UID=root;DATABASE=audit;PORT=3306;FOUND_ROWS=1;NO_CACHE=1;'.
2014-06-20 16:43:14 Information Application 0 DBMS Name : 'MySQL'.
2014-06-20 16:43:14 Information Application 0 DBMS Version : '5.6.14-log'.
2014-06-20 16:43:14 Information Application 0 Driver Mgr. Ver.: '03.80.7601.0000'.
2014-06-20 16:43:14 Information Application 0 Driver Name : 'myodbc5w.dll'.
2014-06-20 16:43:14 Information Application 0 Driver Version : '05.03.0002'.
2014-06-20 16:43:14 Information Application 0 ODBC Version : '03.80.0000'.
2014-06-20 16:43:14 Information Application 0 Data Source Name: ''.
2014-06-20 16:43:14 Information Application 0 Server Name : 'localhost via TCP/IP'.
2014-06-20 16:43:14 Information Application 0 Database Name : 'audit'.
2014-06-20 16:43:14 Information Application 0 User Name : 'root'.
2014-06-20 16:43:14 Information Application 0 Odbc::ExecDirect: 'SELECT Computer_Master.Computer_Name, Audit_Data.Item_12 AS Processor, Audit_Data.Item_13 AS Memory_MB, Audit_Data.Item_14 AS Size_Bytes, Audit_Data.Item_15 AS Display FROM Computer_Master INNER JOIN Audit_Data ON Computer_Master.Last_Audit_ID = Audit_Data.Audit_ID WHERE Audit_Data.Category_ID = 300 ORDER BY ( Computer_Master.Computer_Name )'
2014-06-20 16:43:18 Information Application 0 Disconnecting from database.


from a MySQL query:
16:50:30 SELECT Computer_Master.Computer_Name, Audit_Data.Item_12 AS Processor, Audit_Data.Item_13 AS Memory_MB, Audit_Data.Item_14 AS Size_Bytes, Audit_Data.Item_15 AS Display FROM Computer_Master INNER JOIN Audit_Data ON Computer_Master.Last_Audit_ID = Audit_Data.Audit_ID WHERE Audit_Data.Category_ID = 300 ORDER BY ( Computer_Master.Computer_Name ) LIMIT 0, 1000 1 row(s) returned 0.000 sec / 0.000 sec

so it's returned my machine name without data.
why checking the registry if software is portable and not installed ?!?

Anyway, no data !! :-(

Password... I understand but the software is standalone and local so.. but I understand.

Localhost via TCP/IP... I understand :-)

Red.
Coordinator
Jun 20, 2014 at 3:48 PM
Hi Red,

WinAudit is standalone so it does not write to the registry but it is stilll allowed to read from it. When posting records to the database, a check is made to see if the computer is already know to the DB. Usually the UUID stored in the SMBIOS is good enough. However, some older machines or low end computer manufactures do not follow the publish standard and re-use UUID's or use all seros etc. To workaround this, WinAudit can generated a UUID( Help->Create GUID). This identifier, "WinAuditGUID", has precedence over all other identifiers. The admin needs to save this in the registry as WinAudit won't write it. This is also useful in the event the OS is re-installed as the admin can put back the WinAuditGUID to maintain a continous history.

Clearly MySQL returned a row. I'm not sure why you are not seeing anything at the UI. The report format is WordPad (RTF), perhaps it is malformed. On the report dialog, click "Copy" then paste into WordPad. Put it somewhere I can download it or send to w_i_n_a_u_d_i_t_@p_a_r_m_a_v_e_x_.c_o._u_k without the underscrores.

Oldbury
Jun 30, 2014 at 2:35 PM
Hi Oldbury,
it's working fine now. The trick was to recreate the database with ANSI driver instead of Unicode.
The Access DB is working too.

Thank You for your time.

regards.

Red.