On Startup, Line 74:Argument 2 must be of type string

[Stein Inge]

Hi

Problem:
I have created an exe and the log at build time show no error messages. But when running the exe I get the error message "On Startup, Line 74:Argument 2 must be of type string"

- How can I troubleshoot this problem?
- How do I see line 74, argument 2?

Question:
When starting the exe on a Vista system I have to approve the irsetup.exe file. My customers seem to think that this might be a virus or something and stop the install at this point.

- Is there any way to make Vista not stop at his file?
-------------

Using Setup Factory v8.1.1004.0 and Vista Business SP2

Best regards
Stein Inge Haaland

[Ulrich]

How can I troubleshoot this problem?

You can inspect the installation log file. If you used extended error reporting, you should be able to see the line that caused the error.

How do I see line 74, argument 2?

Open the Setup Factory IDE, go to Actions, and click the "On Startup" script. Scroll down to line 74 and check the function you have there.

Is there any way to make Vista not stop at his file?

The UAC will always kick in, but you could try to code sign your installer, so the alert will be friendlier to the end user, explaining that a file, digitally signed by you, needs access to the computer to proceed with the installation.

Ulrich

[Stein Inge]

Thanks for your feedback Ulrich, but Im still a bit stuck and need some more input in order to get going with the installation.

You can inspect the installation log file. If you used extended error reporting, you should be able to see the line that caused the error.Ulrich

How can I eneable the exteded error reporting?

Open the Setup Factory IDE, go to Actions, and click the "On Startup" script. Scroll down to line 74 and check the function you have there.
Ulrich

The On startup script show only a total of 36 lines.

The UAC will always kick in, but you could try to code sign your installer, so the alert will be friendlier to the end user, explaining that a file, digitally signed by you, needs access to the computer to proceed with the installation.
Ulrich

My exe is code signed, but that dont help as long as the irsetup.exe dont seems to be? Do you have any other thoughts on this? I guess Im not the only one that see this problem on Vista?

best regards
Stein Inge Haaland

[Ulrich]

How can I eneable the exteded error reporting?

See Project > Log Files > Include action details: Extended Errors. It helps if you set the installation log to "overwrite", so you will document only a single install.

The On startup script show only a total of 36 lines.

Probably the error is happening in a function in a included/global script. This is where the log file can help to narrow down what it is happening.

My exe is code signed, but that dont help as long as the irsetup.exe dont seems to be? Do you have any other thoughts on this? I guess Im not the only one that see this problem on Vista?

If you configured Setup Factory to code sign the installer, then the runtime (irsetup.exe) will be code signed during the build process. If you signed the finished installer manually, then yes - you will run into problems because the runtime itself won't be signed. See Publish > Settings > Code Signing.

Ulrich

[Stein Inge]

Thank you. I finally found how to get this fixed. An error in the code :-)

Brest regards
Stein Inge Haaland

[rickson]

Hi Stein Inge,

I'm glad I found this thread and saw that you found a way to fix this error. I'm encountering the same problem but the error code is "On Startup, Line 109: attempt to call a nil value".

May I ask you for the solution? Did you fix this by code signing as suggested by Ulrich?

Looking forward to your reply. =)