Support

Hi there,

since this morning I have an issue with JoomlaPack Remote 2009_3. As soon as I execute it on my local machine, I get a message box: "01-Jan-00 is not a valid date". Once I click OK I get an access validation error, the main window is loaded, and then the screen gets filled up with the 01-Jan-00 and access validation message boxes.

Please let me know if you need more information to troubleshoot this.

My local machine is a Windows XP SP3 machine.

Thank-you for your support!

Regards Andrea.

Andrea,

This is not one that I recognize as a known problem with JP Remote 2009.3. Remote 2009.4 was released last week (beta), you might try that version.

I'll flag this for Nicholas too.

Dale

Hi Dale,

thank-you for your quick answer! I just downloaded and tried out with the version 2009_4 beta executable, and it gives the same issue.

Thank-you.

Rgds AG

I was afraid of that, that's why I flagged it for Nicholas this morning. My guess is that the bad date is in your JP Remote database. That stores your site setups and last backup date and time.

What language are you using? We have had problems in the past with some languages (French, I think) that use special characters in date names.

Dale

Dale: thank-you for your reply.

My PC has Windows XP SP3 with the standard US English locale installed. J! frontend in in Italian, and the backend is in US English.

Dale, could the issue be caused by a problem during a backup ? The day before yesterday I launched a backup from the backend. J! is installed on my notebook as well. The PC went to hibernation and the backup failed of course. I don't know if JP Remote has stopped working since that exact moment though.

Thanks.

Andrea.

Interesting. Go to the JoomlaPack Control Panel in the back end. This is a "magic" place. :D When you go to the Control Panel screen, JoomlaPack assumes that all backups should be aborted and any temporary working files deleted. It does an automatic cleanup.

I still think it is a bad date in your local JPR database. But it should handle the hibernation more gracefully than that.

Dale

Hi Dale, thanks.

I actually even made another backup now (successfully) from the backend. but that didn't solve.

I'd like to thank-you for your continued help.

Rgds AG

You guys are great, deleting the mentioned file solves the issue. THANK-YOU FOR THE SUPER FAST AND PROFESSIONAL SUPPORT !!

(donated).. ;)

Interestingly, I had unistalled and reinstalled JP remote 2009_3 several times with no luck. This means that the abovementioned file is not removed ? I haven't tried to unistall and reinstall the newest beta so I don't know (we have a little saying of: don't touch things that work :D ). It could be an idea to improve the detection of db corruptions into one of the next versions of JPRemote.

Keep up the good work guys - you're great.

Ciao, Andrea.

Andrea,

Thank you for the kind words, and the donation! :D

The jpremote.s3db file is not removed when you uninstall JP Remote. That allows you to upgrade without losing your site definitions. Re-entering one site is an irritation, if you have five or six, it is a pain. :D lol:

Dale

LOL :)

Maybe you can tell him to put a checkbox in the installer-uninstaller:

(X) Preserve JPRemote Sites info

AG

Yeah, I think that workaround would help as well.

Thanks again for the xtensive support.

Andrea.