client install issues

client install issues (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager

Message

pappatoad -> client install issues (4/17/2008 10:51:50 AM)
I am having difficulties with installing the sccm client on the machines. I have Bits enabled but I know it needs the www service also enable in IIS....here is where I am having difficulty...I am trying to enable this feature on a local machine to test if it will work....but the local machine keeps telling me in order to install these features it needs certain files from the windows xp sp2 disk....so I insert it....it tells me over and over it can not copy the files....even from an admin file on our server or copying the entire I386 file from the disk to the local machine and pointing it to that location it keeps telling me it cant install it.....and without getting these HTTP services running...the new sccm client will not install. The log files keep telling me that the ccmsetup.exe fails at the HTTP request portion. Anyone got any ideas on how to force the acceptance of the changes to IIS on the local machine? I have tried both the local admin and domain admin accounts I have and keep getting the same error.

phaustein -> RE: client install issues (4/21/2008 7:20:34 PM)
I am not really sure what you are trying to do but here are some questions. When you are being prompted for the source files, are you using the same OS service pack level that is being prompted for? This could be one reason it will not let you install the files. You are refering to problems with IIS, is that on your MP or the XP Sp2 system? From what I can gather, the problem is with the client not detecting the MP, is that correct?

pappatoad -> RE: client install issues (4/22/2008 11:07:43 AM)
I believe I have found part of the issue involved with this error. To answer your questions...yes we are using the same OS level and service pack...actually from the same CD. I believe we have a problem with IIS on our server that is the MP. I used another computer from our old sms r2 install and updated the bits and webdav setings in it, then tried to update the client. Still failed. I believe it is an issue with our IIS on our server.....I have told my co-worker here (my boss) that we needed the webdav installed in IIS on the server as well and he said no. So after that I checked it and it was installed the next day....but I have a tricky feeling that it was not done correctly. I know we should have uninstalled the MP, uninstalled IIS, reboot, install IIS with all correct functions....reboot....then install the MP. This process I am betting was not followed at at. I have also noted that when we use SCCM to image a computer....the client is not getting installed as it should. It is not even showing up in the local computer's control panel. So all of this including having a mchine that has the correct bits and iis locally installed, is still having issues getting the client installed and the issue today of getting the client installation to get about 90% complete then cause an error saying "Setup was unavle to create the WMI namspace CCM The error code is 80040154" This is all pointing back to WMI on the server.....but I could just be guessing.

phaustein -> RE: client install issues (4/22/2008 1:19:03 PM)
It sounds like you may have a WMI corruption or a bad client install source. Try repairing WMI and or trying a fresh install of the client from a new source, to test.

pappatoad -> RE: client install issues (4/22/2008 1:57:48 PM)
we had errors with wmi last time when we upgraded to sms r2.....so will have to do that.....thanks....just was looking for some confirmation to my thoughts since my coworker dissagrees...lol

pappatoad -> RE: client install issues (4/22/2008 2:49:47 PM)
I do have another question. I am using a WMI checker on several local test machines....each one is coming up with errors in the WMI install....some say WMI is functioning as it should even with the errors ....others say will not work untill errors are fixed. Now to fix the WMI....is that done on each local machine? or is that handled through the deployment server? I am pretty sure that the WMI on our deplyment server is corrupted....but not real sure how to recover/ reinstall a corrected WMI. Any suggestions?

phaustein -> RE: client install issues (4/22/2008 2:58:06 PM)
If you are using WMDIAG, I would recommend following the instructions it provides. If WMI is getting corrupt from the image, then the image itself may need to be looked at. What are the results of runnning WMIDIAG on the deployment server?

pappatoad -> RE: client install issues (4/22/2008 3:27:17 PM)
I have run WMDIAG on clients but not the server yet....will do that and let you know here shortly

pappatoad -> RE: client install issues (4/22/2008 3:42:19 PM)
I have run the WMDIAG on the server....if I am reading the log correctly....there are errors preventing WMI from working correctly. what will I be looking for in the log tp be more precise? I browsed through it and found several places where it says there are errors....but not sure how to interperet them. Shall I post the last portion of the log?

phaustein -> RE: client install issues (4/22/2008 3:54:08 PM)
Go ahead and post the log.

pappatoad -> RE: client install issues (4/22/2008 4:44:10 PM)
it is not allowing me to post the log....even half of it....so here is the tail end of it..... 63405 13:28:56 (0) WMI TIMER instruction(s): ........................................................................................... NONE. 63406 13:28:56 (0) INFO: WMI ADAP status: .............................................................................................. 1. 63407 13:28:56 (0) => The WMI ADAP process is currently running (1). 63408 13:28:56 (0) Some WMI performance classes could be missing at the time WMIDiag was executed. 63409 13:28:56 (0) INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 2 NAMESPACE(S)! 63410 13:28:56 (0) - ROOT/SERVICEMODEL. 63411 13:28:56 (0) - ROOT/MICROSOFTIISV2. 63412 13:28:56 (0) => When remotely connecting, the namespace(s) listed require(s) the WMI client to 63413 13:28:56 (0) use an encrypted connection by specifying the PACKET PRIVACY authentication level. 63414 13:28:56 (0) (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags) 63415 13:28:56 (0) i.e. 'WMIC.EXE /NODE:"TRITON" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\MICROSOFTIISV2 Class __SystemSecurity' 63416 13:28:56 (0) 63417 13:28:56 (0) WMI MONIKER CONNECTIONS: ............................................................................................ OK. 63418 13:28:56 (0) WMI CONNECTIONS: .................................................................................................... OK. 63419 13:28:56 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 1 ERROR(S)! 63420 13:28:56 (0) - root/ccm/DataTransferService, CCM_DTS_JobItem, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found. 63421 13:28:56 (0) MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)' 63422 13:28:56 (0) 63423 13:28:56 (0) WMI MOF representations: ............................................................................................ OK. 63424 13:28:56 (0) WMI QUALIFIER access operations: .................................................................................... OK. 63425 13:28:56 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 1 ERROR(S)! 63426 13:28:56 (0) - ROOT/CIMV2/SMS, InstancesOfAsync, 'SMS_Class_Template', 0x80041011 - (WBEM_E_PROVIDER_NOT_FOUND) Provider referenced in the schema does not have a corresponding registration. 63427 13:28:56 (0) MOF Registration: 'WMI information not available (This could be the case for an external application or a third party WMI provider)' 63428 13:28:56 (0) 63429 13:28:56 (1) !! ERROR: WMI EXECQUERY operation errors reported: ..................................................................... 4 ERROR(S)! 63430 13:28:56 (0) ** - root/ccm/Policy/machine, 'Select * From CCM_ClientActions WHERE ActionID = "{8EF4D77C-8A23-45c8-BEC3-630827704F51}"' did not return any instance while AT LEAST 1 instance is expected. 63431 13:28:56 (0) ** - root/ccm/Policy/machine, 'Select * From CCM_ClientActions WHERE ActionID = "{3A88A2F3-0C39-45fa-8959-81F21BF500CE}"' did not return any instance while AT LEAST 1 instance is expected. 63432 13:28:56 (0) ** - root/ccm/Policy/machine, 'Select * From CCM_ClientProperties' did not return any instance while AT LEAST 1 instance is expected. 63433 13:28:56 (0) ** - ROOT/CCM/Policy/machine, 'Select * From InventoryClientAuthenticationConfig' did not return any instance while AT LEAST 1 instance is expected. 63434 13:28:56 (0) 63435 13:28:56 (0) WMI GET VALUE operations: ........................................................................................... OK. 63436 13:28:56 (0) WMI WRITE operations: ............................................................................................... NOT TESTED. 63437 13:28:56 (0) WMI PUT operations: ................................................................................................. NOT TESTED. 63438 13:28:56 (0) WMI DELETE operations: .............................................................................................. NOT TESTED. 63439 13:28:56 (0) WMI static instances retrieved: ..................................................................................... 4762. 63440 13:28:56 (0) WMI dynamic instances retrieved: .................................................................................... 0. 63441 13:28:56 (0) WMI instance request cancellations (to limit performance impact): ................................................... 2. 63442 13:28:56 (0) ---------------------------------------------------------------------------------------------------------------------------------- 63443 13:28:56 (0) # of Event Log events BEFORE WMIDiag execution since the last 20 day(s): 63444 13:28:56 (0) DCOM: ............................................................................................................. 283. 63445 13:28:56 (0) WINMGMT: .......................................................................................................... 7. 63446 13:28:56 (0) WMIADAPTER: ....................................................................................................... 0. 63447 13:28:56 (0) => Verify the WMIDiag LOG at line #61887 for more details. 63448 13:28:56 (0) 63449 13:28:56 (0) # of additional Event Log events AFTER WMIDiag execution: 63450 13:28:56 (0) DCOM: ............................................................................................................. 0. 63451 13:28:56 (0) WINMGMT: .......................................................................................................... 0. 63452 13:28:56 (0) WMIADAPTER: ....................................................................................................... 0. 63453 13:28:56 (0) 63454 13:28:56 (0) 1 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found 63455 13:28:56 (0) => This error is typically a WMI error. This WMI error is due to: 63456 13:28:56 (0) - a missing WMI class definition or object. 63457 13:28:56 (0) (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures). 63458 13:28:56 (0) You can correct the missing class definitions by: 63459 13:28:56 (0) - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command. 63460 13:28:56 (0) Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag. 63461 13:28:56 (0) (This list can be built on a similar and working WMI Windows installation) 63462 13:28:56 (0) The following command line must be used: 63463 13:28:56 (0) i.e. 'WMIDiag CorrelateClassAndProvider' 63464 13:28:56 (0) - a WMI repository corruption. 63465 13:28:56 (0) In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter 63466 13:28:56 (0) to validate the WMI repository operations. 63467 13:28:56 (0) Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before 63468 13:28:56 (0) executing the WriteInRepository command. To write temporary data from the Root namespace, use: 63469 13:28:56 (0) i.e. 'WMIDiag WriteInRepository=Root' 63470 13:28:56 (0) - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces 63471 13:28:56 (0) the WMI repository must be reconstructed. 63472 13:28:56 (0) Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository, 63473 13:28:56 (0) otherwise some applications may fail after the reconstruction. 63474 13:28:56 (0) This can be achieved with the following command: 63475 13:28:56 (0) i.e. 'WMIDiag ShowMOFErrors' 63476 13:28:56 (0) Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing 63477 13:28:56 (0) ALL fixes previously mentioned. 63478 13:28:56 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory) 63479 13:28:56 (0) 63480 13:28:56 (0) 63481 13:28:56 (0) 1 error(s) 0x80041011 - (WBEM_E_PROVIDER_NOT_FOUND) Provider referenced in the schema does not have a corresponding registration 63482 13:28:56 (0) => This error is typically due to the following major reasons: 63483 13:28:56 (0) - The application queried by the WMI provider is not installed, not available or not running 63484 13:28:56 (0) at the time of the request was made. This error can also be generated because 63485 13:28:56 (0) the application supporting the providers has been uninstalled. 63486 13:28:56 (0) - Some WMI providers (i.e. RSOP Planning Mode, Exchange 2003) are implemented as a WMI service. 63487 13:28:56 (0) Make sure the required services are successfully started. 63488 13:28:56 (0) - The WMI provider binary files are not accessible (i.e. access denied ACL). 63489 13:28:56 (0) - A WMI provider registration problem at the CIM level (MOFCOMP.EXE) or at the COM level (REGSVR32.EXE). 63490 13:28:56 (0) You must re-register the WMI provider by recompiling its associated MOF file with MOFCOMP.EXE 63491 13:28:56 (0) Note: - If the WMI provider DLL CIM and COM registrations are correct, this error can 63492 13:28:56 (0) be returned because the provider has a dependency on another DLL that cannot be 63493 13:28:56 (0) loaded (missing or bad DLL) 63494 13:28:56 (0) - Dependencies can be found with the DEPENDS.EXE tool coming with the 63495 13:28:56 (0) Windows XP and Windows 2003 Support Tools. The command line is as follows: 63496 13:28:56 (0) i.e. DEPENDS.EXE <PATH><Provider.DLL> 63497 13:28:56 (0) => If the software has been de-installed intentionally, then this information must be 63498 13:28:56 (0) removed from the WMI repository. You can use the 'WMIC.EXE' command to remove the provider 63499 13:28:56 (0) registration data and its set of associated classes. 63500 13:28:56 (0) => To correct this situation, you can: 63501 13:28:56 (0) - Install or start the application supporting these providers. 63502 13:28:56 (0) - Register the providers in CIM (MOFCOMP) or DCOM (REGSVR32). 63503 13:28:56 (0) Note: In this case the provider should also be listed in the 'missing WMI 63504 13:28:56 (0) provider DCOM registrations' or in the 'missing WMI provider files' section. 63505 13:28:56 (2) !! WARNING: Re-registering with REGSVR32.EXE all DLL from 'C:\WINDOWS\SYSTEM32\WBEM\' 63506 13:28:56 (0) may not solve the problem as the DLL supporting the WMI class(es) 63507 13:28:56 (0) can be located in a different folder. 63508 13:28:56 (0) You must refer to the class name to determine the software delivering the related DLL. 63509 13:28:56 (0) 63510 13:28:56 (0) ---------------------------------------------------------------------------------------------------------------------------------- 63511 13:28:56 (0) WMI Registry key setup: ............................................................................................. OK. 63512 13:28:56 (0) ---------------------------------------------------------------------------------------------------------------------------------- 63513 13:28:56 (0) ---------------------------------------------------------------------------------------------------------------------------------- 63514 13:28:56 (0) ---------------------------------------------------------------------------------------------------------------------------------- 63515 13:28:56 (0) ---------------------------------------------------------------------------------------------------------------------------------- 63516 13:28:56 (0) 63517 13:28:56 (0) ---------------------------------------------------------------------------------------------------------------------------------- 63518 13:28:56 (0) ------------------------------------------------------ WMI REPORT: END ----------------------------------------------------------- 63519 13:28:56 (0) ---------------------------------------------------------------------------------------------------------------------------------- 63520 13:28:56 (0) 63521 13:28:56 (0) ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\DOCUMENTS AND SETTINGS\ILK-ADMIN\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_TRITON_2008.04.22_13.12.48.LOG' for details. 63522 13:28:56 (0) 63523 13:28:56 (0) WMIDiag executed in 16 minutes. 63524 13:28:56 (3) 63525 13:28:56 (3) 2.0,4/22/2008,1:12:48 PM,4/22/2008 1:12:48 PM,True,False,False,32-bit,x86 Family 15 Model 2 Stepping 5 GenuineIntel,5.2,3790,Service Pack 2,Windows Server 2003 - No service pack - 32-bit,2003_.SRV.RTM.32,00000409,TRITON,CDE\ILK-ADMIN,False,Root,0,SCSI,0,0,0,0, ,36,1344,36,1336, , , ,0,0,2,0,0,0,35,0,11,0,1, , ,0,0,3,0,58,0,1,2,0,0,1,0,0,1,0,4,0,0,0, , , ,0,4762,2,283,7,0,0,0,0,0,19,5,29,4/22/2008,1:28:56 PM,116,3,8,968,123,28,1,WMIDIAG-V2.0_2003_.SRV.RTM.32_TRITON_2008.04.22_13.12.48.LOG,C:\DOCUMENTS AND SETTINGS\ILK-ADMIN\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_TRITON_2008.04.22_13.12.48.LOG 63526 13:28:56 (3) 63527 13:28:56 (0) WMIDiag v2.0 ended on Tuesday, April 22, 2008 at 13:28 (W:123 E:28 S:1). 63981 13:28:56 (0) TXT file "C:\DOCUMENTS AND SETTINGS\ILK-ADMIN\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_TRITON_2008.04.22_13.12.48-REPORT.TXT" closed. 63982 13:28:56 (0) CSV file "C:\DOCUMENTS AND SETTINGS\ILK-ADMIN\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_TRITON_2008.04.22_13.12.48-STATISTICS.CSV" closed. 63983 13:28:56 (0) LOG file "C:\DOCUMENTS AND SETTINGS\ILK-ADMIN\LOCAL SETTINGS\TEMP\WMIDIAG-V2.0_2003_.SRV.RTM.32_TRITON_2008.04.22_13.12.48.LOG" closed.

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.4838867