Jump to content


  • 0
mighty82

HELP! "This installation package could not be opened."

Question

Hi,

i have a problem with install a setup.exe from the sccm to a windows 7 client 64bit.

i create a new package in sccm (sccm is update from sms 2003 to sccm 2007r3)

after the package i create the program and select the java.jre.6u20-32bit.exe

 

ok now i distribute the software package for all windows 7 64bit clients. (java 32bit version is run successfully if i download manually)

 

but from the dp (run advertised programs) i see follow error...

 

"This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid windows installer package."

 

why i have this problem!!! if i download the same exe manually so its work on the same client!!! why not over the sccm!!

 

Plese help me.

 

see Attachment

 

Thanks!

post-7267-0-47261100-1298278651_thumb.jpg

Share this post


Link to post
Share on other sites

9 answers to this question

Recommended Posts

  • 0

can you look at execmgr.log ,CAS.log for errors ?

Check the version on DP and version on the client running ? Is it set to "Download and Execute" or "Run from Distribution Point"?

Try updating the package to DP and try to run it again .

 

 

Hi,

 

DP Update i have maked now. but where is the log files?!?!

on the path sms\log i doesnt find the logfiles... (INFO I Updated from SMS 2003 to SCCM 2007R3)

 

I have actually the Problem...

it is a windows 7 problem?!?! security?!?! what ever....

The SCCM Advanced Client Version is the same. I Push the Client installation from the server to all clients.

Some another software runs perfectly.. but this java setup.exe not.. why!?

 

 

 

thx

Share this post


Link to post
Share on other sites

  • 0

logs can be found the SCCM client C:\windows\system32\ccm\logs on x86 and c:\windows\syswow64\ccm\logs on x64 .

what hapepns when you run the java setup.exe manually ? does it works then ?

 

Hi,

yes its work if i start the same exe file from a local client...!!

i dont no why is not work when i distribute the package....

 

 

but if i start the same package on a xp client, there is work fine!

 

It is a Windows 7 Security?!?!

 

greetz

Share this post


Link to post
Share on other sites

  • 0

Hi,

yes its work if i start the same exe file from a local client...!!

i dont no why is not work when i distribute the package....

 

 

but if i start the same package on a xp client, there is work fine!

 

It is a Windows 7 Security?!?!

 

greetz

 

can you check if you have set the program to run only specific OS or on All OS types ?

can you post the program command line syntax?

Share this post


Link to post
Share on other sites

  • 0

Have you tried extracting the .MSI from the setup.exe file and using that instead?

 

1. Obtain the Offline Source file .EXE from http://www.java.com/en/download/manual.jsp.

(Don't forget to Unblock the downloaded .EXE files.)

2. Navigate to the logged in user's Application Data folder (for example: C:\Documents and Settings\JoeUser\Application Data or C:\Users\JoeUser\AppData\LocalLow).

3. Launch the downloaded .EXE installation file, but do NOT install the program (just leave it running at the initial installation window).

4. Copy ALL the files from the "...\Sun\Java\XXXX" folder containing the extracted contents of the downloaded .EXE file to another location.

5. Cancel the installation setup.

Share this post


Link to post
Share on other sites

  • 0

Have you tried extracting the .MSI from the setup.exe file and using that instead?

 

1. Obtain the Offline Source file .EXE from http://www.java.com/en/download/manual.jsp.

(Don't forget to Unblock the downloaded .EXE files.)

2. Navigate to the logged in user's Application Data folder (for example: C:\Documents and Settings\JoeUser\Application Data or C:\Users\JoeUser\AppData\LocalLow).

3. Launch the downloaded .EXE installation file, but do NOT install the program (just leave it running at the initial installation window).

4. Copy ALL the files from the "...\Sun\Java\XXXX" folder containing the extracted contents of the downloaded .EXE file to another location.

5. Cancel the installation setup.

 

 

Yes i have extract the setup file and use the msi.

but why this error come...

 

Must i have change a special konfig or property on my windows 7 clients?!?! or on the sccm server....

 

 

thx for the reply

Share this post


Link to post
Share on other sites

  • 0

hi,

 

so now i have a new problem with deploy a application (only setup.exe) over the sccm.

we need to install the bizagi process modeler tool.

 

i download the setup.exe file. i create a new package and insert as program the setup.exe file.

after this i distribute the software to all windows workstations.

 

on the windows xp clients work fine but on the windows 7 prof client its not work.... :-(

 

see attachemend for the error

 

if i start manual the setup.exe file from the sccm its ok and i can install this.. but oder the sccm not..

why???

 

i have other problems with the java.jre.exe and now with the exe file from a another application...

should be check a specified config on the sccm to the windows 7 clients... or should be check a config from the windows 7 client to work better with sccm 2007...

 

 

please help....

 

 

thx

post-7267-0-03001800-1304661352_thumb.jpg

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.