WDS fails to install win7 image
Hi!
I created a .wim file with dism.exe and tried to install an updated version of win7 with hyperv but when the install finished (no errors in progress) and i click search for updates, it seems that none of the updates are installed.
In septuperr.log i can see [0x0b003a] error code, wich means somethins is missing, or some dependency not sure what it is or where to look.
I tired these steps: http://serverfault.com/questions/550210/wds-error-windows-cannot-install-required-files-make-sure-all-files-required-f
but, not found a folder like $WINDOWS.~BT.
Here is the setuperr.log: http://pastebin.com/AYVg3mCQ
Any ideas what to do next?
Hi,
How did you apply the windows updates in wim file using DISM? After you apply the updates in wim, please make sure to unmount the image and commit the changes you made.
I recommend to follow this guide
https://msdn.microsoft.com/en-us/library/ff794819.aspx
http://blogs.technet.com/b/configmgrdogs/archive/2012/02/15/applying-windows-updates-to-a-base-wim-using-dism-and-powershell.aspx
Typically, we recommend you use WDS with MDT to deploy the OS and updates, create a deployment share including sysytem updates\hotfix\drivers in MDT.
https://technet.microsoft.com/en-us/magazine/hh307507.aspx
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Similar Messages
-
hello i have ps elements 9 and im trying to update it so that i can open and edit my raw images but it says that some updates failed to install like 9.0.3 camera raw 6.5 and premier elements 9.0.1
Photoshop Elements is not part of the Cloud, I will move this to that forum
Photoshop Elements Forum http://forums.adobe.com/community/photoshop_elements
Select a topic, then click I STILL NEED HELP to activate Photoshop Elements Online chat
-http://helpx.adobe.com/contact.html?product=photoshop-elements or
http://helpx.adobe.com/photoshop-elements/kb/troubleshoot-installation-photoshop-elements- premiere.html -
Hello,
I'm facing some issues while installing an image from configuration file of Windows Embedded 8 Standard. I get an error message which I've tried to indentify using this guide
Use Log Files to Diagnose Image Builder Wizard Installation Problems (Standard 8). I haven't succeeded at all. The errors I have are the following:
At setuperr.log
2015-03-13 11:43:00, Error CBS Failed to process single phase execution. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-03-13 11:43:00, Error CBS Failed to perform operation. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2015-03-13 11:43:18, Error [0x060766] IBS ApplyUnattendFileUsingDism: DISM returned error exit code 2
2015-03-13 11:43:18, Error [0x06076d] IBS ApplyUnattendFileUsingDism: See DISM log file [D:\$WINDOWS.~BT\Sources\Panther\cbs_unattend.log] for more details.
2015-03-13 11:43:18, Error [0x060768] IBS ApplyUnattendFileUsingDism: Failed to use DISM to install modules and apply settings. Error code = 0x80070002
At cbs_unattend.log
2015-03-13 11:41:50, Info DISM Embedded Manager: PID=460 TID=544 Success coping module from "C:\AutoUnattend_Files\offlineServicing\vvvv_45beta33.7~0000000000000000~amd64~~1.0.0.0.emd" to "D:\Windows\servicing\Modules\PendingInstall\vvvv_45beta33.7~0000000000000000~amd64~~1.0.0.0.emd" - ModuleInstaller::CopyForPostboot
2015-03-13 11:41:50, Info DISM DISM Package Manager: PID=460 TID=544 CBS session options=0x0! - CDISMPackageManager::Internal_Finalize
2015-03-13 11:42:01, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:01, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:01, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:01, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:15, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:42:58, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2015-03-13 11:43:00, Info DISM DISM Package Manager: PID=460 TID=384 Error in operation: (null) (CBS HRESULT=0x80070002) - CCbsConUIHandler::Error
2015-03-13 11:43:00, Error DISM DISM Package Manager: PID=460 TID=544 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM Package Manager: PID=460 TID=544 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80070002)
2015-03-13 11:43:02, Error DISM Embedded Manager: PID=460 TID=544 Failed to process package installation(s) - ModuleInstaller::InstallModules(hr:0x80070002)
2015-03-13 11:43:02, Error DISM Embedded Manager: PID=460 TID=544 Failed to install modules - CEmbeddedManager::Apply(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM Unattend Manager: PID=460 TID=544 Error applying unattend for provider: Embedded Manager - CUnattendManager::Apply(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM Unattend Manager: PID=460 TID=544 base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:674 - CUnattendManager::InternalExecuteCmdLine(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM Unattend Manager: PID=460 TID=544 base\ntsetup\opktools\dism\providers\unattendprovider\dll\unattendmanager.cpp:623 - CUnattendManager::ExecuteCmdLine(hr:0x80070002)
2015-03-13 11:43:02, Error DISM DISM.EXE: DISM Unattend Manager processed the command line but failed. HRESULT=80070002
2015-03-13 11:43:02, Info DISM DISM Provider Store: PID=460 TID=544 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
I've googled for them and I've read that the 0x80070002 may be related to updates, but nothing particular about the other.
Could anyone please tell me what can be happening?
I've uploaded cbs_unattend.log and setupact.log in case they are helpful.
http://www.filedropper.com/cbsunattend
http://www.filedropper.com/setupactIt's strange, because I can install that package, and all the other custom ones without error if updates, security updates and hotfixes are not included. It must be one of those packages which is causing the install to fail. I tried to install updates manually
once I deployed the image but after the updates some of my custom applications didn't work well.
All of this just happening on the intel board, not the amd one. -
WinUsb, INF fail to install on Win7 while Successfully install in Win8
Use-case
Windows 2012 as the development machine ( where the INF is signed )
inf2cat and signtool are used to sign the INF
Signed INF ( along with the co-installers ) are deployed on a Win7 Ultimate machine
Problem description
While successfully installed on Win8*.* while right-clicking to install on Win7 I get "The INF file you selected does not support this method of installation" ( setupapi.dev.log say nothing )
When using "devcon dp_add %INF File" the driver is successfully installed, BUT, is not associated with any of the related Hardware IDs... After devcon usage, when manually updating the driver using "Device Manager", I get "The required
section was not found in the INF", setupapi.dev.log is saying the same: "CoInstaller 1: failed(0xe0000101)!, !!! dvi: Error 0xe0000101:
The required section was not found in the INF."
What am I doing wrong? why does for Win8 the INF is successfully installed and for Win7 it fails ?
Signing procedure
inf2cat /driver:"$(ProjectDir)\Driver Files" /os:8_X64,7_X64
signtool sign /p password /f "$(ProjectDir)\Driver Files\certificate.pfx" "$(ProjectDir)\Driver Files\winusbinstallation.cat"
INF File used
; Use for signing: http://msdn.microsoft.com/en-us/library/windows/hardware/ff540161(v=vs.85).aspx
; Installs WinUsb
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGUID = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ManufacturerName%
CatalogFile = WinUSBInstallation.cat
DriverVer=09/04/2014,13.54.20.543
; ========== Manufacturer/Models sections ===========
[Manufacturer]
%ManufacturerName% = Standard,NTamd64
[Standard.NTamd64]
%AOA_Device_2D00% = USB_Install, USB\VID_18D1&PID_2D00
%ADB_Device_2D01% = USB_Install, USB\VID_18D1&PID_2D01&MI_00
%AOA_Device_2D01% = USB_Install, USB\VID_18D1&PID_2D01&MI_01
%AOA_Device_2D05% = USB_Install, USB\VID_18D1&PID_2D05&MI_00
%ADB_Device_2D05% = USB_Install, USB\VID_18D1&PID_2D05&MI_03
%AudControl_Device_2D05% = USB_Install, USB\VID_18D1&PID_2D05&MI_01
; ========== Class definition ===========
[ClassInstall32]
AddReg = ClassInstall_AddReg
[ClassInstall_AddReg]
HKR,,,,%ClassName%
HKR,,NoInstallClass,,1
HKR,,IconPath,%REG_MULTI_SZ%,"%systemroot%\system32\setupapi.dll,-20"
HKR,,LowerLogoVersion,,5.2
; =================== Installation ===================
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
Needs = WINUSB.NT.Services
[USB_Install.HW]
AddReg=Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg=CoInstallers_AddReg
CopyFiles=CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01011.dll,WdfCoInstaller","WinUsbCoInstaller2.dll"
[CoInstallers_CopyFiles]
WinUsbCoInstaller2.dll
WdfCoInstaller01011.dll
[DestinationDirs]
; If your INF needs to copy files, you must not use the DefaultDestDir directive here.
CoInstallers_CopyFiles=11
; ================= Source Media Section =====================
[SourceDisksNames]
1 = %DiskName%
[SourceDisksFiles]
WinUsbCoInstaller2.dll=1
WdfCoInstaller01011.dll=1
; =================== Strings ===================
[Strings]
ManufacturerName="NewComp Inc"
ClassName="Universal Serial Bus devices"
AOA_Device_2D00="Android AOA Interface (2D00)"
AOA_Device_2D01="Android AOA Interface (2D01)"
ADB_Device_2D01="Android ADB Interface (2D01)"
AOA_Device_2D05="Android AOA Interface (2D05)"
ADB_Device_2D05="Android ADB Interface (2D05)"
AudControl_Device_2D05="Android Audio Interface (2D05)"
REG_MULTI_SZ = 0x00010000
Nadav Rubinstein, See my Blog @
http://www.sophin.comThere were two problems, one is, as other mentioned, the fact that Win7 doesn't support INF installation by right-clicking, this however, didn't explain the devcon dp_add installation problem described in the original post, the resolution was to add the
following to the INF file, while this is not required when installing on Win8, IT IS mandatory when installing @ Win7
[USB_Install.Wdf]
KmdfService=WINUSB, WinUsb_Install
[WinUsb_Install]
KmdfLibraryVersion=1.11
I have spent half a day on hunting this down, having better logging information would greatly reduce the time it takes to resolve such problems, for example, By adding the name of the expected/missing section to the message "The
required section was not found in the INF"
Nadav Rubinstein, See my Blog @
http://www.sophin.com -
Attempting to install printer on USGCB Win7 image
Hello everyone. I''m attempting to run the installation for a printer within the USGCB standards, also within a government network with policies and restrictions in place.
On our Windows XP machines, this printer installs fine. On our Win7 machines, it does not. I right click, run as admin, and the program executes (procmon verifies this) but we don't end up with a printer in the printers control panel. The vendor is at a
loss, as it works fine on other Win7 images. I am at a loss, after attempting tons of troubleshooting methods and not being able to even determine the root cause of the blocked installation.
Troubleshooting attempted: During installation, all logs, event monitor output, process monitor output, etc seem to indicate that the printer should be installing, however, the proper registry entries and files are not being created. There are no errors
that pop up. We've had several IT and Security professionals, as well as ImageNow and PeerNet technicians review to no avail. We have dropped the machine from the GPO restrictions, verified valid certificates, and added administrator rights to the accounts,
folders, and files, disabled UAC, DEP, and antivirus, and something is still blocking file creation, however, we can't find any indication of what might be doing the blocking. Other programs can write to the output folders (cutepdf installation is successful).
I am running as Admin.
Any tips, pointers, suggestions, or ways of identifying exactly what is blocking the installation would be greatly appreciated. I left out hundreds of pages of back and forth between me and other troubleshooters, so there's sure to be some things I know
I have done and left out. Honestly, what I really need, is just to know WHICH setting (if it is a GPO setting, or if it's something else) that is blocking the installation, so that we can setup an exception or decide what our path will be. Thanks.I would guess the driver is not installing correctly, since there are no files placed in the "C:\WINDOWS\system32\spool\drivers\w32x86\3" directory as I am told i should expect, and as gets done on a non USCGB installation of win7. I would also guess it
is packageware. I'm told it's digitally signed by our security professionals and the vendor, but never verified this myself. I'm not sure if it's calling spooler API's either. This is the first set of questions i've been asked in 6 months that seem to lead
a direction other than the ones I've taken, so i greatly appreciate your time.
Here's a code block of the OEMsetup.inf file, which i assume is the one that might answer your questions. If not, let me know and I will be happy to follow your instructions or google instructions on getting that info. I'm pretty good with computers and
programming, but don't do much when it comes to printers.
; Printer Installation File for use with the Add Printer Wizard or to install additonal drivers
; List of supported printers, manufacturers
[Version]
Signature="$Windows NT$"
Provider=%PEERNET%
ClassGUID={00000000-0000-0000-0000-000000000000}
LayoutFile=layout.inf
[ClassInstall32.NT]
AddReg=printer_class_addreg
[printer_class_addreg]
HKR,,,,%PrinterClassName%
HKR,,Icon,,"-4"
HKR,,Installer32,,"ntprint.dll,ClassInstall32"
HKR,,NoDisplayClass,,1
[PEERNETInstall_x86]
CopyFiles=PNTIF8I,PNFILES,UNIDRV,LIBS,PSI,PNWNPRT8
PrinterName=ImageNow Printer
DriverName=ImageNow Printer
PrinterSection=PNTIF8_DATA_x86
SetupTitle=TIFF Image Printer 8.0 Setup
HardwareID=PEERNET_Inc.PEERNET.DBCD4
[PEERNETInstall_amd64]
CopyFiles=PNTIF8I,PNFILES,PNFILES_amd64,UNIDRV,LIBS,PSI,PNWNPRT8
PrinterName=ImageNow Printer
DriverName=ImageNow Printer
PrinterSection=PNTIF8_DATA_amd64
SetupTitle=TIFF Image Printer 8.0 Setup
HardwareID=PEERNET_Inc.PEERNET.DBCD4
[PEERNETInstall_x86_vista]
CopyFiles=PNTIF8I,PNFILES,LIBS,PSI,PNWNPRT8
PrinterName=ImageNow Printer
DriverName=ImageNow Printer
PrinterSection=PNTIF8_DATA_x86_vista
SetupTitle=TIFF Image Printer 8.0 Setup
HardwareID=PEERNET_Inc.PEERNET.DBCD4
CoreDriverSections="{D20EA372-DD35-4950-9ED8-A6335AFE79F0},UNIDRV.OEM"
[PEERNETInstall_amd64_vista]
CopyFiles=PNTIF8I,PNFILES,PNFILES_amd64,LIBS,PSI,PNWNPRT8
PrinterName=ImageNow Printer
DriverName=ImageNow Printer
PrinterSection=PNTIF8_DATA_amd64_vista
SetupTitle=TIFF Image Printer 8.0 Setup
HardwareID=PEERNET_Inc.PEERNET.DBCD4
CoreDriverSections="{D20EA372-DD35-4950-9ED8-A6335AFE79F0},UNIDRV.OEM"
; Manufacturer section.
; This section lists all of the manufacturers
; that we will display in the Dialog box
[Manufacturer]
%PEERNET% = PEERNET, NTamd64
; Model Specifications Section
[PEERNET]
"TIFF Image Printer 8.0" = PNTIF8_DATA_x86,PEERNET_Inc.PEERNET.DBCD4,TIFF_Image_Printer_8.0
[PEERNET.NTamd64]
"TIFF Image Printer 8.0" = PNTIF8_DATA_amd64,PEERNET_Inc.PEERNET.DBCD4,TIFF_Image_Printer_8.0
[OEM URLS]
%PEERNET% = "http://www.peernet.com"
; Installer section(s) referenced above.
[PNTIF8_DATA_x86]
CopyFiles=PNTIF8I,PNFILES,UNIDRV,LIBS,PSI,PNWNPRT8
DependentFiles=PNReg8.exe,emsmtp.dll,PNAuth8.exe,PNdrvCS.ocx,PNDRVUI.DLL,pnemail8.dll,PNMapi8.DLL,PNSvc8.exe,PNSrv8.exe,PNAdd8.exe,PNJob8.exe,PSITIF8.chm,PNTIF8I.DLL,PNTIF8I.INI,PSITIF8C.INI,PNTIF8j.DLL,PNTIF8R.DLL,PNTIF8u.DLL,PNTIF8u.GPD,PSITIF8L.INI,IM31bmp.dil,IM31jpg.dil,IM31png.dil,IM31tif.dil,STDNAMES.GPD,UNIDRV.DLL,UNIDRV.HLP,UNIDRVUI.DLL,UNIRES.DLL
DataFile=PNTIF8u.GPD
ConfigFile=PNDRVUI.DLL
HelpFile=UNIDRV.HLP
DriverFile=PNTIF8R.Dll
DefaultDataType="NT EMF 1.008"
DefaultPort=NUL
Comment=Print to TIFF
PrintProcessor=PNWnPrt8,PNWnPrt8.dll
[PNTIF8_DATA_amd64]
CopyFiles=PNTIF8I,PNFILES,PNFILES_amd64,UNIDRV,LIBS,PSI,PNWNPRT8
DependentFiles=PNSvc8.exe,PNSrv8.exe,PNAdd8.exe,PNJob8.exe,PNReg8.exe,emsmtp.dll,PNAuth8.exe,PNMLX864.dll,pnem864.dll,PNdrvCS.ocx,PNDRVUI.DLL,pnemail8.dll,PNMapi8.DLL,PSITIF8.chm,PNTIF8I.DLL,PNTIF8I.INI,PSITIF8C.INI,PNTIF8j.DLL,PNTIF8R.DLL,PNTIF8u.DLL,PNTIF8u.GPD,PSITIF8L.INI,IM31bmp.dil,IM31jpg.dil,IM31png.dil,IM31tif.dil,STDNAMES.GPD,UNIDRV.DLL,UNIDRV.HLP,UNIDRVUI.DLL,UNIRES.DLL
DataFile=PNTIF8u.GPD
ConfigFile=PNDRVUI.DLL
HelpFile=UNIDRV.HLP
DriverFile=PNTIF8R.Dll
DefaultDataType="NT EMF 1.008"
DefaultPort=NUL
Comment=Print to TIFF
PrintProcessor=PNWnPrt8,PNWnPrt8.dll
[PNTIF8_DATA_x86_vista]
CopyFiles=PNTIF8I,PNFILES,LIBS,PSI,PNWNPRT8
DependentFiles=PNReg8.exe,emsmtp.dll,PNAuth8.exe,PNdrvCS.ocx,PNDRVUI.DLL,pnemail8.dll,PNMapi8.DLL,PNSvc8.exe,PNSrv8.exe,PNAdd8.exe,PNJob8.exe,PSITIF8.chm,PNTIF8I.DLL,PNTIF8I.INI,PSITIF8C.INI,PNTIF8j.DLL,PNTIF8R.DLL,PNTIF8u.DLL,PNTIF8u.GPD,PSITIF8L.INI,IM31bmp.dil,IM31jpg.dil,IM31png.dil,IM31tif.dil,UNIDRV.DLL,UNIRES.DLL,UNIDRVUI.DLL,STDNAMES.GPD,STDDTYPE.GDL,STDSCHEM.GDL,STDSCHMX.GDL,UNIDRV.HLP
DataFile=PNTIF8u.GPD
ConfigFile=PNDRVUI.DLL
HelpFile=UNIDRV.HLP
DriverFile=PNTIF8R.Dll
DefaultDataType="NT EMF 1.008"
DefaultPort=NUL
Comment=Print to TIFF
PrintProcessor=PNWnPrt8,PNWnPrt8.dll
[PNTIF8_DATA_amd64_vista]
CopyFiles=PNTIF8I,PNFILES,PNFILES_amd64,UNIDRV,LIBS,PSI,PNWNPRT8
DependentFiles=PNSvc8.exe,PNSrv8.exe,PNAdd8.exe,PNJob8.exe,PNReg8.exe,emsmtp.dll,PNAuth8.exe,PNMLX864.dll,pnem864.dll,PNdrvCS.ocx,PNDRVUI.DLL,pnemail8.dll,PNMapi8.DLL,PSITIF8.chm,PNTIF8I.DLL,PNTIF8I.INI,PSITIF8C.INI,PNTIF8j.DLL,PNTIF8R.DLL,PNTIF8u.DLL,PNTIF8u.GPD,PSITIF8L.INI,IM31bmp.dil,IM31jpg.dil,IM31png.dil,IM31tif.dil,UNIDRV.DLL,UNIRES.DLL,UNIDRVUI.DLL,STDNAMES.GPD,STDDTYPE.GDL,STDSCHEM.GDL,STDSCHMX.GDL,UNIDRV.HLP
DataFile=PNTIF8u.GPD
ConfigFile=PNDRVUI.DLL
HelpFile=UNIDRV.HLP
DriverFile=PNTIF8R.Dll
DefaultDataType="NT EMF 1.008"
DefaultPort=NUL
Comment=Print to TIFF
PrintProcessor=PNWnPrt8,PNWnPrt8.dll
[PNWNPRT8]
PNWNPRT8.dll
[PNTIF8I]
PNTIF8I.dll
[PNFILES_amd64]
pnem864.dll
PNMLX864.dll,,,32
[PNFILES]
PNdrvCS.ocx
PNSvc8.exe
PNSrv8.exe
PNAdd8.exe
PNJob8.exe
PNTIF8j.DLL
pnemail8.dll
PNMapi8.DLL,,,32
emsmtp.dll
PNTIF8I.INI
PNTIF8R.DLL
PNDRVUI.DLL
PNTIF8u.GPD
PNTIF8u.DLL
PNAuth8.exe,,,32
PNReg8.exe
[UNIDRV]
UNIDRV.DLL
UNIRES.DLL
UNIDRVUI.DLL
STDNAMES.GPD
UNIDRV.HLP
[LIBS]
IM31bmp.dil
IM31jpg.dil
IM31png.dil
IM31tif.dil
[OEM]
OEMTIF8L.INI
OEMTIF8C.INI
OEMTIF8.chm
[DestinationDirs]
DefaultDestDir=66000
PNWNPRT8=55
[SourceDisksNames.x86]
33 = %disk1%,,,
34 = %disk1%,,,i386
[SourceDisksNames.amd64]
33 = %disk1%,,,
34 = %disk1%,,,amd64
[SourceDisksFiles]
PNWNPRT8.dll=34
PNTIF8U.Dll=34
PNTIF8R.Dll=34
PNTIF8u.GPD=34
PNTIF8I.Dll=34
PNTIF8I.INI=34
PNDRVUI.Dll=34
pnem864.dll=34
PNMLX864.dll=34
PNSvc8.exe=34
PNAuth8.exe=33
PNTIF8J.Dll=33
PSITIF8C.INI=33
PNSrv8.exe=33
PNAdd8.exe=33
PNJob8.exe=33
PNdrvCS.ocx=33
PSITIF8.chm=33
pnemail8.dll=33
PNMapi8.DLL=33
emsmtp.dll=33
PSITIF8L.INI=33
PNReg8.exe=33
IM31bmp.dil=33
IM31jpg.dil=33
IM31png.dil=33
IM31tif.dil=33
[Strings]
PrinterClassName="Printers"
PEERNET="PEERNET Inc."
disk1="PEERNET Image Printer Setup Disk"
[PSI]
PSITIF8L.INI
PSITIF8C.INI
PSITIF8.chm -
Elements 10 and Premiere 10 failing to install on Win7 64bit
I have just putrchased both products which fail to install.
Both fail installing Shared Technologies.
I have captured the logs. How do I send these to Adobe?
The states the installer goes thtrough for Elements 10 are:--
Copying New files
Installing Elements 10
Installing Elements 10 Organizer
Installing required Shared Technologies
Rolling back the Installing Elements 10 Organizer
Rolling back the Installation of Adobe Photoshop Elements 10
The Wizard was interrupted before Adobe Photoshop Elements 10 could be completely installed
Below mentioned application has failed to install: Shared TechnologiesHi,
This document contains troubleshooting steps that can be performed to resolve the issue you are facing:
Troubleshoot installation problems | Photoshop Elements, Premiere Elements
The document also contains a link to the Adobe Support Advisor using which you can upload your log files for us to view it.
One step that usually helps is to navigate to the shared technologies folder ElementsST1Installer (ST1 means Shared technologies 1) in the installation disc. If you have downloaded the software, you will find this in the extracted installation folder. Run the set up file separately and then reinstall the software. -
Z87-G45 Gaming not able to install Win7 x64 with Samsung 840 EVO
I have a brand new:
i5 4570
MSI Z87-G45 Gaming
250GB Samsung 840 EVO
1x 8GB Corsair ValueRam DDR3 1600
I got everything hooked up properly, but I am not able to install Win7 x64 through an USB pen drive (Kingston Datatravel 32GB USB3) I have a proper official and Legit MSDN ISO, formatted by the Win7 USB tool from MS itself.
Note that i do not have an optical device (DVD) installed so I cannot use it 'the old way'.
Bios settings are okay, everything is recognized
USB Legacy - Kingston Datatraveler
HDD Legacy - Samsung 840 EVO
Win7 setup loads properly; but before I can select the Harddrive / SSD to install Win7 on I get prompted that additional (3rd party) drivers are needed to proceed. The volume is not recognized. This happens 9 out of 10 times. In the 10% cases I do get the option to format the SSD and/or create partitions. However, installation fails after all, cannot load or find file ...
What I've tried so far:
Switch out the SATA cables and power cables
Switch through the various SATA ports on the MB 1 through 6
Tried UEFI and UEFI/Legacy (UEFI doesn't seem to work at all)
Update UEFI to V 1.50
All the above result in the case mentioned.
I have succesfully installed the SSD in an other PC, using the same pen drive and ISO and it worked like a charme, thus ruling out that the SSD, pen drive or image is corrupt.
Even when I switched out the SSD after Win7 setup has succesfully copied, unpacked and installed all the files (doing this on the other machine where it works like a charm). Then switching it to the MSI Z87...it fails; starting the setup procedure right from the start, like nothing was ever written on the SSD...
Finally i turned to Win8, and guess what, it installed without any glitches on the MSI Z87
What am I missing here, I would really want to install Win7 instead of Win8
Forgot to enable / disable something in the UEFI? I really don't know, google doesn't give much information on this specific problem (SSD is recognized properly by the BIOS / UEFI as far as I can tell)
The only thing I have not tried out so far is updating the Samsung SSD firmware to the 1.0 version which has been release 3 days ago...
Any clues, tips, hunches??Quote from: Bernhard on 25-October-13, 18:33:41
Did you disable Secure Boot in the BIOS? If not, then Win7 won't load.
Hmmm not sure, thanks for the reply, will have to look into that later today!
I didn't change it from the default setting I think, unless it is part of the Win8 features in the UEFI. All where disabled by default, and I kept them disabled.
Where is Secure Boot listed in the UEFI, and any idea wether it is enabled by default?
::EDIT::
Found it in some screenshots, I cannot recall from the top of my head wether it was enabled or disabled, allthough my gutt feeling says it already is disabled.
http://cdn.pcper.com/files/imagecache/article_max_width/review/2013-05-31/09-MSI_SnapShot_23.gif
http://cdn.pcper.com/files/imagecache/article_max_width/review/2013-05-31/10-MSI_SnapShot_24.gif
Nice overview of the entire UEFI btw: http://www.pcper.com/reviews/Motherboards/MSI-Z87-GD65-Gaming-Motherboard-Review/BIOS-Features-continued -
Hi All,
Hopefully this is in the right place and someone can offer some assistance for me. I will try to lay this out correctly (newbie on this forum).
Have installed WDS on Server 2012 R2. Settings altered...
Setup my server as standard, nothing special. Created boot.wim from a copy of a Dell Win 7 disk, copied locally and imported. Created capture image. Imported numerous drivers (which were installed manually and worked on the client (testing client)). Settings
changed on the WDS server (it is called ntserver29 for reference).
- PXE Response - Respond to all clients...(require administrator approval not ticked)
- AD DS - Computer Account Location - Same Domain as WDS server
- Boot - as default, require user to press f12.
- Client - Joining a Domain - Do not join...ticked.
- DHCP - Neither 'do not listen' and 'configure dhcp options' ticked. (DHCP not installed on that server)
- TFTP - block size (as default) set to 1298 (have changed the registry file from 0 to 512 as previously instructed on an online guide). Enable the TFTP server to negotiate variable window size requests is ticked.
- Network - UDP port policy is set to 'obtain dynamic ports'
- Advanced - Domain Controller - Allow WDS to dynamically discover domain servers (ticked). DHCP Authorisation - Authorize this WDS server in DHCP
- Multicast - Multicast IP set to obtain IP from DHCP. Transfer Settings set to Keey all multicase clients in a session at the same speed.
From the top. Have had issues which seem resolved, will explain further down.
* With the above set. Have built Dell desktop machine with Dell windows 7 disc flat. Installed relevant drivers, some updates and google chrome.
* Using sysprep and the capture image got as far as saving the wim. Was unable to authenticate to the server as it did not even bring up the account login box, just failed to connect (ISSUE 1).
* Chose to test WDS seperate. Copied the image to an external drive. Copied to the RemoteInstall\Images path on the WDS server. This populate the image to the server without involvement from myself. Restarted the server.
* When rebooting the desktop, device only shows Windows 7 Setup and Windows 7 Setup Capture (my 2 original boot images) and nothing else (ISSUE 2).
Bit stuck from there. WDS didnt work prior to uninstalling a specific update and re-installing a fresh WDS.
Any advice would be GREATLY appreciated. I dont lay claim to being knowledgeable about the system, just looking to learn and get this working for the business. Happy to answer questions and will keep checking in.
Many Thanks, hopefully the above makes sense to someone.
MarkIf this will help any. Obtained the details from CMD.
Unattend file present: No
Status: Enabled
Boot Images for ia64
Image count: 0
Image Information:
There are no images that match the specified criteria.
Boot Images for arm
Image count: 0
Image Information:
There are no images that match the specified criteria.
===============================================================================
Summary:
Total number of boot image stores: 4
Total number of boot images: 3
INSTALL IMAGES
===============================================================================
Image Group DistributionGroup
Name: DistributionGroup
Security: O:BAG:DUD:(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;;FA;;;BA)(A;OICIIO;GA;;;C
O)(A;OICI;0x1200a9;;;BU)(A;CI;LC;;;BU)(A;CI;DC;;;BU)
Image format: WIM
Image count: 6
Image Information:
Dell Optiplex 3020 Test
File name: Dell Optiplex 3020.wim
Image name: Dell Optiplex 3020 Test
Description: Dell Optiplex 3020 Test Capture
ID: <Not Assigned>
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 12172102562 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 15 October 2014 19:58:39
Last modified: 15 October 2014 19:58:46
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\Dell Optiplex 30
20.wim
OS version: Microsoft® Windows® Operating System, 6.1.7601
Service pack level: 1
User filter: O:S-1-5-21-1738485378-1525038498-1803697834-16854G:DUD:(A;;FA;;;BA)
(A;;FA;;;SY)(A;;FA;;;S-1-5-21-1738485378-1525038498-1803697834-16854)(A;;0x1200a
9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
<Error>
Windows 7 HOMEBASIC
File name: install-(2).wim
Image name: Windows 7 HOMEBASIC
Description: Windows 7 HOMEBASIC
ID: {587B12B6-D6D9-4F13-8B81-E962AC7078D7}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8306998658 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:18
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(2).wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 HOMEPREMIUM
File name: install-(3).wim
Image name: Windows 7 HOMEPREMIUM
Description: Windows 7 HOMEPREMIUM
ID: {150666C9-B2D9-4BA0-873C-3A4B7BF986C3}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8747698450 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:21
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(3).wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 PROFESSIONAL
File name: install-(4).wim
Image name: Windows 7 PROFESSIONAL
Description: Windows 7 PROFESSIONAL
ID: {1849C3AE-E2F6-4EC5-9DBD-AD0FD2223185}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8627895833 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:22
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(4).wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 ULTIMATE
File name: install-(5).wim
Image name: Windows 7 ULTIMATE
Description: Windows 7 ULTIMATE
ID: {280A4685-155E-4565-B413-D60BB8F105E7}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8785899727 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:24
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(5).wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 STARTER
File name: install.wim
Image name: Windows 7 STARTER
Description: Windows 7 STARTER
ID: {1C935F5A-1835-49A3-AE1A-B64910FFF925}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8250904871 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:16
Default language: English (United States)
Other languages:
Dependent files:
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install.wim
\\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
NON-NATIVE IMAGES
===============================================================================
===============================================================================
Summary:
Total number of non-wim image groups: 0
Total number of non-wim images: 0
An error occurred while trying to execute the command.
Error Code: 0xC10408B3
Error Description: One or more errors occurred while processing the command. Rev
iew the error logs for more information.
C:\Users\administrator> -
Kb2920189 fails to install on Windows 2012 R2 Essentials
Hello,
I have a 2012 R2 Essentials server that fails to install the UEFI KB2920189 update. All other updates installed fine. It's running two disks, one has 8.1 the other has 2012 R2 Esssentials in dual boot mode. No VM. I have heard reports
of successful installs of this kb2920189 update that basically bricks the OS on reboot. I would like to avoid this. The error code during the failed installation is 800F0922.
ThanksHi,
Based on your description, I understand that you failed to install KB2920189 with error 800F0922.
Please refer to following operations and check if can help you to solve this issue.
Refer to the KB (KB947821), and use the inbox Deployment Image Servicing and Management (DISM) tool. Then install
this update again.
Please
reset Windows Update components and monitor the result.
Please perform a
clean boot and check if you can install this update successfully.
If this issue still persists, please navigate to: %windir%\Windowsupdate.log and check the log file if can
find some more clues.
For more details, please refer to the following KB.
How to read the Windowsupdate.log file
Hope this helps.
Best regards,
Justin Gu -
Fail to install Distibution Point on Windows Server 2012
I have been trying to install a distribution point via sccm 2012 on a windows 2012 server. I keep getting errors about the drive not found (distribution manager failed to verify drive specified by user on distribution point) and it won't install. It worked
on all the other servers I tried, but this one keeps giving trouble.
Does anyone have any idea as to the cause?
I put an extract of the log file here:
Get site system FQDN and account information from DB for ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\ SMS_DISTRIBUTION_MANAGER 31/12/2013 13:56:18 5848 (0x16D8)
Get site system FQDN and account information from DB for ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\ SMS_DISTRIBUTION_MANAGER 31/12/2013 13:56:19 5848 (0x16D8)
Failed to get SMS_DistributionPoint object SMS_DISTRIBUTION_MANAGER 31/12/2013 13:56:20 5848 (0x16D8)
DPConnection::Connect: For ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\, logged-on as SESVANDERHAVE\svc_scom_msaa SMS_DISTRIBUTION_MANAGER 31/12/2013 13:56:32 3724 (0x0E8C)
ConfigureDP SMS_DISTRIBUTION_MANAGER 31/12/2013 13:56:32 3724 (0x0E8C)
Sleep 20 minutes... SMS_DISTRIBUTION_MANAGER 31/12/2013 13:56:44 1724 (0x06BC)
Sleep 20 minutes... SMS_DISTRIBUTION_MANAGER 31/12/2013 13:56:49 1724 (0x06BC)
Sleep 20 minutes... SMS_DISTRIBUTION_MANAGER 31/12/2013 13:56:54 1724 (0x06BC)
DP registry settings have been successfully updated on HUSOWINFP01.sesvanderhave.net SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:05 3724 (0x0E8C)
STATMSG: ID=9500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=8216 TID=3724 GMTDATE=di dec 31 12:57:05.905 2013 ISTR0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\" SMS_DISTRIBUTION_MANAGER 31/12/2013
13:57:05 3724 (0x0E8C)
STATMSG: ID=9503 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=8216 TID=3724 GMTDATE=di dec 31 12:57:05.905 2013 ISTR0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\" SMS_DISTRIBUTION_MANAGER 31/12/2013
13:57:05 3724 (0x0E8C)
ConfigurePXE SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:05 3724 (0x0E8C)
Failed to get SMS_DistributionPoint object SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:07 3724 (0x0E8C)
CDistributionManager::ConfigurePXE failed; 0x80041002 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:07 3724 (0x0E8C)
No need to initialize monitoring task on HUSOWINFP01.sesvanderhave.net SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:16 3724 (0x0E8C)
Creating, reading or updating IIS registry key for a distribution point. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:18 5848 (0x16D8)
IISPortsList in the SCF is "80". SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:18 5848 (0x16D8)
IISSSLPortsList in the SCF is "443". SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:18 5848 (0x16D8)
IISWebSiteName in the SCF is "". SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:18 5848 (0x16D8)
IISSSLState in the SCF is 224. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:18 5848 (0x16D8)
DP settings have been updated to HUSOWINFP01.sesvanderhave.net. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:21 3724 (0x0E8C)
DPConnection::Disconnect: Revert to self SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:22 3724 (0x0E8C)
Sleep 1231 seconds... SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:22 3724 (0x0E8C)
Failed to get SMS_DistributionPoint object SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:22 5848 (0x16D8)
Found notification for package 'SES00003' SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:32 3724 (0x0E8C)
Found notification for package 'SES00004' SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:32 3724 (0x0E8C)
Package Thread Limit: 3 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:32 3724 (0x0E8C)
Retry interval: 30 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:32 3724 (0x0E8C)
DP upgrade thread Limit: 5 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:32 3724 (0x0E8C)
DP upgrade retry interval: 20 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:32 3724 (0x0E8C)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:32 3724 (0x0E8C)
Starting package processing thread, thread ID = 0x2274 (8820) SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:32 3724 (0x0E8C)
Starting package processing thread, thread ID = 0x9B8 (2488) SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:33 3724 (0x0E8C)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:33 3724 (0x0E8C)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=8216 TID=8820 GMTDATE=di dec 31 12:57:33.112 2013 ISTR0="SES00003" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SES00003" SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:33 8820 (0x2274)
Retrying package SES00003 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:33 8820 (0x2274)
No action specified for the package SES00003. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:33 8820 (0x2274)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=8216 TID=2488 GMTDATE=di dec 31 12:57:33.112 2013 ISTR0="SES00004" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SES00004" SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:33 2488 (0x09B8)
Retrying package SES00004 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:33 2488 (0x09B8)
No action specified for the package SES00004. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:33 2488 (0x09B8)
Start adding package to server ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\... SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 8820 (0x2274)
Start adding package to server ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\... SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 2488 (0x09B8)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 7936 (0x1F00)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 3404 (0x0D4C)
The distribution point ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 7936 (0x1F00)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 7936 (0x1F00)
The distribution point ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 3404 (0x0D4C)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 3404 (0x0D4C)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 8820 (0x2274)
Thread Handle = 00000000000031DC SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 8820 (0x2274)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 8820 (0x2274)
DP thread with thread handle 00000000000031DC and thread ID 7936 ended. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 8820 (0x2274)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 2488 (0x09B8)
Thread Handle = 00000000000016A8 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 2488 (0x09B8)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 2488 (0x09B8)
DP thread with thread handle 00000000000016A8 and thread ID 3404 ended. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:35 2488 (0x09B8)
Package SES00003 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 8820 (0x2274)
The package and/or program properties for package SES00003 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 8820 (0x2274)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=SES00003, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 8820 (0x2274)
Package SES00004 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 2488 (0x09B8)
The package and/or program properties for package SES00004 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 2488 (0x09B8)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=SES00004, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 2488 (0x09B8)
StoredPkgVersion (1) of package SES00003. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 8820 (0x2274)
SourceVersion (1) of package SES00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 8820 (0x2274)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=8216 TID=8820 GMTDATE=di dec 31 12:57:36.247 2013 ISTR0="Configuration Manager Client Package" ISTR1="SES00003"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SES00003" SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 8820
(0x2274)
Failed to process package SES00003 after 1 retries, will retry 99 more times SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 8820 (0x2274)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 8820 (0x2274)
StoredPkgVersion (1) of package SES00004. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 2488 (0x09B8)
SourceVersion (1) of package SES00004. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 2488 (0x09B8)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=8216 TID=2488 GMTDATE=di dec 31 12:57:36.282 2013 ISTR0="Configuration Manager Client Upgrade Package"
ISTR1="SES00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SES00004" SMS_DISTRIBUTION_MANAGER 31/12/2013
13:57:36 2488 (0x09B8)
Failed to process package SES00004 after 1 retries, will retry 99 more times SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 2488 (0x09B8)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 31/12/2013 13:57:36 2488 (0x09B8)I uninstalled the WDS according to the information on this site: http://myitforum.com/myitforumwp/2011/11/08/configmgr-2012-no-need-to-manually-install-wds/
But it still keeps giving me errors about the disk not being valid, it does that wether I choose a disk or leave the default values.
DPConnection::Connect: For ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\, logged-on as SESVANDERHAVE\svc_scom_msaa SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:33 2964 (0x0B94)
ConfigureDP SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:33 2964 (0x0B94)
Upgrading DP with ID 16777238. Thread 0x1bdc. Used 1 threads out of 5. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:50 7492 (0x1D44)
Processing 16777238.INS SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:50 7132 (0x1BDC)
Sleep 20 minutes... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:50 7492 (0x1D44)
DPID 16777238 - NAL Path ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\ , ServerName = HUSOWINFP01.SESVANDERHAVE.NET, DPDrive = D:, IsMulticast = 0, PXE = 1, RemoveWDS = 0 SMS_DISTRIBUTION_MANAGER 6/01/2014
8:49:50 7132 (0x1BDC)
Created policy provider trigger for ID 16777238 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:50 7692 (0x1E0C)
DPConnection::Connect: For ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\, logged-on as SESVANDERHAVE\******** SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:54 7132 (0x1BDC)
Failed to find a valid drive on the distribution point ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\ SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:55 7132 (0x1BDC)
Sleep 20 minutes... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:55 7492 (0x1D44)
DPConnection::Disconnect: Revert to self SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:56 7132 (0x1BDC)
Failed to install DP files on the remote DP. Error code = 15 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:56 7132 (0x1BDC)
Drive D: is not valid. Error = 15 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:56 7132 (0x1BDC)
STATMSG: ID=2360 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=4552 TID=7132 GMTDATE=ma jan 06 07:49:56.907 2014 ISTR0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\"
ISTR1="HUSOWINFP01.SESVANDERHAVE.NET" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\" SMS_DISTRIBUTION_MANAGER 6/01/2014
8:49:56 7132 (0x1BDC)
Will try again after 20 mins ... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:56 7132 (0x1BDC)
DP registry settings have been successfully updated on HUSOWINFP01.sesvanderhave.net SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:58 2964 (0x0B94)
STATMSG: ID=9500 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=4552 TID=2964 GMTDATE=ma jan 06 07:49:58.295 2014 ISTR0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\" SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:58 2964
(0x0B94)
STATMSG: ID=9503 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=4552 TID=2964 GMTDATE=ma jan 06 07:49:58.295 2014 ISTR0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\" SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:58 2964
(0x0B94)
ConfigurePXE SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:58 2964 (0x0B94)
Failed to get SMS_DistributionPoint object SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:58 2964 (0x0B94)
CDistributionManager::ConfigurePXE failed; 0x80041002 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:49:58 2964 (0x0B94)
Sleep 20 minutes... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:00 7492 (0x1D44)
Sleep 20 minutes... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:05 7492 (0x1D44)
Initialize monitoring task on HUSOWINFP01.sesvanderhave.net SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:16 2964 (0x0B94)
Failed to get object class SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:16 2964 (0x0B94)
ExecStaticMethod failed (80041002) SMS_DistributionPoint, RegisterDPHealthMonTask SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:16 2964 (0x0B94)
Failed to register DP health monitoring task on HUSOWINFP01.sesvanderhave.net. error = 0x80041002 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:16 2964 (0x0B94)
DP settings have been updated to HUSOWINFP01.sesvanderhave.net. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:21 2964 (0x0B94)
DPConnection::Disconnect: Revert to self SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:21 2964 (0x0B94)
Sleep 60 seconds... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:21 2964 (0x0B94)
Found notification for package 'SES00003' SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:31 2964 (0x0B94)
Found notification for package 'SES00004' SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:31 2964 (0x0B94)
Package Thread Limit: 3 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:31 2964 (0x0B94)
Retry interval: 30 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:31 2964 (0x0B94)
DP upgrade thread Limit: 5 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:31 2964 (0x0B94)
DP upgrade retry interval: 20 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:31 2964 (0x0B94)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:31 2964 (0x0B94)
Starting package processing thread, thread ID = 0x12CC (4812) SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:31 2964 (0x0B94)
Starting package processing thread, thread ID = 0xDD8 (3544) SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:32 2964 (0x0B94)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:32 2964 (0x0B94)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=4552 TID=4812 GMTDATE=ma jan 06 07:50:32.429 2014 ISTR0="SES00003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SES00003" SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:32 4812 (0x12CC)
Retrying package SES00003 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:32 4812 (0x12CC)
No action specified for the package SES00003. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:32 4812 (0x12CC)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=4552 TID=3544 GMTDATE=ma jan 06 07:50:32.475 2014 ISTR0="SES00004" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7=""
ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SES00004" SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:32 3544 (0x0DD8)
Retrying package SES00004 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:32 3544 (0x0DD8)
No action specified for the package SES00004. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:32 3544 (0x0DD8)
Start adding package to server ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:34 4812 (0x12CC)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:34 8896 (0x22C0)
The distribution point ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:34 8896 (0x22C0)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:34 8896 (0x22C0)
Start adding package to server ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:34 3544 (0x0DD8)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:34 4628 (0x1214)
The distribution point ["Display=\\HUSOWINFP01.sesvanderhave.net\"]MSWNET:["SMS_SITE=SES"]\\HUSOWINFP01.sesvanderhave.net\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:34 4628 (0x1214)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:34 4628 (0x1214)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
Thread Handle = 0000000000002BE0 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
DP thread with thread handle 0000000000002BE0 and thread ID 8896 ended. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
Thread Handle = 0000000000002CF0 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
DP thread with thread handle 0000000000002CF0 and thread ID 4628 ended. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
Package SES00004 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
The package and/or program properties for package SES00004 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=SES00004, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
Package SES00003 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
The package and/or program properties for package SES00003 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
CDistributionSrcSQL::UpdateAvailableVersion PackageID=SES00003, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
StoredPkgVersion (1) of package SES00004. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
SourceVersion (1) of package SES00004. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=4552 TID=3544 GMTDATE=ma jan 06 07:50:35.736 2014 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="SES00004" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SES00004" SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
Failed to process package SES00004 after 77 retries, will retry 23 more times SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 3544 (0x0DD8)
StoredPkgVersion (1) of package SES00003. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
SourceVersion (1) of package SES00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BEHQWINSCCM02.sesvanderhave.net SITE=SES PID=4552 TID=4812 GMTDATE=ma jan 06 07:50:35.829 2014 ISTR0="Configuration Manager Client Package" ISTR1="SES00003" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SES00003" SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
Failed to process package SES00003 after 77 retries, will retry 23 more times SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:35 4812 (0x12CC)
Sleep 20 minutes... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:36 7492 (0x1D44)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:37 2964 (0x0B94)
Sleep 1828 seconds... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:37 2964 (0x0B94)
Sleep 20 minutes... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:41 7492 (0x1D44)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:42 2964 (0x0B94)
Sleep 1823 seconds... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:42 2964 (0x0B94)
Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:47 2964 (0x0B94)
Sleep 1818 seconds... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:47 2964 (0x0B94)
Sleep 1818 seconds... SMS_DISTRIBUTION_MANAGER 6/01/2014 8:50:47 2964 (0x0B94) -
Install of CUCM 8.6.1.10000-43 on VMWare fails on installing progmeter
Hi, Everyone
First time post here, and first time installing CUCM (any version).
I built a VM using a downloaded OVA template for CUCM 6.5.1.10000-43, and the install fails with a critical stop. Once I figured out how to dump logs to the virtual serial port, and looked at the install.log, I found the following information that looks like where the install failed (these are the only LVL::Error and LVL::Critical messages in the log).
It looks like install failed to install the progmeter application component.
Does anyone know what this app does? Any ideas on why it might have failed to install and possible workaround?
I may already have the answer to the question, as I'm attempting install on a VM running on VMWare vServer (rather than ESX/ESXi/vSphere). It is possible that simply being on an unsupported configuration is my problem. I'm trying to work with the equipment immediately available to me, but fully understand that I may have set myself up for failure by even attempting this.
Any help is appreciated greatly.
Regards,
Sean C
INSTALL LOG SNIPPET
08/17/2011 17:51:51 component_install|File:/opt/cisco/install/bin/component_install:743, Function: exec_progmeter(), /opt/cisco/install/bin/progmeter failed (1)|<LVL::Error>
08/17/2011 17:51:51 appmanager.sh|Internal Error, File:/usr/local/bin/base_scripts/appmanager.sh:155, Function: install(), failed to install application components|<LVL::Critical>
08/17/2011 17:51:51 post_install|File:/opt/cisco/install/bin/post_install:869, Function: install_applications(), /usr/local/bin/base_scripts/appmanager.sh -install failed (1)|<LVL::Error>
08/17/2011 17:51:51 post_install|Exiting with result 1|<LVL::Info>
08/17/2011 17:51:51 post_install|INSTALL_TYPE="Basic Install"|<LVL::Debug>
08/17/2011 17:51:51 post_install|File:/opt/cisco/install/bin/post_install:570, Function: check_for_critical_error(), check_for_critical_error, found /common/log/install/critical.log, exiting|<LVL::Error>
08/17/2011 17:51:52 post_install|(CAPTURE) Mail notification cancelled - smtp server address for email not found! [/usr/local/platform/conf/platformConfig.xml]|<LVL::Debug>
08/17/2011 17:51:52 display_screen|Arguments: "Critical Error" "The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.
"/opt/cisco/install/callmanager/scripts/cm_msa_post.sh install PostInstall 8.6.1.10000-43 8.6.1.10000-43 /usr/local/cm/ /usr/local/cm/ /common/log/install/capture.txt " terminated. Exceeded max time (360)
The system will now halt.
Continuing will allow you to dump diagnostic information before halting." "Continue"|<LVL::Debug>Hi,
Has anyone found a fix for this?
I am trying to run call manager 8.6.1 on the following enviroment
VMware ESXI 4.1
4GB of RAM
80 GB HDD Space
I have allocated the VM one CPU
In regards to vsergeyey reponse I have checked the network adapter and this is flexible.
I have run the OVA template firstly before mounting the image
I have tried installing numerous times.
Each and every time near the "Installing Database Component" I get the following error; -
Snow Leopard fails to install - Tech Support and Genius Bar can't fix it
I am having an exceedingly difficult time installing Snow Leopard. I have tried everything I can think of and tech support AND the Genius Bar have failed me so far.
The Details:
Every time I install SL it starts off well but sometime between 18 minutes remaining and 6 minutes remaining it fails. I get an error message that says there was an error that prevented installation. Looking in the installer log gives me a little more information. It usually has 15 or so errors, the last of which is always a very long line saying some package failed to install/unpack/be copied. The odd thing is that the file name is different every time.
So far I have tried:
Repairing the disk and installing
Installing from a different install DVD
Installing from external hard drive at the Genius Bar
Installing using RAM borrowed from the Genius Bar
Wiping the HD completely. I erased all my partitions and tried to install on a completely blank hard drive with a single HFS+ partition
I can only think of a few things that can cause the install to fail: DVD, optical drive, RAM, files on HDD, and HDD hardware. I think I've eliminated all those possibilities except HDD hardware. Changing that on a MacBook isn't trivial and I don't have one handy. Also I would think a HDD problem, or any hardware problem, would cause all sorts of errors and with the exception of this the machine has no serious problems and apps crash only occasionally. I've had no system crashes for as long as I can remember.
I have a Time Machine back up and have successfully restored my old Leopard System onto the MacBook (twice now) so at least I have the option to just give up on SL if I want to. As an aside, restoring from TM went well but not perfectly. Next time I install an OS I will be making a disk image backup. Does anyone else have any ideas? If you solve this problem I'll be eternally grateful and very impressed.
Thanks in advance
JayI'm sorry. I should have answered when you asked about RAM the first time. I have 2GB. I have tried installing with that, and I tried installing with RAM at the Genius Bar. I don't know how much the guy used at the Genius Bar.
Last night I restored from time machine so I currently have Leopard installed on the machine. After the restoration my email archive is little strange, I had to re-authorize iTunes and various other annoyances pop up but it runs without any problems. -
System Image Utility 10.6.3 - fails when creating NetBoot image from DVD
System Image Utility 10.6.3, trying to create a NetBoot image from a bundled installer disc that came with a 27" Late 2009 iMac (iMac11,1). Image creation fails consistently, since the image that System Image Utility creates is only 901M.
Anyone see this before?
Don
--------- System Image Utility log ----------
Workflow Started (2010-06-16 14:03:02 -0700)
Starting action: Define Image Source
Finished running action: Define Image Source
Starting action: Create Image
Starting image creation process...
Create NetBoot Image
Initiating NetBoot from Install Media.
Creating working path at /Library/NetBoot/NetBootSP0/NetBoot of Mac OS X Install DVD
Creating disk image (Size: 901 MB)
Finalizing disk image.
created: /Library/NetBoot/NetBootSP0/NetBoot of Mac OS X Install DVD/NetBoot.dmg
Attaching disk image
Installing to destination volume
2010-06-16 14:03:38.126 installer[2365:6f03] Looking for system packages
2010-06-16 14:03:38.129 installer[2365:6f03] no system packages found
2010-06-16 14:03:38.130 installer[2365:6f03] No or Invalid system receipts found on /private/tmp/mnt.LjFArn
2010-06-16 14:03:38.130 installer[2365:6f03] Attempting fallback using: /System/Library/PrivateFrameworks/SystemMigration.framework/Resources/FallbackS ystemFiles.plist
2010-06-16 14:03:38.175 installer[2365:6f03] Finding system files...
2010-06-16 14:03:38.619 installer[2365:6f03] Writing system path cache.
2010-06-16 14:03:38.623 installer[2365:6f03] Error writing cache to /private/tmp/mnt.LjFArn/Library/Caches/com.apple.FindSystemFiles.plist
2010-06-16 14:03:38.625 installer[2365:6f03] Failed to enumerate /tmp/mnt.LjFArn/Library/Caches, cannot prune (
"com.apple.userpictureCache"
installer: Package name is Mac OS X
installer: Installing at base path /private/tmp/mnt.LjFArn
installer: The install failed (There is not enough space on this disk to install the selected items. Deselect at least 6.46 GB and try again.)
Script is done.
NetBoot creation failed.
Image creation process finished...
Stopping image creation.
Image creation failed.Brian Nesse wrote:
Hi Don, here's my guess...
The 901 number is additional space added in the scripts. This indicates that the source image size was 0.
Since you are making a NetBoot from Install media, under the covers the installer process is being run to create a NetBoot volume. The media shipped with the 27" iMac is most likely CPU specific and thus the installation fails because you are trying to create the image (i.e. install the system) on an unsupported CPU.
In order to produce a NetBoot from the install media, you'll have to create it on the 27" iMac.
Hi Brian,
Thanks for the response. This makes perfect sense. I'll give this a try and shout back!
Thanks,
Don -
Pod Touch 32GB MTP USB device has failed to install and can't sync.
After updating iTunes on my Win7 64bit PC, when I plug my iPod Touch 32GB in, I get the error message "MTP USB device has failed to install" and can't sync. Yesterday, everything worked well.
Need help, please!Thank you. I removed iTunes, QT, Safari and related software, then applied a Windows update and reinstalled iTunes and related software. It solved my problem and let me sync my iPod.
Thanks! -
Hello,
My computer was working perfectly with Win7 for about 2years until I formatted on monday to clean a little bit my drives ... Since then I'm unable to install windows again. I have the 0x80070570 error.
The complete error message is:
Windows cannot install required files. The file may be corrupt or missing. Make sure that all files required for installation are available and restart the installation. Error code:0x80070570.
What is the 0x80070570 error when installing Win7 or Win8 or Win 8.1 on a clean SSD/HDD ?! These versions are full from MSDN.
What I did already:
check my RAM (16go gskill)
remove unnecessary hard drives
replace my "old" SSD with a clean new one
remove my sound cards
remove the mouse and use only keyboard
reset the BIOS
check every LED on the motherboard (asus sabertooth z77) and there is no problem
What are the problems?
Thanks,
Adrien.Hi,
If all images cannot be installed, we have a reason to suspect the hardware cause.
If you use two memory slots to get 16G RAM, I suggest you test with just one (8G) to check the result.
Alex Zhao
TechNet Community Support
Maybe you are looking for
-
Hi everyone, While opening a form in one of the Oracle Retail applications the error: FRM:41067-Cannot find Menu Item:Invalid ID is thrown. However when we click OK, the error goes off and system lets us to continue with using the form. On another fo
-
Acura TSX 2007 - Bluetooth doesn't work correctly
I have an Acura TSX 2007. I can't initiate a call from my iPhone 3GS and have it connect via car's bluetooth, even though the iPhone and the car are paired. The call would connect but I can't hear the person on the other end, not through my car's spe
-
A few Dreamweaver CS 4 questions
hello, I have Dreamweaver CS 4 on a computer that is currently not connected to the internet. My question is: is it feasable to code on dreamweaver on this computer, or will I run into problems if I do not update it? The kind of problems I am worried
-
I have a problem with my mini ipod. I went to update it with songs so when i plugged to ipod in to update. i get this message saying " attempting to copy to the disk my name failed The disk could not be read from or written to." Everything is updated
-
How to deploy web service in EP
Hi Gurus!!! I am trying to connect GRC to EP. GRC system is trying to reach EP via a web service but it is giving connection failed. But it is not giving any error. I have a feeling that web service is not published. Somehow I published web service i