SCCM 2012 OSD: Import computer object fails
Hi,
Please see this post:
http://social.technet.microsoft.com/Forums/en-US/6dbd2b38-4dbb-4de3-bb25-e3a30813f108/importing-computer-fails-unable-to-save-changes?forum=configmanagerosd
We have exactly the same issue: we cannot import a computer object due to the error "Unable to save changes", a query which searches for mac-addresses doesn't reveal the pc-name (which is logic because the sccm 2012 should run an inventory first
but the pc is not loaded).
Please advise.
J.
Jan Hoedt
Any chance that the object (where you are trying to add a MAC address) was added to the database by AD group discovery? So the name is already in the database? If so: that's expected.
If not: CU1 for R2 might fix the problem (it is listed as being fixed)
Torsten Meringer | http://www.mssccmfaq.de
Similar Messages
-
SCCM 2012 OSD Retain Computer Name on re-image rebuild
I am migrating our PC workstation Windows 7 build process from MDT 2010 lite touch to SCCM 2012 zero touch. Everything is working expect
one thing.
When I re image a PC, if the PC is already known to AD I want it to keep the previous machine name, so that it retains its collection memberships
for software. If I put the PC into the collection that the OSD task sequence is advertised to, the machine successfully rebuilds with the same machine name. Starting from Windows - i.e the configuration manager client.
If I initiate the rebuild via PXE boot the machine gets a new name.
I have read that if the OS is booted from PXE or boot media then the deployment type is new computer. But if the TS is advertised to an
existing client and initiated from the config manager client, the deployment type is refresh.
I'm currently using itx-solutions.nl AutoNameControl to get RIS style naming i.e. PC-123, PC-124 etc.
When I used MDT and lite touch I used MaikKoster Deployment Webservice and obtained the machine name via the GetComputerNameByNetbootGuid
service. This worked perfectly. I don't know what exactly sets this in AD, but have noticed the PC's built with SCCM have no value for NetbootGuid so this doesn't work.
How do I always get the PC to retain the same name on rebuild?Thank you are correct - It turns out it was the AutoNameControl. It creates a new name regardless.
I set a TS variable called ExisitngClient as the first step of my TS - but put a condition on it, to check for the existence of CcmExec.exe on the client. If it exists then I set the variable to TRUE.
Then later on when the AutoNameControl runs, I put a condition of IF ExistingCient not equals TRUE.
Meaning it only runs if it didn't have Config Manager on before the format.
It seems to work.
Thanks for the help -
SCCM 2012 OSD task sequence condition
Is there a way to set a condition on a step that looks to see if the machine is already known to SCCM / Active Directory?
I have a step that names the PC using ITX Solutions AutoName function. I want to say only use this step if the machine is not known.This is essentially a follow on to: http://social.technet.microsoft.com/Forums/en-US/3c6f37ad-b3dc-4219-ae7f-e6c51f05d5bf/sccm-2012-osd-retain-computer-name-on-reimage-rebuild?forum=configmanagerosd
To my knowledge, there is nothing explicitly built-in; however, you might be able to check _SMSTSMachineName to see if it matches the default WinPE naming convention of MINNIT_* or _SMSTSClientGUID to see if it has a value.
You could also put a task in before the format and partition step to check for an existing installation.
Jason | http://blog.configmgrftw.com -
Hi there
Trying to patch a new Windows 7 SP1 image within SCCM 2012 SP1, but it's failing.
I've searched for information on the failure messages I am seeing, but although there is a LOT of information online concerning Offline Servicing failures, I can't find anything on the errors I am seeing.
I've tried injecting a single update, five updates and ten updates, no difference, same messages.
We have McAfee Access Protection disabled, as we know Offline Servicing simply won't work if this is running.
In the console, in Schedule Update Status for the image I am trying to update, the following message is shown:
"Failed to find or access the update binaries to be applied on the image."
That sounds as if the process can't find the actual .cab file for any update I've tried to inject, but I don't know why it wouldn't be able to do that, we have Software Updates configured and the .cab files are on the same server.
When I looked at the OfflineServicingMgr.log file, I see the following entries:
Processing image at index 1 SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:52:49 8272 (0x2050)
Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\PackageID\W7_Image.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\PackageID\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite' SMS_OFFLINE_SERVICING_MANAGER
14/06/2014 14:52:49 8272 (0x2050)
Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 17514 SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:53:31
8272 (0x2050)
Failed to find properties of file 4 SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:53:31 8272 (0x2050)
UnMounting Image (Commit Changes = 0) ... SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:53:31 8272 (0x2050)
Completed processing image package PackageID. Status = Failed SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:04 8272 (0x2050)
Updated history for image package PackageID in the database SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:04 8272 (0x2050)
Schedule processing failed SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:04 8272 (0x2050)
Processing completed for Schedule with ID 16777237 SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:04 8272 (0x2050)
STATMSG: ID=7910 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMServer.domain SITE=Site_Code PID=8560 TID=8272 GMTDATE=Sat Jun 14 13:54:04.964 2014 ISTR0="16777237" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER
14/06/2014 14:54:04 8272 (0x2050)
Schedule processing thread stopped SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:05 8272 (0x2050)
I'm not sure what file "Failed to find properties of file 4" is referring to, whether dism.exe, an update or the image itself, but immediately after this message appears the image is unmounted. After that this message shows:
"Completed processing image package PackageID. Status = Failed"
As I say, there's a lot of information available re Offline Servicing but I haven't found anything with these particular messages.
If anyone has encountered this before, I'd appreciate any information you have.
Regards,
John.Hi,
I think file named 'NO_SMS_ON_DRIVE.SMS’ might be causing this issue. If this file is present in logical drives, then please give it a shot one more time after deleting this file from the logical drives.
Due to this file, it might be preventing 'smsexec' service to skip the drive when looking for content. So worth a try!
After deleting this file, you also need to restart 'smsexec' service to reflect the changes. You can also verify from below registry value & ensure that all of your logical drives (specially where SCCMContentLib directory resides) should be listed
over there
'HKLM\Software\Microsoft\SMS\DP\ContentLibUsableDrives'
Hope this will help!
Cheers | Navdeep Sidhu -
SCCM 2012 OSD Task Sequence - force Policy and SCEP update?
Hi,
How can I force a policy update to update machine policy and scep definitions at the end of
SCCM 2012 OSD Task Sequence,
Thanks,
Ward.Hi,
I normally use this solution from Chris Nackers to deploy the latest EP definitions during OSD and deploy a custom EP policy, it works great. The policy will be downloaded when the client is registered.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec -
Create a prompt using MDT 2012 in SCCM 2012 OSD task sequence
Hi Experts,
I need some help with SCCM 2012 Task sequence using MDT 2012.
Here is the scenario:I want to build a task sequence where it will propmt whether the technican want to build a new build or refresh. Based on the technicians choice the task sequence will perform specific actions.
We can create the prompt using HTA or VBScript or some otherways.
But the requiremnt for us is to Use ONLY MDT 2012, not any other ways.
Is it possible to do like the above with UDI?
Please can someone shed some light how to do will be great.
Thanks in advance,Hi,
UDI may achieve what you want. Take a look at the blogs below.
http://blogs.technet.com/b/anilm/archive/2012/06/01/integrating-mdt-2012-rtm-with-configuration-manager-2012-rtm-part-3-creating-and-deploying-a-udi-task-sequence.aspx
http://heinrichandsccm.blogspot.com/2013/04/how-to-setup-and-configure-sccm-2012.html
Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Juke Chou
TechNet Community Support -
SCCM 2012 OSD Task Sequence Fails "An error occurred while retrieving policy for this computer"
We have SCCM 2012 R2. I amm trying to start OSD task sequence from bootable media.
Hyper-v client gets DHCP ip and starts MDT bootable media, but could not find policy.
From F8 I can ping SCCM/DP/MP server.
What could be the cause?Yes, this DHCP client is in the same subnet as other working clients.
smsts.log from client
Request was successful. TSPxe
21.03.2014 14:14:14 324 (0x0144)
pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1970)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
reply has no message header marker TSPxe
21.03.2014 14:14:14 324 (0x0144)
DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5868)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
Failed to get client identity (80004005)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1113)
TSPxe 21.03.2014 14:14:14
324 (0x0144)
failed to request for client
TSPxe 21.03.2014 14:14:14
324 (0x0144)
Exiting TSMediaWizardControl::GetPolicy. TSPxe
21.03.2014 14:14:14 324 (0x0144) -
SCCM 2012 R2 - Import CSV (From Microsoft MVLS file) to Asset intelligence - Import failed
Hello my Customer have SCCM 2012 R2 installed and fully fonctionnal. I have import the CSV file from MVLS. When I import CSV file inton Asset Intelligence I obtain import error... Why? I have tryed to import XML files too and no success...
I obtain import error...
Is the error super secret? ;-) You would get more feedback if you provided details.
Torsten Meringer | http://www.mssccmfaq.de -
SCCM 2012 SP1 MDT task sequence fails on reboot does not retain ip
we are having a sccm 2012 sp1 server that used for installation of win 8.1 Enterprise , the task sequence works perfectly fine but when we run the same task on HP Elite 8300 system having Intel 82579LM Adapter from Windows XP , after the reboot the
task fails as no ip address is assigned the NIC , We did download the WInPE Adapter drivers from HP site and injecting to the x86 Boot Image (6.2.9200) however the task still fails ,
Our environment uses all static ip address , the same task as mentioned earlier has worked fine with Different brands of HP elite 8200/8100 , infact the elite 8200 also uses the same NIC card
Find below the smsts.log file
Main error in the log file is
No physical network adapters found OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
Found network adapter "Intel(R) 82579LM Gigabit Network Connection" with IP Address 169.254.181.151. TSMBootstrap 2/12/2014 1:05:41 PM 1984 (0x07C0)
Xtract from LOG
SMSTSRebootDelay=60 Reboot 2/12/2014 1:01:56 AM 3496 (0x0DA8)
SMSTSRebootMessage=A new Microsoft Windows operating system is being installed. The computer must restart to continue. Reboot 2/12/2014 1:01:56 AM 3496 (0x0DA8)
SMSTSRebootRequested=WinPE Reboot 2/12/2014 1:01:56 AM 3496 (0x0DA8)
Process completed with exit code 0 TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
!--------------------------------------------------------------------------------------------! TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
Successfully completed the action (Restart to Windows PE) with the exit win32 code 0 TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
Set authenticator in transport TSManager 2/12/2014 1:01:56 AM 1876 (0x0754)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Clear local default environment TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Updated security on object E:\_SMSTaskSequence. TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Save the current environment block TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Executing command line: "bcdedit.exe" TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
CreateProcess failed. Code(0x80070002) TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Command line execution failed (80070002) TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
Staging boot image UNB0003A TSManager 2/12/2014 1:01:57 AM 1876 (0x0754)
ResolveSource flags: 0x00000000 TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
SMSTSPersistContent: . The content for package UNB0003A will be persisted TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
Set authenticator in transport TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
WinHttp credentials set TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
List of files to be downloaded TSManager 2/12/2014 1:01:59 AM 1876 (0x0754)
Downloaded file from http://unb-ho-sccmdb.exch1.mas.unb.com:80/SMS_DP_SMSPKG$/UNB0003A/sccm?/WinPE.UNB0003A.wim to E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim TSManager 2/12/2014 1:02:22 AM 1876
(0x0754)
VerifyContentHash: Hash algorithm is 32780 TSManager 2/12/2014 1:02:22 AM 1876 (0x0754)
Found boot image E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim TSManager 2/12/2014 1:02:25 AM 1876 (0x0754)
Copying boot image locally... TSManager 2/12/2014 1:02:25 AM 1876 (0x0754)
Failed to find ADK installation root registry key TSManager 2/12/2014 1:02:32 AM 1876 (0x0754)
Opening image file E:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 2/12/2014 1:02:32 AM 1876 (0x0754)
Applying image 1 to volume E:\_SMSTaskSequence\WinPE TSManager 2/12/2014 1:02:32 AM 1876 (0x0754)
Closing image file E:\_SMSTaskSequence\WinPE\sources\boot.wim TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
Capturing WinPE bootstrap settings TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSManager 2/12/2014 1:02:35 AM 1876 (0x0754)
==============================[ OSDNetSettings.exe ]=========================== OSDNetSettings 2/12/2014 1:02:36 AM 2064 (0x0810)
Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} OSDNetSettings 2/12/2014 1:02:36 AM 2064 (0x0810)
No adapters found with non-empty DNSDomainSuffixSearchOrder OSDNetSettings 2/12/2014 1:02:36 AM 2064 (0x0810)
Adapter "ROOT\SYMC_TEEFER2MP\0000" not found OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
No physical network adapters found OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
OSDNetSettings finished: 0x00000000 OSDNetSettings 2/12/2014 1:02:38 AM 2064 (0x0810)
Process completed with exit code 0 TSManager 2/12/2014 1:02:38 AM 1876 (0x0754)
Installing boot image to hard drive TSManager 2/12/2014 1:02:38 AM 1876 (0x0754)
Backing up existing boot system before trying to set up new boot system TSManager 2/12/2014 1:02:38 AM 1876 (0x0754)
BootLoader::backup: C:\, E:\_SMSTaskSequence\backup TSManager 2/12/2014 1:02:39 AM 1876 (0x0754)
BootLoader::restore: E:\_SMSTaskSequence\WinPE, C:\ TSManager 2/12/2014 1:02:43 AM 1876 (0x0754)
Saving bcd store to E:\_SMSTaskSequence\WinPE\boot\BCD TSManager 2/12/2014 1:02:43 AM 1876 (0x0754)
Executing command line: "E:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 2/12/2014 1:02:45 AM 1876 (0x0754)
Process completed with exit code 0 TSManager 2/12/2014 1:02:46 AM 1876 (0x0754)
Updated security on object E:\_SMSTaskSequence. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Save the current environment block TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Updated security on object E:\_SMSTaskSequence. TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57 TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Save the current environment block TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 2/12/2014 1:02:47 AM 1876 (0x0754)
<![LOG[LOGGING: Finalize process ID set to 780]LOG]!><time="01:04:01.537+480" date="02-12-2014" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1495">
1/1/1601 12:00:00 AM 1995266923 (0x76ED5B6B)
==============================[ TSBootShell.exe ]============================== TSBootShell 2/12/2014 1:04:01 AM 784 (0x0310)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' TSBootShell 2/12/2014 1:04:01 AM 784 (0x0310)
Debug shell is enabled TSBootShell 2/12/2014 1:04:01 AM 784 (0x0310)
Waiting for PNP initialization... TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
WinPE boot path: E:\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Booted from fixed disk TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Found config path E:\_SMSTaskSequence TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go. TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430) TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Restoring boot system from E:\_SMSTaskSequence\backup TSBootShell 2/12/2014 1:04:01 AM 796 (0x031C)
Successfully loaded the BCD boot system TSBootShell 2/12/2014 1:04:05 AM 796 (0x031C)
Successfully loaded an exported NTLDR boot system TSBootShell 2/12/2014 1:04:05 AM 796 (0x031C)
BootLoader::restore: E:\_SMSTaskSequence\backup, C:\ TSBootShell 2/12/2014 1:04:05 AM 796 (0x031C)
Successfully merged logs from cache. TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515) TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337) TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430) TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Loading bootstrap settings from E:\_SMSTaskSequence\WinPE TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Loading saved WinPE settings TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00450037004500350042004200360039002D0036003100390038002D0034003500350035002D0042003500430041002D003600430034003600410032004200350045004200370038007D00' TSBootShell
2/12/2014 1:04:06 AM 796 (0x031C)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78} TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Configuring WinPE bootstrap settings TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Creating WinPE answer file TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Setting hive location to "X:\windows\system32" TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Getting namespace "Microsoft-Windows-Setup" for architecture "x86" TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Configuring global network settings TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Join type: TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
DNS domain: exch1.mas.unb.com TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
DNS domain search order: TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
IP filter sec enabled: false TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
No adapters found in environment. Performing global configuration only. TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Writing configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Successfully saved configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
Executing command line: wpeinit.exe -winpe TSBootShell 2/12/2014 1:04:06 AM 796 (0x031C)
The command completed successfully. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Starting DNS client service. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Finalizing network settings TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
No adapters found in environment. Performing global finalization only. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Finalizing global network settings TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
DNS domain: exch1.mas.unb.com TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
DNS domain search order: TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
DNS for WINS enabled: false TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
LMHosts file enabled: true TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Host lookup file: TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
WINS scope ID: TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
The command completed successfully. TSBootShell 2/12/2014 1:05:40 AM 796 (0x031C)
==============================[ TSMBootStrap.exe ]============================== TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL' TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Failed to open PXE registry key. Not a PXE boot. TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Resuming Task Sequence in WinPE TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00' TSMBootstrap
2/12/2014 1:05:40 AM 1984 (0x07C0)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912} TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00' TSMBootstrap
2/12/2014 1:05:40 AM 1984 (0x07C0)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03} TSMBootstrap 2/12/2014 1:05:40 AM 1984 (0x07C0)
Loading the Task Sequencing Environment from "E:\_SMSTaskSequence\TSEnv.dat". TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Updating the local data path in the Task Sequencing Environment. TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogMaxSize to 1000000 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogMaxHistory to 1 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogLevel to 0 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogEnabled to 1 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Setting LogDebug to 1 TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Command line for extension .exe is "%1" %* TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Set command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
Executing command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE TSMBootstrap 2/12/2014 1:05:41 AM 1984 (0x07C0)
==========[ TsProgressUI started in process 2004 ]========== TsProgressUI 2/12/2014 1:05:41 AM 2008 (0x07D8)
Command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:W
In dire need of help,
I have already gone through the below articles on the NET
http://social.technet.microsoft.com/Forums/systemcenter/en-US/0fe5cded-51cf-487a-97e3-837fb3426a3e/install-software-updates-in-osd-reboots-leaves-clients-in-provisioning-mode?forum=configmgrosd
http://social.technet.microsoft.com/Forums/systemcenter/en-US/c590e486-d3ca-423f-8953-e596160f3567/updates-hang-during-osd-kb2509007-not-working-for-me?forum=configmgrosd
Awating response,
Hasan RezaWell Finally I sorted my issue ,
Just want to share the solution, may be it would be helpful to some one else and save some times
The problem was that the Xp images has lot of hidden NIC installed , this would not allow the system to work with the correct NIC card and Ip address (System -> View Hidden Devices) , what I did 2 things
1) Copied the OSD Script folder from the SCCM Server to the Client pc and ran that ztigather.wsf and captured the output , it was evident that it showed capturing multiple adapters , (There are some blogs that pointed out that OSD can capture only one nic
due to the only one Adapter0 section being defined in the ZTIgather.xml file,)
2) I open the registry at the xp pc navigated to HKLM-> System ->Current Control Set-> Services-> TCPIP -> Parameters-> Interfaces ->
Expect for the NIC card that had the Ip address assigned I deleted all other nic card's guid,
As then post running deleting the old scanstate (USMTUTIL /rd c:\statestore) , reran the task and VOILA..
All worked fine , below are the two post I followed , though notvery relevant but they were helpful and help me reached the conclusion.
Thanks,
Hasan Reza.
http://systemscenter.ru/mdt2012.en/ztigatherwsf.htm
http://social.technet.microsoft.com/Forums/windowsserver/en-US/8acb7cd1-7028-4ffe-86c9-eb43041cf8b3/how-do-i-get-rid-of-second-169254xx-ipv4-address-on-windows-server-2008-sp2-x86?forum=winservergen -
SCCM 2012 OSD; Not finding driver package during deployment
I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction. Specifically I am having trouble with device driver deployment while deploying my reference image.
I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012. I am building an OSD deployment and have successfully captured my reference image. I am not sure if it matters, but I manually built a reference
PC and using capture media (USB stick), I successfully captured my reference image. I have imported my drivers for the target PC into Config Manager and into a driver package. The driver package has been deployed to the distribution point
(DP). I checked the status of the driver package within the console and verified it has been deployed to the DP. I created a new task sequence (TS) to deploy the captured wim. Within the TS, I added an "Apply
Driver Package" step and pointed it to the aforementioned driver package. I added a WMI query to the step as follows
select * from Win32_ComputerSystem where Model like "HP Probook 6570b%."
Incidentally, I did a wmi query on the target PC to verify the model. I deployed the TS to the unknown computers collection and PXE booted the target PC. I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found." I checked the smsts.log log and found the following:
Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
for deployment. After more research I have done the following:
Deleted the Driver Package and recreated it and updated the TS step to point to this package.
Deleted and recreated the TS along with the driver package.
Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
When distributing content I verified it was successfully completed each time as per the console.
Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error. If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
I have run out of options to try and hope someone can help point me in the next direction to take. After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
Thanks in advance,
Mike G.Thanks for responding.
Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points. I checked now (about 12 hours later) and the package is showing it has not finished updating. I checked the content status and
it is "waiting for content." I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1". This error would occur every 30 min after each time the DP retried to process
the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
it retried, the error cleared, however the package status is still waiting for content. I tried doing a validation on the package but so far there has been no change. -
SCCM 2012 - Project 2010 Standard deployment failed with error 1603
Hi everyone,
I’m in the progress to roll out a software deployment via SCCM 2012, it’s to remove the current Project 2010 Professional we installed and reinstall the Standard version. We got a task sequence for the job, which is Reboot>Un-install Project 2010 Pro>Reboot>Install
Project 2010 Std.
The Un-installation process uses this command: setup.exe /uninstall PrjPro /config "PrjPro.WW\uninstall.xml"
The Installation process uses this command: setup.exe /adminfile project_silent_install.MSP
But the deployment result is quite random, some of the PCs would succeed without any issue, some of them with fail at the installation process with 1708/1603 error. As far as I know we use standard Win 7 64bits SOE across the environment, so everyone should
have same system baseline.
I reviewed some of the failed Project 2010 Standard installation logs as it shows the following:
Executing chained package: PrjStdWW
05/09/2014 20:16:14 Installing chained package: PrjStdWW
PERF: TickCount=530512 Name=Verify MSI local install source Description=Begin function
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
LIS: wait for package "{90140000-003A-0000-0000-0000000FF1CE}" to complete caching
LIS: package "{90140000-003A-0000-0000-0000000FF1CE}" caching completed
PERF: TickCount=530528 Name=Completed verify local install source Description=End function
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Use Shell UI transform : LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
Current transform is at path: LIS\{90140000-0115-0409-0000-0000000FF1CE}\ShellUI.MST
OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
File at \\SCCM2012\SMSPKGE$\PC100139\PrjStd.WW\ose.exe has version: 14.0.4730.1010
File at C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE has version: 14.0.4730.1010
Running OSE version 14.0.4730.1010
Using transform at path: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST
Catalyst Package Install...
Package: PrjStdWW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
Command Line: PATCH="\\SCCM2012\SMSPKGE$\PC100139\project_silent_install.MSP" ADDLOCAL=C.35347883.0E64.45B4.88A0.1881DE05E259,OSpp_Core,Project_PIA,SetupExeArpEntry,Office10Fix1,ProductFiles,InternationalSupportFiles_JPN,AceFiles,IMNFiles,OfficeIntlRDC,AceOdbc,OArt_DocTheme,OSetupController,WISPFiles,TCDRegistration,SetLanguageFiles,TCWorks7Files,ClviewFiles,VBAFiles,OfficeAppSupport,TextConverters,ProductNonBootFiles,dummy_Office_PIA,CAGOffice10,VSCommonPIAHidden,WebDiscussFiles,CAGCat10,CAGCat10Clips,MsoInstalledPackagesScoped,WxpFiles,SetupControllerFiles,Forms_PIA,dummy_MSCOMCTL_PIA,AlwaysInstalled,Gimme_OnDemandData,AceRepl,OISFiles,OfficeOLESupport,OfficeMSProof6,CAGFiles,InternationalSupportFiles_ArialUni,OSpp,Ace_PIA,GraphicsFiltersFile,WebDriveFiles,PROJECTFiles,ProductFiles_B2TR,SetupXmlFiles,OfficePostBoot,DocumentImagingUtils,VSTOCLR35,CAGCategoryFiles,ProjectCommon,VSTO,ProofingParent,MsoCommonShellHandler,OfficeDigitalSFiles,CARegistryFeature,OfficeCoreRDC,SetupExeAddRegistry,NonC2R_ProductFiles,MSSOAP3,TranslationCore,CAGOffice10Clips REMOVE=WISPHidden ARPENTRY_NOMODIFY="#0" ARPENTRY_MODIFYPATH="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /modify PRJSTD /dll OSETUP.DLL" INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SLD_OEMPIDKEY="0" ARPENTRY_NOELEVATEONMODIFY="#0" SETUP_REBOOT="never" COMPANYNAME=" " ARPENTRY_SKUCOMPONENTS="[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Proofing.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Project.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\Office64.en-us\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\PRJSTD\setup.xml[~]" ARPENTRY_HELPLINK="" ARPENTRY_DISPLAYICON="C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\OSETUP.DLL,1" ARPENTRY_DISPLAYNAME="Microsoft Project Standard 2010" ACCEPTEDEULA="1" ARPENTRY_DISPLAYVERSION="14.0.4763.1000" BRANDING_XML="C:\Windows\TEMP\Setup00001048\BRANDING.XML" SLD_SUPPORTSBYPASS="0" SLD_ACID="5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE" SLD_TRIALTYPE="0" ARPENTRY_PACKAGEREFS="[~]OfficeMUISet.en-us[~]OfficeMUI.en-us[~]Proofing.en-us[~]Proof.en-us[~]Proof.es-es[~]Office64MUISet.en-us[~]PrjStdWW[~]Office64WW[~]Office64MUI.en-us[~]ProjectMUI.en-us[~]Proof.fr-fr[~]" SLD_DPID="#xF804000004000000380032003500300033002D00300030003000390038002D003000300031002D003000300030003000310030002D00300033002D0031003000330033002D0037003600300031002E0030003000300030002D0031003200390032003000310034000000000000000000000000000000000000000000000000000000000000000000350064006300370062006600360031002D0035006500630039002D0034003900390036002D0039006300630062002D00640066003800300036006100320064003000650066006500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500072006F006A0065006300740053007400640056004C00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000A09E4657B64703B2F32E339838F004006FE4EEC0394DE6AB2D77DCABCBC8F1C3B8B617EF54ACB52805F38EE560D0B738230977F4AB92430B37CBF02B49DB7636DCF15CE7E175CCF354E009C7A02432315800310036002D0030003800300035003100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000056006F006C0075006D0065003A00470056004C004B00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006C0074004B004D00530000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" REMOVESAMEVERSION="" SLD_LICENSETYPE="6" SETUPEXEINSTALLUICULTURE="en-US" ARPENTRY_SHELLUITRANSFORMLANGUAGE="en-US" USERNAME=" " ARPENTRY_CONTACT="" ARPENTRY_HELPTELEPHONE="" ARPENTRY_PRODUCTCODES="[~]{90140000-00B4-0409-0000-0000000FF1CE}[~]{90140000-002C-0409-0000-0000000FF1CE}[~]{90140000-003A-0000-0000-0000000FF1CE}[~]{90140000-002A-0000-1000-0000000FF1CE}[~]{90140000-001F-0C0A-0000-0000000FF1CE}[~]{90140000-001F-0409-0000-0000000FF1CE}[~]{90140000-001F-040C-0000-0000000FF1CE}[~]{90140000-0115-0409-0000-0000000FF1CE}[~]{90140000-006E-0409-0000-0000000FF1CE}[~]{90140000-002A-0409-1000-0000000FF1CE}[~]{90140000-0116-0409-1000-0000000FF1CE}[~]" ARPENTRY_INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SETUPEXE_DOARPWRITE="1" ACIDS="11B39439-6B93-4642-9570-F2EB81BE2238;5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE;B6E9FAE1-1A0E-4C61-99D0-4AF068915378" ARPENTRY_SPPSKUID="[~]5DC7BF61-5EC9-4996-9CCB-DF806A2D0EFE[~]" ARPENTRY_NOREMOVE="#0" SLD_PKU="0" SLD_PID="82503-001-0000106-49615" LICTYPE="ltKMS" ARPENTRY_UNINSTALLSTRING="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe"" /uninstall PRJSTD /dll OSETUP.DLL" ARPENTRY_NOREPAIR="#1" ARPENTRY_URLUPDATEINFO="" ARPENTRY_URLINFOABOUT="" REMOVEPREVIOUS="" ARPENTRY_CACHELOCATION="C:\MSOCache\All Users" REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\" ARPSYSTEMCOMPONENT=1 TRANSFORMS="C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\ShellUI.MST" ALLUSERS="1"
PERF: TickCount=530543 Name=MsiPackage::Install Description=Calling OMsiInstaller::InstallProduct for package file "C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Error: Failed to install product: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi ErrorCode: 1603(0x643).
Log level changed from: Standard to: Verbose
Rolling back chain
05/09/2014 20:18:47 Rolling back package: PrjStdWW
There appears to be no rollback work to do for package: PrjStdWW path: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\PrjStdWW.msi
05/09/2014 20:18:47 Rolling back package: Office64WW
Package Office64WW was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64WW
File: C:\MSOCache\All Users\{90140000-003A-0000-0000-0000000FF1CE}-C\Office64WW.msi
Command Line: ADDLOCAL=AcePiaReg64,VSTO64,WordXmlEditVerb64,ExcelXmlEditVerb64,GrooveShellIntegration64,Project64Files,OSpp64_Core,ExcelPiaReg64,GraphPiaReg64,FormsPiaReg64,SmartTagPiaReg64,PPTXmlEditVerb64,MsoInstalledPackagesScoped,OfficeExample64bitFilesA,WAC_XmlEditVerb64SPD,SetupXmlFiles,WordPiaReg64,Outlook64Files,AlwaysInstalled64,VBEPiaReg64,VisioPiaReg64,Outlook64SearchShellReg,OneNote64Files,SetupControllerFiles,ProjectPiaReg64,SearchFilters64Files,OutlookPiaReg64,Gimme_OnDemandData,Visio64ShapeSearch,WAC_PIARegSPD64,ProductNonBootFiles64,XDocsPiaReg64,PublisherPiaReg64,OneNotePIAReg64,ProductFiles64,OfficeExample64bitFilesB,OfficePiaReg64,Visio64Files,TCDRegistration64,OSpp64,XDOCSFiles64,XDocsXmlEditVerb64,MsoCommonShellHandler64bit,AccessPiaReg64,PowerPointPiaReg64 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64WW ProductCode:{90140000-002A-0000-1000-0000000FF1CE}
05/09/2014 20:18:56 Rolling back package: ProjectMUI.en-us
Package ProjectMUI.en-us was installed in the chain... uninstalling as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Install Rollback (uninstall)...
Package: ProjectMUI.en-us
Product Code: {90140000-00B4-0409-0000-0000000FF1CE}
Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back install of package: ProjectMUI.en-us path:C:\MSOCache\All Users\{90140000-00B4-0409-0000-0000000FF1CE}-C\ProjectMUI.msi
05/09/2014 20:19:00 Rolling back package: Proofing.en-us
Package Proofing.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proofing.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proofing.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proofing.en-us ProductCode:{90140000-002C-0409-0000-0000000FF1CE}
05/09/2014 20:19:04 Rolling back package: Proof.en-us
Package Proof.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.en-us
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.en\Proof.msi
Command Line: ADDLOCAL=FindAllWordFormsFiles_1033,Gimme_OnDemandData,SpellingAndGrammarFiles_1033,ThesaurusFiles_1033,MsoInstalledPackagesScopedIntl_1033,HyphenationFiles_1033,OCR_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.en-us ProductCode:{90140000-001F-0409-0000-0000000FF1CE}
05/09/2014 20:19:05 Rolling back package: Proof.fr-fr
Package Proof.fr-fr was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.fr-fr
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.fr\Proof.msi
Command Line: ADDLOCAL=MsoInstalledPackagesScopedIntl_1036,Gimme_OnDemandData,SpellingAndGrammarFiles_1036,SetupControllerFiles,FindAllWordFormsFiles_1036,TranslationFiles_1036,ThesaurusFiles_1036,HyphenationFiles_1036,SetupXmlFiles,OCR_1036 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.fr-fr ProductCode:{90140000-001F-040C-0000-0000000FF1CE}
05/09/2014 20:19:11 Rolling back package: Proof.es-es
Package Proof.es-es was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Proof.es-es
File: C:\MSOCache\All Users\{90140000-002C-0409-0000-0000000FF1CE}-C\Proof.es\Proof.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SpellingAndGrammarFiles_3082,OCR_3082,FindAllWordFormsFiles_3082,HyphenationFiles_3082,ThesaurusFiles_3082,MsoInstalledPackagesScopedIntl_3082,SetupControllerFiles,SetupXmlFiles,TranslationFiles_3082 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Proof.es-es ProductCode:{90140000-001F-0C0A-0000-0000000FF1CE}
05/09/2014 20:19:12 Rolling back package: Office64MUISet.en-us
Package Office64MUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUISet.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUISet.en-us ProductCode:{90140000-0116-0409-1000-0000000FF1CE}
05/09/2014 20:19:19 Rolling back package: Office64MUI.en-us
Package Office64MUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: Office64MUI.en-us
File: C:\MSOCache\All Users\{90140000-0116-0409-1000-0000000FF1CE}-C\Office64MUI.msi
Command Line: ADDLOCAL=OfficeExample64bitFilesBIntl_1033,OfficeExample64bitFilesAIntl_1033,Gimme_OnDemandData,Outlook64SearchShellRegIntl_1033,ProductFilesIntl64_1033,MsoInstalledPackagesScopedIntl_1033,OneNoteToLinkedNotesIEAddin64Intl_1033,GrooveFiles64Intl_1033,SetupControllerFiles,SetupXmlFiles REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: Office64MUI.en-us ProductCode:{90140000-002A-0409-1000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUISet.en-us
Package OfficeMUISet.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUISet.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUISet.msi
Command Line: ADDLOCAL=Gimme_OnDemandData,SetupXmlFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUISet.en-us ProductCode:{90140000-0115-0409-0000-0000000FF1CE}
05/09/2014 20:19:20 Rolling back package: OfficeMUI.en-us
Package OfficeMUI.en-us was uninstalled in the chain... installing with previous feature states as part of chain rollback...
Resource File Manager : Converted CultureTag [en-US] to LocaleId [1033].
Catalyst Package Uninstall Rollback (install)...
Package: OfficeMUI.en-us
File: C:\MSOCache\All Users\{90140000-0115-0409-0000-0000000FF1CE}-C\OfficeMUI.msi
Command Line: ADDLOCAL=MetricConverterIntl_1033,AlwaysInstalledIntl_1033,MSTagPluginStockFilesIntl_1033,WebDiscussFilesIntl_1033,GraphicsFiltersPNGFilesIntl_1033,EquationEditorFilesIntl_1033,GraphicsFiltersEPSFilesIntl_1033,MSTagPluginNamesFilesIntl_1033,TCWP5FilesIntl_1033,CAGOffice10Intl_1033,OISFilesIntl_1033,WxpFilesIntl_1033,XDOCSEditorFilesIntl_1033,CAGFilesIntl_1033,WISPHiddenIntl_1033,CAGCat10Intl_1033,SetLanguageFilesIntl_1033,OSetupControllerIntl_1033,MsoInstalledPackagesScopedIntl_1033,TCRecoverFilesIntl_1033,SetupControllerFiles,ClviewFilesIntl_1033,GraphHelpFilesIntl_1033,ProductNonBootFilesIntl_1033,MSTagPluginPlacesFiles_1033,VisioPreviewerIntl_1033,ProductFilesIntl_1033,AceReplIntl_1033,GraphicsFiltersCGMFilesIntl_1033,GraphicsFiltersWPGFilesIntl_1033,Gimme_OnDemandData,TCWP6FilesIntl_1033,GraphicsFiltersGIFFilesIntl_1033,GRAPHFilesIntl_1033,MSTagPluginDateFilesIntl_1033,WebDriveFilesIntl_1033,LOBiFilesIntl_1033,LISTFilesIntl_1033,UICaptionsCompanionIntl_1033,SetupXmlFiles,AceFilesIntl_1033,TOOLSFilesIntl_1033,MSSOAP3Intl_1033,VBAHelpFilesIntl_1033,GraphicsFiltersPICTFilesIntl_1033,OfficeDigitalSFilesIntl_1033,VBAFilesIntl_1033,GraphicsFiltersJPEGFilesIntl_1033,QueryFilesIntl_1033,SetLanguageHelpFilesIntl_1033 REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1033 SETUPINTLDLLDIRECTORY="C:\Windows\TEMP\Setup00001048\"
MSI(INITIALIZE): '<NULL>'
MSI(TERMINATE): '<NULL>'
Successfully rolled back the configuration of package: OfficeMUI.en-us ProductCode:{90140000-006E-0409-0000-0000000FF1CE}
Error attaching to OSE, error 0x00000000
Stopping running ose
LIS: start uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-002C-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-003A-0000-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-00B4-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0115-0409-0000-0000000FF1CE}-C"
LIS: start uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
LIS: finished uncaching for download "{90140000-0116-0409-1000-0000000FF1CE}-C"
Error attaching to OSE, error 0x00000000
Stopping running ose
SystemRestore : Attempting to cancelling System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
SystemRestore : Successfully cancelled System-Restore-Point for Product [Microsoft Project Standard 2010] (with RestorePointType [0, Installed]).
Not showing completion dialog because it was not requested.
Catalyst execution finished: 05/09/2014 20:19:25. Return code: 1603.
PERF: TickCount=722128 Name=RunSetup Description=End function
Can onyone enlighten me what's went wrong, and why did I get this inconsitent installation behaviour?
Thank you very much!!!1603 means there is a fatal error during installation process.
Take a look at the article below. It may help on finding cause.
Hi Juke,
I did do fair a bit of Googling before I started the post. I have increased the logging level on one of the machines failed on the installation. Apparently Project installation log doesn't throw the "return value 3", I think it's pointing to a particular
updating item, anyone knows what is it?
Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed.
The following is the detailed installation log.
MSI (s) (8C:B4) [20:31:33:122]: Executing op: SetTargetFolder()
MSI (s) (8C:B4) [20:31:33:122]: Executing op: FontRegister(Title=Arial Unicode MS (TrueType),File=ARIALUNI.TTF)
MSI (s) (8C:B4) [20:31:33:122]: SHELL32::SHGetFolderPath returned: C:\WINDOWS\Fonts
MSI (s) (8C:B4) [20:31:33:122]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (8C:B4) [20:31:33:122]: Error in rollback skipped. Return: 5
MSI (s) (8C:B4) [20:31:33:746]: Entering MsiProvideAssembly. AssemblyName: Policy.12.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:746]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:777]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:777]: Entering MsiProvideAssembly. AssemblyName: Policy.11.0.Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:777]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:808]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:808]: Entering MsiProvideAssembly. AssemblyName: Microsoft.Office.Interop.MSProject,version="14.0.0.0000000",processorArchitecture="MSIL",publicKeyToken="71E9BCE111E9429C",fileVersion="14.0.4751.1000",culture="neutral", AppContext: , InstallMode: -4
MSI (s) (8C:B4) [20:31:33:808]: Pathbuf: 0, pcchPathBuf: 0
MSI (s) (8C:B4) [20:31:33:840]: MsiProvideAssembly is returning: 1607
MSI (s) (8C:B4) [20:31:33:840]: Note: 1: 2318 2:
MSI (s) (8C:B4) [20:31:33:840]: No System Restore sequence number for this installation.
MSI (s) (8C:B4) [20:31:33:840]: Unlocking Server
MSI (s) (8C:B4) [20:31:33:980]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Transforming table InstallExecuteSequence.
MSI (s) (8C:B4) [20:31:33:980]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 - Update '{35347883-0E64-45B4-88A0-1881DE05E259}' could not be installed. Error code 1603. Additional information is available in the log file C:\WINDOWS\TEMP\MSI1f79e.LOG.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed an update. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Update Name: {35347883-0E64-45B4-88A0-1881DE05E259}. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Note: 1: 1708
MSI (s) (8C:B4) [20:31:34:011]: Product: Microsoft Office Project Standard 2010 -- Installation operation failed.
MSI (s) (8C:B4) [20:31:34:011]: Windows Installer installed the product. Product Name: Microsoft Office Project Standard 2010. Product Version: 14.0.4763.1000. Product Language: 0. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: Unable to delete the file. LastError = 32
MSI (s) (8C:B4) [20:31:34:011]: Deferring clean up of packages/files, if any exist
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202cf.msp
MSI (s) (8C:B4) [20:31:34:011]: Attempting to delete file C:\WINDOWS\Installer\5a202d0.mst
MSI (s) (8C:B4) [20:31:34:011]: MainEngineThread is returning 1603
MSI (s) (8C:24) [20:31:34:011]: No System Restore sequence number for this installation.
MSI (s) (8C:24) [20:31:34:011]: User policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Machine policy value 'DisableRollback' is 0
MSI (s) (8C:24) [20:31:34:011]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (8C:24) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (8C:24) [20:31:34:027]: Restoring environment variables
MSI (s) (8C:24) [20:31:34:027]: Destroying RemoteAPI object.
MSI (s) (8C:48) [20:31:34:027]: Custom Action Manager thread ending.
MSI (c) (F4:1C) [20:31:34:027]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F4:1C) [20:31:34:027]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/05/2014 20:31:34 === -
Hi Friends,
We have planned to upgrade our SCCM 2012 SP1 infrastructure to SCCM 2012 R2 so we have setup test environment to test SQL database upgrade before doing same in production.
But while testing SQL database upgrade on test machine, it is getting failed with below error.
ConfigMgrSetupWizard.log
ConfigMgrSetupWizard Verbose: 1 : Scripted setup failure handling callback called. Failure: 29.
ConfigMgrSetupWizard Verbose: 1 : Received error [Setup cannot upgrade the ConfigMgr database. Contact your SQL administrator.] from native code.
ConfigMgrSetup.log
ERROR: SQL Server error: [23000][2627][Microsoft][SQL Server Native Client 11.0][SQL Server]Violation of PRIMARY KEY constraint 'ContentDistribution_PK'. Cannot insert duplicate key in object 'dbo.ContentDistribution'. The duplicate key value is (921). :
tr_ContentDistributionNotification_insert
ERROR: Failed to execute SQL Server command: ~-- ~-- Rebuild ContentDistribution tables ~-- ~IF (EXISTS(SELECT TOP 1 1 FROM dbo.SMSData WHERE SMSBuildNumber <= 7900) AND dbo.fnIsSecondary() != 1) ~BEGIN ~ exec spRebuildContentDistribution
@TruncateTables=0 ~END
Failed to create process of SetupWpf.exe.
Can anyone please help to get this resolved.
Thanks.We found out that there were duplicate entries in the PkgStatus_G and the PkgServers_G tables in the SCCM DB. We identified them, deleted them , and then we were able to run the /TESTDBUPGRADE command and it went through fine. We performed
all of this on a COPY of the PROD DB and then moved the changes in PROD. Hope this helps someone.
- Dave -
SCCM 2012 SP1 Secondary Site installation Fails
Hi.
I have multiple secondary sites when i am trying to install new SCCM 2012 Secondary site server remotely but installation status shows a pending from last few days.
1) SEC server have privilages on System managent container
2) Primary site Server account and computer have local admin right on SEC server
hman logs says the following error message
Cannot get SQL Certificate from site xxx
CheckParentSQLServerCertificate: Failed to get SQL certificate for site XXX
1) Deleted the secondary site and reinstalled the site with different Site code but no luck
2) Able to telnet 1433 and 4022 from both primary to secondary and vice versa
3) SQL server Configuration Manager , TCP IP port was set to 1433.
please let me know if any thing i am missing
ThanksHi Guys
Exact same problem as described above:
Been told to install SQL Express manually first, but even after that, we continued to get the same problem.
The SQL Communication between the 2 sites doesn't seem to work.
I noticed that the Primary's SQL Security Account doesn't get created on Primary DB, in the Database replication the link has not yet been created either.
The "Exec spDrsSendSubscriptionInvalid 'Secondary 3 digit site code','Primary 3 digit site code','configuration data'" worked on 1 Secondary, but fails on all the rest.
Uninstalling/Installing the Secondary doesn't work either.
HMAN.LOG:
Update site server active directory informtion into DB SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
CheckSQLServiceRestart : SQL Service hasn't been restart since last time we check, skip it. SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
Time to verify if the parent['PRI-SITECODE'] sql server certificate is still valid on site ['SEC-SITECODE'] sql server. SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
Cannot get SQL Certificate from Site 'PRI-SITECODE'. SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
CheckParentSQLServerCertificate: Failed to get SQL certificate for site PM2 SMS_HIERARCHY_MANAGER 2013/07/28 09:51:12 AM 7964 (0x1F1C)
Any ideas would be appreciated. -
Helix gen.2 very slow with USB 3.0 and SCCM 2012 OSD
Hello there, i have a problem with our Helix gen.2. i would like deploy the OSD with SCCM 2012 and so i insert the USB 3.0 Dongle driver in WinPE. The Download and WIM installation is very fast but slows down after the OSD TS insert all Drivers for the system an makes a reboot. After the reboot the machine runs very slow over the network (1GB) and over 20 Hours and breaks down with a unsigned Error Message 80004005. i change the driver to an old version for the UBS 3.0 but it doesn´t helps so i need help from you. with best regards andré
What OS are you deploying on the box, 7 or 8.1?
Did you import the drivers from the Helix2 SCCM driver pack for the appropriate OS into a Driver Package?
Did you also add the USB 3.0 drivers specific to the OS being deployed into that same Driver Package?
Do you have an Apply Drivers task that references this driver package in the task sequence? If so, you should be able to find the task ID in the SMSTS.log file and verfiy it is running. -
SCCM 2012 OSD - unattended XML problem?
Hi,
I am having an issue with SCCM 2012 SP1 / MDT OSD task sequence. The issue is
with the Apply Operating system step. It applies the OS reboots and boots into
the new OS. We are trying to install Windows 2008 R2.
The first dialog I see is:
"Windows could not parse or process the unattende answer file for pass [specialize].
The settings epcified in the answer file cannot be applied. The
error was detected while processing for component [Microsoft-Windows-Shell-Setup]"
Then in the black background under the dialog".
"Setup is applying system settings"
-- So I click "OK" the computer reboots..
Then I get
"The computer restarted unexpectedly or encounted an
unexpected error. Windows Installation cannot proceeed. To install
Windows, click "OK" to restart the computer, and then restart the
installation.
The in the black background see:
"Setup is preparing your computer for first use"
If I click on "OK" here it reboots and presents the same dialog again - so it gets stuck and loops
around and does not progress.
Questions
1. So from the "Apply OS step" I can see you can see you can specify a specific "unattended.xml" file.
Is there a log file I can look at that can give me more specific detail on what the exact setting it does
not like in that XML file so I can correct it?
2. If I don't specicy anything how is that XML generated and where would its log file be? I assume the same
as question 1?
3. For question 2 - where can I find the unattended XML on the target OS.
4. Since I am not in PE anymore and F8 does not work is there anyway I can bring up a command prompt?
Thanks,
Ward.1. You'll have to check the Windows setup logs files because at this point, that's what's running.
2. There is a default XML file generated/used.
3. You will only find the file on deployed systems and I think you can traditionally find it under the panther folder.
4. Actually, you can use F8 to launch a command-prompt in the target OS during the TS as long as you enabled it in the boot image. However, as mentioned, you are in Windows setup at this point (which is actually another instance of WinPE) and so F8 doesn't
work here. Shift-F10 should though.
Jason | http://blog.configmgrftw.com
Maybe you are looking for
-
Can't boot properly in UEFI mode
Hi! After enabling "windows 8 feature" and booting in uefi only mode, no boot device is detected anymore. The efi shell comes up after the bios has started and I can't boot into windows. I tried a clear cmos but it didn't work. I have a Z87-GD65 (lat
-
Working with DSLR Video in Lightroom 4 | Getting Started with Adobe Photoshop Lightroom 4 | Adobe TV
Master the new features for editing, adjusting, rendering, and sharing video clips in Lightroom 4. http://adobe.ly/wOuQdl
-
Flex...is it really that good?
I hear all these things about flex being a rapid development environment for flash apps. I have been using flash for quite some time, I don't really use the timeline nor do any timeline scripting I just use AS3 classes. So I think flex may be good fo
-
Issue with executing Business Rules from Planning web
Hi, We are using Hyperion Planning 9.3.0.1 and we keep getting an issue with the Business Rules. We get an error if we try to run the rules from Planning web. The same rules validates and executes fine if we run it from AAS. This issue gets resolved
-
CS4 Crashing while Saving (I believe)
Hi, Was wondering if anybody else has experienced this. Pro CS4 (PC), & I doubt this has anything to do with it, but just in case - my assets have recently reached just over 1,000 (mostly quite short clips)...from say 700 a couple weeks ago. Pro has