9 replies to this topic

[mspradley]

I cannot seem to get Installscript CA's to work properly. I have one after AppSearch and it is just ignored.

I know this issue has been posted before and the posted fixes were to declare the export function properly. I have done this and it still does not work.

The generated MSI database just seems to have one reference to f1 which is generated automatically by InstallShield. Could InstallShield be generating the MSI improperly?

The log file just indicates the action is skipped. It is in the install execute sequence right after AppSearch.

Any help is appreciated.

Matt

[JoeThompson]

Does your CustomAction have any conditions?  If so, what are they?

Joe

[mspradley]

No conditions, function just shows a messagebox. I was just testing to see if it would work.

Here it is:

export prototype MyFunction(HWND);  
function MyFunction (hMSI)  
begin            
   MessageBox ("InstallShield", INFORMATION);
   return ERROR_SUCCESS;
end;

If put in the execute sequence after AppSearch it is just ignored.

If put in the UI execute sequence after AppSearch log looks like this:

=== Logging started: 1/23/2002  10:47:28 ===
Action start 10:47:28: ISVerifyScriptingRuntime.
Action ended 10:47:28: ISVerifyScriptingRuntime. Return value 1.
Action start 10:47:28: LaunchConditions.
Action ended 10:47:28: LaunchConditions. Return value 1.
Action start 10:47:28: FindRelatedProducts.
Action ended 10:47:28: FindRelatedProducts. Return value 1.
Action start 10:47:28: AppSearch.
Action ended 10:47:28: AppSearch. Return value 1.
Action start 10:47:28: TT.
1: RPC runtime reported exception 0x6ba
Action ended 10:47:29: TT. Return value 3.
1: Failed to launch action 'TT', error is 1603
=== Verbose logging stopped: 1/23/2002  10:47:29 ===

[JoeThompson]

Is your CA type set to run immediately?  What is the type exactly (e.g. 65600)

Joe

[mspradley]

Execute immediate:

65536

[JoeThompson]

This is somewhat of a guess but why don't you try changing it to ignore the return code (65600) or remove the return statement from you CA and let me know what happens.

Joe

[mspradley]

Tried that and install keeps going. Following is section of log:

Action ended 13:13:59: AppSearch. Return value 1.
Action start 13:13:59: TT.
1: RPC runtime reported exception 0x6ba
Action ended 13:13:59: TT. Return value 1.
Action start 13:13:59: ValidateProductID.

I put a messagebox command in the function and it is not displaying.

My guess is its not calling into the script correctly -- I am pretty new to InstallShield. It seems to me something as basic as this should work. It is a totally blank project copying one file. I was using it as a test bed since I could not get the CA to work in my full project.

[JoeThompson]

Well, I am sort of new to this too.  I just created a brand new Basic project, created one custom action of type 65536 that calls MyFunction.  My function does exactly what your code does (MessageBox, and return).  I inserted it directly after AppSearch with no conditions and ran it.  When it hit the execute sequence the message box was displayed correctly.  I don't know what you could be doing differently.
This is probably a stupid question but you are calling the right function aren't you?  I notice in your log you have TT and your code posting was MyFunction...

Joe

[mspradley]

Joe,

It's good to know someone can get it to work. The TT reference was the name of the custom action. The TT custom action calls MyFunction.

I am beginning to think it might have something to do with my development system. I am running W2K Server SP2. I might try building the project with another system configuration although I would rather not.

I am pretty much at wits end.

[JoeThompson]

Hi Matt,

I know how you feel - I've been there plenty of times with this.  My guess is it will end up being something real obvious we're overlooking.  Maybe you should repost this question in the CustomActions forum and hopefully someone will be of more help...

Good luck,
Joe