ODBC connection: no data input into SQL DB...

[sfl33]

Hi folks,

i got the following situation:

Advanced NMEA Data Logger 2.7.3 build 526 (short reference ANMEADL)
Installed on a fully patched windows 7 x64, runs smoothly.

1 single configuration for port COM8 (USB GPS Device). No problem.

Data acquisition is perfect, GPS data logged into a local logfile on drive D:. So far perfectly.

Additionally ODBC configuration specified to only insert $GPRMC data into a SQL 2012 Express SP1 local database. Runs perfectly.

ANMEADL configured to run as a windows service, including option to allow interactive communication with the desktop/logged-on user activated (!!).

But now the problem:
--------------------
As long as i have the GUI opened and run (while the service is stopped), data insert into the SQL Database works perfectly.
But as soon as I close the GUI and start the service, there's no new data exported into the SQL Database, but still ANMEADL goes on protocolling into the local log-(txt)-file.

My assumption is that there's something wrong with the ANMEADL service selecting/reading the data export module (ODBC). Am i wrong? Any proposals or even solutions? Any help? why does the service not log into the SQL Database through the ODBC module...?

now please don't tell me that thats by design, that only the SQL Database Professional module is capable of doing so...

thanks for any advices!

sfl33, switzerland

[Arthur Grasin]

This problem is related with security on Windows 7. The service is running under another account name with other privileges. Please, the following:

1. Stop the service
2. Start the program as administrator (right click over the program icon and select "Run as administrator")
3. Verify your settings. It is possible that the program is not registered or not configured.
4. Start the service.

[sfl33]

Thanks very much, Arthur, for your reply!

Your hints didn't work out as they should, but it lead me to the conclusion.
The ANMEADL service needs to be run in the same user account context as
you use to configure the ANMEADL configuration. Its a bit strange, though
the ODBC connection is configured as system DSN, not user DSN.
But anyway, it works now! Hope this may help someone else...

Cheers - sfl33