AAMEE error

I'm trying to create an installer for Illustrator CS that was downloaded from Adobe using AAMEE 2.1 on Windows 7 Enterprise X64. I've extracted the files from the Illustrator download, installed AAMEE 2.1, and attempted to create an installer pacakage. I keep getting the error "A valid installer could not be found". It's valid enough that running it manually installs Illustrator CS. What is going on?

Hi jrandom421,
Which version of Illstrator are you trying to install.
-Prabs

Similar Messages

Error - A valid installer could not be found, using AAMEE and CS6

I receive the error - A valid installer could not be found, when using AAMEE 3.0 to create a CS6 Trial Package in Windows 7. I'm following the procedure documented here - http://blogs.adobe.com/oobe/tag/cs6 Imaging CS6-Attack of the Clones. I've tried both pointing at the DVD and pointing to a local folder, after copying the DVD to a local folder and copying the \payloads folder from the second DVD. I know the DVD is valid because I did a manual installation. I'm pointing at the folder that contains the Set-up.exe file, plus I've tried pointing at every other folder as well, with no success. I have a 40 user license for CS6 Master Collection for a classroom on our campus. I need to create a image for this classroom, and was thrilled that a solution was being provided to accomodate this, but AAMEE does not work! I'm working in a Windows 7 environment.
On top of this frustration, my Adobe ID is not working, I've used "chat" support and phone support and I can still not log in. They claim it has been escalated. When I explained the AAMEE error to the phone support rep, he informed me that there was no technical support and my only option was to post the question on the forum...but you have to log in with your Adobe ID to post a question! Round and round it goes. So I had to create another ID under a different email, just to post my question. I'm getting the mystery "an error has occurred, please try again", when I try to log in with my work Adobe ID.
Help! Anyone?

RESOLVED - Thanks in part to the ALBERT-in-Vancouver and Tushar Bammi thread concerning a similar problem. I dissected the PDApp.log. I had copied the installation DVDs to a local folder per the Deployment Guide, when installing from the DVD initially failed. But, PDApp.log stated - EnterpriseNativeApplet Individual media disks on fixed volumes are not supported, please use CD/DVD or mounted ISO/DMG media. That clued me in to trying to create the MSI using the DVDs again. My fault - that the original attempts to create the MSI from the DVDs did not work, I didn't realize I needed to run AAMEE with elevated privileges. Note - the earlier attempts when I was running AAMEE with elevated privileges and pointing to the locally copied installation files, failed. Interesting. I'm confused as to why the Deployment Guide directed my to create a product-install folder...
I haven't tested the MSI file yet, but if I have additional problems I will start a new thread.
Thanks.

"Internal error occurred" when launching Acrobat Pro X (AAMEE 3.1.150.0)

AAMEE 3.1.105.0 generated packages run fine when pushed to Macs that do not have an existing previous version of CS.
However, if pushed to a Mac that has CS4 installed, CS6 installs but Acrobat Pro X will not launch ("Internal error occurred").
We are using the latest Adobe CS6 Design & Web Premium installer DMGs from licensing.adobe.com and we are following the standard workflow.
I know Adobe's position is "We don't recommend or support concurrent installs of Creative Suite" (I get that).
Since OS X lacks package management (ala Yum, RPM, etc.), the term "Uninstall" is vague, but we appreciate Adobe's "cleaner tool".
Unfortunately the "cleaner tool" is only marginally effective, it leaves a mess behind.
And...when "cleaner tool" is used to remove CS4, it whacks CS6.
Wait...it gets worse...when "cleaner tool" is used, we now can't push our CS6 package to the Mac...we get...<drumroll>..."Internal error occurred" when launching Acrobat Pro X.
Someone shoot me...please put me out of my misery.
Why can't deploying CS6 be as simple as...
http://www.toysrus.com/product/index.jsp?productId=3938350&CAWELAID=479925582
Don

OK, we resolved the issue. Apparently there was a ~/Library/ColorSync folder present, not owned by the logged in user, and the logged in user had no access. Given OS X's domain model, it looks like Acrobat Pro X looks at that folder when it launches, even though it doesn't need to, and it can't get into it, so it tosses up the error.
Removing the folder (since it's not needed) resolves the issue. If the folder was needed, we would change ownership and permissions so Acrobat Pro X could access it.
Problem solved.
Thanks,
Don

CS 5.5+AAMEE=No packaging errors but won't install

I'm packaging CS 5.5 Master Collection using AAMEE 2.1 on Mac OS X 10.7. It's a completely vanilla workflow; I just have AAMEE suck in MC, find any updates (it finds 3), and spit out a .pkg. No customizations whatsoever.
But the .pkg that AAMEE ouputs fails to install. It seems to run normally for a couple of minutes, then the time estimate starts climbing until it finally fails out about 15 minutes later. The error I'm able to discern is a "Script error". A few portions of CS 5.5 do get installed (the ones starting with "A") but nothing else.
What I've tried:
* Redownloading CS 5.5 MC from Adobe, in case I got a bad download,
* Repackaging using AAMEE on a completely different Mac,
* Installing on more than one Mac. I've tried it on three, on both OS X 10.6 and 10.7.
I was previously able to package CS 5.0 using AAMEE so I've gotten it to work before. Just not sure how to troubleshoot what's happening here.
Thanks!
-Kurt

Hi,
Sorry to hear that you are facing problems. Can you please send the PDApp.log file present at /user/Library/Logs. This will help us debug the issue.
Some tips -
A conflicting process may be running which is causing the install to fail.
Make sure you have administrative privileges while installing Adobe Products.
We can tell you the exact reason by looking at the Logs.
Regards,
Saransh Katariya | Adobe Systems | [email protected]

Adobe FrameMaker 12, serial number error on AAMEE 2.1

Hi,
I am trying to do silent install package from FrameMaker 12 with AAMEE 2.1 but it will give error about serial number.
AAMEE 3.1 does not work at all.
I have tested serial number by installing it manually and it works fine.
Any ideas?

I am also having this issue on a x64 bit machine.
I desperately need a fix.
I am not getting any information as to why this could be happening.
Thanks,
Toby

App-V 5 SP1 Creative Cloud Enterprise Illustrator 213:19 Error

Hello, I'm currently working on creating an App-V 5 sequence for Adobe Creative Cloud Enterprise. Firstly I'm trying to create a sequence for CC Illustrator, however I'm running into what appear to be licensing errors.
From what I understand in Adobe Create Cloud Enterprise, the licensing restrictions which tie the license to the machine have now been removed so that packages can be created with serial numbers included for deployment and imaging purposes.
I've created a package for Illustrator using the Creative Cloud Packager and included the serial number and then sequenced this in App-V 5.
When I deploy this app-v sequence, Illustrator loads but I end up with a 213:19 error. Looking in the amt3.log the full error is
09/24/13 16:58:35:478 | [ERROR] | | | | SLCoreService | | | 5624 | error deleting bad mkey:
09/24/13 16:58:35:478 | [ERROR] | | | | SLCoreService | | | 5624 | Could not load machine key
09/24/13 16:58:35:478 | [ERROR] | | | | SLCoreService | | | 5624 | License store synchronization took 14.6 ms and return "License Store Access Failure: Machine key cannot be deleted (213:19)".
09/24/13 16:58:35:539 | [INFO] | | | | ALM | | | 5624 | _time_: (func: ALM_License_SilentValidate, duration: 0.078 sec)
09/24/13 16:58:35:539 | [INFO] | | | | ALM | | | 5624 | _info_: ALM_License_SilentValidate return license status: Invalid and error: 213 : 19
09/24/13 16:58:35:539 | [ERROR] | | | | ALMService | | | 5624 | ERROR: License_Check error 213:19. (Errno = 2)
I've also tried creating a package using a trial licence and then using the adobe_prtk.exe tool to serialize the product at launch with no success.
I've read the support statemnt at http://helpx.adobe.com/creative-suite/kb/technical-support-boundaries-virtualized-or.html, but would appreciate direction from adobe as to what would be causing the above error.

Hello, thanks for the reply.
I have read those articles (multiple times :-)) I've installed the required c++ redistributables on the sequencer and also on the test machines.
I'm not getting any errors being reported in the App-V eventlogs.
I initially used the adobe_prtk.exe tool to serialize the app-v application at launch via startprocess in the userconfig file as shown. This runs but it doesn't work around this issue.
<UserScripts>
      <StartProcess RunInVirtualEnvironment="true">
        <Path>[{AppVPackageRoot}]\..\Scripts\adobe_prtk.exe</Path>
        <Arguments>--tool=VolumeSerialize --provfile=[{AppVPackageRoot}]\..\Scripts\prov.xml</Arguments>
        <Wait RollbackOnError="true"/>
<ApplicationId>[{AppVPackageRoot}]\Support Files\Contents\Windows\Illustrator.exe</ApplicationId>
      </StartProcess>
    </UserScripts>
Following that I read that AAMEE 3.1 removed the (http://blogs.adobe.com/oobe/2012/09/aamee-3-1or-why-puffer-fish-is-a-delicacy.html) machine to license issue
therefore allowing packages to be created using serial numbers and to be included within build images.
As I'm packaging Creative Cloud (not CS6), I'm assuming this has been carried into the Creative Cloud Packager for Enterprise which now must be used.
Any other ideas appreciated.

App-V 5 Adobe Creative Cloud (CC) Enterprise Licensing Error 213:19

Hello, I've posted this on Adobe forums but also posting here to see if anyone else has experienced/overcome this issue.
I'm attempting to create an App-V 5 sequence for Adobe Creative Cloud Enterprise software, but I appear to be getting licensing errors when launching the App-V sequence.
From what I understand in Adobe Create Cloud Enterprise, the licensing restrictions which tie the license to the machine have now been removed so that the base packages can be created with serial numbers and can be included within build images etc as opposed
to creating a trial package and then using a serialization file at install/launch time.
To start with I've created a package using the Adobe Creative Cloud Packager tool (CCP) for just the Illustrator CC application which includes the serial number. I've then sequenced this package using App-V 5 SP1.
When I run this app-v sequence on a test machine , Illustrator loads but I end up with a 213:19 error. Looking in the amt3.log the full error is
09/24/13 16:58:35:478 | [ERROR] | | | | SLCoreService | | | 5624 | error deleting bad mkey:
09/24/13 16:58:35:478 | [ERROR] | | | | SLCoreService | | | 5624 | Could not load machine key
09/24/13 16:58:35:478 | [ERROR] | | | | SLCoreService | | | 5624 | License store synchronization took 14.6 ms and return "License Store Access Failure: Machine key cannot be deleted (213:19)".
09/24/13 16:58:35:539 | [INFO] | | | | ALM | | | 5624 | _time_: (func: ALM_License_SilentValidate, duration: 0.078 sec)
09/24/13 16:58:35:539 | [INFO] | | | | ALM | | | 5624 | _info_: ALM_License_SilentValidate return license status: Invalid and error: 213 : 19
09/24/13 16:58:35:539 | [ERROR] | | | | ALMService | | | 5624 | ERROR: License_Check error 213:19. (Errno = 2)
I've tested out modifying permissions on the following folders within the app-v package under root but this has no effect.
C:\Program Files\Common Files\Adobe\Adobe PCD\
C:\ProgramData\Adobe\SLStore
I've also tried creating a package using a trial licence and then using the adobe_prtk.exe tool to serialize the product at launch (startprocess event in userconfig file) with no success.
Anyone tried this or have any ideas?

Hello, thanks for the reply.
I have read those articles (multiple times :-)) I've installed the required c++ redistributables on the sequencer and also on the test machines.
I'm not getting any errors being reported in the App-V eventlogs.
I initially used the adobe_prtk.exe tool to serialize the app-v application at launch via startprocess in the userconfig file as shown. This runs but it doesn't work around this issue.
<UserScripts>
      <StartProcess RunInVirtualEnvironment="true">
        <Path>[{AppVPackageRoot}]\..\Scripts\adobe_prtk.exe</Path>
        <Arguments>--tool=VolumeSerialize --provfile=[{AppVPackageRoot}]\..\Scripts\prov.xml</Arguments>
        <Wait RollbackOnError="true"/>
<ApplicationId>[{AppVPackageRoot}]\Support Files\Contents\Windows\Illustrator.exe</ApplicationId>
      </StartProcess>
    </UserScripts>
Following that I read that AAMEE 3.1 removed the (http://blogs.adobe.com/oobe/2012/09/aamee-3-1or-why-puffer-fish-is-a-delicacy.html) machine to license issue
therefore allowing packages to be created using serial numbers and to be included within build images.
As I'm packaging Creative Cloud (not CS6), I'm assuming this has been carried into the Creative Cloud Packager for Enterprise which now must be used.
Any other ideas appreciated.

AAMEE not working when trying to sign in.

So I downloaded the newest version of AAMEE, because I wanted to test the new function to install CS6 products serialized on my master image, but now I get a error each time I try to login with the Adobe-ID I have. This problem has been going on for 2 days now, even though it just tells me to try later. I want to test the new feature, because I got some troubles with activating two CS6 products on one image and the people that use this software is getting kind of impatient.

can you please share pdapp.log file on my email id.
thanks,
Rahul | [email protected]

Create prov.xml file error 14 or 28

When I wan’t to create a prov.xml file for Muse to activate computers in the Enterprise I get the 14 error, the comandline I use is:
adobe_prtk --tool=VolumeSerialize --generate --serial=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx --leid=Muse-1.0-Win-GM
Copyright 2012 Adobe Systems Incorporated
All rights reserved.
Return Code Code = 14
When I use the comandline with provfilepath I get the error 28;
adobe_prtk.exe --tool=VolumeSerialize --generate -- serial=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx --leid=Muse-1.0-Win-GM --provfilepath=C:\temp\prov.xml
Copyright 2012 Adobe Systems Incorporated
All rights reserved.
Return Code Code = 28
What goes wrong, any help would be appreciated
TIA.
Harmen

Hello Harmen, please check the %temp%\oobelib.log after completing your first command. This will reveil more details.
@Adobe:
I do get the same error code 14 (and then 19) when running the above command for leid=DesignSuiteStandard-CS6-Win-GM
del "%temp%\oobelib?.log" /q /s
%~dp0adobe_prtk --tool=VolumeSerialize --generate --serial=xxxxxxxxxxxxxxxxxxxxxxx --leid=DesignSuiteStandard-CS6-Win-GM --regsuppress=ss --eulasuppress --locales=de_DE --provfilepath=%temp%
ren "%temp%\oobelib.log" oobelib1.log
%~dp0adobe_prtk --tool=VolumeSerialize --stream --provfile=%temp%\prov.xml
ren "%temp%\oobelib.log" oobelib2.log
Permissions are correctly set for \SLStore and \SLCaches. Prov-File-Path was set to %temp% and is accessible/writable. Scripts were run with elevated privileges.
In Adobe's damn bad documentation I found a hint that Adobe Application Manager (now Adobe Creative Cloud Client) is required for the VolumeSerialize commands to work* but in my case this didnt change a thing...
* p.135 http://wwwimages.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/DE/AdobeApplicat ionManagerEnterpriseEditionDep…
further reading chapter "Volumenserialisierung des Pakets" Creative Cloud-Hilfe | Verwenden von Adobe Provisioning Toolkit Enterprise Edition
Adobe advises to catch the %temp%\oobelib.log which includes more information. However make sure to backup this file after each run of adobe_prtk because it gets overwritten :/
My results:
- step 1 "generation of prov.xml" ends with OOBELIB: SN validated for AAMEE Mode; stat = 27; Adobe PRTK: Failed to validate the serial number => Code 14
- step 2 "activation" ends with "invalid prov.xml" because of step 1 => Code 19
Once I set provfilepath to c: or c:\ step one quits with return code 28 (sufficient rights are set though). Whenever I omit the provfile-Parameters in step 1 and 2 I still receive return code 14 and 19.
Btw. another hint: check logs when doing a single command line serialization... For me I get loads of errors and end up with a trial mode and register popup
adobe_prtk --tool=Serialize --leid=DesignSuiteStandard-CS6-Win-GM --serial=xxxxxxxx [email protected]
Please help me out
PS: We're on ETLA (OTH Regensburg, former University of Applied Sciences, Ratisbon)

CS6 DesignWebPrem-AAMEE 3.1 Fails

I'm attempting to packed CS6 for Mac using AAMEE 3.1 but it fails with the following entries in the Console:
Thu Aug 1 14:06:14 2013
[INFO] AdobePackageBuilder - Build Version - 3.1.105.0
Thu Aug 1 14:06:14 2013
[INFO] AdobePackageBuilder - Logging Level verbosity Set to 4
Thu Aug 1 14:06:14 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/Enterprise/toolkit/../toolkit/PackageTemplate/CS6/Template_Uninstall.bin /Users/admin/Desktop/AdobeCS6_Full/Build/AdobeCS6_Full_Uninstall.pkg
Thu Aug 1 14:06:14 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/Enterprise/toolkit/../toolkit/PackageTemplate/CS6/Template_Install.bin /Users/admin/Desktop/AdobeCS6_Full/Build/AdobeCS6_Full_Install.pkg
Thu Aug 1 14:06:14 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/Enterprise/toolkit/../utilities/APTEE/CS6 /Users/admin/Desktop/AdobeCS6_Full/Build/AdobeCS6_Full_Install.pkg/Contents/Resources/Pro visioningTool
Thu Aug 1 14:06:14 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/Enterprise/toolkit/../utilities/APTEE/CS6 /Users/admin/Desktop/AdobeCS6_Full/Build/AdobeCS6_Full_Uninstall.pkg/Contents/Resources/P rovisioningTool
Thu Aug 1 14:06:14 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/Enterprise/toolkit/../toolkit/ASU/packages /Users/admin/Desktop/AdobeCS6_Full/Build/AdobeCS6_Full_Install.pkg/Contents/Resources/ASU /packages
Thu Aug 1 14:06:17 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Applications/Utilities/Adobe Application Manager/Enterprise/toolkit/../toolkit/ASU/Install.dylib /Users/admin/Desktop/AdobeCS6_Full/Build/AdobeCS6_Full_Install.pkg/Contents/Resources/ASU /Install.dylib
Thu Aug 1 14:06:29 2013
[INFO] AdobePackageBuilder - START utilCopySrcFolderToDstFolder /Volumes/CS6 DesWebPrm 1/Adobe CS6 Design and Web Premium/Install.app /Users/admin/Desktop/AdobeCS6_Full/Build/AdobeCS6_Full_Install.pkg/Contents/Resources/Set up/Install.app
Thu Aug 1 14:06:41 2013
[ERROR] AdobePackageBuilder - OS ErrMsg : Failed to copy object. ErrorCode (-128) ErrorString (userCanceledErr:).
Thu Aug 1 14:06:41 2013
[ERROR] AdobePackageBuilder - Aborted the copy operation.
Thu Aug 1 14:06:41 2013
[FATAL] AdobePackageBuilder - Error Failed to copy the contents of the folder.
Thu Aug 1 14:06:41 2013
[ERROR] AdobePackageBuilder - Failed to copy Setup folder (Install.app)
This is using a DVD from OETC. Any help would be appreciated.

Hi airlocksniffer,
Please copy the content of the DVD on your Mac HD and try to create a pacakge again.
If still it gives the same error please download the CS6 software from mentioned link: http://prodesigntools.com/adobe-cs6-direct-download-links.html and try creating the package again.
Regards,
Romit Sinha

Macintosh Creative Suite 6 package built with AAMEE 3.1 fails to install

I'm trying to create a new install CS6 Standard package for Macintosh using AAMEE 3.1.
All machines are new iMacs running 10.8.4.
I walk through the process of building the package, provide serial number, adobe login, and configure the setup. The package seems to be created without any errors or problems.
When I try to install the package on a machine, installation starts and runs for a minute or two, then stops showing the folllowing error:
The installation failed.
The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.
When I look at the Adobe setup error log, I see this message:
[       0] Wed Jun 19 18:17:43 2013 INFO
DEVersion: 6.0.0.0
Loading library from /Applications/Utilities/Adobe Application Manager/DECore/DE6/Setup.dylib
[       0] Wed Jun 19 18:17:43 2013 INFO
::START TIMER:: [Total Timer]
CHECK: Single instance running
CHECK : Credentials
Load Deployment File
Create Required Folders
Assuming uninstall mode
Lookup for master payload
[       0] Wed Jun 19 18:17:43 2013 ERROR
DW040: The product "{19D99776-D832-4EB7-84BD-55C06FD8D44C}" is not installed. Cannot proceed with the uninstall
[       0] Wed Jun 19 18:17:43 2013 INFO
##### Running EDT Workflow #####
:: END TIMER :: [Total Timer] took 1 milliseconds (0.001 seconds)
[       0] Wed Jun 19 18:17:44 2013 INFO
Uninstalling AAM
I have tried using the default settings for creating a new package. I've also tried making various changes from the defaults, such as disabling checking for conflicting applications, enabling AIR, and changing what updates are applied. The result is always the same error when I try to install the package.
There's no possibility of a conflict with a previous version of CS or something like that. I am literally doing this process on brand new Macs right out of the box, with a freshly downloaded copy of AAMEE, and a freshly downloaded DMG for CS6.
The log refers to "assuming uninstall mode" and "Cannot proceed with the uninstall" but since this is a completely new fresh install on a clean fresh OS I can't even begin to imagine what that could possibly mean.
I've tried contacting Adobe support, but so far have only had generic tier one responses. Will be trying again tomorrow.
I have searched this forum and the web in general, and I've found a similar reports with proposed solutions, such as disabling the check for conflicting applications, but none of them have helped.

You don't have to look at Adobe's log, it's an objective C programming issue.
Adobe didn't update their code.
Open Mac OS console application and look for installation error, you will find something similar meaning the code is deprecated for Mac OS 10.8:
11/7/13 5:03:55.758 PM Locum[74925]: Connection with distnoted server was invalidated
11/7/13 5:10:32.433 PM Installer[78488]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
11/7/13 5:10:32.433 PM Installer[78488]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
11/7/13 5:10:32.445 PM Installer[78488]: *** WARNING: -[NSImage compositeToPoint:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
11/7/13 5:10:32.445 PM Installer[78488]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
11/7/13 5:11:14.879 PM Installer[78488]: The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.

Deploying AAMEE 3.1 created MSI by double clicking it in UI mode

With the release of AAMEE 3.1, AAMEE created MSI supports both silent and UI based installation.
For UI based install of AAMEE 3.1 created packages, run the MSI as an administrator. If you are logged in as Admin user, you can double click it, otherwise right click the MSI and run as administrator. A minimalistic UI will be shown with just a progress bar. Any error during MSI install will cause a roll back and the user should check the logs to see what went wrong. You can also run the MSI in UI mode through this command line –
msiexec.exe /i <path of msi>
AAMEE still supports silent installation as the standard way of deploying the packages. Silent installation can be done only through the command line option –
msiexec.exe /i <path of msi> /qn.
Make sure that the command line is invoked with admin privileges. For users using SCCM 2007 for deploying AAMEE created packages, make sure to check “Allow users to interact with this program” checkbox in Environment tab of the SCCM Program for UI based installation. The corresponding checkbox for SCCM 2012 is “Allow users to view and interact with the program installation”.
For uninstallation of MSI in UI mode, there is only a command line option –
msiexec.exe /x <path of msi>
For silent uninstallation, add the /qn switch with the above command line –
msiexec.exe /x <path of msi> /qn
This UI based installation is only supported by the packages created using AAMEE 3.1. If you are using AAMEE 3.1 beta or AAMEE 3.0 for CS6 packaging, please download AAMEE 3.1 from http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html.
Feel free to mail me at [email protected] in case you see any issues.
Thanks,
Saransh Katariya | Member of technical staff | Adobe Systems | [email protected]

I want to revisit this. You can also see my related posts here:
http://forums.adobe.com/message/5073735
I had contented myself that I would use a batch file and require users to right-click and run as admin on the batch file. This was so that I could get Acrobat 10 installed at the same time. However, now that I have Acrobat 11, and I can separate out the installers, I would like to get back to this "double-click" method. I've verified that my new package (without Acrobat) works using the msiexec command. However, it still doesn't work as a double-click.
Here are the key lines from PDApp.log:
3/8/2013 07:54:21 [ERROR] Setup - Error parsing command line arguments at - "DISABLE_CCM_DESKTOPSHORTCUT".
Expected arguments are -
--mode=silent
--overrideFile="<FilePath>"
3/8/2013 07:54:21 [FATAL] Setup - Administrative Privileges required to continue
3/8/2013 07:54:21 [FATAL] Setup - End Adobe Setup. Exit code: -10
However, I am an admin on the machine, just as I am on all the machines that I've tested this on. And when I use a batch file with the msiexec and right-click and run as admin, I don't have to put other credentials in, verifying that I am, in fact, an admin on the machine.
Thanks for your assistance.
Mark

AAMEE 3.1 Photoshop package - Installation not possible

Hi,
-successfully created a Photoshop CS6 package with AAMEE 3.1
-starting the Adobe Photoshop CS6.msi with msiexec /i c:\temp\Adobe Photoshop CS6.msi /qn is starting the msi/setup
-Photoshop is not installed
- msi directly started - same proplem
-Logfiles searched for errors - nor error found which tells me what's wrong
-Package 7times new created
-no idea what i can do now
for any help thanks in advance!
Best regards
Stefan

The command which you are using is correct but the path which you have mentioned in the command have some space in the folder name. So would recoomend try to add double codes in the path like "c:\temp\Adobe Photoshop CS6.msi".
Here is the command which you can use to install the software silently. - msiexec /i "c:\temp\Adobe Photoshop CS6.msi" /qn
or you can change the directory first in the command prompt and then enter the command : msiexec /i "Photoshop CS6.msi" /qn

Remote Update Manager Error.

Hi all,
I'm receiving the following errors in the RemoteUpdateManager log. I can't get this to clear up. Did a full re-sync of our Adobe Update Server twice, to be sure it wasn't a corrupted file or download at our end.
01/10/13 10:30:27:181 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | ##################################################
01/10/13 10:30:27:181 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Launching the RemoteUpdateManager...
01/10/13 10:30:27:181 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | RemoteUpdateManager version is : 3.1.105.0 (BuildVersion: 3.1; BuildDate: Tue Sep 04 2012 13:58:18 )
01/10/13 10:30:27:182 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | **************************************************
01/10/13 10:30:27:182 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Initializing UpdaterCore Library...
01/10/13 10:30:27:348 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | UpdaterCore library initialized successfully.
01/10/13 10:30:27:348 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | **************************************************
01/10/13 10:30:27:348 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Starting UpdaterCore CheckForUpdate...
01/10/13 10:30:27:911 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | CheckForUpdates completed successfully.
01/10/13 10:30:27:911 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | **************************************************
01/10/13 10:30:27:911 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Starting UpdaterCore DownloadUpdates...
01/10/13 10:30:27:916 | [WARN] | | AAMEE | Utilities | RemoteUpdateManager | | | Update (AdobeDigitalPublishingCS6-2.0/2.05.1.550) is not supported by RemoteUpdateManager. Skipping processing of this update.
01/10/13 10:30:27:916 | [WARN] | | AAMEE | Utilities | RemoteUpdateManager | | | No new applicable Updates. Seems like all products are up-to-date.
01/10/13 10:30:27:917 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | **************************************************
01/10/13 10:30:27:918 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | ##################################################
01/10/13 10:30:27:918 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Ending the RemoteUpdateManager Return Code (0)
01/10/13 10:30:27:918 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | ##################################################
01/10/13 10:30:27:918 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | ##################################################
The AdobeDigitalPublishing update is the only one having issues. Anyone else seeing this? I've seen the AdobeDigitalPublishing updates get installed properly in the past using RUM.

RUM is turning out to be rubbish
Instead of RUM Adobe please engineer so that the Updater can be run via the command line. At the moment it just open up the Application Manager but from the mac toolbar doing it manually by opening the "Updater" works.
In enterprise NO ONE has admin rights!
01/22/13 11:09:32:630 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Starting UpdaterCore DownloadUpdates...
01/22/13 11:09:32:637 | [WARN] | | AAMEE | Utilities | RemoteUpdateManager | | | Update (AdobeDigitalPublishingCS6-2.0/2.05.1.550) is not supported by RemoteUpdateManager. Skipping processing of this update.
01/22/13 11:09:32:637 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Following Updates are to be downloaded :
01/22/13 11:09:32:637 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | (AdobePhotoshopCS6Support-13.0/13.0.4)
01/22/13 11:09:32:637 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | |
01/22/13 11:09:32:637 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | *** Downloading (AdobePhotoshopCS6Support-13.0/13.0.4) ...
01/22/13 11:09:46:842 | [ERROR] | | AAMEE | Utilities | RemoteUpdateManager | | | UpdaterCore failed for DownloadUpdates errorCode(207) curRefId(AdobePhotoshopCS6Support-13.0/13.0.4) errorCodeString(U43M1D207)
01/22/13 11:09:46:842 | [ERROR] | | AAMEE | Utilities | RemoteUpdateManager | | | *** Failed to download (AdobePhotoshopCS6Support-13.0/13.0.4) ...
01/22/13 11:09:46:842 | [ERROR] | | AAMEE | Utilities | RemoteUpdateManager | | | Some Updates failed to download ...
01/22/13 11:09:46:842 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | **************************************************
01/22/13 11:09:46:842 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Starting UpdaterCore InstallUpdates...
01/22/13 11:09:46:842 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | No new Updates to be installed ...
01/22/13 11:09:46:842 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | **************************************************
01/22/13 11:09:46:842 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Following Updates failed to Download :
01/22/13 11:09:46:842 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | (AdobePhotoshopCS6Support-13.0/13.0.4)
01/22/13 11:09:46:842 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | **************************************************
01/22/13 11:09:46:915 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | ##################################################
01/22/13 11:09:46:915 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | Ending the RemoteUpdateManager Return Code (2)
01/22/13 11:09:46:916 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | ##################################################
01/22/13 11:09:46:916 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | | ##################################################
01/22/13 11:09:46:916 | [INFO] | | AAMEE | Utilities | RemoteUpdateManager | | |

AAMEE msi created file is not installing on Windows 7 64bit

I am using AAMEE 3.01 which I belive is the latest. I am trying to package Adobe InDesign CS6.
I run through the basic options and the MSI is created. So before I upload the package to the server I need to test it out. I run the msi in silent mode via CMD and nothing ever happens. So I edited the MSI in InstallShield and removed the requirement for it to be ran silently so I can do some monitoring. From here, I run the MSI and click next a few times and then it begins the install process. After a few moments it says "copying files" and then proceeds to "rolling back" and disappears. At some point the install is encountering an error and failing but I am not sure why. I can install the product fine on my machine by using the .exe I built the package from

Hi,
I look into the various information from Adobe's forum and I find this usefull video :
http://tv.adobe.com/watch/creative-suite-in-the-enterprise/using-aamee-to-package-cs6-for- enterprise-deployment/
After that I tried another thing just to be sure.
When you create your MSI package, during the "Configuration" page, select "Ignore conflicts and continue installation".
Before using SCCM to deploy this MSI, I tried locally from a command prompt (run as)
msiexec /i AdobePhotoshopCS6.msi (without any parameter) to view the installation progress.
At the end it works fine and the software has been installed properly.
Now il will be able to try through SCCM.
I would add, that the MSI package created with AAMEE can be used with SCCM or any other tool that can push/upload the package (folder container).
SCCM is a basic tool that upload the package to the destination (WS), once done, a command line (or batch file) will be ran from the WS.

AAMEE error

Similar Messages

Maybe you are looking for