DPM 2012 Manual Agent Install Fails
Hello Everyone,
Using DPM 2012 SP1, I've been stuck on an issue for some time now in trying to get a DPM agent install accomplished on a certain server. The DPM server resides on a parent domain and the server that I am having an issue with is on a child domain. Other servers
on the child domain have installed the agent without issue when doing it manually.
Here is the command I use (as an administrator):
net use X: \\DPMSERVERNAME.parentdomain.com\c$
cd /d X:\Program Files\Microsoft System Center 2012\DPM\DPM\agents\RA\4.1.3465.0\amd64\1033
DPMAgentInstaller_KB2991995_AMD64.exe dpmservername.parentdomain.com
The installation proceeds through the Microsoft License Terms, begins to install and then backs out. The error message that is generated states: "DPMAgentinstaller failed with error code = 0X80070643 error says: fatal error during installation"
In researching the 1708 error within the log file it lead me to the fact that maybe the firewall on the target server was the issue. I
ran this suggested fix on the target server:
netsh advfirewall firewall set rule group=\"@FirewallAPI.dll,-29502\" new enable=yes
netsh advfirewall firewall set rule group=\"@FirewallAPI.dll,-34251\" new enable=yes
netsh advfirewall firewall add rule name=dpmra dir=in program=\"%PROGRAMFILES%\\Microsoft Data Protection Manager\\DPM\\bin\\DPMRA.exe\" profile=Any action=allow
netsh advfirewall firewall add rule name=DPMRA_DCOM_135 dir=in action=allow protocol=TCP localport=135 profile=Any
The issue still persists.
The MSDPMAgentinstall log file says the following at the end:
Property©: Date = 1/7/2015
Property©: MsiNetAssemblySupport = 4.0.30319.18408
Property©: MsiWin32AssemblySupport = 6.1.7601.17514
Property©: MsiRunningElevated = 1
Property©: Privileged = 1
Property©: USERNAME = Windows User
Property©: DATABASE = c:\b1e38ee30069ed00e510\DPMRA.msi
Property©: OriginalDatabase = c:\b1e38ee30069ed00e510\DPMRA.msi
Property©: SOURCEDIR = c:\b1e38ee30069ed00e510\
Property©: VersionHandler = 5.00
Property©: ROOTDRIVE = c:\
Property©: EXECUTEACTION = INSTALL
Property©: ACTION = INSTALL
Property©: UILevel = 5
Property©: CostingComplete = 0
Property©: OutOfDiskSpace = 0
Property©: OutOfNoRbDiskSpace = 0
Property©: PrimaryVolumeSpaceAvailable = 0
Property©: PrimaryVolumeSpaceRequired = 0
Property©: PrimaryVolumeSpaceRemaining = 0
MSI © (68:E8) [09:38:14:119]: Note: 1: 1708
MSI © (68:E8) [09:38:14:119]: Note: 1: 2205 2: 3: Error
MSI © (68:E8) [09:38:14:119]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708
MSI © (68:E8) [09:38:14:119]: Note: 1: 2205 2: 3: Error
MSI © (68:E8) [09:38:14:119]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI © (68:E8) [09:38:14:119]: 吰瞒
MSI © (68:E8) [09:38:14:119]: 吰瞒
MSI © (68:E8) [09:38:14:119]: Grabbed execution mutex.
MSI © (68:E8) [09:38:14:119]: Cleaning up uninstalled install packages, if any exist
MSI © (68:E8) [09:38:14:119]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/7/2015 9:38:14 ===
Any ideas where to turn next?
I do not have a Program Files\Microsoft System Center 2012\DPM\DPM\ProductionAgents\RA\4.1.3313.0\amd64
file path on the DPm system.
Rather Program Files\Microsoft System Center 2012\DPM\DPM\ProtectionAgents\RA\4.1.3313.0\amd64
Still, I ran the DPMAgentInstaller_x64.exe
from that file path and the agent did not install.
Also, on the DPM server I have added the target machine name to the DPMRADmTrustedMachines
group. I also made sure that the domain service account is in the same group. Still no luck.
Similar Messages
-
SCOM agent install fails Error 80070035 - the network path was not found
I have deployed SCOM 2012 agents to most servers (2008, 2008 R2, 2012, 2012R2) in our estate but some either fail to install or are not monitored. I assume the two problems are related, but for now I am concentrating on the servers that fail completely.
Installation is from the Discovery Wizard and I have about 20 servers that fail of various server versions.
So looking at one specific server that is failing to install the agent - a 2008 standard service pack 2
The firewall in on and file and printer sharing is enabled for domain, remote administration is enabled for domain
I added a specific rule to allow TCP 5723 and 5724
DCOM is enabled
I can Ping the target server from the SCOM server by both name and FQDN - both return the same IP and our DNS server has only one entry for this server
I can browse to the admin share \\server\C$ from the SCOM Server, using the same account that I specify for the agent install that is a domain admin with rights on this server (and on the other servers the agent
did install to) and the server has plenty of disk space available
I am not sure what else to look at so would welcome any ideas
ThanksHi Petro,
I have a Agent installation failure cheat sheet, For your error 80070035 it is said to perform a manual installation.
So i would like to understand which version of SCOM is this ? 2007 R2 or 2012 or 2012 r2 ?
Also check if your agents have the WMI service started and enabled ?
Also if yours is a SCOM 2007 R2 do you have a RMS & MS in your management group ? If yes then Pushing the agent installation from MS may cause such issue. So would suggest you push the installation from RMS.
Also check if your Network connectivity meets the minimum requirement as recommended by SCOM. Below is applicable for Both SCOM 2007 R2 & SCOM 2012 & 2012 R2.
Component A
Component B
Minimum Requirement
Root management server or management server
Agent
64 Kbps
Root management server or management server
Agentless
1024 Kbps
Root management server or management server
Database
256 Kbps
Also check if you have any Anti virus / Firewall which is blocking the install / communication. If yes disabe or add the "Monitoringhost.exe to the safe list or what your feature is.
Check if you have another IP assigned to the NIC card and remove it tempraurly andchecl.
Also post the event logs of the Agents which are in not monitored state for analysis.
SCOM Agent installation failure error codes
Error
Error Code(s)
Remediation Steps
The MOM Server could not execute WMI Query "Select * from Win32_Environment where
NAME='PROCESSOR_ARCHITECTURE'" on computer server.domain.com
Operation: Agent Install
Install account: domain\account
Error Code: 80004005
Error Description: Unspecified error
80004005
1. Check the PATH environment variable. If the PATH statement is very long, due to lots of installed third party software - this can
fail. Reduce the path by converting any long filename destinations to 8.3, and remove any path statements that are not necessary.
2. The cause
could be corrupted Performance Counters on the target Agent.
To rebuild all Performance counters including extensible and third party counters in Windows Server 2003, type the following commands at a command
prompt. Press ENTER after each command.
cd
\windows\system32
lodctr /R
Note /R is uppercase.
Windows Server 2003 rebuilds all the counters because it reads all the .ini files in the C:\Windows\inf\009 folder for the English operating system.
How to manually rebuild Performance Counter Library values
http://support.microsoft.com/kb/300956
3. Manual agent install.
The MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on
computer “servername.domain.com”
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
8004100A
800706BA
1. Ensure agent push account has local admin rights
2. Firewall is blocking NetBIOS access
3. Inspect WMI health and rebuild repository if necessary
4. Firewall is blocking ICMP (Live OneCare)
5. DNS incorrect
The MOM Server failed to open service control manager on computer "servername.domain.com". Access is Denied
Operation: Agent Install
Install account: DomainName\User Account
Error Code: 80070005
Error Description: Access is denied.
80070005
80041002
1. Verify SCOM agent push account is in Local Administrators group on target computer.
2. On Domain controllers will have to work with AD team to install agent manually if agent push account is not a domain admin.
Disable McAfee antivirus during push
The MOM Server failed to open service control manager on computer "servername.domain.com".
Therefore, the MOM Server cannot complete configuration of agent on the computer.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 800706BA
Error Description: The RPC server is unavailable.
800706BA
1. Firewall blocking NetBIOS ports
2. DNS resolution issue. Make sure the agent can ping the MS by NetBIOS and FQDN. Make sure the MS can ping the agent by NetBIOS
and FQDN
3. Firewall blocking ICMP
4. RPC services stopped.
The MOM Server failed to acquire lock to remote computer servername.domain.com. This means there is already an agent management operation proceeding
on this computer, please retry the Push Agent operation after some time.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: 80072971
Error description: Unknown error 0x80072971
80072971
This problem occurs if the LockFileTime.txt file is located in the following folder on the remote computer:
%windir%\422C3AB1-32E0-4411-BF66-A84FEEFCC8E2
When you install or remove a management agent, the Operations Manager 2007 management server copies temporary files to the remote computer. One
of these files is named LockFileTime.txt. This lock file is intended to prevent another management server from performing a management agent installation at the same time as the current installation. If the management agent installation is unsuccessful and
if the management server loses connectivity with the remote computer, the temporary files may not be removed. Therefore, the LockFileTime.txt may remain in the folder on the remote computer. When the management server next tries to perform an agent installation,
the management server detects the lock file. Therefore, the management agent installation is unsuccessful.
http://support.microsoft.com/kb/934760/en-us
The MOM Server detected that the following services on computer "(null);NetLogon" are not running. These services are required for push
agent installation. To complete this operation, either start the required services on the computer or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Remote Computer Name: servername.domain.com Install account: DOMAIN\account
Error Code: C000296E
Error Description: Unknown error 0xC000296E
C000296E
1. Netlogon service is not running. It must be set to auto/started
The MOM Server detected that the following services on computer
"winmgmt;(null)" are not running
C000296E
1. WMI services not running or WMI corrupt
The MOM Server detected that the Windows Installer service (MSIServer) is disabled on computer "servername.domain.com". This service is
required for push agent installation. To complete this operation on the computer, either set the MSIServer startup type to "Manual" or "Automatic", or install the MOM agent manually by using MOMAgent.msi located on the product CD.
Operation: Agent Install
Install account: DOMAIN\account
Error Code: C0002976
Error Description: Unknown error 0xC0002976
C0002976
1. Windows Installer service is not running or set to disabled – set this to manual or auto and start it.
The Agent Management Operation Agent Install failed for remote computer servername.domain.com.
Install account: DOMAIN\account
Error Code: 80070643
Error Description: Fatal error during installation.
Microsoft Installer Error Description:
For more information, see Windows Installer log file "C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameAgentInstall.LOG
C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameMOMAgentMgmt.log" on the Management Server.
80070643
1. Enable the automatic Updates service…. Install the agent – then disable the auto-updates service if desired.
Call was canceled by the message filter
80010002
Install latest SP and retry. One server that failed did not have Service pack installed
The MOM Server could not find directory \\I.P.\C$\WINDOWS\. Agent will not be installed on computer "name". Please verify the required
share exists.
80070006
1. Manual agent install
Possible locking on registry?
http://www.sysadmintales.com/category/operations-manager/
Try manual install.
Verified share does not exist.
The network path was not found.
80070035
1. Manual agent install
The Agent Management Operation Agent Install failed for remote computer "name". There is not enough space on the disk.
80070070
1. Free space on install disk
The MOM Server failed to perform specified operation on computer "name". The semaphore timeout period has expired.
80070079
NSlookup failed on server. Possible DNS resolution issue.
Try adding dnsname to dnssuffix search list.
The MOM Server could not start the MOMAgentInstaller service on computer "name" in the time.
8007041D
80070102
NSlookup failed on server. Possible DNS resolution issue.
Verify domain is in suffix search list on management servers.
The Agent Management Operation Agent Install failed for remote computer "name"
80070643
1. Ensure automatic updates service is started
2. Rebuild WMI repository
3. DNS resolution issue
The Agent Management Operation Agent Install failed for remote computer "name". Another installation is already in progress.
80070652
Verify not in pending management. If yes, remove and then attempt installation again.
The MOM Server detected that computer "name" has an unsupported operating system or service pack version
80072977
Install latest SP and verify you are installing to Windows system.
Not discovered
Agent machine is not a member of domain
Ping fails
1. Server is down
2. Server is blocked by firewall
3. DNS resolving to wrong IP.
Fail to resolve machine
1. DNS issue
The MOM Server failed to perform specified operation on computer "name". Not enough server storage…
8007046A
1. This is typically a memory error caused by the remote OS that the agent is being installed on.
There are currently no logon servers available to service the logon request.
8007051F
1. Possible DNS issue
This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version
of the Windows Installer service.
8007064D
1. Install Windows Installer 3.1
The network address is invalid
800706AB
Possible DNS name resolution issue.
Tried nslookup on server name and did not get response.
Verify domain is in suffix search list on management servers.
The MOM Server failed to perform specified operation on computer servername.domain.com
80070040
1. Ensure agent push account has local admin rights
The MOM Server detected that the actual NetBIOS name SERVERNAME is not same as the given NetBIOS name provide for remote computer SERVERNAME.domain.com.
80072979
1. Correct DNS/WINS issue.
2. Try pushing to NetBIOS name
Gautam.75801 -
DPM 2012 R2 Backup job FAILED for some Hyper-v VMs and Some Hyper-v VMs are not appearing in the DPM
DPM 2012 R2 Backup job FAILED for some Hyper-v VMs
DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
(0x800423F3))
All the vss Writers are in stable state
Also Some Hyper-v VMs are not appearing in the DPM 2012 R2 Console When I try to create the Protection Group please note that they are not part of cluster.
Host is 2012 R2 and The VM is also 2012 R2.Hi,
What update rollup are you running on the DPM 2012 R2 server ? DPM 2012 R2 UR5 introduced a new refresh feature that will re-enumerate data sources on an individual protected server.
Check for VSS errors inside the guests that are having problems being backed up.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights. -
DPM 2012 R2 agent update on Windows 2003 server x64 - Exchange
According to the release notes on http://blogs.technet.com/b/dpm/archive/2014/04/23/now-available-update-rollup-2-for-system-center-2012-r2-data-protection-manager.aspx the following workloads are supported on Win2K3 with DPM2012 R2 UR2:
SQL 2005
SQL 2008
SQL 2008 R2
SharePoint 2007
Does that mean protecting Exchange 2007 on Win2K3 is no longer an option after upgrading to DPM 2012 R2 (UR2)? It works on DPM 2012 SP1 but I need to know if it will continue to work after upgrading.
(This question follows on from this thread http://social.technet.microsoft.com/Forums/en-US/c425421b-b726-4125-82fc-beae8947722c/dpm-2012-r2-agent-update-on-windows-2003-server-x64?forum=dpmsetup which was marked as 'answered')Hi,
Yes, Exchange 2007 backup will continue to work. I think that due to the timeframe of the UR2 release not all workloads were able to be re-certified, thus the limit in supported workloads.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights. -
VMM Agent install fails on Windows Server 2012 R2 Hyper-V
Hi,
We are unable to install VMM 2012 R2 agent on Windows Server 2012 R2 server either from VMM console or manually on the hyper-v server.
Error on VMM Console:
Error (410)
Agent installation failed on chsicoecdh03.casper.com.
Fatal error during installation (0x80070643)
Recommended Action
Try the operation again. If the problem persists, install the agent locally and then add the managed computer.
==================================================================
Error on Hyper-v server:
MSI (c) (E8:D0) [16:53:24:726]: Windows Installer installed the product. Product Name: Microsoft System Center Virtual Machine Manager Agent (x64). Product Version: 3.2.7510.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success
or error status: 1603.
Also, I suspect may be issue with WMI then checked WMI repository and it is in consistent state. winmgmt /verifyrepository.
Please help on this issue.
Any help would be appreciated.
Thanks
Kumaresan LakshmananSo, I've managed to research this some more since Thursday and I've come to the conclusion that Hyper-V does a horrible job of supporting Qualcomm NIC cards. That's the only thing I can conclude as far as where the issue is originating. I've read many
post and walkthroughs but nothing that has helped. The issue wasn't with any settings in the domain controller. The issue was that there really is a slow connection originating at the domain controller that is a VM and has network connectivity through the
virtual switch from Hyper-V. So, next question is, how do I get the DC to have better connectivity through the NIC that Hyper-V won't give it? If hyper-v would allow passthrough, this would be so much simpler. VM-ware is looking really good at this point.
Im disappointed in MS right now. -
SCVMM 2012 agent install fails on standalone 2008 R2 host
I am attempting to install SCVMM 2012 agent and getting this error:
Error (421)
Agent installation failed on exhpv01.denverwater.org because of a WS-Management configuration error.
Recommended Action
Ensure that the Windows Remote Management service is enabled and running on the server exhpv01.denverwater.org. Additionally, in the Local Group Policy Editor (gpedit.msc), navigate to Computer Configuration\Administrative Templates\Windows Components\Windows
Remote Management (WinRM), and then ensure that there are no policy settings configured for WinRM Client or WinRM Service.
I have run winrm qc and it shows winrm is configured. I have verified there is no gpo settings configuring winrm.
My runas account is a local administrator on the target host.
I can install the agent local but still cannot add to the SCVMM server.
MarkI am attempting to install SCVMM 2012 agent and getting this error:
Error (421)
Agent installation failed on exhpv01.denverwater.org because of a WS-Management configuration error.
Recommended Action
Ensure that the Windows Remote Management service is enabled and running on the server exhpv01.denverwater.org. Additionally, in the Local Group Policy Editor (gpedit.msc), navigate to Computer Configuration\Administrative Templates\Windows Components\Windows
Remote Management (WinRM), and then ensure that there are no policy settings configured for WinRM Client or WinRM Service.
I have run winrm qc and it shows winrm is configured. I have verified there is no gpo settings configuring winrm.
My runas account is a local administrator on the target host.
I can install the agent local but still cannot add to the SCVMM server.
Mark -
DPM 2012 UR3 Agent Update Error: HRESULT E_FAIL...DCOM Error
My DPM Server is Windows 2008 R2 SP1 with a locally installed SQL and DPM Server and fully patched. My Workstations are all Windows 7 Ultimate x64, fully patched. I have manually installed the DPM RTM Agent and pushed the UR2 update from the DPM Server
without any challenges or issues. I have SCEP running with process exclusions for the DPM services on the WS and DPM Server. I’ve been running DPM 2012 RTM and then UR2 without any issues or challenges to-date.
I have recently updated my DPM 2012 Server from UR2 to UR3 and pushed out all the Agent Updates, which appeared to go successfully from the DPM Console perspective. I spot checked a few systems, 1 workstation (WS) and 1 server, everything looked good. A
couple of days after this I noticed 2 of my workstations failed backing up to Tape. I noticed the recovery options available for these WS’s have stopped updating hours after pushing the UR3 Agent update. The 2 WS’s I'm troubleshooting have a little different
scenario. I have 2 other WS’s that were updated in the same manner and are working perfectly.
Both WS cannot connect to the DPM Server and displays this DCOM Error:
"ERROR:ERROR HRESULT E_FAIL has been returned from a call to a COM component."
The 1st WS DPM Client has a Yelow Sign over-lay and "Administrator has not configured backups." when you hover over it.
The 2nd WS does not the Yellow Sign over-lay.
All the properties of the Local DPM Client Console 'Summary and Protected item' tabs are not updated on the 1st WS but are on the 2nd WS.
1st WS process:
The Recovery Tab shows the available recover dates to choice from.
I can expand one of the backup dates, folders and copy a file to this system.
I can view my previous recovery Points from the console dating back to when I updated the Agents.
I’ve validated the DCOM settings on both WS's compared to a WS that is working, they are the same.
I uninstalled the agent manually, then copied and reinstalled the new UR3 Agent Version with the same outcome.
I uninstalled the new version and reinstalled the previous version, same error.
I then proceeded with upgrading UR2 agent version installing the UR3 version over the top, same error.
I logged on to this WS as the Domain Admin, removed and reinstalled the UR3 version, same error.
I removed, applied and then re-added the DPM server to the local WS DPM and DCOM Groups.
I removed, applied and then re-added the WS from the Groups on the DPM Server.
I’m able to see, ping and view other backup folders presented on the DPM server on this WS.
In the DPM Console I am able to connect to this Workstation successfully from the Administrative, Agent Space.
The DPMClientProtectionCurr.errlog file shows this repeatedly:
0FC0
065C 10/13 05:02:32.499
03 service.cpp(298)
[000000000021FD90]
ACTIVITY
CService::AnnounceServiceStatus
0FC0
0D18 10/13 05:02:33.059
33 dlsclientprotection.cpp(778)
[00000000002BC850]
NORMAL
Connecting to DPM Server: (<Server.FQDN>)
0FC0
0D18 10/13 05:02:33.171
33 dlsclientprotection.cpp(861)
[00000000002BC850]
WARNING Failed: Hr: = [0x80004005] : Failed to set client OS details - ClientName:<WS.FQDN>, ClientOSVersion:6.1.7601, OSType:2, AgentVersion: 4.0.1920.0
0FC0
0D18 10/13 05:02:33.171
33 dlsclientprotection.cpp(1490)
[00000000002BC850]
WARNING Failed: Hr: = [0x80004005] : Failed to get connection to DPM server: lVal : ConnectToDPMServer(bstrClientMachineName, &pIUnknown, &fConnectionSuccessful, &dCurrentStatus,
exceptionResult)
The
DPMRACurr.eerlog show this for both WS's:
0EF0 1110 10/13 04:05:02.157 22 genericthreadpool.cpp(824) [000000000093C360] NORMAL Hr: = [0x80070002] CGenericThreadPool::m_dwMaximumNumberOfThreads[20]
0EF0 1110 10/13 04:05:02.157 03 miscellaneousutils.cpp(918) NORMAL Error:ERROR_UNKNOWN_PRODUCT, While detecting DPM version. Assuming DPM isnt installed.
And this one repeatedly:
0BE8 08EC 10/13 13:59:40.404 29 radefaultsubtask.cpp(382) [00000000002F1640] 4F801526-72F2-4460-8760-F9D6E127FECB WARNING Failed: Hr: = [0x809909b0] : CRADefaultSubTask: WorkitemID does not exist, {DB3F138D-DE37-414D-BADC-5A161C6E7E1C}
0BE8 08EC 10/13 13:59:40.404 05 defaultsubtask.cpp(546) [00000000002F1640] 4F801526-72F2-4460-8760-F9D6E127FECB WARNING Failed: Hr: = [0x809909b0] : Encountered Failure: : lVal : CommandReceivedSpecific(pCommand,
pOvl)
0BE8 08EC 10/13 13:59:40.404 05 defaultsubtask.cpp(751) [00000000002F1640] 4F801526-72F2-4460-8760-F9D6E127FECB WARNING Failed: Hr: = [0x809909b0] : Encountered Failure: : lVal : CommandReceived(pAgentOvl)
The 2nd WS Process:
I did not remove or touch the local agent installation because the information is populated on this client’s agent properties fields.
I can see the folder selections I’ve chosen to be backed up by the protection group configuration.
When i open the Agent UI I receive the sam DCOM error.
I also receive a different error message on this WS when I try and do a Sync Now from the General Tab: Failed to trigger synchronization.
I was able to perform a consistency check on this WS that completed successfully from the DPM server.
I’ve validated the networking configuration settings are correct.
I flushed local DNS cache.
Thanks,
PaulHi,
I have a Windows 7 x64 machine that exhibits this problem. It seems that it is not caused on the client side but on the server side.
In our case the server logs the following every time the client tries to connect:
WARNING Verify disconnected client failed with exception: System.ArgumentException: Das Element wurde bereits hinzugefügt. Schlüssel im Wörterbuch: "<machinename>". Hinzuzufügender Schlüssel: "<machinename>".
(Translation: Element has already been added. Key in Table: "<machinename>". Key to be added: "<machinename>".
I have uninstalled the agent on the client several times. One time I have seen the following error message on the server side:
Deployment.cs(2815) NORMAL Removing all agent records for server[<machinename>] from table InstalledAgent.
ntlmutils.cpp(185) WARNING Failed: Hr: = [0x80070002] : Error trying to open key [HKLM\Software\Microsoft\Microsoft Data Protection Manager\Agent\2.0\NtlmAuthData\<machinename>]
SchedulerImpl.cs(166) NORMAL Entering DeRegister, JobDefID: bafe2b8b-53b2-4694-aa28-9e2c6c152d51
Catalog.cs(1006) WARNING No retry on exception The specified @name ('') does not exist. while executing sp_delete_alert
Catalog.cs(1013) WARNING SqlException encountered, SqlRetryCommand diag details - SqlCommandText => Name=msdb.dbo.sp_delete_alert, CommandType=StoredProcedure
Catalog.cs(1013) WARNING CommandDiagInfo => CanRetry=False, CommandTimeout=3600
Catalog.cs(1013) WARNING CommandParams => Count=2, InTx=True
Catalog.cs(1013) WARNING Param[0] => ParameterName=@name | Value= | Size=0 | DbType=NVarChar | Direction=Input | IsNullable=False
Catalog.cs(1013) WARNING Param[1] => ParameterName=@RETURN_VALUE | Value=1 | Size=0 | DbType=Int | Direction=ReturnValue | IsNullable=False
EventManager.cs(98) NORMAL Publishing event from SchedulerImpl.cs(838): JobScheduleChange, [JobDefID=bafe2b8b-53b2-4694-aa28-9e2c6c152d51]
Errors on the client side appear the moment the agent is re-added to the DPM server (I use "connect agent" instead of "install agent"). After that moment I get the message "Error connection to the DPM server. Error: a COM-component returned E_FAIL" every time
I open the DPM client. This is mirrored by the Verify error mentioned above on the server side.
To me it seems that parts of the machine config are still in the MSDB after removal (maybe caused by the registry error). If this client is connected again, the orphaned database entries cause the Verify error
If that's true, how could we get rid of those entries? Would it help to rename the client?
Uwe -
DPM 2012 Protection Agent Connection Failure
I was successfully protecting a Windows Server 2008 R2 Ent. Server with my M.S. System Center 2012 R2 DPM R2 Server until today. The only changes I know about are the fact that this 2008 server was promoted to a domain controller today using the same
name and I.P. Address. It appears that the DCPromo process has broken DPM protection somehow. Is it true that a "dcpromo" of a protected server can cause DPM Agent failures? If so what is the preferred method to fix this problem.
I'm hoping that I don't really have to stop and clean up the current protection for this server and then start over again. Does anyone have a solution for this problem? Here are the errors I'm getting:
Affected area: ServerName.DomainName
Occurred since: 1/13/2015 8:30:02 AM
Description: The DPM protection agent on ServerName.DomainName could not be contacted. Subsequent protection activities for this computer may fail if the connection is not established. The attempted contact failed for the following reason: (ID 3122)
The protection agent operation failed because it could not access the protection agent on ServerName.DomainName. ServerName.DomainName may be running DPM, or the DPM protection agent may have been installed by another DPM server. (ID 302 Details: )
More information
Recommended action: Uninstall DPM or the DPM protection agent from ServerName.DomainName and install the DPM protection agent again from the computer that you want to use to protect the computer.
On the Agents tab in the Management task area, check the status of the agent.
Resolution: To dismiss the alert, click below
Inactivate
Protection agent version: 4.2.1254.0
Error: Data Protection Manager Error ID: 270
The agent operation failed on ServerName.DomainName because DPM could not communicate with the DPM protection agent. The computer may be protected by another DPM server, or the protection agent may have been uninstalled on the protected computer.
If ServerName.DomainName is a workgroup server, the password for the DPM user account could have been changed or may have expired.
Recommended action: Check the following to troubleshoot this issue:
1) If the agent is not installed on ServerName.DomainName, run DpmAgentInstaller.exe with this DPM computer as a parameter. For details, see the DPM Deployment Guide.
2) To attach the computer correctly to this DPM server, run the SetDpmServer tool with the -Add option on the protected computer.
3) If the computer is protected by another DPM server, or if the protection agent has been uninstalled, remove the protected data sources on this computer from active protection. Then, remove the entry of this computer from the Agents tab in the Management
task area.
4) If ServerName.DomainName is a workgroup server, run SetDpmServer with the -UpdatePassword flag on the protected computer and Update-NonDomainServerInfo.ps1 on the DPM server to update the password.
5) If the DPM server and the protected computer are not in the same domain, ensure that there is a two-way trust setup between the two domains.
Note: I tried running the setdpmserver tool but got the following message:
SetDpmServer failed with errorcode =0x80070534, error says: No mapping between account names and security IDs was done.
I also tried the attach agents option but DPM tells me that there is already an agent installed.
I also tried to manually start the DPMRA service on the client but it fails with error code 1168.
Any helpfull information would be greatly appreciated.
Thank you,
MPetersonHi,
Try the following:
Uninstall the agent from the protected computer.
Restart the computer.
Install the DPM-agent manually.
Re run the SetDPMServer command.
Try start the service.
If the problem still exist, please look into the following steps:
Verify the COM+ permissions for the DPM agent on the protected server. There could be a mismatch in the permissions:
Click START / Administrative Tools / Component Services
Expand Component Services / Computers / My Computer / DCOM Config
Right click on the "DPM RA Services" and choose properties. Verify that under the Security tab / Launch and Activation Permissions you got Customize marked, click the "Edit..." button in the ACL you should see the computer account for
your DPM server.
If it's not present add it and mark all allow boxes and try to start the service again.
You should also verify that your DPM-server computer account is a member of these two local security groups on the protected server:
DPMRADCOMTrustedMachines
DPMRADmTrustedMachines -
SCOM 2012 R2 agent upgrade fails crippling agents
Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues. Warning this issue is not for the faint of heart.
Plan:
I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2. I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters.
Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
Problem:
I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state. At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
be done. What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate. This is no problem and I am able to do this. (Note: all other methods of agent removal did not work ie:
Cleanmom.exe utility or add remove)
Task:
Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
Notes:
Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down.
Looking at the MSI log, I see a common issue among systems that had this problem.
******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
******* Action:
******* CommandLine: **********
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: 3: MOMAgent.msi
MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
Action ended 8:08:44: RemoveExistingProducts. Return value 3.
Action ended 8:08:44: INSTALL. Return value 3.
Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine. Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent.
Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
Action ended 8:08:11: FindRelatedProducts. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_OM_AGENT_FOUND.
MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a 64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE). This is the point of my confusion and my suspicion as the cause of the problem I am having.
Concluding thoughts:
Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid. Could a 32 bit agent have got on this 64 bit server based on the details of this log? Would this
cause my agents to fail the upgrade? I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
Thanks in advance if you took the time to read this and think about it. Extra points if you have any extra thoughts!
KeithHi,
Have you used Requirement to limit the platform when you deploy application with SCCM.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
DPM 2012 R2 agent update on Windows 2003 server x64
Hi,
I have an old windows 2003 server x64 protected by DPM 2012 Sp1. After DPM upgrade to 2012 R2 I cannot update DPM Agent on server. If I try to update agent manually error message is : agentsetup.exe is not a valid win32 application.
Mihaicommand back,
edit: it seems like a reboot is definitely needed to get it working
got it working like described here: http://support.microsoft.com/kb/2958100/en-us
Install the Microsoft Visual C++ 2008 Redistributable on Windows Server 2003 servers if it is not already installed.
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2008 Redistributable Package (x64)
Note The following error occurs if the C++ redistributable is not installed:
Data Protection Manager Setup
Could not load the setup launch screen. Please contact Microsoft Product Support.
Copy the Windows Server 2003 Agent installer that is located on in the DPM server to the Windows Server 2003 server, and then install the agent.
64-bit: <var>DPM Installation Location</var>\DPM\agents\RA\4.2.1226.0\amd64\1033\DPMAgentInstaller_Win2K3_AMD64.exe
32-bit: <var>DPM Installation Location</var>\DPM\agents\RA\4.2.1226.0\i386\1033\
DPMAgentInstaller_Win2K3_i386.exe
Run the following command at an administrative command prompt:
cd DPM Agent Installation Location\DPM\bin\setdpmserver.exe –dpmservername DPM Server Name
Run the following Windows Powershell cmdlet to establish a connection with the DPM server:
Attach-ProductionServer.ps1 DPMServerNameProductionServerNameUserNamePasswordDomain
regards
Stefan -
SCCM 2012 SP1 agent install via WSUS
Hi guys,
I'm having got an issue when I try installing the agent via WSUS. When I try installing manually everything seems to work.
Here are the infos from the ccmsetup.log:
==========[ ccmsetup started in process 2252 ]========== ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Running on platform X86 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Updated security on object C:\WINDOWS\ccmsetup\cache\. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Launch from folder C:\WINDOWS\SoftwareDistribution\Download\Install\ ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
CcmSetup version: 5.0.7804.1000 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Ccmsetup command line: "C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe" ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSJoinedToADDomain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Local Machine is joined to an AD domain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetAssignedSiteFromAD ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
DhcpGetOriginalSubnetMask entry point is supported. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Begin checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
spNamespace.Open(sNamespacePath), HRESULT=8004100e (e:\nts_sccm_release\sms\framework\ccmutillib\ccmiputil.cpp,1109) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Finished checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
LSGetADSiteName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Current AD site of machine is DE-Zeilarn ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Attempting to query AD for assigned site code ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=2887256160)(MSSMSRangedIPHigh>=2887256160))))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=172.24.8.0)(mSSMSRoamingBoundaries=DE-Zeilarn)(mSSMSSiteCode=XYZ)))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Verifying Site Compatibility for <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7804.1000' for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Site Version = '5.00.7804.1000' Site Capabilities = <Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities> ccmsetup 08.02.2013
13:45:47 196 (0x00C4)
LSIsSiteVersionCompatible : Site Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSIsSiteCompatible : Site <XYZ> Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetAssignedSiteFromAD : Trying to Assign to the Site <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Got site code 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
OperationalXml '<ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
HTTP is selected for Client. The current state is 0. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
The MP name retrieved is 'mysccmserver.mydomain.tld' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities>' ccmsetup 08.02.2013
13:45:47 196 (0x00C4)
MP 'mysccmserver.mydomain.tld' is not compatible ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieved 0 MP records from AD for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Certificate Issuers = ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
SslState value: 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Detected sitecode 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPPORT: 80 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSPORT: 443 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSSTATE: 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMHTTPSCERTNAME: ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FSP: ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMCERTISSUERS: CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMFIRSTCERT: 1 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Creating CCMCertStore ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMCERTID: SMS;FB0F35392A7FF68D2FA9C97D0CD54A3E0057964E ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
No MP or source location has been explicitly specified. Trying to discover a valid content location... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Looking for MPs from AD... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Security settings: Certificate Issuers = CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Current directory 'C:\WINDOWS\SoftwareDistribution\Download\Install' is not a valid source location. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
DetermineInstallSource(), HRESULT=80004005 (e:\nts_sccm_release\sms\setup\ccmsetup\ccmsetup.cpp,4426) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
Failed to parse '"C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe" ' with error 0x80004005 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
A Fallback Status Point has not been specified. Message with STATEID='307' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
ParseCommandLine(), HRESULT=80004005
My boundaries and boundary groups are configured, I can see the objects in the Systems Management Container in AD, but still the agent install via WSUS will not work. Any suggestions?
Cheers
Sebastian Bammersee my latest post. It looks like a bug in the setup. It selects a certificate but still it presents information that iis on the mp does not accept. Check your iis logs. Manual install works for ssl only sites. I haven't got any other methods yet. I will
keep you updated. -
Hi everyone,
Been trying to install an agent on a solaris box for a couple days now. It errors out on agentConfig.sh complaining the gent port (3872) is busy. The agent port is not in use. I've run the installer with while loops doing netstat -a|grep 3872 and lsof as well and they show nothing on that port at any time. I've tried this through the GUI and the manual way with the same result. Anyone have any idea?
I'm stumped. Below is some of the logfile
Thanks in advance....Brien
Executing command: /u00/app/oracle/agent/core/12.1.0.1.0/oui/bin/runConfig.sh ORACLE_HOME=/u00/app/oracle/agent/core/12.1.0.1.0 RESPONSE_FILE=/u00/app/oracle/agent/core/12.1.0.1.0/agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true
Configuration Log Location:/u00/app/oracle/agent/core/12.1.0.1.0/cfgtoollogs/cfgfw/CfmLogger<timestamp>.log
ERROR: Agent Configuration Failed SEVERE: Agent port passed by user is busy and cannot proceed with the configuration. Pass a free port and retry the configuration.
and from CfmLogger_2012-01-27_12-15-10-PM.log:
1.ORACLE_HOME=/u00/app/oracle/agent/core/12.1.0.1.0
2.AGENT_PORT=3872
3.ORACLE_HOSTNAME=ddbpr01.servicemagic.com
4.b_doDiscovery=true
5.AGENT_BASE_DIR=/u00/app/oracle/agent
6.AGENT_INSTANCE_HOME=/u00/app/oracle/agent/agent_inst
7.s_hostname=ddbpr01.servicemagic.com
8.OMS_HOST=smcloudpr001.servicemagic.com
9.b_startAgent=true
10.b_secureAgent=true
11.b_chainedInstall=false
12.b_forceConfigure=false
13.EM_UPLOAD_PORT=4890
14.b_forceAgentDefaultPort=false
15.s_staticPorts=
INFO: oracle.sysman.top.agent:Validating OMS_HOST and EM_UPLOAD_PORT
INFO: oracle.sysman.top.agent:Validating with http protocol ...
INFO: oracle.sysman.top.agent:URL framed is:http://smcloudpr001.servicemagic.com:4890/empbs/genwallet
INFO: oracle.sysman.top.agent:Validating with https protocol ...
INFO: oracle.sysman.top.agent:URL framed is:https://smcloudpr001.servicemagic.com:4890/empbs/genwallet
SEVERE: oracle.sysman.top.agent:Connection refusedUnrecognized SSL message, plaintext connection?
INFO: oracle.sysman.top.agent:EM Protocol Switch determined: http
INFO: oracle.sysman.top.agent:Performing free port detection..
SEVERE: oracle.sysman.top.agent:Agent port passed by user is busy and cannot proceed with the configuration. Pass a free port and retry the configuration.
INFO: oracle.sysman.top.agent:Paths after canonical format conversions are :
1. state_dir=/u00/app/oracle/agent/agent_inst
2. agentBaseDir=/u00/app/oracle/agent
3. oraHome=/u00/app/oracle/agent/core/12.1.0.1.0
INFO: oracle.sysman.top.agent:Parent directory of agent instance home:/u00/app/oracle/agent
SEVERE: oracle.sysman.top.agent:Agent configuration has failed
INFO: oracle.sysman.top.agent:AgentConfiguration:agent configuration finished with status = false
INFO: oracle.sysman.top.agent:AgentConfiguration:agent configuration finished with status = false
INFO: oracle.sysman.top.agent:The plug-in Agent Configuration Assistant has failed its perform method
INFO: Cfm.save() was called
INFO: Cfm.save(): 2 aggregate instances saved
INFO: done waiting for Action from 12:15:13.121Hi,
This seems to be similar issue addressed in the following bug:
Bug 13652664: AGENT DEPLOY FAILS WITH AGENT PORT PASSED BY USER IS BUSY
Issue is not with the PORT, but IP Address for the server in file /etc/hosts file is incorrect.
Best Regards,
Venkat -
Hi,
We have DPM 2012 R2 installed on Windows 2012 R2 and Protecting SQL 2012 with DPM and recovery point created twice per day.
And getting frequently warning and error mails “DPM Agent not Reachable” and "Not enough storage is available to complete this operation (0x8007000E)" in DPM Console.
I know its SQL server and it occupies most of the RAM and CPU, but can I set its frequencly or time interval of DPM Agent perodic check to avoid this mails.Hi,
Did you try limiting the sql memory to 60% of physical memory ?
Also adjust the paging file to be physical ram * 1.5 + if necessary.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights. -
SCCM Agent install failed - CcmUnloadWmiProviders. Unloading WMI providers
Hi I have a SCCM 2007 SP2 setup in native mode. I have sccm client problem on Exchange server with os 2008 sp2.
SCCM agent was working on this server few months back but it is not working now.
SCCM agent stops at "CcmUnloadWmiProviders. Unloading WMI providers" steps.
I tried below steps to resolve this but no luck.
1. Uninstall sccm setup using command "ccmsetup.exe /uninstall"
2. Run "Cccmclean.exe /all"
3. Run delcert.exe
4. Rename SMSCFG.ini file
5. Run ccmsetup.exe again with source folder path too
6. As agent installation failed i rebuild WMI repository
7. Re run setup but it failed at same step.
8. I rebooted server and rebuild Repository but same error.
Any Idea about problem
If needed i can provide Log files too
ccmsetup.log (Last few lines)
<![LOG[MSI:
Action 20:07:08: CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:08.980+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:08:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:08.980+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:08:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:08.995+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:08:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:08.995+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:08:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:08.995+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.011+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.011+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.011+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.042+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.042+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.042+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.073+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.073+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.073+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.089+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.089+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.089+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.120+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.120+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.120+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.136+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.136+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.136+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.167+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.167+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.167+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.182+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.182+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.182+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.214+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.214+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.214+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.229+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.229+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.229+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.245+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.245+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.245+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.260+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.260+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.260+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.292+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.292+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.292+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.307+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.307+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.307+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.323+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.323+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.323+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.354+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.354+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.354+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTaskRollback. Removing System
Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmRegisterSystemTask. Registering System
Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmCreateIISApplicationPoolsInit. ]LOG]!><time="20:07:09.385+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmCreateIISVirtualDirectoriesInit.
]LOG]!><time="20:07:09.479+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
RegisterUser. Registering user]LOG]!><time="20:07:09.572+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmFixupServiceConfigInit. ]LOG]!><time="20:07:09.572+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:09:
CcmSetObjectSecurityInit. Applying security
permissions]LOG]!><time="20:07:09.650+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:11:
CcmSetObjectSecurity. Applying security
permissions]LOG]!><time="20:07:11.429+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:11:
CcmSetupLoggingInit. ]LOG]!><time="20:07:11.429+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmSetupLogging. Initializing
logging...]LOG]!><time="20:07:13.176+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
SmsSwDistCacheConfigInit. ]LOG]!><time="20:07:13.176+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
SmsSwDistSetCacheConfig. Configuring Software Distribution
Cache]LOG]!><time="20:07:13.270+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmRegisterPerfCountersInit. Registering performance
counters]LOG]!><time="20:07:13.270+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmRegisterPerfCountersRollback. ]LOG]!><time="20:07:13.613+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmRegisterPerfCounters. Registering performance
counters]LOG]!><time="20:07:13.613+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:13:
CcmRegisterComponentsInit. ]LOG]!><time="20:07:13.613+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmRegisterComponentsRollback. ]LOG]!><time="20:07:14.159+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmRegisterComponents. Registering CCM
Components]LOG]!><time="20:07:14.174+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetLUAAccessPermissionsInit. Setting Access
Permissions]LOG]!><time="20:07:14.174+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetLUAAccessPermissions. Setting Access
Permissions]LOG]!><time="20:07:14.252+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
InstallServices. Installing new
services]LOG]!><time="20:07:14.252+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
WriteEnvironmentStrings. Updating environment
strings]LOG]!><time="20:07:14.315+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmSetServiceConfigInit. Configuring
service]LOG]!><time="20:07:14.315+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmSetServiceConfig. Configuring
service]LOG]!><time="20:07:14.393+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsMigrateInventoryInit. Migrating SMS Legacy Client inventory
settings]LOG]!><time="20:07:14.393+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsMigrateInventory. Migrating SMS Legacy Client inventory
settings]LOG]!><time="20:07:14.471+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmConfigDCOMInit. Configuring
service]LOG]!><time="20:07:14.486+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmConfigDCOM. Configuring service]LOG]!><time="20:07:14.564+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsShellNotify. Setting SMS
configuration]LOG]!><time="20:07:14.580+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetClientLookupConfigInit. ]LOG]!><time="20:07:14.580+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmInitializePolicyInit. Initializing
policy]LOG]!><time="20:07:14.642+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmInitializePolicy. Initializing
policy]LOG]!><time="20:07:14.736+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetClientConfigInit. Setting SMS
configuration]LOG]!><time="20:07:14.736+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
SmsSetClientConfig. Setting SMS
configuration]LOG]!><time="20:07:14.970+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:14:
CcmMigrateDownloadSchemaInit. ]LOG]!><time="20:07:14.970+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmMigrateDownloadSchema. ]LOG]!><time="20:07:15.110+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmRegisterProduct. Registering
product]LOG]!><time="20:07:15.126+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmRegisterProductRollback. Registering
product]LOG]!><time="20:07:15.126+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsInstallPrepDrvrInitAMD64. ]LOG]!><time="20:07:15.126+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsInstallPrepDrvr. Installing Software Metering PREP
Driver]LOG]!><time="20:07:15.204+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
StartServices. Starting services]LOG]!><time="20:07:15.204+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmStartService. ]LOG]!><time="20:07:15.204+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsCleanupDesktopMigrationInfo. Deinstalling the SMS Legacy Client or
SMS 2.0 Client]LOG]!><time="20:07:15.220+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsClientInstallSucceeded. Sending status
message]LOG]!><time="20:07:15.220+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
InstallFinalize. ]LOG]!><time="20:07:15.220+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmStopServiceRollback. ]LOG]!><time="20:07:15.251+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
ProcessComponents. Updating component
registration]LOG]!><time="20:07:15.266+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmStopService. ]LOG]!><time="20:07:15.391+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
StopServices. Stopping services]LOG]!><time="20:07:15.563+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
SmsUninstallPrepDrvrAMD64. Uninstalling Software Metering PREP
Driver]LOG]!><time="20:07:15.563+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Warning 25702. Failed to
uninstall PrepDrvr.Sys for Software Metering
Agent.]LOG]!><time="20:07:15.641+000" date="04-11-2014"
component="ccmsetup" context="" type="2" thread="9048"
file="msiutil.cpp:370">
<![LOG[MSI: Action 20:07:15:
SmsStopUIComponents. Stopping UI
Components]LOG]!><time="20:07:15.641+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
DeleteServices. Deleting services]LOG]!><time="20:07:15.734+000"
date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
<![LOG[MSI: Action 20:07:15:
CcmUnloadWmiProviders. Unloading WMI
providers]LOG]!><time="20:07:15.734+000" date="04-11-2014"
component="ccmsetup" context="" type="0" thread="9048"
file="msiutil.cpp:374">
Thanks Mike and theinfraguys for your suggestions. My problem is resolved.
The solution which worked for me has no logic but it solved my issue.
When my installation stopps at “CcmUnloadWmiProviders. Unloading WMI providers” step client.msi.log file have incomplete entry as “C:\Windows\SysWOW64\C”
At this time I have to restart WMI service and service will not stop correctly so I have to forcefully kill Winmgmt process and setup will continue.
I have to follow same process for upgrading SCCM client. During client upgrade some time I have to kill ccmexec process too. -
OS managemnet agent install fails.....
I have a group of Solaris 10 servers where the agent installation fails at
executing step : sc_console
verified sc_console command is OK
Configuring sc_console
checking existing sc_console connections
doing sc-console registration
Feb 23, 2012 7:37:26 PM org.apache.commons.httpclient.HttpMethodDirector execute WithRetry
INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection timed out
I have logged into each system and verified (ping, ssh, wget) they have access to the proxy server and the EC console machines.
Any idea what would cause this??I think you need more than that, did you check all the required ports as per the site prep guide? You could also check the ops center security guide
these are the ones for the agent to communicate (there's a whole list in the docs)
proxy controller to agent
FTP, TCP: Port 21
SSH, TCP: Port 22
Telnet, TCP: Port 23
DHCP, UDP: Ports 67, 68
SNMP, UDP: Ports 161, 162
IPMI, TCP+UDP: Port 623
Service Tags, TCP: Port 6481
ICMP ping: no port
agent to proxy controller
HTTPS, TCP: Port 21165
HTTPS, TCP: Port 8002
OS to proxy controller
HTTP, TCP: Port 8004
java client to public API's
Transport Layer Security(TLS): Port 11172
Maybe you are looking for
-
A warning about your MacBook Pro (Do not let this happen to you)
If your MacBook Pro is nearing the end of its warranty do like be like me. Purchase the extended warranty! Just before the warranty ran out on my 17" MacBook Pro in December of 2007 the NVIDEA Graphics chip set failed. (8600GT). As you will see below
-
Hi, I can able ran the SSIS package in BIDS, since set to false in Run64BitRuntime property. Then I created SQL server Agent job I tried the following ways Step 1: Type is set as SQL Server Integration Services Packages, Run as - SQL Server Agent Ser
-
Passing parameters to reports from forms.
Hi we are using developer suite 10g and developed some applications.Our reports are working from report buider and also from the forms when we are not passing any parameter. But when we add the clause to pass the parameter from forms fields it does n
-
Directory Serice Connection status in Red color
Hi all, We use LDAP transaction to setup AD connector, RFC defined, LDAP connector defined and in green status, system user defiend. While back to Dirctory service Connetion "LDAP", choose server and connector we defined earlier, the status still sho
-
How do I sync this iPhone 4s to his laptop? The phone was stolen last week and everything was deleted. I've been trying for over an hour to get it to sync.