1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Error 0xC80003FB & 0xC80003FA

Discussion in 'Windows Update' started by maninrochester, Apr 16, 2008.

  1. I Am running W2k3 Ent. ed. I cannot do Sindows update this is the only
    meesage I get. I have tried removing/renaming the
    C:\%windir%\softwaredistribution folder. the WindowsUpdate.log has the
    following information:

    2008-04-16 10:52:12:041 872 138 AU ########### AU: Initializing Automatic
    Updates ###########
    2008-04-16 10:52:12:041 872 138 AU # Approval type: Scheduled (User
    preference)
    2008-04-16 10:52:12:041 872 138 AU # Scheduled install day/time: Every
    day at 3:00
    2008-04-16 10:52:12:041 872 138 AU # Auto-install minor updates: Yes
    (User preference)
    2008-04-16 10:52:12:041 872 138 AU Setting AU scheduled install time to
    2008-04-17 07:00:00
    2008-04-16 10:52:12:041 872 138 AU AU finished delayed initialization
    2008-04-16 10:52:12:572 872 934 DtaStor WARNING: DS: Database will be reset
    next time it starts up due to 0xc80003fb
    2008-04-16 10:52:12:603 872 934 PT WARNING: PopulateDataStore failed:
    0xc80003fb
    2008-04-16 10:52:12:603 872 934 PT WARNING: Sync of Updates: 0xc80003fb
    2008-04-16 10:52:12:603 872 934 PT WARNING: SyncServerUpdatesInternal
    failed: 0xc80003fb
    2008-04-16 10:52:12:603 872 934 Agent * WARNING: Failed to synchronize,
    error = 0xC80003FB
    2008-04-16 10:52:12:603 872 934 Agent * WARNING: Exit code = 0xC80003FB
    2008-04-16 10:52:12:603 872 934 Agent *********
    2008-04-16 10:52:12:603 872 934 Agent ** END ** Agent: Finding updates
    [CallerId = WindowsUpdate]
    2008-04-16 10:52:12:603 872 934 Agent *************
    2008-04-16 10:52:12:603 872 934 Agent WARNING: WU client failed Searching
    for update with error 0xc80003fb
    2008-04-16 10:52:12:619 2132 65c COMAPI >>-- RESUMED -- COMAPI: Search
    [ClientId = WindowsUpdate]
    2008-04-16 10:52:12:619 2132 65c COMAPI - Updates found = 0
    2008-04-16 10:52:12:619 2132 65c COMAPI - WARNING: Exit code = 0x00000000,
    Result code = 0xC80003FB
    2008-04-16 10:52:12:619 2132 65c COMAPI ---------
    2008-04-16 10:52:12:619 2132 65c COMAPI -- END -- COMAPI: Search
    [ClientId = WindowsUpdate]
    2008-04-16 10:52:12:619 2132 65c COMAPI -------------
    2008-04-16 10:52:12:619 2132 938 COMAPI WARNING: Operation failed due to
    earlier error, hr=C80003FB
    2008-04-16 10:52:12:619 2132 938 COMAPI FATAL: Unable to complete
    asynchronous search. (hr=C80003FB)
    2008-04-16 10:52:17:635 872 934 Report REPORT EVENT:
    {ADBF6EEA-FAFC-4E33-92A6-25675E2CA56F} 2008-04-16
    10:52:12:603-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 c80003fb WindowsUpdate Failure Software
    Synchronization Windows Update Client failed to detect with error 0xc80003fb.


    The event log has the following information in event ID 476\

    wuaueng.dll (872) SUS20ClientDataStore: The database page read from the file
    "C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb" at offset 2625536
    (0x0000000000281000) for 4096 (0x00001000) bytes failed verification because
    it contains no page data. The read operation will fail with error -1019
    (0xfffffc05). If this condition persists then please restore the database
    from a previous backup. This problem is likely due to faulty hardware. Please
    contact your hardware vendor for further assistance diagnosing the problem.

    this server is a virtual server using VMware server
     
  2. "maninrochester" <maninrochester@discussions.microsoft.com> wrote in message
    news:B7725EC4-48FC-4900-8872-FC2DF2642974@microsoft.com...
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > The event log has the following information in event ID 476
    >
    > wuaueng.dll (872) SUS20ClientDataStore: The database page read from the file
    > "C:WINDOWSSoftwareDistributionDataStoreDataStore.edb" at offset 2625536
    > (0x0000000000281000) for 4096 (0x00001000) bytes failed verification because
    > it contains no page data. The read operation will fail with error -1019
    > (0xfffffc05).<!--colorc--><!--/colorc-->


    0x3FB = 1019. Coincidence?


    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > If this condition persists then please restore the database from a previous backup.<!--colorc--><!--/colorc-->


    Here's what net helpmsg 1018 and 1019 report on XPsp2

    <cmd_output OS="XPsp2
    E:\>set /a c = 0x3FA
    1018
    E:\>net helpmsg %c%

    Illegal operation attempted on a registry key that has been marked for deletion.

    E:\>set /a c = 0x3FB
    1019
    E:\>net helpmsg %c%

    System could not allocate the required space in a registry log.

    </cmd_output>

    So, if instead of the "database" referred to by your event log it is really your
    registry which is bad that could explain all your symptoms.

    I would try using ProcMon to supplement the (vague) diagnostics you are getting.

    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > This problem is likely due to faulty hardware. Please
    > contact your hardware vendor for further assistance diagnosing the problem.
    >
    > this server is a virtual server using VMware server<!--colorc--><!--/colorc-->


    That could be a clue. What diagnostics does it have? <eg>


    Good luck

    Robert Aldwinckle
    ---
     
  3. Bruno Garcia

    Bruno Garcia Guest

    Hello,

    I have the exact same problem:
    W2k3 Ent, virtualized with vmware.

    And I got the exact same error messages on both wupdate and eventlog.
    Any solutions for this problem?

    "Robert Aldwinckle" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > "maninrochester" <maninrochester@discussions.microsoft.com> wrote in message
    > news:B7725EC4-48FC-4900-8872-FC2DF2642974@microsoft.com...
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    > > The event log has the following information in event ID 476
    > >
    > > wuaueng.dll (872) SUS20ClientDataStore: The database page read from the file
    > > "C:WINDOWSSoftwareDistributionDataStoreDataStore.edb" at offset 2625536
    > > (0x0000000000281000) for 4096 (0x00001000) bytes failed verification because
    > > it contains no page data. The read operation will fail with error -1019
    > > (0xfffffc05).<!--colorc--><!--/colorc-->
    >
    >
    > 0x3FB = 1019. Coincidence?
    >
    >
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    > > If this condition persists then please restore the database from a previous backup.<!--colorc--><!--/colorc-->
    >
    >
    > Here's what net helpmsg 1018 and 1019 report on XPsp2
    >
    > <cmd_output OS="XPsp2
    > E:>set /a c = 0x3FA
    > 1018
    > E:>net helpmsg %c%
    >
    > Illegal operation attempted on a registry key that has been marked for deletion.
    >
    > E:>set /a c = 0x3FB
    > 1019
    > E:>net helpmsg %c%
    >
    > System could not allocate the required space in a registry log.
    >
    > </cmd_output>
    >
    > So, if instead of the "database" referred to by your event log it is really your
    > registry which is bad that could explain all your symptoms.
    >
    > I would try using ProcMon to supplement the (vague) diagnostics you are getting.
    >
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    > > This problem is likely due to faulty hardware. Please
    > > contact your hardware vendor for further assistance diagnosing the problem.
    > >
    > > this server is a virtual server using VMware server<!--colorc--><!--/colorc-->
    >
    >
    > That could be a clue. What diagnostics does it have? <eg>
    >
    >
    > Good luck
    >
    > Robert Aldwinckle
    > ---
    >
    >
    > <!--colorc--><!--/colorc-->
     

Share This Page