Problem running installer on Windows 2003 R2

Friedrich,

I'm using the latest build of SB5. When I try to run the install on Windows
2003 R2 at a client site I get
"This application has encountered a problem and needs to close. 002:000998.

Best Regards,

Michael Gould

Michael,

The temporary Windows folder seems not to be accessible. The loader is
unable to unpack and link the decompression library.

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 5

FYI: we'll make the loader a little bit smarter in the next build. If the
temporary Windows folder is not accessible, the loader will try to unpack
to the root of c:\. More and more administrators limit the access to the
Windows temp folder.

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 5

Friedrich,

Would it be possible for us to define this folder in the script via a
variable or a command line option? For example, I just talked to the system
administrator at this site. He's locked down the Windows temporary folder
as well as the C:\, however he said I can create a temp file under the
application directory.

Best Regards,

Michael Gould

Michael,

The problem is this happens when the installer initializes itself. The
loader "stub" (this app reported the error) unpacks the decompression
library, then loads the decompression/encryption library and initializes
the script engine). In other words, the script engine is not available.

I think a good option would be a command line switch. If such an error
is detected, the user can start the installer with a command line switch
to define a valid temporary folder. I like your idea very much. Thank
you! I'll see what we can do here...

Friedrich

Friedrich,

Thanks for taking the time to look at this.

Best Regards,

Michael Gould

BTW, some protection packages scan (temp) folder activity. If something
is (temporary) installed to the temp Windows folder (or other folders),
the software removes the file immediately. The SetupBuilder loader error
0002:xxxxxxx always means that the LoadLibrary Windows API failed. Because
you did not get a 0001:xxxxxxx error, the loader was able to copy files to
the Windows temp folder. But milliseconds after that, something happened
(access restricted, file deleted, etc.) and the loader was unable to
LoadLibrary the decompression DLL.

This can also happen if the Windows temp folder is set to a shared folder
(see errorcode thread by Jean-Pierre GUTSATZ).

Friedrich

Hi,

I don't think this is the issue. I just checked with my guy out in SLC
doing an install. He's on as administrator and can install under
InstallShield the Sybase CD as well as another product called OTN. Both of
which extracts to the TEMP as well. But, he's getting the same exact error
message on two different Setup Builders. 100% sure he's on with full access
to the box.

The person doing this is our vice-president, and he knows computers well.
He flew out there this morning and he comes back on Saturday. His training
starts tomorrow and the pgm doesn't install. I've walked him through
configuring it all manually via the registry and manually placing the Sybase
ODBC objects in the WIN32 directory.

Suggestions?

-Robert

How about rolling back to a previous version of SetupBuilder?

--

Ben E. Brady
The information contained in the message above, as expressed by the author,
is copyright 2006 by Ben E. Brady, All rights strictly reserved worldwide.
The information contained in the message above may not be posted on any
other information forum or web site without the express written permission
of the author.

www.clariondeveloper.com
www.singularvisionsoftware.com
Want OUTRAGEOUS web disk space and bandwidth?
110 GB disk space and 1110 GB transfer per month,
http://www.servage.net/?coupon=CUST13495

Hi Friedrich

Why not use the folder in which the installer is started? I would think this more
acceptable to sysadmins than C: root.
At least in the present folder we will know that the operator has access.

John Griffiths

Hello,

Help ... same issue ... have an installer who went onsite to Salt Lake City
.... there this evening, and can't install our application on the server.
I'd have them run it via a workstation but the install does a lot with the
registry as well as sets up ODBC and places things in the WIN32 directory.

Odd that I didn't / never seen this issue at any site except for today. It
is a Windows 2003 R2 server.

-Robert

Robert,

Nothing changed in the loader stub except:

1. Prototype error fixed. A "long" was expected, but all previous versions
used a "char". Compiler complained about this for a long time.
2. Wrong usage of one LZClose() function. Replaced by CloseHandle()
3. One missing LZClose() function (we hit a 16 file limit on Windows 98
machines).

I have Windows 2003 R2 server here, but cannot reproduce this :-( Perhaps a
new Windows update causes this?

What happens if you run a test installer compiled with a previous SB5
version? Does this work? And if you recompile the test installer with the
new SB56, now it fails?

Friedrich

Robert,

Okay, we have set up a clean "DEP" test machines now (running the latest
Windows x64 on AMD).

When DEP is enabled, all installation executables compiled with SetupBuilder
5.0 - 5.5 result in a "To help protect your computer, Windows has closed
this program." Windows message. If you close the dialog, the installer
GPFs.

Installation executables compiled with the new 5.6 build 1627 result in an
installer Error# 0002:000998 followed by an installer Error#
0002:0004202513. After that a "To help protect your computer, Windows has
closed this program." Windows message is displayed and Windows lets the
installer GPF.

I see the "To help protect your computer, Windows has closed this program."
message on quite a few applications now. Internet Explorer simply generates
a DEP error asking you if you want to make a DEP exception for Internet
Explorer and then crashes. Symantec products causes the same. What the
hell...

We'll try to find out what kind of code in our loader causes this DEP
message.

Friedrich

Robert,

I think we have a solution available now. We'll test it a few more hours
here in-house and then make a test build available.

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 5.6

John,

You can't use the folder where the installer has started. The installer
could be starting from a CD or maybe a Memory Stick that doesn't have enough
memory to decompress.

We require that the person installing is ADMIN and the Setup Builder script
is set to only work under Administrator. Yet, we still have this error ...
so not sure if it is really an ADMIN issue.

-Robert