.NET Framework 2.0, Security Updates, Error applying transforms
Hello forum!
Microsoft has released security patches for .NET Framework 2.0;
- KB922770 (http://go.microsoft.com/fwlink/?LinkId=70202)
- KB917283 (http://go.microsoft.com/fwlink/?LinkId=67181)
I want to update the clients with these security patches via Microsoft WSUS.
Attempting to install the update locally (this happens with both updates, but I will only paste the errors for one), it generates a popup message;
"Error applying transforms. Verify that the specified transform paths are valid."
It generates the following error in the system Application log;
In the logfile "NDP20-KB917283-X86-msi.0.log" it has the following entries;
I searched for the "96d7.mst" file on the local computer but did not return any results.
The bad part about troubleshooting this is that I did not create the repackage/deployment of the .NET Framework 2.0 -- so the transform it is looking for, I have no knowledge of.
I am thinking I may have to start from scratch to apply the updates then redeploy .NET Framework 2.0 ?
How does everyone else deal with security updates that are published after a deployment of .NET Framework?
Any ideas or suggestions?
Microsoft has released security patches for .NET Framework 2.0;
- KB922770 (http://go.microsoft.com/fwlink/?LinkId=70202)
- KB917283 (http://go.microsoft.com/fwlink/?LinkId=67181)
I want to update the clients with these security patches via Microsoft WSUS.
Attempting to install the update locally (this happens with both updates, but I will only paste the errors for one), it generates a popup message;
"Error applying transforms. Verify that the specified transform paths are valid."
It generates the following error in the system Application log;
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 1023
Date: 1/29/2007
Time: 1:07:27 PM
User: xx*domain*xx\xx*user*xx
Computer: XXXXX
Description:
Product: Microsoft .NET Framework 2.0 - Update 'Security Update for Microsoft .NET Framework 2.0 (KB917283)' could not be installed. Error code 1624. Additional information is available in the log file C:\DOCUME~1\xxxx\LOCALS~1\Temp\NDP20-KB917283-X86\NDP20-KB917283-X86-msi.0.log.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 37 31 33 31 36 34 36 {7131646
0008: 44 2d 43 44 33 43 2d 34 D-CD3C-4
0010: 30 46 34 2d 39 37 42 39 0F4-97B9
0018: 2d 43 44 39 45 34 45 36 -CD9E4E6
0020: 32 36 32 45 46 7d 20 7b 262EF} {
0028: 39 36 37 42 30 39 38 41 967B098A
0030: 2d 30 34 32 44 2d 34 33 -042D-43
0038: 36 37 2d 42 41 43 39 2d 67-BAC9-
0040: 38 42 43 31 31 36 38 34 8BC11684
0048: 31 37 34 46 7d 20 31 36 174F} 16
0050: 32 34 24
In the logfile "NDP20-KB917283-X86-msi.0.log" it has the following entries;
DEBUG: Error 2250: Database: Transform: Cannot add existing row. Table: Property
1: 2250 2: 3: Property
Error applying transforms. Verify that the specified transform paths are valid.
C:\WINDOWS\Installer\96d7.mst
I searched for the "96d7.mst" file on the local computer but did not return any results.
The bad part about troubleshooting this is that I did not create the repackage/deployment of the .NET Framework 2.0 -- so the transform it is looking for, I have no knowledge of.
I am thinking I may have to start from scratch to apply the updates then redeploy .NET Framework 2.0 ?
How does everyone else deal with security updates that are published after a deployment of .NET Framework?
Any ideas or suggestions?
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
gmorgan618
17 years ago
The mst error is occuring because the MST that was used to install contains a table (row) that doesn't exist in the patch being applied. That may not make sense but try this.. The transform is trying to change a value that doesn't exist...
Go to HKEY_CLASSES_ROOT\Installer\Products\D6461317C3DC4F04799BDCE9E42626FE
this should be 2.0 Framework - if it's not search the Products key for the .net 2.0 listing.
Delete the Value "Transforms"...
Just to be clear, in the registry a value is the whole entry - value data is what it's set to... so
Version is the value
0x0200c627 is the value data
So delete the transforms listing... rerun your patch.
Deleting this value will stop it from attempting to apply the transform...
In the future, you'll have to be a little more careful as to what changes you make to your packages...
Good luck
Go to HKEY_CLASSES_ROOT\Installer\Products\D6461317C3DC4F04799BDCE9E42626FE
this should be 2.0 Framework - if it's not search the Products key for the .net 2.0 listing.
Delete the Value "Transforms"...
Just to be clear, in the registry a value is the whole entry - value data is what it's set to... so
Version is the value
0x0200c627 is the value data
So delete the transforms listing... rerun your patch.
Deleting this value will stop it from attempting to apply the transform...
In the future, you'll have to be a little more careful as to what changes you make to your packages...
Good luck
Posted by:
JdotQ
17 years ago
gmorgan,
Thank you very much for the fast reply. Following your steps resolved my issue!
HKEY_CLASSES_ROOT\Installer\Products\D6461317C3DC4F04799BDCE9E42626FE was the correct path for Framework 2.0
The registry value was set to;
Transforms = @netfx.mst
I deleted the entire key and the install went through flawless [:)]
And unfortunately, I am following in the footsteps of a previous packager that packaged this .NET Framework deployment -- so it was a shot in the dark to troubleshoot the issue.
Thanks again for your help and reply.
Best regards.
Thank you very much for the fast reply. Following your steps resolved my issue!
HKEY_CLASSES_ROOT\Installer\Products\D6461317C3DC4F04799BDCE9E42626FE was the correct path for Framework 2.0
The registry value was set to;
Transforms = @netfx.mst
I deleted the entire key and the install went through flawless [:)]
And unfortunately, I am following in the footsteps of a previous packager that packaged this .NET Framework deployment -- so it was a shot in the dark to troubleshoot the issue.
Thanks again for your help and reply.
Best regards.
Posted by:
JdotQ
17 years ago
I also wanted to post and find out your recommended way of incorporating updates to .NET Framework -- such as the two security updates I posted previously in this thread.
Do you recommend to use a method such as WSUS to deploy to clients, or to incorporate the security updates in the packages and redeploy them?
Thanks again.
Do you recommend to use a method such as WSUS to deploy to clients, or to incorporate the security updates in the packages and redeploy them?
Thanks again.
Posted by:
gmorgan618
17 years ago
How are you deploying .NET Framework ? GPO or some deployment tool?
My personal opinion, is to use admin install points and then just update the AIP with the updates. this would be done with msiexec /a <Path to MSI of AIP> /p <Path to patch> /qb
Then have the install (update) call - netfx.msi REINSTALL=ALL REINSTALLMODE=OMUS /qb
This will install the patches over an existing installation.
--------------------
Anyway, I'm glad the transform fixed helped...
My personal opinion, is to use admin install points and then just update the AIP with the updates. this would be done with msiexec /a <Path to MSI of AIP> /p <Path to patch> /qb
Then have the install (update) call - netfx.msi REINSTALL=ALL REINSTALLMODE=OMUS /qb
This will install the patches over an existing installation.
--------------------
Anyway, I'm glad the transform fixed helped...
Posted by:
JdotQ
17 years ago
.NET Framework is being deployed via GPO.
I like the idea of the admin install points. That is the approach I am taking for deploying the latest version of Adobe Reader (v8.0)
It appears that the .NET Framework may have been setup as a AIP. Any way I can affirmatively tell that? It's a directory on a server with approximately 59 files -- a mix of .dll's, .ini, .exe. txt, msi
So if it is already setup as an AIP, I could just run the Microsoft security patches against the install to update the AIP.
After updating the AIP, does anything else have to be done on the clients, so they get the most recent/updated version of the software? Will it be the same process for other apps like Adobe Reader (ex. install 8.0 now, when 8.0.1 comes out what needs to be done to the clients?)
Thanks again for all the help
I like the idea of the admin install points. That is the approach I am taking for deploying the latest version of Adobe Reader (v8.0)
It appears that the .NET Framework may have been setup as a AIP. Any way I can affirmatively tell that? It's a directory on a server with approximately 59 files -- a mix of .dll's, .ini, .exe. txt, msi
So if it is already setup as an AIP, I could just run the Microsoft security patches against the install to update the AIP.
After updating the AIP, does anything else have to be done on the clients, so they get the most recent/updated version of the software? Will it be the same process for other apps like Adobe Reader (ex. install 8.0 now, when 8.0.1 comes out what needs to be done to the clients?)
Thanks again for all the help
Posted by:
gmorgan618
17 years ago
You may have to run something to remove the transforms entry - I don't remember if Startup scripts run before Application installation - but you could use this as your method of removing that key.
In GPO you'll just have to say Reinstall application once the AIP is updated -- sorry it's been so long since i've used ADGPO i don't remember the exact wording...
In GPO you'll just have to say Reinstall application once the AIP is updated -- sorry it's been so long since i've used ADGPO i don't remember the exact wording...
Posted by:
JdotQ
17 years ago
Posted by:
oneill3
16 years ago
ORIGINAL: gmorgan618
The mst error is occuring because the MST that was used to install contains a table (row) that doesn't exist in the patch being applied. That may not make sense but try this.. The transform is trying to change a value that doesn't exist...
Go to HKEY_CLASSES_ROOT\Installer\Products\D6461317C3DC4F04799BDCE9E42626FE
this should be 2.0 Framework - if it's not search the Products key for the .net 2.0 listing.
Delete the Value "Transforms"...
Just to be clear, in the registry a value is the whole entry - value data is what it's set to... so
Version is the value
0x0200c627 is the value data
So delete the transforms listing... rerun your patch.
Deleting this value will stop it from attempting to apply the transform...
In the future, you'll have to be a little more careful as to what changes you make to your packages...
Good luck
gmorgan,
This solution also fixed a problem I was having with Adobe Reader, however, how do you tell which table row it is trying to update?
thanks
Garry
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.