• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 95 subscribers
  • Views 1740 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Process LogComponent issue in v6.1.3

Anton Akimov
over 6 years ago

Hello guys!

I was quite surprised finding out the LogComponent unable to write any logs into JobService logs file. No errors, but no logs either. I remember it performed pretty well.
Is there any special configuration for that? From my memories, just setting a value to "Message" varible, and for example "Warning" or 'Error" as EntryType was sufficient.

Just for information, using "AppData.Instance.RaiseMessage" call in a VB script, does the job.


Any ideas?

Best regards,

Parents
  • 0 over 6 years ago

    Hi Anton,

    My understanding is this only writes to the server's event log, not the job service log.

    Trevor

  • 0 over 6 years ago in reply to Trevor Pike

    Hi Trevor! And thank you!

    Do you know if there is any way to "redirect" log component to the jobservice output? (or may be it it could be done using an another component in process)?

    I would need to easily write logs into jobservice logs from a process, ideally without passing by a script.

    Best regards,

  • 0 over 6 years ago in reply to Anton Akimov

    The output cannot be redirected. But honestly, I didn't understand your use-case completely. The LogComponent would mean you already have a separate process step to log something. Why not replace this process step with a script component logging the message to the JobService log as described.

  • 0 over 6 years ago in reply to Markus Weiss-Ehlers

    Well, I completely agree with you Markus, it could also be done in this way (just as I described in my first message), as, for instance, for runing some SQL commands it could also be done by calling a VB script which would perform SQL using .Net....
    But, instead of this, in some "light" cases we would prefer a dedicated component which is a "HandleObjectComponent".
    Same thing for logs, in some cases, I need log some informations between my process steps easily (without going to the "script level"). And I remember having being able to do this using LogComponent. Thats why I've been quite surprised that it didn't worked this time.

Reply
  • 0 over 6 years ago in reply to Markus Weiss-Ehlers

    Well, I completely agree with you Markus, it could also be done in this way (just as I described in my first message), as, for instance, for runing some SQL commands it could also be done by calling a VB script which would perform SQL using .Net....
    But, instead of this, in some "light" cases we would prefer a dedicated component which is a "HandleObjectComponent".
    Same thing for logs, in some cases, I need log some informations between my process steps easily (without going to the "script level"). And I remember having being able to do this using LogComponent. Thats why I've been quite surprised that it didn't worked this time.

Children