Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
No p2p sync on mobile pc, only placeholders RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Several weeks ago I installed Live Mesh on three computers, Home, Work and Mobile.
    I use Live Mesh version 0.9.3424.14

    Home and Work pc's synchronize as expected.
    However, the Mobile pc only syncs correctly when attached to the home network.

    When Mobile is on any other network, the only thing I get are placeholders, not the actual files.
    Newly created Folders and subfolders, however, are synchronized.

    I've changed the Moe.exe.config for all three computers
    <configuration>
      <microsoft.live.moe>
         <switches>
    <add name="VRRelayName" value="relay.data.edge.messenger.live.com"/>
         </switches>
      </microsoft.live.moe>
    </configuration>

    But the problem still exists.

    Anyone with ideas?
    -Leo-
    Wednesday, January 28, 2009 1:29 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Leo,

    If you could submit a bug with logs (instructions) from the Mobile PC, we can take a closer look at what's going on.  Feel free to post the Connect Feedback ID here after you've submitted the bug, so that others can validate it.

    Thanks,

    Ben.

    • Marked as answer by Stephen BootsMVP, Moderator Wednesday, January 28, 2009 8:59 PM
    • Unmarked as answer by akja Wednesday, January 28, 2009 9:53 PM
    • Marked as answer by akja Tuesday, February 17, 2009 9:51 AM
    • Unmarked as answer by akja Tuesday, February 17, 2009 9:51 AM
    • Marked as answer by Stephen BootsMVP, Moderator Tuesday, February 17, 2009 6:32 PM
    Wednesday, January 28, 2009 6:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This problem has disappeared with the new Mesh version. I don't know if it is due to the new version or a correction during the installation process.
    Things run smooth now between all four machines on any network.
    A thank you to anyone who bothered to find a cause and possible solutions.
    • Marked as answer by akja Wednesday, March 25, 2009 10:47 AM
    Wednesday, March 25, 2009 10:46 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Leo,

    If you could submit a bug with logs (instructions) from the Mobile PC, we can take a closer look at what's going on.  Feel free to post the Connect Feedback ID here after you've submitted the bug, so that others can validate it.

    Thanks,

    Ben.

    • Marked as answer by Stephen BootsMVP, Moderator Wednesday, January 28, 2009 8:59 PM
    • Unmarked as answer by akja Wednesday, January 28, 2009 9:53 PM
    • Marked as answer by akja Tuesday, February 17, 2009 9:51 AM
    • Unmarked as answer by akja Tuesday, February 17, 2009 9:51 AM
    • Marked as answer by Stephen BootsMVP, Moderator Tuesday, February 17, 2009 6:32 PM
    Wednesday, January 28, 2009 6:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Could you clarify what you mean by "mobile PC?" I assume that you are referring to a laptop that you take to other locations and connect via HotSpots or via cellular connection? Assuming that I understand your situation, when the PC is not connected to your Home network, how long does the PC remain connected to the network? How many and how large are the files that you are synchronzing from Home that only show as placeholders on the mobile PC?

    -steve

    Microsoft MVP Windows Live / Windows Live OneCare Forum Moderator
    Wednesday, January 28, 2009 9:11 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Stephen Boots said:

    Could you clarify what you mean by "mobile PC?" I assume that you are referring to a laptop that you take to other locations and connect via HotSpots or via cellular connection? Assuming that I understand your situation, when the PC is not connected to your Home network, how long does the PC remain connected to the network? How many and how large are the files that you are synchronzing from Home that only show as placeholders on the mobile PC?

    -steve

    Microsoft MVP Windows Live / Windows Live OneCare Forum Moderator

    "Mobile" refers to a laptop (netbook with XP). At work my laptop is connected to the network the whole day. (wired and wireless, makes no difference)
    During travels it is connected for hours via UMTS or GPRS.

    As soon as I am home and connect to my home network, everything is sync'd quite fast (in minutes).

    NB: I installed Live Mesh at home through my (wireless) home network. Maybe it is dependend on de network that was present during installation??

    I'll try to figure out how to submit a bug...
    Wednesday, January 28, 2009 9:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you for your reply. I'll try to submit the bug.  
    Wednesday, January 28, 2009 9:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Ben [Live Mesh] said:

    Hi Leo,

    If you could submit a bug with logs (instructions) from the Mobile PC, we can take a closer look at what's going on.  Feel free to post the Connect Feedback ID here after you've submitted the bug, so that others can validate it.

    Thanks,

    Ben.


    Sorry Ben, submitting a bug seems to require a study by itself. I don't have the time to deal with all kinds of errors. Also to the log-collector is buggy: it ends with an error without leaving a trace of what went wrong and where it stored things (if it stored something at all)

    I'll probably return to the good old Groove Networks 3.1a, which has served me for years (since the first version in 1999/2000) without a hitch, and wait until Live Mesh (or the bug collection system) is a little more mature.
    I do applaud the effort and hope that Live Sync and  Live Mesh are integrated as soon as possible.

    BTW: why isn't the Groove sync engine used? It even uses delta files for faster sync'ing. 
    Wednesday, January 28, 2009 10:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    akja said:

    Ben [Live Mesh] said:

    Hi Leo,

    If you could submit a bug with logs (instructions) from the Mobile PC, we can take a closer look at what's going on.  Feel free to post the Connect Feedback ID here after you've submitted the bug, so that others can validate it.

    Thanks,

    Ben.


    Sorry Ben, submitting a bug seems to require a study by itself. I don't have the time to deal with all kinds of errors. Also to the log-collector is buggy: it ends with an error without leaving a trace of what went wrong and where it stored things (if it stored something at all)

    I'll probably return to the good old Groove Networks 3.1a, which has served me for years (since the first version in 1999/2000) without a hitch, and wait until Live Mesh (or the bug collection system) is a little more mature.
    I do applaud the effort and hope that Live Sync and  Live Mesh are integrated as soon as possible.

    BTW: why isn't the Groove sync engine used? It even uses delta files for faster sync'ing. 



    Hi Leo,

    I'm sorry you've decided to stop using Live Mesh, and do hope you'll give us a try again in the future.

    If you wouldn't mind clarifying just a bit: When you try to collect logs (Start Menu > All Programs > Live Mesh > Collect Live Mesh Logs) do you see the command prompt window open up?  But no .cab file is generated on your desktop?  Do you, perhaps, have your desktop folder redirected somewhere?  (It is, as you might imagine, particularly concerning when the tool for discovering the causes of bugs itself seems not to work properly.)

    Again, I hope we'll see you back here once Live Mesh has matured a bit more.

    Thanks,

    Ben.

    • Marked as answer by Ben [Live Mesh] Wednesday, January 28, 2009 10:37 PM
    • Unmarked as answer by akja Tuesday, February 17, 2009 9:51 AM
    Wednesday, January 28, 2009 10:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Ben [Live Mesh] said:

    Hi Leo,

    I'm sorry you've decided to stop using Live Mesh, and do hope you'll give us a try again in the future.

    If you wouldn't mind clarifying just a bit: When you try to collect logs (Start Menu > All Programs > Live Mesh > Collect Live Mesh Logs) do you see the command prompt window open up?  But no .cab file is generated on your desktop?  Do you, perhaps, have your desktop folder redirected somewhere?  (It is, as you might imagine, particularly concerning when the tool for discovering the causes of bugs itself seems not to work properly.)

    Again, I hope we'll see you back here once Live Mesh has matured a bit more.

    Thanks,

    Ben.



    Hi Ben,

    I found a LiveMeshLogs.cab in the GacBase dir.

    The problems with the collector:

    The CMD-window is opens normal. (prompts are all in Dutch)
    The first line complains that "TaskList is not recognized as an internal or external command...

    Next complaint is about not being able to find "TEMP-12287.tmp" in my local temp directory (%USERPROFILE%)

    The Desktop folder is NOT redirected.

    The cmd-window closes before I can read the last echo's and have no time to fiddle with the batchfile.

    Anyway, good luck!

    Thursday, January 29, 2009 2:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    akja said:
    "Mobile" refers to a laptop (netbook with XP). At work my laptop is connected to the network the whole day. (wired and wireless, makes no difference)
    During travels it is connected for hours via UMTS or GPRS.

    As soon as I am home and connect to my home network, everything is sync'd quite fast (in minutes).

    NB: I installed Live Mesh at home through my (wireless) home network. Maybe it is dependend on de network that was present during installation??

    I'll try to figure out how to submit a bug...

    Thanks for the clarification. Where you were connected when Live Mesh was installed should make no difference. However, if the network you are connected to at work isn't allowing the Live Mesh traffic to pass, perhaps because it is blocked at a firewall/proxy or you are connecting through an authenticated proxy, it obviously won't be able to sync the files.

    I can't see why it would not sync via UMTS or GPRS if you are connected for hours, except that Live Mesh might see the bandwidth available and really slow down the sync, especially over GPRS.

    -steve

    Microsoft MVP Windows Live / Windows Live OneCare Forum Moderator
    Thursday, January 29, 2009 3:57 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Ben [Live Mesh] said:

    Hi Leo,

    If you could submit a bug with logs (instructions) from the Mobile PC, we can take a closer look at what's going on.  Feel free to post the Connect Feedback ID here after you've submitted the bug, so that others can validate it.

    Thanks,

    Ben.



    Hi Ben,

    Found the time to submit a bug. It has id: 408492

    It contains a the cab-file with the logs on the notebook. (is it safe to have that public?)

    Friday, January 30, 2009 10:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Only Microsoft can see the attached log files, akja.

    -steve

    Microsoft MVP Windows Live / Windows Live OneCare Forum Moderator
    Friday, January 30, 2009 5:23 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    akja said:

    Ben [Live Mesh] said:

    Hi Leo,

    If you could submit a bug with logs (instructions) from the Mobile PC, we can take a closer look at what's going on.  Feel free to post the Connect Feedback ID here after you've submitted the bug, so that others can validate it.

    Thanks,

    Ben.



    Hi Ben,

    Found the time to submit a bug. It has id: 408492

    It contains a the cab-file with the logs on the notebook. (is it safe to have that public?)



    Hi Leo,

    Thank for submitting your bug and logs; I'm tracking it internally now, and I'll follow up with you as soon as I learn anything from the developers.  Your log files are quite full, which should help us narrow in on the problem.  And, as Steve indicates, your logs are only visible to the Live Mesh team: they are not visible to the public.  If you have any questions, please let me know.

    Thanks,

    Ben.

    Friday, January 30, 2009 7:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ben and Steve,

    Maybe this is helpful:

    I copied an existing file that already was sync'd, simply with xtrl-c and ctrl-v, and that file was sync'd in minutes (seconds?) while I was connected using UMTS.

    However, copying a non sync'd file did not result in a sync'd copy.

    Weird...

    I'll submit this with a cab-file. Maybe it's visible somewhere. ID: 409059

    (This should follow thread http://social.microsoft.com/Forums/en/LiveMesh/thread/39f63f87-27a5-4720-b49f-9dec0e18438a)

    TIA for your help

    Friday, January 30, 2009 10:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Could it be possible that the already synced file was re-synced (under a different filename) as fast as it was due to it having the same hash?

    Do the new files *never* sync?
    Sunday, February 1, 2009 2:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    nachmore said:

    Could it be possible that the already synced file was re-synced (under a different filename) as fast as it was due to it having the same hash?

    Do the new files *never* sync?


    Nachmore, I don't know what their hashcodes are, so I wouldn't know.

    And yes, new files are *never* sync'd with/from my netbook, as long as my netbook is signed in on other networks than my home network.

    But, as I wrote: newly created folders and ctrl-c ctrl-v files *are* sync'd.

    BTW: I keep getting a "Foldername[0000]" in my temp directories on all my pc's. And if I put my netbook to sleep, Live mesh creates a new "Foldername[0001]", then "Foldername[0002]" etc.
    "Foldername[0000]" has the same name as one of my shared folders, except for the counter within the square brackets. None of my other shared folders appears with such a folder in the Local settings temp dir.

    Shutting Mesh down deletes the folder with the higherst number. I can manually delete the remaining folders without any apparent effect on the functionality of mesh.
    Monday, February 9, 2009 10:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It would seem to me that the temp folder creation is happening because something is borked  (technical term for screwed up <g>) with the sync pointers. Hopefully your logs will reveal what the cause is.
    -steve
    Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum Moderator
    Tuesday, February 10, 2009 2:13 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Stephen Boots said:

    It would seem to me that the temp folder creation is happening because something is borked  (technical term for screwed up <g>) with the sync pointers. Hopefully your logs will reveal what the cause is.
    -steve

    Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum Moderator


    Thank you Stephen, interesting notion. It could mean that the p2p sync problem is isolated to the folder that is "borked". I will try this out with the other folders.

    Question: is there a way to (kind of) reset Mesh sync'ing, like the way you can use GrooveClean.exe in Groove? Or do I have to unshare and reshare?

    TIA

    Tuesday, February 10, 2009 3:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    As far as I know it would be unshare/share in order to reset things. Keep in mind that my speculation is purely that - speculation - based on your observation of the temp folders being created and orphaned.
    -steve
    Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum Moderator
    Tuesday, February 10, 2009 4:30 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    FYI, I am having the exact same issue as you describe.  Once upon a time, sync to remote locations was happening successfully.  It stopped suddenly, and was briefly corrected by the moe.exe.config VRRelayName setting you described above.  It does not appear to be working still on existing or newly created Mesh folders.

    Sharing mesh folders with others is only working if the files also exist on the LiveDesktop.

    Has a solution been found for this issue, or is it still an outstanding bug?
    Sunday, February 15, 2009 7:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Bozford,

    What you are describing sounds like a P2P problem - rather than a pure syncing problem (since it works to and from the Live Desktop).

    Could you start a new thread detailing your exact problem, including whether or not you have an interesting network setup / firewalls / antiviruses etc. that could be blocking Live Mesh's P2P traffic.

    Cheers,

    Oren
    Monday, February 16, 2009 1:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Bozford said:

    FYI, I am having the exact same issue as you describe.  Once upon a time, sync to remote locations was happening successfully.  It stopped suddenly, and was briefly corrected by the moe.exe.config VRRelayName setting you described above.  It does not appear to be working still on existing or newly created Mesh folders.

    Sharing mesh folders with others is only working if the files also exist on the LiveDesktop.

    Has a solution been found for this issue, or is it still an outstanding bug?



    Hi Bozford,

    No solution yet. They are probably still digging through the log. One of the folders I share is 3 GB.
    I've just used unshare-share on the largest folder, to see what happens. It seems that the Moe.exe on my Netbook is still busy merging the folders...
    If that (unshare-share) is a solution, I will post it here.
    Monday, February 16, 2009 1:07 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
     As an FYI, this thread is marked as answered because the current answer for this issue, and the proper path for anyone else reporting the same issue, is to file a bug on Connect and submit logs. Being a beta service, unexpected behavior warrants a bug report and the actual solution may be a code change in a future release. If the Connect bug reveals a different cause and solution, then it would be great to have that added to this thread and the answer tag applied to that post.
    -steve
    Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum Moderator
    Tuesday, February 17, 2009 6:36 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    This problem has disappeared with the new Mesh version. I don't know if it is due to the new version or a correction during the installation process.
    Things run smooth now between all four machines on any network.
    A thank you to anyone who bothered to find a cause and possible solutions.
    • Marked as answer by akja Wednesday, March 25, 2009 10:47 AM
    Wednesday, March 25, 2009 10:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Excellent news, akja.
    -steve
    Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum Moderator
    Wednesday, March 25, 2009 4:19 PM
    Moderator