Jump to content


TronixS

Established Members
  • Posts

    31
  • Joined

  • Last visited

Everything posted by TronixS

  1. No one a Tipp or Hint for me?!
  2. No, all Systems are the Same Problem, when i make a Big ALLUPDATES File find the Client over 30 or more Patches, it looks fine but the Client makes nothing. When i split many Updates in little Parts runs this, the Client detect Updates and install them. The Windows Update Agent is the last and ends with .788 (from Oktober). thx.
  3. Okay, Error Code 0x8007057 is a Probleme when a client becomes a lot of Updates or Patches. My Version was .784 but i must upgrade to .788 (it´s WindowsUpdater x86 http://support.microsoft.com/kb/949104 ) I did it but after a Reboot with the new installer is there a same Error in UpdaterHandler.log Updates scan completion received, result = 0x80070057. UpdatesHandler 10.11.2008 14:02:49 2400 (0x0960) omg
  4. Okay, this is strange, now i had a "normal" Windows Update Message to Install KB898461 per Express or from Hand. but i have now enough logs and post them as files in a ZIP. in the SCANAGENT.LOG is this a Part of Error. *****WSUSLocationUpdate received for location request guid={8140EB31-A06D-4B91-AF27-D4BA388472B5} ScanAgent 10.11.2008 12:07:01 3060 (0x0BF4) - - - - - -Scan completed successfully for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C}, ScanType=1, ContentVersion=59 ScanAgent 10.11.2008 12:10:58 3796 (0x0ED4) - -ScanJob (Online scan request) is completed for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C}. ScanAgent 10.11.2008 12:10:58 3796 (0x0ED4) - -Reporting Scan request complete to clients... ScanAgent 10.11.2008 12:10:58 3796 (0x0ED4) - - Calling back to client on Scan request complete... ScanAgent 10.11.2008 12:10:58 3076 (0x0C04) CScanAgent::ScanComplete- Scan completion received. ScanAgent 10.11.2008 12:10:58 3076 (0x0C04) - -Processing Scan tool history removal request ScanAgent 10.11.2008 12:17:35 4080 (0x0FF0) *****ScanByUpdates request received with ForceReScan=0, ScanOptions=0x00000008, DownloadPriority = 2, LocationTimeout = 604800, DownloadTimeout = 864000, PerDPInactivityTimeout = 0, TotalInactivityTimeout = 0, DPLocalityFlags = 10, ForceInventory=0 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) -Scan will be requested for ToolUniqueID={6BFFF379-09FE-4BFC-B853-2F38804D2AD7} ToolVersion=4.00.6221.1000 ToolName=ConfigMgr-Überprüfungsprogramm für Microsoft Updates ToolContentVersion=5 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) -Scan will be requested for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C} ToolVersion=3.0 ToolName=WSUS Enterprise Server ToolContentVersion=59 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) CScanTool::RequestContentFromCAS - failed at RequestContent for ToolUniqueID {6BFFF379-09FE-4BFC-B853-2F38804D2AD7} with Error=0x80070057 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) Raising event: [sMS_CodePage(850), SMS_LocaleID(1031)] instance of SMS_SUMScanAgentError_ContentDownloadFailed { ClientID = "GUID:3290F89E-192D-425B-9164-62587CA5852E"; ContentID = ""; ContentVersion = "5"; DateTime = "20081110111736.703000+000"; MachineName = "W14739"; ProcessID = 1804; SiteCode = "NDH"; ThreadID = 3692; UpdateSourceUniqueID = "{6BFFF379-09FE-4BFC-B853-2F38804D2AD7}"; UpdateType = "Microsoft Update"; }; ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) CScanTool::Scan- failed at RequestContentFromCAS for ToolUniqueID={6BFFF379-09FE-4BFC-B853-2F38804D2AD7} with Error=0x80070057 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) CScanToolManager::CreateNewScanTool- failed at CScanTool::Scan() with Error=0x80070057 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) CScanToolManager::AddScanTool- failed to create new ScanTool for ScanToolsID={6BFFF379-09FE-4BFC-B853-2F38804D2AD7} with Error=0x80070057 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) CScanJobManager::Scan- failed at AddScanTool for ToolUniqueID={6BFFF379-09FE-4BFC-B853-2F38804D2AD7}, with error=0x80070057, skipping this tool ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) CScanTool::Scan- Requesting Offline Scan for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C} with last known location and version=59 ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) - - - -Scan request is queued for ToolUniqueID={7C7DE67C-8C3A-42EA-A627-039624445B7C} ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) - -1 Scan requests added, creating Scan-Job to track these scan requests. ScanAgent 10.11.2008 12:17:36 3692 (0x0E6C) Message received: '<?xml version='1.0' ?> <UpdateSourceMessage MessageType='ScanByUpdateSource'> <ForceScan>TRUE</ForceScan> <UpdateSourceIDs> <ID>{7C7DE67C-8C3A-42EA-A627-039624445B7C} </ID> </UpdateSourceIDs> </UpdateSourceMessage>' ScanAgent 10.11.2008 12:17:51 2268 (0x08DC) Big Thx for help and sorry for my bad english André Logs.zip
  5. Ok, i install directly a new Workstation with XP SP2 and Office 2003 SP1, then i will try a automaticly update and post the Reports. The ConfigMgr Clientversion 4.0.0.6221.1000 our Consulting tells us that is normal to deploy not all Updates (28max Patches) as one Pak, we must do more Groups for Deployupdates in more Steps. i can´t believe this, in my test with WSUS 3.01 i don´t have this Problems but our Firma would take SCCM 2007 and in background runs WSUS 3.01...... Okay, in ca. 60Min, the Client is Ready and i will Post the Logs... Big thx for this time.
  6. Hello, we are testing SCCM 2007 SP1 R2 to installing Clients (WXP SP 1 / SP 2 / SP 3 and Vista) but there are many Problems. We have a little Group of Maschines they are installing with no Problems and other doesn´t run, the find many updates (60 - 75) but they do nothing. the Logs are not really helpful. The SCCM Client for our Test i deploy per GPO what goes fine. Now i would find anyone where has same Problems or Tipps to fix it. A College tells me i should create more Update Packages for the deploy but i don´t will do this, it is more Work for me. Big thx for helpful informations..... with best regards........ André
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.