For The Record - The rule-based scheduling suite (28 Viewers)

[Gixxer]

The PowerScheduler plugins should not be used (not on the client, and definitely not on the server). It's not compatible with the standard Windows-based suspend/resume For The Record uses.

wow thats a big step backwards !! I just got powerscheduler to work like i wanted

so what is the optimum solution when using for the record if I want my computer to go to sleep from 1am to 9am, wake up at 9am, and wake up if there is a FRT recording during the night?

 

[dvdfreak]

It's a surprise you never ran into problems before if you've been using PowerScheduler with For The Record all this time

What you need is a tool that supports and uses the standard suspend/resume in Windows. After a very quick google I turned up this e.g.: Auto PowerOn & ShutDown - Wake up your PC and Auto ShutDown, but I'm sure there are other alternatives that may even be much better than what I found with zero effort

 

[Gixxer]

I have not been using powerscheduler since this weekend.

Right, so i will have to set the timmings using an external tool.ok.

Initially i was going to use SetPower software which is free. lets see how it goes.


thanks

p.d. hope some day it would be possible to make this easier for the user and make FTR and powerscheduler compatibles.

 

[Gixxer]

dvdfreak thanks for your help. I have used Setpower SetPower - Power Management Software and i think its all working correctly now.

hope this post helps others with setting their system.

btw. i am now having trouble setting the email alert. i have setup FTR with exactly the same parameters and acronis home and in acronis everything works but in FTR when i press the button to send a test email, i get nothing. logs say...
02/04/2010 17:50:08 [Information][Mailer]: Se excedió el tiempo de espera de la operación.
means...waiting time for the operation was exceded.



also... in msn bot... i get this...

01/04/2010 9:02:27 [Information][MSN-bot]: 'net.tcp://localhost:49942/ForTheRecord/' not found, is the service running?

I have changed some ports to access webepg of ftr from the internet. but i dont htink it is related. any help??

thanks a lot

 

[dvdfreak]

If everything works except for sending a test mail, it really must be the mail settings somehow...

Remember that For The Record by default runs under the SYSTEM account, perhaps that's part of the explanation?

 

[Gixxer]

If everything works except for sending a test mail, it really must be the mail settings somehow...

Remember that For The Record by default runs under the SYSTEM account, perhaps that's part of the explanation?

I really dont know what to get from that.

As for the email problem, i have it setup exactly as acronis (all settings the same, including the security checkbox). Dont know why its not working.


As for the Bot, can you think why i am getting such error?

02/04/2010 18:01:53 [Information][MSN-bot]: MSN-bot thread started.
02/04/2010 18:01:53 [Information][MSN-bot]: Starting service.
02/04/2010 18:01:58 [Information][MSN-bot]: 'net.tcp://localhost:49942/ForTheRecord/' not found, is the service running?

what service name is exactly referring to?

 

[dvdfreak]

If that error is only once in the bot's log and it works otherwise it simply means it had to retry the connection to For The Record's core services.

 

[Gixxer]

If that error is only once in the bot's log and it works otherwise it simply means it had to retry the connection to For The Record's core services.

the bot does not get online as i cant find it connected in my other messenger account. so there must be something else going wrong. howerver i only get those 3 log lines...

02/04/2010 19:14:34 [Information][MSN-bot]: MSN-bot thread started.
02/04/2010 19:14:34 [Information][MSN-bot]: Starting service.
02/04/2010 19:14:40 [Information][MSN-bot]: 'net.tcp://localhost:49942/ForTheRecord/' not found, is the service running?

 

[dvdfreak]

It's indeed more likely there's an issue for your bot to log into the Windows Live network. That connection failure is likely to be ignored since your core services are running just fine, right?

You could also try to restart the bot service, does it then keep giving that error?

 

[Gixxer]

It's indeed more likely there's an issue for your bot to log into the Windows Live network. That connection failure is likely to be ignored since your core services are running just fine, right?

You could also try to restart the bot service, does it then keep giving that error?

the rest of FTR is working perfectly fine.
i have tried to restart computer and same problem
restart just the service and same problem.

sorry but dont know what extra info i can give you as logs dont say anything more. should i get a log line saying the bot was not able to connect? what else can i try?