PDA

View Full Version : Express 2 : Error Number -1. Unknown Error - why is this happening constantly?



NewsArchive
02-04-1998, 01:00 AM
I am getting this error constantly when trying to build a Delphi-based
project. I see 4 blocks of progress and 'Building setup data' when this
error appears - it is a nuisance. Can anyone help? Is there a patch
available? I have re-installed the software twice (the Microsoft engineer
bit) with no luck.

Regards

Darren Drysdale
darrendrysdale@email.msn.com

NewsArchive
02-06-1998, 01:00 AM
Hi Darren,
Where is your .iwz file located. If it is in a UNC path, it may be the
cause of the problem. Refer to the attached KB article for an explanation.
--
Rich
InstallShield Software Corp.


P.S. Our website, http://www.installshield.com/, covers a wide range of
resources for your installation development. Read technical whitepapers,
view documentation or search the Knowledge Base to get support information
24 hours a day, 7 days a week.



PRB: A "Number -1 Unknown Error" Message Is Displayed While Running Disk
Builder
Document ID: Q101269

This article applies to the following:
Product(s): All InstallShield Express Editions
Last Revised On: 10/6/1997

Summary
An "Error number -1. Unknown error" message is displayed while running Disk
Builder on your project.



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

Discussion
This error message is generated by one of the three DOS programs used by
Disk Builder while creating your setup's disk images. This message may be
displayed if your InstallShield Express project's .iwz file is opened or
saved on a network resource using a Uniform Naming Convention (UNC) path
name (for example: \\Test\MyProject.iwz). In this case, the DOS programs
used to compress your setup's files and split the compressed library over
your distribution media will not understand that the current directory is a
UNC path. The same may hold true if your copy of InstallShield Express is
located on a network resource and accessed with a UNC path name, since this
will be the current directory from which Disk Builder (and the DOS programs
it utilizes) is run. No files outside of this current directory will be
accessible.

If your InstallShield Express checkpad interface has a UNC path name under
the toolbar (above the "Setup Checklist" title), then this may be the cause
of the problem. Please use only standard DOS paths when opening or saving
your InstallShield Express project's .iwz file. If you have InstallShield
Express installed on a network, please make sure that this network resource
is mapped to a drive letter.

Note: This problem does not affect using UNC paths for the locations of your
setup's source files.


Peter Crawford wrote in message <34d891b4.0@news.installshield.com>...
>
>I am getting this error constantly when trying to build a Delphi-based
>project. I see 4 blocks of progress and 'Building setup data' when this
>error appears - it is a nuisance. Can anyone help? Is there a patch
>available? I have re-installed the software twice (the Microsoft engineer
>bit) with no luck.
>
>Regards
>
>Darren Drysdale
>darrendrysdale@email.msn.com
>
>

NewsArchive
03-11-1998, 01:00 AM
I had the same problems, repeatedly and all paths are local, no UNC
paths anywhere. I've come across this problem a number of times now, and
sometimes making a complete new instalation file seems to solve the
problem, but not always. Would love to hear any other causes than the
UNC paths.

Regards, Aiko Gieskens


> Hi Darren,
> Where is your .iwz file located. If it is in a UNC path, it may be the
> cause of the problem. Refer to the attached KB article for an explanation.

> >I am getting this error constantly when trying to build a Delphi-based
> >project. I see 4 blocks of progress and 'Building setup data' when this
> >error appears - it is a nuisance. Can anyone help? Is there a patch
> >available? I have re-installed the software twice (the Microsoft engineer
> >bit) with no luck.


-------------------------------------------------
| E Y E |
| Aiko Gieskens C O M |
| aiko@euronet.nl I M A |
| G E S |
-------------------------------------------------

NewsArchive
03-11-1998, 01:00 AM
On Wed, 11 Mar 1998 17:26:10 +0100, Aiko Gieskens <aiko@euronet.nl> wrote:
>I had the same problems, repeatedly and all paths are local, no UNC
>paths anywhere. I've come across this problem a number of times now, and
>sometimes making a complete new instalation file seems to solve the

Look for recursive directories in your groups, e.g. one group might point
to a group which in turn points to another, which points back to the first.

Stefan
ellipse data systems

NewsArchive
03-12-1998, 01:00 AM
Stefan Paetow wrote:
>
> On Wed, 11 Mar 1998 17:26:10 +0100, Aiko Gieskens <aiko@euronet.nl> wrote:
> >I had the same problems, repeatedly and all paths are local, no UNC
> >paths anywhere. I've come across this problem a number of times now, and
> >sometimes making a complete new instalation file seems to solve the
>
> Look for recursive directories in your groups, e.g. one group might point
> to a group which in turn points to another, which points back to the first.

Thanks, but nope, that's not it either. To make it even uncannier, the
error not always occurs at the same point with the same installshield
project. What deserves mentioning is that they're quite big projects
(about 120 directories/subdirectories). Sometimes it might be after a
good 40 that it gives this message, and sometimes maybe 70 or 80 might
be done succesfully before this message comes along.

-------------------------------------------------
| E Y E |
| Aiko Gieskens C O M |
| aiko@euronet.nl I M A |
| G E S |
-------------------------------------------------

NewsArchive
03-12-1998, 01:00 AM
On Thu, 12 Mar 1998 10:29:03 +0100, Aiko Gieskens <aiko@euronet.nl> wrote:
>(about 120 directories/subdirectories). Sometimes it might be after a
>good 40 that it gives this message, and sometimes maybe 70 or 80 might
>be done succesfully before this message comes along.

Ok, let's assume that the error occurs at 40 groups. Is it the same project
that spews out the error after about 70 groups on other PCs? Or are those
different projects?

What I'mn trying to establish with this is to find out if there are any
memory issues involved.

Stefan
ellipse data systems