CS6 InDesign install error

[sgorney]

Hey all,
Getting this error when installing an InDesign CS6 package I'm getting this error

Installation failed. The installer reported: dyld: DYLD_ environment variables being ignored because main executable (/System/Library/PrivateFrameworks/Install.framework/Resources/runner) is setuid or setgid

The package is coming off an SMB repository, so it's wrapped in a DMG and using that script from the Resource kit. The pkg was made with AAMEE 3.1 and is deployed via Self Service. Funny thing is that the PhotoShop package is done the same way and it works just fine.

Thoughts?

[donmontalvo]

@sgorney I bumped up your post over at the AAMEE Adobe enterprise deployment forum.

http://forums.adobe.com/message/4968129

Don

[sgorney]

@donmontalvo

I never posted this to the AAMEE forum. That was someone else's.

[donmontalvo]

Ahh...looks like the same issue, or close.

Maybe post your error there too? I pinged Karl at Adobe to ask someone on his engineering team to respond. :)

Don

[sgorney]

Thanks you for doing that.

[kagibson]

I have responded to this post on the Adobe Forum. As it has been converted on an AFP share to DMG the fact that it is hosted on SMB should not impact the installer as it would if this had not been complete. Please respond to the thread on the forum and we will try and get this resolved for you.

http://forums.adobe.com/message/4968129

PS thank you Don for pinging me.

Cheers
Karl
Product Manager: Adobe

[Jpcorzo]

Hello everyone..
I was getting the same initial error when trying AAMEE 2.1. I install the latest version AAMEE 3.1 and stopped getting this error but now the installation doesn't complete at all, it gets half way and hangs in there, doesn't fail or anything like that. Any you guys think i might be missing? I've tried both methods, direct install, and caching then install.

[donmontalvo]

Just a thought, since the install starts, you might want to post to the AAMEE forum, where Adobe engineers can jump in to ask questions, ask for log files, etc. If you go that route, maybe post your solution here? :)

[mscottblake]

My reply from the thread linked above:

I have found that when I switched from AAMEE 3.0 beta to 3.1, I started receiving error messages like these. They come up when I double click the PKG straight from AAMEE. I believe the problem relates to permissions on the update files that AAMEE retrieves. I run the following command and it generally allows the package to install "chmod -R 755 /path/to/AAMEE/generated.pkg" (obviously without the quotes). This gives every file inside the package the read and execute permissions the installer needs.

Edit: Thinking about it, it could just be the updates and have nothing to do with the difference between 3.0 beta and 3.1. There weren't any updates to install back then.

I would definitely try running ```
chmod -R 755 /path/to/AAMEE/generated.pkg
```

[Kyuubi]

bump

[laurendc]

This error has actually been driving me a bit batty with our Adobe packages. I have yet to try chmodding the pkg. I will have to see how that goes.

[tkimpton]

Don you rock!

[donmontalvo]

Er, um...ok... :D

[tkimpton]

@donmontalvo][/url your commitment to help others is cool that is, plus 6 gin and tonics :)

[donmontalvo]

Oh, haha...paying it forward, hoping to mooch a cuple'a beers off the JAMF newbies at JNUC2014. :P

[bentoms]

@donmontalvo. That's my thing!