The linked document is not correct, as it applies to installation error codes, and I assume that the error code 14 you are refering to is generated by the provisioning toolkit.
If so, the oobelib.log file may give an indication why the error appears.
Please send me your contact details at romsinha@adobe.com so that I may call you and try to get the issue fixed.
I am also searching for a way to mass deploy this software on a lab of 40 iMacs. The pkg maker tool does not work with PS Elements 12. How do you mas deploy?
With over 9 hours of hold time, waiting for call backs that never happen, online chats that never happen, and a tech that messed up my machine, I have no faith in the bumbling idiots in the Vol Lic support center.
Mark
Hi Hawz,
yes the error code 14 is generated by the Adobe Provisioning Toolkit Enterprise Edition for CS6 (Windows).
But there is no oobelib.log file generated.
Regards,
Vojtech
Hi
I have the same issue. Each time i try to use adobe_prtk.exe i received an error 14.
I try on 2 different computer with admin rights.
What can i do ?
Rgds
Stéphane
Hello!
I did all required steps, as you mentioned above to serialize Adobe Elements 12, but it was not successfull. I had an return code=14 in oobelib.log.
What I did:
1) Installed "Adobe Photoshop Elements 12" on the machine
2) It has been successfully installed.
3) I opened "Command-line" cmd.exe as administrator (I have an administrative privileges on that machine)
4) Run following command:
adobe_prtk.exe --tool=VolumeSerialize --generate --serial="my_serial_number" --leid="V7{}PhotoshopElements-EMT12-Win-GM" --regsuppress=ss
where my_serial_number is my actually serial number with dashes.
5) After few seconds I got following:
Copyright 2012 Adobe Systems Incorporated
All rights reserved.
Return Code = 14
6) oobelib.log says following:
2013-12-09 10:48:05 [34556] Adobe PRTK: __OOBELIB_LOG_FILE__
2013-12-09 10:48:05 [34556] Adobe PRTK: *** Adobe PRTK tool START ***
2013-12-09 10:48:05 [34556] Adobe PRTK: Adobe PRTK tool VolumeSerialize invoked
2013-12-09 10:48:05 [34556] Adobe PRTK: .
2013-12-09 10:48:05 [34556] Adobe PRTK: creating .\prov.xml
2013-12-09 10:48:05 [34556] OOBELib: *************OOBELib Session Starts*************
2013-12-09 10:48:05 [34556] OOBELib: Version 6.2.0.43,6.2
2013-12-09 10:48:05 [34556] PCDService: PCD Service in non-threaded mode
2013-12-09 10:48:06 [34556] OPMWrapper: Failed in getting value for key in OPMGetValueForKey
2013-12-09 10:48:06 [34556] OOBELib: Failed to get Proxy username in OPM DB
2013-12-09 10:48:06 [34556] AXFBLicensing: Failed to load axlib.dll, trying again
2013-12-09 10:48:06 [34556] AXFBLicensing: Failed to load axlib.dll, trying again with axlib in ACF
2013-12-09 10:48:06 [34556] AXFBLicensing: All function pointers successfully retrieved
2013-12-09 10:48:06 [34556] OOBELib: Received Params for Online Validation : Driver : ”V7{}PhotoshopElements-EMT12-Win-GM”, Caller : 3
2013-12-09 10:48:06 [34556] OOBELib: received LEID : ”V7{}PhotoshopElements-EMT12-Win-GM”
2013-12-09 10:48:06 [34556] OOBELib: Supported Locales : ALL
2013-12-09 10:48:06 [34556] OOBELib: OOBELib ValidateSerialOnline
2013-12-09 10:48:06 [34556] OOBELib: Invalid licensing leid passed-[”V7{}PhotoshopElements-EMT12-Win-GM”].
2013-12-09 10:48:06 [34556] OOBELib: IAL Failed to set the LicensingLEID, falling back to GM
2013-12-09 10:48:06 [34556] OOBELib: Validate using Driver LEID : ”V7{}PhotoshopElements-EMT12-Win-GM”, App LEID : <blank>, SN : *******************************************
2013-12-09 10:48:06 [34556] OOBELib: Failed to get system default proxy in setProxyCredentialsForIALSession
2013-12-09 10:48:06 [34556] OOBELib: Failed to set proxy credentials for IAL session while validating serial number
2013-12-09 10:48:06 [34556] OOBELib: HTTPCommunicationAgent::processMessage is https://lm.licenses.adobe.com/aes/aes/v1/serialInfo (extURL=)
2013-12-09 10:48:06 [34556] OOBELib: Using proxy server.
2013-12-09 10:48:07 [34556] OOBELib: HTTP Request Status code 200.
2013-12-09 10:48:07 [34556] OOBELib: HTTPCommunicationAgent- Return Code:[0] response size-[232] time taken-[1599.47]ms.
2013-12-09 10:48:07 [34556] OOBELib: Got error from server-[9].
2013-12-09 10:48:07 [34556] OOBELib: ErrDesc from server: Some unknown error has occurred. : No associated Driver LEID is present in the database..
2013-12-09 10:48:07 [34556] OOBELib: Validate Serial status-[521] took-[1620.81]ms.
2013-12-09 10:48:07 [34556] OOBELib: OOBELib IAL VSN unknown error occured
2013-12-09 10:48:07 [34556] OOBELib: OOBELib IAL ValidateSerial call has failed : 521
2013-12-09 10:48:07 [34556] OOBELib: Using Driver/ALL combination for offline/invalid SNs scenario
2013-12-09 10:48:07 [34556] OOBELib: SN validated for AAMEE mode
2013-12-09 10:48:08 [34556] OOBELib: OOBELib stat = 257
2013-12-09 10:48:08 [34556] Adobe PRTK: Failed to validate the serial number
2013-12-09 10:48:08 [34556] Adobe PRTK: Return code 14
2013-12-09 10:48:08 [34556] Adobe PRTK: *** Adobe PRTK tool END ***
where SN : ******************************************* - is my serial number, I think. I changed it to * due to the security reasons.
PS. I have an internet connection.
What I do wrong? Can somebody help me?
I'm also getting the Return Code 14 on this. It looks like it's working for a few people but not others. Any other suggestons?
I had to remove the quotation marks around the leid name to get rid of the return code 14, now I'm getting a return code 0. I used this:
adobe_prtk.exe --tool=VolumeSerialize --generate --serial="xxxx-xxxx-xxxx-xxxx-xxxx-xxxx" --leid=V7{}PhotoshopElements-EMT12-Win-GM --regsuppress=ss
It's still popping up and asking me to sign in with an Adobe ID though, but now I'm able to close that window and use the photo editor. Before it wouldn't even let me use it if I didn't sign in.
Eric_D, did you manage to get rid of the login screen? I'm facing the same issue.. I've tried to set DISABLEOLSFEATURES=1 in setup.ini, but that didn't do the trick.
Can someone please clarify whether the adobe_prtk.exe commands are meant to be run on each client, i.e. as part of an installation script? Or do I somehow serialize the installation media?
Neither the instructions at http://helpx.adobe.com/photoshop-elements/kb/photoshop-element-12-silent-install.html or in this thread make this clear.
If, in fact, these commands are meant to be run on each client as part of the install script, how do I programmatically determine whether the activation has completed successfully? If someone can provide a sample installation script which implements some reasonable error handling, that would be helpful.
RyanGSteele wrote:
Can someone please clarify whether the adobe_prtk.exe commands are meant to be run on each client, i.e. as part of an installation script? Or do I somehow serialize the installation media?
Neither the instructions at http://helpx.adobe.com/photoshop-elements/kb/photoshop-element-12-sile nt-install.html or in this thread make this clear.
If, in fact, these commands are meant to be run on each client as part of the install script, how do I programmatically determine whether the activation has completed successfully? If someone can provide a sample installation script which implements some reasonable error handling, that would be helpful.
AFAIK you only need to generate the prov.xml file once. Then when you've installed PSE 12 to a client, run APTEE as follows (on the target machine, as part of your deployment script):
adobe_prtk.exe --tool=VolumeSerialize --provfile="prov.xml"
Obviously you need to supply correct paths to aptee executable as well as the prov.xml file.
APTEE returns error level 0 if everything is well, which is good enough for me. I used this to copy a dummy log to the target machine, indicating if activation went well. Batch script example as follows (taken from my mind, might contain errors):
@echo off
"%PROGRAMDATA%\APTEE\adobe_prtk.exe" --tool=VolumeSerialize --provfile="%PROGRAMDATA%\APTEE\prov.xml"
if %errorlevel% == 0 copy /y dummylog.log "%PROGRAMDATA%\APTEE\PSE12_APTEE_Status.log"
HTH
Pelle
Thanks Pelle, that's exactly the info I needed.
For anyone else who is deploying with something like Microsoft System Center 2012 Configuration Manager (SCCM), here's the batch file I used to install and serialize:
start "Photoshop Elements 12 Setup" /wait "%~dp0setup.exe" /UL1033 /V"SERIALNUMBER=XXXX-XXXX-XXXX-XXXX-XXXX-XXXX COUNTRY=39 NODESKTOPICON=1" if errorlevel 1 exit /b %errorlevel% "%~dp0adobe_prtk.exe" --tool=VolumeSerialize --provfile="%~dp0prov.xml" if errorlevel 1 exit /b 1
I just copied the adobe_prtk.exe and the prov.xml into the root of the deployment folder, along with this batch file. Replace the XXXX's with your own serial number, of course. I've added the NODESKTOPICON=1 as we prefer not to have the desktop shortcut created.
The first "if errorlevel" statement will make sure the MSI error code gets returned to the deployment process in case the installation fails for some reason. The second one returns an errorlevel of 1 if the serialization fails for any reason, and I can go chase down the log file if I need further details. (Haven't tested this part so this is all theoretical.)
For those having trouble with automatic updates not being disabled or the EULA being displayed, check out http://helpx.adobe.com/photoshop-elements/kb/photoshop-element-12-silent-install.html. It has the updated instructions for creating the application.xml.override file.
Adobe: Please improve the documentation about suppressing the prompt for Adobe ID at the above link, and update http://helpx.adobe.com/photoshop-elements/kb/silent-install-instructions-photoshop-element s-1.html to indicate it applies to Photoshop Elements 11 only.
Edit: I realized after I posted this that if setup.exe required a reboot, my script would interpret that as an error and serialization would fail. Here's a second pass at my batch file which should work around that condition. I've explicitly set REBOOT=ReallySuppress in the setup variables so if a reboot is required, setup.exe will not perform the reboot but will instead exit with error code 3010. In that case, the serialization is still performed but the error code can't be passed back to the calling process (i.e. SCCM) since we need to pass error code 3010 to ensure the calling process knows a reboot is required. In that case, if serialization failed, we won't know about it. Hopefully serialization will still work if a reboot is pending. Warning: this code is untested.
start "Photoshop Elements 12 Setup" /wait "%~dp0setup.exe" /UL1033 /V"SERIALNUMBER=XXXX-XXXX-XXXX-XXXX-XXXX-XXXX COUNTRY=39 NODESKTOPICON=1 REBOOT=ReallySuppress" if %errorlevel% equ 3010 goto rebootrequired if %errorlevel% neq 0 exit /b %errorlevel% "%~dp0adobe_prtk.exe" --tool=VolumeSerialize --provfile="%~dp0prov.xml" exit /b %errorlevel% :rebootrequired "%~dp0adobe_prtk.exe" --tool=VolumeSerialize --provfile="%~dp0prov.xml" exit /b 3010
Another question. If we need to uninstall the software after it has been serialized using this technique, is there something special we need to do to deactivate the software to return the license, or does the uninstaller take care of that?
I have the exact same problem with, sign in form poping up, but the program can be used?
Have you found any solution to supress the sign in form once and for all?
/ Anders
I found a decent work around for the time being until Adobe gives a solution.
I used this tip here:
http://www.itninja.com/software/adobe/photoshop-elements/12-1001
"I found a quick & dirty way to get rid of the log-in prompt that appears when starting PSE12, which many people find annoying:
1. Rename %ProgramFiles(x86)%\Common Files\Adobe\OOBE\PDApp\core\PDapp.exe to PDapp.old (or something)
2. Copy notepad.exe to the path above and rename it to PDapp.exe"
But found I get an error when you open Elements. To get around that I used nop.exe http://joenord.com/apps/nop/ and replaced PDapp.exe with it.
Now i get a clean open of Elements. No asking for sign in information.
Hope this helps!
I have not seen any issue with a sign in form popping up.
One more thing I should mention: make sure that if you are copying and pasting any commands from this thread that the quotation marks (") haven't gotten converted to typographic quotes (”). Particularly, this has happened in the comment from Romsinha above.
Hi all,
Anyone facing activation issue with PSE/PRE please send an e-mail to me at romsinha@adobe.com so that we may work towards a possible resolution.
Regards,
Romit Sinha
Hi Romsinha,
Rather than have everybody who is having trouble send you an email, wouldn't it be better to update the documentation at http://helpx.adobe.com/photoshop-elements/kb/photoshop-element-12-silent-install.html so that it actually has the correct information?
Also, can I suggest you update your comment at http://forums.adobe.com/message/6260649#5781206 to remove the typographic quotes and replace them with straight quotes? I think that would help resolve the issues some people are facing.
Hi HMwkr,
Please try the below mentioned steps to serialize Elements:
1. Generate prov.xml usng the command:
adobe_prtk.exe --tool=VolumeSerialize --generate --serial=<<Volume SN>> --leid=V7{}PhotoshopElements-EMT12-Win-GM --regsuppress=ss
2. Serialize using the command:
adobe_prtk --tool=VolumeSerialize --provfile="absolute path to prov.xml"
Please let us know whether it worked.
Regards,
Romit Sinha
Hi RyanGSteele,
I will work upon to get the document updated for silent installation for Elements.
Regards,
Romit Sinha