Connecting Tech Pros Worldwide Help | Site Map

Launching VB invokes Installshield

  #1  
Old June 27th, 2008, 05:16 PM
Raoul Watson
Guest
 
Posts: n/a
This has happened numerous times in the past and I never can pinpoint what
caused it.
It has to do with Installshield (either a failed software removal or
installation).

When a source code is opened, or VB is launched, the Installshield dialog
comes up
as of it is trying to install a software. It will then err out with a dialog
"The feature you are trying to use is on a CD Rom or other removable
media..Insert
Installshield disk..etc." when you cancel it comes up with "Error 1706: No
valid
source can be found for product Installshield Express.." If you hit cancel
again,
it may take two or three times but eventually VB loads. Running any source
code
may also bring up this dialog..

No one seems to have experienced this weird happening...


  #2  
Old June 27th, 2008, 05:16 PM
Dean Earley
Guest
 
Posts: n/a

re: Launching VB invokes Installshield


Raoul Watson wrote:
Quote:
This has happened numerous times in the past and I never can pinpoint
what caused it. It has to do with Installshield (either a failed
software removal or installation).
>
When a source code is opened, or VB is launched, the Installshield
dialog comes up as of it is trying to install a software. It will
then err out with a dialog "The feature you are trying to use is on a
CD Rom or other removable media..Insert Installshield disk..etc."
when you cancel it comes up with "Error 1706: No valid source can be
found for product Installshield Express.." If you hit cancel again,
it may take two or three times but eventually VB loads. Running any
source code may also bring up this dialog..
>
No one seems to have experienced this weird happening...
As you said, this is normally due to a broken install, and is often
triggered by using the custom controls.

Have a look for the "MSI cleanup utility" and remove the errant install
form the list.

--
Dean Earley (dean.earley@icode.co.uk)
i-Catcher Development Team

iCode Systems
  #3  
Old June 27th, 2008, 05:16 PM
Raoul Watson
Guest
 
Posts: n/a

re: Launching VB invokes Installshield



"Dean Earley" <dean.earley@icode.co.ukwrote in message
news:484cf891$0$2478$da0feed9@news.zen.co.uk...
Quote:
Raoul Watson wrote:
Quote:
>This has happened numerous times in the past and I never can pinpoint
>what caused it. It has to do with Installshield (either a failed
>software removal or installation).
>>
>When a source code is opened, or VB is launched, the Installshield
>dialog comes up as of it is trying to install a software. It will
>then err out with a dialog "The feature you are trying to use is on a
>CD Rom or other removable media..Insert Installshield disk..etc."
>when you cancel it comes up with "Error 1706: No valid source can be
>found for product Installshield Express.." If you hit cancel again, it
>may take two or three times but eventually VB loads. Running any
>source code may also bring up this dialog..
>>
>No one seems to have experienced this weird happening...
>
As you said, this is normally due to a broken install, and is often
triggered by using the custom controls.
>
Have a look for the "MSI cleanup utility" and remove the errant install
form the list.
>
--
Dean Earley (dean.earley@icode.co.uk)
i-Catcher Development Team
>
iCode Systems
Thanks Dean.. I appreciate your advice.
I have looked at this utility but got scared because i don't remember half
the things on my PC... didn't want to get rid of something I need.

I was hoping they would make a version that will scan failed installs in the
regitry 9sopme sort of cross referencer)


  #4  
Old June 27th, 2008, 05:16 PM
Dean Earley
Guest
 
Posts: n/a

re: Launching VB invokes Installshield


Raoul Watson wrote:
Quote:
"Dean Earley" <dean.earley@icode.co.ukwrote in message
news:484cf891$0$2478$da0feed9@news.zen.co.uk...
Quote:
>Raoul Watson wrote:
Quote:
>>This has happened numerous times in the past and I never can pinpoint
>>what caused it. It has to do with Installshield (either a failed
>>software removal or installation).
>>>
>>When a source code is opened, or VB is launched, the Installshield
>>dialog comes up as of it is trying to install a software. It will
>>then err out with a dialog "The feature you are trying to use is on a
>>CD Rom or other removable media..Insert Installshield disk..etc."
>>when you cancel it comes up with "Error 1706: No valid source can be
>>found for product Installshield Express.." If you hit cancel again, it
>>may take two or three times but eventually VB loads. Running any
>>source code may also bring up this dialog..
>>>
>>No one seems to have experienced this weird happening...
>As you said, this is normally due to a broken install, and is often
>triggered by using the custom controls.
>>
>Have a look for the "MSI cleanup utility" and remove the errant install
>form the list.
>>
>--
>Dean Earley (dean.earley@icode.co.uk)
>i-Catcher Development Team
>>
>iCode Systems
>
Thanks Dean.. I appreciate your advice.
I have looked at this utility but got scared because i don't remember half
the things on my PC... didn't want to get rid of something I need.
>
I was hoping they would make a version that will scan failed installs in the
regitry 9sopme sort of cross referencer)
Surely you know what you use?
Normally, the culprit app is the one listed on the "please insert disk"
dialog, in this case, InstallSheild?

You can always reinstall later.

--
Dean Earley (dean.earley@icode.co.uk)
i-Catcher Development Team

iCode Systems
  #5  
Old June 27th, 2008, 05:16 PM
Raoul Watson
Guest
 
Posts: n/a

re: Launching VB invokes Installshield



"Dean Earley" <dean.earley@icode.co.ukwrote in message
news:484e32d4$0$26088$db0fefd9@news.zen.co.uk...

...<snip>
Quote:
>
You can always reinstall later.
>
--
Dean Earley (dean.earley@icode.co.uk)
i-Catcher Development Team
>
iCode Systems
You are absolutely right.

I'll knock 'em off one at a time starting with the most recent installs and
removals (my previous experience indicated InstallShield Express is just
invoked but the failed app is another one)


Closed Thread