[WiX-users] Managed CA fails to extract to temp directory (on one machine)

Discussion:

Alex DeNeui

2009-01-23 09:18:36 UTC

Hi all -

I have a managed CA created using DTF and WiX (3.0.4318) that is failing with MSI error 2896 on a single Windows XP machine with .NET 2.0 installed on it. The exact same MSI works fine on multiple XP and Vista machines. I spent some time looking into the issue, and it appears that on the faulty machine the DLL is not being extracted from the MSI and placed into the temp folder when the CA is invoked. The HD has plenty of space, virus scanners have been removed, etc. Any ideas?

I found an ancient thread where someone talked about a similar problem, but this appears to be an issue where the DLL is never extracted, not occasionally extracted: http://osdir.com/ml/windows.devel.wix.user/2005-06/msg00086.html

FYI my CA config

<Binary Id="GenerateLoginDll"
SourceFile="$(var.RootPath)\Installer.Login\bin\$(var.BuildType)\Installer.Login.Native.dll" />
<CustomAction Id="GenerateLogin" BinaryKey="GenerateLoginDll"
DllEntry="TryGenerateLogin" Execute="immediate" />

And my usings for the managed CA:

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.Deployment.WindowsInstaller;
using System.Net;
using System.IO;
using System.Threading;
using System.Security.Cryptography;
using System.Windows.Forms;

Thoughts?

alexd
-----

MSI (c) (80:74) [08:46:36:723]: Creating MSIHANDLE (1) of type 790542 for thread 3700
MSI (c) (80:A4) [08:46:36:738]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI1B.tmp, Entrypoint: TryGenerateLogin
MSI (c) (80:24) [08:46:36:801]: Cloaking enabled.
MSI (c) (80:24) [08:46:36:801]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (80:24) [08:46:36:801]: Connected to service for CA interface.
MSI (c) (80!38) [08:46:37:910]: Creating MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:910]: Closing MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:926]: Creating MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:941]: Closing MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Creating MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Closing MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80:A4) [08:46:38:332]: Closing MSIHANDLE (1) of type 790542 for thread 3700
Action ended 8:46:38: GenerateLogin. Return value 3.
DEBUG: Error 2896: Executing action GenerateLogin failed.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2896. The arguments are: GenerateLogin, ,
Action ended 8:46:38: WelcomeDlg. Return value 3.
MSI (c) (80:A8) [08:46:38:332]: Doing action: FatalError
Action 8:46:38: FatalError.
Action start 8:46:38: FatalError.
Action 8:46:38: FatalError. Dialog created
Action ended 8:46:41: FatalError. Return value 2.
Action ended 8:46:41: INSTALL. Return value 3.

Rob Mensching

2009-01-23 09:23:23 UTC

Permalink

No idea, but 3.0.4318.0 is a really old build.

-----Original Message-----
From: Alex DeNeui [mailto:***@docverse.com]
Sent: Friday, January 23, 2009 01:19
To: wix-***@lists.sourceforge.net
Subject: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Hi all -

I have a managed CA created using DTF and WiX (3.0.4318) that is failing with MSI error 2896 on a single Windows XP machine with .NET 2.0 installed on it. The exact same MSI works fine on multiple XP and Vista machines. I spent some time looking into the issue, and it appears that on the faulty machine the DLL is not being extracted from the MSI and placed into the temp folder when the CA is invoked. The HD has plenty of space, virus scanners have been removed, etc. Any ideas?

I found an ancient thread where someone talked about a similar problem, but this appears to be an issue where the DLL is never extracted, not occasionally extracted: http://osdir.com/ml/windows.devel.wix.user/2005-06/msg00086.html

FYI my CA config

<Binary Id="GenerateLoginDll"
SourceFile="$(var.RootPath)\Installer.Login\bin\$(var.BuildType)\Installer.Login.Native.dll" />
<CustomAction Id="GenerateLogin" BinaryKey="GenerateLoginDll"
DllEntry="TryGenerateLogin" Execute="immediate" />

And my usings for the managed CA:

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.Deployment.WindowsInstaller;
using System.Net;
using System.IO;
using System.Threading;
using System.Security.Cryptography;
using System.Windows.Forms;

Thoughts?

alexd
-----

MSI (c) (80:74) [08:46:36:723]: Creating MSIHANDLE (1) of type 790542 for thread 3700
MSI (c) (80:A4) [08:46:36:738]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI1B.tmp, Entrypoint: TryGenerateLogin
MSI (c) (80:24) [08:46:36:801]: Cloaking enabled.
MSI (c) (80:24) [08:46:36:801]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (80:24) [08:46:36:801]: Connected to service for CA interface.
MSI (c) (80!38) [08:46:37:910]: Creating MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:910]: Closing MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:926]: Creating MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:941]: Closing MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Creating MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Closing MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80:A4) [08:46:38:332]: Closing MSIHANDLE (1) of type 790542 for thread 3700
Action ended 8:46:38: GenerateLogin. Return value 3.
DEBUG: Error 2896: Executing action GenerateLogin failed.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2896. The arguments are: GenerateLogin, ,
Action ended 8:46:38: WelcomeDlg. Return value 3.
MSI (c) (80:A8) [08:46:38:332]: Doing action: FatalError
Action 8:46:38: FatalError.
Action start 8:46:38: FatalError.
Action 8:46:38: FatalError. Dialog created
Action ended 8:46:41: FatalError. Return value 2.
Action ended 8:46:41: INSTALL. Return value 3.

Alex DeNeui

2009-01-23 18:13:00 UTC

Permalink

Hi Rob -

I upgraded to 3.0.4805.0 but that does not solve the problem.

Any ideas on how to debug what could be going on?

alex

-----Original Message-----
From: Rob Mensching [mailto:***@microsoft.com]
Sent: Friday, January 23, 2009 1:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

No idea, but 3.0.4318.0 is a really old build.

-----Original Message-----
From: Alex DeNeui [mailto:***@docverse.com]
Sent: Friday, January 23, 2009 01:19
To: wix-***@lists.sourceforge.net
Subject: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Hi all -

I have a managed CA created using DTF and WiX (3.0.4318) that is failing with MSI error 2896 on a single Windows XP machine with .NET 2.0 installed on it. The exact same MSI works fine on multiple XP and Vista machines. I spent some time looking into the issue, and it appears that on the faulty machine the DLL is not being extracted from the MSI and placed into the temp folder when the CA is invoked. The HD has plenty of space, virus scanners have been removed, etc. Any ideas?

I found an ancient thread where someone talked about a similar problem, but this appears to be an issue where the DLL is never extracted, not occasionally extracted: http://osdir.com/ml/windows.devel.wix.user/2005-06/msg00086.html

FYI my CA config

<Binary Id="GenerateLoginDll"
SourceFile="$(var.RootPath)\Installer.Login\bin\$(var.BuildType)\Installer.Login.Native.dll" />
<CustomAction Id="GenerateLogin" BinaryKey="GenerateLoginDll"
DllEntry="TryGenerateLogin" Execute="immediate" />

And my usings for the managed CA:

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.Deployment.WindowsInstaller;
using System.Net;
using System.IO;
using System.Threading;
using System.Security.Cryptography;
using System.Windows.Forms;

Thoughts?

alexd
-----

MSI (c) (80:74) [08:46:36:723]: Creating MSIHANDLE (1) of type 790542 for thread 3700
MSI (c) (80:A4) [08:46:36:738]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI1B.tmp, Entrypoint: TryGenerateLogin
MSI (c) (80:24) [08:46:36:801]: Cloaking enabled.
MSI (c) (80:24) [08:46:36:801]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (80:24) [08:46:36:801]: Connected to service for CA interface.
MSI (c) (80!38) [08:46:37:910]: Creating MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:910]: Closing MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:926]: Creating MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:941]: Closing MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Creating MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Closing MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80:A4) [08:46:38:332]: Closing MSIHANDLE (1) of type 790542 for thread 3700
Action ended 8:46:38: GenerateLogin. Return value 3.
DEBUG: Error 2896: Executing action GenerateLogin failed.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2896. The arguments are: GenerateLogin, ,
Action ended 8:46:38: WelcomeDlg. Return value 3.
MSI (c) (80:A8) [08:46:38:332]: Doing action: FatalError
Action 8:46:38: FatalError.
Action start 8:46:38: FatalError.
Action 8:46:38: FatalError. Dialog created
Action ended 8:46:41: FatalError. Return value 2.
Action ended 8:46:41: INSTALL. Return value 3.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Rob Mensching

2009-01-23 18:32:31 UTC

Permalink

Nope, sorry. I don't use DTF.

-----Original Message-----
From: Alex DeNeui [mailto:***@docverse.com]
Sent: Friday, January 23, 2009 10:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Hi Rob -

I upgraded to 3.0.4805.0 but that does not solve the problem.

Any ideas on how to debug what could be going on?

alex

-----Original Message-----
From: Rob Mensching [mailto:***@microsoft.com]
Sent: Friday, January 23, 2009 1:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

No idea, but 3.0.4318.0 is a really old build.

-----Original Message-----
From: Alex DeNeui [mailto:***@docverse.com]
Sent: Friday, January 23, 2009 01:19
To: wix-***@lists.sourceforge.net
Subject: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Hi all -

I have a managed CA created using DTF and WiX (3.0.4318) that is failing with MSI error 2896 on a single Windows XP machine with .NET 2.0 installed on it. The exact same MSI works fine on multiple XP and Vista machines. I spent some time looking into the issue, and it appears that on the faulty machine the DLL is not being extracted from the MSI and placed into the temp folder when the CA is invoked. The HD has plenty of space, virus scanners have been removed, etc. Any ideas?

I found an ancient thread where someone talked about a similar problem, but this appears to be an issue where the DLL is never extracted, not occasionally extracted: http://osdir.com/ml/windows.devel.wix.user/2005-06/msg00086.html

FYI my CA config

<Binary Id="GenerateLoginDll"
SourceFile="$(var.RootPath)\Installer.Login\bin\$(var.BuildType)\Installer.Login.Native.dll" />
<CustomAction Id="GenerateLogin" BinaryKey="GenerateLoginDll"
DllEntry="TryGenerateLogin" Execute="immediate" />

And my usings for the managed CA:

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.Deployment.WindowsInstaller;
using System.Net;
using System.IO;
using System.Threading;
using System.Security.Cryptography;
using System.Windows.Forms;

Thoughts?

alexd
-----

MSI (c) (80:74) [08:46:36:723]: Creating MSIHANDLE (1) of type 790542 for thread 3700
MSI (c) (80:A4) [08:46:36:738]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI1B.tmp, Entrypoint: TryGenerateLogin
MSI (c) (80:24) [08:46:36:801]: Cloaking enabled.
MSI (c) (80:24) [08:46:36:801]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (80:24) [08:46:36:801]: Connected to service for CA interface.
MSI (c) (80!38) [08:46:37:910]: Creating MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:910]: Closing MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:926]: Creating MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:941]: Closing MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Creating MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Closing MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80:A4) [08:46:38:332]: Closing MSIHANDLE (1) of type 790542 for thread 3700
Action ended 8:46:38: GenerateLogin. Return value 3.
DEBUG: Error 2896: Executing action GenerateLogin failed.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2896. The arguments are: GenerateLogin, ,
Action ended 8:46:38: WelcomeDlg. Return value 3.
MSI (c) (80:A8) [08:46:38:332]: Doing action: FatalError
Action 8:46:38: FatalError.
Action start 8:46:38: FatalError.
Action 8:46:38: FatalError. Dialog created
Action ended 8:46:41: FatalError. Return value 2.
Action ended 8:46:41: INSTALL. Return value 3.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Jason Ginchereau

2009-01-24 00:06:32 UTC

Permalink

How do you know the DLL is not extracted, versus some other problem executing it? It's not clear from the log below. Keep in mind that when extracted it actually has the filename extension .TMP instead of .DLL.

On the failing system are there any unusual filesystem permissions in the \Windows\Installer directory or the user temp directory?

If the CA binary is not even being extracted from the MSI, then it's not a DTF-specific issue because no DTF code ever gets to run.

-Jason-

-----Original Message-----
From: Rob Mensching [mailto:***@microsoft.com]
Sent: Friday, January 23, 2009 10:33 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Nope, sorry. I don't use DTF.

-----Original Message-----
From: Alex DeNeui [mailto:***@docverse.com]
Sent: Friday, January 23, 2009 10:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Hi Rob -

I upgraded to 3.0.4805.0 but that does not solve the problem.

Any ideas on how to debug what could be going on?

alex

-----Original Message-----
From: Rob Mensching [mailto:***@microsoft.com]
Sent: Friday, January 23, 2009 1:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

No idea, but 3.0.4318.0 is a really old build.

-----Original Message-----
From: Alex DeNeui [mailto:***@docverse.com]
Sent: Friday, January 23, 2009 01:19
To: wix-***@lists.sourceforge.net
Subject: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Hi all -

I have a managed CA created using DTF and WiX (3.0.4318) that is failing with MSI error 2896 on a single Windows XP machine with .NET 2.0 installed on it. The exact same MSI works fine on multiple XP and Vista machines. I spent some time looking into the issue, and it appears that on the faulty machine the DLL is not being extracted from the MSI and placed into the temp folder when the CA is invoked. The HD has plenty of space, virus scanners have been removed, etc. Any ideas?

I found an ancient thread where someone talked about a similar problem, but this appears to be an issue where the DLL is never extracted, not occasionally extracted: http://osdir.com/ml/windows.devel.wix.user/2005-06/msg00086.html

FYI my CA config

<Binary Id="GenerateLoginDll"
SourceFile="$(var.RootPath)\Installer.Login\bin\$(var.BuildType)\Installer.Login.Native.dll" />
<CustomAction Id="GenerateLogin" BinaryKey="GenerateLoginDll"
DllEntry="TryGenerateLogin" Execute="immediate" />

And my usings for the managed CA:

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.Deployment.WindowsInstaller;
using System.Net;
using System.IO;
using System.Threading;
using System.Security.Cryptography;
using System.Windows.Forms;

Thoughts?

alexd
-----

MSI (c) (80:74) [08:46:36:723]: Creating MSIHANDLE (1) of type 790542 for thread 3700
MSI (c) (80:A4) [08:46:36:738]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI1B.tmp, Entrypoint: TryGenerateLogin
MSI (c) (80:24) [08:46:36:801]: Cloaking enabled.
MSI (c) (80:24) [08:46:36:801]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (80:24) [08:46:36:801]: Connected to service for CA interface.
MSI (c) (80!38) [08:46:37:910]: Creating MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:910]: Closing MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:926]: Creating MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:941]: Closing MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Creating MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Closing MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80:A4) [08:46:38:332]: Closing MSIHANDLE (1) of type 790542 for thread 3700
Action ended 8:46:38: GenerateLogin. Return value 3.
DEBUG: Error 2896: Executing action GenerateLogin failed.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2896. The arguments are: GenerateLogin, ,
Action ended 8:46:38: WelcomeDlg. Return value 3.
MSI (c) (80:A8) [08:46:38:332]: Doing action: FatalError
Action 8:46:38: FatalError.
Action start 8:46:38: FatalError.
Action 8:46:38: FatalError. Dialog created
Action ended 8:46:41: FatalError. Return value 2.
Action ended 8:46:41: INSTALL. Return value 3.

Alex DeNeui

2009-01-26 21:59:45 UTC

Permalink

Very unscientifically... I have an Explorer window open to the Temp folder. On a working machine I can see the file being extracted to the temp folder and then removed after the CA is done. On the broken machine it never shows up in the folder. However, I installed FileMon on the broken machine and it looks like msiexec.exe is writing out the file to disk even though it isn't showing up in Explorer. So I guess the file is there at some point.

Here are my permissions... I believe they are ok (I'm installing as Administrator)

C:\WINDOWS>fileacl C:\WINDOWS\Installer
C:\WINDOWS\Installer;NT AUTHORITY\SYSTEM:F
C:\WINDOWS\Installer;Everyone:RX
C:\WINDOWS\Installer;BUILTIN\Administrators:F

C:\WINDOWS>fileacl "C:\Documents and Settings\Administrator\Local Settings\Temp"

C:\Documents and Settings\Administrator\Local Settings\Temp;JOSH-4E34964239\Admi
nistrator:F[I]
C:\Documents and Settings\Administrator\Local Settings\Temp;NT AUTHORITY\SYSTEM:
F[I]
C:\Documents and Settings\Administrator\Local Settings\Temp;BUILTIN\Administrato
rs:F[I]
________________________________________
From: Jason Ginchereau [***@microsoft.com]
Sent: Friday, January 23, 2009 4:06 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

How do you know the DLL is not extracted, versus some other problem executing it? It's not clear from the log below. Keep in mind that when extracted it actually has the filename extension .TMP instead of .DLL.

On the failing system are there any unusual filesystem permissions in the \Windows\Installer directory or the user temp directory?

If the CA binary is not even being extracted from the MSI, then it's not a DTF-specific issue because no DTF code ever gets to run.

-Jason-

-----Original Message-----
From: Rob Mensching [mailto:***@microsoft.com]
Sent: Friday, January 23, 2009 10:33 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Nope, sorry. I don't use DTF.

-----Original Message-----
From: Alex DeNeui [mailto:***@docverse.com]
Sent: Friday, January 23, 2009 10:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Hi Rob -

I upgraded to 3.0.4805.0 but that does not solve the problem.

Any ideas on how to debug what could be going on?

alex

-----Original Message-----
From: Rob Mensching [mailto:***@microsoft.com]
Sent: Friday, January 23, 2009 1:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

No idea, but 3.0.4318.0 is a really old build.

-----Original Message-----
From: Alex DeNeui [mailto:***@docverse.com]
Sent: Friday, January 23, 2009 01:19
To: wix-***@lists.sourceforge.net
Subject: [WiX-users] Managed CA fails to extract to temp directory (on one machine)

Hi all -

I have a managed CA created using DTF and WiX (3.0.4318) that is failing with MSI error 2896 on a single Windows XP machine with .NET 2.0 installed on it. The exact same MSI works fine on multiple XP and Vista machines. I spent some time looking into the issue, and it appears that on the faulty machine the DLL is not being extracted from the MSI and placed into the temp folder when the CA is invoked. The HD has plenty of space, virus scanners have been removed, etc. Any ideas?

I found an ancient thread where someone talked about a similar problem, but this appears to be an issue where the DLL is never extracted, not occasionally extracted: http://osdir.com/ml/windows.devel.wix.user/2005-06/msg00086.html

FYI my CA config

<Binary Id="GenerateLoginDll"
SourceFile="$(var.RootPath)\Installer.Login\bin\$(var.BuildType)\Installer.Login.Native.dll" />
<CustomAction Id="GenerateLogin" BinaryKey="GenerateLoginDll"
DllEntry="TryGenerateLogin" Execute="immediate" />

And my usings for the managed CA:

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.Deployment.WindowsInstaller;
using System.Net;
using System.IO;
using System.Threading;
using System.Security.Cryptography;
using System.Windows.Forms;

Thoughts?

alexd
-----

MSI (c) (80:74) [08:46:36:723]: Creating MSIHANDLE (1) of type 790542 for thread 3700
MSI (c) (80:A4) [08:46:36:738]: Invoking remote custom action. DLL: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\MSI1B.tmp, Entrypoint: TryGenerateLogin
MSI (c) (80:24) [08:46:36:801]: Cloaking enabled.
MSI (c) (80:24) [08:46:36:801]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (80:24) [08:46:36:801]: Connected to service for CA interface.
MSI (c) (80!38) [08:46:37:910]: Creating MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:910]: Closing MSIHANDLE (2) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:926]: Creating MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:37:941]: Closing MSIHANDLE (3) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Creating MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80!38) [08:46:38:254]: Closing MSIHANDLE (4) of type 790531 for thread 3896
MSI (c) (80:A4) [08:46:38:332]: Closing MSIHANDLE (1) of type 790542 for thread 3700
Action ended 8:46:38: GenerateLogin. Return value 3.
DEBUG: Error 2896: Executing action GenerateLogin failed.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2896. The arguments are: GenerateLogin, ,
Action ended 8:46:38: WelcomeDlg. Return value 3.
MSI (c) (80:A8) [08:46:38:332]: Doing action: FatalError
Action 8:46:38: FatalError.
Action start 8:46:38: FatalError.
Action 8:46:38: FatalError. Dialog created
Action ended 8:46:41: FatalError. Return value 2.
Action ended 8:46:41: INSTALL. Return value 3.

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Corry, Davidson

2009-01-23 18:47:21 UTC

Permalink

(Sorry if this is an FAQ. If so, I haven't found it yet, and please
point me to it.)

I want to modify the context-menu that appears when you click
on the drive+arrow icon in the standard feature-selection control,
on a per-feature basis. Specifically, I need to

* no "entire feature will be installed" when feature is a leaf
(and otherwise handle parent-features differently from leaves)
* no "feature installed when required" (no on-demand install)
* no "installed to run from network" (force local install)
* disallow ANY selection when the feature is already installed
(features are databases user may have updated, want to make
them "install-only" so that user updates are never lost)
[BUT have to allow select/deselect of not-yet-installed features]

and the biggie:
* pop up an edit box when the feature is selected for install,
allow entry of an activation code for the feature, vet the
code against a database, and allow re-entry of the code if
the entered value is invalid, etc.
Some features need a code, some don't and just need selection.

Ideally, I would also like to be able to control the icon displayed
for a feature: not just drive+arrow or red-X+arrow or grayed for
parent feature with some-but-not-all subfeatures selected, but
e.g. green for "already installed" etc.

Is this possible with WiX? If so, how?

Or am I better off writing my own control?

Thanks for your help.
-- Daí

Brian Simoneau

2009-01-23 18:56:06 UTC

Permalink

This is not possible with a Windows Installer tree control. You will need to write your own.

-Brian Simoneau

-----Original Message-----
From: Corry, Davidson [mailto:***@sage.com]
Sent: Friday, January 23, 2009 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Modify behavior of tree selection control?

(Sorry if this is an FAQ. If so, I haven't found it yet, and please
point me to it.)

I want to modify the context-menu that appears when you click
on the drive+arrow icon in the standard feature-selection control,
on a per-feature basis. Specifically, I need to

* no "entire feature will be installed" when feature is a leaf
(and otherwise handle parent-features differently from leaves)
* no "feature installed when required" (no on-demand install)
* no "installed to run from network" (force local install)
* disallow ANY selection when the feature is already installed
(features are databases user may have updated, want to make
them "install-only" so that user updates are never lost)
[BUT have to allow select/deselect of not-yet-installed features]

and the biggie:
* pop up an edit box when the feature is selected for install,
allow entry of an activation code for the feature, vet the
code against a database, and allow re-entry of the code if
the entered value is invalid, etc.
Some features need a code, some don't and just need selection.

Ideally, I would also like to be able to control the icon displayed
for a feature: not just drive+arrow or red-X+arrow or grayed for
parent feature with some-but-not-all subfeatures selected, but
e.g. green for "already installed" etc.

Is this possible with WiX? If so, how?

Or am I better off writing my own control?

Thanks for your help.
-- Daí

Corry, Davidson

2009-01-23 19:04:08 UTC

Permalink

Poo.

Well, thanks anyway! -- Daí

-----Original Message-----
From: Brian Simoneau [mailto:***@FreedomScientific.com]
Sent: Friday, January 23, 2009 10:56 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Modify behavior of tree selection control?

This is not possible with a Windows Installer tree control. You will need to write your own.

-Brian Simoneau

-----Original Message-----
From: Corry, Davidson [mailto:***@sage.com]
Sent: Friday, January 23, 2009 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Modify behavior of tree selection control?

(Sorry if this is an FAQ. If so, I haven't found it yet, and please
point me to it.)

I want to modify the context-menu that appears when you click
on the drive+arrow icon in the standard feature-selection control,
on a per-feature basis. Specifically, I need to

* no "entire feature will be installed" when feature is a leaf
(and otherwise handle parent-features differently from leaves)
* no "feature installed when required" (no on-demand install)
* no "installed to run from network" (force local install)
* disallow ANY selection when the feature is already installed
(features are databases user may have updated, want to make
them "install-only" so that user updates are never lost)
[BUT have to allow select/deselect of not-yet-installed features]

and the biggie:
* pop up an edit box when the feature is selected for install,
allow entry of an activation code for the feature, vet the
code against a database, and allow re-entry of the code if
the entered value is invalid, etc.
Some features need a code, some don't and just need selection.

Ideally, I would also like to be able to control the icon displayed
for a feature: not just drive+arrow or red-X+arrow or grayed for
parent feature with some-but-not-all subfeatures selected, but
e.g. green for "already installed" etc.

Is this possible with WiX? If so, how?

Or am I better off writing my own control?

Thanks for your help.
-- Daí

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Rob Mensching

2009-01-23 18:59:35 UTC

Permalink

Windows Installer doesn't support that so the WiX toolset can't either.

-----Original Message-----
From: Corry, Davidson [mailto:***@sage.com]
Sent: Friday, January 23, 2009 10:47
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Modify behavior of tree selection control?

(Sorry if this is an FAQ. If so, I haven't found it yet, and please
point me to it.)

I want to modify the context-menu that appears when you click
on the drive+arrow icon in the standard feature-selection control,
on a per-feature basis. Specifically, I need to

* no "entire feature will be installed" when feature is a leaf
(and otherwise handle parent-features differently from leaves)
* no "feature installed when required" (no on-demand install)
* no "installed to run from network" (force local install)
* disallow ANY selection when the feature is already installed
(features are databases user may have updated, want to make
them "install-only" so that user updates are never lost)
[BUT have to allow select/deselect of not-yet-installed features]

and the biggie:
* pop up an edit box when the feature is selected for install,
allow entry of an activation code for the feature, vet the
code against a database, and allow re-entry of the code if
the entered value is invalid, etc.
Some features need a code, some don't and just need selection.

Ideally, I would also like to be able to control the icon displayed
for a feature: not just drive+arrow or red-X+arrow or grayed for
parent feature with some-but-not-all subfeatures selected, but
e.g. green for "already installed" etc.

Is this possible with WiX? If so, how?

Or am I better off writing my own control?

Thanks for your help.
-- Daí