Search
Active

5
Sign in to vote
0
Sign in to vote
Sign in
to vote
Type: Bug
ID: 428272
Opened: 3/30/2009 9:05:13 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I am trying to upload a data object with associated file and metadata to the mesh; something like the following using the April 2009 ctp tools:

m_feed.DataEntries.AddCompleted += new EventHandler<LiveItemEventArgs<DataEntry>>(DataEntries_AddCompleted);

DataEntry dataEntry = new DataEntry(info.Name);
CustomItemData data = new CustomItemData();
data.Description = "Standard description....blah...";
dataEntry.Resource.Type = "File";
m_feed.DataEntries.AddAsync(dataEntry, info);

then,

void DataEntries_AddCompleted(object sender, LiveItemEventArgs<DataEntry> e)
{
    FileInfo info = e.UserState as FileInfo;
    if (info != null)
    {
        FileStream fs = info.Open(FileMode.Open);
        e.Result.UpdateMediaResource(fs, "Application/Octet-Stream");
    }
}

The UpdateMediaResource call throws a null reference exception with the following stack trace:

at Microsoft.LiveFX.Client.DataEntry.GetMediaResourceOperationContext(Uri url, String mediaType, String slug, LiveOperatingEnvironment service)
at Microsoft.LiveFX.Client.DataEntry.UploadMediaResourceToStagingArea(Uri mediaStagingAreaUrl, String slug, LiveOperatingEnvironment service, Stream mediaResource, String mediaType)
at Microsoft.LiveFX.Client.DataEntry.UpdateMediaResource(Stream mediaResource, String mimeType)

Also, looking in the debugger shows e.Result.mediaStagingAreaUrl to be null in the AddCompleted event handler!
Details (expand)
Repro Steps
Run the above sample code compiled against the April 2009 Live Framework Tools in the debugger.
What OS are you using on your computer?
Vista SP1 (Enterprise)
What platform is your OS?
x86
Where in the product are you seeing your problem?
Live Framework
What browser are you using to view Live Mesh?
PC - Internet Explorer 8

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
1 attachments
AddProblem.saz
Sign in to post a comment.
Posted by Microsoft on 3/30/2009 at 1:12 PM
thanks baba! We'll have someone look at the installation logs and update the bug here when we have more info for you.

-Ben W.
Posted by Microsoft on 3/30/2009 at 1:13 PM
Sorry, I meant from the trace (not the install log). Got two different items confused. - Ben
Posted by Microsoft on 3/30/2009 at 1:37 PM
the trace you attached does not have any references to user-ctp.windows.net. Can you exit off your mesh.com client and rerun this against the cloud LOE? You can see the process name of the request in fiddler and all of yours in the attached trace are coming from moe.exe which is the mesh.com process.
Posted by Baba&ThePigman on 3/31/2009 at 9:54 AM
The app I am developing is a WPF application that connects to the local loe only at the moment. Anyway, after your request I have added some code to connect to the cloud and when I connect to the cloud and run the code that I posted I don't get the exception in 'UpdateMediaResource'. Having explained that does it still help if I generate fiddler trace from this code running against the cloud loe?
Posted by Microsoft on 4/1/2009 at 2:34 PM
Thanks for clarifying. I switched to client LOE and I am seeing the exception as well so I don't need the trace anymore.
-Ben
Posted by pkr2000 on 6/27/2009 at 4:18 PM
I *need* this in order to use Silverlight as a mesh client.