Hi,
I made an mst file with Installshield for Adobe Acrobat Pro 9.0.0
And i am using Radia as my deployment tool.
Installing, Repairing, Uninstalling and launching - everything working fine manually. But through Radia, i am getting the [ISX-SERIALNUMBER] - Error. It is not installing at all.
I tried through customization wizard for version 9. But it is also showing the same error.

Is this problem occuring only in Radia or what?[8|]


Please help me.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Does the error message actually say ISX-SERIALNUMBER or does it have the serial number listed there?

I had something very similar with my Acrobat 9 package. it was throwing a window with the title "Adobe Acrobat 9" and the text just ####-####-####-#### error but it was my serial number.

Turns out there is some internal consistency checking going on with the MSI and i always modify the MSI files to include a custom action. once i went back to the downloaded one, this error went away. Is there a chance that Radia is modifying the actual MSI when it's deploying?
Answered 09/30/2008 by: Chipster
Blue Belt

Please log in to comment
0
how are you publishing in radia? what does your MSILOG say? Is it even applying the transform at all?
Answered 09/30/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
As Chipster say, mine also the same error. I tried it from downloaded one. But i am getting the same error.

Kiptek,


The following options have been carried out:
1) Published using an AIP option
2) Without the AIP option
3) With the MST transform provided by Acrobat utility ( Acrostan.mst )
4) Without the MST transform
5) Published using local AIP method
6) With/Without silent manually installing and working fine.

The thread started by Chackz - "Acrobat 9.0 standard packaging using Radia 4.1 also the same issue.
Answered 09/30/2008 by: laxmikumaris
Senior Yellow Belt

Please log in to comment
0
I am having the same issue trying to deploy Acrobat 9.0 through Radia. If you have RadiaMSI create a verbose log during install, you can see that the MSI, when coming from Radia, is treated as a retail binary and not a volume binary so your serial number doesn't work.

Executing the installation from a command line works fine because the MSI on your computer is treated as a volume binary. The MSI that's coming down from Radia is different from the manufacturer's MSI and so the check fails. I have refered this issue to our Radia contact and hope to get some type of answer soon.
Answered 10/01/2008 by: flipper
Senior Yellow Belt

Please log in to comment
0
[:'(] [:@]

my bad lax.... went back & retried it & it fails... tried a /qf & i manually typed in the serial & still got an invalid serial # fail.... i guess we wait on flipper's contact 2 make contact... [8D]
Answered 10/02/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
Hi,

Do you have an .ini file with the application, If so could you please add the .ini file as a additional file when publishing it in radia and check it.

Regards,
Sathish.S
Answered 10/04/2008 by: ssathish05
Senior Yellow Belt

Please log in to comment
0
abcpy.ini or setup.ini??
Answered 10/06/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
I think abcpy.ini will do good..

Sathish.S
Answered 10/06/2008 by: ssathish05
Senior Yellow Belt

Please log in to comment
0
nope. still errors out. the funny thing is i can manually run the install from where radia puts it & it works just fine, but with radia managing the install, it fails on the serial check even with a /qf & retyping it in to make sure there are no special characters or anything like that.
Answered 10/06/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
Yes Kiptek. Like you said, all are working fine........but through Radia, it is not working..........[&o]
Answered 10/06/2008 by: laxmikumaris
Senior Yellow Belt

Please log in to comment
0
we are also experiencing issues when using radia to deploy adobe 9 saying the serial is invaild...:(

will let you know if we come up with a fix, looking at the HP forums they are talking about a tmp file to do with verisign so were looking in to that at the mo..
Answered 10/08/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
What options are you using to upload the package to Radia?

What version of Radia?
machine/User split?
LongFile Names?
Selecting the Transform?

Regards,
P
Answered 10/08/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
Were using V4.0.1
2nd ever package i'm doing in radia, Office 2007 was my first using component selection and this will be my second package using the msi instead

Not sure what you mean about the rest, Copied media to temp dir on network and ran the adobe custom wizard. Navigated radia publisher to the msi, ticked the box in the tansform option and additional files (setup.exe 2x ini files, windows installer 3.1v2 etc)
Clicked next and it started the adobe install came up with the username and company then said serial was invaild trying a monitor mode installation at the mo, i know the install works using "msiexec /i acrostan.msi /t acrostan.mst /qn"
Answered 10/08/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
When publishing from the publisher try using the following options:

Admin Install Point
If possible, tick "Publish with AIP" although it may already be an aip of course.
Select the AIP path, I usually use C:\temp\aip
Tick "Use local AIP support for MSI redirector
Tick "Use long filenames

Transforms
Select your transform

Also once thats done check that under "Properties" you can see the property in question which is causing the problems.

Failing all of this try doing a basic publish, without advanced or AIP just as a test to see if you can get Radia deploying the package

Regards,
P
Answered 10/08/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
I dont have the options about use local aip etc, once selecting the msi, i get screen 2 Edit

Admin Install Point
Tick Box publish with AIP c:\temp\adobe
Execute user interface set to full
delete aip when done
connect aip package to service and all the options on the left
install simulater
features properties
transforms
etc

Copied the CD to c:\adobe and lanuched publisher pointed it to the msi in c:\adobe and then set an AIP as c:\temp\adobe ticked the box for transform and ticked the box for the other source files from the CD setup.exe the ini files etc click next and it goes through and creates a network installation point using adobe software, or click the Installation Simulation and it launches the msi and then prompts me for a serial although the Username and company fileds are filled in? very odd
Answered 10/08/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
Appears in that case that I have a different version of the publisher, as I get the local AIP options just below "Connect AIP package to service".

When publishing instead of selecting "Advanced" try a publish with "Basic", just as a test to confirm that radia can deploy the package with no problems, with a transform.

Also have you checked http://itninja.com/link/adobe-customization-wizard-8 as there is a mention of a property that prevents the ISX_SERIALNUMBER property being used, may be worth a look even though its only version 8 not 9.

P
Answered 10/08/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
Admin Install Point
If possible, tick "Publish with AIP" although it may already be an aip of course.
Select the AIP path, I usually use C:\temp\aip
Tick "Use local AIP support for MSI redirector
Tick "Use long filenames

Transforms
Select your transform


With these options, I get an error right off the bat with a 2k log... Looks like trouble finding the local AIP which I published from & is copied down to C:\INSTALLDIR\ACROPRO90\... (All 1.23 gigs):


=== Verbose logging started: 10/8/2008 12:06:14 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:\PROGRA~1\Novadigm\RadiaMSI.EXE ===
MSI (c) (F8:98) [12:06:14:755]: Resetting cached policy values
MSI (c) (F8:98) [12:06:14:755]: Machine policy value 'Debug' is 0
MSI (c) (F8:98) [12:06:14:755]: ******* RunEngine:
******* Product: c:\RadiaMsiAip\AC76BA86-1033-F400-7760-000000000004\ACROPRO.MSI
******* Action:
******* CommandLine: **********
MSI (c) (F8:98) [12:06:14:755]: Note: 1: 2203 2: c:\RadiaMsiAip\AC76BA86-1033-F400-7760-000000000004\ACROPRO.MSI 3: -2147287037
MSI (c) (F8:98) [12:06:14:805]: MainEngineThread is returning 3
=== Verbose logging stopped: 10/8/2008 12:06:14 ===

Answered 10/08/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
more from the connect log:


NVD000010I [zspawn_method ] 12:06:06 [RADCONCT / 00000624] SYSTEM --- -------- [Pid=00001EAF] ----- BEGIN C:\PROGRA~1\Novadigm\RadiaMSI.EXE -----
NVD000001V [close_log_file ] 12:06:06 [RADCONCT / 00000624] SYSTEM --- Closing log file on [Wed Oct 08 12:06:06 2008]
NVD000001V [open_log_file ] 12:06:08 [RADIAMSI / 000000f8] SYSTEM --- System [Microsoft Windows (32Bit)] started [RADIAMSI] on [Wed Oct 08 12:06:08 2008]
NVD000501A [open_log_file ] 12:06:08 [RADIAMSI / 000000f8] SYSTEM --- Running OS: Windows NT 5.1 Build=(2600)
NVD000512A [Radiamsi.exe ] 12:06:08 [RADIAMSI / 000000f8] SYSTEM --- Module Information: Rev 1.17 Aug 13 2004 09:58:58
NVD000513A [C:\PROGRA~1\Nov] 12:06:08 [RADIAMSI / 000000f8] SYSTEM --- Module Date:[12/23/2004] Time:[16:24:44] Size:[135348] File:[C:\PROGRA~1\Novadigm\radiamsi.exe]
NVD000512A [RadiaMsi.dll ] 12:06:09 [RADIAMSI / 000000f8] SYSTEM --- Module Information: Rev 1.76.1.5 Jan 21 2005 15:17:32
NVD000513A [RadiaMsi.dll ] 12:06:09 [RADIAMSI / 000000f8] SYSTEM --- Module Date:[2/14/2005] Time:[10:57:02] Size:[680116] File:[C:\PROGRA~1\Novadigm\RadiaMsi.dll]
NVD000001V [Initialize ] 12:06:09 [RADIAMSI / 000000f8] SYSTEM --- Read MSI.EDM
NVD000001V [ProcessMsi ] 12:06:09 [RADIAMSI / 000000f8] SYSTEM --- MSI filename ACROPRO.MSI
NVD000010V [ProcessMSI ] 12:06:09 [RADIAMSI / 000000f8] SYSTEM --- Using Msi Package: c:\RadiaMsiAip\AC76BA86-1033-F400-7760-000000000004\ACROPRO.MSI
NVD000001V [FindOject ] 12:06:09 [RADIAMSI / 000000f8] SYSTEM --- MST filename AcroPro90.mst
NVD000001V [OpenPackage ] 12:06:09 [RADIAMSI / 000000f8] SYSTEM --- Open Package C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADBE_A~1\NvdTemp.msi
NVD000010V [ProductExist ] 12:06:10 [RADIAMSI / 000000f8] SYSTEM --- Checking for existing ProductCode: {AC76BA86-1033-F400-7760-000000000004}.
NVD000010V [ProductExist ] 12:06:10 [RADIAMSI / 000000f8] SYSTEM --- Product: {AC76BA86-1033-F400-7760-000000000004} not installed
NVD000001V [MergeMSTs ] 12:06:10 [RADIAMSI / 000000f8] SYSTEM --- Applying transform C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADBE_A~1\AcroPro90.mst
NVD000001V [OpenPackage ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Open Package C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADBE_A~1\ACROPRO.MSI
NVD000010V [ProductExist ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Checking for existing ProductCode: {AC76BA86-1033-F400-7760-000000000004}.
NVD000010V [ProductExist ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Product: {AC76BA86-1033-F400-7760-000000000004} not installed
NVD000001V [CreateGUIDDir ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Creating GUID directory: [C:\PROGRA~1\Novadigm\Lib\AC76BA86-1033-F400-7760-000000000004\]
NVD000001V [FindRelatedProd] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Searching for related Products by upgrade code: {AC76BA86-0000-0000-7760-7E8A45000000}
NVD000001V [FindRelatedProd] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- No related product found.
NVD000001V [MsiCntrlObj::Bu] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Building MSI Control Object: MSICNTRL.EDM
NVD000001V [MergeFeatureLis] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Number of heaps: 1
NVD000001V [MergeFeatureLis] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Merging MSI features from: C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADBE_A~1\00000000.000\04336406.001\MSIFEATS.EDM
NVD000001V [ReadFeatureList] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Reading MSI Feature Control Object: C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADBE_A~1\00000000.000\04336406.001\MSIFEATS.EDM
NVD000010V [ReadObj ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Read MsiFeats object
NVD000001V [ReadOject ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Read Properties Object
NVD000001I [GetPropertiesCo] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- REBOOT="ReallySuppress"
NVD000001V [RadiaMST ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Constructing Transform File: Radia.MST
NVD000001V [OpenPackage ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Open Package C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADBE_A~1\Applied.msi
NVD000010V [ProductExist ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Checking for existing ProductCode: {AC76BA86-1033-F400-7760-000000000004}.
NVD000010V [ProductExist ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Product: {AC76BA86-1033-F400-7760-000000000004} not installed
NVD000001V [AppliedRadiaCA ] 12:06:11 [RADIAMSI / 000000f8] SYSTEM --- Building Radia Transform Radia Transform
NVD000001V [ApplyRadiaCA ] 12:06:12 [RADIAMSI / 000000f8] SYSTEM ---
NVD000001V [ApplyRadiaCA ] 12:06:12 [RADIAMSI / 000000f8] SYSTEM ---
NVD000001V [ApplyRadiaCA ] 12:06:12 [RADIAMSI / 000000f8] SYSTEM ---
NVD000001V [SubstituteRadia] 12:06:13 [RADIAMSI / 000000f8] SYSTEM --- No RadiaVariable records to substitute.
NVD000001V [MergeMSTs ] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- Merging transform C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADBE_A~1\AcroPro90.mst
NVD000010V [MakeMST ] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- Generate Radia Transform
NVD000010V [SetupLogAndUIOp] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- Initializing Log and UI properties
NVD000010V [SetupLogAndUIOp] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- [Command Line]:/qf /l*v C:\INSTALLDIR\AcroPro90.log
NVD000010V [SetupUserOption] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- [Log File]:C:\INSTALLDIR\ACROPRO90.LOG [Log Mode]:*V
NVD000010V [SetupLogAndUIOp] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- [UI Settings]:/QF
NVD000010V [ClearLogAndUI ] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- /QF /L*V C:\INSTALLDIR\ACROPRO90.LOG
NVD000010V [SetupUserOption] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- MSI Command Line:[ ]
NVD000001V [InstallProduct ] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- Command Line : [ NOIE=TRUE REBOOT=Suppress NVD_INSTALL_MODE=Y NVD_USERCNTRL=N REBOOT="ReallySuppress" TRANSFORMS=C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE\ADBE_A~1\Radia.mst NVD_STARTTIME= 128679555746553488 SOURCELIST="c:\RadiaMsiAip\AC76BA86-1033-F400-7760-000000000004\" ]
NVD000001V [InstallProduct ] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- Launch Product Install from source [c:\RadiaMsiAip\AC76BA86-1033-F400-7760-000000000004\ACROPRO.MSI]
NVD000010V [InstallProduct ] 12:06:14 [RADIAMSI / 000000f8] SYSTEM --- Installation ended with Error Code [3]
NVD000010V [StopMsiService ] 12:06:15 [RADIAMSI / 000000f8] SYSTEM --- Stopping Msi Service
NVD000010A [Edm_Exit ] 12:06:15 [RADIAMSI / 000000f8] SYSTEM --- Terminating program
NVD000001V [close_log_file ] 12:06:15 [RADIAMSI / 000000f8] SYSTEM --- Closing log file on [Wed Oct 08 12:06:15 2008]
NVD000011V [nvd_exec ] 12:06:15 [RADCONCT / 00000624] SYSTEM --- Process complete: Wait rc = [0] getexit rc = [1] ExitCode = [8]
NVD000010I [zspawn_method ] 12:06:15 [RADCONCT / 00000624] SYSTEM --- -------- [Pid=00001EAF] ----- END C:\PROGRA~1\Novadigm\RadiaMSI.EXE ----- rc = [8]

NVD000010I [zspawn_method ] 12:06:15 [RADCONCT / 00000624] SYSTEM --- [zspawn_method] is resuming in [EDMFSM]
NVD000002E [C:\PROGRA~1\Nov] 12:06:15 [RADCONCT / 00000624] SYSTEM --! MsiError: 3 - The system cannot find the path specified.
NVD005460E [zspawn_method ] 12:06:15 [RADCONCT / 00000624] SYSTEM --! Method [C:\PROGRA~1\Novadigm\RadiaMSI.EXE] returned rc [8], process would be aborted
NVD005460E [zspawn_method ] 12:06:15 [RADCONCT / 00000624] SYSTEM --! Fatal Error : [MsiError: 3 - The system cannot find the path specified. ]
NVD005460E [zspawn_method ] 12:06:15 [RADCONCT / 00000624] SYSTEM --! Method [C:\PROGRA~1\Novadigm\RadiaMSI.EXE] returned rc [8]
NVD000010E [fsm_process_add] 12:06:15 [RADCONCT / 00000624] SYSTEM --! RC [709] after executing ZCREATE [E00104336406] of class [ZSERVICE]
NVD000010E [fsm_process ] 12:06:15 [RADCONCT / 00000624] SYSTEM --! Optional adds processed for [ZSERVICE] rc [709]
NVD000010E [fsm_process_upd] 12:06:15 [RADCONCT / 00000624] SYSTEM --! RC [709] after updating children of class [ZMASTER ]
NVD000010E [fsm_process ] 12:06:15 [RADCONCT / 00000624] SYSTEM --! Optional updates processed for [ZMASTER ] rc [709]
NVD000010E [zstate_machine ] 12:06:15 [RADCONCT / 00000624] SYSTEM --! Processing failed for [ZMASTER ] rc[709]
NVD000010E [zstate_machine ] 12:06:15 [RADCONCT / 00000624] SYSTEM --! Error : <This application failed to install correctly. Please contact your system administrator for assistance.>
NVD111111V [state_machine_p] 12:06:15 [RADCONCT / 00000624] SYSTEM --- END STATE MACHINE RC [709]
Answered 10/08/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
I know diddly about Radia but reading the log above, it seems to me that some process failed to create the folder 'c:\RadiaMsiAip\AC76BA86-1033-F400-7760-000000000004'
Answered 10/09/2008 by: VBScab
Red Belt

Please log in to comment
0
Sounds like a problem with publishing up the files tbh, go with a "Basic" mode publish, avoiding advanced, and confirm that this will allow you to publish and deploy the complete package.

As all this does is use msiexec via Radia I would think it should work, but at least its worth a try for confirmation.

Looking through the log files its looking to find the MSI in the c:\RadiaMsiAip\AC76BA86-1033-F400-7760-000000000004\ directory and failing to do so which suggests that as stated above the files aint comming down from Radia. Can you confirm what ZCreate method you have?

Incidently do you see the files under the AIP in Radia System Explorer when browsing the ZService and package, on the ZService that fails?

P
Answered 10/09/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
FYI tried using the basic and everything looked good, created the package and policied it to a packaging machine, ran the connect and it downloaded some files then nothing happened, checked the lib folder and the package was there and inside was the acrostan.msi and the mst but it wasnt installed. run a manual cmd prompt to point to it and install it and everything installed ok

Regarding the tmp file i was talking about earlier in the thread it turns out to be the original msi not the acrostan.msi in the folder which is smaller than the original hmmm
Answered 10/09/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
the connect and it downloaded some files then nothing happenedwhat does your ZCREATE look like?
Answered 10/09/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
My ZCreate service says RadisMSI /i
Answered 10/12/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
On a basic mode install that "WONT" work as a ZCreate method, of course on a normal installation, advanced publish, it should work.

Drilling down to the AIP on the Package, can you see all the files etc listed as expected?
Answered 10/14/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
I Did see the files,

I have decided to delete all the files and packages and start again using the publisher i have set an AIP as c:\temp\adobe with delete aip when publishing complete and connect aip package to service.

Ticked the transform.mst and clicked next

Then the Adobe Acrobat App Launches
Specify a network location for the server image of the product.
c:\temp\adobe is set as default.

this extracts a few files and folders and then renames them:
common
common~1
system32
progra~1
acrostan.msi
etc
but no MST

Then publisher moves on to part 3 package info
so i give it a name adobe_acrobat_09_01
then asks to create service info again use the same info
Name and display name, Assignment type and management set to auto

Then goes to step 4 Summary ready to publish

click publish and it starts to copy all the files from c:\temp\adobe to radia.

Click Finish

It then deletes all the files from c:\temp\adobe

In system explorer i now have a Application ZService called adobe_acrobat_9_01 with
ZCreate RadiaMSI /i

below the service there is the service again and the service_acp
when expanding the first service it lists the MSI, MST and a msiacp.idx
the next lists all the files that came from the c:\temp\adobe and the third is all the properties

Policy the ZService application to the machine

and did a connect and nothing is installed, checked the lib folder and have a msi.log attached below


MSI (s) (A4:B4) [14:38:19:937]: Transforming table CustomAction.
MSI (s) (A4:B4) [14:38:19:968]: Transforming table Binary.
MSI (s) (A4:6C) [14:38:19:984]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI53.tmp, Entrypoint: Vsn
EmiOrientation: CryptQueryObject failed with 8007007b
EmiOrientation: CryptQueryObject failed with 8007007b
EmiOrientation: Verified that it is NOT a volume binary
MSI (s) (A4!FC) [14:38:20:171]: PROPERTY CHANGE: Adding ESIV property. Its value is '1'.
MSI (s) (A4!FC) [14:38:20:203]: PROPERTY CHANGE: Adding ISX_SERIAL property. Its value is '910187026766140242270689'.
MSI (s) (A4!FC) [14:38:20:234]: PROPERTY CHANGE: Adding ESIVEMULOV property. Its value is '1'.
EmiOrientation: User has entered a volume serial number in a retail build. Rejecting.
MSI (s) (A4!FC) [14:38:20:281]: PROPERTY CHANGE: Deleting ESIVEMULOV property. Its current value is '1'.
MSI (s) (A4!FC) [14:38:20:312]: PROPERTY CHANGE: Deleting ESIV property. Its current value is '1'.
Action ended 14:38:20: CA_UIV. Return value 1.
MSI (s) (A4:B4) [14:38:20:359]: Doing action: SetColorFileToInstall
Action start 14:38:20: SetColorFileToInstall.
MSI (s) (A4:B4) [14:38:20:421]: Transforming table CustomAction.
MSI (s) (A4:B4) [14:38:20:453]: Transforming table Binary.
MSI (s) (A4:C4) [14:38:20:468]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI54.tmp, Entrypoint: SetColorFileToInstall
MSI (s) (A4!F0) [14:38:20:750]: PROPERTY CHANGE: Adding COLOR_CSF_EMULATEACROBAT4 property. Its value is '1'.
ADelRCP: Not existing file to be added=> "COLOR_CSF_EMULATEACROBAT4"
Action ended 14:38:20: SetColorFileToInstall. Return value 1.
MSI (s) (A4:B4) [14:38:20:875]: Doing action: CA_QV
Action start 14:38:20: CA_QV.
MSI (s) (A4:B4) [14:38:20:921]: Transforming table CustomAction.
1016-1000-5526-6056-6048-3314 error.
MSI (s) (A4:B4) [14:38:20:953]: Product: Adobe Acrobat 9 Standard -- xxxx-xxxx-xxxx-xxxx error.
Action ended 14:38:20: CA_QV. Return value 3.
MSI (s) (A4:B4) [14:38:21:000]: Transforming table InstallExecuteSequence.
Action ended 14:38:21: INSTALL. Return value 3.


The software installs ok if i enter the serial normally but lookin at this it didnt like it? is it "User has entered a volume serial number in a retail build. Rejecting.
MSI"
Answered 10/14/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
however with the files that are created using the network install point i can use the command line msiexec /i acrostan.msi transforms=acrostan.mst and it installs fine so i cant see how its the licence like it states above in the log?
Answered 10/14/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
i gave up & went with a basic publish & just ran a .cmd file to install. If you ever find out what the license problem is/was, please post the solution if any. I am done with Adobe for now (however short-lived).
Answered 10/14/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
Hey guys,

Im new to this forum, I have it working in radia 3.2, I also had it working in radia 5 I simply selected extra files in the advanced publishing stage and it used it when installing.. Not sure if radia 4.0 has that capability..

I have an AIP that will work (you need to create a new MST file), I have also posted a fix here on the HP forums.. Still testing but im pretty sure this meathod works..
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1272468

cheers
Craig
Answered 10/14/2008 by: wcraig
Yellow Belt

Please log in to comment
0
Extra files bit select that Asnv.tmp file otherwise known as a the hidden original MSI that is first extracted from the installer... :-)
Answered 10/14/2008 by: wcraig
Yellow Belt

Please log in to comment
0
No offence, but did you want to try again but this time in English? As it stands, your post makes no sense whatsoever.
Answered 10/15/2008 by: VBScab
Red Belt

Please log in to comment
0
Sorry to hear it didnt work craig! i'll keep plugging away at it here
Answered 10/15/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
when going through my instructions above it didnt work, but i had a reason to manually install the software for a short period of time, then unpoilcied the adobe software as it didnt work and it removed adobe? tried again and the package fails, carried out another manual install and sent a connect about 15 minutes later it finished and looks like it ran a repair? very odd!!
Answered 10/16/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
Hi all,

When surfing the log file, created by radia, we all know that it is showing the error as,

Action start 11:25:57: CA_UIV.
EmiOrientation: CryptQueryObject failed with 8007007b
EmiOrientation: CryptQueryObject failed with 8007007b
MSI (s) (88!D4) [11:25:58:295]: PROPERTY CHANGE: Adding ESIV property. Its value is '1'.
MSI (s) (88!D4) [11:25:58:295]: PROPERTY CHANGE: Adding ISX_SERIAL property. Its value is '910181756285480758958076'.
MSI (s) (88!D4) [11:25:58:295]: PROPERTY CHANGE: Adding ESIVEMULOV property. Its value is '1'.
EmiOrientation: Verified that it is NOT a volume binary
MSI (s) (88!D4) [11:25:58:327]: PROPERTY CHANGE: Deleting ESIVEMULOV property. Its current value is '1'.
MSI (s) (88!D4) [11:25:58:327]: PROPERTY CHANGE: Deleting ESIV property. Its current value is '1'.
EmiOrientation: User has entered a volume serial number in a retail build. Rejecting.

so, from some custom action it is getting the information whether it is volume or retail build. May be that custom action is "IsVolumeBuild". Because, in log file, it is failed at this point.

Action start 11:25:54: IsVolumeBuild.
EmiOrientation: CryptQueryObject failed with 8007007b
EmiOrientation: CryptQueryObject failed with 80070002
EmiOrientation: Verified that it is NOT a volume binary.


What is this "CryptQueryObject"?
Whether the volume or retail build is checking here?
Answered 10/20/2008 by: laxmikumaris
Senior Yellow Belt

Please log in to comment
0
Ive just read this topic quickly as I m looking for another Radia Problem, just thoufht I would add this

I had this problem 3 years ago

Create your admin point with msiexec /a {msi} transforms={mst} SHORTFILENAMES=TRUE TARGETDIR="C:\AIP\ADOBE" /qb

Once created COPY your mst to the admin point ( c:\aip\adobe)

Use the Basic Publisher in Radia not the Advanced Publisher in Refwi

Select your MSI file location = your AIP point
Select your MST location = your AIP point

Check Control Point
Set it to the location of your AIP

That should do the trick

The advanced publisher can be a little strange at times, using the basic has fixed my problems in the past.
The Advanced publisher is obviously not picking up your Transform to apply the Licence Key

Other way round is to merge your MST into your MSI using orca and publish that way

Ive done both and both work

Hope this helps
Answered 10/21/2008 by: pmclough
Yellow Belt

Please log in to comment
0
Use the Basic Publisher in Radia not the Advanced Publisher in Refwi

The Advanced publisher is obviously not picking up your Transform to apply the Licence Key
Publishing it using basic defeats the purpose of going through the trouble of creating an AIP, etc as we lose the advantaged extra management that Radia promises hence our frustration. I think most of us have been successful in getting it to work that route.

Actually the transform is being applied fine & the correct license key is presented (deployed with a /qf & all my changes showed up). Th issue seems to be that at some point in the install, a temp MSI is created & it seems that this is what is used to check the license key against (or at least this is what is intimated from the link below)...

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1272468&admit=109447626+1224079979957+28353475
Answered 10/21/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
i agree with kiptek, the transform is applied as it pick out the username and company and even the correct serial number, it just doesnt like the serial, even if you launch the msi from C:\Program Files\Novadigm\Lib\SYSTEM\RADIA\SOFTWARE\ZSERVICE mannually you also get invaild serial number, however if you rename the tmp file to msi you will notice that it is the original Adobe msi from the media and works fine.
Answered 10/23/2008 by: mdlister
Senior Yellow Belt

Please log in to comment
0
Just updated this forum with a word attachment with fairly comprehensive instructions,

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1272468&admit=109447626+1224079979957+28353475

check it out and see how you go..
Answered 10/28/2008 by: wcraig
Yellow Belt

Please log in to comment
0
Hello everybody,

i had the same problem with Acrobat Professional 9.
We're using Radia 4.2.
At the first time i deleted the tmp-file before publishing (who needs tmp-files). And yes, it didn't work.
Then i published WITH the tmp-file as additionell file and it didn't work too.

But then, i thought about the localmsi-driver availible in Radia 4.
I used it and, YES it works!!!!!!!!
Answered 02/17/2009 by: SlayerTOM
Senior Yellow Belt

Please log in to comment
0
Hi SlayerTOM,

I'm also using Radia 4 and we dont have a localmsi-driver installed so can't use that option :(

I run the MSI + MST fine from the network not a problem, then use Radia Adv Publishing to create an AIP and its then it stops working, using the media from the Disk with our volume licence we get an error in the msiverbose.log saying you are using a volume licence with a retail build when it gets to the Custom Action CA_UIV so we went to the Adobe licencing site and downloaded the copy available there, again works fine with MSI and MST now i'm getting further in the custom action where it says User has entered Retail serial number in a retail build Return Action 1

but the lines around are look like they fail

Emiorentation: CrypyQueryObject failed with 8007007b

This has been going on for a while and some have a solution but everything i have tried seems to fail, yeah i could package it up in component mode dump the msi cab and mst but then whats the point of having publisher to manage MSI installations then.

I have also tried to drop the custom action from the msi which installs the software but when it launches it askes to be registered.

I've also had a go at getting radia to create the AIP and then copying in the original MSI over the top before it publishes the files to the server but that also failed.

Any help would be great this has been an on going issue that i pick up and run with and then put down as its so annoying!!
Answered 04/16/2010 by: mdlister
Senior Yellow Belt

Please log in to comment
0
few installations are not handled by Radia properly in that case you may have to use Component select method and run the installation using a script.
Answered 04/16/2010 by: mekaywe
Brown Belt

Please log in to comment
0
ORIGINAL: mdlister

Hi SlayerTOM,

I'm also using Radia 4 and we dont have a localmsi-driver installed so can't use that option :(




Hello!

As far as i know, there is nothing you must install to use the "localmsi-driver".
It is a new feature with Radia 4.2

You can switch it "on" in the RadiaSystemExplorer.
There you find it at the properties of the MSI-File.
The name is "MSIDRIVR" Description "Use local AIP". This must be "Y"
If you open the property you can switch it on at the top.

Hope this helps.
Greetings from Germany to wherever... :-)
Answered 04/22/2010 by: SlayerTOM
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity