Device crashing
w.sm...@gmail.com
days the GooSync program (3.0.0.0) crashes my Palm and it will enter a
loop of restart. The only to stop is a hard reset, losing all my data.
What can I do?
Stuart - GooSync Support
Does this crash occur during a sync or when the GooSync client is
opened?
If it's during the sync please provide your GooSync username and we'll
get the log files checked.
w.sm...@gmail.com
once it happened when I choose "Clean up deleted records" (hoping of
of course that this would rather solve the problem).
My GooSync username is wsmout
Thanks for answering anyway; in case this works you've got a new
customer...
On 6 mrt, 15:31, "Stuart - GooSync Support"
Stuart - GooSync Support
I've checked your log files and they do show some 511 errors caused
because the authentication with Google failed part way through a sync
(the reason for this was not returned by Google).
However, I wouldn't have expected this type of sync termination to
cause a crash. I would have just expected the device to show a sync
failed message.
One possibilty of this is that the version of your client differs from
the version of the device information we've got stored on the server.
The device information is still from version 2.9.9.6 of the GooSync
client (I'm assuming you upgraded to version 3 at some point).
I've made a change on the server to force the client to send the
latest device information to us. Please ensure you've got version 3 of
the GooSync client installed and run the sync again.
Let me know the results.
w.sm...@gmail.com
the "about"-screen of myGoosync-client and it aid "3.0.0.0.". I
started the sync, the device connected to internet and the counter
started, but then suddenly the screen became black and the loop of
automatic rebooting started. Only a hard reset could stop it.
Willem
On 7 mrt, 11:44, "Stuart - GooSync Support"
Steve S.
having exactly the same problem. (It just happened again). Mind you,
I now am quite good at dealing with hard resets. :) The first time
it happened, I ended up losing 45d worth of GCal data (the Palm
"updated" GCal with the blank data - I've learned since then).
Other than this one (big) SNAFU, I love the service - even enough to
pony up the 20 pounds! This is *exactly* what I need... save for the
reseting.
My GooSync user name is uriel1998. Please help!
On Mar 7, 12:18 pm, w.smou...@gmail.com wrote:
> Hi Stuart, it just happened again. Upon your information, I checkes
> the "about"-screen of myGoosync-client and it aid "3.0.0.0.". I
> started the sync, the device connected to internet and the counter
> started, but then suddenly the screen became black and the loop of
> automatic rebooting started. Only a hard reset could stop it.
> Willem
>
> On 7 mrt, 11:44, "Stuart - GooSync Support"
>
> <stu.etche...@googlemail.com> wrote:
> > Hi,
>
> > I've checked your log files and they do show some 511 errors caused
> > because the authentication with Google failed part way through a sync
> > (the reason for this was not returned by Google).
>
> > However, I wouldn't have expected this type of sync termination to
> > cause acrash. I would have just expected the device to show a sync
> > failed message.
>
> > One possibilty of this is that the version of your client differs from
> > the version of the device information we've got stored on the server.
> > The device information is still from version 2.9.9.6 of the GooSync
> > client (I'm assuming you upgraded to version 3 at some point).
>
> > I've made a change on the server to force the client to send the
> > latest device information to us. Please ensure you've got version 3 of
> > the GooSync client installed and run the sync again.
>
> > Let me know the results.
>
> > On Mar 6, 6:53 pm, w.smou...@gmail.com wrote:
>
> > > Usually it happens during a sync; never simply by opening the client;
> > > once it happened when I choose "Clean up deleted records" (hoping of
> > > of course that this would rather solve the problem).
> > > My GooSync username is wsmout
> > > Thanks for answering anyway; in case this works you've got a new
> > > customer...
>
> > > On 6 mrt, 15:31, "Stuart - GooSync Support"
>
> > > <stu.etche...@googlemail.com> wrote:
> > > > Hi,
>
> > > > Does thiscrashoccur during a sync or when the GooSync client is
> > > > opened?
>
> > > > If it's during the sync please provide your GooSync username and we'll
> > > > get the log files checked.
>
> > > > On Mar 6, 11:58 am, w.smou...@gmail.com wrote:
>
> > > > > I am usingPalmTXand synchronisation works fine. However: every few
> > > > > days the GooSync program (3.0.0.0) crashes myPalmand it will enter a
robm...@gmail.com
soon as I installed Goosync, did a sync, and when I performed a soft
reset to test, it entered the loop of death again.
user: maingray
Promising app, will wait until this is resolved.
r
On Mar 19, 6:10 pm, "Steve S." <Steven.S...@gmail.com> wrote:
> I'm glad to know it's not just me! I also am using aPalmTX, and am
> having exactly the same problem. (It just happened again). Mind you,
> I now am quite good at dealing with hard resets. :) The first time
> it happened, I ended up losing 45d worth of GCal data (thePalm
> "updated" GCal with the blank data - I've learned since then).
> Other than this one (big) SNAFU, I love the service - even enough to
> pony up the 20 pounds! This is *exactly* what I need... save for the
> reseting.
>
> MyGooSyncuser name is uriel1998. Please help!
>
> On Mar 7, 12:18 pm, w.smou...@gmail.com wrote:
>
> > Hi Stuart, it just happened again. Upon your information, I checkes
> > the "about"-screen of myGoosync-client and it aid "3.0.0.0.". I
> > started the sync, the device connected to internet and the counter
> > started, but then suddenly the screen became black and the loop of
> > automatic rebooting started. Only a hardresetcould stop it.
> > Willem
>
> > On 7 mrt, 11:44, "Stuart -GooSyncSupport"
>
> > <stu.etche...@googlemail.com> wrote:
> > > Hi,
>
> > > I've checked your log files and they do show some 511 errors caused
> > > because the authentication with Google failed part way through a sync
> > > (the reason for this was not returned by Google).
>
> > > However, I wouldn't have expected this type of sync termination to
> > > cause acrash. I would have just expected the device to show a sync
> > > failed message.
>
> > > One possibilty of this is that the version of your client differs from
> > > the version of the device information we've got stored on the server.
> > > The device information is still from version 2.9.9.6 of theGooSync
> > > client (I'm assuming you upgraded to version 3 at some point).
>
> > > I've made a change on the server to force the client to send the
> > > latest device information to us. Please ensure you've got version 3 of
> > > theGooSyncclient installed and run the sync again.
>
> > > Let me know the results.
>
> > > On Mar 6, 6:53 pm, w.smou...@gmail.com wrote:
>
> > > > Usually it happens during a sync; never simply by opening the client;
> > > > once it happened when I choose "Clean up deleted records" (hoping of
> > > > of course that this would rather solve the problem).
> > > > MyGooSyncusername is wsmout
> > > > Thanks for answering anyway; in case this works you've got a new
> > > > customer...
>
> > > > On 6 mrt, 15:31, "Stuart -GooSyncSupport"
>
> > > > <stu.etche...@googlemail.com> wrote:
> > > > > Hi,
>
> > > > > Does thiscrashoccur during a sync or when theGooSyncclient is
> > > > > opened?
>
> > > > > If it's during the sync please provide yourGooSyncusername and we'll
> > > > > get the log files checked.
>
> > > > > On Mar 6, 11:58 am, w.smou...@gmail.com wrote:
>
> > > > > > I am usingPalmTXand synchronisation works fine. However: every few
> > > > > > days theGooSyncprogram (3.0.0.0) crashes myPalmand it will enter a
> > > > > > loop of restart. The only to stop is a hardreset, losing all my data.
> > > > > > What can I do?
Stuart - GooSync Support
I've checked your log files but they just show that the sync process
completed successfully.
I've sent a message to the client developers to get their input on
what may be causing this reset to occur.
Steven Saus
a sync at the time. It seems to happen after a period of use AFTER
syncing.
I also was NOT updating/syncing/purging with the hotsync calendar;
could too many events be the cause?
Again, the behavior: sudden looping resets. I was able to stop the
loops with a warm reboot, but wireless was disabled. I tried to purge
old events through goosync, and it went into an loop that required a
hard reset.
But, on the plus side, I'm a LOT better about backing stuff up now.
--
Steven Saus http://surge.ods.org
"When the facts change, I change my mind. What do you do, sir?" -John
Maynard Keynes
Steve S.
morning. I had had syncing off entirely, but in the thought that
hotsyncing it might help purge deleted records, I turned it back on.
This is not the first sync since then - but it *is* the first sync
since then when I had deleted records. Here's the HotSync log:
-- Calendar
- Could not read the next handheld record.
Please check your connections and try again.
- Could not purge the deleted records on the handheld.
Please check your connections and try again.
- Some PC records were not copied to the handheld. Your handheld may
be full. To correct this situation, delete some records and perform a
HotSync operation again.
Desktop = 57, Handheld = 0
Calendar synchronization failed
The device went pooft *during* sync. A warm boot brought it back
enough to hotsync it again (no error this time, oddly), though the
WiFi was still toasty, so a total reset was needed. Attempting to
purge deleted records with GooSync also crashed the device.
Everything seems to point towards some way that GooSync interfaces
with the Palm T|X calendar *database*, rather than an error/bug/memory
leak in the GooSync app itself.
On Mar 28, 9:18 pm, "Steven Saus" <steven.s...@gmail.com> wrote:
> I just had it happen again this morning - though I oddly wasn't doing
> a sync at the time. It seems to happen after a period of use AFTER
> syncing.
>
> I also was NOT updating/syncing/purging with the hotsync calendar;
> could too many events be the cause?
>
> Again, the behavior: sudden looping resets. I was able to stop the
> loops with a warm reboot, but wireless was disabled. I tried to purge
> old events through goosync, and it went into an loop that required a
> hard reset.
>
> But, on the plus side, I'm a LOT better about backing stuff up now.
>
> On 3/26/07, Stuart - GooSync Support <stu.etche...@googlemail.com> wrote:
>
>
>
>
>
> > Hi,
>
daka...@gmail.com
TX too. It has caused loss of data, much inconvienence and
aggravation. I love the product and have shelled out the bucks to
Goosync but I don't think I can put Goosync back on my TX until
something changes...I guess its money down the drain...
> > Maynard Keynes- Hide quoted text -
>
> - Show quoted text -
Stuart - GooSync Support
We updated the Palm GooSync client at the end of last week that should
help with these crashing issues.
You can update to release 3.0.1.2 of the Palm client by either using
the "Check for updates" feature within your existing client or by
downloading and reinstalling the client available at
http://www.goosync.com/PalmClientInstall.aspx.
nsel...@gmail.com
new TX. I just subscribed and have really been looking forward to
syncing with my Google calendar (one of the main reasons I bought the
TX to replace my old Sony Clie). I've seen several instances of
infinitely looping resets, with a hard reset seemingly the only
solution.
On Apr 10, 4:45 am, "Stuart - GooSync Support"
<stu.etche...@googlemail.com> wrote:
> Hi,
>
> We updated thePalmGooSync client at the end of last week that should
> help with these crashing issues.
>
> You can update to release 3.0.1.2 of thePalmclient by either using
> the "Check for updates" feature within your existing client or by
> downloading and reinstalling the client available athttp://www.goosync.com/PalmClientInstall.aspx.
>
> On Apr 5, 11:18 pm, dakai...@gmail.com wrote:
>
> > Just want to report that this SAME EXACT behavior happening here on my
> > TX too. It has caused loss of data, much inconvienence and
> > aggravation. I love the product and have shelled out the bucks to
> > Goosync but I don't think I can put Goosync back on my TX until
> > something changes...I guess its money down the drain...
>
> > On Mar 30, 6:52 am, "Steve S." <Steven.S...@gmail.com> wrote:
>
> > > I had a loopingcrashwhen it was trying to sync Calendar this
> > > morning. I had had syncing off entirely, but in the thought that
> > > hotsyncing it might help purge deleted records, I turned it back on.
> > > This is not the first sync since then - but it *is* the first sync
> > > since then when I had deleted records. Here's the HotSync log:
>
> > > -- Calendar
> > > - Could not read the next handheld record.
> > > Please check your connections and try again.
> > > - Could not purge the deleted records on the handheld.
> > > Please check your connections and try again.
> > > - Some PC records were not copied to the handheld. Your handheld may
> > > be full. To correct this situation, delete some records and perform a
> > > HotSync operation again.
> > > Desktop = 57, Handheld = 0
> > > Calendar synchronization failed
>
> > > The device went pooft *during* sync. A warm boot brought it back
> > > enough to hotsync it again (no error this time, oddly), though the
> > > WiFi was still toasty, so a total reset was needed. Attempting to
> > > purge deleted records with GooSync also crashed the device.
>
> > > Everything seems to point towards some way that GooSync interfaces
> > > with thePalmT|X calendar *database*, rather than an error/bug/memory
Stuart - GooSync Support
Please provide me with your GooSync username and we'll investigate
these issues.
w.sm...@gmail.com
I have installed the new client, given it some time to test it and I
am happy to say that it works smoothly now. That is great!
Maybe I should add what happened to me when I installed the new
client. I installed it, thought it might be wise to reboot and then
the repeated crashing started again! But upon re-installing,
everything was correct and has remained so ever since. So in a way it
seems that all remnant of the old client needs to be deleted before it
is safe.
Anyhow, it is good to meet developpers that really listened to
customers.
Willem
On 10 apr, 11:45, "Stuart - GooSync Support"
<stu.etche...@googlemail.com> wrote:
> Hi,
>
Maingray
crashing older version?
r
w.sm...@gmail.com
On 26 apr, 13:09, Maingray <robma...@gmail.com> wrote:
> You mean you re-installed the new version after a hard reset of the
> crashing older version?
>
> r
>
Gary A
experimentation, I believe that I have identified the source of the
problem.
It's seems that when the GooSync client deletes entries from the
calendar on the TX, it leaves the database in a state that causes a
crash on the next system restart. The problem is hard to identify
because the restart loop can take place a long time after the Calendar
database is modified. Once in the restart loop, the only way to get
out is to replace the CalendarDB-PDat database. Typically, this is
accomplished with a hard reset.
Here is my workaround until the problem is resolved by Toffa. It
requires an SD Card with about 100MB of free space.
Preparation
1) Install NVBackup (http://www.freewarepalm.com/utilities/
nvbackup.shtml) to the \Palm\Launcher directory of your SD card
2) Use NVBackup to perform a full backup of your TX, (call it Full
Backup)
3) Do a hard reset
4) If you don't use Calendar's default categories, make your category
changes at this time
5) Launch NVBackup from your SD Card
6) Use NVBackup to perform another backup of your TX (call it Clean
Calendar)
7) Use NVBackup's selective restore feature to restore everything from
the Full Backup, except CalendarDB-PDat
8) Use GooSync to reload your palm
If you get into a reset loop, do the following
1) Do a warm reset
2) Use NVBackup to selectively restore CalendarDB-PDat from your
"Clean Calendar" backup
3) Use GooSync to reload your palm
If you want to save some space you can delete all of the Clean
Calendar backup files on your SD Card, except CalendarDB-PDat and %
%Comment.txt. Backup are found in \Palm\Programs\NVBackup
I am a big fan of the GooSync product. Hopefully this will help
alleviate my one source of frustration.
Gary
Stuart - GooSync Support
Can you confirm you are using release 3.0.1.1 (or higher) of the Palm
GooSync client?
Maingray
new update of Goosync before I aw this post, and it again entered the
loop of death a day or so later. I *really* want to use this program,
but until this is resolved, I can't live with the reset potential.
R
Gary A
I am using version 3.0.1.2.
Stuart - GooSync Support
I'll contact the client developers again and see if they can offer any
more assistance.
w.sm...@gmail.com
this i just to confirm that the system has fallen back to its old sins
again. On April 26th I told you there were no more problems but a few
weeks later they returned, regularly causing the abominous loop of
death...
Thanks for looking after it,
Willem
On 14 mei, 16:05, Stuart - GooSync Support
Maingray
loop of death. Maybe goosync should buy a T|X for testing?
Stuart - GooSync Support
Just to make you aware that the Palm client has been updated to
version 3.0.2.1. This can be downloaded from
http://www.goosync.com/downloads/GooSyncPalmClient.zip
The client developers suggest that when updating to this new release
(from a version that was causing problems) you should use the "Cleanup
deleted records" option within the client and then perform a Reload
Device sync.
This will ensure that the Palm calendar database is recreated
correctly.
On Jun 8, 11:56 am, Maingray <robma...@gmail.com> wrote:
> Ditto, I had used the most recent client version and it re-did the
> loop of death. Maybe goosync should buy a T|X for testing?
>