Web setup MSI fails on Windows Server 2008

Question

I have built a web setup project in VS2008 which installs my ASP.NET/Silverlight app into IIS. This works fine everywhere except on Windows Server 2008.

I get this error message in the MSI installer log file:

MSI (c) (C8:D8) [15:02:21:067]: Invoking remote custom action. DLL: C:\Users\ADMINI~1\AppData\Local\Temp\1\MSIB7DD.tmp, Entrypoint: SetTARGETSITE
MSI (c) (C8!F0) [15:02:21:097]: Creating MSIHANDLE (14) of type 790531 for thread 2288
INFO   : [08/27/2009 15:02:21:097] [SetTARGETSITE                           ]: Custom Action is starting...
INFO   : [08/27/2009 15:02:21:107] [SetTARGETSITE                           ]: CoInitializeEx - COM initialization Apartment Threaded...
ERROR  : [08/27/2009 15:02:21:107] [SetTARGETSITE                           ]: FAILED:  -2147221164
ERROR  : [08/27/2009 15:02:21:127] [SetTARGETSITE                           ]: Custom Action failed with code: '340'
INFO   : [08/27/2009 15:02:21:137] [SetTARGETSITE                           ]: Custom Action completed with return code: '340'
MSI (c) (C8!F0) [15:02:21:137]: Closing MSIHANDLE (14) of type 790531 for thread 2288
MSI (c) (C8:D8) [15:02:21:137]: Closing MSIHANDLE (13) of type 790542 for thread 3040
Action ended 15:02:21: WEBCA_SetTARGETSITE. Return value 3.
MSI (c) (C8:E0) [15:02:21:147]: Doing action: FatalErrorForm

I've tried googling the various error codes, but I'm not having much luck.

What is the problem?

Answer 1

Like the comment, it looks like this could be something COM related. That would lead me to believe that the MSI is using something that is probably specific to IIS 6.

Make sure you have the IIS 6 compatibility options installed with IIS 7 in Windows 2008. That should install the COM components that your MSI is trying to access.

...just a guess of course. Good luck.

Answer 2

This might help http://social.msdn.microsoft.com/Forums/en-US/winformssetup/thread/6940016e-0a08-4368-8231-689e475f2d59

cedi

Answer 3

I have a Default Web Site and getting the same error so I don't think this is the answer. Turning on all IIS Server roles though enables the II6 Compatibility which solves the problem. I am looking for a way to make my setup IIS7 compatible without this IIS6 legacy stuff... any ideas on this?