Mesh has stopped synchronization a folder.
Sorry for my English (remarks are accepted :) )
At a forum there was recently similar theme, but at me other case.
I have two PC:
1. Home PC
2. Work PCAlso I have folder MyFotos (many subfolders, capacity = 7,36Gb, 99% files are *.jpg) that synced p2p between Home PC and Work PC. I add this folder on Home PC. Next, on Desktop Work PC appear blue folder. I have selected the necessary folder. On a question "...to make merge of these folders..." has answered YES. Synchronisation process has started. There were many inquiries about the resolution of conflicts. I worked on Work PC and have selected variant "(approximate) ... leave from Home PC..." for all conflicts. (I wanted that the traffic went from the Home PC on Work PC). In a folder MyFoto on Work PC appeared many files *.WLX. Downloading of files has started. It was visible in the notifier. My Work PC - works always. Home PC works only in the evenings. Process went couple of days. Then has suddenly stopped.
On Work PC folder MyFotos inconsistent state. What can I do? How to restore process?
If I reinstall Mesh I will spend again the traffic, and the error again can repeat (At my home the limited traffic tariff). Therefore reinstallation is not desirable.
-----------
I have tried such variant. Has changed on Home PC for one of *.JPG files (that = *.WLX) a creation date. It was synchronised. I can arrive certainly so with all files, but it is too much them.
What I still can do?
Respuestas
- Your English is very good. :-)
Did you resolve all conflicts on the Work PC? It is possible that the sync will continue again after you've resolved the conflicts or after some period of time.
Did you also Sync with the Live Desktop at www.mesh.com? Are all of the files there?
You can submit a bug report with logs:
How to Submit Bugs and Live Mesh Logs
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator- Marcado como respuestaStephen BootsMVP, Moderadordomingo, 28 de junio de 2009 23:51
Todas las respuestas
- Your English is very good. :-)
Did you resolve all conflicts on the Work PC? It is possible that the sync will continue again after you've resolved the conflicts or after some period of time.
Did you also Sync with the Live Desktop at www.mesh.com? Are all of the files there?
You can submit a bug report with logs:
How to Submit Bugs and Live Mesh Logs
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator- Marcado como respuestaStephen BootsMVP, Moderadordomingo, 28 de junio de 2009 23:51
Did you resolve all conflicts on the Work PC?
Absolutely ALLIt is possible that the sync will continue again after you've resolved the conflicts or after some period of time
It has not occurredDid you also Sync with the Live Desktop at www.mesh.com?
No, only p2p home pc - work pcYou can submit a bug report with logs
I have made it. feedback = 471293- I also have problems with synch folders. It worked very well for month until last week. I synch my Favorites folder which contains over 2000 small files in 300 folders. I also resolved all conflics, wait every day over 8 hours, event I reinstall all LiveSynch on one machine - nothing.
I also notice that list of News on Notifier was stopped update. I can read all news on IE8 but not on notifier.
After reinstall I also notice that on Notifier the list of devices and folders is not completed.
I have sync everything with LiveDesktop.
Any Idea?
Piotr Maciejewski - gbbsoft,
I would have suggested the reinstall, which you've already done. So, the best I can suggest is to submit a bug report, too.
How to Submit Bugs and Live Mesh Logs
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator - Thanks for filing the bug report.
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator My LiveMesh begin to work.
I seem have understood as it works. It has started to work after Home PC switch on and idled about an hour. After that process begin to work.I only have not understood, why such wide interval of inactivity?
(It is necessary to make parametre regulating this interval. And still the button of immediate compulsory synchronisation.)
What to me now to do with the feedback?- It should not idle that long before synchronizing. If you have already filed the bug, you can add a comment to provide the new information about the delay before the sync began.
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator I also have problems with synch folders. It worked very well for month until last week. I synch my Favorites folder which contains over 2000 small files in 300 folders. I also resolved all conflics, wait every day over 8 hours, event I reinstall all LiveSynch on one machine - nothing.
I also notice that list of News on Notifier was stopped update. I can read all news on IE8 but not on notifier.
After reinstall I also notice that on Notifier the list of devices and folders is not completed.
I have sync everything with LiveDesktop.
Any Idea?
Piotr Maciejewski
My solution:
I notice a lot of "Root element is missing" errors in log.
I found this article: http://forums.asp.net/p/650453/663377.aspx#663377
I change maxRequestLength from 4096 to 40960 in httpRuntime in machine.config file.
Piotr Maciejewski- Piotr, can you submit a bug report with logs for your issue and include the steps that you took to resolve the problem? Thanks!
How to Submit Bugs and Live Mesh Logs
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator Piotr, can you submit a bug report with logs for your issue and include the steps that you took to resolve the problem? Thanks!
How to Submit Bugs and Live Mesh Logs
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator
I did it: https://connect.microsoft.com/LiveMesh/feedback/ViewFeedback.aspx?FeedbackID=471696
:-)
Piotr Maciejewski- Thanks, Piotr.-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator I change maxRequestLength from 4096 to 40960 in httpRuntime in machine.config file.
Piotr Maciejewski
I notice it was wrong.
Now I made second change. I change Moe.exe.config in directory: "c:\Documents and Settings\<user>\Local Settings\Application Data\Microsoft\Live Mesh\GacBase
Now this file has following containt:<configuration> <microsoft.live.moe> <switches> </switches> </microsoft.live.moe> <system.net> <settings> <httpWebRequest maximumResponseHeadersLength="128" /> </settings> </system.net> </configuration>
And sudenly mesh start synchronize everything... :-)
Piotr Maciejewski- Propuesto como respuestaBaldrian viernes, 13 de noviembre de 2009 19:07
- Where did you get the idea to make that change, Piotr? I just checked on my Vista machine and the config file only contains the following:
-steve<configuration> <microsoft.live.moe> <switches> </switches> </microsoft.live.moe> </configuration>
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator - From my mind... :-)
Piotr Maciejewski - If it works, who am I to argue with that? :-)
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator - I received a lot of 'Root element is missing' in log files.
I found in internet that one of reason of that is that XML file is empty or zero length.
I think out that LiveMesh receved or send too big WebService request or responce.
I hear that in .NetFramework that are some limits to XML request/resonce files.
My 1 idea was maxRequestLength in httpRuntime
Today I found maximumResponseHeadersLength in httpWebRequest.
1 solution was wrong because this options is for server, not client. LiveMesh is client in client-server partnership.
The second solution is better because I think that LiveMesh client received too big responce, so .Net infrastructure just block it (cut it to 0 bytes or something similar).
I mesh my Favorites and this is 2067 small files in 325 folders, maybe this is the reason.
Why I change this file?
Previously I changed machine.config file, but this is global computer configuration.
Moe.exe.config is local configuration file only for LiveHash.
Do you think it is hold water?
Piotr Maciejewski - I don't know if it is a good change to make, but, like I said, it worked for you, so it seems good. I'll ask Ken from the Live Mesh team to look at this and perhaps he'll respond.
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums Moderator - Mesh is working better but not perfect. I still have problems to synch news in Mesh.
Piotr Maciejewski Mesh is working better but not perfect. I still have problems to synch news in Mesh.
Piotr Maciejewski
News has been funky for me lately, too. I suspect that's a server side issue.
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums ModeratorI change maxRequestLength from 4096 to 40960 in httpRuntime in machine.config file.
Piotr Maciejewski
I notice it was wrong.
Now I made second change. I change Moe.exe.config in directory: "c:\Documents and Settings\<user>\Local Settings\Application Data\Microsoft\Live Mesh\GacBase
Now this file has following containt:>see post of Piotr above<
And sudenly mesh start synchronize everything... :-)
Piotr Maciejewski
I had a similar problem: I want to use mesh for synchronizing my Documents folder. I have a lot of subfolders in there with a lot of Documents. Mesh showed me a lot of these subfolders as empty directories. These empty subfolders were in a "deep hierarchy" (sorry don't know the english expression for that) --> Folders like this: Documents\Subfolder1\Subfolder2\Subfolder3\Subfolder4\Subfolder5\... . All Folders "deeper" than Subfolder 4 (I think it was 4) were indicated as empty.
With the solution of Piotr above Mesh now also synchronizes subfolders "deeper" than 4 and everything works fine now. So probably the Mesh team could just implement that code in the next release so the problems that users like Piotr and me had could be avoided... :-)
