|
| |||||||||
| Tags: 0x80244019, connecting, local |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| Windows Update Error 0x80244019 connecting to local Windows Update from a local server running Windows Update Server. The client workstation is XP SP2 and I have disabled the firewall. The server is in this building and there is not firewall or proxy server blocking communication. Here is the WindowsUpdate.log from the last time I tried to receive updates. 2005-04-29 10:01:10-0400 1824 734 Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3BD629 82-7F06-4861-B489-4A9917C474E8}.bin for reading. 2005-04-29 10:01:10-0400 2232 ca4 Trying to make out of proc datastore active 2005-04-29 10:01:11-0400 2232 ca4 Out of proc datastore is now active 2005-04-29 10:01:11-0400 1824 734 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2005-04-29 10:01:11-0400 1824 734 PT: Using server URL http://eqbobmcapp01/ClientWebService/client.asmx 2005-04-29 10:01:11-0400 1824 734 PT: Calling GetConfig on server 2005-04-29 10:01:11-0400 1824 734 Add header for accept-encoding: xpress succeeded 2005-04-29 10:01:11-0400 1824 734 DetectCompressionType returning type 0, hr=0x1 2005-04-29 10:01:11-0400 1824 734 GetConfig: 0x80244019 2005-04-29 10:01:11-0400 1824 734 PT: Cannot recover from fault, origin=GetConfig, hr=0x80244019 2005-04-29 10:01:11-0400 1824 734 Failed to obtain cached cookie with hr = 80244019. 2005-04-29 10:01:11-0400 1824 734 Failed to upload events with hr = 80244019. 2005-04-29 10:06:11-0400 2232 ca4 Out of proc datastore is shutting down 2005-04-29 10:06:12-0400 2232 ca4 Out of proc datastore is now inactive 2005-04-29 10:11:11-0400 1824 338 Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3BD629 82-7F06-4861-B489-4A9917C474E8}.bin for reading. 2005-04-29 10:11:11-0400 3152 f08 Trying to make out of proc datastore active 2005-04-29 10:11:12-0400 3152 f08 Out of proc datastore is now active 2005-04-29 10:11:12-0400 1824 338 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2005-04-29 10:11:12-0400 1824 338 PT: Using server URL http://eqbobmcapp01/ClientWebService/client.asmx 2005-04-29 10:11:12-0400 1824 338 PT: Calling GetConfig on server 2005-04-29 10:11:12-0400 1824 338 Add header for accept-encoding: xpress succeeded 2005-04-29 10:11:12-0400 1824 338 DetectCompressionType returning type 0, hr=0x1 2005-04-29 10:11:12-0400 1824 338 GetConfig: 0x80244019 2005-04-29 10:11:12-0400 1824 338 PT: Cannot recover from fault, origin=GetConfig, hr=0x80244019 2005-04-29 10:11:12-0400 1824 338 Failed to obtain cached cookie with hr = 80244019. 2005-04-29 10:11:12-0400 1824 338 Failed to upload events with hr = 80244019. 2005-04-29 10:16:12-0400 3152 f08 Out of proc datastore is shutting down 2005-04-29 10:16:13-0400 3152 f08 Out of proc datastore is now inactive 2005-04-29 10:21:12-0400 1824 368 Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3BD629 82-7F06-4861-B489-4A9917C474E8}.bin for reading. 2005-04-29 10:21:12-0400 968 b58 Trying to make out of proc datastore active 2005-04-29 10:21:13-0400 968 b58 Out of proc datastore is now active 2005-04-29 10:21:13-0400 1824 368 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2005-04-29 10:21:13-0400 1824 368 PT: Using server URL http://eqbobmcapp01/ClientWebService/client.asmx 2005-04-29 10:21:13-0400 1824 368 PT: Calling GetConfig on server 2005-04-29 10:21:13-0400 1824 368 Add header for accept-encoding: xpress succeeded 2005-04-29 10:21:13-0400 1824 368 DetectCompressionType returning type 0, hr=0x1 2005-04-29 10:21:13-0400 1824 368 GetConfig: 0x80244019 2005-04-29 10:21:13-0400 1824 368 PT: Cannot recover from fault, origin=GetConfig, hr=0x80244019 2005-04-29 10:21:13-0400 1824 368 Failed to obtain cached cookie with hr = 80244019. 2005-04-29 10:21:13-0400 1824 368 Failed to upload events with hr = 80244019. 2005-04-29 10:26:13-0400 968 b58 Out of proc datastore is shutting down 2005-04-29 10:26:15-0400 968 b58 Out of proc datastore is now inactive 2005-04-29 10:31:13-0400 1824 694 Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3BD629 82-7F06-4861-B489-4A9917C474E8}.bin for reading. 2005-04-29 10:31:14-0400 3168 844 Trying to make out of proc datastore active 2005-04-29 10:31:14-0400 3168 844 Out of proc datastore is now active 2005-04-29 10:31:14-0400 1824 694 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2005-04-29 10:31:14-0400 1824 694 PT: Using server URL http://eqbobmcapp01/ClientWebService/client.asmx 2005-04-29 10:31:14-0400 1824 694 PT: Calling GetConfig on server 2005-04-29 10:31:14-0400 1824 694 Add header for accept-encoding: xpress succeeded 2005-04-29 10:31:17-0400 1824 694 DetectCompressionType returning type 0, hr=0x1 2005-04-29 10:31:17-0400 1824 694 GetConfig: 0x80244019 2005-04-29 10:31:17-0400 1824 694 PT: Cannot recover from fault, origin=GetConfig, hr=0x80244019 2005-04-29 10:31:17-0400 1824 694 Failed to obtain cached cookie with hr = 80244019. 2005-04-29 10:31:17-0400 1824 694 Failed to upload events with hr = 80244019. 2005-04-29 10:36:15-0400 3168 844 Out of proc datastore is shutting down 2005-04-29 10:36:16-0400 3168 844 Out of proc datastore is now inactive 2005-04-29 10:39:57-0400 1824 724 Service received SERVICE_CONTROL_STOP control 2005-04-29 10:39:57-0400 1824 80 Exiting Service Main 2005-04-29 10:39:57-0400 812 f1c Trying to make out of proc datastore active 2005-04-29 10:39:58-0400 812 f1c Out of proc datastore is now active 2005-04-29 10:39:58-0400 812 f1c Out of proc datastore is shutting down 2005-04-29 10:39:58-0400 1824 80 WUAUENG ServiceMain exits. Exit code is 0x240001 2005-04-29 10:39:58-0400 2512 9c0 ChangeServiceConfig for wuauserv succeeded 2005-04-29 10:39:59-0400 812 f1c Out of proc datastore is now inactive |
|
#2
| |||
| |||
| Re: Windows Update Error 0x80244019 connecting to local Windows Update
Bellow is some troubleshooting steps. If at any point you try using Windows Update and it begins working again there’s no need to continue the troubleshooting steps. a.. Make sure: a.. That the account you’re running is an administrator account. b.. That you have the latest Service Pack available for your version of Windows (http://www.google.com/search?q=Micro...ervice+P ack). c.. That you have the latest Internet Explorer version (http://www.microsoft.com/windows/ie/). d.. That you’re virus free (http://security.symantec.com/sscv6/vc_about.asp). b.. Try running Windows Update again, continue if it does not work. c.. Clear the Temporary Internet Files and History: 1. Start Internet Explorer. 2. On the Tools menu, click Internet Options. 3. Click the General tab, and then click Delete Files under Temporary Internet files. 4. Click to clear the Delete all offline content check box, and then click OK. 5. Click Delete Cookies, and then click OK when you are prompted for confirmation. 6. Under Temporary Internet files, click Settings. 7. In the Settings dialog box, click View Objects. 8. Right-click the Windows Update Class file (may be called “WUWebControl Class” or something similar), click Remove, and then click Yes to confirm. Note: If you cannot find the Update Class file, continue to the next procedure. 9. Close the Windows Explorer window, and then click OK in the Settings dialog box. 10. Under History, click Clear History, and then click Yes when you are prompted for confirmation. 11. In the Internet Options dialog box, click OK. 12. Enable cookies. To do this, follow these steps: o In Control Panel, double-click the Internet Options icon. o Click the Privacy tab, and then click Default. o Click OK. 13. Click Start, click Run, type “%tmp%”, and then click OK. 14. In the Windows Explorer window that appears, delete the contents of this Temp folder. Note: Any file that cannot be deleted is probably being used. Make sure that you have closed all applications that were running. Then, try to delete the contents of this folder again. If you cannot delete a specific file, delete all the files that you can delete. · Try running Windows Update again, continue if it does not work. · Delete the Windows Update ActiveX control: The Windows Update ActiveX control may become corrupted. Therefore, you may have to remove and then reinstall the Windows Update ActiveX control. To remove and to reinstall the Windows Update ActiveX control, follow these steps. Note: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. 1. Quit Internet Explorer. 2. Click Start, and then click Search. 3. In the Search Results pane, click All files and folders under Search Companion. 4. In the All or part of the file name box, type “wuweb.dll”, and then click Search. 5. In the list of files, right-click wuweb.dll, and then click Delete. When you are prompted to confirm the deletion, click Yes. Note: If there are multiple copies of the wuweb.dll file, delete all of them. · Try running Windows Update again, continue if it does not work. · Temporarily turn off personal firewalls, download managers, pop-up blockers, and Web acceleration products: If you are using one of the following products, temporarily turn off the product and then try to use the Windows Update site: o Personal firewalls such as Norton Personal Firewall, McAfee Personal Firewalls, or Zone Labs o Download managers such as Get Right o Web accelerators such as Download Accelerator o Pop-up blockers Warning: This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk. · Try running Windows Update again, continue if it does not work. · Add Windows Update to the Trusted Sites Zone: 1. From the toolbar in Internet Explorer, click Tools, click Internet Options, and then click Security. 2. Click Trusted Sites Zone, and then click Sites. 3. Click to clear the Require server verification (https:) for all sites in this zone option. 4. In the Add this Web site to the zone: text box, type “http://*.microsoft.com”, and then click Add. 5. Click OK. 6. Click Custom Level, and then select Enable for the following items: o Download signed ActiveX controls. o Download unsigned ActiveX controls. o Initialize and script ActiveX controls not marked as safe. o Run ActiveX controls and plug-ins. o Script ActiveX controls marked safe for scripting. 7. Click OK, and then click OK again to exit Internet Properties. · Try running Windows Update again, continue if it does not work. · Disable script or proxy settings: 1. In Control Panel, double-click the Internet Options icon. 2. Click the Connections tab, and then click LAN Settings. 3. Click to clear the Use automatic configuration script check box, and then click to clear the Use a proxy server check box. 4. Make sure that the Automatically detect settings check box is selected. 5. Click OK two times to close the Internet Properties dialog box. · Try running Windows Update again, continue if it does not work. · Perform a clean boot on your computer, based on your operating system: Try to update from the Windows Update site after you start your computer by using the appropriate clean boot method that is mentioned in the following Microsoft Knowledge Base articles: For more information about how to perform a clean boot Windows XP and in Windows 2003, click the following article number to view the article in the Microsoft Knowledge Base: 310353 (http://support.microsoft.com/kb/310353/) How to perform a clean boot in Windows XP For more information about how to perform a clean boot in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base: 281770 (http://support.microsoft.com/kb/281770/) How to perform clean-boot troubleshooting for Windows 2000 For more information about how to perform a clean boot in Windows Millennium Edition, click the following article number to view the article in the Microsoft Knowledge Base: 267288 (http://support.microsoft.com/kb/267288/) How to perform a clean boot in Windows Millennium Edition For more information about how to perform a clean boot in Windows 98, click the following article number to view the article in the Microsoft Knowledge Base: 192926 (http://support.microsoft.com/kb/192926/) How to perform Clean-Boot troubleshooting for Windows 98 · Check to see if the Automatic Updates is enabled: 1. Right-click My Computer and select Properties 2. Select the Automatic Updates tab and make sure that Automatic is selected, and then click OK. Note: This does not apply to Windows 98. · Try running Windows Update again, continue if it does not work. · Check to see if Automatic Updates is service is running: 1. Click Start, and then click Run. 2. Type “services.msc” without the quotes and press enter. 3. The Services window should pop-up. Under the name column find Automatic Updates. If it does not appear there skip over this bullet, if it is double-click on it. 4. The properties dialog should open up. Make sure it says “Automatic” in the Startup type box and the Service status says “Started”. Note: This does not apply to Windows 98, ME. · Try running Windows Update again, continue if it does not work. · Register the DLL files: 1. Click Start, and then click Run. 2. Type “command” (or “cmd” on non-98/ME OS) without the quotes and press enter. 3. Type in the following and press enter after each line: o REGSVR32 %windir%\system32\wuapi.dll o REGSVR32 %windir%\system32\wuaueng.dll o REGSVR32 %windir%\system32\atl.dll o REGSVR32 %windir%\system32\wucltui.dll o REGSVR32 %windir%\system32\wups.dll o REGSVR32 %windir%\system32\qmgr.dll o REGSVR32 %windir%\system32\qmgrprxy.dll o Enter “exit” and press enter. · Try running Windows Update again, continue if it does not work. · Troubleshoot network connection issues: Detection failure may be caused by network connection issues. If you have a second computer that is connected to the Internet, try using the other computer to access the Windows Update Web site. If you cannot use the Windows Update installation process because your computer is behind a proxy server and the proxy server is preventing the Windows Update installation process from working correctly, you may have to contact your network administrator or your Internet service provided (ISP) to obtain assistance in bypassing or in configuring the proxy server. · Try running Windows Update again, if Windows Update continues not to work please email me your WindowsUpdate.log file. To gather your WindowsUpdate.log file: 1. Select Start, and then click Run. 2. Type “%windir%” and press enter. The WindowsUpdate.log file will be located in this folder. Please email this file along with as much information about your issue (error messages and numbers) to NOSPAM.bbodenmiller@hotmail.com.NOSPAM. -- Ben B. [US] "Sperrin" <Sperrin@discussions.microsoft.com> wrote in message news:452E327A-AD9E-4847-A049-1577D30DFEFE@microsoft.com... >I receive Error 0x80244019 in the Windows Update.log when getting updates > from a local server running Windows Update Server. The client workstation is > XP SP2 and I have disabled the firewall. The server is in this building and > there is not firewall or proxy server blocking communication. > > Here is the WindowsUpdate.log from the last time I tried to receive updates. > > 2005-04-29 10:01:10-0400 1824 734 Successfully opened event cache file at > C:\WINDOWS\SoftwareDistribution\EventCache\{3BD629 82-7F06-4861-B489-4A9917C474E8}.bin for reading. > 2005-04-29 10:01:10-0400 2232 ca4 Trying to make out of proc datastore active > 2005-04-29 10:01:11-0400 2232 ca4 Out of proc datastore is now active > 2005-04-29 10:01:11-0400 1824 734 PT: Using serverID > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} > 2005-04-29 10:01:11-0400 1824 734 PT: Using server URL > http://eqbobmcapp01/ClientWebService/client.asmx > 2005-04-29 10:01:11-0400 1824 734 PT: Calling GetConfig on server > 2005-04-29 10:01:11-0400 1824 734 Add header for accept-encoding: xpress > succeeded > 2005-04-29 10:01:11-0400 1824 734 DetectCompressionType returning type 0, > hr=0x1 > 2005-04-29 10:01:11-0400 1824 734 GetConfig: 0x80244019 > 2005-04-29 10:01:11-0400 1824 734 PT: Cannot recover from fault, > origin=GetConfig, hr=0x80244019 > 2005-04-29 10:01:11-0400 1824 734 Failed to obtain cached cookie with hr = > 80244019. > 2005-04-29 10:01:11-0400 1824 734 Failed to upload events with hr = 80244019. > 2005-04-29 10:06:11-0400 2232 ca4 Out of proc datastore is shutting down > 2005-04-29 10:06:12-0400 2232 ca4 Out of proc datastore is now inactive > 2005-04-29 10:11:11-0400 1824 338 Successfully opened event cache file at > C:\WINDOWS\SoftwareDistribution\EventCache\{3BD629 82-7F06-4861-B489-4A9917C474E8}.bin for reading. > 2005-04-29 10:11:11-0400 3152 f08 Trying to make out of proc datastore active > 2005-04-29 10:11:12-0400 3152 f08 Out of proc datastore is now active > 2005-04-29 10:11:12-0400 1824 338 PT: Using serverID > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} > 2005-04-29 10:11:12-0400 1824 338 PT: Using server URL > http://eqbobmcapp01/ClientWebService/client.asmx > 2005-04-29 10:11:12-0400 1824 338 PT: Calling GetConfig on server > 2005-04-29 10:11:12-0400 1824 338 Add header for accept-encoding: xpress > succeeded > 2005-04-29 10:11:12-0400 1824 338 DetectCompressionType returning type 0, > hr=0x1 > 2005-04-29 10:11:12-0400 1824 338 GetConfig: 0x80244019 > 2005-04-29 10:11:12-0400 1824 338 PT: Cannot recover from fault, > origin=GetConfig, hr=0x80244019 > 2005-04-29 10:11:12-0400 1824 338 Failed to obtain cached cookie with hr = > 80244019. > 2005-04-29 10:11:12-0400 1824 338 Failed to upload events with hr = 80244019. > 2005-04-29 10:16:12-0400 3152 f08 Out of proc datastore is shutting down > 2005-04-29 10:16:13-0400 3152 f08 Out of proc datastore is now inactive > 2005-04-29 10:21:12-0400 1824 368 Successfully opened event cache file at > C:\WINDOWS\SoftwareDistribution\EventCache\{3BD629 82-7F06-4861-B489-4A9917C474E8}.bin for reading. > 2005-04-29 10:21:12-0400 968 b58 Trying to make out of proc datastore active > 2005-04-29 10:21:13-0400 968 b58 Out of proc datastore is now active > 2005-04-29 10:21:13-0400 1824 368 PT: Using serverID > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} > 2005-04-29 10:21:13-0400 1824 368 PT: Using server URL > http://eqbobmcapp01/ClientWebService/client.asmx > 2005-04-29 10:21:13-0400 1824 368 PT: Calling GetConfig on server > 2005-04-29 10:21:13-0400 1824 368 Add header for accept-encoding: xpress > succeeded > 2005-04-29 10:21:13-0400 1824 368 DetectCompressionType returning type 0, > hr=0x1 > 2005-04-29 10:21:13-0400 1824 368 GetConfig: 0x80244019 > 2005-04-29 10:21:13-0400 1824 368 PT: Cannot recover from fault, > origin=GetConfig, hr=0x80244019 > 2005-04-29 10:21:13-0400 1824 368 Failed to obtain cached cookie with hr = > 80244019. > 2005-04-29 10:21:13-0400 1824 368 Failed to upload events with hr = 80244019. > 2005-04-29 10:26:13-0400 968 b58 Out of proc datastore is shutting down > 2005-04-29 10:26:15-0400 968 b58 Out of proc datastore is now inactive > 2005-04-29 10:31:13-0400 1824 694 Successfully opened event cache file at > C:\WINDOWS\SoftwareDistribution\EventCache\{3BD629 82-7F06-4861-B489-4A9917C474E8}.bin for reading. > 2005-04-29 10:31:14-0400 3168 844 Trying to make out of proc datastore active > 2005-04-29 10:31:14-0400 3168 844 Out of proc datastore is now active > 2005-04-29 10:31:14-0400 1824 694 PT: Using serverID > {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} > 2005-04-29 10:31:14-0400 1824 694 PT: Using server URL > http://eqbobmcapp01/ClientWebService/client.asmx > 2005-04-29 10:31:14-0400 1824 694 PT: Calling GetConfig on server > 2005-04-29 10:31:14-0400 1824 694 Add header for accept-encoding: xpress > succeeded > 2005-04-29 10:31:17-0400 1824 694 DetectCompressionType returning type 0, > hr=0x1 > 2005-04-29 10:31:17-0400 1824 694 GetConfig: 0x80244019 > 2005-04-29 10:31:17-0400 1824 694 PT: Cannot recover from fault, > origin=GetConfig, hr=0x80244019 > 2005-04-29 10:31:17-0400 1824 694 Failed to obtain cached cookie with hr = > 80244019. > 2005-04-29 10:31:17-0400 1824 694 Failed to upload events with hr = 80244019. > 2005-04-29 10:36:15-0400 3168 844 Out of proc datastore is shutting down > 2005-04-29 10:36:16-0400 3168 844 Out of proc datastore is now inactive > 2005-04-29 10:39:57-0400 1824 724 Service received SERVICE_CONTROL_STOP > control > 2005-04-29 10:39:57-0400 1824 80 Exiting Service Main > 2005-04-29 10:39:57-0400 812 f1c Trying to make out of proc datastore active > 2005-04-29 10:39:58-0400 812 f1c Out of proc datastore is now active > 2005-04-29 10:39:58-0400 812 f1c Out of proc datastore is shutting down > 2005-04-29 10:39:58-0400 1824 80 WUAUENG ServiceMain exits. Exit code is > 0x240001 > 2005-04-29 10:39:58-0400 2512 9c0 ChangeServiceConfig for wuauserv succeeded > 2005-04-29 10:39:59-0400 812 f1c Out of proc datastore is now inactive |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "Windows Update Error 0x80244019 connecting to local Windows Update" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Error 0X80244019 in Windows Update | Jerry | Windows Update | 8 | 12-02-2009 03:13 AM |
| Windows Update Error Message 0X80244019 | gerrypotter | Windows Update | 2 | 27-12-2008 09:19 PM |
| Vista Update (error found: Code 0x80244019) | Prijesh | Windows Update | 2 | 03-12-2008 02:25 AM |
| 0x80244019 error on update.microsoft.com | nerochen | Windows Update | 5 | 09-10-2007 06:04 PM |
| WSUS Problem - Error connecting to the Windows Server Update Servi | Jeff Baublitz | Server Update Service | 15 | 17-12-2006 02:19 PM |