Skip to main content
Question

Adobe CS6 crashing loop.


Show first post

56 replies

RobertHammen
Forum|alt.badge.img+28
  • Esteemed Contributor
  • 1027 replies
  • January 18, 2013

Supposedly installing the Photoshop 13.0.4 patch + using APTEE to re-provision the software fixes the issue. Too early to tell, Adobe's not saying this on-the-record yet...


Forum|alt.badge.img+13
  • Author
  • Valued Contributor
  • 256 replies
  • January 18, 2013

I just forced a sync with my RUM server and it didn't pull down 13.0.4 yet. Hoping it will sometime over the weekend. I already have the APTEE tool packaged and in Casper to deploy as needed. What a pain - TGIF!


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 19, 2013

Just read the tech note on APTEE and it say you need to be connected to the Internet to serialize...... We have a proxy server so that not going to work!!!

Again Adobe not thinking


donmontalvo
Forum|alt.badge.img+36
  • Legendary Contributor
  • 4293 replies
  • January 20, 2013

@tkimpton wrote:

Just read the tech note on APTEE and it say you need to be connected to the Internet to serialize...... We have a proxy server so that not going to work!!! Again Adobe not thinking

From page 4 of the APTEE tech note:

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AdobeProvisioningToolkitEnterpriseEditionTechNote.pdf

Introduction The toolkit supplies commands that enable you to conveniently manage the serialization of an installed product. You might need to do this for example, in Creative Suite 6, users needs to be online for serialization to be successful. However if there are client machines that are not connected to the internet, you can use the Adobe Provisioning Toolkit Enterprise Edition to serialize a package on the machine.

Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 21, 2013

Thanks Don


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 21, 2013

Actually take that back lol...

Don this is EXACTLY what i am taking about and where the Adobe loathing comes from...no UAT what so ever!

from APTEE tech note:

Serializing a package when a user is offline In Creative Suite 6, users needs to be online for serialization to be successful. However if there are client machines that are not connected to the internet, the following process, called the Type1Exception process, can be followed to serialize a package. ???? Using the Adobe Provisioning Toolkit Enterprise Edition Syntax For Creative Suite 6 6 This process requires generation of a keycode on the offline client machine. The keycode is then used to generate a response code from an online machine. The response code generated using the online machine is then used to serialize the package on the offline client machine. This process can be used for both Retail and Volume customers. 1. On the offline client machine, generate a request code for activation by running the following command: adobe_prtk --tool=Type1Exception --generate --serial=serialNum where serialNum is the serial number This command returns a 44-character request code. 2. Using an online machine, visit the AOES website: http://www.adobe.com/go/getactivated 3. At the AOES website, log in with the Adobe ID. 4. Once authenticated, enter the Adobe serial number and the request code that was generated in step 1. Once the activation service successfully activates it, the response code is displayed. 5. Note down the response code 6. On the offline client machine, run the following command to activate the package: adobe_prtk --tool=Type1Exception accept --serial=serialNum --responsecode=responseCode --leid=LEID where: ? serialNum is the serial number ? responseCode is the code generated on the online machine in step 4 ? LEID is the product’s licensing identifier (see “Product identification” on page 9).

Behind a dam proxy like loads of other Enterprises.

DO YOU REALLY EXPECT ME TO GO AROUND TO EVERY SINGLE DAM MACHINE TO GENERATE THE CODE ADOBE!!!

Cant i just unserialize and then use the serialized package i created with AAMEE?


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 21, 2013

just tried the offline activation and this doesn't do anything

technote:

adobe_prtk --tool=Type1Exception accept --serial=serialNum --responsecode=responseCode --leid=LEID

also from adobe_prtk -h

adobe_prtk --tool=Type1Exception --accept --serial=serialNum [--responsecode=responseCode] --leid=DRIVERLEID

ADOBE SORT YOUR DOCUMENTATION OUT!

As you can see both say different things and they both dont work


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 21, 2013

Tried RUM

Photoshop 13.0.4 is not showing on Adobes Akami servers. Either this is overlooked or Adobe are confident of this fix yet.

Im inclined to think its the latter especially as the UAT has been non existant and seems to have gotten worse.


Forum|alt.badge.img+10
  • New Contributor
  • 343 replies
  • January 21, 2013

Tim - in your situation another option would be to just uninstall the CS6 product, then reinstall, making sure the Photoshop 13.0.3 and 13.0.3 updates are not applied, but the Photoshop 13.0.4 update is applied.


Forum|alt.badge.img+10
  • Contributor
  • 18 replies
  • January 21, 2013

Tim,
We are investigating why the PS 13.0.4 patch is not appearing with RUM or AUSST, there is nothing different about this patch that it should not have been posted. If you are in a situation whereby your clients cannot connect to the internet then it is best to use APTEE to create a prov.xml file that you can push to the clients this means the clients will not have to be online.

The steps I would advise you take are Create Update Package with AAMEE 3.1 and include PS 13.0.4
Use below command with APTEE to create prov.xml

1) create prov.xml file using following commandline -
adobe_prtk --tool=VolumeSerialize --generate --serial=<serial number> --leid=<LEID of product> --provfilepath=<path where it should be created>

NOTE:
If –provfilepath flag is used, then prov.xml will be created at the specified location. If –provfilepath flag is not used, then prov.xml will be created at the default location. The default location will be the location where the adobe_prtk file is present.

2) on client serialize with command line -
adobe_prtk --tool=VolumeSerialize –stream –provfile=<Path of prov file>

You could push this out with casper.

Please let me know if this works or does not work.

Cheers
Karl Gibson | Product Manager | Enerprise IT Tools


Forum|alt.badge.img+13
  • Author
  • Valued Contributor
  • 256 replies
  • January 21, 2013

@tkimpton - still not up on their AUS servers yet. I've been doing a check every 12 hours or so.

I'm going the un-install re-install route on the computers that have 13.0.3 applied. I can't apply the patches manually via the GUI due to my settings in AAMEE having updates disabled. I know there is a way to install these patches in a different manner, but I don't have the time to go through the documentation at this moment to figure it out, considering an uninstall/reinstall is just a couple of clicks away using Casper.

In addition, my attempts at uploading the patch to the AUS have been unsuccessful, due to some errors in RUM about being unable to download the patch, despite all the permissions being correct and I'm able to get the patch over http through a direct URL in a web browser.

It's disappointing the loopholes that legally licensed volume customers are going through to get this software installed, when you can still go on Pirate Bay and download a cracked version of every version of their software, despite all of Adobe's copy and licensing protection.


donmontalvo
Forum|alt.badge.img+36
  • Legendary Contributor
  • 4293 replies
  • January 21, 2013

@taugust04 wrote:

It's disappointing the loopholes that legally licensed volume customers are going through to get this software installed, when you can still go on Pirate Bay and download a cracked version of every version of their software, despite all of Adobe's copy and licensing protection.

Karl just posted a fix/workaround for the missing 13.0.4 patch issue:

http://forums.adobe.com/docs/DOC-2991


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 22, 2013

Thanks Don but Again Adobe with ZERO instructions what to do with it...FFFFIIINNGGG BRILLIANT!!!!


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 22, 2013

KARL

I HAVE WASTED ABSOLUTELTY HOURS AND HOURS (YES THIS IS SHOUTING)

THERE IS ABSOLUTELY NO WHERE DOES IT SAY TO USE THE FLAG adobe_prtk --tool=VolumeSerialize

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AdobeProvisioningToolkitEnterpriseEditionTechNote.pdf

It also does say in terminal if i just type in adobe_prtk and hit enter.

ADOBE TWAT THE DOCUMENT WRITER SERIOUSLY ....HUNDEREDS IF NOT THOUSANDS OF ADMINS READ THE MANUALS AND THEY ARE WRONG!!!


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 22, 2013

KARL

I ALREADY HAVE SERIAL PKGS CREATED WITH AAMEE3.1

WHY CANT I JUST USE THOSE????


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 22, 2013

**KARL

LET US KNOW WHEN WE CAN REPACKAGE USING AAMEE3.1 WHICH WILL AUTOMATICALLY PULL DOWN THE CORRECT UPDATES AND MAKE WORKING INSTALLERS**


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 22, 2013

Added to AUSST Server.

Shows when manually invoking the Adobe Updater from the top toolbar.

Invoking via RUM doesnt install it or show in the logs

I am unable to open the AAM in (Updater) mode via the command line so i can even add this to self service.

Karl please tell us all how we can invoke the AAM in Updater mode to launch via the command line so we can do this


Forum|alt.badge.img+21
  • Honored Contributor
  • 970 replies
  • January 22, 2013

not impressed!

Also not all updates install via RUM!!!

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 | | | #################################################


donmontalvo
Forum|alt.badge.img+36
  • Legendary Contributor
  • 4293 replies
  • January 22, 2013

AAMEE 3.1 should let you update existing PKG and add the update.

This is a real nightmare. :(


Forum|alt.badge.img+10
  • Contributor
  • 18 replies
  • January 22, 2013

Hi All, Ok so we have been doing more testing and this is the current state of play.

We have tested AUSST and the 13.0.4 update is showing up
We have tested RUM and it is pulling in the 13.0.4 PS patch
We have tested creating update package with AAMEE which includes patch
We have also tested manually adding the patch to AUSST with instructions provided (a little awkward)

If you have affected systems these are the steps you should take

  1. Install 13.0.4 patch on client in one of the three methods listed above
  2. Use AAMEE 3.1 to create a serialization file
  3. Deploy Serialization file to the client

This in all our tests resolved the issue on a machine that was affected and we launched the product multiple times with no issue.

We are in the process of testing a serialization file created with AAMEE 3.0 however it is best to use 3.1 if possible.

Please let me know if there is any issues and please rest assured that we will be conducting a post mortem to try and make sure the issue does not occur again and also that our response would be better if we fail on our first promise :-)

Cheers
Karl Gibson | Product Manager | Enerprise IT Tools


donmontalvo
Forum|alt.badge.img+36
  • Legendary Contributor
  • 4293 replies
  • January 22, 2013

@kagibson wrote:

Please let me know if there is any issues and please rest assured that we will be conducting a post mortem to try and make sure the issue does not occur again and also that our response would be better if we fail on our first promise :-)

Karl,

Thanks for pushing this through to resolution. For what it's worth, I hope the post mortem includes a commitment by Adobe to adhere to Apple Software Delivery Guidelines. I'd hate to see the Mac admin community toss Adobe into the "Cr@ppy Apps" list.

AAMEE is a great workaround, but it really is a big piece of duct tape. It's a step in the right direction. But now it's time for Adobe to slam on the brakes and shift gears - we need installers that adhere to Apple and Microsoft standards (er, respectively). :)

Don

"I ain't gotta apologize for st!" Scott Forstall


Forum|alt.badge.img+24
  • Honored Contributor
  • 341 replies
  • January 22, 2013
Karl, Thanks for pushing this through to resolution. For what it's worth, I hope the post mortem includes a commitment by Adobe to adhere to Apple Software Delivery Guidelines. I'd hate to see the Mac admin community toss Adobe into the "Cr@ppy Apps" list. AAMEE is a great workaround, but it really is a big piece of duct tape. It's a step in the right direction. But now it's time for Adobe to slam on the brakes and shift gears - we need installers that adhere to Apple and Microsoft standards (er, respectively). :) Don

+1


Forum|alt.badge.img+10
  • Contributor
  • 18 replies
  • January 22, 2013

Don, Indeed and I know where you are coming from. This issue has been tough in that I feel like we may have lost some of the good graces we had earned with the Mac IT admin community as a result of AAMEE and the IT Tools like RUM & AUSST. However hopefully the community will still have a little trust in Myself , Jody and the team. We really try and create the IT tools with the focus firmly on the IT Admin. We will of course continue to do so and I understand and share your desire to move to native installers.

Cheers
Karl Gibson | Product Manager | Enerprise IT Tools


Forum|alt.badge.img+10
  • New Contributor
  • 343 replies
  • January 22, 2013

Karl writes:

If you have affected systems these are the steps you should take

  1. Install 13.0.4 patch on client in one of the three methods listed above
  2. Use AAMEE 3.1 to create a serialization file
  3. Deploy Serialization file to the client

A major problem here is that the Serialization executable/file generated by AAMEE 3.x is not easily deployable. The admin still has to figure out how to get the executable and xml file delivered to each machine and has to come up with some way to actually execute the thing. AAMEE should spit out an Apple Package that does the task.

I wrote a tool to do just that using APTEE:
https://github.com/gregneagle/makereserializationpkg

It would not be hard for AAMEE to do the same thing.


donmontalvo
Forum|alt.badge.img+36
  • Legendary Contributor
  • 4293 replies
  • January 22, 2013

@gregneagle wrote:

A major problem here is that the Serialization executable/file generated by AAMEE 3.x is not easily deployable. The admin still has to figure out how to get the executable and xml file delivered to each machine and has to come up with some way to actually execute the thing. AAMEE should spit out an Apple Package that does the task.

I have to agree, the Platypus solution results in a non-deployable app that someone with admin rights has to double-click on every computer. When you have hundreds or thousands of computers, time/effort/cost goes up very high very fast.

If AAMEE can spit out a zero-touch PKG, we can push out to the target computers.

Else, who foots the bill for all the sneaker-net?

Don


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings