Any help or advice would be greatly appreciated.
Posted 09 February 2002 - 01:03
Any help or advice would be greatly appreciated.
Posted 19 February 2002 - 17:57
I also note that my Dr.Watson IDriver failure happens when the InstallShield Wizard, Setup Status, is at 100% and indicating "Setup is performing the requested operations". Is this what you mean by "just before the OnFirstUIAfter event"?
I can trap a similar error during a rare uninstall of the same package which logged "Action ended 14:03:29: INSTALL. Return value 1. DEBUG: Error 2769: Custom Action ISMsiServerStartup did not close 19 MSIHANDLEs. Internal Error 2769. ISMsiServerStartup, 19 Action ended 14:03:29: ISMsiServerStartup. Return value 0.").
I wonder if its one of those cases where a service doesn't quite get long enough to start.
I am still working on this issue, I'll let you know if I have any breakthroughs, please keep me posted as well.
Posted 25 February 2002 - 11:45
Any ideas anyone?
Posted 25 February 2002 - 15:24
Here in America, it appears that Dr. Watson didn't log anything like he says he is doing (in the error dialog). Perhaps you could get a better handle on this (being from England)? Anything in your log when you run drwtsn32? Perhaps you could call in Holmes for some assistance? Any clues might be helpful.
Posted 26 February 2002 - 00:56
This is how I fixed it: I ran the "full validation suite" which, as usual, produced many mostly irrelevant warnings. However, it did note an "invalid feature requirement" [or something like that]. Turned out that a feature had been requiring another feature, which had been renamed/deleted. Amazingly, this had not produced a compile-time warning. Simply going to FEATURES/<FeatureName>/REQUIRED_FEATURES and removing the non-existent requirement fixed the problem.
Then it came back, this time is was an invalid [no longer existing] PARENT entry in the DIRECTORY table. Though ISD7 is supposed to clean up the unused directories, it had left about a dozen behind--removing these entries via the Direct Editor fixed the problem.
Probably not coincidences.
Hope this helps.
Posted 26 February 2002 - 14:39
Seems my installation had simialr problems - a non-existant required feature and some unused entries in the directory table. I ran the full validation suite and sorted out the errors - this seems to fix the problem.
Alex
Posted 26 February 2002 - 22:20
I got 1 error when I ran the full validation suite :
ICE03ErrorInvalid DefaultDir string; Table: Directory, Column: DefaultDir, Key(s): ISYourCompanyDirhttp://dartools/iceman/ice03.htmlDirectoryDefaultDirISYourCompanyDir
Any idea how I would fix this?
Posted 26 February 2002 - 23:18
InstallShield support just informed me that this is due a bug with 7.02:
" This bug is slated to be fixed for a future maintenance release for Dev7. Since we are able to reproduce the error, we should be able to determine a fix, and most likely it will make it in the next MP. However, the fix may take longer and could be released in a later MP. "
They did't have any work-arounds for me to use.
I was forced to revert back to using InstallShield Professional 6.3 for this delivery. To make matters worse InstallShield support charged me 贄 / incident for problems encountered during the emergency work-around since it involved IS Pro. I even talked to the same person who finally determined it was a bug with IS Dev!
(Edited by John Schwab at 5:22 pm on Feb. 26, 2002)
(Edited by John Schwab at 8:18 am on Feb. 27, 2002)
(Edited by John Schwab at 6:41 pm on Feb. 28, 2002)
Posted 08 July 2002 - 13:47
Posted 06 August 2002 - 08:25