Discussion Forums/PDQ Deploy/Questions
Answered
Java update 27 (file rights issue)
Chris
asked this on September 20, 2011 08:40
I have created an install for Java 6 update 27 using PDQDeploy and silent install of java 6 update 25 instructions(http://support.adminarsenal.com/entries/20140308-silent-install-of-...) as a template.
The account that is being used for authentication is the "current account". The rights on the share is Change(RWED) for everyone. The directory rights has everyone at Read and execute. The "current user" can browse to the file to add it to the install. But I still get the error I am receiving is "Installer file can not be opened".
Comments
Hi Chris, what version of PDQ Deploy are you using? Will you please export the installer and attach it here, or you may also send to support@adminarsenal.com.
Thanks!
PDQ Deploy 1.2 r7. The installer that I am uploading has been "Duplicated" and had the server name changed to protect the internal infrastructure where it is being used. Other than that it is the exact installer (and relative server path, etc...) that I am using.
Any ideas?
Sorry for the delay Chris. We noticed some issues with the downloaded version of update 27 from Oracle that are separate from your issues. What OS is your console machine (where PDQ Deploy is installed)? What OS are you attempting to push to (targets). (XP, Vista, Win7)?
Thanks
Win7 on both Push and client machines. Install share is on a Server 2008 box.
Hi Chris, your installer checked out great in our lab (Win7 console > Win7 target with media on Server 2008 R2). (see attached image on our share perms)
Let's move our focus to your share perms. There are two tests that we can run.
1) Please choose a target machine that you were attempting to deploy Java to, and from that machine the same logon that you used for the PDQ push, are you able to access the share?
2) From PDQ Deploy, after you select the targets to push to, select the tab on the left that says "Authentication" and enter an administrative user/password. I'd be curious to see if that worked.
Please let us know what you find. We're standing by to assist.
User x logged into target deploy machine and was able to browse the path where the msi was loacated. Double clicked the MSI and was greeted with a UAC dialog. Would UAC be a hinderance for a deployment? If so, how can I bypass UAC only for a push.
You will need to use the "other user" option and provide a user name and password. Using the "current user" option has some issues with UAC.
Just retried with the same user I have been user, but placed the same creds in the 'other users' area, and it failed with the same error('unable to open installer file').
Chris,
1) does this user have admin rights on the target?
2) With this user can you whack into the share and manually start the installer?
It sounds like we're still having a rights issue here. I know that your PDQ Installer file is setup correctly. We'll get it straightened out.
Yes, the user has AD DA privs, I did move onto another machine(as I allowed the msi installer to run manually on the previous test system). This is the same user as I used on the prev system, so the ability to access the share are the same. This is even the same user as I ran the msi installer as on the prev system.
I agree that is sounds like rights, I have just exhausted where I know to look. I was hoping the known diff with using 'current user' and 'other user' may have been a place, but it does not appear to be the case here.
Chris, I'm going to open a support ticket under your name/email with our current issues and assign this to Shane to work in the lab. You'll see the ticket info emailed to you shortly. Thanks for your patience.
not ticket email yet.
Added chris.burns@perceptis.com to ticket thread.
Ticket 6138. If you don't see it in your inbox will you please check your spam filter? If it's still not there please let us know. Thanks!
Chris,
It appears that the error is coming from within the MSI installer, and it may be masking another problem. Follow these steps to get a log file:
http://documentation.adminarsenal.com/PDQDeploy/1.1/index.html?msi_logging.htm
The log file should tell us what the root problem is.
Received the update from the helpdesk team, but never received an email containing the url that will allow me to update the ticket.
the log file was blank. included anyway.
Chris,
Can you submit the error using the diagnose link? This will supply some diagnostic information about where the error is occurring, it's possible that this error is happening in a different place when we normally expect.
submitted with ticket number as the body
submitted with ticket number as the body
Thank you, it's definitely an error 1620 which means that the MSI file cannot be opened, usually due to file corruption.
http://www.appdeploy.com/msierrors/detail.asp?id=26
It can mean that the MSI is corrupt, but as the link above shows, it could be that there is a problem with the MSI cache. Can you try to run the MSI manually on one of the computers that's failing? (run it all the way through, it may be failing in the middle of the install)
If it works manually that would eliminate the cache possibility.
Another possibility, which seems remote, is that the file is getting corrupted during the copy to the target computer. This can happen because of anti-virus software, but it doesn't seem too likely.
This can be tested by the following steps:
1. Create a batch file with only a single command: pause
2. Put the batch file in the same directory as the source installer.
3. Deploy the batch file, check the "include all files in directory" box to make sure that the MSI and the batch file are both copied.
4. The batch file won't exit, so it will leave the MSI on the target in C:\Windows\PDQDeploy\exec.
5. Run the MSI file manually on the target computer.
6. Once your done, abort the deployment so that the batch file is killed and the files are cleaned up.
This will tell you if the MSI file is being corrupted during delivery to the target computer.
Install returned successful, there was no DeployPDQ directory in the windows folder. Did a further search(using unc access to the c$ share) on the machine and was not successful in finding anything with PDQ in its name.
I was also not able to see any process with the name of my batch file in the machines process list. So it appears the pause did not take.
I apologize, the pause command doesn't work in the background. You can get the installer to hang by replacing pause with a call to notepad:
%windir%\notepad.exe
The installer will then continue running until it is aborted allowing you to see the java installer file.
end machine test results:
Process
Remotely ran the deployment including the notepad batch file.
ran c:\windows\PDQDeploy\exec\jxpinstall.msi
Java rel 27 installed
Uninstalled Java rel27
killed notepad.exe
unloaded antivirus
created new installer that has the msiexec command that was in the uploaded installed in a batch file.
ran the installer
saw msiexec show up under the system user (stalled- it never went away)
PDQDeploy installer returned 1620 failed.
I then utilized the AppDeploy article to look into the \windows\installer dir. using install date to find the installer, I found 41e94d.msi (This file also showed J2E runtime as the Authors under the Details tab.) I ran this file. It popped up and died.
I created a bat file locally on the machine that used launched the installer with the logging option (msiexec /i c:\windows\installer\41e94d ALLUSERS=1 /q /norestart /log c:\installj2.log)
when I ran this no log file was generated.
Chris,
Something strange is going on with that MSI. Can you send us the jxpinstall.msi file you're using (if you need to I can send you login information for our FTP server). I'd like to try the exact file in our lab to see if we can duplicate this probelm.
sending the FTP info would be fine. Things have been hectic the past few days, so my timeline for response may not be the greatest, but I will get it to you.
I would think sending the FTP data via email would be best.
Thank you for continuing to help.
Hi Chris,
did you get the ftp instructions that were sent out last week? If not, let us know and we will resend them. We'd like to test a deployment with the java installation that you downloaded.