Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CREATEFILE 0xC0190005 Errors... RRS feed

 > 

  • General discussion

  • Discussion
    Sign in to vote
    0
    Sign in to vote
    I posted a bug report on Connect a while ago about the fact that one machine didn't seem to be syncing: MOE reported that it was downloading, but nothing new was appearing in the folder (I could verify this by monitoring the size of the sync folder). Even the .wlx files weren't appearing on the non-syncing machine.

    The response from Connect in the end was it may be better if I started from scratch... I tried and nothing changed. Anyway, over Xmas I had the "pleasure" of rebuilding the machine that wasn't syncing. So, I started from scratch on both machines and thought I'd try again. The same thing happened-one machine wasn't syncing.

    Looking at some of the newer entries in this forum, it doesn't seem like I'm alone...

    MOE was/is constantly syncing, nothing new was appearing on the rebuilt machine (when I know there should be) and is was crippling the system as the CPU usage went up to 40%.

    So, I started up Process Monitor to view what MOE was doing...

    The VERY obvious thing that was happening was that MOE was attempting to create the .wlx file, but the call to CREATEFILE was always failing with the return value 0xC0190005 (STATUS_RM_NOT_ACTIVE - Transaction support within the specified file system resource manager was not started or was shut down due to an error.). I'm running Vista Enterprise and the Mesh folder on the PC that isn't syncing is on a secondary internal hard drive (if that makes any difference).

    So, this *seems* to be the reson why the files aren't syncing (?). And could also be the same for other posts with the same issues (one PC not syncing/.wlx files not appearing)?

    Will the imminent (cough) update address any issues like this that you've come up against?

    Hope this helps and let me know if you want any other infomation about this,

    Cheers,

    pq

    indigoblue
    Monday, January 5, 2009 11:07 PM

All replies

  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Thank you for the update.  Would you mind letting me know the feedback ID of your original Connect bug report?  I'd like to look into this further, and follow up with the appropriate members of our developer team.

    Thanks,

    Ben.
    Tuesday, January 6, 2009 4:38 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    No problem Ben, it was ID 378991.

    pq
    indigoblue
    Tuesday, January 6, 2009 5:17 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    indigoblue said:

    No problem Ben, it was ID 378991.

    pq

    indigoblue



    Hi,

    I've taken a look at the bug - it's still under active investigation (so not, I'm afraid, resolved in the upcoming release).  The new information you've gathered could prove invaluable to the developers doing the investigating, though, so if you wouldn't mind, could you please update your bug through Connect with your observations above?

    And since this is on my radar now, I'll keep an eye on it and let you know if I learn anything.

    Thanks for helping us test Live Mesh.

    Ben.
    Tuesday, January 6, 2009 7:28 PM
  • Discussion
    Sign in to vote
    0
    Sign in to vote
    Hi Ben,

    I've updated the report - I just thought it might be useful here too as several posts seem to be having similar issues.

    Thanks for your help & good luck!

    Paul
    indigoblue
    Wednesday, January 7, 2009 10:49 AM