Hi Erik, > On 2 Mar 2017, at 16:36, Erik Boström <erik.g.bost...@gmail.com> wrote: > > Thanks for you reply Panagoitis! > > > First thing that comes to mind is checking if timestamp used by nxlog is > > properly formatted. What happens if you run the query manually? > > How do you mean "manually"? We have ran the query from PowerShell > successfully. >> Our NXLog configuration: >> >> <Input ODBC> >> Module im_odbc >> Connectionstring dsn=DSNNAME;database=Databasename; >> SQL Select StartTime as id, AdminId from [Databasename].[view].[view] Where >> StartTime > ? >> Savepos TRUE >> IdIsTimestamp TRUE >> </Input> >> >> AdminId is an Int datatype >> StartTime is a datetime. Example value is 2016-09-16 08:42:45.433 > > Does this datetime format come from nxlog debug log? > > The DateTime format comes from MS SQL Server. Displayed in Editor window. The > NXLog debug log only contains the error message "Invalid precision value". > > NXLog is successful when we change the query and use AdminId as id. > > Any more hints what can be wrong?
Not sure yet. Which version of nxlog are you using? > / Erik > > […] -- Panagiotis (atmosx) Atmatzidis email: a...@convalesco.org URL: http://www.convalesco.org GnuPG ID: 0x1A7BFEC5 gpg --keyserver pgp.mit.edu --recv-keys 1A7BFEC5 "Everyone thinks of changing the world, but no one thinks of changing himself.” - Leo Tolstoy
signature.asc
Description: Message signed with OpenPGP
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
