[THIN] Re: Trouble Migrating 1.8 IMS applications to PS4 IM

  • From: "Rick Mack" <Rick.Mack@xxxxxxxxxxxxxx>
  • To: <thin@xxxxxxxxxxxxx>
  • Date: Sun, 25 Jun 2006 21:01:10 +1000

Hi Shane,
 
I migrated about 10-12 IMS 1.8 packages to 2003/XP IM and actually tested them 
by installing with IM (and running the apps) before knocking up the doco you're 
using. 
 
There are 2 useful ways of debugging the ADF install scripts. 
 
The first is to actually try running the script manually, eg c:\program 
files\citrix\installeraginst.exe" /install \\server\software 
folder\application\application.wfs. If it works it'll install the app. If it 
doen't it may just give you enough info to help.

The packager also comes with a script verifier, c:\program 
files\citrix\im\adfverfw.exe which can be used to check the script for any 
syntax errors.

Failing that, zip up and send me one of the applications where IM is failign 
and I'll debug it for you.

regards,

Rick

Ulrich Mack 
Volante Systems 


________________________________

From: thin-bounce@xxxxxxxxxxxxx on behalf of Shane A Broomhall (AUST)
Sent: Sat 24/06/2006 15:25
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Trouble Migrating 1.8 IMS applications to PS4 IM



HI All,
 
I am currently trying to work on migrating some windows nt4.0/metaframe 1.8
IMS scripts to work on Win2k3/PS4.
The company that I am working for cannot find the medis for most of the
applications in the 1.8 farm. In the scripts I have modified the following,
 
Deleted the value in ProductDirectory
 
Changed the value for require OS from nt4 to nt52
Require='"%OS%"="" | (%!Split(OSVER,v)%%!eval('"%OS%"="WinNT" & %v1%
=5 & %v2%=2')', This application is only Packaged to run on Windows Server
2003 with MetaFrame.
 
Added the _NT52 value in the operating system area.
_NT52=%!Split(SOVER,v)%%!eval('"%OS%"="WinNT" & %v1%=5 & %v2%
=2')%
 
Added the directory to install it onto, under global symbols
APPINSTALLDISK=Y:
 
Changed the entries in the .wfs script and the directory structure of the files
from WTSRV to windows
 
replaced %_NT4% with %_NT52%
 
replaced _WINNT4 with _WINNT52
 
removed any entries for !toshortpath
 
The application is fine being added to the IM section of the CMC and allows for
me to choose to install the pacages agains a development server I have. The
install fails.
 
Since this failing I have looked at also chainging the entry from
PackagerVersion=1.0.1.293 (Release) to version=2 under the main section and
the script is now identified as version 2 instead of version 1.
 
it is not showing up under the properties of the script when added to the CMC
which operating system it is intended for.
 
The entries under the event log of the failed server show the following.  They
are WIndows 2k3 sp1 with PS4, and rollup pack 1.
 

The description for Event ID ( 1000 ) in Source ( Gemini Installer ) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event: Failed to
install aidmods Application.
Application description file: ims20://localhost/218019/aidmods.wfs
 
 
Any thoughts or tips ???
 
Thanks in advance
 
Shane Broomhall
 
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************



#####################################################################################
This e-mail, including all attachments, may be confidential or privileged.  
Confidentiality or privilege is not waived or lost because this e-mail has been 
sent to you in error.  If you are not the intended recipient any use, 
disclosure or copying of this e-mail is prohibited.  If you have received it in 
error please notify the sender immediately by reply e-mail and destroy all 
copies of this e-mail and any attachments.  All liability for direct and 
indirect loss arising from this e-mail and any attachments is hereby disclaimed 
to the extent permitted by law.
#####################################################################################

Other related posts: