I got this error in emplode while syncing via ethernet:
Synchronise failed while rebuilding database.
An existing connection was forcibly closed by the remote host (error 0x80072746)

And under details:
Task: Initialising
Warning:Meltdown could not be syncronised., An existing connection was forcibly closed by the remote host (error 0x80072746)

Meltdown was the last track syncing from the album I had added. The empeg was still moving the sync logo around for 10 mins after that, and had the drive spun up, but no activity according to the icon on the display. I closed emplode and reopened it, and it would see the empeg, but gave it a question mark and wou;dn't reconnect. Once I powercycled, it rebuilt the database on the player during boot, then the next sync it did an fschk and rebuilt the database. Once I got back in, I checked the album, and Meltdown was not there. Resyncing with just Meltdown worked fine, and the album overall seems fine.

Also had some problems concerning the retrieval of the database... Don't know what caused it, don't know what solved it, but I noticed the network settings in the about menu were gone! There was a gap between serial number and owner's details. Very, very strange...

Just got this same error, but with the test "Syncronise failed while rebuilding database" instead of the warning I got last time.

Any word at all on this one?

Wee...

Just rebooted the empeg, reconencted, and got "Download failed while checking media
Read on socket failed (error 0x8004003d)"

I'm going to try some USB syncs, it seems these are all network related.

(Yet another person increasing post count replying to his own messages, oh well...)

I think I have all of my sync errors worked out. It's the noisy network the empeg sits on here at work. I tried syncing several more things to get very similar errors as above almost all the time. Putting the empeg and laptop on a hub of their own, problem went away. I'll test it again with the next beta version, and see if it has helped any.

This is still important. I would think they'd want to make sure it synchs on impacted networks, too.

This one seems to be fixed with Beta 7. I just put 280 megs of stuff on the empeg across the same network, and not a single glitch. Before, I could barley get 50 done.

I just got this on 2.0B11. It had done about 13GB. I blew away my setup earlier as it was in a state, but initially it had done all 17gb without error.

Ditto. Just got this last night while syncing about 300 MB. It gave me a sync error while rebuilding, I think.

I suggest that people who are seeing this regularly keep a serial terminal open to the player, where possible. This error is generally caused by the player crashing. If it does, grab the output and send it to [email protected], making sure to note which version of the software (the full version, please) this is happening with.

We can then cross-reference the stack trace with the map file generated when we build the release and see what's going bang, and why.

I see this now everytime I try to synch in stage 'Removing deleted items' (even though I didn't delete anything...I just added playlists).
Next time I try to synch, it always starts to check disc integrity... I'm logging that right now.

(Mark 2a, 2.00b11, Hijack v253)

I'm a new empeg user and I to had had the same problem when dumping 20Gb to the player (a ver 2a). Like others I found the solution was to remove hijack.

Actually let me clarify my last comment. I'm using V2.0-b11 and have seen two different issues when syncing anything more then one or two Mb. First with hijack loaded the transfer failes while files are being downloaded. The empeg appears to die and the 'syncing' icon stops moving. This requires a power off/on to clear the isses and results in a corrupt database and happens with both Ethernet and USB.

I thought removing hijack cleared the problem but I found out last night that was not correct. In this case the download works fine but the empeg does not re-boot properly when requested to do so by emplode (It just seems to power off - blue light pulsing). Powering off and on at the correct time causes the sync to complete without errors. I only tried this over Ethernet.

I'm still trying to sort out what I want on my empeg and I have a tendancy to wipe the unit and download everything again so this is kind of problem. In due course I hope the collection will become pretty static. I expect to update my collection (again) later this week so I will try debuging using hyperterm and older firmware to see what happens.

Do consumer images use the serial port for debug messages or is it just the development images?

The problem where the player does not properly reboot itself during the synch is a known bug and will be fixed in the next release.

Regarding the "it won't synch when I'm using hijack" problem (which is a separate problem I believe)... Are you using ethernet or USB?

If you are using ethernet, is there a chance that you've got the Nimda or Code Red viruses running on your machine/network by any chance? Those hammer web-enabled ethernet devices pretty hard and might be responsible for killing an ethernet synch. You see, one of Hijack's features is to web-enable the car player. If Nimda or Code Red were present, a synch without hijack might behave normally, while a synch with hijack might be overwhelmed by port-80-requests.

This is just a wild guess. But I can't think of any other reason that adding Hijack would result in a synch failure.

It happens with both USB and Ethernet. There are some other threads on the same subject elsewhere on the BBS which suggest syncing fails with Hijack loaded due to insufficient free memory.

I guess most people don't see this as there empegs are pretty static - me I'm a newbie and still have a lot of work to do not least because I created my collection back before ID3 was supported by ripping programs. I would re-rip except I rip tracks and not albums and it took weeks last time to identify what to rip. Guess I'm fussy about what I listen too :-)