unregistered error (when running as service with local system account)

Support for Windows users
Post Reply
Mortyfar
Posts: 14
Joined: 04 Jun 2018, 09:47

unregistered error (when running as service with local system account)

Post by Mortyfar »

Hello

I just purchased a license a few days ago, and ran into a small issue.

I activated the license without any problems, in CMD.

When I run my script with filebot.exe everything works fine.
However, my script is setup to run in the background once a day using filebot.launcher.exe and that produces an unregistered message in the log file, and nothing is renamed?

I am using ver. 4.8.5 on Windows 10.

LOG file
https://anonymousfiles.io/Awus7W2y/

in the log you will see, that I ran the script 2 times, 1st with filebot.launcher.exe, and 2nd with filebot.exe.

Is there any logical explanation for this?
Thank you
User avatar
rednoah
The Source
Posts: 22995
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: unregistered error

Post by rednoah »

Please read this thread:
viewtopic.php?f=8&t=11234
:idea: Please read the FAQ and How to Request Help.
Mortyfar
Posts: 14
Joined: 04 Jun 2018, 09:47

Re: unregistered error (when running as service with local system account)

Post by Mortyfar »

Thank you very much, that solved it ;)
Had some issues with tasks not running on schedule, so I changed the user to system. Hopefully it will run on the next scheduled time.
User avatar
rednoah
The Source
Posts: 22995
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: unregistered error (when running as service with local system account)

Post by rednoah »

Well, not sure if system user works, since that one hasn't got the license installed either. You'll want to run the service as your user, same user you use normally, so that they share the same application data and installed license.
:idea: Please read the FAQ and How to Request Help.
Mortyfar
Posts: 14
Joined: 04 Jun 2018, 09:47

Re: unregistered error (when running as service with local system account)

Post by Mortyfar »

hehe yeah I changed it back from system to the user I'm logged in with, I see that wasn't very clear :)
Post Reply