Help! Packaging Adobe Acrobat 4
Hi, I'm trying to package Adobe Acrobat 4.0.5 with InstallShield X Professional Edition. There are a few issues I'm having, but it seems that the main issue right now is that everytime I run the application after I've installed my package, , a window comes up trying to install Acrobat again, sometimes telling me to reboot. This will happen forever in an endless loop, regardless of what account I'm using (user account, or admin account). What could I do to solve this? Any suggestions are greatly appreciated.. thanks!!
0 Comments
[ - ] Hide Comments

so that the conversation will remain readable.
Answer this question
or Comment on this question for clarity
Answers
Hi Legapps,
I assume you've checked out http://www.appdeploy.com/packages/detail.asp?id=337 ?
I'd suggest you look in your event log, it will tell you why the installer is trying to reinstall all the time.
Hope that helps
Rgds
Paul
I assume you've checked out http://www.appdeploy.com/packages/detail.asp?id=337 ?
I'd suggest you look in your event log, it will tell you why the installer is trying to reinstall all the time.
Hope that helps
Rgds
Paul
Please log in to comment
Hi Paul,
Yes I've already read that site you mentioned, but nowone there mentions how to package it with InstallShield - one guy was able to package it with Wise Package Studio though.
I'll check the Event Log and let you know what I find out - I'm assuming you mean Windows Event Viewer right?
Yes I've already read that site you mentioned, but nowone there mentions how to package it with InstallShield - one guy was able to package it with Wise Package Studio though.
I'll check the Event Log and let you know what I find out - I'm assuming you mean Windows Event Viewer right?
Please log in to comment
legapps,
You need to enable verbose logging of the Windows Installer Service. The info is here:
http://itninja.com/question/what-is-pxe?3
You may have:
- captured some temp file as a part of your package
- have a keypath set on some Acrobat file that is dynamic
Craig --<>.
You need to enable verbose logging of the Windows Installer Service. The info is here:
http://itninja.com/question/what-is-pxe?3
You may have:
- captured some temp file as a part of your package
- have a keypath set on some Acrobat file that is dynamic
Craig --<>.
Please log in to comment
craig,
I went to that site, and I'm not sure if I did things right, because I couldn't find any log file when I went to my C:\Windows\TEMP after I installed my package.
Here's what I did : I went to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer in the registry
I created a KEY called "Logging" (to me it looked like it created a subfolder)
I made the value of that to "voicewarmup"
I then installed the msi, and looked in my C:\windows\temp and found nothing..
what do you think went wrong?
I went to that site, and I'm not sure if I did things right, because I couldn't find any log file when I went to my C:\Windows\TEMP after I installed my package.
Here's what I did : I went to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer in the registry
I created a KEY called "Logging" (to me it looked like it created a subfolder)
I made the value of that to "voicewarmup"
I then installed the msi, and looked in my C:\windows\temp and found nothing..
what do you think went wrong?
Please log in to comment
legapps,
You will find the log file in C:\documents and settings\%username%\local settings\temp, where %username% is the login name you used to do your test.
Craig --<>.
You will find the log file in C:\documents and settings\%username%\local settings\temp, where %username% is the login name you used to do your test.
Craig --<>.
Please log in to comment
craig,
I went to that path - C:\documents and settings\%username%\local settings\temp -, and the only thing I found (I was watching it in real time as the msi was installing) is an msi file that appeared in there during the install of the package, then it disappeared when the install was over.
If you look at my previous post where I described what I did with the registry, could you verify that that is correct? I'm not sure if I did the right thing. I created a 'Key' (not string, dword, or any of that other stuff), is that right? And is it right to put 'voicewarmup' as the value? By putting voicewarmup, I believe it should log everything.. right?
I went to that path - C:\documents and settings\%username%\local settings\temp -, and the only thing I found (I was watching it in real time as the msi was installing) is an msi file that appeared in there during the install of the package, then it disappeared when the install was over.
If you look at my previous post where I described what I did with the registry, could you verify that that is correct? I'm not sure if I did the right thing. I created a 'Key' (not string, dword, or any of that other stuff), is that right? And is it right to put 'voicewarmup' as the value? By putting voicewarmup, I believe it should log everything.. right?
Please log in to comment
Check to make sure that you created "logging" as a string value and not a dword value. If you like, you can paste this into a new .reg file and just click on it to make the correct entry:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\installer]
"logging"="voicewarmup"
Craig --<>.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\installer]
"logging"="voicewarmup"
Craig --<>.
Please log in to comment
legapps,
By the size of that log file, it sounds like it is the original one from the initial install of your package. Here is a suggestion to make the log a little easier to examine:
- Empty your temp directory by moving and archiving any log files to another location. I would not delete them since you are troubleshooting; there is always a chance you may want to refer to them.
- Make your source .msi temporarily unavailable by renaming it or its path, then run Acrobat and allow the repair to fail.
This should now create a new log file that is smaller, and one that is easier to search. Open it with any text editor, and do a search for writes and overwrites. You should see failures since the Windows Installer Service will not to complete the repair without access to the source .msi.
I know these log files are not pretty to look at or easy to understand if you have not dealt with them before. Getting familiar and comfortable with them will become increasingly helpful, though, as you package more and more.
Craig --<>.
By the size of that log file, it sounds like it is the original one from the initial install of your package. Here is a suggestion to make the log a little easier to examine:
- Empty your temp directory by moving and archiving any log files to another location. I would not delete them since you are troubleshooting; there is always a chance you may want to refer to them.
- Make your source .msi temporarily unavailable by renaming it or its path, then run Acrobat and allow the repair to fail.
This should now create a new log file that is smaller, and one that is easier to search. Open it with any text editor, and do a search for writes and overwrites. You should see failures since the Windows Installer Service will not to complete the repair without access to the source .msi.
I know these log files are not pretty to look at or easy to understand if you have not dealt with them before. Getting familiar and comfortable with them will become increasingly helpful, though, as you package more and more.
Craig --<>.
Please log in to comment
craig,
Ok, I made the smaller log file as you said (came out to 500KB), and did a search for write and overwrite .. I found some, but I didn't find any info that would help me resolve the problem.. is it easier if I e-mail you the log file? I guess I'm at a loss as to what to do at this point..
I do appreciate all your help!
Ok, I made the smaller log file as you said (came out to 500KB), and did a search for write and overwrite .. I found some, but I didn't find any info that would help me resolve the problem.. is it easier if I e-mail you the log file? I guess I'm at a loss as to what to do at this point..
I do appreciate all your help!
Please log in to comment
Go ahead and send it to me and I will see what I can pick out. I'll post anything definite I see here so that all can reference it.
Craig --<>.
Craig --<>.
Please log in to comment
craig,
sounds good - but I couldn't find your e-mail address! In the window where I can e-mail you from your profile, it doesn't have an option to send attachments. I thought it'd be too huge if I copy & pasted the text into that window, so, do you want to send me your e-mail address? If you prefer not to let it be known publicly, you can e-mail it to me at mirko79 [at] gmail dot com
thanks
sounds good - but I couldn't find your e-mail address! In the window where I can e-mail you from your profile, it doesn't have an option to send attachments. I thought it'd be too huge if I copy & pasted the text into that window, so, do you want to send me your e-mail address? If you prefer not to let it be known publicly, you can e-mail it to me at mirko79 [at] gmail dot com
thanks
Please log in to comment
Comments