PDA

View Full Version : Error 112



NewsArchive
12-03-1997, 01:00 AM
When installing Delphi 3.0, I received an Error 112 warning. By
looking in the Knowledge Base I found out, it means that there is no
TEMP environment variable or that it points to a non-existent
directory. Well I do have a TEMP variable and it points to an existing
directory.
What could be wrong to receive this notice.

NewsArchive
12-03-1997, 01:00 AM
On Wed, 03 Dec 1997 08:33:39 GMT, F.Staal@Getronics.nl (Frank Staal) wrote:
>TEMP environment variable or that it points to a non-existent
>directory. Well I do have a TEMP variable and it points to an existing
>directory.

You might try and scandisk your drive, then run defrag on it to move enough
space together.

You see, although it says that you do have enough space, you don't, because
if the intrinsic problems with FAT allocation. Once you defragment, you
should have enough space available for the installation PLUS an additional
amount in which InstallShield can uncompress its files.

Stefan
ellipse data systems

NewsArchive
01-29-1999, 01:00 AM
Hi there,
I'm not sure. But here is what the user said in the email

"Setup is unable to find installation languages in C:\WINDOWS\TEMP\PFT~1\SETUP.LID
file.

Error 105"

Hope this helps. Thanks.
-----------------------------------------------------------------------------
InstallShield Software Corporation wrote:

> On Thu, 28 Jan 1999 15:34:19 -0800, Senan Yang <senan@hehe.com> wrote:
> > A user of my program uses Swedish Windows95 and when he tries to
> >install my program he gets error 105. What is that? How can I solve it? Thanks.
>
> Where does the error occur?
>
> Stefan Paetow
> InstallShield Software Corporation

NewsArchive
01-29-1999, 01:00 AM
Hi there,
I use the version comes with VC++6. It seems only to have English
support.
How do I get other support for other languages? Thanks
-------------------------------------------------------------------------------

Stefan Krueger wrote:

> Hi,
>
> which version of InstallShield are you using, maybe an international? Is
> support for Swedish included in your setup?
>
> Stefan Krueger
> Independent Setup Consultant
>
> // InstallSite - Resources for setup developers
> // http://www.installsite.org (primary site - USA)
> // http://installsite.sw.com.sg (mirror site - Singapore)
>
> My reply-to address is invalid to avoid spam.
> If you are looking for individual assistance,
> like e-mail support, please mail to
> contract@installsite.org for support options.
>
> Senan Yang schrieb in Nachricht <36B0F3FA.2ECD848B@hehe.com>...
> >Hi there,
> > A user of my program uses Swedish Windows95 and when he tries to
> >install my
> >program he gets error 105. What is that? How can I solve it? Thanks.
> >

NewsArchive
01-30-1999, 01:00 AM
Hi,

you should be able to run your English setup on Swedish Windows. If you want
to display your setup dialogs in Swedish, you'd have to upgrade to
InstallShield International West.

Stefan Krueger
Independent Setup Consultant

NEU: Deutschsprachiges Forum auf InstallSite

// InstallSite - Resources for setup developers
// http://www.installsite.org (primary site - USA)
// http://installsite.sw.com.sg (mirror site - Singapore)

My reply-to address is invalid to avoid spam.
If you are looking for individual assistance,
like e-mail support, please mail to
contract@installsite.org for support options.

Senan Yang schrieb in Nachricht <36B24B7E.A1F59F43@hehe.com>...
>Hi there,
> I use the version comes with VC++6. It seems only to have English
>support.
>How do I get other support for other languages? Thanks
>---------------------------------------------------------------------------
----
>
>Stefan Krueger wrote:
>
>> Hi,
>>
>> which version of InstallShield are you using, maybe an international? Is
>> support for Swedish included in your setup?
>>
>> Stefan Krueger
>> Independent Setup Consultant
>>
>> // InstallSite - Resources for setup developers
>> // http://www.installsite.org (primary site - USA)
>> // http://installsite.sw.com.sg (mirror site - Singapore)
>>
>> My reply-to address is invalid to avoid spam.
>> If you are looking for individual assistance,
>> like e-mail support, please mail to
>> contract@installsite.org for support options.
>>
>> Senan Yang schrieb in Nachricht <36B0F3FA.2ECD848B@hehe.com>...
>> >Hi there,
>> > A user of my program uses Swedish Windows95 and when he tries to
>> >install my
>> >program he gets error 105. What is that? How can I solve it? Thanks.
>> >
>

NewsArchive
10-29-1999, 12:00 AM
Hello Jim,

I delete the Driver and LastUser attribute from the data source component
and get the same error.

Thanks for your help,
Stephan Schmitz


Jim Kang <?@installshield.com> schrieb in im Newsbeitrag:
381641b7.0@news.installshield.com...
> In article <3815cbfa.0@news.installshield.com>, "Stephan Schmitz"
<sschmitz@adiscon.com> wrote:
> > Hello,
> >
> > I want to install a ODBC Resource (System DSN) and get the Error "Error
> > 1919.Error configuring ODBC data source xyz, ODBC error 8 Verify that
the
> > file xyz exists and you can access it." during Installation. The ODBC
> > Recource is for SQL-Server was created with the Component Wizard. On the
> > target machine there is a SQL-Server with the database und the required
> > user. I can create the ODBC Resource manually on the target machine.
>
> The Component Wizard generally extracts the Driver as an attribute, and
the
> ODBC manager does not like this as an attribute for SQL Server resources.
Just
> delete the Driver attribute for this data source component. you should do
the
> same for the LastUser attribute if it exists for this component.
>
> ----
>
> Jim Kang - Developer Support Engineer
> InstallShield Software Corporation
>

NewsArchive
11-02-1999, 01:00 AM
In article <381991a4.0@news.installshield.com>, "Stephan Schmitz" <sschmitz@adiscon.com> wrote:
> Hello Jim,
>
> I delete the Driver and LastUser attribute from the data source component
> and get the same error.

Stephan,

Try deleting other attributes, build, then running iteratively until you
discover the attribute that causes the error.

> Jim Kang <?@installshield.com> schrieb in im Newsbeitrag:
> 381641b7.0@news.installshield.com...
> > In article <3815cbfa.0@news.installshield.com>, "Stephan Schmitz"
> <sschmitz@adiscon.com> wrote:
> > > Hello,
> > >
> > > I want to install a ODBC Resource (System DSN) and get the Error "Error
> > > 1919.Error configuring ODBC data source xyz, ODBC error 8 Verify that
> the
> > > file xyz exists and you can access it." during Installation. The ODBC
> > > Recource is for SQL-Server was created with the Component Wizard. On the
> > > target machine there is a SQL-Server with the database und the required
> > > user. I can create the ODBC Resource manually on the target machine.
> >
> > The Component Wizard generally extracts the Driver as an attribute, and
> the
> > ODBC manager does not like this as an attribute for SQL Server resources.
> Just
> > delete the Driver attribute for this data source component. you should do
> the
> > same for the LastUser attribute if it exists for this component.
> >
> > ----
> >
> > Jim Kang - Developer Support Engineer
> > InstallShield Software Corporation
> >
>
>

----

Jim Kang - Developer Support Engineer
InstallShield Software Corporation

NewsArchive
11-11-1999, 01:00 AM
Thank you for your answer!

But the error still appears if the customer copies all files to his
harddrive - and in the meantime there is an second customer who reported
this error (until now we sold the program with this installation about 500
times but there are only this two appearence of the described error)!

Bernhard Reichl

--
Bernhard Reichl
wrote:
> > A customer of us get the error 1606 ("Could not access network location
> > ....\") on a Windows 98 system with no network connection if he starts
the
> > installation. Did anybody know the reason for this error?
>
> That comes up when it fails to access a local resource, also. This means
that
> the source media, drive, or folder is not accessible to the installer
service.
>
> ----
>
> Jim Kang - Developer Support Engineer
> InstallShield Software Corporation
>

NewsArchive
12-18-1999, 01:00 AM
In article <385a8b68.0@news.installshield.com>, "Eric Liu" <eliu@wquinn.com> wrote:
> The exact error message is:
> "Error 1926 Could not set file security for file C:\Config.msi\.
> Error: 123. Verify that you have sufficient priviliges to modify the
> security permissions for this file."
> The Config.msi seems like a tempory directory, there is a file in the
> directory. When I click OK, this directory is removed.

Where in the install process does this show up?
What do the permissions for that folder look like? Does this happen
consistently, and what target platform is it?

----

Jim Kang - Developer Support Engineer
InstallShield Software Corporation

NewsArchive
12-20-1999, 01:00 AM
Hi jim,

This happened only on one machine right now. The machine is NT 4.00.1381,
IE4.0 4.72.3110.8.
The error message show up at "status: Copying new files". I looked the
property of the directory Config.Msi, the permission check boxed are all
unchecked. There is a file named "e69f50f.rbs" under the directory
Config.Msi.
Thanks

Eric

Jim Kang <?@installshield.com> wrote in message
news:385ae558.0@news.installshield.com...
> In article <385a8b68.0@news.installshield.com>, "Eric Liu"
<eliu@wquinn.com> wrote:
> > The exact error message is:
> > "Error 1926 Could not set file security for file C:\Config.msi\.
> > Error: 123. Verify that you have sufficient priviliges to modify the
> > security permissions for this file."
> > The Config.msi seems like a tempory directory, there is a file in the
> > directory. When I click OK, this directory is removed.
>
> Where in the install process does this show up?
> What do the permissions for that folder look like? Does this happen
> consistently, and what target platform is it?
>
> ----
>
> Jim Kang - Developer Support Engineer
> InstallShield Software Corporation
>

NewsArchive
12-20-1999, 01:00 AM
Eric,

Try running:

msizap t {product code of your project}

Do this for every project you've wokred on and run. Msizap comes with the
Windows Installer SDK. It clears away internally stored Windows Installer
information.

In article <385e6443.0@news.installshield.com>, "Eric Liu" <eliu@wquinn.com>
wrote:
> Hi jim,
>
> This happened only on one machine right now. The machine is NT 4.00.1381,
> IE4.0 4.72.3110.8.
> The error message show up at "status: Copying new files". I looked the
> property of the directory Config.Msi, the permission check boxed are all
> unchecked. There is a file named "e69f50f.rbs" under the directory
> Config.Msi.
> Thanks
>
> Eric
>
> Jim Kang <?@installshield.com> wrote in message
> news:385ae558.0@news.installshield.com...
> > In article <385a8b68.0@news.installshield.com>, "Eric Liu"
> <eliu@wquinn.com> wrote:
> > > The exact error message is:
> > > "Error 1926 Could not set file security for file C:\Config.msi\.
> > > Error: 123. Verify that you have sufficient priviliges to modify the
> > > security permissions for this file."
> > > The Config.msi seems like a tempory directory, there is a file in the
> > > directory. When I click OK, this directory is removed.
> >
> > Where in the install process does this show up?
> > What do the permissions for that folder look like? Does this happen
> > consistently, and what target platform is it?
> >
> > ----
> >
> > Jim Kang - Developer Support Engineer
> > InstallShield Software Corporation
> >
>
>

----

Jim Kang - Developer Support Engineer
InstallShield Software Corporation

NewsArchive
12-20-1999, 01:00 AM
Jim,
I have tried
msizap * ALLPRODUCT
to remove all product. Still get the same error.

Eric

Jim Kang <?@installshield.com> wrote in message
news:385e667b.0@news.installshield.com...
> Eric,
>
> Try running:
>
> msizap t {product code of your project}
>
> Do this for every project you've wokred on and run. Msizap comes with the
> Windows Installer SDK. It clears away internally stored Windows Installer
> information.
>
> In article <385e6443.0@news.installshield.com>, "Eric Liu"
<eliu@wquinn.com>
> wrote:
> > Hi jim,
> >
> > This happened only on one machine right now. The machine is NT
4.00.1381,
> > IE4.0 4.72.3110.8.
> > The error message show up at "status: Copying new files". I looked the
> > property of the directory Config.Msi, the permission check boxed are all
> > unchecked. There is a file named "e69f50f.rbs" under the directory
> > Config.Msi.
> > Thanks
> >
> > Eric
> >
> > Jim Kang <?@installshield.com> wrote in message
> > news:385ae558.0@news.installshield.com...
> > > In article <385a8b68.0@news.installshield.com>, "Eric Liu"
> > <eliu@wquinn.com> wrote:
> > > > The exact error message is:
> > > > "Error 1926 Could not set file security for file C:\Config.msi\.
> > > > Error: 123. Verify that you have sufficient priviliges to modify
the
> > > > security permissions for this file."
> > > > The Config.msi seems like a tempory directory, there is a file in
the
> > > > directory. When I click OK, this directory is removed.
> > >
> > > Where in the install process does this show up?
> > > What do the permissions for that folder look like? Does this happen
> > > consistently, and what target platform is it?
> > >
> > > ----
> > >
> > > Jim Kang - Developer Support Engineer
> > > InstallShield Software Corporation
> > >
> >
> >
>
> ----
>
> Jim Kang - Developer Support Engineer
> InstallShield Software Corporation
>

NewsArchive
06-22-2000, 12:00 AM

NewsArchive
08-21-2000, 12:00 AM
C.J,

Make sure that there are only numbers aa.bb.cccc in the ProductVersion field
of the General window.

Michael J Steiner

C. J. Reddy <c.j.reddy@larc.nasa.gov> wrote in message
news:3990253F.FCF213DC@larc.nasa.gov...
>
> As a followup, I encountered this problem on Win 98 also.
> More over on Win 98, It did not copy the executable of
> my application to install directory (where it should
> be copying). Is there a way it can be fixed ??
>
> I appreciate any help.
>
> Thanks
>
> C.J. Reddy
>
> "C. J. Reddy" wrote:
> >
> > I am building the setup of my application using
> > InstallShield Express 3.1. When I try to install
> > the program on Win NT4/2000. I get the following
> > error:
> >
> > Error 1406: Could not write value VersionMinor
> > to key HKEY_LOCAL_MACHINE\Software\Microsoft\
> > Windows\CurrentVersion\Uninstall\{......}
> > Verify that yo uhave sufficient access to that
> > key, or contact your support personnel.
> >
> > I am installing as Administrator and I click
> > on 'Ignore', the set up proceeds normally.
> > Though it of no consequence in my application
> > as I do not need to change any registry entries
> > I would like to get around this by skipping the
> > 'registering the product' step in the installation,
> >
> > I am new to using InstallShield and alo to the
> > issues related to Registry. I appreciate if
> > some can let me know how to get around this.
> >
> > Thanks
> >
> > C.J. Reddy

NewsArchive
09-26-2000, 12:00 AM
Yes, I meant a dynamic file link.

I changed the media to "Compressed" and then the problem went away. It only
happens if I don't select "compressed"

David

NewsArchive
10-26-2000, 12:00 AM
But why does my operating system with 2.01 installed have an older version of
Windows Installer? Shouldn't IPWI have installed the new one?

Einar Onsum wrote:

> In step 5, in IPWI 2.01, at the bottom of the "Releases" pane, you can
> suppress this warning. Set "Suppress Launcher Warning" to "Yes".
>
> Einar
>
> "Daren Burke" <burked@rd.simplexnet.com> wrote in message
> news:39F80B6B.44276C0B@rd.simplexnet.com...
> > I just created a new installation with 2.01 and when I try to run it, I
> > get error 1207. The message says something about this is an older
> > version of Windows Installer. How can I fix this?
> >
> > thanks,
> >

NewsArchive
10-26-2000, 12:00 AM
I assume you saw the error on Windows 2000. Windows 2000 includes Windows
Installer 1.1 as a system component that cannot be updated via instmsi.exe.
Windows 2000 will not have Windows Installer 1.2 until it is included in a
Windows 2000 service pack.

--
Art Middlekauff
InstallShield Software Corporation

--------------


Daren Burke wrote in message <39F851CB.A886611@rd.simplexnet.com>...
>But why does my operating system with 2.01 installed have an older version
of
>Windows Installer? Shouldn't IPWI have installed the new one?
>
>Einar Onsum wrote:
>
>> In step 5, in IPWI 2.01, at the bottom of the "Releases" pane, you can
>> suppress this warning. Set "Suppress Launcher Warning" to "Yes".
>>
>> Einar
>>
>> "Daren Burke" <burked@rd.simplexnet.com> wrote in message
>> news:39F80B6B.44276C0B@rd.simplexnet.com...
>> > I just created a new installation with 2.01 and when I try to run it, I
>> > get error 1207. The message says something about this is an older
>> > version of Windows Installer. How can I fix this?
>> >
>> > thanks,
>> >
>

NewsArchive
11-27-2000, 01:00 AM
We have more than one installer that this is happening with a particular NT
machine. It is hard to give more detail. The installers are written in the
States and QAed in Belgium(long story). I have not been able to reproduce
it here.

"Alexander Rodov" <arodov@nospam.earthlink.net> wrote in message
news:3a22a3e4$1@12.41.20.38...
> Joe,
>
> I would recommend to restart your machine, and if error happens again -
> provide more details. See MSI help on "Error Codes"
>
>
> ERROR_CREATE_FAILED 1631 The Windows Installer service failed to
> start. Contact your support personnel.
>
>
> Let me know if that helps,
> Alex Rodov
>
> "Joe Russ" <joe.russ@merant.com> wrote in message
> news:3a22969f$1@12.41.20.38...
> > What is this error? I cannot find any documentation on it.
> >
> >
>
>

NewsArchive
11-28-2000, 01:00 AM
Could it be som security polices on the computers in Belgium that do this??

--Rune G

"Joe Russ" <joe.russ@merant.com> wrote in message
news:3a22abe1@12.41.20.38...
> We have more than one installer that this is happening with a particular
NT
> machine. It is hard to give more detail. The installers are written in
the
> States and QAed in Belgium(long story). I have not been able to reproduce
> it here.
>
> "Alexander Rodov" <arodov@nospam.earthlink.net> wrote in message
> news:3a22a3e4$1@12.41.20.38...
> > Joe,
> >
> > I would recommend to restart your machine, and if error happens again -
> > provide more details. See MSI help on "Error Codes"
> >
> >
> > ERROR_CREATE_FAILED 1631 The Windows Installer service failed to
> > start. Contact your support personnel.
> >
> >
> > Let me know if that helps,
> > Alex Rodov
> >
> > "Joe Russ" <joe.russ@merant.com> wrote in message
> > news:3a22969f$1@12.41.20.38...
> > > What is this error? I cannot find any documentation on it.
> > >
> > >
> >
> >
>
>

NewsArchive
01-10-2001, 01:00 AM
Yeah, I did get it during runtime.

Chandima Rajakaruna <no reply@installshield.com> wrote in message
news:3a5cf328$1@12.41.20.38...
> This is a Windows Installer error which means "Error attempting to open
the
> source file: [3]. System error code: [2] "
>
> Do you get this at runtime? The file it's pointing to could be some temp
> file that was deleted after the setup.
>
> "Nitin" <nitin@dcinc.net> wrote in message news:3a5ce09a$1@12.41.20.38...
> > Hi,
> > error 1309 ... SimplerequestsecurityproviderImplsimpleprinciple.html
file
> > not found.
> >
> > Could you throw some light into this message.
> >
> > Thanks in Advance,
> > Nitin
> >
> >
>
>

NewsArchive
01-10-2001, 01:00 AM
Did you include it in your setup? If so where? (Files View, Support Files,
Custom Action, etc..) Does the error occur if you delete that file from your
setup?


"Nitin" <nitin@dcinc.net> wrote in message news:3a5cf984$1@12.41.20.38...
> Yeah, I did get it during runtime.
>
> Chandima Rajakaruna <no reply@installshield.com> wrote in message
> news:3a5cf328$1@12.41.20.38...
> > This is a Windows Installer error which means "Error attempting to open
> the
> > source file: [3]. System error code: [2] "
> >
> > Do you get this at runtime? The file it's pointing to could be some temp
> > file that was deleted after the setup.
> >
> > "Nitin" <nitin@dcinc.net> wrote in message
news:3a5ce09a$1@12.41.20.38...
> > > Hi,
> > > error 1309 ... SimplerequestsecurityproviderImplsimpleprinciple.html
> file
> > > not found.
> > >
> > > Could you throw some light into this message.
> > >
> > > Thanks in Advance,
> > > Nitin
> > >
> > >
> >
> >
>
>

NewsArchive
01-11-2001, 01:00 AM
Hi,
The file SimplerequestsecurityproviderImplsimpleprinciple.html is an
installshield program file I guess. I have not included it in my setup nor
have I explicitly left it out from the setup.
Thanks,
Nitin
Chandima Rajakaruna <no reply@installshield.com> wrote in message
news:3a5d0c24$1@12.41.20.38...
> Did you include it in your setup? If so where? (Files View, Support Files,
> Custom Action, etc..) Does the error occur if you delete that file from
your
> setup?
>
>
> "Nitin" <nitin@dcinc.net> wrote in message news:3a5cf984$1@12.41.20.38...
> > Yeah, I did get it during runtime.
> >
> > Chandima Rajakaruna <no reply@installshield.com> wrote in message
> > news:3a5cf328$1@12.41.20.38...
> > > This is a Windows Installer error which means "Error attempting to
open
> > the
> > > source file: [3]. System error code: [2] "
> > >
> > > Do you get this at runtime? The file it's pointing to could be some
temp
> > > file that was deleted after the setup.
> > >
> > > "Nitin" <nitin@dcinc.net> wrote in message
> news:3a5ce09a$1@12.41.20.38...
> > > > Hi,
> > > > error 1309 ... SimplerequestsecurityproviderImplsimpleprinciple.html
> > file
> > > > not found.
> > > >
> > > > Could you throw some light into this message.
> > > >
> > > > Thanks in Advance,
> > > > Nitin
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
01-11-2001, 01:00 AM
Do you get this during the setup or after the setup when you try to launch
the program you installed?

If during setup:

It's not an Installshield file. In your setup, go to Files and Features view
and scroll through the files listed and look for something with "Link
broken" or "File not found" link. Once you find it delete it.

If when trying to launch the program:
The program your launching is looking for an htm file which was not included
in the setup. Do a search on your Hard disk for this file and include in
your setup.

"Nitin" <nitin@dcinc.net> wrote in message news:3a5ddb18$1@12.41.20.38...
> Hi,
> The file SimplerequestsecurityproviderImplsimpleprinciple.html is an
> installshield program file I guess. I have not included it in my setup nor
> have I explicitly left it out from the setup.
> Thanks,
> Nitin
> Chandima Rajakaruna <no reply@installshield.com> wrote in message
> news:3a5d0c24$1@12.41.20.38...
> > Did you include it in your setup? If so where? (Files View, Support
Files,
> > Custom Action, etc..) Does the error occur if you delete that file from
> your
> > setup?
> >
> >
> > "Nitin" <nitin@dcinc.net> wrote in message
news:3a5cf984$1@12.41.20.38...
> > > Yeah, I did get it during runtime.
> > >
> > > Chandima Rajakaruna <no reply@installshield.com> wrote in message
> > > news:3a5cf328$1@12.41.20.38...
> > > > This is a Windows Installer error which means "Error attempting to
> open
> > > the
> > > > source file: [3]. System error code: [2] "
> > > >
> > > > Do you get this at runtime? The file it's pointing to could be some
> temp
> > > > file that was deleted after the setup.
> > > >
> > > > "Nitin" <nitin@dcinc.net> wrote in message
> > news:3a5ce09a$1@12.41.20.38...
> > > > > Hi,
> > > > > error 1309 ...
SimplerequestsecurityproviderImplsimpleprinciple.html
> > > file
> > > > > not found.
> > > > >
> > > > > Could you throw some light into this message.
> > > > >
> > > > > Thanks in Advance,
> > > > > Nitin
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
02-01-2001, 01:00 AM
No error specifically said:

Error 1603: General Windows Installer Error: Increase the diskspace required
in setup.ini file.

Changing the diskspace requirement did not solve the problem.

Thanks

Ajay

"Chandima Rajakaruna" <no reply@installshield.com> wrote in message
news:3a79d2c4@12.41.20.38...
> Actually Error 1603 means that a file you are trying change is in use
> (probably by another program)
>
> "Ajay" <abelambe@isi-america.com> wrote in message
> news:3a79c1c3@12.41.20.38...
> > As soon as installer starts installation he gets this error: something
> about
> > Increase the diskspace required.
> >
> > Any clues.
> >
> > Ajay
> >
> >
>
>

NewsArchive
03-01-2001, 01:00 AM
I only have choices of "None" and "Extract COM Information" for executable
files. The VB Merge module is included and both of the executables that are
giving me this error are set to binary compatability.


"Alain Hendrikse" <alain@bayvilla.com> wrote in message
news:3a9e6986@12.41.20.38...
> Try setting the properties of the file to Self-Registering, Jeff - I've
had
> this problem once before. Also - if you're developing the component in
VB,
> make sure that the VB VM merge module is included , and that you have
binary
> compatibility set to ON in your VB project.
>
> "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> news:3a9e646b$1@12.41.20.38...
> > I am getting an error 1911 "Cannot register type library for file
> > [Filename], where [Filename is an ActiveX exe that I install. If I
ignore
> > this error the application seems to work fine. I am using ISX 3.03. Any
> help
> > would be appreciated.
> >
> > Jeff
> >
> >
>
>

NewsArchive
03-05-2001, 01:00 AM
If ignoring the error doesn't have an effect on the performance of your
application after install, try setting the Registration of the 2 files to
none.

"Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
news:3a9e753c@12.41.20.38...
> I only have choices of "None" and "Extract COM Information" for executable
> files. The VB Merge module is included and both of the executables that
are
> giving me this error are set to binary compatability.
>
>
> "Alain Hendrikse" <alain@bayvilla.com> wrote in message
> news:3a9e6986@12.41.20.38...
> > Try setting the properties of the file to Self-Registering, Jeff - I've
> had
> > this problem once before. Also - if you're developing the component in
> VB,
> > make sure that the VB VM merge module is included , and that you have
> binary
> > compatibility set to ON in your VB project.
> >
> > "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> > news:3a9e646b$1@12.41.20.38...
> > > I am getting an error 1911 "Cannot register type library for file
> > > [Filename], where [Filename is an ActiveX exe that I install. If I
> ignore
> > > this error the application seems to work fine. I am using ISX 3.03.
Any
> > help
> > > would be appreciated.
> > >
> > > Jeff
> > >
> > >
> >
> >
>
>

NewsArchive
03-06-2001, 01:00 AM
A newby question.

How do you set the registration to nothing?

"Chandima Rajakaruna" <no reply@installshield.com> wrote in message
news:3aa44c4d$1@12.41.20.38...
> If ignoring the error doesn't have an effect on the performance of your
> application after install, try setting the Registration of the 2 files to
> none.
>
> "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> news:3a9e753c@12.41.20.38...
> > I only have choices of "None" and "Extract COM Information" for
executable
> > files. The VB Merge module is included and both of the executables that
> are
> > giving me this error are set to binary compatability.
> >
> >
> > "Alain Hendrikse" <alain@bayvilla.com> wrote in message
> > news:3a9e6986@12.41.20.38...
> > > Try setting the properties of the file to Self-Registering, Jeff -
I've
> > had
> > > this problem once before. Also - if you're developing the component
in
> > VB,
> > > make sure that the VB VM merge module is included , and that you have
> > binary
> > > compatibility set to ON in your VB project.
> > >
> > > "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> > > news:3a9e646b$1@12.41.20.38...
> > > > I am getting an error 1911 "Cannot register type library for file
> > > > [Filename], where [Filename is an ActiveX exe that I install. If I
> > ignore
> > > > this error the application seems to work fine. I am using ISX 3.03.
> Any
> > > help
> > > > would be appreciated.
> > > >
> > > > Jeff
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
03-06-2001, 01:00 AM
I can't set registration to none because these are ActiveX components. If I
don't register them when I try to call them from another app I get an error.


"Chandima Rajakaruna" <no reply@installshield.com> wrote in message
news:3aa44c4d$1@12.41.20.38...
> If ignoring the error doesn't have an effect on the performance of your
> application after install, try setting the Registration of the 2 files to
> none.
>
> "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> news:3a9e753c@12.41.20.38...
> > I only have choices of "None" and "Extract COM Information" for
executable
> > files. The VB Merge module is included and both of the executables that
> are
> > giving me this error are set to binary compatability.
> >
> >
> > "Alain Hendrikse" <alain@bayvilla.com> wrote in message
> > news:3a9e6986@12.41.20.38...
> > > Try setting the properties of the file to Self-Registering, Jeff -
I've
> > had
> > > this problem once before. Also - if you're developing the component
in
> > VB,
> > > make sure that the VB VM merge module is included , and that you have
> > binary
> > > compatibility set to ON in your VB project.
> > >
> > > "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> > > news:3a9e646b$1@12.41.20.38...
> > > > I am getting an error 1911 "Cannot register type library for file
> > > > [Filename], where [Filename is an ActiveX exe that I install. If I
> > ignore
> > > > this error the application seems to work fine. I am using ISX 3.03.
> Any
> > > help
> > > > would be appreciated.
> > > >
> > > > Jeff
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
03-06-2001, 01:00 AM
Hmmm. That certainly is a problem. Couple of suggestions.

1. Run a Custom Action using Regsvr (or Regsvr32) to register these files
once the installation is complete

2. Try setting the registration back to "Extract COM Information". Now using
Regserver register your Exe on the machine. Reboot and try a build again. If
I am not mistaken the necessary Prog Id and COM info is picked up from the
Registry during build time.

3. If you know the COM classes and where they get registered to, distribute
them though the registry view




"Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
news:3aa4e944$1@12.41.20.38...
> I can't set registration to none because these are ActiveX components. If
I
> don't register them when I try to call them from another app I get an
error.
>
>
> "Chandima Rajakaruna" <no reply@installshield.com> wrote in message
> news:3aa44c4d$1@12.41.20.38...
> > If ignoring the error doesn't have an effect on the performance of your
> > application after install, try setting the Registration of the 2 files
to
> > none.
> >
> > "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> > news:3a9e753c@12.41.20.38...
> > > I only have choices of "None" and "Extract COM Information" for
> executable
> > > files. The VB Merge module is included and both of the executables
that
> > are
> > > giving me this error are set to binary compatability.
> > >
> > >
> > > "Alain Hendrikse" <alain@bayvilla.com> wrote in message
> > > news:3a9e6986@12.41.20.38...
> > > > Try setting the properties of the file to Self-Registering, Jeff -
> I've
> > > had
> > > > this problem once before. Also - if you're developing the component
> in
> > > VB,
> > > > make sure that the VB VM merge module is included , and that you
have
> > > binary
> > > > compatibility set to ON in your VB project.
> > > >
> > > > "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> > > > news:3a9e646b$1@12.41.20.38...
> > > > > I am getting an error 1911 "Cannot register type library for file
> > > > > [Filename], where [Filename is an ActiveX exe that I install. If I
> > > ignore
> > > > > this error the application seems to work fine. I am using ISX
3.03.
> > Any
> > > > help
> > > > > would be appreciated.
> > > > >
> > > > > Jeff
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
03-06-2001, 01:00 AM
Right click on the file. From the menu choose Properties. Then go to the
advanced tab. There you will see the registration property. The registration
property is enabled for only exec, dll and ocx files. This is for Express
3.03 by the way.

"Pascal Mestdach" <pascal@tkfy.com> wrote in message
news:3aa4dad1$1@12.41.20.38...
> A newby question.
>
> How do you set the registration to nothing?
>
> "Chandima Rajakaruna" <no reply@installshield.com> wrote in message
> news:3aa44c4d$1@12.41.20.38...
> > If ignoring the error doesn't have an effect on the performance of your
> > application after install, try setting the Registration of the 2 files
to
> > none.
> >
> > "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> > news:3a9e753c@12.41.20.38...
> > > I only have choices of "None" and "Extract COM Information" for
> executable
> > > files. The VB Merge module is included and both of the executables
that
> > are
> > > giving me this error are set to binary compatability.
> > >
> > >
> > > "Alain Hendrikse" <alain@bayvilla.com> wrote in message
> > > news:3a9e6986@12.41.20.38...
> > > > Try setting the properties of the file to Self-Registering, Jeff -
> I've
> > > had
> > > > this problem once before. Also - if you're developing the component
> in
> > > VB,
> > > > make sure that the VB VM merge module is included , and that you
have
> > > binary
> > > > compatibility set to ON in your VB project.
> > > >
> > > > "Jeff Manney" <Jeffrey_Manney@Instron.com> wrote in message
> > > > news:3a9e646b$1@12.41.20.38...
> > > > > I am getting an error 1911 "Cannot register type library for file
> > > > > [Filename], where [Filename is an ActiveX exe that I install. If I
> > > ignore
> > > > > this error the application seems to work fine. I am using ISX
3.03.
> > Any
> > > > help
> > > > > would be appreciated.
> > > > >
> > > > > Jeff
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
03-19-2001, 01:00 AM
Thanks for your answers. We have solved the problem.

Br, Evgen Zmarzli


"Rune G" <rg#world-online.no> wrote in message
news:3ab1f31c$1@12.41.20.38...
> Set the Supress launcher warning flag on your release build page to YES..
>
> This should fix it..
>
> --Rune G
>
> "martin luter" <martin@luter.net> wrote in message
> news:3ab1de83@12.41.20.38...
> > Hi!
> >
> > We are creating setup package on NT4.0 SP6 machine with InstallShield
> > Professional (Windows Installer Edition) v2.01. When we run our setup on
> > W2000 machine, installation reports:
> >
> > Error 1207 ( Installer 1.11.1314.0 found. This is an older version of
> > Windows Installer. Click OK to continue.
> >
> > If you click OK, setup continues normaly.What seems to be the problem?
> >
> > Thanks for your answers!
> >
> > Evgen
> >
> >
> >
> >
>
>

NewsArchive
04-27-2001, 12:00 AM
Not me, but our customer, who tried to install our product, got this message
both on Windows 95 and Windows 98 systems on different computers. But I
tried to install this on all the computers in our office and couldn't get
this error.

Will appreciate any advise.


Madhavi Gullapalli <noreplyplease@installshield.com> wrote in message
news:3ae72bad$1@12.41.20.38...
> Do you get this on a specific OS (9x vs. win 2k)?
>
> Classic Software <classicpos@sprint.ca> wrote in message
> news:3ae45eb3$1@12.41.20.38...
> > Did anybody have an error #1402 during the installation? What does it
> mean?
> >
> > Thanks
> >
> >
> >
>
>

NewsArchive
04-29-2001, 12:00 AM
Probably you need to install a new version of Windows Installer.


Classic Software <classicpos@sprint.ca> schreef in berichtnieuws
3ae9a4c3@12.41.20.38...
> Not me, but our customer, who tried to install our product, got this
message
> both on Windows 95 and Windows 98 systems on different computers. But I
> tried to install this on all the computers in our office and couldn't get
> this error.
>
> Will appreciate any advise.
>
>
> Madhavi Gullapalli <noreplyplease@installshield.com> wrote in message
> news:3ae72bad$1@12.41.20.38...
> > Do you get this on a specific OS (9x vs. win 2k)?
> >
> > Classic Software <classicpos@sprint.ca> wrote in message
> > news:3ae45eb3$1@12.41.20.38...
> > > Did anybody have an error #1402 during the installation? What does it
> > mean?
> > >
> > > Thanks
> > >
> > >
> > >
> >
> >
>
>
>
>

NewsArchive
04-30-2001, 12:00 AM
Do you have the Customer Information Dialog included in your setup? If not,
try including it.

Windows Installer Service on Win 9.x machines returns this error if the user
profile on these machines is turned on. You will have to disable the user
profile on these machines as a work around. Please refer to article Q236427,
which talks about this error in Microsoft's Knowledge base database. This
article can be accessed at http://msdn.microsoft.com or by clicking on the
following link:
http://support.microsoft.com/support/kb/articles/Q236/4/27.ASP. This article
will walk you through disabling the User Profile or creating a new profile
and running the setup again.


Classic Software <classicpos@sprint.ca> wrote in message
news:3ae9a4c3@12.41.20.38...
> Not me, but our customer, who tried to install our product, got this
message
> both on Windows 95 and Windows 98 systems on different computers. But I
> tried to install this on all the computers in our office and couldn't get
> this error.
>
> Will appreciate any advise.
>
>
> Madhavi Gullapalli <noreplyplease@installshield.com> wrote in message
> news:3ae72bad$1@12.41.20.38...
> > Do you get this on a specific OS (9x vs. win 2k)?
> >
> > Classic Software <classicpos@sprint.ca> wrote in message
> > news:3ae45eb3$1@12.41.20.38...
> > > Did anybody have an error #1402 during the installation? What does it
> > mean?
> > >
> > > Thanks
> > >
> > >
> > >
> >
> >
>
>
>
>

NewsArchive
05-04-2001, 12:00 AM
"P.C.Quick" wrote:
>
> Do you also use Installshield 3.03?

yes. Sorry for not specifying

> Which operating system do you use?

Windows 98

> And how many files have you packed with installshield?

There doesn't seem to be any easy way of counting them, but between my 3
features there are probably literally thousands of files.

I am just using an evaluation copy of IS right now. I am trying to
figure out if it is going to meet our needs.

Thanks for any insights you may have!

--Robyn Kozierok <robyn@mitre.org>
The MITRE Corporation

NewsArchive
05-04-2001, 12:00 AM
"P.C.Quick" wrote:
>
> Do you also use Installshield 3.03?

yes. Sorry for not specifying

> Which operating system do you use?

Windows 98

> And how many files have you packed with installshield?

There doesn't seem to be any easy way of counting them, but between my 3
features there are probably literally thousands of files.

I am just using an evaluation copy of IS right now. I am trying to
figure out if it is going to meet our needs.

Thanks for any insights you may have!

--Robyn Kozierok <robyn@mitre.org>
The MITRE Corporation

NewsArchive
05-29-2001, 12:00 AM
Hi

Thanx! There is a line:
Info 1903.Scheduling reboot operation: Deleting file
C:\WINNT\Installer\2d97f.msi. Must reboot to complete operation.

But this is not one of my files?!?!?!?



Thomas Eskesen



"Edward Clements" <klikli@compuserve.com> wrote in message
news:3b1345ab$1@12.41.20.38...
> Thomas,
>
> Probably one of the files you're replacing is in use -- you can check this
> by creating a log file (msiexec /i {your-product-code} /l*v
logfilename.log)
> and searching the log file for the text "reboot"...
>
> Edward Clements
>
> "Thomas Eskesen" <te@danware.dk> wrote in message
> news:3b121cb5@12.41.20.38...
> > Hi
> >
> > When I update my installation (using Maintenance/Repair) I get an
"Error"
> in
> > the end (#1703) - It tells me to reboot, for the update to take effect
> > (using IDS_ERROR_74).
> > Anyone know where it comes from? and why?
> > Can I disable this - I do NOT need to reeboot!
> >
> > Regards,
> > Thomas Eskesen
> >
> >
>
>

NewsArchive
05-30-2001, 12:00 AM
Thomas,

Do you have a "v" in your REINSTALLMODE, maybe?

Anyone else know what's the problem?

Edward Clements

"Thomas Eskesen" <te@danware.dk> wrote in message
news:3b134987@12.41.20.38...
> Hi
>
> Thanx! There is a line:
> Info 1903.Scheduling reboot operation: Deleting file
> C:\WINNT\Installer\2d97f.msi. Must reboot to complete operation.
>
> But this is not one of my files?!?!?!?
>
>
>
> Thomas Eskesen
>
>
>
> "Edward Clements" <klikli@compuserve.com> wrote in message
> news:3b1345ab$1@12.41.20.38...
> > Thomas,
> >
> > Probably one of the files you're replacing is in use -- you can check
this
> > by creating a log file (msiexec /i {your-product-code} /l*v
> logfilename.log)
> > and searching the log file for the text "reboot"...
> >
> > Edward Clements
> >
> > "Thomas Eskesen" <te@danware.dk> wrote in message
> > news:3b121cb5@12.41.20.38...
> > > Hi
> > >
> > > When I update my installation (using Maintenance/Repair) I get an
> "Error"
> > in
> > > the end (#1703) - It tells me to reboot, for the update to take effect
> > > (using IDS_ERROR_74).
> > > Anyone know where it comes from? and why?
> > > Can I disable this - I do NOT need to reeboot!
> > >
> > > Regards,
> > > Thomas Eskesen
> > >
> > >
> >
> >
>
>

NewsArchive
05-30-2001, 12:00 AM
Yes I have a "v"!!!
I need the "v" - otherwise my Maintenance/Repair wont update possible new
files (from a new build).

Thomas

"Edward Clements" <klikli@compuserve.com> wrote in message
news:3b1498cc@12.41.20.38...
> Thomas,
>
> Do you have a "v" in your REINSTALLMODE, maybe?
>
> Anyone else know what's the problem?
>
> Edward Clements
>
> "Thomas Eskesen" <te@danware.dk> wrote in message
> news:3b134987@12.41.20.38...
> > Hi
> >
> > Thanx! There is a line:
> > Info 1903.Scheduling reboot operation: Deleting file
> > C:\WINNT\Installer\2d97f.msi. Must reboot to complete operation.
> >
> > But this is not one of my files?!?!?!?
> >
> >
> >
> > Thomas Eskesen
> >
> >
> >
> > "Edward Clements" <klikli@compuserve.com> wrote in message
> > news:3b1345ab$1@12.41.20.38...
> > > Thomas,
> > >
> > > Probably one of the files you're replacing is in use -- you can check
> this
> > > by creating a log file (msiexec /i {your-product-code} /l*v
> > logfilename.log)
> > > and searching the log file for the text "reboot"...
> > >
> > > Edward Clements
> > >
> > > "Thomas Eskesen" <te@danware.dk> wrote in message
> > > news:3b121cb5@12.41.20.38...
> > > > Hi
> > > >
> > > > When I update my installation (using Maintenance/Repair) I get an
> > "Error"
> > > in
> > > > the end (#1703) - It tells me to reboot, for the update to take
effect
> > > > (using IDS_ERROR_74).
> > > > Anyone know where it comes from? and why?
> > > > Can I disable this - I do NOT need to reeboot!
> > > >
> > > > Regards,
> > > > Thomas Eskesen
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
05-30-2001, 12:00 AM
Hi..

This is the WI cached installer file for your previous installation..

If this file cannot be deleteted without a reboot it's most probarly
something that uses it.


--Rune G

"Thomas Eskesen" <te@danware.dk> wrote in message
news:3b134987@12.41.20.38...
> Hi
>
> Thanx! There is a line:
> Info 1903.Scheduling reboot operation: Deleting file
> C:\WINNT\Installer\2d97f.msi. Must reboot to complete operation.
>
> But this is not one of my files?!?!?!?
>
>
>
> Thomas Eskesen
>
>
>
> "Edward Clements" <klikli@compuserve.com> wrote in message
> news:3b1345ab$1@12.41.20.38...
> > Thomas,
> >
> > Probably one of the files you're replacing is in use -- you can check
this
> > by creating a log file (msiexec /i {your-product-code} /l*v
> logfilename.log)
> > and searching the log file for the text "reboot"...
> >
> > Edward Clements
> >
> > "Thomas Eskesen" <te@danware.dk> wrote in message
> > news:3b121cb5@12.41.20.38...
> > > Hi
> > >
> > > When I update my installation (using Maintenance/Repair) I get an
> "Error"
> > in
> > > the end (#1703) - It tells me to reboot, for the update to take effect
> > > (using IDS_ERROR_74).
> > > Anyone know where it comes from? and why?
> > > Can I disable this - I do NOT need to reeboot!
> > >
> > > Regards,
> > > Thomas Eskesen
> > >
> > >
> >
> >
>
>

NewsArchive
05-31-2001, 12:00 AM
Thomas,

I don't think you would go into the MaintenanceWelcome dialog box if you had
a new build (i.e., a minor/major upgrade).
The MSI help says for 'v': "Use to run from the source package and re-cache
the local package." -- try it without the 'v'...

Edward Clements

"Thomas Eskesen" <te@danware.dk> wrote in message
news:3b14b220$1@12.41.20.38...
> Yes I have a "v"!!!
> I need the "v" - otherwise my Maintenance/Repair wont update possible new
> files (from a new build).
>
> Thomas
>
> "Edward Clements" <klikli@compuserve.com> wrote in message
> news:3b1498cc@12.41.20.38...
> > Thomas,
> >
> > Do you have a "v" in your REINSTALLMODE, maybe?
> >
> > Anyone else know what's the problem?
> >
> > Edward Clements
> >
> > "Thomas Eskesen" <te@danware.dk> wrote in message
> > news:3b134987@12.41.20.38...
> > > Hi
> > >
> > > Thanx! There is a line:
> > > Info 1903.Scheduling reboot operation: Deleting file
> > > C:\WINNT\Installer\2d97f.msi. Must reboot to complete operation.
> > >
> > > But this is not one of my files?!?!?!?
> > >
> > >
> > >
> > > Thomas Eskesen
.....

NewsArchive
05-31-2001, 12:00 AM
Hi

I would like a simple way to update my installed application, eg with a new
build of my program!
I have used many days to try to change product/upgrade/package codes nad
version numbers in different combinations; but the result was: either the
files are not updated or the user just get a messagebox telling him to
uninstall the old version and install the new version from scratch,....
with the "v" flag and renaming of the "Repair" text to "Update/Repair" the
user gets a easy/simple way to upgrade files, serialnumbers etc.

Regards,
Thomas


"Edward Clements" <klikli@compuserve.com> wrote in message
news:3b15ee76@12.41.20.38...
> Thomas,
>
> I don't think you would go into the MaintenanceWelcome dialog box if you
had
> a new build (i.e., a minor/major upgrade).
> The MSI help says for 'v': "Use to run from the source package and
re-cache
> the local package." -- try it without the 'v'...
>
> Edward Clements
>
> "Thomas Eskesen" <te@danware.dk> wrote in message
> news:3b14b220$1@12.41.20.38...
> > Yes I have a "v"!!!
> > I need the "v" - otherwise my Maintenance/Repair wont update possible
new
> > files (from a new build).
> >
> > Thomas
> >
> > "Edward Clements" <klikli@compuserve.com> wrote in message
> > news:3b1498cc@12.41.20.38...
> > > Thomas,
> > >
> > > Do you have a "v" in your REINSTALLMODE, maybe?
> > >
> > > Anyone else know what's the problem?
> > >
> > > Edward Clements
> > >
> > > "Thomas Eskesen" <te@danware.dk> wrote in message
> > > news:3b134987@12.41.20.38...
> > > > Hi
> > > >
> > > > Thanx! There is a line:
> > > > Info 1903.Scheduling reboot operation: Deleting file
> > > > C:\WINNT\Installer\2d97f.msi. Must reboot to complete operation.
> > > >
> > > > But this is not one of my files?!?!?!?
> > > >
> > > >
> > > >
> > > > Thomas Eskesen
> ....
>
>

NewsArchive
06-01-2001, 12:00 AM
Thomas,

Then why not dynamically change the REINSTALLMODE to contain the "v" when
you are doing an upgrade and not otherwise?

Edward Clements

"Thomas Eskesen" <te@danware.dk> wrote in message
news:3b15f351$1@12.41.20.38...
> Hi
>
> I would like a simple way to update my installed application, eg with a
new
> build of my program!
> I have used many days to try to change product/upgrade/package codes nad
> version numbers in different combinations; but the result was: either the
> files are not updated or the user just get a messagebox telling him to
> uninstall the old version and install the new version from scratch,....
> with the "v" flag and renaming of the "Repair" text to "Update/Repair" the
> user gets a easy/simple way to upgrade files, serialnumbers etc.
>
> Regards,
> Thomas
>
>
> "Edward Clements" <klikli@compuserve.com> wrote in message
> news:3b15ee76@12.41.20.38...
> > Thomas,
> >
> > I don't think you would go into the MaintenanceWelcome dialog box if you
> had
> > a new build (i.e., a minor/major upgrade).
> > The MSI help says for 'v': "Use to run from the source package and
> re-cache
> > the local package." -- try it without the 'v'...
> >
> > Edward Clements
> >
> > "Thomas Eskesen" <te@danware.dk> wrote in message
> > news:3b14b220$1@12.41.20.38...
> > > Yes I have a "v"!!!
> > > I need the "v" - otherwise my Maintenance/Repair wont update possible
> new
> > > files (from a new build).
> > >
> > > Thomas
> > >
> > > "Edward Clements" <klikli@compuserve.com> wrote in message
> > > news:3b1498cc@12.41.20.38...
> > > > Thomas,
> > > >
> > > > Do you have a "v" in your REINSTALLMODE, maybe?
> > > >
> > > > Anyone else know what's the problem?
> > > >
> > > > Edward Clements
> > > >
> > > > "Thomas Eskesen" <te@danware.dk> wrote in message
> > > > news:3b134987@12.41.20.38...
> > > > > Hi
> > > > >
> > > > > Thanx! There is a line:
> > > > > Info 1903.Scheduling reboot operation: Deleting file
> > > > > C:\WINNT\Installer\2d97f.msi. Must reboot to complete operation.
> > > > >
> > > > > But this is not one of my files?!?!?!?
> > > > >
> > > > >
> > > > >
> > > > > Thomas Eskesen
> > ....
> >
> >
>
>

NewsArchive
07-05-2001, 12:00 AM
Thanks,
I'm not sure what to do though since we aren't adding any registry settings,
is InstallShield adding these values on it's own? How do we know in advanced
what keys are locked.
Thanks again


"Jim Kang" <replytogroup@installshield.com> wrote in message
news:3b420481$1@12.41.20.38...
> If this doesn't happen on other machines, it's likely that some process is
> locking that key on that machine. I think NTHandleEx from
www.sysinternals.com
> (I think - it might be another tool from that site) can tell you if and
who is
> holding the key.
>
> In article <3b41e9db@12.41.20.38>, "Buddy Flynn" <Buddy_Flynn@dssihq.com>
> wrote:
> >Hello,
> >We just installed InstallShield Express 3.03, and migrated the our
previous
> >..ism files over. Now I'm getting this error:
> >
> >"Error 1406. Could not qrite value 409 to key
> >HKEY_LOCAL_MACHINE\Software\Classes\Component
> >Categories\{40FC6ED5-2438-11CFA3DB-080036f12502}. Verify you have
sufficient
> >access to that key, or contact your support personal."
> >
> >I tried logging on as the administrator and still got the same error. If
you
> >click Ignore,the same error is repeated a couple more time with different
> >keys but the install completes and the program seems to run OK. Any
ideas?
> >
> > Thanks,
> > Buddy Flynn
> >
> >

NewsArchive
07-05-2001, 12:00 AM
What I thought might be happening is that that key is being held before the
install even starts by a process unrelated to the installation on that
particular machine (unless this is reproducible on multiple machines).
NTHandleEx would help you figure out what that process was.

In article <3b449d02$1@12.41.20.38>, "Buddy Flynn" <Buddy_Flynn@dssihq.com>
wrote:
>Thanks,
>I'm not sure what to do though since we aren't adding any registry settings,
>is InstallShield adding these values on it's own? How do we know in advanced
>what keys are locked.
> Thanks again
>
>
>"Jim Kang" <replytogroup@installshield.com> wrote in message
>news:3b420481$1@12.41.20.38...
>> If this doesn't happen on other machines, it's likely that some process is
>> locking that key on that machine. I think NTHandleEx from
>www.sysinternals.com
>> (I think - it might be another tool from that site) can tell you if and
>who is
>> holding the key.
>>
>> In article <3b41e9db@12.41.20.38>, "Buddy Flynn" <Buddy_Flynn@dssihq.com>
>> wrote:
>> >Hello,
>> >We just installed InstallShield Express 3.03, and migrated the our
>previous
>> >..ism files over. Now I'm getting this error:
>> >
>> >"Error 1406. Could not qrite value 409 to key
>> >HKEY_LOCAL_MACHINE\Software\Classes\Component
>> >Categories\{40FC6ED5-2438-11CFA3DB-080036f12502}. Verify you have
>sufficient
>> >access to that key, or contact your support personal."
>> >
>> >I tried logging on as the administrator and still got the same error. If
>you
>> >click Ignore,the same error is repeated a couple more time with different
>> >keys but the install completes and the program seems to run OK. Any
>ideas?
>> >
>> > Thanks,
>> > Buddy Flynn
>> >
>> >
>
>

NewsArchive
07-13-2001, 12:00 AM
Ok, I actually had done that before I posted. Now, what does that mean?
The user removed the application that he is trying to upgrade by running the
uninstall, and he still gets the error. There must be some file or registry
entry that didn't get cleaned up. How does one find out what is triggering
the error?

"Edward Clements" <klikli@compuserve.com> wrote in message
news:3b4ead11@12.41.20.38...
> You need to look at the MSI-help
> 1714 says "The older version of [2] cannot be removed. Contact your
> technical support group. System Error [3]. "
>
> Edward Clements
>
> "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> news:3b4dc604@12.41.20.38...
> > Does anyone know what would cause this error? I have a customer how was
> > getting it when he attempted to upgrade to a newer version of our
product.
> > Since then, he has run the uninstall for the old version, but he is
still
> > unable to install our new version -- same error. I haven't had much
luck
> > finding anything about this error. Where would I look for the problem?
> >
> > -- Jeremy
> >
> >
>
>

NewsArchive
07-13-2001, 12:00 AM
If the cached install for the "unremovable" product is still available, try
running with logging turned on. Maybe a clue to what didn't work properly
might be found. Also get a hold of the msicu utility and zap it. This
leaves the files but removes all the msi information about the product.
Just my two cents worth.


"J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
news:3b4f16b3$1@12.41.20.38...
> Ok, I actually had done that before I posted. Now, what does that mean?
> The user removed the application that he is trying to upgrade by running
the
> uninstall, and he still gets the error. There must be some file or
registry
> entry that didn't get cleaned up. How does one find out what is
triggering
> the error?
>
> "Edward Clements" <klikli@compuserve.com> wrote in message
> news:3b4ead11@12.41.20.38...
> > You need to look at the MSI-help
> > 1714 says "The older version of [2] cannot be removed. Contact your
> > technical support group. System Error [3]. "
> >
> > Edward Clements
> >
> > "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> > news:3b4dc604@12.41.20.38...
> > > Does anyone know what would cause this error? I have a customer how
was
> > > getting it when he attempted to upgrade to a newer version of our
> product.
> > > Since then, he has run the uninstall for the old version, but he is
> still
> > > unable to install our new version -- same error. I haven't had much
> luck
> > > finding anything about this error. Where would I look for the
problem?
> > >
> > > -- Jeremy
> > >
> > >
> >
> >
>
>

NewsArchive
07-13-2001, 12:00 AM
Hmm, sounds reasonable, but with a twist: The older version that he is
trying to remove (version 2.0) was installed with Installshield version 5.5.
I wonder if it's possible that the new setup (version 3.1) could be tripping
over itself: It failed the first time it ran. Is it possible that it left
some "clutter" behind? I have asked the customer to run the new setup with
logging turned on, but I have not yet received the log. Hopefully that will
shed some light on things...

"RHK" <ralph.kreiplenospam@software.rockwell.com> wrote in message
news:3b4f3bd1$1@12.41.20.38...
> If the cached install for the "unremovable" product is still available,
try
> running with logging turned on. Maybe a clue to what didn't work properly
> might be found. Also get a hold of the msicu utility and zap it. This
> leaves the files but removes all the msi information about the product.
> Just my two cents worth.
>
>
> "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> news:3b4f16b3$1@12.41.20.38...
> > Ok, I actually had done that before I posted. Now, what does that mean?
> > The user removed the application that he is trying to upgrade by running
> the
> > uninstall, and he still gets the error. There must be some file or
> registry
> > entry that didn't get cleaned up. How does one find out what is
> triggering
> > the error?
> >
> > "Edward Clements" <klikli@compuserve.com> wrote in message
> > news:3b4ead11@12.41.20.38...
> > > You need to look at the MSI-help
> > > 1714 says "The older version of [2] cannot be removed. Contact your
> > > technical support group. System Error [3]. "
> > >
> > > Edward Clements
> > >
> > > "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> > > news:3b4dc604@12.41.20.38...
> > > > Does anyone know what would cause this error? I have a customer how
> was
> > > > getting it when he attempted to upgrade to a newer version of our
> > product.
> > > > Since then, he has run the uninstall for the old version, but he is
> > still
> > > > unable to install our new version -- same error. I haven't had much
> > luck
> > > > finding anything about this error. Where would I look for the
> problem?
> > > >
> > > > -- Jeremy
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
07-13-2001, 12:00 AM
I made the assumption that the original install was an MSI based install.
See what happens when you assume. Anyhow, if the MSI install has fouled
something, the msicu utility might clean it up enough to start over.

Good luck,

RHK

"J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
news:3b4f5271$1@12.41.20.38...
> Hmm, sounds reasonable, but with a twist: The older version that he is
> trying to remove (version 2.0) was installed with Installshield version
5.5.
> I wonder if it's possible that the new setup (version 3.1) could be
tripping
> over itself: It failed the first time it ran. Is it possible that it
left
> some "clutter" behind? I have asked the customer to run the new setup
with
> logging turned on, but I have not yet received the log. Hopefully that
will
> shed some light on things...
>
> "RHK" <ralph.kreiplenospam@software.rockwell.com> wrote in message
> news:3b4f3bd1$1@12.41.20.38...
> > If the cached install for the "unremovable" product is still available,
> try
> > running with logging turned on. Maybe a clue to what didn't work
properly
> > might be found. Also get a hold of the msicu utility and zap it. This
> > leaves the files but removes all the msi information about the product.
> > Just my two cents worth.
> >
> >
> > "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> > news:3b4f16b3$1@12.41.20.38...
> > > Ok, I actually had done that before I posted. Now, what does that
mean?
> > > The user removed the application that he is trying to upgrade by
running
> > the
> > > uninstall, and he still gets the error. There must be some file or
> > registry
> > > entry that didn't get cleaned up. How does one find out what is
> > triggering
> > > the error?
> > >
> > > "Edward Clements" <klikli@compuserve.com> wrote in message
> > > news:3b4ead11@12.41.20.38...
> > > > You need to look at the MSI-help
> > > > 1714 says "The older version of [2] cannot be removed. Contact your
> > > > technical support group. System Error [3]. "
> > > >
> > > > Edward Clements
> > > >
> > > > "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> > > > news:3b4dc604@12.41.20.38...
> > > > > Does anyone know what would cause this error? I have a customer
how
> > was
> > > > > getting it when he attempted to upgrade to a newer version of our
> > > product.
> > > > > Since then, he has run the uninstall for the old version, but he
is
> > > still
> > > > > unable to install our new version -- same error. I haven't had
much
> > > luck
> > > > > finding anything about this error. Where would I look for the
> > problem?
> > > > >
> > > > > -- Jeremy
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
07-16-2001, 12:00 AM
The word "upgrade" has a specific meaning in the Installer world. It's a
specific in-place method of replacing an older version with a newer version,
both of which have to be Windows Installer products. That's why you're
confusing people ;-)

If the old version is 5.5 install, what exactly are you doing to cause it to
be uninstalled? Are you trying to use the Upgrade Table?

"J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
news:3b4f5271$1@12.41.20.38...
> Hmm, sounds reasonable, but with a twist: The older version that he is
> trying to remove (version 2.0) was installed with Installshield version
5.5.
> I wonder if it's possible that the new setup (version 3.1) could be
tripping
> over itself: It failed the first time it ran. Is it possible that it
left
> some "clutter" behind? I have asked the customer to run the new setup
with
> logging turned on, but I have not yet received the log. Hopefully that
will
> shed some light on things...
>
> "RHK" <ralph.kreiplenospam@software.rockwell.com> wrote in message
> news:3b4f3bd1$1@12.41.20.38...
> > If the cached install for the "unremovable" product is still available,
> try
> > running with logging turned on. Maybe a clue to what didn't work
properly
> > might be found. Also get a hold of the msicu utility and zap it. This
> > leaves the files but removes all the msi information about the product.
> > Just my two cents worth.
> >
> >
> > "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> > news:3b4f16b3$1@12.41.20.38...
> > > Ok, I actually had done that before I posted. Now, what does that
mean?
> > > The user removed the application that he is trying to upgrade by
running
> > the
> > > uninstall, and he still gets the error. There must be some file or
> > registry
> > > entry that didn't get cleaned up. How does one find out what is
> > triggering
> > > the error?
> > >
> > > "Edward Clements" <klikli@compuserve.com> wrote in message
> > > news:3b4ead11@12.41.20.38...
> > > > You need to look at the MSI-help
> > > > 1714 says "The older version of [2] cannot be removed. Contact your
> > > > technical support group. System Error [3]. "
> > > >
> > > > Edward Clements
> > > >
> > > > "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> > > > news:3b4dc604@12.41.20.38...
> > > > > Does anyone know what would cause this error? I have a customer
how
> > was
> > > > > getting it when he attempted to upgrade to a newer version of our
> > > product.
> > > > > Since then, he has run the uninstall for the old version, but he
is
> > > still
> > > > > unable to install our new version -- same error. I haven't had
much
> > > luck
> > > > > finding anything about this error. Where would I look for the
> > problem?
> > > > >
> > > > > -- Jeremy
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
07-17-2001, 12:00 AM
Ah, I should probably be a bit more precise. The new setup is designed to
perform MSI upgrades -- that is, I have entries in the upgrade table, and I
update the package code/product code/version number when appropriate.
However, the "upgrade" that the customer is trying to perform involves a
base version that was installed with a pre-MSI installer (Installshield
5.5). So, in this case, the MSI install would be functioning as an install,
not an installer upgrade.


"Phil Wilson" <phil.wilson@unisys.nospam.com> wrote in message
news:3b533fa0$1@12.41.20.38...
> The word "upgrade" has a specific meaning in the Installer world. It's a
> specific in-place method of replacing an older version with a newer
version,
> both of which have to be Windows Installer products. That's why you're
> confusing people ;-)
>
> If the old version is 5.5 install, what exactly are you doing to cause it
to
> be uninstalled? Are you trying to use the Upgrade Table?
>
> "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> news:3b4f5271$1@12.41.20.38...
> > Hmm, sounds reasonable, but with a twist: The older version that he is
> > trying to remove (version 2.0) was installed with Installshield version
> 5.5.
> > I wonder if it's possible that the new setup (version 3.1) could be
> tripping
> > over itself: It failed the first time it ran. Is it possible that it
> left
> > some "clutter" behind? I have asked the customer to run the new setup
> with
> > logging turned on, but I have not yet received the log. Hopefully that
> will
> > shed some light on things...
> >
> > "RHK" <ralph.kreiplenospam@software.rockwell.com> wrote in message
> > news:3b4f3bd1$1@12.41.20.38...
> > > If the cached install for the "unremovable" product is still
available,
> > try
> > > running with logging turned on. Maybe a clue to what didn't work
> properly
> > > might be found. Also get a hold of the msicu utility and zap it.
This
> > > leaves the files but removes all the msi information about the
product.
> > > Just my two cents worth.
> > >
> > >
> > > "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> > > news:3b4f16b3$1@12.41.20.38...
> > > > Ok, I actually had done that before I posted. Now, what does that
> mean?
> > > > The user removed the application that he is trying to upgrade by
> running
> > > the
> > > > uninstall, and he still gets the error. There must be some file or
> > > registry
> > > > entry that didn't get cleaned up. How does one find out what is
> > > triggering
> > > > the error?
> > > >
> > > > "Edward Clements" <klikli@compuserve.com> wrote in message
> > > > news:3b4ead11@12.41.20.38...
> > > > > You need to look at the MSI-help
> > > > > 1714 says "The older version of [2] cannot be removed. Contact
your
> > > > > technical support group. System Error [3]. "
> > > > >
> > > > > Edward Clements
> > > > >
> > > > > "J.Marsch" <marschj_no_spam@no.spam.swbell.net> wrote in message
> > > > > news:3b4dc604@12.41.20.38...
> > > > > > Does anyone know what would cause this error? I have a customer
> how
> > > was
> > > > > > getting it when he attempted to upgrade to a newer version of
our
> > > > product.
> > > > > > Since then, he has run the uninstall for the old version, but he
> is
> > > > still
> > > > > > unable to install our new version -- same error. I haven't had
> much
> > > > luck
> > > > > > finding anything about this error. Where would I look for the
> > > problem?
> > > > > >
> > > > > > -- Jeremy
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
08-01-2001, 12:00 AM
I have the same problem with testing this on my 200 machine it does the same
as the win98se machine.

it will be a pain as i now need to distribute copys to my clients this week
and this bug is all i need to slow production up.

Anybody found a fix

Eddie Stonham
Keypadit Ltd

"Jim Kang" <replytogroup@installshield.com> wrote in message
news:3b44ab65$1@12.41.20.38...
> What I thought might be happening is that that key is being held before
the
> install even starts by a process unrelated to the installation on that
> particular machine (unless this is reproducible on multiple machines).
> NTHandleEx would help you figure out what that process was.
>
> In article <3b449d02$1@12.41.20.38>, "Buddy Flynn"
<Buddy_Flynn@dssihq.com>
> wrote:
> >Thanks,
> >I'm not sure what to do though since we aren't adding any registry
settings,
> >is InstallShield adding these values on it's own? How do we know in
advanced
> >what keys are locked.
> > Thanks again
> >
> >
> >"Jim Kang" <replytogroup@installshield.com> wrote in message
> >news:3b420481$1@12.41.20.38...
> >> If this doesn't happen on other machines, it's likely that some process
is
> >> locking that key on that machine. I think NTHandleEx from
> >www.sysinternals.com
> >> (I think - it might be another tool from that site) can tell you if and
> >who is
> >> holding the key.
> >>
> >> In article <3b41e9db@12.41.20.38>, "Buddy Flynn"
<Buddy_Flynn@dssihq.com>
> >> wrote:
> >> >Hello,
> >> >We just installed InstallShield Express 3.03, and migrated the our
> >previous
> >> >..ism files over. Now I'm getting this error:
> >> >
> >> >"Error 1406. Could not qrite value 409 to key
> >> >HKEY_LOCAL_MACHINE\Software\Classes\Component
> >> >Categories\{40FC6ED5-2438-11CFA3DB-080036f12502}. Verify you have
> >sufficient
> >> >access to that key, or contact your support personal."
> >> >
> >> >I tried logging on as the administrator and still got the same error.
If
> >you
> >> >click Ignore,the same error is repeated a couple more time with
different
> >> >keys but the install completes and the program seems to run OK. Any
> >ideas?
> >> >
> >> > Thanks,
> >> > Buddy Flynn
> >> >
> >> >
> >
> >

NewsArchive
09-06-2001, 12:00 AM
It's a "Standard" project.

Steve

Mingbiao Fei <mf@installshield.com> wrote in message
news:3b97e666$1@news.installshield.com...
> Steve:
>
> Are you using basic MSI project type or this is a standard project type?
>
> Fei
>
> "Steve Weisner" <noreply@nowhere.com> wrote in message
> news:3b97b48c$1@news.installshield.com...
> > I saw some postings last month about Error 1714 (The older version of
> MyApp
> > cannot be removed...) which is causing a fatal error during an upgrade.
> >
> > I am seeing the exact same behaviour, but it looks like the discussion
has
> > been taken offline. Is there a solution for this that could be posted?
> >
> > Any help would be appreciated.
> >
> > Steve
> >
> >
> >
>
>

NewsArchive
09-12-2001, 12:00 AM
Hi Chandima,

It seems to be working... Thanks !!!!
I spent hours searching for this but didn't find it.

Thanks again !!

Wim

"Chandima Rajakaruna" <no reply@installshield.com> wrote in message
news:3b9f5dc1$1@news.installshield.com...
> This is probably because your Product Code changed between projects.
Windows
> Installer 1.2 does not Support Major upgrades. Try the following approach
> when creating your patch.
>
> Create your first setup.
> Build (using default)
> Do a Save As and change the project name (This was you have the same
Product
> Code in second project)
> Change the Package Code (in Summary info)
> Change Version number of necessary
> Either replace old file with newer file, or new files to an existing
> component
> Do NOT add a new component to an existing feature (This won;t install due
to
> a limitation with Windows Installer 1.2)
> Build (using default)
>
> Now create a patch between the two projects.
>
> "news.installshield.com" <sorry@nospam.be> wrote in message
> news:3b9f1ba7@news.installshield.com...
> > Hi,
> >
> > I'm just starting with InstallShield Developer 7 and have an annoying
> > problem I just seem to be unable to find the solution for.
> >
> > I created a simple project (installation procedure only contains 1
> > executable).
> > I created a second simple project (containing another executable): the
> > intention is to have the first executable patched to the second.
> > Projectype: "Basic MSI"
> > For both projects I do a default Build.
> >
> > I launch the patch wizard, leave all settings to default and indicate
that
> I
> > want to patch between the first project and the second project. The
wizard
> > finds the differences between the 2 projects and creates an .msp file.
> >
> > Then doing the test:
> > - I install the first version: OK
> > - I apply the patch: OK
> > When I retry to apply the patch, I get "Error 1316: A network error
> occurred
> > while attemting to to read from the file c:\winnt\installer\test.msi"
> > I fact the file is not there, but it was not even there after the
initial
> > install or the first patch.
> >
> > I will probably do something wrong (Patch GUIDs to be ignored, DiskID,
> > FileID, ... ???) I experimented with these settings to no avail. Perhaps
> the
> > fact I do use two different projects causes this problem ... ? ...
> >
> > I didn't find any solutions on the Microsoft sites either...
> >
> > Thanks in advance,
> >
> > Wim Lambrechts
> >
> >
> >
>
>

NewsArchive
09-13-2001, 12:00 AM
> Were both of your msi files buitl using Developer? If the first was built
> using 2.03, the patch will not work due to a schema change in the msi from
> 1.2 to 2.0.
Yes, both Developer.

> Are you trying to do a Major Upgrade (Product Versions differ)? This is
not
> possible due to a bug in Windows Installer 1.2.
No

> Is this a Standard Project or a Msi Only Project? If it's a standard
> project, have you added the OnPatchUIBefore and OnPatchUIAfter funtions to
> the installscript?
Standard Projects. Didn't know about OnPatchUIBefore and OnPatchUIAfter.
Do I need add any code to these added functions? Didn't see any mention of
them in the Help documentation for adding patches.

> According to msi patching rules for Windows Installer 1.2, you cannot:
> 1. change the primary keys in the File Table between the original and new
> .msi file versions
> 2. move files from one folder to another
> 3. move files from one cabinet to another
> 4. change the order of files in a cabinet
> 5. add a new component to an existing feature
>
> Are you doing any of the above mentioned?
No

> Is your first version distributed as a Compressed Single Image? If so try
> running the patch after installing the first version with an UNCOMPRESSED
> build.
Not compressed.

Thanks for your response. I will try the two functions you mention.

NewsArchive
09-13-2001, 12:00 AM
In the Second project,

Go to the Installscript view
Select Setup.rul and move cursor to end of script
Select "Miscellaneous" from the Combo Box on Left
Select "Patch UI Before" and "Patch UI After" from the Combo box on Right

That's all you have to do. The default code is enought to get the patch
working.

"David Franck" <franck@truedisk.com> wrote in message
news:3ba0f349$1@news.installshield.com...
> > Were both of your msi files buitl using Developer? If the first was
built
> > using 2.03, the patch will not work due to a schema change in the msi
from
> > 1.2 to 2.0.
> Yes, both Developer.
>
> > Are you trying to do a Major Upgrade (Product Versions differ)? This is
> not
> > possible due to a bug in Windows Installer 1.2.
> No
>
> > Is this a Standard Project or a Msi Only Project? If it's a standard
> > project, have you added the OnPatchUIBefore and OnPatchUIAfter funtions
to
> > the installscript?
> Standard Projects. Didn't know about OnPatchUIBefore and OnPatchUIAfter.
> Do I need add any code to these added functions? Didn't see any mention
of
> them in the Help documentation for adding patches.
>
> > According to msi patching rules for Windows Installer 1.2, you cannot:
> > 1. change the primary keys in the File Table between the original and
new
> > .msi file versions
> > 2. move files from one folder to another
> > 3. move files from one cabinet to another
> > 4. change the order of files in a cabinet
> > 5. add a new component to an existing feature
> >
> > Are you doing any of the above mentioned?
> No
>
> > Is your first version distributed as a Compressed Single Image? If so
try
> > running the patch after installing the first version with an
UNCOMPRESSED
> > build.
> Not compressed.
>
> Thanks for your response. I will try the two functions you mention.
>
>
>
>

NewsArchive
09-13-2001, 12:00 AM
Ok, I got it to work with the OnPatchUIBefore and OnPatchUIAfter functions
in place. Thanks!

But my next question: is there anyway to get a patch to work if the first
version is distributed as a Compressed Single Image?

NewsArchive
09-14-2001, 12:00 AM
Do you still have the Version 1 ism? If so do an uncompressed build of it
and use that msi to generate your patch. If I am not mistaken this should
still update any distributed version, even if it was compressed. Worth a
try.

"David Franck" <franck@truedisk.com> wrote in message
news:3ba12c88$1@news.installshield.com...
>
> Ok, I got it to work with the OnPatchUIBefore and OnPatchUIAfter functions
> in place. Thanks!
>
> But my next question: is there anyway to get a patch to work if the first
> version is distributed as a Compressed Single Image?
>
>

NewsArchive
09-14-2001, 12:00 AM
Yes, I have been trying to do it the way you suggest and it only works if I
install the first version using the uncompressed build. If I install using
the compressed build, I get the 1706 error everytime. I really can't use
the patching tool if I can't have the compressed build to be the default.

Thanks for you help. Let me know if InstallShield decides to fix this.


"Chandima Rajakaruna" <no reply@installshield.com> wrote in message
news:3ba2087a$1@news.installshield.com...
> Do you still have the Version 1 ism? If so do an uncompressed build of it
> and use that msi to generate your patch. If I am not mistaken this should
> still update any distributed version, even if it was compressed. Worth a
> try.
>
> "David Franck" <franck@truedisk.com> wrote in message
> news:3ba12c88$1@news.installshield.com...
> >
> > Ok, I got it to work with the OnPatchUIBefore and OnPatchUIAfter
functions
> > in place. Thanks!
> >
> > But my next question: is there anyway to get a patch to work if the
first
> > version is distributed as a Compressed Single Image?
> >
> >
>
>

NewsArchive
09-14-2001, 12:00 AM
> Windows Installer 1.2 does not Support Major upgrades.

I was not aware of this. I thought that was a limitation only in
version 1.0. Is that documented anywhere?

--
Stefan Krueger - Independent Setup Consultant

InstallSite - code samples, tips, tools, bug lists, and more
http://www.installsite.org http://www.installsite.de (GERMAN)
Support and consulting http://www.installsite.org/krueger

Stefan Krueger and the InstallSite web site are not affiliated
with InstallShield Software Corporation.

NewsArchive
09-20-2001, 12:00 AM
Had an idea. For your Verison 1 setup, make a compressed network image (as
you already have). Now in the Release Settings, set the "Cache Web Download"
property to "Yes" and give a location to the "Cache Path" property. Build
and install verison 1. This will make a copy of the msi to location you
mentioned and I think it run's the setup from there. So when you apply the
patch, it will uninstall from this location. Try the same scenario after a
reboot as well to make sure the msi wasn't cleaned out.

"David Franck" <franck@truedisk.com> wrote in message
news:3ba232ea$1@news.installshield.com...
> Yes, I have been trying to do it the way you suggest and it only works if
I
> install the first version using the uncompressed build. If I install
using
> the compressed build, I get the 1706 error everytime. I really can't use
> the patching tool if I can't have the compressed build to be the default.
>
> Thanks for you help. Let me know if InstallShield decides to fix this.
>
>
> "Chandima Rajakaruna" <no reply@installshield.com> wrote in message
> news:3ba2087a$1@news.installshield.com...
> > Do you still have the Version 1 ism? If so do an uncompressed build of
it
> > and use that msi to generate your patch. If I am not mistaken this
should
> > still update any distributed version, even if it was compressed. Worth a
> > try.
> >
> > "David Franck" <franck@truedisk.com> wrote in message
> > news:3ba12c88$1@news.installshield.com...
> > >
> > > Ok, I got it to work with the OnPatchUIBefore and OnPatchUIAfter
> functions
> > > in place. Thanks!
> > >
> > > But my next question: is there anyway to get a patch to work if the
> first
> > > version is distributed as a Compressed Single Image?
> > >
> > >
> >
> >
>
>

NewsArchive
10-01-2001, 12:00 AM
Is this a standard or basic project?

I think there is some problem with the Directory table. Can you post your
directory table?

Kent

"dsanborn" <dsanborn@home.com> wrote in message
news:3bb8ed68$1@news.installshield.com...
> Colin,
> I've got the exact same problem (well almost). Mine gives me "Error 1606.
> Could not access network location False". I'm in the same boat. For the
> life of me, I can't find the root of the problem.
>
> Help!
> Don
>
>
> "Colin Ronayne" <cronayne@hotmail.com> wrote in message
> news:3bb8a307$1@news.installshield.com...
> > "Error 1606. Could not access network location True" Does this mean
that
> it
> > is looking for a directory called True, or is it True that it can't find
> the
> > network location. This error appears at the CostFinalise Action, and I
> cant
> > seem to figure it out. Any help would be appreciated. Thanks,
> > Colin.
> >
> >
>
>

NewsArchive
10-01-2001, 12:00 AM
Kent,
Here's by Directory table. Thanks for the help.

Don


"Kent Foyer" <no@address.com> wrote in message
news:3bb8f76d$1@news.installshield.com...
> Is this a standard or basic project?
>
> I think there is some problem with the Directory table. Can you post your
> directory table?
>
> Kent
>
> "dsanborn" <dsanborn@home.com> wrote in message
> news:3bb8ed68$1@news.installshield.com...
> > Colin,
> > I've got the exact same problem (well almost). Mine gives me "Error
1606.
> > Could not access network location False". I'm in the same boat. For
the
> > life of me, I can't find the root of the problem.
> >
> > Help!
> > Don
> >
> >
> > "Colin Ronayne" <cronayne@hotmail.com> wrote in message
> > news:3bb8a307$1@news.installshield.com...
> > > "Error 1606. Could not access network location True" Does this mean
> that
> > it
> > > is looking for a directory called True, or is it True that it can't
find
> > the
> > > network location. This error appears at the CostFinalise Action, and
I
> > cant
> > > seem to figure it out. Any help would be appreciated. Thanks,
> > > Colin.
> > >
> > >
> >
> >
>
>

NewsArchive
10-01-2001, 12:00 AM
Kent,
I forgot to answer your question... This is a standard project.

Also, I took another cold look at the Directory table. I removed the
entries 'CRISIS_2000' and 'DefaultDir1' and then I changed INSTALLDIR so
that it's parent is ISYourProductDir (to follow the standard install
location).

Now I'm getting "Error 1606. Could not access network location True" instead
of 'False'.

Is that progress or what!

Don



"Kent Foyer" <no@address.com> wrote in message
news:3bb8f76d$1@news.installshield.com...
> Is this a standard or basic project?
>
> I think there is some problem with the Directory table. Can you post your
> directory table?
>
> Kent
>
> "dsanborn" <dsanborn@home.com> wrote in message
> news:3bb8ed68$1@news.installshield.com...
> > Colin,
> > I've got the exact same problem (well almost). Mine gives me "Error
1606.
> > Could not access network location False". I'm in the same boat. For
the
> > life of me, I can't find the root of the problem.
> >
> > Help!
> > Don
> >
> >
> > "Colin Ronayne" <cronayne@hotmail.com> wrote in message
> > news:3bb8a307$1@news.installshield.com...
> > > "Error 1606. Could not access network location True" Does this mean
> that
> > it
> > > is looking for a directory called True, or is it True that it can't
find
> > the
> > > network location. This error appears at the CostFinalise Action, and
I
> > cant
> > > seem to figure it out. Any help would be appreciated. Thanks,
> > > Colin.
> > >
> > >
> >
> >
>
>

NewsArchive
10-02-2001, 12:00 AM
Eureka!
I found the problem. This was an old project that I converted from an older
InstallShield. The script was passing a value to a registry setting via one
of the directory entries. I changed the approach and we're off to the
races!

Don



"dsanborn" <dsanborn@home.com> wrote in message
news:3bb9531f@news.installshield.com...
> Kent,
> I forgot to answer your question... This is a standard project.
>
> Also, I took another cold look at the Directory table. I removed the
> entries 'CRISIS_2000' and 'DefaultDir1' and then I changed INSTALLDIR so
> that it's parent is ISYourProductDir (to follow the standard install
> location).
>
> Now I'm getting "Error 1606. Could not access network location True"
instead
> of 'False'.
>
> Is that progress or what!
>
> Don
>
>
>
> "Kent Foyer" <no@address.com> wrote in message
> news:3bb8f76d$1@news.installshield.com...
> > Is this a standard or basic project?
> >
> > I think there is some problem with the Directory table. Can you post
your
> > directory table?
> >
> > Kent
> >
> > "dsanborn" <dsanborn@home.com> wrote in message
> > news:3bb8ed68$1@news.installshield.com...
> > > Colin,
> > > I've got the exact same problem (well almost). Mine gives me "Error
> 1606.
> > > Could not access network location False". I'm in the same boat. For
> the
> > > life of me, I can't find the root of the problem.
> > >
> > > Help!
> > > Don
> > >
> > >
> > > "Colin Ronayne" <cronayne@hotmail.com> wrote in message
> > > news:3bb8a307$1@news.installshield.com...
> > > > "Error 1606. Could not access network location True" Does this mean
> > that
> > > it
> > > > is looking for a directory called True, or is it True that it can't
> find
> > > the
> > > > network location. This error appears at the CostFinalise Action,
and
> I
> > > cant
> > > > seem to figure it out. Any help would be appreciated. Thanks,
> > > > Colin.
> > > >
> > > >
> > >
> > >
> >
> >
>
>

NewsArchive
11-02-2001, 01:00 AM
Thanks for your reply. Yes, it does. However, I cleaned out the binary table
(via Power Editor) to no avail. I got to looking in the Intern directory and
saw remnants of test scripts. I deleted everything, re-created the script,
and sure enough, problem resolved. It appears bogus scripts in that
directory will cause a problem.

Thanks again for the help!

"Johannes John" <jn@rib.de> wrote in message
news:3be2b2cb@news.installshield.com...
> Hello Mike,
>
> does the compilation of your script file run without error?
> I find my setup.inx files in the ...\build\intern directory.
>
> Regards!
> Johannes
>
>
> "Mike Bevan" <mike.bevan@matrixsys.com> schrieb im Newsbeitrag
> news:3be2a6ef@news.installshield.com...
> > I keep getting error -1024 whenever I create a custom action. the
message
> > says:
> >
> > .\Setup.inx not found. Cannot stream the file into the binary table.
> >
> > If I take the custom action out, the build works ok. I'm very new to
this,
> > so I was just attempting to launch notepad during the install so I can
> > launch a batch file in "real life" when I'm done testing/learning.
> >
> > #include "isrt.h"
> > #include "iswi.h"
> >
> > export prototype LaunchNotepad(HWND);
> >
> > function LaunchNotepad(hMSI)
> > begin
> >
> > LaunchAppAndWait("C:\\WINNT\\notepad.exe", "", WAIT);
> >
> > end;
> >
> > Any help ASAP would be greatly appreciated.
> >
> >
> >
> >
>
>

NewsArchive
11-06-2001, 01:00 AM
Would you post your log file? Below is a KB on how to do it.

HOWTO: Logging a Standard Based Project
Document ID: Q105237
This article applies to the following:
Product(s): InstallShield Developer 7.0
Last Revised On: 08/07/2001

Summary
In order to create a log file that records the progress of a standard based
installation, you can either execute the setup.exe at the command line using
the /Verbose switch or you can set a specific registry entry. The log file
can be used to diagnose the cause of failure or unexpected behavior in an
installation.


----------------------------------------------------------------------------
----


Discussion
To log a standard installation via setup.exe one will need to run a command
line similar to the following:
Setup.exe /Verbose"d: \place for logs\package.log"

Running the above command line will log everything verbosely.

The other option would be to set the following registry entry:

HKCU\Software\InstallShield\ISWI\3.0\SetupExeLog\VerboseLogFileName, where
the value should be your full log path.

If the above registry entry is set, a log file will be generated every time
the standard project is run.

"Mike Watkins" <mwatkins@codesprings.com> wrote in message
news:3be7dd8f$1@news.installshield.com...
> HI,
>
> I am also getting error 1628 when trying to install my application. This
> seems to have only happened since I upgraded to installshield developer
> 7.01. Now none of my setups work on machines that do not already have the
> latest MSI engine on them. What is going on?
>
> I am going to try un-installing ISD completely and then re-installing off
> the CD to see if it fixes the problem. I will let you know.
>
> Mike
>
> "Dan Decasper" <ddd@jibenetworks.com> wrote in message
> news:3be70c06@news.installshield.com...
> > We are trying to produce a very simple upgrade of a single feature
> > application (standard mode, maintenance mode off). As far as I know, all
> we
> > have to do is change the package code and the version number. However,
> when
> > I try to install a new version on a system which has the old one, I'm
> > getting
> >
> > 1628: Failed to complete installation
> >
> > What am I missing here?
> >
> > Thanks,
> >
> > -Dan
> >
> >
> >
> >
>
>

NewsArchive
11-09-2001, 01:00 AM

NewsArchive
11-13-2001, 01:00 AM

NewsArchive
11-14-2001, 01:00 AM
Yes, it's related to a custom action that was installed with the setup. Maybe
I could add a condition to the custom action so that it would not be launched
in maintenance mode.

I have a question about those status properties that are set by the installer
at run time, e.g. Installed.. If I am in the process of uninstalling, but
have not completed. Is "Installed" set to true or false? In other words,
executing which action changes "Installed" from true to false?

Thanks.


Kent Foyer wrote:

> I have seen this before with custom actions. Specifically, if you are
> launching a file that was installed with the setup. Anyway, I think the
> problem may be related to a custom action. After doing a quick search in
> MSDN and MSI help, I couldn't find any helpful information on what the
> problem may be.
>
> Kent
>
> "Josephine Cai" <josephine@kurzweiledu.com> wrote in message
> news:3BF2A761.E0559672@kurzweiledu.com...
> > Hi,
> >
> > When I tried to uninstall, I got the following error:
> >
> > Error 1721: There is a problem with this windos installer package. A
> > program required for this install to complete cold not be run.
> >
> > Anyboday has any idea?
> >
> > Thanks,
> > Jo
> >

NewsArchive
11-14-2001, 01:00 AM
Installed has a value if the product is installed (some part of that product
has previously been installed), so if you're in maintenance mode Installed
has a value. Strictly speaking, it doesn't have a value of "True" or "1" -
if you ever do a VBScript CA that does a Msgbox on the value, you'll see
it's a date/time string, so don't test it for 1 or True.

"Josephine Cai" <josephine@kurzweiledu.com> wrote in message
news:3BF2DAC5.2A9B048@kurzweiledu.com...
>
> Yes, it's related to a custom action that was installed with the setup.
Maybe
> I could add a condition to the custom action so that it would not be
launched
> in maintenance mode.
>
> I have a question about those status properties that are set by the
installer
> at run time, e.g. Installed.. If I am in the process of uninstalling, but
> have not completed. Is "Installed" set to true or false? In other words,
> executing which action changes "Installed" from true to false?
>
> Thanks.
>
>
> Kent Foyer wrote:
>
> > I have seen this before with custom actions. Specifically, if you are
> > launching a file that was installed with the setup. Anyway, I think the
> > problem may be related to a custom action. After doing a quick search
in
> > MSDN and MSI help, I couldn't find any helpful information on what the
> > problem may be.
> >
> > Kent
> >
> > "Josephine Cai" <josephine@kurzweiledu.com> wrote in message
> > news:3BF2A761.E0559672@kurzweiledu.com...
> > > Hi,
> > >
> > > When I tried to uninstall, I got the following error:
> > >
> > > Error 1721: There is a problem with this windos installer package. A
> > > program required for this install to complete cold not be run.
> > >
> > > Anyboday has any idea?
> > >
> > > Thanks,
> > > Jo
> > >
>

NewsArchive
11-16-2001, 01:00 AM
Bump

I have tried everything I know to do. I have unchecked it, rebuilt it,
checked it again, and rebuilt it again. Still it gives the same error. I
have looked in the tables and have checked to see if the component is valid
and everything else I know to check. All of my other ODBC DSNs work fine,
why is this one giving my so much trouble?!? Also, it worked in the past.
"Martin Markevics" <martinm@installshield.com> wrote in message
news:3be9b3e8$1@news.installshield.com...
Are you creating the MTS Practice ODBC data source with your install. Can
you look at the ODBCDataSource table in the Direct Editor view of your
project. Does this Component_ column for this Data Source reference a valid
component? Run MSI validation on your project. Select Build | Validate |
Full MSI Validation Suite from the menu. Are there any validation errors
related to this Data Source?

--
Martin
InstallShield Software Corp.
"Adam Watkins" <Adam.Watkins@ccci.org> wrote in message
news:3be9acdf@news.installshield.com...

What exactly does this error mean? I looked in the help and it didn't
help... I am running Windows 2000 and it already has ODBC functionality.
Other ODBC connections work, just this one gives problems.

Thanks,

Adam Watkins

NewsArchive
11-19-2001, 01:00 AM
Thanks, that solved it.

"Nikolaus Schmitt" <n.schmitt@scaet.de> wrote in message
news:3bf32289$1@news.installshield.com...
> Recheck the components directory location. The ISDEV UI sometimes acts a
bit
> strange ...
> Build the setup without packing and compressing.
> Enable full logging:
> Standard project: setup.exe /verbose /f1:c:\myis.log /V"/L*v c:\mymsi.log"
> Analyze the MSI log. Since 1308 is an MSI error, the "source" information
> should be somewhere in the MSI log file.
>
>
> "Nick Mooney" <nicholas_mooney@nospamhotmail.com> wrote in message
> news:3bf320fe@news.installshield.com...
> > OK, I have a file which I placed in Component System. Orginally, I had
> > forgotten to specify the destination as the system folder. I built
> several
> > releases and when it came time to use this file (a dll) I discovered my
> > error.
> >
> > So, I moved the file to the correct location and it is stored correctly
in
> > the build image. However, InstallShield is still trying to locate it at
> the
> > previous source location. I have looked at the tables directly, I have
> > changed everything I can think of to get the installer to work. I still
> get
> > an error 1308 saying the source file doesn't exist.
> >
> > Anyone have any ideas?
> >
> > Thanks,
> > Nick
> >
> >
>
>

NewsArchive
12-11-2001, 01:00 AM
I can not use v7.01 because of bugs that I have already submitted concerning
this version and update patches. I am waiting for v7.02 so I can evaluate
the need for Windows Installer 2.0 and it's impact on my userbase (requiring
NT Service Pack 6, etc).

This error pops up a few seconds after the installation program is started.
Yes, I do have a few custome actions. They are simple actions that check for
the existence of 2 registry entries, and set an Installshield property
accordingly. I just want to know what error 1645 is, and what causes it.

"Martin Markevics" <martinm@installshield.com> wrote in message
news:3c1639e7$1@news.installshield.com...
> Make sure you get the current MP, 7.01. It may or may not be related to
this
> issue, but there were a number of fixes in 7.01 that you should get (also
> 7.02 is due out shortly). When do you get this error? Do you have any
> InstallScript custom actions?
>
> --
> Martin
> InstallShield Software Corp.
>
>
> "Derick Bailey" <dbailey@airsysco.com> wrote in message
> news:3c162c6c@news.installshield.com...
> > ISDEV 7.0, BASIC MSI Project.
> >
> > what is error 1645 and why would it show up when trying to run an
> > installation created with ISDEV 7.0? I cannot find any documentation
> > (Installshield or Microsoft) concerning this error.
> >
> > HELP!
> >
> > -Derick.
> >
> >
>
>

NewsArchive
12-11-2001, 01:00 AM
The reason I asked if you have InstallScript custom actions is to find out
if you are using the InstallScript engine which apparently you are. Error
1645 was only in Developer 7.0. We changed the way we install the script
engine somewhat for 7.01 so 1645 is now a non-issue.

Anyway, 1645 comes up when we are unable to remove the scripting engine. If
there is an older version of the script engine, we removed it and then
install the new version. Can you run isscript.msi from your Disk1 folder
manually? Does the (un)install complete successfully?

Also, you are more than welcome to take it off line with me as far as what
bugs are preventing you from going to 7.01. I don't know of anything
(granted I don't have a list in front of me or know your specific issue(s))
that we broke from 7.0 to 7.01 while there were numerous fixes. Also, I'm
rather confident that 7.01 would solve this issue as well. Again, feel free
to contact me off-line if you have any concerns about this.

--
Martin
InstallShield Software Corp.

"Derick Bailey" <dbailey@airsysco.com> wrote in message
news:3c168629$1@news.installshield.com...
> I can not use v7.01 because of bugs that I have already submitted
concerning
> this version and update patches. I am waiting for v7.02 so I can evaluate
> the need for Windows Installer 2.0 and it's impact on my userbase
(requiring
> NT Service Pack 6, etc).
>
> This error pops up a few seconds after the installation program is
started.
> Yes, I do have a few custome actions. They are simple actions that check
for
> the existence of 2 registry entries, and set an Installshield property
> accordingly. I just want to know what error 1645 is, and what causes it.
>
> "Martin Markevics" <martinm@installshield.com> wrote in message
> news:3c1639e7$1@news.installshield.com...
> > Make sure you get the current MP, 7.01. It may or may not be related to
> this
> > issue, but there were a number of fixes in 7.01 that you should get
(also
> > 7.02 is due out shortly). When do you get this error? Do you have any
> > InstallScript custom actions?
> >
> > --
> > Martin
> > InstallShield Software Corp.
> >
> >
> > "Derick Bailey" <dbailey@airsysco.com> wrote in message
> > news:3c162c6c@news.installshield.com...
> > > ISDEV 7.0, BASIC MSI Project.
> > >
> > > what is error 1645 and why would it show up when trying to run an
> > > installation created with ISDEV 7.0? I cannot find any documentation
> > > (Installshield or Microsoft) concerning this error.
> > >
> > > HELP!
> > >
> > > -Derick.
> > >
> > >
> >
> >
>
>