Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Patch Creation Wizard - Error 1328 on installation

Updated: 21 May 2010 | 1 comment
Shaun Wilkinson's picture
0 0 Votes
Login to vote

Hey Guys,

RE: Wise Installation Studio

Im definitely pulling my hair out on this one guys !

I have used the Patch Creation Wizard to generate a .MSP file patch for an installation.
It just contains an update to 1 file.

In some instances we are experiencing an error 1328 on installation...

Error 1328... applying patch to file C:\Config.Msi\PT18.tmp.
It has probably been updated by other means, and can no longer be modified by this patch.

I can confirm the file has not been updated by other mean but just does not load.
Through reading web posts they suggest..

The file is damaged (corrupted).----- (It is still working fine in application)
The file was updated with a more recent update. (Not the case)
There are incorrect permissions on the file. (Logged in as admin)
The file is in use by another program. (Tried on a stand alone machine and checked all processes)

I built the path in no different way to that I have built any other .msp file that works correctly.

Has anyone experienced this that can tell me whats stopping the file from updating ?

Any help would be greatly appreciated

regards
Shaun

Discussion Filed Under:

Comments

EdT's picture
24
Jun
2009
0 Votes 0
Login to vote

Don't assume anything

1. Being logged in as admin does not guarantee you have permissions to alter files. If admin permissions have been revoked on a file, leaving only system permissions, then you won't be able to do anything to update the file.
Simplest test is to grab a copy of the updated file and try and copy it over the existing file while logged in as admin. If you cannot do it, then you at least know where to look for the issue. 

2. Being on a standalone machine as opposed to a networked machine may not make any difference to whether the file is locked, if it happens to be started as a service or by some other startup process during boot.

3. Perform an MD5 checksum on your original version of this file, and compare it with the checksum of the file on the test system you are trying to update.  Out of interest, was the original file an exe that was installed over the internet?

4. Check your antivirus and antispyware solution to make sure it is not blocking the update to your presumed executable - as this can be mistaken as virus activity.

5. If posting again, let us know more details of the type of file you are updating, and the target operating system. If it is Vista, let us know if the same issue persists when you turn off UAC.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.