Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WLOC Service Has Stopped RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    After reinstalling (Hub), OC 2.0 because of a backup issue (this did solve the problem until restarting the pc as describe further on), I found that in OC 2.0 main UI the name of the computer was not exactly same as in System Properties, Computer name tab. The difference between the names is in OC the name appears in *uppercase* letters and in Computer name tab the name is *lowercase* letters.

     

    At first I wonder about this difference since with Windows XP during setup naming the pc it is not allowed to use *uppercase* letters and why has there been a change in OneCare 2.0? Until the computer was restarted and OneCare 2.0 error “Windows Live OneCare cannot continue” “The Windows Live OneCare service is not working or has stopped. To correct this problem, try restarting computer. If the problem persists contact support.”

     

    Restarting the computer does not correct this problem either. I also found these errors logged the same time in Windows Event Viewer.

    ·        Event ID 1000, Faulting application winss.exe version 2.0.2318.12, faulting module ntdll.dll version 5.1.2600.2180, fault address 0x000106c3

    ·        Event ID 1001, Fault bucket 490327208

    ·        These two Event IDs are repeated several times in the Event Viewer when OneCare repeats the above error.

     

    Using the command prompt type sc query winss, does report the service has stopped. 

     

    Now if this isn’t enough the client pc was on (activity online) and in OneCare UI also had the pc name changed to *uppercase* and OneCare immediately went into the same error” “The Windows Live OneCare service is not working or has stopped. To correct this problem, try restarting computer. If the problem persists contact support”

     

    Now I have two computers with unusable OC 2.0 installed and reinstall won’t change a thing.

     

    I am not pleased, is this, a bug in this version of OC 2.0.2318.12 or someone’s bright idea?

     

    Knightsky

     

    Thursday, August 23, 2007 4:27 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Steve,

    Yes, that maybe my attraction to the beta testing world, never a dull moment.

     

    Anyway thought you might like to know I may not need to reinstall OC on the client pc. At this time OC appears to be stable, since I had the forethought to remove the client pc from the OneCare Circle before the same error occurred, since I already had been dealing with it on the Hub pc.

     

    A cold restart had OneCare back in the green again, and then all I needed to do was reactivate, configure OC like the hub pc is configured, turn off backup etc. Of course this defeats the purpose of the OneCare Circle, sharing printer and centralize backups. But at this time both pcs with OneCare installed are stable again.

     

    Probably should have posted this issue in the Topic *Update*, but at the time I had not made connection. Been reading a few posts in the forum and bug reports on Connect. An with my own observation and data I may have found why after reinstalling OC on the Hub pc everything was OK for a day or so and then went down hill fast. The client pc was ok for sometime now (been turn off while I dealt with the Hub pc), and then suddenly without warning on the 22nd did the same thing. Should I be correct in my theory, the correction is not in my hand.

     

    Thanks,

    Knightsky

     

    Friday, August 24, 2007 5:12 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    As I replied to your other psot last night, I'm sure sorry to read that your troubles continue and have actually gotten worse.

    My recommendation is to file a bug or bugs on Connect and include the support zip files with the bug reports so that the developers can attempt to diagnose what happened.

    You can then contact support, although I would probably forego the support side and simply uninstall and reinstall, one PC at a time, to see if I can get OneCare working again.

    -steve

     

    Thursday, August 23, 2007 2:03 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Steve,

    Thanks for the reply, I am beginning to believe that OC 2.0 is keeping me entertained by throwing anything that *can* go wrong *will* go wrong.

     

    Simply uninstall and reinstall, does not work well, since I was able to configure the external drive for centralized backup and the Hub pc successfully backup to the drive before the error started. Reinstall will reproduce the original errors (access denied, permission error), I started with concerning the external drive. A cold start-up produces the same error I am now getting.

     

    Well, here we go again, saved all files (screen shots, OC support zip, and Dr Watson files) concerning this new problem. Wiped the drive and installed the OS from an image file. Installed OC 2.0 and the UI still has the pc name in uppercase, then activated OC. But this time no configuration for backup (I don’t trust the program), or as a Hub pc and the external drive is not installed. At the moment a cold start has not reproduced the OneCare *cannot continue error* and how long this is going to last I don’t know.

     

    Yet to *tactical* similar situation with the client pc, that will be tonight’s fun.

     

    But I agree with you OneCare support, I’ll forgo that one in favor of just submitting a bug report and watching how this install goes.

     

    Thanks,

    Knightsky

     

    Thursday, August 23, 2007 3:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Welcome to the world of beta testing. :-) Yes, indeed, beta testing can be lots of fun with cascading issues. The fact that you are able to restore an image and start over is excellent as you try to work through what is causing the issues.

    -steve

     

    Thursday, August 23, 2007 4:08 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Steve,

    Yes, that maybe my attraction to the beta testing world, never a dull moment.

     

    Anyway thought you might like to know I may not need to reinstall OC on the client pc. At this time OC appears to be stable, since I had the forethought to remove the client pc from the OneCare Circle before the same error occurred, since I already had been dealing with it on the Hub pc.

     

    A cold restart had OneCare back in the green again, and then all I needed to do was reactivate, configure OC like the hub pc is configured, turn off backup etc. Of course this defeats the purpose of the OneCare Circle, sharing printer and centralize backups. But at this time both pcs with OneCare installed are stable again.

     

    Probably should have posted this issue in the Topic *Update*, but at the time I had not made connection. Been reading a few posts in the forum and bug reports on Connect. An with my own observation and data I may have found why after reinstalling OC on the Hub pc everything was OK for a day or so and then went down hill fast. The client pc was ok for sometime now (been turn off while I dealt with the Hub pc), and then suddenly without warning on the 22nd did the same thing. Should I be correct in my theory, the correction is not in my hand.

     

    Thanks,

    Knightsky

     

    Friday, August 24, 2007 5:12 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the update and the continued testing efforts, Knigthsky.

    -steve

     

    Friday, August 24, 2007 1:44 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I found this over on Connect.

     

    Entered by patchKY on 8/24/2007

    I contacted support and they gave me this link (below) to the OneCare Update Fix tool, which is supposed to reset permission of the Database folder. The downside is you lose your backup info so onecare thinks you haven't ever performed a backup. But after running the tool OneCare is working fine again.

    http://download.microsoft.com/download/7/4/f/74f8bf9b-a19e-4f14-b3e7-0a3fe389224d/CaclsDeleteDB.exe

    Monday, August 27, 2007 5:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Scortch2,

     

    Thanks for the information; this tool may not be helpful since resetting the permission of the database for the *hub* pc and possible loss of OC backup. Will recreate the permission error I have been receiving, when backing up to the external drive. The most I can do is the first backup and then I will *run end* to the same permission error. I have *tested* this out. Hope is on the horizon for this issue, as I have been reassured this permission error will be *fix* after *beta refresh*.

     

    The “WLOC Service Has Stopped” error occurred after a clean install (hub) of OC v. 2.0.2318.12 on a fresh install of Win XP, (all was ok until), and receiving two automatic updates. Same error on the *client* pc after receiving the version as an update, the two automatic updates were already installed. At this time not creating OneCare Circle and configuring no back-ups on both pcs, keeps both installs of OC from crashing, with this configuration there is no problem OC starting and receiving updates. Sounds odd I know but have filed a bug report and uploaded files.

     

    Thanks,

    Knightsky

     

     

    Monday, August 27, 2007 4:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yea looks like they broke it big time.

     

    Monday, August 27, 2007 6:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
       I discovered that my Windows Live Onecare was not working when I went to "Programs".  When it came up, it was green, but this error came up "Onecare...not working properly...and has stopped". This patch worked.

     

    Thursday, August 30, 2007 9:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Sorry, I don’t understand, what patch are you referring to? Do you mean this tool that Scortch2 posted in his reply? If so, then I am glad to hear it does for you.

     

    http://download.microsoft.com/download/7/4/f/74f8bf9b-a19e-4f14-b3e7-0a3fe389224d/CaclsDeleteDB.exe

     

    Knightsky

     

    Thursday, August 30, 2007 9:52 PM