Hi,
I don't think that "what was fixed in 1795 has been unfixed in 1798", but by evidence you are still seeing an issue.

Generating new debug log + ELF would be useful to see what is going on on your side.

Thanks!

It appears that what was fixed in 1795 has been unfixed in 1798 and an additional bug was added.

Wireless syncing seems to crash the service again. Getting the same db locked and query error.

Wired syncing throws an error about timing out and restarting pc/device to fix it.. which so far as not.

I'll try to run the debugger later.

Hi mcow,

Well, it's not fixed exactly; the problem recurs. I can't say whether it's an MMW problem or not.

OK, if you can replicate, logs would be great

Thanks.

-Rusty

rusty wrote:Hi mcow,

If I understand correctly, you're saying that the originally reported issue has been fixed (i.e. MMA/MMW now consistently connect)

Well, it's not fixed exactly; the problem recurs. I can't say whether it's an MMW problem or not.

In the older bug, the problem seemed not to occur so long as MMW was not running when I put the system sleep. So I've made a habit of exiting MMW before putting the system to sleep. But that hasn't helped with the recent manifestation.

I'm pretty sure this isn't the same thing olivechicago is seeing; I don't get error boxes or crash indications, and MMW remains running. I just can't get a consistent network presence of the MMW server.

Right this instant, tho, it's working fine. :/

Hi,
thanks for the crash logs.
Based on it I was able to fix the reason for the crash as http://www.ventismedia.com/mantis/view.php?id=13302

The service crashed on closing and most probably caused that MM.DB remained locked for another MM instance (the database is locked SQL errors).
The crash should no longer happens in the next build 1796.

For now rebooting your computer should fix the issue.

Data submitted


Ticket ID #XSE-818-43206
log ID: LA8BRPKLPZ

Initiating the service seems to be a deal breaker.



That is the phones WiFi MAC.

I'll run the debugging stuff tomorrow.

So far, so good. Sync over WiFi has left 1795 stable so far.

I didn't install it as a service yet though. I'll do that next and see what happens.

Hi mcow,

If I understand correctly, you're saying that the originally reported issue has been fixed (i.e. MMA/MMW now consistently connect), but files are syncing unnecessarily. If so, I'll continue the discussion at http://www.mediamonkey.com/forum/viewto ... 21&t=83533

Olive Chicago,

Can you please try out build 1795 (to be posted in a few minutes), and send a debug log? See details at: url=http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

That'll give us the information needed to figure out why this is happening. Thanks.

-Rusty

I'm getting a lot of this too:




This path doesn't even exist


Rolling back to 1790, which never gave me a problem before did not fix it.

Seems stable until a remote device tries to sync... then it's crashing.

I uninstalled and reinstalled the service... same thing.

I've got the same problem. Started for me with 1791 I think.

The service crashes.

Faulting application name: MediaMonkey.exe, version: 4.1.12.1793, time stamp: 0x573643fc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x3540
Faulting application start time: 0x01d1b179dbe75bea
Faulting application path: C:\Program Files (x86)\MediaMonkey\MediaMonkey.exe
Faulting module path: unknown
Report Id: 48ba732e-58ea-40ea-9e1c-01099a8b56b4
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: MediaMonkey.exe, version: 4.1.12.1791, time stamp: 0x5730dd94
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x17a8
Faulting application start time: 0x01d1b16765df61b4
Faulting application path: C:\Program Files (x86)\MediaMonkey\MediaMonkey.exe
Faulting module path: unknown
Report Id: 29326988-4620-4403-8153-3c6d5954512a
Faulting package full name:
Faulting package-relative application ID:

After reading that bug, yes, I checked the firewall rules, and they all appeared in order.

After running build 1791, the firewall rules had changed, as described in that bug. When I tested again, I still did not have success, as I mentioned.

Running now, tho, the sync server is discoverable (and so I see the problem from http://www.mediamonkey.com/forum/viewto ... 21&t=83533 instead). Not sure what the discrepancy is.

Have you checked Firewall rules, do you see MMW in UPnP of MMA?

You know how to find me

I wondered if the fix for http://www.ventismedia.com/mantis/view.php?id=13261 in build 1791 would happen to fix this bug as well, but it did not.