Answered by:
400 request cannot be fulfilled

Question
-
I have a problem that is described in: http://groups.google.com/group/microsoft.public.windows.live.foldershare/browse_thread/thread/33d1bb824976bc51/08b486b62dd4ff58#08b486b62dd4ff58
The moderator on that discussion group forwarded me to this forum. Attached to the post is the cab file of the error that I am getting right now (http://www.mediafire.com/?dpk30flxwez). It would be muchly appreciated to learn what is going on. Thanks.Tuesday, July 22, 2008 4:52 AM
Answers
-
Ken's #2 above sounds like the problem. This scenario is not supported today.
Richard Chung [ Live Mesh ]- Marked as answer by Ben [Live Mesh] Tuesday, September 2, 2008 8:20 PM
Wednesday, July 23, 2008 6:52 PMAnswerer
All replies
-
Hi,
Please go ahead and submit a bug with your Live Mesh logs attached. Instructions for doing so are in an Announcement at the top of the forums.
Thanks,
Ben.Tuesday, July 22, 2008 6:05 PM -
That link sure formatted badly here in the forum. :-(
And there's no cab file attached to the post, so I'm not sure where that went.
This is your original post from the newsgroup (I'm not a moderator there, by the way...)
"Hi,
I'm trying to upload something from my external hard drive to my
account's cloud, but apparently I can't sync properly with the error
shown in the subject title. What would exactly solve the problem, or
is there a link where I could see similar problems?"
-steve
Microsoft MVP Windows Live / Windows Live OneCare Forum ModeratorTuesday, July 22, 2008 6:08 PMModerator -
A 400 return error is typically caused by a couple culprits.
1) You are attempting to Map a folder locally and the location you picked to map to doesn't exist.
Example: you want to map your Photo's from your Live Mesh desktop to your new computer. In the dialog you choose download to: d:\new junk\shared photos\the share
If you haven't created the folders for (new junk) and (shared photos) it will return a 400 error.
2) Mesh currently doesn't really support sharing folders on removable media. If it detected your external hard drive as such it would return that failure error as well.
-Ken- Proposed as answer by Stephen BootsMVP, Moderator Thursday, July 24, 2008 1:43 AM
Wednesday, July 23, 2008 6:44 PM -
Ken's #2 above sounds like the problem. This scenario is not supported today.
Richard Chung [ Live Mesh ]- Marked as answer by Ben [Live Mesh] Tuesday, September 2, 2008 8:20 PM
Wednesday, July 23, 2008 6:52 PMAnswerer -
I'm experiencing this issue on one of three machines. One machine is running XP, the other two are running vista.
I meshed my "C:\Windows\Fonts" folder between one XP and one Vista machine without a problem.
On the other Vista machine, Mesh responds with the "Merge with existing folder?" dialog, followed by the error 400.
It doesn't seem like any of Ken's responses above describe my situation.
Any ideas?
"We're all in it together, kid." - Harry Tuttle, Heating EngineerFriday, April 10, 2009 1:48 PM -
My first guess would be a permissions or rights issue since it is a folder within the %system% folder, \Windows. However, I may be way off base since it worked with the other Vista machine.
How are you navigating to the local folder on the Vista machine you are trying to merge the Mesh folder to? On that machine is the User and admin? Are both Vista machines running 32 bit Vista or is one of them x64?
I think that your best bet would be to capture the logs from the machine with the problem and submit a bug, posting the bug ID/Link to the bug back here as a reply.
How to Submit Bugs and Live Mesh Logs
-steve
Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum ModeratorFriday, April 10, 2009 2:12 PMModerator -
I experienced this issue as well using a shared Mesh folder with a Beta version of the client and accessing shared folders created with newer versions of the client. Updating the client, changing the sync settings to "Never Synchronize With This Device," waiting for the the sync settings to replicate, then resyncing fixed the problem for me.Monday, May 4, 2009 11:23 AM
-
Thanks for sharing your experience, LK23. I assume that you found that the issue was that the Live Mesh client was not the same on the PCs and the client that encountered the error was the older one.
-steve
Microsoft MVP Windows Live / Windows Live OneCare & Live Mesh Forum ModeratorMonday, May 4, 2009 12:45 PMModerator -
i'm getting the same error... never had this error before in my home PC, been using MESH for almost a year now and I encountered this now.Tuesday, September 8, 2009 9:07 AM
-
i'm getting the same error... never had this error before in my home PC, been using MESH for almost a year now and I encountered this now.
Are you attempting to mesh a new location or is this being returned for a new device into the Mesh or an existing folder?
-steve
Microsoft MVP Windows Live / Windows Live OneCare, Live Mesh, & MS Security Essentials Forums ModeratorTuesday, September 8, 2009 11:38 AMModerator