[THIN] Re: PS4 hotfix installer error

  • From: "Joe Shonk" <joe.shonk@xxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Fri, 28 Oct 2005 13:08:38 -0700

Why not ditch the .mst?  It's not required for a scripted install as you can
add all of the switches to the msiexec.exe line.   Wrap it up in a .cmd file
and it's easier to modify than an .mst file.

 

Joe

 

  _____  

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Jeff Pitsch
Sent: Wednesday, September 28, 2005 1:02 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: PS4 hotfix installer error

 

Yea, I figured out it was only one.  I got confused becaues the person who
was here before me named all the mst's the same.  Now I just need to script
the removal of that data for our install and I'm golden.

 

Thank you again,

 

Jeff

 

On 9/28/05, BRUTON, Malcolm, FM <Malcolm.BRUTON@xxxxxxxx> wrote: 

Just to explain what we do as it will help explain why we get this error.

 

Basically we have an automated build using altiris that installs using an
mst transform for MetaFrame XP.  It automatically puts it in the right farm
and zone etc.  We run a chfarm to move it a test farm which we toy with.  We
then test patch upgrades and whatever.  We were testing a few features of
PS3 and PS4 and were getting this error when trying to apply the latest PS4
rollup. 

 

I suspect the reason for this is the transform that it's trying to use no
longer has any correlation with it's current configuration.  e.g. the farm
name of the server etc is completely different to what's in the transform. 

 

removing
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\E7D590508AB4F5047A15C
5C581FB0554\Transforms=xxxxxxxxxxx

 

fixed this for us.  We just did a search for the name of the transform in
the register and this was the only place it lived.  We guessed it was the
transform from the logging as that was the last entry in the msiexec log
file that we generated when trying to install the patch. 

 

Hope this explains it

 

Malcolm

 

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Jeff Pitsch
Sent: 27 September 2005 17:33
To: thin@xxxxxxxxxxxxx

Subject: [THIN] Re: PS4 hotfix installer error




BRILLIANT!!!!!

 

that's exactly what it was.  I'm curious though, what reg entry did you
remove?  I removed everything I found but I'm curious if it's one particular
entry.

 

You have my undying gratitude!

 

Jeff

 

On 9/27/05, BRUTON, Malcolm, FM <Malcolm.BRUTON@xxxxxxxx
<mailto:Malcolm.BRUTON@xxxxxxxx> > wrote: 

Turn on full logging with msiexec when you install.  Look for any error in
the log file.  We found MetaFrame looking for a Transform file when
installing.  Removing the transform location form the registry fixed a very
similar issue for us trying to patch PS4. 

 

Malcolm

 

PS our error was slightly different than yours...

 

Event Type: Information
Event Source: Application Popup
Event Category: No
Event ID: 26
Date:  26/09/2005
Time:  09:04:35
User:  N/A
Computer: ######### 
Description:
Application popup: msiexec.exe - Application Error : The instruction at
"0x74734bb7" referenced memory at "0x00000000". The memory could not be
"read".

 

Click on OK to terminate the program

 

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Jeff Pitsch
Sent: 26 September 2005 20:12 
To: thin@xxxxxxxxxxxxx
Subject: [THIN] PS4 hotfix installer error

I'm trying to install PS4 hotfix PSE400W2K3014.msp and when it tries, either
through IM or locally, it errors out on msiexec.  All other MSI's will
install but not this.  I've reinstalled installer (latest 3.1 v2).  the
error in the event log is this: 

 

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 1013
Date:  9/26/2005
Time:  3:05:41 PM
User:  UFPIAD\SA-Citrix
Computer: GRCITRIX01
Description:
Internal MSI error. Installer terminated prematurely. 

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp .

 

thanks ahead of time

Jeff



****************************************************************************
*******
The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered
Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
Authorised and regulated by the Financial Services Authority 

This e-mail message is confidential and for use by the 
addressee only. If the message is received by anyone other 
than the addressee, please return the message to the sender 
by replying to it and then delete the message from your 
computer. Internet e-mails are not necessarily secure. The 
Royal Bank of Scotland plc does not accept responsibility for 
changes made to this message after it was sent. 

Whilst all reasonable care has been taken to avoid the 
transmission of viruses, it is the responsibility of the recipient to 
ensure that the onward transmission, opening or use of this 
message and any attachments will not adversely affect its 
systems or data. No responsibility is accepted by The Royal 
Bank of Scotland plc in this regard and the recipient should carry 
out such virus and other checks as it considers appropriate. 
Visit our websites at: 
http://www.rbs.co.uk/CBFM 
http://www.rbsmarkets.com <http://www.rbsmarkets.com/>  
****************************************************************************
****

 



****************************************************************************
******* 
The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered
Office: 36 St Andrew Square, Edinburgh EH2 2YB. 
Authorised and regulated by the Financial Services Authority 

This e-mail message is confidential and for use by the 
addressee only. If the message is received by anyone other 
than the addressee, please return the message to the sender 
by replying to it and then delete the message from your 
computer. Internet e-mails are not necessarily secure. The 
Royal Bank of Scotland plc does not accept responsibility for 
changes made to this message after it was sent. 

Whilst all reasonable care has been taken to avoid the 
transmission of viruses, it is the responsibility of the recipient to 
ensure that the onward transmission, opening or use of this 
message and any attachments will not adversely affect its 
systems or data. No responsibility is accepted by The Royal 
Bank of Scotland plc in this regard and the recipient should carry 
out such virus and other checks as it considers appropriate. 
Visit our websites at: 
http://www.rbs.co.uk/CBFM 
http://www.rbsmarkets.com <http://www.rbsmarkets.com/>  
****************************************************************************
**** 



 

Other related posts: