Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Adobe Customization Wizard Error code 14

Community Beginner ,
May 14, 2015 May 14, 2015

I'm trying to build an Adobe Acrobat package following the instructions from http://tv.adobe.com/watch/acrobat-it-tips-tricks-tutorials/customization-wizard-xi-for-mac-os-x/.  When I try to create the final package the Wizard errors out showing a code 14.  I looked that up and got this: The APTEE tool called from within returned an error. See /tmp/oobelib.log for details. I'm attaching the logs because I cannot figure out why the package is not being created. I can't figure out why the serial number is not being validated.

Screen Shot 2015-05-14 at 1.10.37 PM.png

Any help would be appreciated.

Thanks,

TOPICS
Acrobat
5.2K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 14, 2015 May 14, 2015

The third line from the end of the log.

"2015-05-14  12:17:09  [3830]  Adobe PRTK:  Failed to validate the serial number"

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 09, 2015 Dec 09, 2015

Steve,

Pointing out the line that says "Failed to validate the serial number" does not help the customer with his problem.  We know the validation failed; that goes with code 14.  What the customer needs is help finding WHY it failed.  Also, I need the same.

In my own case, I have checked network connectivity and can reach adobe servers. 

I'm using a serial number retrieved from a redemption code for Acrobat DC (12).  I have entered the serial number with no spaces, with spaces, and with hyphens instead of spaces.  Now, pay attention to this:

I HAVE HAD A CO-WORKER CHECK MY TYPING TO ENSURE THAT I ENTERED THE SERIAL CODE CORRECTLY.

Also, we are working from a printout of the serial code as provided by Adobe, NOT manually copied from the screen.

Several lines above the "Failed" line, the error log (running on a separate machine or I'd copy/paste it) says that this is an "OOBELib Bad Serial Number."  Given that this serial is a printout from Adobe and HAS BEEN TYPED CORRECTLY, then that's IMPOSSIBLE.

What is going on??

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 10, 2015 Dec 10, 2015

Check a couple of things:

Is the URL used by the Adobe Customization Wizard being blocked by a firewall, proxy, security software, etc...

Does the PRTK tool work on it's own to validate the serial number?  In other words, are you able to serialize a default installation using the Adobe Provisioning Tool?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 10, 2015 Dec 10, 2015

The URL is NOT blocked by our firewall.  I administer the firewall, so that was easy to check.  We don't use proxies and blockers and security software have been pushed aside or disabled.  I even tried this on a bare machine.

As far as the provisioning tool, I haven't used it. However, I did use this serial number on an installation and it validated perfectly fine, with the security software turned on.  That's how we discovered Adobe's obstructive, useless "constant sign-in required" which would not be a proper set-up for that multi-user workstation.  (PLEASE DO NOT try to argue why or why not this would not function for that workstation.  That is not the topic here.  The topic is getting the customization wizard to function properly.)  I did not sign in.  After researching how to disable this idiocy, I stayed on-line and did a proper removal, allowing the Adobe un-installer to do the work.  Ultimately, the key code has already been demonstrated to be valid and is not in use.

Let's remember that Adobe regularly publishes broken software with lame, hard-coded requirements.  For example, many Adobe installers require that one be logged in as the local machine administrator, not just a user with local admin privileges.  Also, the local admin CANNOT be renamed, which is a step many shops take for security reasons, but Adobe can't figure out how to require only admin priv's, rather than hard coding a specific username.  In the previous iteration of the Customization Wizard, version 11, there was a hard-coded leftover from version 10 where an executable would get called from the version 10 folder, which does not exist on a version 11 installation of the customization wizard.  The workaround was to manually create the version 10 folders and copy the v11 executable in question into the folder, but run the main program from the proper version 11 folder.  All that to point out that Adobe regularly publishes broken software.

Now, what mysterious little ticks are broken in the DC version of CW & how do I work around them?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 10, 2015 Dec 10, 2015

Here is the error log from today's attempt at running the Wizard.  I've tried looking into the axlibv7.dll file and gotten nowhere.

12/10/15 10:22:43:284 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | *** Adobe PRTK tool START ***

12/10/15 10:22:43:284 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | Adobe PRTK tool VolumeSerialize invoked

12/10/15 10:22:43:284 | [ERROR] |  |  |  | Adobe PRTK |  |  | 724 | C:\Users\ADMINI~1\AppData\Local\Temp\CusE88B1100

12/10/15 10:22:43:284 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | creating  C:\Users\ADMINI~1\AppData\Local\Temp\CusE88B1100\prov.xml

12/10/15 10:22:43:284 | [INFO] |  |  |  | OOBELib |  |  | 724 | *************OOBELib Session Starts*************

12/10/15 10:22:43:284 | [INFO] |  |  |  | OOBELib |  |  | 724 | Version 9.0.0.21,7.0

12/10/15 10:22:43:284 | [INFO] |  |  |  | PCDService |  |  | 724 | PCD Service in non-threaded mode

12/10/15 10:22:43:284 | [INFO] |  |  |  | DispatchClientLib |  |  | 724 | Dispatch table loaded from path: C:\Users\ADMINI~1\AppData\Local\Temp\CusE88B.tmp\dispatchtable.xml

12/10/15 10:22:43:284 | [INFO] |  |  |  | DispatchClientLib |  |  | 724 | (re)load Local Dispatch Table status-[0].

12/10/15 10:22:43:284 | [INFO] |  |  |  | DispatchClientLib |  |  | 724 | Scope : [2]

12/10/15 10:22:43:284 | [INFO] |  |  |  | DispatchClientLib |  |  | 724 | Setting scope to GM

12/10/15 10:22:44:033 | [ERROR] |  |  |  | OPMWrapper |  |  | 724 | Failed in getting value for key in OPMGetValueForKey

12/10/15 10:22:44:033 | [INFO] |  |  |  | OOBELib |  |  | 724 | Failed to get Proxy username in OPM DB

12/10/15 10:22:44:033 | [INFO] |  |  |  | AXFBLicensing |  |  | 724 | Failed to load axlibv7.dll, trying again

12/10/15 10:22:44:033 | [INFO] |  |  |  | AXFBLicensing |  |  | 724 | Failed to load axlibv7.dll, trying again with axlib in ACF

12/10/15 10:22:44:033 | [INFO] |  |  |  | AXFBLicensing |  |  | 724 | Failed to load axlibv7.dll from ACF

12/10/15 10:22:44:033 | [INFO] |  |  |  | OOBELib |  |  | 724 | Received Params for Online Validation : Driver : V7{}AcrobatESR-12-Win-GM, Caller : 3

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 724 | received LEID : V7{}AcrobatESR-12-Win-GM

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 724 | Supported Locales : ALL

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 760 | OOBELib ValidateSerialOnline

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Scope : [2]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Setting scope to GM

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 760 | Validate using Driver LEID : V7{}AcrobatESR-12-Win-GM, App LEID : <blank>, SN : 910182170481708027387763

12/10/15 10:22:44:048 | [ERROR] |  |  |  | OOBELib |  |  | 760 | Failed to get system default proxy in setProxyCredentialsForIALSession

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 760 | Failed to set proxy credentials for IAL session while validating serial number

12/10/15 10:22:44:048 | [INFO] |  |  |  | OOBELib |  |  | 760 | IALClient IAL_SetCaller-[0] took-[0.00]ms.

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | EndPoint requested: [AES]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Length of the URL: [51]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Returning from getEndpointAddr: [0]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | EndPoint requested: [AES]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Length of the URL: [51]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | URL found [https://lm.licenses.adobe.com/aes/aes/v1/serialInfo]

12/10/15 10:22:44:048 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Returning from getEndpointAddr: [0]

12/10/15 10:22:44:111 | [INFO] |  |  |  | OOBELib |  |  | 760 | HTTPCommunicationAgent::processMessage is https://lm.licenses.adobe.com/aes/aes/v1/serialInfo (extURL=)

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 2384 | HTTP Request Status code 200.

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | HTTPCommunicationAgent- Return Code:[0] response size-[3172] time taken-[821.19]ms.

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | Validate Serial status-[0] took-[887.02]ms.

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | IALClient IAL_SetCaller-[0] took-[0.00]ms.

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | OOBELib No associated locales returned by IAL

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Scope : [2]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Setting scope to GM

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | EndPoint requested: [GetSLConfig]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Length of the URL: [58]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Returning from getEndpointAddr: [0]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | EndPoint requested: [GetSLConfig]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Length of the URL: [58]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | URL found [https://lm.licenses.adobe.com/arlm/slconfig/v1/getSLConfig]

12/10/15 10:22:44:938 | [INFO] |  |  |  | DispatchClientLib |  |  | 760 | Returning from getEndpointAddr: [0]

12/10/15 10:22:44:938 | [INFO] |  |  |  | OOBELib |  |  | 760 | HTTPCommunicationAgent::processMessage is https://lm.licenses.adobe.com/arlm/slconfig/v1/getSLConfig (extURL=)

12/10/15 10:22:45:359 | [INFO] |  |  |  | OOBELib |  |  | 2888 | HTTP Request Status code 200.

12/10/15 10:22:45:468 | [INFO] |  |  |  | OOBELib |  |  | 760 | HTTPCommunicationAgent- Return Code:[0] response size-[37520] time taken-[519.25]ms.

12/10/15 10:22:45:484 | [INFO] |  |  |  | OOBELib |  |  | 760 | Get SLConfig File Data status-[0] took-[549.94]ms.

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | File successfully downloaded

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | Creating the SLConfigs folder

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | Creating the folder for leid

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | Creating/Updating SLConfig.xml

12/10/15 10:22:45:484 | [DEBUG] |  |  |  | OOBELib |  |  | 760 | Error creating SLConfig.xml

12/10/15 10:22:45:484 | [INFO] |  |  |  | OOBELib |  |  | 760 | checking LEID V7{}AcrobatESR-12-Win-GM

12/10/15 10:22:45:484 | [INFO] |  |  |  | OOBELib |  |  | 760 | LEID : V7{}AcrobatESR-12-Win-GM qualifies for install

12/10/15 10:22:45:484 | [ERROR] |  |  |  | OOBELib |  |  | 760 | Cannot accept a Retail SN in the AAMEE workflow

12/10/15 10:22:45:484 | [ERROR] |  |  |  | OOBELib |  |  | 760 | Using Driver/ALL combination for offline/invalid SNs scenario

12/10/15 10:22:45:484 | [ERROR] |  |  |  | OOBELib |  |  | 760 | SN validated for AAMEE mode

12/10/15 10:22:45:484 | [INFO] |  |  |  | OOBELib |  |  | 760 | OOBELib stat = 27

12/10/15 10:22:46:076 | [ERROR] |  |  |  | Adobe PRTK |  |  | 724 | Failed to validate the serial number

12/10/15 10:22:46:076 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | Return code 14

12/10/15 10:22:46:076 | [INFO] |  |  |  | Adobe PRTK |  |  | 724 | *** Adobe PRTK tool END ***

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 10, 2015 Dec 10, 2015

Are you using a VOLUME serial number or a RETAIL serial number?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Dec 10, 2015 Dec 10, 2015

We got this installation via redemption code bundled with scanner hardware.  That would lead me to believe, as you phrase it, the 7th line, working up from the bottom of the log.

I also noticed that the 5 line up says "SN validated for AAMEE mode."  That means the serial number was validated.

So, does the CW work with only one type of license, Volume OR Retail, not each??  What does that mean for the log message that the SN was validated??

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 11, 2015 Dec 11, 2015
LATEST

It will only work with a VOLUME serial number.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines