Design & Web Premium CS6 AAMEE 3.1 main package doesn't complete installation

[Guest]

Hi,

I've packaged Design & Web Premium CS6 using AAMEE3.1, but the main package doesn't complete installation on our corporate build but does on vanilla Windows 7. No error messgae comes up, I can't see anything obvious in the MSI log (where it get's to); it just sits there after copying all the files forever. i would appreciate is anyone has any pointers? The package is configured to continue if there are any conflicts. Thanks.

[Arpit Kapoor]

First of all make sure you have followed the CS Deployment Guide and made the package, just to avoid any conflicts. Also, make sure

If the same build works on your Vanilla Win 7 but not on your corporate environment, then i suppose the issue might be around permissions. Check the permission on that user account.

Try installing CS6 on the local admin and check.

If same issue, analyze the install log and look for errors

[Guest]

Hi Arpit, thanks for your assistance. I did follow the guide as I did for the deployment packages for Dreamweaver CS6 and InDesign CS6. Didn't have any prolem with those. In all cases I did the AAMEE packaging from an admin account, then tested on an admin account, before deploying to a user account.

In this case, the installation would halt after 37,721 files have been written to the hard drive, and the following line of the MSI log has been written:

MSI (s) (E8:74) [16:49:28:980]: Executing op: CustomActionSchedule(Action=CADeploy,ActionType=1025,Source=BinaryData,Target=runDeploymentManagerCA,CustomActionData=mode=install;sourceDir=Z:\STUDIO\Packages\AAMEE3.1\Adobe_DesignWebPremium-CS6_W7\Working\Adobe_DesignWebPremium-CS6_W7\Build\;installDir=;origDB=Z:\STUDIO\Packages\AAMEE3.1\Adobe_DesignWebPremium-CS6_W7\Working\Adobe_DesignWebPremium-CS6_W7\Build\Adobe_DesignWebPremium-CS6_W7.msi)

Now, when I run the AAMEE produced MSI installation (always from the commandline, by the way with the /qb) on a vanilla W7, it completes a successful installation within about 30 mins. However, when I run the MSI on our corporate build, it writes all the files (37,721) logs events in the MSI log to the point above, and appears to halt; no error message. I usually would give up after about an hour.

However, last night, I left it running on my VM, and went home. THis morning it had completed with this very interesting entries in the MSI log:

MSI (s) (E8:74) [16:49:28:980]: Executing op: CustomActionSchedule(Action=CADeploy,ActionType=1025,Source=BinaryData,Target=runDeploymentManagerCA,CustomActionData=mode=install;sourceDir=Z:\STUDIO\Packages\AAMEE3.1\Adobe_DesignWebPremium-CS6_W7\Working\Adobe_DesignWebPremium-CS6_W7-LV-1.0.0\Build\;installDir=;origDB=Z:\STUDIO\Packages\AAMEE3.1\Adobe_DesignWebPremium-CS6_W7\Working\Adobe_DesignWebPremium-CS6_W7-LV-1.0.0\Build\Adobe_DesignWebPremium-CS6_W7-LV-1.0.0.msi)

MSI (s) (E8:A8) [16:49:29:038]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI83B.tmp, Entrypoint: runDeploymentManagerCA

MSI (s) (E8!AC) [16:49:29:577]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (E8!AC) [16:49:29:599]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (s) (E8!AC) [16:49:29:623]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (E8!AC) [16:49:29:707]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (s) (E8:74) [21:43:21:887]: Executing op: ActionStart(Name=WriteRegistryValues,Description=Writing system registry values,Template=Key: [1], Name: [2], Value: [3])

For some reason, there was a pause from 16:49 till 21:43; and installation went on to complete successfully at 21:43. What do you make of this?

No typical file system or registry permissions issues as I was trying to install as an admin user.

Thanks again for your assistance.

[Arpit Kapoor]

Hmn, strange. May be some application is causing it to delay. Did you try performing selective startup as it might happen due to some 3rd party application. If its working fine on vanila, so i don' think that the issue is with the build. Might be due to the policies or permissions applied on that domain user or its account. You might need to check that.

[Arpit Kapoor]

[Moved the discussion to Creative Suite Enterprise Deployment Forum]