Upgrading from Acrobat 7
I am having two problems related to the removal of Acrobat 7 and the subsequent install of Acrobat 9:
>>When I use the CustWiz (v9) and check the boxes to uninstall previous version, I get the log file error where it thinks I have a bad serial number. I have confirm my SN is correct and valid. Anyone have a similar issue and how did you get around it? I am new to the CustWiz and any help is appreciated.
>>When I use the scripted method v7 gets removed but v9 wont install until after a reboot. Is there anyway to avoid the reboot? The logfile error is:
Thanks for the help,
>>When I use the CustWiz (v9) and check the boxes to uninstall previous version, I get the log file error where it thinks I have a bad serial number. I have confirm my SN is correct and valid. Anyone have a similar issue and how did you get around it? I am new to the CustWiz and any help is appreciated.
>>When I use the scripted method v7 gets removed but v9 wont install until after a reboot. Is there anyway to avoid the reboot? The logfile error is:
"MSI (s) (4C:40) [12:31:34:132]: Product: Adobe Acrobat 9 Pro - English, Français, Deutsch -- Acrobat has detected another process which has not yet completed. You need to restart the system in order to complete this process."Thanks for the help,
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
jcarri06
15 years ago
Puma,
What deployment tool are you using? Is the installation using the System account to install or a predefined account? This link explains the issue right now with Adobe 9 and the serial number error.
Good luck,
Jay
What deployment tool are you using? Is the installation using the System account to install or a predefined account? This link explains the issue right now with Adobe 9 and the serial number error.
Good luck,
Jay
Posted by:
pumagaju
15 years ago
We use Altiris for deployments, and I have my script run with AutoIt3. We also use the system account. I will try to run locally and see if that works.
Thanks,
Thanks,
Posted by:
jcarri06
15 years ago
Are you doing "Run Script" or "Install Package"? If you do "Install Package", betcha it works :).
Posted by:
pumagaju
15 years ago
ORIGINAL: jcarri06
Are you doing "Run Script" or "Install Package"? If you do "Install Package", betcha it works :).
Guess I dont know how to tell the difference between the two.
We use Altiris NS. My guess would be Install Package as I dont see anything related to Run Script. If I change the setting to copy local and run under Specified User I get the same results as previous.
Posted by:
pumagaju
15 years ago
The reboot issues stems from the v7 removal. I found this item in the log file:
Dependency Walker shows this file tied into all kinds of OS stuff.
Any one know of a good way to get this file deleted without the reboot?
Info 1903.Scheduling reboot operation: Deleting file C:\Program Files\Adobe\ActiveX\AcroIEHelper.dll
Dependency Walker shows this file tied into all kinds of OS stuff.
Any one know of a good way to get this file deleted without the reboot?
Posted by:
anonymous_9363
15 years ago
I *believe* there's a programmtic way to remove ActiveX objects from IE's clutches, which is what I suspect is going on here.
Adobe's "programmatic" way is clearly to set the file for deletion and reboot. Priceless. But then, we expect nothing less than the sledgehammer approach from this vendor. I'll have a wander and see what I can find.
The first and crucial step is to check if IE is running and, if it is, handle that. I say "handle that" in that bald fashion because some folks like to simply kill processes, others like to pop up a polite request to the user. Your choice. Once IE is closed, we can proceed with the removal of the control from its grasp. Note that, IE windows aren't always visible. You may also want to check for the MSHTA.EXE process, which hosts HTAs. I believe this also use hooks to parts of IE.
The next stage is to unregister the DLL. I can tolerate the use of RegSvr32 in this instance but, I suspect (hope) that Adobe's MSI would do that (sniggers behind hand...)
Now you should be able to delete the file.
Adobe's "programmatic" way is clearly to set the file for deletion and reboot. Priceless. But then, we expect nothing less than the sledgehammer approach from this vendor. I'll have a wander and see what I can find.
The first and crucial step is to check if IE is running and, if it is, handle that. I say "handle that" in that bald fashion because some folks like to simply kill processes, others like to pop up a polite request to the user. Your choice. Once IE is closed, we can proceed with the removal of the control from its grasp. Note that, IE windows aren't always visible. You may also want to check for the MSHTA.EXE process, which hosts HTAs. I believe this also use hooks to parts of IE.
The next stage is to unregister the DLL. I can tolerate the use of RegSvr32 in this instance but, I suspect (hope) that Adobe's MSI would do that (sniggers behind hand...)
Now you should be able to delete the file.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.