Error on executing SB 6.5 on Vista

[NewsArchive]

I'm using SB 6.5 1953.

Lately (Today, in fact), a message started to appear on SB startup:

SetupBuilder 6.5
[1] Variable name too long.
Script line:

That's all.
Then, upon Accept, another message:
SetupBuilder 6.5.1953
This application has encountered a problem and needs to close. Please contact
the vendor of the application. Error# 0007:0005

Then, SB starts.
I'm having the same error on my own WUpdate programs.
I already restart the machine.
Any idea?

--
Jorge Alejandro Lavera
www.ClarionTemplates.com
www.InBack.com

[NewsArchive]

Hi Jorge,

Sorry, I have never ever seen this before. I fear it is machine specific
(and nothing we can do).

Friedrich

[NewsArchive]

BTW, what you can do is to check if one of your "protection products" does
something with wupdate.exe. I am sure it is related to one of your recent
updates (virus or spyware tools, etc.).

HTH,
Friedrich

[NewsArchive]

Hi All,

Jorge posted a message regarding error 0007: 0005 being posted when he
attempts to run SB (see above). He also has told me that he was never able
to determine the cause and had to go back to XP to resolve his problems.

I now have received an Email from a customer reporting the same error, only
his error is being reported when he attempts to run an install created with
SB. His explanation is below:

** Begin **
Tried to install the trial version of your software program on Windows
Vista. When I tried to install I get the following error (Setup Builder
6.5.1852)

Application has encountered a problem and needs to close. Please contact the
vendor of this installation.
Error # 0007: 0005

I also tried to run the file as Administrator, but no luck. Help!
** End **

I am confident the issue *DOES NOT* lie with SB, but....

Has anyone else seen this error?
Does anyone have even so much as a guess what might be causing this error?
What can be done to fix it?

Thanks.

--
Regards,

Lee
http://www.cya2day.com

[NewsArchive]

Hi Lee,

> I am confident the issue *DOES NOT* lie with SB, but....
>
> Has anyone else seen this error?
> Does anyone have even so much as a guess what might be causing this error?
> What can be done to fix it?

This is an unspecified error. The SetupBuilder loader reports it after it
tried to initialize parts of the installer. Perhaps his temporary folder is
full, does not allow access, a security software locks it, or something
similar. A download transmission error can also cause it. But this error
is too unspecified to definitely find out where or why it happens.

If you are interested, please ask your customer to run your installer in
"event logging mode" (if you have not disabled it). The /E command line
switch starts the installer in event logging mode, e.g. test.exe /E

This will create a file named c:\sbevents.txt

Please ask your customer to send you this file and then forward it to
support (at) lindersoft (dot) com.

Perhaps this file will give us more information (but I am not sure). If the
error occurs before event logging is initialized then we are lost.

HTH,
Friedrich

[NewsArchive]

Hi Friedrich,

Thank you for the reply.

I don't recall ever seeing this switch. Where is it located in the IDE so I
can determine that it is active on my customers install EXE? I can't find
any reference to event logging in the help other than on the "Command Line
Options - Installer" page.

--
Regards,

Lee
http://www.cya2day.com

[NewsArchive]

Hi Lee,

The following would disable installer event capability:

Set Installer Flag $SB_DISABLEEVENTLOGFLAG$ to "1"

Friedrich

[NewsArchive]

Hi Friedrich,

I have not set such a flag so I must assume the event logging has not been
disabled. I confirmed this by running the install with /E on the command
line and it did produce the log.

I will see if my customer will do this and send me the log file.

Thanks for your help.

--
Regards,

Lee
http://www.cya2day.com