I have been imaging 8 machines at a time. i am using the quick partition, due to we have hundreds to image. I have been doing this for a while. Suddenly 5-6 of the machines will fail with the error below. Then when you rerun the same machine may or may not image fime the next time. It does not matter if it is an unknown machine or a known machine. Please help i am pulling out my hair. FALSE, HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\diskvolume.cpp,1172) OSDDiskPart 5/12/2010 11:29:37 AM 1516 (0x05EC) Format failed (0x80070057) OSDDiskPart 5/12/2010 11:29:37 AM 1516 (0x05EC) CVolume::Format( sDrive.c_str(), (*iter)->getFilesystem(), (*iter)->getVolumeName().c_str(), 0, (*iter)->getIsQuickFormat() ? CVolume::foptQuick : 0, FormatProgressCallback, NULL), HRESULT=80070057 (e:\nts_sms_fre\sms\client\osdeployment\osddiskpart\main.cpp,936) OSDDiskPart 5/12/2010 11:29:37 AM 1516 (0x05EC) Failed to format drive C: (0x80070057) OSDDiskPart 5/12/2010 11:29:37 AM 1516 (0x05EC) FormatPartitions(oDisk), HRESULT=80070057 (e:\nts_sms_fre\sms\client\osdeployment\osddiskpart\main.cpp,1465) OSDDiskPart 5/12/2010 11:29:37 AM 1516 (0x05EC) Failed to format partition(s) for disk 0 (0x80070057) OSDDiskPart 5/12/2010 11:29:37 AM 1516 (0x05EC) OSDDiskPart.exe failed: 0x80070057 OSDDiskPart 5/12/2010 11:29:37 AM 1516 (0x05EC) Process completed with exit code 2147942487 TSManager 5/12/2010 11:29:37 AM 1440 (0x05A0) !--------------------------------------------------------------------------------------------! TSManager 5/12/2010 11:29:37 AM 1440 (0x05A0) Failed to run the action: Partition Disk. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 5/12/2010 11:29:37 AM 1440 (0x05A0) Sending status message . . . TSManager 5/12/2010 11:29:37 AM 1440 (0x05A0) Am I needing to place more information in this. I have not recieved one response. Has there not been antbody else have this issue ever?

Did you ever find a fix for this? I'm having the same issue on one of my machines. thankshttp://nikifoster.blogspot.com/

No fix found as of yet. Problem is still random/intermittent. All assistance welcomed.

I too am having this problem. Unable to find a consistent cause.-Richard

what os is it ? how many partitions listed using diskpart ? My step by step SCCM Guides I'm on Twitter > ncbrady

I am also having this same issue. Some machines format and partition without any problem. Some are failing to format the partition. This seems to be random as the process wll work, then fail when doing the process over again on the same machine. This is a MDT 2010 Update 1 template task sequence installing Win7 Enterprise (custom collected image). My TS is only adding one partition using 100% disk space and quick format. This issue is getting pretty annoying :) Almost reminds me of the Uberbug in XP (Set Diskpart BIOS Compatibility Mode is disabled in the TS). Here is the OSDISKPART section of the SMSTS.log ==============================[ OSDDiskPart.exe ]============================== Command line: "osddiskpart.exe" Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL' Reading partition size info for partition 0 Remaining size before partition: 80023265280 size units: SIZE_PERCENT 100% size specified. Remaining size after partition 0: 0 Checking volume 'C:' for BitLocker Volume 'C:' is on disk '0l' 0, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\encryptablevolume.cpp,368) Volume 'C:' is not an encryptable volume Checking volume 'D:' for BitLocker Checking volume 'X:' for BitLocker Command line for extension .exe is "%1" %* Set command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\osddiskpart.txt" Executing command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\osddiskpart.txt" Process completed with exit code 0 Formatting partitions Formatting drive C: with NTFS filesystem, method quick Creating instance of service loader Loading service Waiting for service to initialize Querying for software providers Found a VDS software provider Querying for IVdsSwProvider Querying for packs Found a VDS pack Querying for IVdsPack Querying for volumes Found a VDS software provider Querying for IVdsSwProvider Querying for packs Found a VDS pack Querying for IVdsPack Querying for volumes Found a VDS volume Querying for IVdsVolumeMF Querying for access paths Found a VDS pack Querying for IVdsPack Querying for volumes Found a VDS volume Querying for IVdsVolumeMF Querying for access paths Found a volume with access path 'C:\' Querying for IVdsVolume Querying for IVdsVolumeMF FALSE, HRESULT=80070057 (e:\nts_sms_fre\sms\framework\tscore\diskvolume.cpp,1172) Format failed (0x80070057) CVolume::Format( sDrive.c_str(), (*iter)->getFilesystem(), (*iter)->getVolumeName().c_str(), 0, (*iter)->getIsQuickFormat() ? CVolume::foptQuick : 0, FormatProgressCallback, NULL), HRESULT=80070057 (e:\nts_sms_fre\sms\client\osdeployment\osddiskpart\main.cpp,936) Failed to format drive C: (0x80070057) FormatPartitions(oDisk), HRESULT=80070057 (e:\nts_sms_fre\sms\client\osdeployment\osddiskpart\main.cpp,1465) Failed to format partition(s) for disk 0 (0x80070057) OSDDiskPart.exe failed: 0x80070057 Process completed with exit code 2147942487 !--------------------------------------------------------------------------------------------! Failed to run the action: Format and Partition Disk. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows)

Surfing around I discovered this posted by another user. Well it turns out that it is not actually an access is denied error but incorrect function. There seems to be an error with the ztisetvariable.wsf script. If you modify that script with the following line it should work. I am still investigating the root cause of the problem. oEnvironment.Item("OSDDiskpartBiosCompatibilityMod e") = oEnvironment.Item("TRUE")

I get this problem randomly too. It's a huge pain when I have technicians in the field reimaging or settin up new machines, it ruins a PXE deployment like clockwork. They end up having to partition manually, and I have to "reset" the PXE sequence for the collection. Anyone ever find a sure fire fix? What is real funny is that if I run a diskpart manually and try to partition the disk on my own it works until I get to the format step. Diskpart will say "Parameter is Incorrect" I simply press the up arrow and then enter to repeat teh command and it may say "parameter incorrect" numerous times. I've seen up to 20 times before. Eventually it will format the disk. If I reboot after this I generally am able to have the machine run the task sequence correctly. Also as you mentioned this does not happen all the time, it's totally random. This is a sure fire bug, it happens on all models of machines. RPM666, did that modification of the script seem to fix your problem?

I get this problem randomly too. It's a huge pain when I have technicians in the field reimaging or settin up new machines, it ruins a PXE deployment like clockwork. They end up having to partition manually, and I have to "reset" the PXE sequence for the collection. Anyone ever find a sure fire fix? What is real funny is that if I run a diskpart manually and try to partition the disk on my own it works until I get to the format step. Diskpart will say "Parameter is Incorrect" I simply press the up arrow and then enter to repeat teh command and it may say "parameter incorrect" numerous times. I've seen up to 20 times before. Eventually it will format the disk. If I reboot after this I generally am able to have the machine run the task sequence correctly. Also as you mentioned this does not happen all the time, it's totally random. This is a sure fire bug, it happens on all models of machines. RPM666, did that modification of the script seem to fix your problem? Have not had a chance to try and test.

No that script looked to only apply to SMS 2003, no resolution has been found.

Does the machine have more than one physical disk ?? Michaelhttp://kongkuba1.spaces.live.com

Hello everybody, This seems not be related with a Bug, could be related with the disk or the SATA controller. Have 3 questions..... Do you have MDT integration? Are you doing Quick Format during the formating steps? Is that is true, could you try to do a Normal Format, and make the same test? Best Regards

1. At the time of these issues MDT integration was not installed 2. Quick Format 3. As I recall a Normal format would function correctly. Systems have only Single Disks and identical BIOS configurations. On a side note, We completely rebuilt our entire SCCM environment and now no longer have this problem.

Hello RPM666 Sory to hear that. One more question, had you tried to change SATA modes in your BIOS configurations? Best regards,

My problem was that the partition disk section of the task sequence defined static sizing of the partition(s). Once I removed the statics and added use 100% of disk, I was able to get past this error.