XPSP2 Exe corrupt?

[kippy13]

Hi,
I am doing some install work with XPSP2 at the moment and havent come across this issue before.
I have the SP2 exe file, and it runs and installs okay on most machines, however on two machines when the files are in the extracting phase the extraction stops and an error pops up "File Corrupt"
I have copied over a known working file but the same issues occurs. This is happening to two machines, the only thing in common I can see is that they are in a difference OU to the others and may, but should not, be efeceted by different GPO's.
The accounts installing the SP are local admin on the machines.
Anyone come across this issue before?
Kippy

 

[TheLad]

Have you got any virus scanning application running on the affected desktops and does disabling it stop the issue?

--------------------------------------
"Insert funny comment in here!"
--------------------------------------

 

[Glenn9999]

For being a file so big, sometimes you get little errors in copying or the like, or timeout errors on access. Sometimes I'd run the file on CD and get an error, but copy the file to the hard drive and it would run just fine. Actually this is one of the reasons I've taken to burning an MD5 file (I have a program that generates and checks them here) along with my other files so I can check them for accuracy.

If it's just these two machines, you might start looking at hardware (slow drives, or minor malfunctions).

 

[kippy13]

Cheers for the replies guys.
Just to clarify, The company I am deploying for has 4500 machines, across a number of sites. This is an inital testing phase, we are testing two machines per site. On all other sites we have not had this issue, only with the two machines on this site. The AV on the machines is the same as across the other sites and configured the same, trend micro.
The file is on a hard drive and is being run from there and as I have said I have copied over a know working file a number of times, all with the same issue.
Its about half way through extracting when the error pops up.
There appear to be no hardware issues with either machine. I am stumped.

 

[bcastner]

The service pack is self-verifying as to its integrity using MD5.

Other than a dirty disk, you might consider the possibility that this indicates an issue with workstation RAM. That certainly is the case for XP installation errors that are similar in kind and nature:

When you install Windows, you may receive a message during text-mode Setup that states that a file cannot be copied because it is damaged or missing. If you attempt to skip the file, you may receive the same message for random files that Setup tries to copy to your hard disk. Retrying a file may or may not work, but the process continues to stop on subsequent files.


This behavior can occur because of any of the following reasons:

• The Windows CD-ROM is damaged or dirty.
• PC133 SDRAM is being used in a computer that requires PC100 SDRAM.
• The CD-ROM drive is malfunctioning.
• The RAM is mismatched or the memory is faulty.

Source:

http://support.microsoft.com/?kbid=257954

____________________________
Users Helping Users

 

[linney]

Maybe you can get around the problem by Slipstreaming the SevricePack?

Slipstream Service Packs
thread779-900263

Where are the files being extracted to? Is it the same Temp folder location as the successful extractions?

Have you tried disabling your AV (and other security type programs), even though that wasn't necessary at other locations? Do these machines have any Bios Scanning running?

 

[kippy13]

Slipstreaming isnt an option I am afraid, nor is disabling the AV.
As far as I am aware it is getting extracted to the same temp folder.
I'll just have to try a few more things and have a look deeper into it.
Kippy

***************************************
Looking for the best answers:
faq222-2244
Keeping your system clear of malware:
faq608-4650
***********************************
Dont forget to post back with the eventual resolution.
***************************************

 

[linney]

Will it install from the Windows Update site, or however you take your updates?

See if the install has proceeded far enough to create any logs. The Setup program logs information about the Windows XP SP2 installation to the following log files:
• Setupapi.log
• Svcpack.log
• Spuninst.log
The log files are located in the %Windir% folder. For example, if Windows XP is installed to the C:\Windows folder, the log files are located in the C:\Windows folder.