error 0x80248013 and 0x80244019 Rafael Moran 5/29/2007 12:03:02 AM have 200 machine with next errors 0x80248013 and 0x80244019 i am have gpo policy why this error my machines the status is "not reporting" please help me my problem is yet WSUS 2.0 console

Re: error 0x80248013 and 0x80244019 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/29/2007 1:07:50 AM "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message news:A42355E3-D3BD-46BB-8FE1-9E2F5BD3D09F[ at ]microsoft.com... [Quoted Text] > have 200 machine with next errors 0x80248013 and 0x80244019 i am have gpo > policy why this error > my machines the status is "not reporting" please help me > my problem is yet WSUS 2.0 console Run the Client Diagnostic Tool on: [a] The WSUS Server, and [b] One of the client systems and then post the results from both systems. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: error 0x80248013 and 0x80244019 Rafael Moran 5/29/2007 4:14:01 PM Hi Lawrence thanks for you help this test is my wsus server WSUS Client Diagnostics Tool Checking Machine State Checking for admin rights to run tool . . . . . . . . . PASS Automatic Updates Service is running. . . . . . . . . . PASS Background Intelligent Transfer Service is running. . . PASS Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS This version is WSUS 2.0 Checking AU Settings AU Option is 1 : Disabled . . . . . . . . . . . . . . . PASS Option is from Control Panel Checking Proxy Configuration Checking for winhttp local machine Proxy settings . . . PASS Winhttp local machine access type <Direct Connection> Winhttp local machine Proxy. . . . . . . . . . NONE Winhttp local machine ProxyBypass. . . . . . . NONE Checking User IE Proxy settings . . . . . . . . . . . . PASS User IE Proxy. . . . . . . . . . . . . . . . . NONE User IE ProxyByPass. . . . . . . . . . . . . . NONE User IE AutoConfig URL Proxy file:////sv-dc-02/netlogon/proxyciti.pac User IE AutoDetect AutoDetect in use Checking Connection to WSUS/SUS Server AU does not have Policy Set AU does not have Policy Set UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL -------------------------------------------------------------------- this is the one client machine no report. WSUS Client Diagnostics Tool Checking Machine State Checking for admin rights to run tool . . . . . . . . . PASS Automatic Updates Service is running. . . . . . . . . . PASS Background Intelligent Transfer Service is not running. PASS Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS This version is WSUS 2.0 Checking AU Settings AU Option is 4: Scheduled Install . . . . . . . . . . . PASS Option is from Policy settings Checking Proxy Configuration Checking for winhttp local machine Proxy settings . . . PASS Winhttp local machine access type <Direct Connection> Winhttp local machine Proxy. . . . . . . . . . NONE Winhttp local machine ProxyBypass. . . . . . . NONE Checking User IE Proxy settings . . . . . . . . . . . . PASS User IE Proxy. . . . . . . . . . . . . . . . . NONE User IE ProxyByPass. . . . . . . . . . . . . . NONE User IE AutoConfig URL Proxy file:////sv-dc-02/netlogon/proxyciti.pac User IE AutoDetect AutoDetect not in use Checking Connection to WSUS/SUS Server WUServer = http://suscuscasv:8530 WUStatusServer = http://suscuscasv:8530 UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS Connection to server. . . . . . . . . . . . . . . . . . PASS SelfUpdate folder is present. . . . . . . . . . . . . . PASS test this is the my client machine "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message > news:A42355E3-D3BD-46BB-8FE1-9E2F5BD3D09F[ at ]microsoft.com... > > have 200 machine with next errors 0x80248013 and 0x80244019 i am have gpo > > policy why this error > > my machines the status is "not reporting" please help me > > my problem is yet WSUS 2.0 console > > Run the Client Diagnostic Tool on: > [a] The WSUS Server, and > [b] One of the client systems > > and then post the results from both systems. > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > > >

Re: error 0x80248013 and 0x80244019 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/29/2007 11:49:49 PM "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message news:320E51DE-A4FC-44BC-A6AD-615375645678[ at ]microsoft.com... [Quoted Text] > Hi Lawrence thanks for you help > this test is my wsus server > Checking AU Settings > AU Option is 1 : Disabled . . . . . . . . . . . . . . . PASS > Option is from Control Panel Why is Automatic Updates disabled on your WSUS Server? > Checking Proxy Configuration > Checking for winhttp local machine Proxy settings . . . PASS > Winhttp local machine access type > <Direct Connection> > Winhttp local machine Proxy. . . . . . . . . . NONE > Winhttp local machine ProxyBypass. . . . . . . NONE > Checking User IE Proxy settings . . . . . . . . . . . . PASS > User IE Proxy. . . . . . . . . . . . . . . . . NONE > User IE ProxyByPass. . . . . . . . . . . . . . NONE > User IE AutoConfig URL Proxy > file:////sv-dc-02/netlogon/proxyciti.pac > User IE AutoDetect > AutoDetect in use If access through the proxy server is *required*, the autoconfig won't be of any use. The WUA uses WinHTTP to access the WSUS Server (even if it's on the same physical box), and if the proxy is required, then you'll need to configure the WinHTTP proxy settings -- either using the Proxy Configuration dialog box of the WSUS Administration Console, or using the proxycfg.exe utility. > Checking Connection to WSUS/SUS Server > AU does not have Policy Set > AU does not have Policy Set > UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL No policy applied to the WSUS server, either. How are you applying Critical and Security Updates to your WSUS Server? > -------------------------------------------------------------------- > > this is the one client machine no report. > Checking Proxy Configuration > Checking for winhttp local machine Proxy settings . . . PASS > Winhttp local machine access type > <Direct Connection> > Winhttp local machine Proxy. . . . . . . . . . NONE > Winhttp local machine ProxyBypass. . . . . . . NONE > Checking User IE Proxy settings . . . . . . . . . . . . PASS > User IE Proxy. . . . . . . . . . . . . . . . . NONE > User IE ProxyByPass. . . . . . . . . . . . . . NONE > User IE AutoConfig URL Proxy > file:////sv-dc-02/netlogon/proxyciti.pac > User IE AutoDetect > AutoDetect not in use Same note as for the server. If access through the proxy is *required*, not having configured WinHTTP will be problematic. > Checking Connection to WSUS/SUS Server > WUServer = http://suscuscasv:8530 > WUStatusServer = http://suscuscasv:8530 > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS > Connection to server. . . . . . . . . . . . . . . . . . PASS > SelfUpdate folder is present. . . . . . . . . . . . . . PASS The client is successfully communicating with the WSUS server. >> > have 200 machine with next errors 0x80248013 and 0x80244019 Next step is to post a log segment showing these two errors. I don't have documentation on the 0x80248013, but the 0x80244019 is an HTTP 404 error. I'd need to know what the client was trying to access when it encountered this error. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: error 0x80248013 and 0x80244019 Rafael Moran 5/30/2007 3:23:03 PM good morning hi Lawrence thanks no use proxy for my wsus client i have policy by means of active directory then my client updated from one server is this conect to internet and download the updated. the stranger is this machine no all have chance the name. check the windowsupdated.log and show me the next Failure Software Synchronization Error: Agent failed detecting with reason: 0x80244010 please help me not that to do "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message > news:320E51DE-A4FC-44BC-A6AD-615375645678[ at ]microsoft.com... > > > Hi Lawrence thanks for you help > > this test is my wsus server > > > Checking AU Settings > > AU Option is 1 : Disabled . . . . . . . . . . . . . . . PASS > > Option is from Control Panel > > Why is Automatic Updates disabled on your WSUS Server? > > > Checking Proxy Configuration > > Checking for winhttp local machine Proxy settings . . . PASS > > Winhttp local machine access type > > <Direct Connection> > > Winhttp local machine Proxy. . . . . . . . . . NONE > > Winhttp local machine ProxyBypass. . . . . . . NONE > > Checking User IE Proxy settings . . . . . . . . . . . . PASS > > User IE Proxy. . . . . . . . . . . . . . . . . NONE > > User IE ProxyByPass. . . . . . . . . . . . . . NONE > > User IE AutoConfig URL Proxy > > file:////sv-dc-02/netlogon/proxyciti.pac > > User IE AutoDetect > > AutoDetect in use > > If access through the proxy server is *required*, the autoconfig won't be of > any use. The WUA uses WinHTTP to access the WSUS Server (even if it's on the > same physical box), and if the proxy is required, then you'll need to > configure the WinHTTP proxy settings -- either using the Proxy Configuration > dialog box of the WSUS Administration Console, or using the proxycfg.exe > utility. > > > Checking Connection to WSUS/SUS Server > > AU does not have Policy Set > > AU does not have Policy Set > > UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL > > No policy applied to the WSUS server, either. How are you applying Critical > and Security Updates to your WSUS Server? > > > -------------------------------------------------------------------- > > > > this is the one client machine no report. > > > Checking Proxy Configuration > > Checking for winhttp local machine Proxy settings . . . PASS > > Winhttp local machine access type > > <Direct Connection> > > Winhttp local machine Proxy. . . . . . . . . . NONE > > Winhttp local machine ProxyBypass. . . . . . . NONE > > Checking User IE Proxy settings . . . . . . . . . . . . PASS > > User IE Proxy. . . . . . . . . . . . . . . . . NONE > > User IE ProxyByPass. . . . . . . . . . . . . . NONE > > User IE AutoConfig URL Proxy > > file:////sv-dc-02/netlogon/proxyciti.pac > > User IE AutoDetect > > AutoDetect not in use > > Same note as for the server. If access through the proxy is *required*, not > having configured WinHTTP will be problematic. > > > Checking Connection to WSUS/SUS Server > > WUServer = http://suscuscasv:8530 > > WUStatusServer = http://suscuscasv:8530 > > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS > > Connection to server. . . . . . . . . . . . . . . . . . PASS > > SelfUpdate folder is present. . . . . . . . . . . . . . PASS > > The client is successfully communicating with the WSUS server. > > >> > have 200 machine with next errors 0x80248013 and 0x80244019 > > Next step is to post a log segment showing these two errors. I don't have > documentation on the 0x80248013, but the 0x80244019 is an HTTP 404 error. > I'd need to know what the client was trying to access when it encountered > this error. > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >

Re: error 0x80248013 and 0x80244019 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/30/2007 4:46:40 PM "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message news:D8B67778-A01A-4FCE-BA11-618290299914[ at ]microsoft.com... [Quoted Text] > good morning hi Lawrence thanks > no use proxy for my wsus client i have policy by means of active directory > then my client updated from one server is this conect to internet and > download the updated. > > the stranger is this machine no all have chance the name. check the > windowsupdated.log and show me the next Failure Software Synchronization > Error: Agent failed detecting with reason: 0x80244010 please help me not > that > to do How about you post the actual log segment, with the actual log/error entries, and we'll evaluate from there. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: error 0x80248013 and 0x80244019 "Cecils\(MSFT\)" <cecils[ at ]online.microsoft.com> 5/31/2007 12:22:57 AM error 0x80248013 is a WU_E_DS_DuplicateUpdateID -- Cecil [MSFT] Deployment, WSUS Microsoft This posting is provided "As Is" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm "Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message news:OgleMwkoHHA.208[ at ]TK2MSFTNGP05.phx.gbl... [Quoted Text] > "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message > news:320E51DE-A4FC-44BC-A6AD-615375645678[ at ]microsoft.com... > >> Hi Lawrence thanks for you help >> this test is my wsus server > >> Checking AU Settings >> AU Option is 1 : Disabled . . . . . . . . . . . . . . . PASS >> Option is from Control Panel > > Why is Automatic Updates disabled on your WSUS Server? > >> Checking Proxy Configuration >> Checking for winhttp local machine Proxy settings . . . PASS >> Winhttp local machine access type >> <Direct Connection> >> Winhttp local machine Proxy. . . . . . . . . . NONE >> Winhttp local machine ProxyBypass. . . . . . . NONE >> Checking User IE Proxy settings . . . . . . . . . . . . PASS >> User IE Proxy. . . . . . . . . . . . . . . . . NONE >> User IE ProxyByPass. . . . . . . . . . . . . . NONE >> User IE AutoConfig URL Proxy >> file:////sv-dc-02/netlogon/proxyciti.pac >> User IE AutoDetect >> AutoDetect in use > > If access through the proxy server is *required*, the autoconfig won't be > of any use. The WUA uses WinHTTP to access the WSUS Server (even if it's > on the same physical box), and if the proxy is required, then you'll need > to configure the WinHTTP proxy settings -- either using the Proxy > Configuration dialog box of the WSUS Administration Console, or using the > proxycfg.exe utility. > >> Checking Connection to WSUS/SUS Server >> AU does not have Policy Set >> AU does not have Policy Set >> UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL > > No policy applied to the WSUS server, either. How are you applying > Critical and Security Updates to your WSUS Server? > >> -------------------------------------------------------------------- >> >> this is the one client machine no report. > >> Checking Proxy Configuration >> Checking for winhttp local machine Proxy settings . . . PASS >> Winhttp local machine access type >> <Direct Connection> >> Winhttp local machine Proxy. . . . . . . . . . NONE >> Winhttp local machine ProxyBypass. . . . . . . NONE >> Checking User IE Proxy settings . . . . . . . . . . . . PASS >> User IE Proxy. . . . . . . . . . . . . . . . . NONE >> User IE ProxyByPass. . . . . . . . . . . . . . NONE >> User IE AutoConfig URL Proxy >> file:////sv-dc-02/netlogon/proxyciti.pac >> User IE AutoDetect >> AutoDetect not in use > > Same note as for the server. If access through the proxy is *required*, > not having configured WinHTTP will be problematic. > >> Checking Connection to WSUS/SUS Server >> WUServer = http://suscuscasv:8530 >> WUStatusServer = http://suscuscasv:8530 >> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS >> Connection to server. . . . . . . . . . . . . . . . . . PASS >> SelfUpdate folder is present. . . . . . . . . . . . . . PASS > > The client is successfully communicating with the WSUS server. > >>> > have 200 machine with next errors 0x80248013 and 0x80244019 > > Next step is to post a log segment showing these two errors. I don't have > documentation on the 0x80248013, but the 0x80244019 is an HTTP 404 error. > I'd need to know what the client was trying to access when it encountered > this error. > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > .... >

Re: error 0x80248013 and 0x80244019 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/31/2007 2:40:10 AM "Cecils(MSFT)" <cecils[ at ]online.microsoft.com> wrote in message news:%23ZXeYnxoHHA.4132[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] > error 0x80248013 is a WU_E_DS_DuplicateUpdateID So, he's getting a DuplicateUpdateId error concurrent with an HTTP '404' error on the resource. That's confusing! Here's to hoping the actual log segment shows them as unrelated. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: error 0x80248013 and 0x80244019 Rafael Moran 5/31/2007 6:12:01 PM {01B0B9F1-0C77-45EB-ADA6-E0886BCAB10E} 2007-05-28 08:49:10-0600 1 161 101 {1AFB1AFE-9AAF-4DC4-9DAC-C75303A84655} 100 80244019 AutomaticUpdates Failure Content Download Error: Download failed. {EDEB0FF0-3554-4362-B943-1131215D2FE8} 2007-05-29 08:46:26-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 AutomaticUpdates Failure Software Synchronization Error: Agent failed detecting with reason: 0x80248013 {4A6659FD-B120-4B08-952C-BE1246AE3D35} 2007-05-29 13:47:34-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 AutomaticUpdates Failure Software Synchronization Error: Agent failed detecting with reason: 0x80248013 {AB3675EE-D29D-4803-9181-ED5D1F6D8280} 2007-05-30 08:43:09-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 AutomaticUpdates Failure Software Synchronization Error: Agent failed detecting with reason: 0x80248013 {F694C58F-67CA-4E58-879A-A4A2CF30FCD8} 2007-05-30 13:44:22-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 AutomaticUpdates Failure Software Synchronization Error: Agent failed detecting with reason: 0x80248013 {2EC5BF30-655C-41D9-92A8-9BA4BD54C46C} 2007-05-31 08:45:54-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 AutomaticUpdates Failure Software Synchronization Error: Agent failed detecting with reason: 0x80248013 {81711039-FDBA-4DBE-A967-A42A94E7FFCD} 2007-05-31 08:46:26-0600 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. this example the log machine what happend. "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Cecils(MSFT)" <cecils[ at ]online.microsoft.com> wrote in message > news:%23ZXeYnxoHHA.4132[ at ]TK2MSFTNGP02.phx.gbl... > > > error 0x80248013 is a WU_E_DS_DuplicateUpdateID > > So, he's getting a DuplicateUpdateId error concurrent with an HTTP '404' > error on the resource. > > That's confusing! > > Here's to hoping the actual log segment shows them as unrelated. > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >

Re: error 0x80248013 and 0x80244019 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/31/2007 9:02:41 PM "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message news:20706184-5511-4BF5-ADEE-D2577A2EB416[ at ]microsoft.com... My take on these log entries (unfortunately you didn't include the *whole* segment)... Is that they're separate errors. [Quoted Text] > {01B0B9F1-0C77-45EB-ADA6-E0886BCAB10E} 2007-05-28 > 08:49:10-0600 1 161 101 {1AFB1AFE-9AAF-4DC4-9DAC-C75303A84655} 100 > 80244019 AutomaticUpdates Failure Content Download Error: Download failed. This is the download process griping because it cannot find the content to download. > {EDEB0FF0-3554-4362-B943-1131215D2FE8} 2007-05-29 > 08:46:26-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > AutomaticUpdates Failure Software > Synchronization Error: Agent failed detecting with reason: 0x80248013 > {4A6659FD-B120-4B08-952C-BE1246AE3D35} 2007-05-29 > 13:47:34-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > AutomaticUpdates Failure Software > Synchronization Error: Agent failed detecting with reason: 0x80248013 > {AB3675EE-D29D-4803-9181-ED5D1F6D8280} 2007-05-30 > 08:43:09-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > AutomaticUpdates Failure Software > Synchronization Error: Agent failed detecting with reason: 0x80248013 > {F694C58F-67CA-4E58-879A-A4A2CF30FCD8} 2007-05-30 > 13:44:22-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > AutomaticUpdates Failure Software > Synchronization Error: Agent failed detecting with reason: 0x80248013 > {2EC5BF30-655C-41D9-92A8-9BA4BD54C46C} 2007-05-31 > 08:45:54-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > AutomaticUpdates Failure Software > Synchronization Error: Agent failed detecting with reason: 0x80248013 These are the DETECTION errors, griping because (as Cecil offered), there seems to be a WU_E_DS_DuplicateUpdateID issue. > {81711039-FDBA-4DBE-A967-A42A94E7FFCD} 2007-05-31 > 08:46:26-0600 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 > AutomaticUpdates Failure Software > Synchronization Unable to Connect: Windows is unable to connect to the > automatic updates service and therefore cannot download and install > updates > according to the set schedule. Windows will continue to try to establish a > connection. This is the english language version of the previous 80248013 errors. Is this the only client with these errors? Do all of your clients have these errors? What about the WUA on the WSUS server itself? Can the WSUS server detect and update from itself? -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: error 0x80248013 and 0x80244019 Rafael Moran 5/31/2007 9:27:00 PM how fix this problem and my clients now are 179 client no report status. please tell me what to do ? "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message > news:20706184-5511-4BF5-ADEE-D2577A2EB416[ at ]microsoft.com... > > My take on these log entries (unfortunately you didn't include the *whole* > segment)... > > Is that they're separate errors. > > > {01B0B9F1-0C77-45EB-ADA6-E0886BCAB10E} 2007-05-28 > > 08:49:10-0600 1 161 101 {1AFB1AFE-9AAF-4DC4-9DAC-C75303A84655} 100 > > 80244019 AutomaticUpdates Failure Content Download Error: Download failed. > > This is the download process griping because it cannot find the content to > download. > > > {EDEB0FF0-3554-4362-B943-1131215D2FE8} 2007-05-29 > > 08:46:26-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > {4A6659FD-B120-4B08-952C-BE1246AE3D35} 2007-05-29 > > 13:47:34-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > {AB3675EE-D29D-4803-9181-ED5D1F6D8280} 2007-05-30 > > 08:43:09-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > {F694C58F-67CA-4E58-879A-A4A2CF30FCD8} 2007-05-30 > > 13:44:22-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > {2EC5BF30-655C-41D9-92A8-9BA4BD54C46C} 2007-05-31 > > 08:45:54-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > These are the DETECTION errors, griping because (as Cecil offered), there > seems to be a WU_E_DS_DuplicateUpdateID issue. > > > > {81711039-FDBA-4DBE-A967-A42A94E7FFCD} 2007-05-31 > > 08:46:26-0600 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 > > AutomaticUpdates Failure Software > > Synchronization Unable to Connect: Windows is unable to connect to the > > automatic updates service and therefore cannot download and install > > updates > > according to the set schedule. Windows will continue to try to establish a > > connection. > > This is the english language version of the previous 80248013 errors. > > Is this the only client with these errors? Do all of your clients have these > errors? > > What about the WUA on the WSUS server itself? Can the WSUS server detect and > update from itself? > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > > >

Re: error 0x80248013 and 0x80244019 Rafael Moran 5/31/2007 9:29:01 PM how the fix error in my client please help? "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message > news:20706184-5511-4BF5-ADEE-D2577A2EB416[ at ]microsoft.com... > > My take on these log entries (unfortunately you didn't include the *whole* > segment)... > > Is that they're separate errors. > > > {01B0B9F1-0C77-45EB-ADA6-E0886BCAB10E} 2007-05-28 > > 08:49:10-0600 1 161 101 {1AFB1AFE-9AAF-4DC4-9DAC-C75303A84655} 100 > > 80244019 AutomaticUpdates Failure Content Download Error: Download failed. > > This is the download process griping because it cannot find the content to > download. > > > {EDEB0FF0-3554-4362-B943-1131215D2FE8} 2007-05-29 > > 08:46:26-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > {4A6659FD-B120-4B08-952C-BE1246AE3D35} 2007-05-29 > > 13:47:34-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > {AB3675EE-D29D-4803-9181-ED5D1F6D8280} 2007-05-30 > > 08:43:09-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > {F694C58F-67CA-4E58-879A-A4A2CF30FCD8} 2007-05-30 > > 13:44:22-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > {2EC5BF30-655C-41D9-92A8-9BA4BD54C46C} 2007-05-31 > > 08:45:54-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80248013 > > AutomaticUpdates Failure Software > > Synchronization Error: Agent failed detecting with reason: 0x80248013 > > These are the DETECTION errors, griping because (as Cecil offered), there > seems to be a WU_E_DS_DuplicateUpdateID issue. > > > > {81711039-FDBA-4DBE-A967-A42A94E7FFCD} 2007-05-31 > > 08:46:26-0600 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 > > AutomaticUpdates Failure Software > > Synchronization Unable to Connect: Windows is unable to connect to the > > automatic updates service and therefore cannot download and install > > updates > > according to the set schedule. Windows will continue to try to establish a > > connection. > > This is the english language version of the previous 80248013 errors. > > Is this the only client with these errors? Do all of your clients have these > errors? > > What about the WUA on the WSUS server itself? Can the WSUS server detect and > update from itself? > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > > >

Re: error 0x80248013 and 0x80244019 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 5/31/2007 10:32:48 PM "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message news:4C92979F-756F-4717-A9D4-AFFD49081CFB[ at ]microsoft.com... [Quoted Text] >> Is this the only client with these errors? Do all of your clients have >> these >> errors? >> >> What about the WUA on the WSUS server itself? Can the WSUS server detect >> and >> update from itself? > how fix this problem and my clients now are 179 client no report status. > please tell me what to do ? Well... if you want help... then you start by answering the questions presented in order to obtain useful information which will help us try to identify the problem and provide a solution. You appear to have answered one of them, if I am to assume that all 179 clients are experiencing this problem. If that's the case, then I'd make an educated guess that your WSUS server installation is defective and/or the database is corrupted. What can you tell me about the installation process for your WSUS server? (Tell me everything.) -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: error 0x80248013 and 0x80244019 Rafael Moran 5/31/2007 10:52:00 PM yes only about you questions is for this server is updated yes the stranger is this machine ones is new and other is rename the name the machina example sv018caj01 the older name caja-18 "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message > news:4C92979F-756F-4717-A9D4-AFFD49081CFB[ at ]microsoft.com... > > >> Is this the only client with these errors? Do all of your clients have > >> these > >> errors? > >> > >> What about the WUA on the WSUS server itself? Can the WSUS server detect > >> and > >> update from itself? > > > how fix this problem and my clients now are 179 client no report status. > > please tell me what to do ? > > > Well... if you want help... then you start by answering the questions > presented in order to obtain useful information which will help us try to > identify the problem and provide a solution. > > You appear to have answered one of them, if I am to assume that all 179 > clients are experiencing this problem. > > If that's the case, then I'd make an educated guess that your WSUS server > installation is defective and/or the database is corrupted. > > What can you tell me about the installation process for your WSUS server? > (Tell me everything.) > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >

Re: error 0x80248013 and 0x80244019 "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/1/2007 4:21:33 PM "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message news:01ACE695-3FB5-490B-A806-53E5BF7730CB[ at ]microsoft.com... [Quoted Text] > yes only > about you questions is for this server is updated yes > the stranger is this machine ones is new and other is rename the name the > machina > example sv018caj01 the older name caja-18 So... you renamed your server and now nothing can find it? Is that what you're telling me? -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: error 0x80248013 and 0x80244019 Rafael Moran 6/1/2007 6:45:01 PM no my server no the problem is and some machine are new and other no more change name. "Lawrence Garvin (MVP)" wrote: [Quoted Text] > "Rafael Moran" <RafaelMoran[ at ]discussions.microsoft.com> wrote in message > news:01ACE695-3FB5-490B-A806-53E5BF7730CB[ at ]microsoft.com... > > yes only > > about you questions is for this server is updated yes > > the stranger is this machine ones is new and other is rename the name the > > machina > > example sv018caj01 the older name caja-18 > > So... you renamed your server and now nothing can find it? > > Is that what you're telling me? > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >