Synchronize Failed..., error 0x80072736

Posted by: maczrool

Synchronize Failed..., error 0x80072736 - 12/10/2009 15:26

I'm getting this error whenever I try to synch using Emplode on my MK2A with 2.0, Hijack 5.08, 2 100 GB drives and 32 MB of RAM. The error reads "Synchronize failed while writing player configuration. An operation was attempted on something that is not a socket. (error 0x80072736)." Anyone know what this error means and how to get it to stop appearing?

My drives have roughly 120 GB of files on them. I can synch if I don't make any changes, but as soon as I do, it gets stuck during the second connecting to player step and eventually displays the above error, trashing the database in the process and introducing the building database message at boot.

Thanks,
Stu
Posted by: tfabris

Re: Synchronize Failed..., error 0x80072736 - 12/10/2009 19:44

Any chance your config.ini is messed up? Like, it's huge or something? Or you've been editing the file recently?
Posted by: maczrool

Re: Synchronize Failed..., error 0x80072736 - 12/10/2009 21:48

Hey Tony,

I've not done anything with it for years, but I was thinking about the config.ini file as well. Is there anyway to return it to default values other than going in manually and changing everything back? Will copying from a working machine and pasting into the suspect one fully replace the file?

Thanks,
Stu
Posted by: tfabris

Re: Synchronize Failed..., error 0x80072736 - 12/10/2009 22:03

I'm not worried about the values within the config.ini file being wrong, I'm only worried that the file itself is corrupted somehow, for instance, like it could get corrupted with 2.0 Beta 11.

Look at the file in Emplode and see if looks right. If it looks right, there's no need to overwrite it with anything. If you feel like overwriting it, yes you can copy one over from another player or just edit it whole-hog in Emplode.

Posted by: maczrool

Re: Synchronize Failed..., error 0x80072736 - 12/10/2009 22:24

I just had a look and although everything looked ok, to be safe I copied it from another unit that has no sync problems, but I still get the error. It spends about two minutes writing the player configuration, then I get the error, the success chime and Emplode crashes follwed by the endless building music database message (until I laboriously repair it).

Ugh!
Stu
Posted by: Roger

Re: Synchronize Failed..., error 0x80072736 - 13/10/2009 06:03

Originally Posted By: maczrool
An operation was attempted on something that is not a socket. (error 0x80072736)." Anyone know what this error means and how to get it to stop appearing?


The error comes from the Windows end and simply means that the socket was closed, probably by the player crashing and rebooting during the synchronisation. That, unfortunately, is all the error message can tell us.

To figure out what's actually happening, you'd need to get a serial log from the player during the sync process.
Posted by: maczrool

Re: Synchronize Failed..., error 0x80072736 - 13/10/2009 17:13

Thanks Roger.

There are some errors but I'm not sure how to address them. Here is the serial capture following connection to Emplode:

spindown_chunk_cache_runner.cpp: 294:Filling up space (9)
spindown_chunk_cache_runner.cpp: 294:Filling up space (9)
spindown_chunk_cache_runner.cpp: 294:Filling up space (9)
Adding Swap: 16028k swap-space (priority -1)
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda4 is mounted.
e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hdc4 is mounted.
! playerdb.cpp : 182:Failed to build dynamic database (status=0xc004401a).
Restored terminal settings
Remounting first music partition read-only
Remounting second music partition read-only
Restart code received
Starting player
Timezone: Atlantic/Bermuda

Hijack: intercepting config.ini

player.cpp : 385:empeg-car 2.00 2003/04/01.
! tags.cpp : 61:Failed to open tags (0xc0041002).


Any ideas?
Stu
Posted by: maczrool

Re: Synchronize Failed..., error 0x80072736 - 14/10/2009 15:04

Searching around, it looks like the problem lies in the error "Failed to build dynamic database (status=0xc004401a)" which appears can only be corrected by rebuilding the drives. I fear though that the error may return once the database starts to grow.

Is there any other way to make this work?

Stu
Posted by: mlord

Re: Synchronize Failed..., error 0x80072736 - 15/10/2009 00:08

Delete the database files and try a manual database build.

Details of that are in the FAQ, somewhere.. wink
Posted by: maczrool

Re: Synchronize Failed..., error 0x80072736 - 15/10/2009 12:34

Quote:
Delete the database files and try a manual database build.


Thanks Mark. Unfortunately, I've done that numerous times but it only lasts until I sync the unit again. Then the error comes right back. The only way others have fixed this is start over with a new build, which I think is a pretty poor solution.

Stu
Posted by: peter

Re: Synchronize Failed..., error 0x80072736 - 15/10/2009 12:46

How many fids have you got (i.e. what's the highest one)? Does this player rely on set_empeg_max_fid, and, if so, have you reapplied it since you last used a full upgrade file? (Or does Hijack incorporate set_empeg_max_fid these days?)

Peter
Posted by: maczrool

Re: Synchronize Failed..., error 0x80072736 - 15/10/2009 15:29

The highest FID is 87050 and there are 28,864 files. The player does not have set_empeg_max_fid applied to the best of my knowledge.

Stu
Posted by: tman

Re: Synchronize Failed..., error 0x80072736 - 15/10/2009 19:35

Originally Posted By: maczrool
The highest FID is 87050 and there are 28,864 files. The player does not have set_empeg_max_fid applied to the best of my knowledge.

I think the stock limit was around 21000?
Posted by: maczrool

Re: Synchronize Failed..., error 0x80072736 - 15/10/2009 23:07

I decided to try Mark's FID hack and it worked! I've had two consecutive syncs without error. Since I have 32 MB of RAM to play with, is there anything I can do with it to further enhance things?

Thanks everyone,
Stu
Posted by: mlord

Re: Synchronize Failed..., error 0x80072736 - 16/10/2009 01:14

That's pretty much the best. One *could* fiddle with the partition tables, making the dynamic data partition larger and such. But it's probably not worth the incompatibility headache.

Cheers
Posted by: benjammin

Re: Synchronize Failed..., error 0x80072736 - 16/10/2009 04:47

as a sidenote,

UltraEdit works fine on Unix files.

The FAQ implied that UE needs a step to hexedit mode only while actually it can be used to directly edit the file in the native Unix/Linux format.

Cheers,

-Ben
Posted by: peter

Re: Synchronize Failed..., error 0x80072736 - 16/10/2009 16:51

Originally Posted By: tman
Originally Posted By: maczrool
The highest FID is 87050 and there are 28,864 files. The player does not have set_empeg_max_fid applied to the best of my knowledge.

I think the stock limit was around 21000?

28,672. So you've only just gone over it, which is why it's only just started failing. Using set_empeg_max_fid means you're good for (typically) up to 44,099.

Peter
Posted by: maczrool

Re: Synchronize Failed..., error 0x80072736 - 17/10/2009 13:01

Thanks again Peter. Tony, do you think you could refer to this thread in the FAQ as a solution to crashes during sync? I don't believe the set_empeg_max_fid fix is mentioned in the FAQ in association with this problem.

Thanks,
Stu
Posted by: tfabris

Re: Synchronize Failed..., error 0x80072736 - 17/10/2009 20:05

Added to this faq entry.
Posted by: peter

Re: Synchronize Failed..., error 0x80072736 - 18/10/2009 08:32

Originally Posted By: maczrool
Searching around, it looks like the problem lies in the error "Failed to build dynamic database (status=0xc004401a)" which appears can only be corrected by rebuilding the drives.

Looking back at those threads, it's very conspicuous that in the 2003 thread (user "cushman") I never figured out what was going on, even though in retrospect it was almost certainly the same thing that was going wrong in the 2005 thread (user "JeffreyB") as well as now for you. Mind you, I suppose that's the better way round: it'd be more embarrassing if I'd figured it out in 2003 but not 2005...

Peter