Error 25001 Setup Failed Due To Unexpected
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home2012Previous VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error 25001. Setup failed due to unexpected circumstances System Center Configuration Manager > Configuration Manager 2007 General
Ccmsetup Failed With Error Code 0x80041010
Question 0 Sign in to vote Hi I am having issues with about 20 ccmgetosversion failed with 0x80041010 of my servers, all in the sameexternaldomain in an external forest. I manage these servers as workgroup machines. The issue
Checkandlogosinformation Failed With 0x80041010
has gone unnoticed fora while. The issue is as follows. The Config Mgr agent is installed on all the servers but if you open it there are several things missing. Under the General tab failed to get client version for sending messages to fsp. error 0x80041010 somethings looks good except that it cannot detect the site mode , there is no site code(and it cannot detect it), there is no listed management point and connection type is set to currently internet. Under the components tab the components are listed as Installed but none are enabled. Under the Actions tab only two options are listed, Machine PolicyRetrieval& Evaluation Cycle and User PolicyRetrieval & Evaluation Cycle. Under ccmgetosversion failed with 0x80041010 ccmsetup the Advanced tab there is no site code set.In my Config Mgr console the servers are not listed at all, that could be because they have been removed because they are inactive after 90 days. There are several agents in the same subnet, in the same domain and forest that work fine. All the servers are 2008 R2 and have been deployed and installed from SCCM. I have two questions: How do I fix this and is it possible to detect these kind of issues? Hope someone can help :) Edit: Forgot to add that if you reinstall or try to repair the agent you get the following error message:Error 25001. Setup failed due to unexpected circumstances Edited by Nico_ Friday, February 03, 2012 1:33 PM Friday, February 03, 2012 12:33 PM Reply | Quote Answers 0 Sign in to vote Ok looks like i figured this out. The servers having problemsre installingthe agent had shared configuration enabled on the IIS. This prevented the Config Mgr agent from being installed. Once I disabled shared config it was possible to re install the agent properly. So I was able to fix the issue but I was not able toidentifythe root
a Service Our Company Work Here Contact Us HomeInfrastructure James Avery July 1, 2009 Infrastructure 6 Comments Tweet SCCM Client Installation Error 80041001 While upgrading workstations from SMS client to SCCM client, I ran into several workstations having WMI errors in the
Ccmgetosversion Failed With 0x8004100e
CCMSETUP.LOG file, specifically; "MSI: Warning 25001. Setup failed due to unexpected circumstance. The error failed to get client version for sending state messages. error 0x80041010 code is 80041001" I was able to resolve this by following the process outlined below. Uninstall the SCCM client by running
Sccm 0x80041010
"%WinDir%\System32\ccmsetup\ccmsetup.exe /uninstall" Click on Start -> Run -> Type "services.msc" ->
go fine..... http://www.networksteve.com/enterprise/topic.php/MSI:_Setup_failed_due_to_unexpected_circumstances_The_Error_Code/?TopicId=14115&Posts=0 but at the End of it I get the last Two lines and it just stops. -------------------------Start CCMSETUP.LOG------------------------- Version: 4.0.6487.2000 Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. "Command failed with line: ""C:\WINDOWS\system32\ccmsetup\ccmsetup.exe"" /runservice /config:MobileClient.tcf" CCMHTTPPORT: 80 CCMHTTPSPORT: 443 CCMHTTPSSTATE: 0 CCMHTTPSCERTNAME: FSP: CCMFIRSTCERT: 0 Config file: C:\WINDOWS\system32\ccmsetup\MobileClient.tcf Retry time: 10 minute(s) MSI log file: "MSI properties: INSTALL=""ALL"" SMSSITECODE=""HS1"" SMSCACHESIZE=""2048"" CCMHTTPPORT=""80"" CCMHTTPSPORT=""443"" CCMHTTPSSTATE=""0"" CCMFIRSTCERT=""0""" Source List: \\SCCMSERVER.SOMEDOMAIN.BIZ\SMSClient \\SCCMSERVER\SMSClient MPs: ccmgetosversion failed with SCCMSERVER.SOMEDOMAIN.BIZ Updated security on object C:\WINDOWS\system32\ccmsetup\. A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. "Running as user ""SYSTEM""" Detected 36580 MB free disk space on system drive. DetectWindowsEmbeddedFBWF() Detecting OS Version "Client OS Version is 5.1, Service Pack Version 2" Client OS is not a supported Windows Embedded Platform Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. Deleted file C:\WINDOWS\system32\ccmsetup\client.msi Successfully ran BITS check. IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\ccmsetup.cab' is MS signed. Successfully extracted manifest file C:\WINDOWS\system32\ccmsetup\ccmsetup.xml from file C:\WINDOWS\system32\ccmsetup\ccmsetup.cab. Loading manifest file: C:\WINDOWS\system32\ccmsetup\ccmsetup.xml Successfully loaded ccmsetup manifest file. "Adding file 'http://SCCMSERVER.SOMEDOMAIN.BIZ:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\WIN