- This topic has 43 replies, 11 voices, and was last updated 14 years, 2 months ago by
kimerajamm.
-
AuthorPosts
-
June 3, 2010 at 6:24 pm #378691
dead2sin
ParticipantSorry, I forgot to post that.
The build machine is running 10.6.3 and InstaDMG 1.6b2 with instaup2date and I am building 10.6.3 images as well.
I’ll try dumping it in a .dmg and see what happens 🙂 Thanks for the help. (Greg is the man btw!)
Nate
June 3, 2010 at 6:35 pm #378692vogtstev
ParticipantI posted my specs before:
I am using 10.6.3 of my build machine.
My out images and I am installing 10.6, then running the 10.6.3 Combo
I am running 1.6b2 of InstaDMG
.4b of InstaUp2DateI am trying the dmg and setting the adobe install path back to $2.
Thanks!
June 3, 2010 at 7:02 pm #378693vogtstev
ParticipantShucks. Failed again.
This time it was off the dmg and adobe scripts unaltered (remained $3 in preflight)
However, I got slightly different error messages in the log:./preinstall: Error : Unable to complete Silent workflow
./preinstall: Exit Code: 7
./preinstall: AAMEE Installer : Exit code of AdobeDeploymentManager is (127)
./preinstall: AAMEE Installer : Exit …
PackageKit: Install Failed: PKG: pre-install scripts for “com.adobe.Enterprise.install.E420041C-1497-41F2-BB5B-1DE9A7007470”
Error Domain=PKInstallErrorDomain Code=112 UserInfo=0x100510a90 “An error occurred while running scripts from the package “photoshopcs5_Install.pkg”.” {
NSFilePath = “./preinstall”;
NSLocalizedDescription = “An error occurred while running scripts from the package U201cphotoshopcs5_Install.pkgU201d.”;
NSURL = “file://localhost/private/tmp/InstaDMG_temp_folder.miV7p4/mount_point.lHuYa0/photoshopcs5_Install.pkg”;
PKInstallPackageIdentifier = “com.adobe.Enterprise.install.E420041C-1497-41F2-BB5B-1DE9A7007470”;June 3, 2010 at 7:12 pm #378694dead2sin
Participant[QUOTE][u]Quote by: vogtstev[/u][p]Shucks. Failed again.
This time it was off the dmg and adobe scripts unaltered (remained $3 in preflight)
However, I got slightly different error messages in the log:./preinstall: Error : Unable to complete Silent workflow
./preinstall: Exit Code: 7
./preinstall: AAMEE Installer : Exit code of AdobeDeploymentManager is (127)
./preinstall: AAMEE Installer : Exit …
PackageKit: Install Failed: PKG: pre-install scripts for “com.adobe.Enterprise.install.E420041C-1497-41F2-BB5B-1DE9A7007470”
Error Domain=PKInstallErrorDomain Code=112 UserInfo=0x100510a90 “An error occurred while running scripts from the package “photoshopcs5_Install.pkg”.” {
NSFilePath = “./preinstall”;
NSLocalizedDescription = “An error occurred while running scripts from the package U201cphotoshopcs5_Install.pkgU201d.”;
NSURL = “file://localhost/private/tmp/InstaDMG_temp_folder.miV7p4/mount_point.lHuYa0/photoshopcs5_Install.pkg”;
PKInstallPackageIdentifier = “com.adobe.Enterprise.install.E420041C-1497-41F2-BB5B-1DE9A7007470”; [/p][/QUOTE]I got the same error message 🙁 Hrmmm, guess its time to poke around some more.
June 3, 2010 at 7:32 pm #378695dead2sin
ParticipantIn the AAMEE itself, you can specify a custom install location, I wonder if we could somehow use that to tweak it a tiny bit to get it to play nicely with InstaDMG. By default, according to the documentation, it looks to install it on the boot volume, whatever that may be, unless you specify another location.
June 4, 2010 at 12:01 pm #378696vogtstev
ParticipantI was wondering about the Custom Install Location as well.
Just for kicks this AM, I tried the pkg in SIU and it failed there too.June 4, 2010 at 12:07 pm #378697vogtstev
ParticipantDo you think as a test that I could set one of the InstaDMG options to specifically to a certain scratch folder or output folder, then point Adobe to that same folder? Or create a specific named volume I could point the Adobe installer too? If so, what options might I change? I noticed -t, -o, n might be some possibilities? Any ideas?
Thanks,
SteveJune 4, 2010 at 1:10 pm #378698ttpedersen
ParticipantI haven’t had time to test AAMEE but regarding the problems discussed above, could they be related to the statement at [url]http://blogs.adobe.com/OOBE/2010/06/adobe_application_manager_ente.html[/url]: “When deploying through ARD a user is currently required to be logged in on the target system.” This is why AAMEE is still listed as a “preview” I guess.
I would think that this requirement will break the InstaDMG workflow, wouldn’t you think so?
June 4, 2010 at 10:30 pm #378699dead2sin
Participant[QUOTE][u]Quote by: ttpedersen[/u][p]I haven’t had time to test AAMEE but regarding the problems discussed above, could they be related to the statement at [url]http://blogs.adobe.com/OOBE/2010/06/adobe_application_manager_ente.html[/url]: “When deploying through ARD a user is currently required to be logged in on the target system.” This is why AAMEE is still listed as a “preview” I guess.
I would think that this requirement will break the InstaDMG workflow, wouldn’t you think so?[/p][/QUOTE]
This was my thought too, but it seems that the error message being thrown on the InstaDMG workflow is different from the one thrown when you install it over ARD without anyone logged in. Also, when InstaDMG is running, someone is technically logged in, but I’m not sure how the AAMEE installer determines that.
I’m super busy getting a new image ready with CS5 on it (Repacking it with Composer for now…). As soon as I get done setting up a new server and getting this image buttoned up, I’ll help you guys poke around the CS5 installer some more 🙂
I like vogtstev’s idea about manually specifying the target file. If we can manually specify a target and set a hard link to that in the preflight, maybe we’ll progress to the next set of errors that the installer throws 😆
June 11, 2010 at 12:11 pm #378731sumita
ParticipantHey Steve and dead2sin,
Please do not change the preinstall script. “installDirPath” is the path, where user want to installs CS5 product/ suite. I am not sure for InstallDmg, but with ARD, it is root ‘/’, unless user manually change “IFPkgFlagDefaultLocation” key in info.plist of the package. In former case (that is default case, when installDirPath =’/’), location specified in ‘deploy to’ field at Config options screen of Adobe Application Manager would be used.
However, if user enters “IFPkgFlagDefaultLocation” (it should be absolute location) in info.plist of pkg, installation would take place at that location.
From the echo statements, it seems that installDirPath is some mount location and installation to that location is not successful.June 13, 2010 at 9:29 pm #378746sgstuart
ParticipantHi All,
I am sorry that I am getting late to this topic and installation. However, I am having the same problem’s as stated. I also noticed in Console logs that it is on the machine that is creating the image there is a Adobe CS5(spelled out though), Here are the logs that I am seeing from there. Above the ones there, there are many similar messages that go on for quite some time, and I do not know if they are relevant.——-
Value returned on lookup of payload: {44EAE408-3960-11DF-ACCC-D8A62C404F28} Adobe InDesign CS5 Common Language Files_AdobeInDesign7CommonLang-en_GB is: false
Action string for {44EAE408-3960-11DF-ACCC-D8A62C404F28} Adobe InDesign CS5 Common Language Files_AdobeInDesign7CommonLang-en_GB is none
Payload {44EAE408-3960-11DF-ACCC-D8A62C404F28} Adobe InDesign CS5 Common Language Files_AdobeInDesign7CommonLang-en_GB is extension payload. Aligning its action according to parent.
Value returned on lookup of payload: {68489BE8-3960-11DF-8F88-C4A72C404F28} Adobe InDesign CS5 Common Language Files_AdobeInDesign7CommonLang-en_US is: false
Action string for {68489BE8-3960-11DF-8F88-C4A72C404F28} Adobe InDesign CS5 Common Language Files_AdobeInDesign7CommonLang-en_US is none
Payload {68489BE8-3960-11DF-8F88-C4A72C404F28} Adobe InDesign CS5 Common Language Files_AdobeInDesign7CommonLang-en_US is extension payload. Aligning its action according to parent.
Value returned on lookup of payload: {8D3FB5B0-395D-11DF-AEA7-642B2C404F28} Adobe InDesign CS5 Application Language Files_AdobeInDesign7AppLang-en_US is: false
Action string for {8D3FB5B0-395D-11DF-AEA7-642B2C404F28} Adobe InDesign CS5 Application Language Files_AdobeInDesign7AppLang-en_US is none
Payload {8D3FB5B0-395D-11DF-AEA7-642B2C404F28} Adobe InDesign CS5 Application Language Files_AdobeInDesign7AppLang-en_US is extension payload. Aligning its action according to parent.
END Setting requested payload actions
Collected advanced path check information for INSTALLDIR
INSTALLDIR is a well-formed path
[ 0] Sat Jun 12 22:21:10 2010 FATAL
INSTALLDIR cannot be the root path
[ 0] Sat Jun 12 22:21:10 2010 INFO
:: END TIMER :: [Total Timer] took 2265 miliseconds (2.265 seconds) DTR = 8875.94 KBPS (8.66791 MBPS)
————————————– Summary ————————————–
– 1 fatal error(s), 9 error(s), 0 warning(s)
ERROR: Payload path does not exist and no media record specified.
ERROR: Payload path does not exist and no media record specified.
ERROR: Payload path does not exist and no media record specified.
ERROR: Payload path does not exist and no media record specified.
ERROR: Payload path does not exist and no media record specified.
ERROR: Payload path does not exist and no media record specified.
ERROR: Payload path does not exist and no media record specified.
ERROR: Payload path does not exist and no media record specified.
ERROR: Payload path does not exist and no media record specified.
FATAL ERROR: INSTALLDIR cannot be the root pathSearch the same string above to find when the error occured.
————————————————————————————-
Exit Code: 22 – INSTALLDIR check failed
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
END – Installer Session
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*Notice how it says INSTALLDIR cannot be root path, and the previous persons message, saying that it is installing on root. I have a sneaking suspicion this is the problem, or at least part of it.
By the way, has anyone solved it yet? If so can the solution be posted, I am going to try until then though.
Thanks,
Steven StuartJune 14, 2010 at 7:45 am #378747sumita
ParticipantHi Steven,
Sorry for the misunderstanding. Adobe CS5 product/ suites can Not be installed on root folder.
What I meant was that, when CS5 pkg is created using Adobe Application Manager Enterprise Edition (AAMEE) and deployed via ARD, installDirPath value turns out to be ‘/’, which is handled in AAMEE deployment logic and converted to default installation location specified in product/ suite(generally /Applications) and deployment takes place there.
I believe, you haven’t used pkg created via AAMEE for installation. Please feel free to post any further queries.June 14, 2010 at 2:50 pm #378750vogtstev
ParticipantHi sumita.
Thanks for you reply. Just to give a little more detail to my post as well to help you understand. I am not deploying this package via ARD. I am putting it in the build train for InstaDMG. I have for sure made new packages with AAMEE and I am not using the original packages. I could maybe put a different destination in AAMEE when building the package, but at this point have just used the default. Have you tried this in InstaDMG and had it work?
Thank you very much.
June 14, 2010 at 4:41 pm #378752sgstuart
ParticipantHi Sumita,
I have been using the AAMEE, and creating a new package (.PKG) for both Design Standard, and Production Premium. Design Standard is much smaller, so that has been the one I have currently been using.Hi Allister,
I am using rev 300, on a 10.6.3.Hi all,
I did try changing the default location to /Applications editing the info.plist file, directly. However, even though it did install (theoretically), when the image was done, it was not there, it had 10 errors and 234 warnings in the CS5 logs. I set the installer to abort on errors, so maybe that is what was/is happening. I also found quite a few things installing on the host machine (the machine that is creating the InstaDMG image) they are Adobe Help, Adobe Media Player, Adobe Media Encoder CS5, and under Utilities, there is a folder called Adobe Installers, with a symlink(short cut) to Adobe Creative Suite 5 Design Standard, which links to the uninstaller, under /Library/Application Support/Adobe/(Uninstall/long set of numbers here).
So it is definitely not fully going to the image for some reason.
I am also testing now, using ARD. I am finding that if the machine is on, but not logged in (so at a login prompt) the install fails, however if you log in (I am logging in as the local admin) it appears to install fine(It installed successfully, no errors on ARD).
My guess is this is why it does not install on InstaDMG, because to my knowledge InstaDMG is not installing as a user (that is why it does not create user garbage) , “root” assuming that is how InstaDMG is installing, is not a true user.
Thanks,
Steven StuartJune 15, 2010 at 6:06 am #378753chandan
ParticipantHi All,
Please go through [url=http://www.adobe.com/devnet/creativesuite/pdfs/DeployGuide_CS5.pdf]CS5 Enterprise Deployment Guide[/url] and [url=http://www.adobe.com/devnet/creativesuite/pdfs/AdobeApplicationManagerEnterpriseEditionReadme.pdf]Adobe Application Manager Enterprise Edition ReadeMe[/url] documents before using [url=http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html]Adobe Application Manager Enterprise Edition[/url].
Thanks,
Chandan -
AuthorPosts
- You must be logged in to reply to this topic.
Comments are closed