by toyzrme » Wed May 08, 2013 10:14 pm
MMA connected to MMW only ONCE with 1609, NEVER with 1639.
Windows 7/x64, all the latest patches. On a Lenovo W510 w/12GB RAM.
MMW: 4.1.0.1636 & 1609 - both installed as portable, in separate directories.
MMA: 1.0.4.0127
on Galaxy Note
Android ICS 4.0.4
Debug logs sent 10:48pm Eastern May 8, 2013
I was able to get 4.1.0.1609 to connect, ONCE, but never again. Never could get 1636 to connect even once.
1609 would not connect at all. I shut down Symantec Endpoint Protection - nothing. I added MMW .exe to Windows firewall to grant local access. Nothing. I tried adding the MMW COM exe, and *that* seemed to let it connect. ONCE. Thereafter it would never connect again. MMW should be configuring these, or at least ask me if I want the rules configured.
On 1639, I could NEVER get it to connect, even once, even after configuring the firewall.
I tried doing a USB connection, it found the phone (MTP), and I enable remote sync. Nope - still could not connect wirelessly.
There seems to be no way to forget/disconnect/disable a sync server in MMA.
There is no way to do an uninstall on MMW, even though your FAQ says to do a clean install (unless you just mean wipe the directory - if so, just say so!).
You're going to need a LOT better user tooling for your users to diagnose connection problems, or you are going to suffer some painful debugging support. Better doc on how to add/remove sync servers, what each feature does (like do I need to *add* a sync server? why would I ever need that function, ie 2 sync servers on the same MM instance?) Better status notification/logging would go a long way - let me know each step it is taking - like that it found the server *machine*, even before trying to get access to the MMW library. All-or-nothing "hail Mary" communication logging is begging for things to fail in the middle - at every possible place.
MMA also seems to hang when the connection fails - which is all the time. I have to kill it through the task list.
Rebooting Android does not help.
Thanks.
MMA connected to MMW only ONCE with 1609, NEVER with 1639.
Windows 7/x64, all the latest patches. On a Lenovo W510 w/12GB RAM.
MMW: 4.1.0.1636 & 1609 - both installed as portable, in separate directories.
MMA: 1.0.4.0127
on Galaxy Note
Android ICS 4.0.4
Debug logs sent 10:48pm Eastern May 8, 2013
I was able to get 4.1.0.1609 to connect, ONCE, but never again. Never could get 1636 to connect even once.
1609 would not connect at all. I shut down Symantec Endpoint Protection - nothing. I added MMW .exe to Windows firewall to grant local access. Nothing. I tried adding the MMW COM exe, and *that* seemed to let it connect. ONCE. Thereafter it would never connect again. MMW should be configuring these, or at least ask me if I want the rules configured.
On 1639, I could NEVER get it to connect, even once, even after configuring the firewall.
I tried doing a USB connection, it found the phone (MTP), and I enable remote sync. Nope - still could not connect wirelessly.
There seems to be no way to forget/disconnect/disable a sync server in MMA.
There is no way to do an uninstall on MMW, even though your FAQ says to do a clean install (unless you just mean wipe the directory - if so, just say so!).
You're going to need a LOT better user tooling for your users to diagnose connection problems, or you are going to suffer some painful debugging support. Better doc on how to add/remove sync servers, what each feature does (like do I need to *add* a sync server? why would I ever need that function, ie 2 sync servers on the same MM instance?) Better status notification/logging would go a long way - let me know each step it is taking - like that it found the server *machine*, even before trying to get access to the MMW library. All-or-nothing "hail Mary" communication logging is begging for things to fail in the middle - at every possible place.
MMA also seems to hang when the connection fails - which is all the time. I have to kill it through the task list.
Rebooting Android does not help.
Thanks.