Hi,

When I try to do a admin install at the server to be able to deploy the package over the network I get this error message:

"Error 1311.Source file not found(cabinet): D:\CA\DSM\SD\ASM\LIBRARY\activate\BED37160-3221-4756-B2E6-FBFE4532E9A1.itm\1.vol\Help_ko.cab. Verify that the file exists and that you can access it."

It I take a look in the CAB file the file istent there.
If I take a look at the original source of files (before I copy it to the server) the file isent there either. But when I install the file via the CMD (msiexec /i spss.msi TRANSFORMS=mytransform.mst /qb) it installs OK. So then it dont want the file??

Anyone that can help me with what actions I will take to make this to work?

Thanks in advanced!!
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
You don't necessarily *have* to do an admin install, simply to get a network-ready package. Creating an AIP is a good way to extract all the files within a package but, if you prepare a transform with your target's likely feature choices (or a set of transforms, each with a different set of feature choices), you don't need much else.

As to why the admin install points to non-existent files in a CAB...is this a captured MSI?
Answered 05/09/2009 by: VBScab
Red Belt

Please log in to comment
0
Those files can be found on the SPSS Statistics 17.0 Disk 2.

The patch for 17.0.1 is a joke though. It is a standalone msi, all components set to leave installed on uninstall and the run registry key contains the uninstallstring for this same msi! I double checked but it didn't say Adobe SPSS...
Answered 05/11/2009 by: pgiesbergen
Orange Belt

Please log in to comment
0
I double checked but it didn't say Adobe SPSS...My belly laugh for the day. Thank you, Patrick! :)
Answered 05/11/2009 by: VBScab
Red Belt

Please log in to comment
0
Well the sad thing is that I have to do an admin install of the package to be able to push it out with our tool (CA Unicenter Software Delivery)
If I dont to the admin install at the CA server first the package will crash when I try to deploy it.
Answered 05/12/2009 by: aXz
Blue Belt

Please log in to comment
0
Although direct editing of vendor MSIs is to be discouraged, have you tried making a copy of it (so that you have a fall-back) and using Orca to alter the WordCount property to fool the CA tool into believing it's an admin image? Remember that WordCount is in the Summary stream, not the Property table.
Answered 05/12/2009 by: VBScab
Red Belt

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