Search
Active

3
Sign in to vote
0
Sign in to vote
Sign in
to vote
Type: Bug
ID: 430426
Opened: 4/3/2009 4:02:53 PM
Access Restriction: Public
0
Workaround(s)
1
User(s) can reproduce this bug
Operating the local mesh should be for the most part entirely possible without any network connection.

This is not possible with the .NET APIs, where it's trying to reach the cloud to add/remove mesh objects from the local LOE.
Details (expand)
Repro Steps
[TestClass]
public class LiveMeshFixture
{
[TestMethod]
public void ShouldAddMeshObjectOffline()
{
var loe = new LiveOperatingEnvironment();
loe.Connect(new System.Net.NetworkCredential(), new LiveItemAccessOptions(false, true));

var mo = new MeshObject("Offline MeshObject");
loe.Mesh.MeshObjects.Add(ref mo);

Assert.IsNotNull(mo.Resource.Id);

// Fails with:
//failed: System.Net.WebException: The operation has timed out
// at System.Net.HttpWebRequest.GetResponse()
// at Microsoft.Web.Clients.HttpClient.PostOrPut(String verb, Uri uri, HttpClientRequestStreamWriter requestBodyWriter, SyndicationOperationContext context)
// at Microsoft.Web.Clients.HttpClient.Post(Uri uri, HttpClientRequestStreamWriter requestBodyWriter, SyndicationOperationContext context)
// at Microsoft.Web.Clients.AtomPubClient.CreateOrUpdate[TResource](Boolean create, Uri feedUri, HttpClientRequestStreamWriter requestBodyWriter, SyndicationOperationContext context)
// at Microsoft.Web.Clients.AtomPubClient.CreateEntryResource[TResource](Uri collectionUrl, TResource entry, SyndicationOperationContext context)
// at Microsoft.Web.Clients.AtomPubClient.CreateEntryResource(Uri collectionUrl, SyndicationItem entry, SyndicationOperationContext context)
// at Microsoft.LiveFX.Client.LiveItemCollection`2.Add(TMeshItem& entry)
}

[TestMethod]
public void ShouldRemoveMeshObjectOffline()
{
var loe = new LiveOperatingEnvironment();
loe.Connect(new System.Net.NetworkCredential(), new LiveItemAccessOptions(false, true));

var mo = loe.Mesh.CreateQuery<MeshObject>().First();

loe.Mesh.MeshObjects.Remove(mo);

// Fails with:
//failed: Microsoft.LiveFX.Client.LiveOperationException: Live operation failed, please review the innerException for transport level exception details
// Microsoft.LiveFX.Client.LiveOperationException: Live operation failed, please review the innerException for transport level exception details ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
// at System.Net.HttpWebRequest.GetResponse()
// at Microsoft.Web.Clients.HttpClient.Delete(Uri uri, SyndicationOperationContext context)
// --- End of inner exception stack trace ---
// at Microsoft.LiveFX.Client.LiveItemCollection`2.Remove(TMeshItem entry)
}
}
What OS are you using on your computer?
Vista SP1 (Ultimate)
What platform is your OS?
x64
Where in the product are you seeing your problem?
Live Framework
What browser are you using to view Live Mesh?
Other

Our team will be able to actively investigate your issue if you provide your logs

Our team will be able to actively investigate your issue if you provide your logs
 

You will be given the option of attaching log files to your bug after you click the submit button below. 

To create the log files for Live Framework Client reporting:

1.  Click Start
2.  Select All Programs so that you are looking at the program folder for Live Framework Client (see screenshot below).
3.  Click Collect Logs
4. Your logs will be bundled together in a cab file named LiveFxClientLogs.cab saved on your desktop.
5. Complete the bug form and provide as much details as possible for our team to be able to understand and investigate your issue
6. Submit your bug. You will attach the cab file after the bug has been submitted.
7. On the bottom of the next page click attach files.
8. Attach the LiveFxClientLogs.cab saved on your desktop.

Thank you for helping us build a better product!


Installation issues

If you run into an error during the installation of the Live Mesh software a Servicing.log will be created.  The easiest way to find this log file:

1.  Click Start
2.  In the search bar (Vista) or Click Search (XP/2003) type Servicing*
3.  In the search results you will see Servicing.log or Servicing(0000).log depending on where the installation failed. 

To directly go to the file, the Servicing log is in INSTALLDIR\Setup\Servicing.log or %temp%\Live Mesh\Servicing[0000].log if Live Mesh was uninstalled/rolled back during a failed installation.

1. Submit a new bug and enter all information that will help us understand and investigate your issue.
2. Once completed submit your bug (you will attach the log file after the bug has been submitted)
3. On the bottom of the next page click attach files.
4. Attach your Servicing.log file to your bug.

File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 4/6/2009 at 1:20 PM
Thanks for posting this kzu. We'll get this over to the right team to review it.
Posted by kzu on 4/6/2009 at 1:34 PM
BTW, please note that this error has nothing to do with the fact that I'm not passing credentials to the Connect method. It fails the same if I do.

Thanks for investigating!