Skip to main content
G
GL_107616944-Participant
4-Participant
October 2, 2023
Solved

Data logger problem

  • October 2, 2023
  • 2 replies
  • 4242 views

Dear Kepserver,

I'm enounter problem in data logger with error 

Date Time Level Source Event
02/10/2023 09:34:49 Error Data Logger Plug-in Unable to query recordset on Log Group 'Glass_Data'. Reason: sp_cursor: The value of the parameter 'value' is invalid.

 

I check the value which generated default and only rename the " value name " and not for the data type. can you help me which can cause error?

 

Best answer by aservetas

An Event Log message has been added to v6.14 to notify users if settings have not been applied when making changes in the Config.

 

-Andy

Andy Servetas
Principal Technical Support Engineer | Kepware Technologies

2 replies

V
24-Ruby III
VladimirN24-Ruby III
24-Ruby III
October 2, 2023

Take a look here:

S
SlidingDownhill12-Amethyst
12-Amethyst
October 2, 2023

Check that the database column is the same name and datatype you expect it to be in the Logger setup and that the source tag is still the same as datalogger is looking for. note that datalogger group has to be disabled to change parameters or they will not be saved (even though it appears they do - I wish KW would fix that with a notification of some type) 

A
aservetas15-MoonstoneAnswer
15-Moonstone
October 3, 2023

An Event Log message has been added to v6.14 to notify users if settings have not been applied when making changes in the Config.

 

-Andy

Andy Servetas
Principal Technical Support Engineer | Kepware Technologies

S
SlidingDownhill12-Amethyst
12-Amethyst
October 3, 2023

Hey Andy

Well that's good to hear - Its interesting to note that if I change the sources of the items in the log group, like deleting the tag in the PLC that they point to, it doesn't stop the logging of the entire group or even note it in the event log,

But if I then stop and start that group it wont allow a re-start because that tag can't be reached. That implies to me that it should be possible technologically to change log items while the logger is running but a conscious decision was made to check the tags at startup prevent the group from starting at all even though there seems on the surface to be no real reason to prevent the rest of the tags from logging and just note the bad tag like the devices do.  

 

Is it too much to ask just to allow changes while on-line and not prevent the entire group from logging for one (or more) bad tag?   Asking for a friend...

Terms & ConditionsCookie settingsAccessibility statement