Our current user environment is using Java 7 update 45.  We need to get to update 55. However, my normal and simple, java installation is no longer working properly when deployed thru SCCM 2012.  The installation is prompting users with a Interactive Services Detection Error stating the following:

RunDLL: There was a problem starting C:\Program Files (x86)\Java\jre7\bin\\installer.dll.  The specified module could not be found

Where do I begin?  I tried using a task sequence to clean-up old installations but I still receive this error when trying to uninstall version 1.7.45.  Except this time the error is not displayed thru interactive services dialog. I tried performing this on a clean machine and receive this error.  I do not receive this error when I install from command line only SCCM.

Perplexed...and feel like I am wasting a lot of time.

Answer Summary:
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1

I had a very similar issue and below is what I did to resolve the deployment issues I was running into.

 

1.       Download Java 7u55 and extracted the .msi and cab files.

2.       Used ORCA to create a transform file with the customization that my environment needed (see below).

Orca Custom Parameters:

Property

Effect of the Property

Default Value

Custom Value

AUTOUPDATECHECK

Prevent Auto Updates

1

0

IEEXPLORER

Enable Java in Internet Explorer

0

1

JAVAUPDATE

Prevent Auto Updates

1

0

JU

Prevent Auto Updates

1

0

MOZILLA

Enable Java in Plugin based browsers

0

1

EULA

Agree to EULA

0

1

RebootyYesNo

Suppresses Reboot

Yes

No

 

3.       Created a vbscript that:

a.       Forcibly closes IE. 

b.      Uninstalls for Java 7u51 (that’s what we currently have in our environment). 

                                                               i.      Change the product code to match the version for Java 7u45

c.       Forcibly closes IE. 

d.      Install’s Java 7u55

e.      Delete the start menu folder for Java that now gets created under C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Java. 

I forcibly close IE multiple times because of the sleep periods I am running after the uninstall/install.  Some environments will probably not needs this, but I included it because our users could be impatient and open IE during the install. 

 

VBScript:

DIM objFSO

Set objFSO = CreateObject("Scripting.FileSystemObject")

DIM oShell

Set oShell = CreateObject("WScript.Shell")

DIM FolderName

FolderName = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Java"

 

oShell.Run "taskkill /im iexplore.exe /f", , True

WScript.Sleep(2000)

 

oShell.Run "msiexec.exe /x {26A24AE4-039D-4CA4-87B4-2F83217051FF} /qn /norestart", 1, true

WScript.Sleep(30000)

 

oShell.Run "taskkill /im iexplore.exe /f", , True

WScript.Sleep(2000)

 

oShell.Run "msiexec /i jre1.7.0_55.msi TRANSFORMS=Java755.mst /qn", 1, true

WScript.Sleep(30000)

 

objFSO.DeleteFolder(FolderName)

                WScript.Echo 0

 

                                WScript.Quit(0)

 

 

 

 

-Bert

Answered 04/30/2014 by: BeeP
White Belt

  • You know, you might be onto something with the changing of the product code to 45. 45 upgrades without any issues. It's only 51 that has been presenting this problem. Thank you for provided your VBScript as well. A great help when there's tangible code.
  • Thanks for you answer Bert. I've marked yours as the correct answer. The deployment went smooth for the most part.
Please log in to comment

Answers

0

Probably a trivial point but ...

C:\Program Files (x86)\Java\jre7\bin\\installer.dll

contains a double backslash ....

Spartacus

 

Answered 04/28/2014 by: spartacus
Black Belt

  • That is a preset path built within the Java 1.7.51 installer. I had nothing to do with the pathing.
  • Hey Trinity,
    I used the same method, Bert used below, with the msi and editing the table with Orca. I've found this error seems to have something to do with the way the new Java uninstalls previous versions. It appears to be looking for this installer.dll file, which has already been removed. Only seems to be happening to a fraction of my machines (like 100 out of 2000). The fix I've been applying is manually deleting the java folder from the Program Files (x86) directory, then manually reinstalling the nee Java. Perhaps you could script this to avoid the hassle?
Please log in to comment
This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.

0

I had a very similar issue and below is what I did to resolve the deployment issues I was running into.

 

1.       Downloaded Java 7u55 and extracted the .msi and cab files.

2.       Used ORCA to create a transform file with the customizations that my environment needed (see below).

Orca Custom Parameters:

Property

Effect of the Property

Default Value

Custom Value

AUTOUPDATECHECK

Prevent Auto Updates

1

0

IEEXPLORER

Enable Java in Internet Explorer

0

1

JAVAUPDATE

Prevent Auto Updates

1

0

JU

Prevent Auto Updates

1

0

MOZILLA

Enable Java in Plugin based browsers

0

1

EULA

Agree to EULA

0

1

RebootyYesNo

Suppresses Reboot

Yes

No

 

3.       Created a vbscript that:

a.       Forcibly closes IE. 

b.      Uninstalls Java 7u51 (that’s what we currently have in our environment). 

                                                               i.      Change the product code to match the version for Java 7u45

c.       Forcibly closes IE. 

d.      Install’s Java 7u55

e.      Deletes the start menu folder for Java that now gets created under C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Java. 

I forcibly close IE multiple times because of the sleep periods I am running after the uninstall/install.  Some environments will probably not needs this, but I included it because our users tend to be impatient and open IE during the install. 

 

VBScript:

DIM objFSO

Set objFSO = CreateObject("Scripting.FileSystemObject")

DIM oShell

Set oShell = CreateObject("WScript.Shell")

DIM FolderName

FolderName = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Java"

 

oShell.Run "taskkill /im iexplore.exe /f", , True

WScript.Sleep(2000)

 

oShell.Run "msiexec.exe /x {26A24AE4-039D-4CA4-87B4-2F83217051FF} /qn /norestart", 1, true

WScript.Sleep(30000)

 

oShell.Run "taskkill /im iexplore.exe /f", , True

WScript.Sleep(2000)

 

oShell.Run "msiexec /i jre1.7.0_55.msi TRANSFORMS=Java755.mst /qn", 1, true

WScript.Sleep(30000)

 

objFSO.DeleteFolder(FolderName)

                WScript.Echo 0

 

                                WScript.Quit(0)

 

 

 

 

-BP

Answered 04/30/2014 by: BeeP
White Belt

Please log in to comment
0

if it works with command line but not through SCCM that means it`s a writes issue.  I`ve had a similar issue in the past.  The way i got around it is to create a task sequence with a comand line task, and on this command line task you have the option to specify an administrator account and password.  Give it a try and let me know if that works for you.

Answered 04/25/2014 by: KevinViolette
Fourth Degree Black Belt

  • Testing scenario 1: Updated from Java 7 Update 7 to Java 7 Update 55 using AppStore Allowed install and SCCM Required install. Both tests were successful without receiving the error stated above.
    • The Java installer is a pile of s*, well version 1.6 was anyway. I havent deployed 1.7 so I dont know if it has gotten better.

      http://www.itninja.com/question/java-1-6u30

      I would suggest you do a Beyond Compare between a working Java install and broken SCCM java upgrade. I suspect the installer fubared some files whilst trying to upgrade - the files it prob needed to do a cleanup or whatever.

      But before that, best thing to do is check the MSI logging, that will paint a better picture of whats going on.
Please log in to comment
Answer this question or Comment on this question for clarity