InDesign CS4: Exit code 7
Hi,
I would appreciate some help repackaging Adobe InDesign CS4.
I have made the following bat file to install Adobe InDesign CS4:
When i logon at a client with an admin account and run this bat file everything works as intended.
As we deploy our software by GPO, i put this bat file inside an msi end tested it manually. The setup fails within 1 minute and returns exit code 7.
I searched this forum, and came across a post with the same error
(http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning7235&mpage=1&key=뢃). My experience with repackaging is limited, so i was wondering if the method mentioned in the reply from VBScab at the end of that particular post can be used to create a new msi or is there an easier way to make this work?
I would appreciate some help repackaging Adobe InDesign CS4.
I have made the following bat file to install Adobe InDesign CS4:
"\\server\share$\XPPackages\AdobeIndesignCS4\Adobe CS4\Setup.exe" --mode=Silent --deploymentFile="\\server\share$\XPPackages\AdobeIndesignCS4\install.xml"
if exist "C:\Documents and Settings\%username%\Menu Start\Programma's\Adobe" goto exists
mkdir "C:\Documents and Settings\%username%\Menu Start\Programma's\Adobe"
:exists
move "C:\Documents and Settings\%username%\Menu Start\Programma's\Adobe*CS4.*" "C:\Documents and Settings\All Users\Menu Start\Programma's\Adobe"
reg import "\\server\share$\XPPackages\AdobeIndesignCS4\DisableProductImprovement.reg"
exit
When i logon at a client with an admin account and run this bat file everything works as intended.
As we deploy our software by GPO, i put this bat file inside an msi end tested it manually. The setup fails within 1 minute and returns exit code 7.
Installer Operation: UninstallBootstrapperOperation
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
UninstallBootstrapperOperation: Changed working directory to C:\
Uninstalling bootstrapper
[ 4068] Tue Apr 06 09:27:30 2010 INFO
Checking bootstrapper progress
[ 4068] Tue Apr 06 09:27:30 2010 FATAL
Exception: JavaScript Support file could not be loaded: ReferenceError: systemCheck_wp is undefined
Exit code: 7
[ 4068] Tue Apr 06 09:27:30 2010 INFO
-----------------------------------------------------------------
------------------ END Silent Installer Session -----------------
-----------------------------------------------------------------
I searched this forum, and came across a post with the same error
(http://itninja.com/question/gnu,-freeware-and-shareware-programs-to-cloning7235&mpage=1&key=뢃). My experience with repackaging is limited, so i was wondering if the method mentioned in the reply from VBScab at the end of that particular post can be used to create a new msi or is there an easier way to make this work?
0 Comments
[ + ] Show comments
Answers (13)
Please log in to answer
Posted by:
pjgeutjens
14 years ago
Ahh, Adobe CS4 packages and error code 7 ... the memories (well nightmares, but hey)
In Adobe-Land, exit code 7 means "unable to complete silent workflow" (and not Windows' THE STORAGE CONTROL BLOCKS WERE DESTROYED - talk about scary error messages [:D])
what we had happen was the LocalSystem account used for distributions did not have access to the network share that contained the installation sources. As a test you could try giving Domain Computers Read/Execute access to \\server\share$\XPPackages\AdobeIndesignCS4\Adobe CS4. You can also "manually" map the network location in your VBS, this will make it so LocalSystem can access it. Another thing to try is copying the setup.exe files to the local disk before starting the installation.
P.S this goes for my personal experience with Adobe Photoshop and Creative Suite CS4, but after using the Adobe Deployment Toolkit, I had something called AdobeUberInstaller.exe, with a matching XML-file that was used to kick off installs. Ring any bells for you?
PJ
In Adobe-Land, exit code 7 means "unable to complete silent workflow" (and not Windows' THE STORAGE CONTROL BLOCKS WERE DESTROYED - talk about scary error messages [:D])
what we had happen was the LocalSystem account used for distributions did not have access to the network share that contained the installation sources. As a test you could try giving Domain Computers Read/Execute access to \\server\share$\XPPackages\AdobeIndesignCS4\Adobe CS4. You can also "manually" map the network location in your VBS, this will make it so LocalSystem can access it. Another thing to try is copying the setup.exe files to the local disk before starting the installation.
P.S this goes for my personal experience with Adobe Photoshop and Creative Suite CS4, but after using the Adobe Deployment Toolkit, I had something called AdobeUberInstaller.exe, with a matching XML-file that was used to kick off installs. Ring any bells for you?
PJ
Posted by:
anonymous_9363
14 years ago
Didn't I read here on AD that Adobe specifically counsel against deploying from a network share, saying that they recommend copying locally and running the install from there?
Posted by:
ekniranjan
14 years ago
Hi TalkingMarble,
Have you checked this
http://www.adobe.com/aboutadobe/openoptions/pdfs/manualenterprisedeployment_cs4_help.pdf
Nice document for Adobe CS4.
Have you checked this
http://www.adobe.com/aboutadobe/openoptions/pdfs/manualenterprisedeployment_cs4_help.pdf
Nice document for Adobe CS4.
Posted by:
TalkingMarble
14 years ago
I put the install files (including the bat/msi file) on a local drive and made the necessary adjustments inside the bat file and the msi wrapper. I also created two new xml files so everything points to the local setup files. After that i manually executed the msi wrapper but the setup still fails with exit code 7.
I already gave the method described in the deployment toolkit a try. When i use AdobeUberInstaller.exe inside the bat file and manually execute the bat file as admin, then indesign installs without any errors. But when i wrap this bat file inside an msi and manually execute this msi then i also get exit code 7.
So it makes no difference if i use the deployment toolkit or using the --record=1 method.
I already gave the method described in the deployment toolkit a try. When i use AdobeUberInstaller.exe inside the bat file and manually execute the bat file as admin, then indesign installs without any errors. But when i wrap this bat file inside an msi and manually execute this msi then i also get exit code 7.
So it makes no difference if i use the deployment toolkit or using the --record=1 method.
Posted by:
ekniranjan
14 years ago
How abt this, i tried to insert the .bat file in MSI, but i got some issues. So why don't you create a wise script of VBS and insert that one in MSI.
I just inserted the wise script in my MSI, (.WSP compiled to .EXE & inserted in MSI).
This is just a suggestion & trial to help you.
I just inserted the wise script in my MSI, (.WSP compiled to .EXE & inserted in MSI).
This is just a suggestion & trial to help you.
Posted by:
TalkingMarble
14 years ago
I did checked out the manual enterprise deployment document, but essentially its the same as the deployment toolkit. The advantage from the deployment toolkit is that you don't have to worry about the location from some files.
Which tools inside WPS 6.0 do i use to make a wise script of VBS? I have no knowledge making wise scripts, but i'm willing to give it a try.
Which tools inside WPS 6.0 do i use to make a wise script of VBS? I have no knowledge making wise scripts, but i'm willing to give it a try.
Posted by:
anonymous_9363
14 years ago
why don't you create a wise script of VBS and insert that one in MSI.What difference would that make? The underlying logic will still be the same. Just because it's an EXE doesn't bestow magical powers upon it.
A colleague at my last client did InDesign CS4 and as far as I can remember, we used the Adobe MSIs with appropriate MSTs: we didn't need wrappers, scripts or any other nonsense.
Posted by:
TalkingMarble
14 years ago
Correct me when i'm wrong,but that would mean that i get a gpo with 38 msi/mst entries as the install logfile show that about 38 msi are installed.
Posted by:
ekniranjan
14 years ago
Hi TalkingMarble,
Is your problem solved ? if you have any more question, please post ?
Is your problem solved ? if you have any more question, please post ?
Posted by:
TalkingMarble
14 years ago
appropriate MSTs
What do you mean by appropriate MST? MSTs delivered by Adobe or MSTs made of the properties used in the temporary files?
Posted by:
anonymous_9363
14 years ago
I mean response transforms for each of the MSIs. If Adobe provide MSTs, they're probably for different languages. Take a look at them, comparing them to their base MSI. Whether or not you need them depends on how they transform the MSI.
Posted by:
lady.d
14 years ago
this may or may not be helpful. i had problems with PhotoExt. and WebPrem CS4. The original XP package used the install.xml from the outcome of --record=1 method. When I was repackaging to take them to Win7 i was using the original .xml, but kept getting kept getting Exit Code 7. I then used the Deployment Toolkit to produce the UberInstall/Uninstall and they now work perfect for Win7. There was a problem with original .xml not being able to determine if x64 Photoshop files were needed. The Uber xml added a lot more info.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.