Failed To Get Session From Datastore Error 0x80004002
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 12:16:21 GMT by s_wx1094 (squid/3.5.20)
WSUS 3 Server View New Content Page 1 of 1 You cannot start a new topic You cannot reply to this topic Datastore issue / InitAUComponents failed on some clients #1 data1025 Newbie Group: New Members Posts: 1 Joined: 13-Nov-07 Posted 13 Nov 2007, 07:49 We recently upgraded from 2.0 to 3.0 (actually a reinstall since we were running x32bit 2.0 and moved to x64 3.0), and 80% of our clients are checking in and working fine. There are some, however, that checked in initially but have not checked in since then. There is nothing "different" about the build/OS of the 20% that have http://answers.microsoft.com/en-us/windows/forum/windows_other-update/windows-update-0x80004002/8a11757b-84b2-421c-a375-7b6f5181ce70 not checked in. They are all XP SP2, just like the 80%. I have been searching for about a week and tried the following: - Stop wuauserv, re-register DLL's, start service. - Stop wuauserv, delete Software Dist. folder and windowsupdate.log, start service. - delete PC from WSUS console - Reboot, wuauclt /detectnow, /register, /reportnow, etc. etc. etc. Any ideas? Here is the log of one of our PCs: 2007-11-13 09:03:22:540 892 http://www.wsus.info/index.php?showtopic=11135 724 AU ########### AU: Initializing Automatic Updates ########### 2007-11-13 09:03:22:590 892 724 AU AU setting next detection timeout to 2007-11-13 14:03:22 2007-11-13 09:03:24:803 892 724 Agent WARNING: GetServiceList failed with error 0x80004002. 2007-11-13 09:03:24:803 892 724 AU WARNING: QueryRegisteredProvider failed with error 0x80004002 2007-11-13 09:03:24:803 892 724 AU # WSUS server: HTTP://HPE16SFP295001 2007-11-13 09:03:24:803 892 724 AU # Detection frequency: 10 2007-11-13 09:03:24:803 892 724 AU # Approval type: Scheduled (Policy) 2007-11-13 09:03:24:803 892 724 AU # Scheduled install day/time: Tuesday at 20:00 2007-11-13 09:03:24:803 892 724 AU # Auto-install minor updates: Yes (Policy) 2007-11-13 09:03:29:329 892 724 AU FATAL: Failed to get session from datastore, error = 0x80004002 2007-11-13 09:03:29:359 892 724 AU FATAL: Failed to Unserialize from data store, error = 0x80004002 2007-11-13 09:03:29:359 892 724 AU # WARNING: Exit code = 0x80004002 2007-11-13 09:03:29:369 892 724 AU WARNING: InitAUComponents Failed, will restart AU in 30 mins, error = 0x80004002 2007-11-13 09:03:29:369 892 724 AU AU Restart required.... 2007-11-13 09:03:29:369 892 724 Report *********** Report: Initializing static reporting data *********** 2007-11-13 09:03:29:369 892 724 Report * OS Version = 5.1.2600.2.0.65792 2007-11-13 09:03:32:914 892 724 Report * Computer Brand = Dell Computer Corporation 2007-11-13 09:03:32:914 892 724 Report * Computer Model = OptiPlex GX1 500L 2007-11-13 09:03:32:944 892 724 Repor
it means that Windows ran into a problem and had to shut down abnormally to prevent further damage to your PC or even loss of valuable data. However, don't hurry to call to PC repair http://www.0x0000007b.info/resolving-codes/failed-to-get-session-from-datastore-error-0x80004002.html services and pay from $250 to $450 for things you can easily do on your own at little or no cost). If you are not a PC expert use the following first-aid solutions: Solution 1: Highly recommended http://blog.ranjangaur.com/2009/01/windows-update-error-0x80004002.html if you can start Windows at least in Safe Mode: Free Download the Fix for 'Failed To Get Session From Datastoerror 0x80004002' This is my favorite tool so far because it has never failed me and failed to fixed failed to get session from datastoerror 0x80004002 and all other errors I had It automatically fixes a wide range of computer problems, such as failed to get session from datastoerror 0x80004002 and other errors, blue screens, crashes, freezes, system file and registry damage, .dll and .sys file errors, privacy issues and other troubles. This tool is widely used even by PC technicians to fix Windows errors and repair damaged systems! Another, very important failed to get reason why I highly recommend this tool is that with it I don't even have to upgrade my computer! The third (but not the last) reason is that even PC technicians use this tool to automatically remove Windows errors and fix the damaged systems. Simply let it scan your computer and remove the errors. Solution 2: Recommended if you cannot enter Windows because of the error at startup or logon: Use This 1-Clik Fix Tool 1-Clik Fix Utilities fixes computers that won't boot because of a blue screen error message, black screen, boot loop, "ntldr is missing", "bootmgr is missing", "operating system not found" and other error messages. It also eliminates about 100% of problems that cause boot error messages and slow performance. Start 1-Clik Fix Utilities and follow the simple direction on the screen. When you access your broken system let Utilities fix the errors to prevent problems in future Fix Everything Yourself And Save Hundreds Of Dollars! failed to get session from datastore error 0x80004002 "Failed to get session from datastore error 0x80004002" code is greater than only a shame, that's a fatal OS crash. You won't have time to lose if you come across a blue screen problem. failed to get session from datastore error 0x80004002 - When Os Is Disobliging Queued: Problem: Windows XP
seeing the following errors in "%Windir%\WindowsUpdate.log". FATAL: Failed to get session from datastore, error = 0x80004002FATAL: Failed to Unserialize from data store, error = 0x80004002WARNING: Exit code = 0x80004002WARNING: InitAUComponents Failed, will restart AU in 30 mins, error = 0x80004002DnldMgr FATAL: DM:CAgentDownloadManager::CheckAllCallDownloadStates: GetSession failed with 0x80004002. Try the following steps:Rename/Delete "%Windir%\WindowsUpdate.log" before you start to see the latest detection. 1. If you have a proxy server - Stop Automatic Update Service - "Net stop wuauserv". Run the following command:"proxycfg.exe -u". Start Automatic Update Service - "Net start wuauserv". Force update detection and see if that works. 2. Re-create the Datastore - Stop Automatic Update Service - "Net stop wuauserv". Rename/delete "%Windir%\SoftwareDistribution" folder. Start Automatic Update Service - "Net start wuauserv". Force update detection and see if that works. 3. Try to force install WUA. Download WUA WindowsUpdateAgent20-x86.exe from http://go.microsoft.com/fwlink/?LinkId=43264. and run the following command: "WindowsUpdateAgent20-x86.exe /wuforce".If nothing works you can always post your results from "%Windir%\WindowsUpdate.log" on microsoft.public.windows.server.update_services.
Posted by Ranjan at 7:19 PM Labels: Error 0x80004002, windows update 0 comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) RSS Posts Atom Posts Comments Atom Comments About Me Ranjan email: me at ranjangaur dot com View my complete profile Blog Archive ▼ 2009 (18) ► July (2) ► May (6) ► February (1) ▼ January (9) Permissions with Vmware ESX Server 3.5 The curious case of missing DLL Non Paged Pool Memory followup Windows Update Error 0x80004002 Up Up and Away The Tubes are full Windows 7 Oracle Server Non paged pool memory error Happy new year everyone ! Seen this one before ? O... ► 2008 (1) ► December (1) Labels 10.2.0.2 (1) Active Directory (1) cdprobe.sys (1) defrag (1) Domain Controller (1) Error 0x80004002 (1) ESX 3.5 (1) event id 1202 (1) Event ID: 2019 (1) Event ID: 6008 (1) Event ID: 6012 (1) Exchange 2003 (2) IO SYSTEM VERIFICATION ERROR (1) iSCSI (1) Jet (1) LUN (1) memtriage (1) mfc71u.dll (1) nonpaged pool (2) Ntfs.sys (1) Oracle (2) poolmon (2) Replication (1) Richcopy (1) SAN (1) Starwind (1) stop 0xD5 (1) Symantec EPM (1) The Practical Guide to Defect Prevention (1) verifier (1) Windbg (1) WIndows 2003 (