Windows Installer XML (WiX) toolset › wix-users

WriteMetabaseChanges: Error 0x80070057: failed to create web application

16 messages

WriteMetabaseChanges: Error 0x80070057: failed to create web application

Reply Threaded

We are getting the following error and are not sure why. We have been
successful at creating virtual directories in several other environments
(development, integration, etc.), however the environment we are currently
deploying to is having issues :(

Action 14:41:11: StartMetabaseTransaction. Starting IIS Metabase Transaction
Action 14:41:11: RollbackMetabaseTransaction. Rolling back IIS Metabase
Transaction
Action 14:41:11: CommitMetabaseTransaction. Committing IIS Metabase
Transaction
Action 14:41:11: WriteMetabaseChanges. Installing Metabase Keys and Values
WriteMetabaseChanges: Error 0x80070057: failed to create web application:
/Root/SecurityAutomation
Error 26105. Failed to create web application. (-2147024809
/Root/SecurityAutomation )
MSI (s) (CC!30) [15:56:04:702]: Product: kCTools (64 bit) -- Error 26105.
Failed to create web application. (-2147024809
/Root/SecurityAutomation )

WriteMetabaseChanges: Error 0x80070057: failed to create ASP App
Action ended 15:56:04: InstallFinalize. Return value 3.
Action 15:56:04: Rollback. Rolling back action:
Rollback: Installing Metabase Keys and Values
Rollback: Committing IIS Metabase Transaction
Rollback: Rolling back IIS Metabase Transaction
Rollback: Starting IIS Metabase Transaction
Rollback: Copying new files
Rollback: Creating folders
Rollback: Deleting services
Rollback: Stopping services
Rollback: Updating component registration
Action ended 15:56:22: INSTALL. Return value 3.

Here is our WiX IIS settings:

<iis:WebAppPool Id="WAP__kCTools.ApplicationPool.Uber"
Name="[kCTools.ApplicationPool.Name.Uber]" />
<iis:WebSite Id="WS__kCTools.WebServices"
Description="[kCTools.WebServices.WebSite]">
<iis:WebAddress Id="WA__kCTools.AllUnassigned"
Port="[kCTools.WebServices.Port]" Header="[kCTools.WebServices.Header]" />
</iis:WebSite>

The IIS Web site on which we are creating the virtuals exists. We are able
to manually create virtuals. The local hosts file is set to resolve the
WebSite name we want to create our virtual on. We are passing in the above
MSI properties via a mst file, and have verified they exist and are properly
set.

We are using WiX version 3.0.4805.

Any ideas about what else we may consider looking at?

- Troy
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

Mike Carlson (DEV DIV)

Re: WriteMetabaseChanges: Error 0x80070057: failed to create web application

Reply Threaded

A *lot* has changed in the IIS custom actions since WiX v3.0.4805, including an error that looks very similar to this. First, I would upgrade to the latest WiX 3.0 build (v3.0.5419) and see if you still have a problem after that.

Thanks,
Mike Carlson

-----Original Message-----
From: troy hostetter [mailto:[hidden email]]
Sent: Wednesday, July 01, 2009 9:31 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] WriteMetabaseChanges: Error 0x80070057: failed to create web application

We are getting the following error and are not sure why. We have been
successful at creating virtual directories in several other environments
(development, integration, etc.), however the environment we are currently
deploying to is having issues :(

Action 14:41:11: StartMetabaseTransaction. Starting IIS Metabase Transaction
Action 14:41:11: RollbackMetabaseTransaction. Rolling back IIS Metabase
Transaction
Action 14:41:11: CommitMetabaseTransaction. Committing IIS Metabase
Transaction
Action 14:41:11: WriteMetabaseChanges. Installing Metabase Keys and Values
WriteMetabaseChanges: Error 0x80070057: failed to create web application:
/Root/SecurityAutomation
Error 26105. Failed to create web application. (-2147024809
/Root/SecurityAutomation )
MSI (s) (CC!30) [15:56:04:702]: Product: kCTools (64 bit) -- Error 26105.
Failed to create web application. (-2147024809
/Root/SecurityAutomation )

WriteMetabaseChanges: Error 0x80070057: failed to create ASP App
Action ended 15:56:04: InstallFinalize. Return value 3.
Action 15:56:04: Rollback. Rolling back action:
Rollback: Installing Metabase Keys and Values
Rollback: Committing IIS Metabase Transaction
Rollback: Rolling back IIS Metabase Transaction
Rollback: Starting IIS Metabase Transaction
Rollback: Copying new files
Rollback: Creating folders
Rollback: Deleting services
Rollback: Stopping services
Rollback: Updating component registration
Action ended 15:56:22: INSTALL. Return value 3.

Here is our WiX IIS settings:

<iis:WebAppPool Id="WAP__kCTools.ApplicationPool.Uber"
Name="[kCTools.ApplicationPool.Name.Uber]" />
<iis:WebSite Id="WS__kCTools.WebServices"
Description="[kCTools.WebServices.WebSite]">
<iis:WebAddress Id="WA__kCTools.AllUnassigned"
Port="[kCTools.WebServices.Port]" Header="[kCTools.WebServices.Header]" />
</iis:WebSite>

The IIS Web site on which we are creating the virtuals exists. We are able
to manually create virtuals. The local hosts file is set to resolve the
WebSite name we want to create our virtual on. We are passing in the above
MSI properties via a mst file, and have verified they exist and are properly
set.

We are using WiX version 3.0.4805.

Any ideas about what else we may consider looking at?

- Troy
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

troy hostetter

Re: WriteMetabaseChanges: Error 0x80070057: failed to create web application

Reply Threaded

Mike -

Installed version 3.0.5419, built msi, and am now getting this error during
install:

Action 18:36:40: StartMetabaseTransaction. Starting IIS Metabase Transaction
Action 18:36:40: RollbackMetabaseTransaction. Rolling back IIS Metabase
Transaction
Action 18:36:40: CommitMetabaseTransaction. Committing IIS Metabase
Transaction
Action 18:36:40: ConfigureIIsExec.
ConfigureIIsExec: A matching web object in memory was found, but the web
object in memory has no associated base
ConfigureIIsExec: Error 0x80070002: Failed to find Web base
ConfigureIIsExec: Error 0x80070002: Failed to get base of web:
WS__kCTools.WebServices for VirtualDir
ConfigureIIsExec: Error 0x80070002: failed while processing WebVirtualDirs
Error 26004. Failed while processing WebVirtualDirs. (-2147024894 )
MSI (s) (78!98) [18:37:50:712]: Product: kCTools (64 bit) -- Error 26004.
Failed while processing WebVirtualDirs. (-2147024894 )

Action ended 18:37:50: InstallFinalize. Return value 3.
Action 18:37:50: Rollback. Rolling back action:
Rollback: ConfigureIIsExec
Rollback: Committing IIS Metabase Transaction
Rollback: Rolling back IIS Metabase Transaction
Rollback: Starting IIS Metabase Transaction
Rollback: Copying new files
Rollback: Creating folders
Rollback: Deleting services
Rollback: Stopping services
Rollback: Updating component registration
Action ended 18:38:07: INSTALL. Return value 3.

Thanks,
- Troy

On Wed, Jul 1, 2009 at 12:51 PM, Mike Carlson (DEV DIV) <
[hidden email]> wrote:

> A *lot* has changed in the IIS custom actions since WiX v3.0.4805,
> including an error that looks very similar to this. First, I would upgrade
> to the latest WiX 3.0 build (v3.0.5419) and see if you still have a problem
> after that.
>
> Thanks,
> Mike Carlson
>
> -----Original Message-----
> From: troy hostetter [mailto:[hidden email]]
> Sent: Wednesday, July 01, 2009 9:31 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] WriteMetabaseChanges: Error 0x80070057: failed to
> create web application
>
> We are getting the following error and are not sure why. We have been
> successful at creating virtual directories in several other environments
> (development, integration, etc.), however the environment we are currently
> deploying to is having issues :(
>
> Action 14:41:11: StartMetabaseTransaction. Starting IIS Metabase
> Transaction
> Action 14:41:11: RollbackMetabaseTransaction. Rolling back IIS Metabase
> Transaction
> Action 14:41:11: CommitMetabaseTransaction. Committing IIS Metabase
> Transaction
> Action 14:41:11: WriteMetabaseChanges. Installing Metabase Keys and Values
> WriteMetabaseChanges: Error 0x80070057: failed to create web application:
> /Root/SecurityAutomation
> Error 26105. Failed to create web application. (-2147024809
> /Root/SecurityAutomation )
> MSI (s) (CC!30) [15:56:04:702]: Product: kCTools (64 bit) -- Error 26105.
> Failed to create web application. (-2147024809
> /Root/SecurityAutomation )
>
> WriteMetabaseChanges: Error 0x80070057: failed to create ASP App
> Action ended 15:56:04: InstallFinalize. Return value 3.
> Action 15:56:04: Rollback. Rolling back action:
> Rollback: Installing Metabase Keys and Values
> Rollback: Committing IIS Metabase Transaction
> Rollback: Rolling back IIS Metabase Transaction
> Rollback: Starting IIS Metabase Transaction
> Rollback: Copying new files
> Rollback: Creating folders
> Rollback: Deleting services
> Rollback: Stopping services
> Rollback: Updating component registration
> Action ended 15:56:22: INSTALL. Return value 3.
>
> Here is our WiX IIS settings:
>
> <iis:WebAppPool Id="WAP__kCTools.ApplicationPool.Uber"
> Name="[kCTools.ApplicationPool.Name.Uber]" />
> <iis:WebSite Id="WS__kCTools.WebServices"
> Description="[kCTools.WebServices.WebSite]">
> <iis:WebAddress Id="WA__kCTools.AllUnassigned"
> Port="[kCTools.WebServices.Port]" Header="[kCTools.WebServices.Header]" />
> </iis:WebSite>
>
> The IIS Web site on which we are creating the virtuals exists. We are able
> to manually create virtuals. The local hosts file is set to resolve the
> WebSite name we want to create our virtual on. We are passing in the above
> MSI properties via a mst file, and have verified they exist and are
> properly
> set.
>
> We are using WiX version 3.0.4805.
>
> Any ideas about what else we may consider looking at?
>
> - Troy
>
> ------------------------------------------------------------------------------
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

Mike Carlson (DEV DIV)

Re: WriteMetabaseChanges: Error 0x80070057: failed to create web application

Reply Threaded

Does your website have a component associated with it?

The log sounds as though you're using a website locator record (which is simply a website with no associated component), and the website it's trying to locate on the machine doesn't exist (in which case the install is intended to fail). If you want the website to be created if it doesn't exist, the website must be associated with a component.

Thanks,
Mike Carlson

-----Original Message-----
From: troy hostetter [mailto:[hidden email]]
Sent: Wednesday, July 01, 2009 11:54 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WriteMetabaseChanges: Error 0x80070057: failed to create web application

Mike -

Installed version 3.0.5419, built msi, and am now getting this error during
install:

Action 18:36:40: StartMetabaseTransaction. Starting IIS Metabase Transaction
Action 18:36:40: RollbackMetabaseTransaction. Rolling back IIS Metabase
Transaction
Action 18:36:40: CommitMetabaseTransaction. Committing IIS Metabase
Transaction
Action 18:36:40: ConfigureIIsExec.
ConfigureIIsExec: A matching web object in memory was found, but the web
object in memory has no associated base
ConfigureIIsExec: Error 0x80070002: Failed to find Web base
ConfigureIIsExec: Error 0x80070002: Failed to get base of web:
WS__kCTools.WebServices for VirtualDir
ConfigureIIsExec: Error 0x80070002: failed while processing WebVirtualDirs
Error 26004. Failed while processing WebVirtualDirs. (-2147024894 )
MSI (s) (78!98) [18:37:50:712]: Product: kCTools (64 bit) -- Error 26004.
Failed while processing WebVirtualDirs. (-2147024894 )

Action ended 18:37:50: InstallFinalize. Return value 3.
Action 18:37:50: Rollback. Rolling back action:
Rollback: ConfigureIIsExec
Rollback: Committing IIS Metabase Transaction
Rollback: Rolling back IIS Metabase Transaction
Rollback: Starting IIS Metabase Transaction
Rollback: Copying new files
Rollback: Creating folders
Rollback: Deleting services
Rollback: Stopping services
Rollback: Updating component registration
Action ended 18:38:07: INSTALL. Return value 3.

Thanks,
- Troy

On Wed, Jul 1, 2009 at 12:51 PM, Mike Carlson (DEV DIV) <
[hidden email]> wrote:

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

troy hostetter

Re: WriteMetabaseChanges: Error 0x80070057: failed to create web application

Reply Threaded

In reply to this post by troy hostetter

FWIW .. I passed in the IP address of the existing web site .. the new WiX
looks like:

<iis:WebSite Id="WS__kCTools.WebServices"
Description="[kCTools.WebServices.WebSite]">
<iis:WebAddress Id="WA__kCTools.AllUnassigned"
Port="[kCTools.WebServices.Port]" Header="[kCTools.WebServices.Header]" IP="
[WEBSERVICES_IP]" />
</iis:WebSite>

Still no go :( .. same error as below.

- Troy

On Wed, Jul 1, 2009 at 2:54 PM, troy hostetter <[hidden email]>wrote:

> Mike -
>
> Installed version 3.0.5419, built msi, and am now getting this error during
> install:
>
> Action 18:36:40: StartMetabaseTransaction. Starting IIS Metabase
> Transaction
> Action 18:36:40: RollbackMetabaseTransaction. Rolling back IIS Metabase
> Transaction
> Action 18:36:40: CommitMetabaseTransaction. Committing IIS Metabase
> Transaction
> Action 18:36:40: ConfigureIIsExec.
> ConfigureIIsExec: A matching web object in memory was found, but the web
> object in memory has no associated base
> ConfigureIIsExec: Error 0x80070002: Failed to find Web base
> ConfigureIIsExec: Error 0x80070002: Failed to get base of web:
> WS__kCTools.WebServices for VirtualDir
> ConfigureIIsExec: Error 0x80070002: failed while processing WebVirtualDirs
> Error 26004. Failed while processing WebVirtualDirs. (-2147024894
> )
> MSI (s) (78!98) [18:37:50:712]: Product: kCTools (64 bit) -- Error 26004.
> Failed while processing WebVirtualDirs. (-2147024894 )
>
> Action ended 18:37:50: InstallFinalize. Return value 3.
> Action 18:37:50: Rollback. Rolling back action:
> Rollback: ConfigureIIsExec
> Rollback: Committing IIS Metabase Transaction
> Rollback: Rolling back IIS Metabase Transaction
> Rollback: Starting IIS Metabase Transaction
> Rollback: Copying new files
> Rollback: Creating folders
> Rollback: Deleting services
> Rollback: Stopping services
> Rollback: Updating component registration
> Action ended 18:38:07: INSTALL. Return value 3.
>
> Thanks,
> - Troy
>
>
> On Wed, Jul 1, 2009 at 12:51 PM, Mike Carlson (DEV DIV) <
> [hidden email]> wrote:
>
>> A *lot* has changed in the IIS custom actions since WiX v3.0.4805,
>> including an error that looks very similar to this. First, I would upgrade
>> to the latest WiX 3.0 build (v3.0.5419) and see if you still have a problem
>> after that.
>>
>> Thanks,
>> Mike Carlson
>>
>> -----Original Message-----
>> From: troy hostetter [mailto:[hidden email]]
>> Sent: Wednesday, July 01, 2009 9:31 AM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: [WiX-users] WriteMetabaseChanges: Error 0x80070057: failed to
>> create web application
>>
>> We are getting the following error and are not sure why. We have been
>> successful at creating virtual directories in several other environments
>> (development, integration, etc.), however the environment we are currently
>> deploying to is having issues :(
>>
>> Action 14:41:11: StartMetabaseTransaction. Starting IIS Metabase
>> Transaction
>> Action 14:41:11: RollbackMetabaseTransaction. Rolling back IIS Metabase
>> Transaction
>> Action 14:41:11: CommitMetabaseTransaction. Committing IIS Metabase
>> Transaction
>> Action 14:41:11: WriteMetabaseChanges. Installing Metabase Keys and Values
>> WriteMetabaseChanges: Error 0x80070057: failed to create web application:
>> /Root/SecurityAutomation
>> Error 26105. Failed to create web application. (-2147024809
>> /Root/SecurityAutomation )
>> MSI (s) (CC!30) [15:56:04:702]: Product: kCTools (64 bit) -- Error 26105.
>> Failed to create web application. (-2147024809
>> /Root/SecurityAutomation )
>>
>> WriteMetabaseChanges: Error 0x80070057: failed to create ASP App
>> Action ended 15:56:04: InstallFinalize. Return value 3.
>> Action 15:56:04: Rollback. Rolling back action:
>> Rollback: Installing Metabase Keys and Values
>> Rollback: Committing IIS Metabase Transaction
>> Rollback: Rolling back IIS Metabase Transaction
>> Rollback: Starting IIS Metabase Transaction
>> Rollback: Copying new files
>> Rollback: Creating folders
>> Rollback: Deleting services
>> Rollback: Stopping services
>> Rollback: Updating component registration
>> Action ended 15:56:22: INSTALL. Return value 3.
>>
>> Here is our WiX IIS settings:
>>
>> <iis:WebAppPool Id="WAP__kCTools.ApplicationPool.Uber"
>> Name="[kCTools.ApplicationPool.Name.Uber]" />
>> <iis:WebSite Id="WS__kCTools.WebServices"
>> Description="[kCTools.WebServices.WebSite]">
>> <iis:WebAddress Id="WA__kCTools.AllUnassigned"
>> Port="[kCTools.WebServices.Port]" Header="[kCTools.WebServices.Header]" />
>> </iis:WebSite>
>>
>> The IIS Web site on which we are creating the virtuals exists. We are
>> able
>> to manually create virtuals. The local hosts file is set to resolve the
>> WebSite name we want to create our virtual on. We are passing in the
>> above
>> MSI properties via a mst file, and have verified they exist and are
>> properly
>> set.
>>
>> We are using WiX version 3.0.4805.
>>
>> Any ideas about what else we may consider looking at?
>>
>> - Troy
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> WiX-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> WiX-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>
>
>

troy hostetter

Re: WriteMetabaseChanges: Error 0x80070057: failed to create web application

Reply Threaded

In reply to this post by Mike Carlson (DEV DIV)

No .. it does not have an associated component. The website does exist on
the server. Here's what we have in the IIS metabase file .. so it does
exist:

<IIsWebServer Location ="/LM/W3SVC/1438500861"
AuthFlags="0"
LogExtFileFlags="LogExtFileDate | LogExtFileTime |
LogExtFileClientIp | LogExtFileUserName | LogExtFileServerIp |
LogExtFileMethod | LogExtFileUriStem | LogExtFileUriQuery |
LogExtFileHttpStatus | LogExtFileWin32Status | LogExtFileBytesSent |
LogExtFileBytesRecv | LogExtFileTimeTaken | LogExtFileServerPort |
LogExtFileUserAgent"
LogFileLocaltimeRollover="TRUE"
LogFilePeriod="1"
LogFileTruncateSize="20971520"
LogPluginClsid="{FF160663-DE82-11CF-BC0A-00AA006111E0}"
SSLCertHash="501969bd0101e2920f6410edf638a8059065e040"
SSLStoreName="MY"
SecureBindings="16.230.41.151:89:"
ServerAutoStart="TRUE"
ServerBindings="16.230.41.151:88:"
ServerComment="webservice.sharepoint.com"
>
</IIsWebServer>

My iis:WebSite and iis:WebAddress tags point to the ServerComment and port.

I recall seeing this suggestion on another post, however when i associate a
component to the locator record, it requires a Directory element and I am
unsure what value to place here. Our web site is a root web site in IIS, on
which we want to create several virtual directories.

Ideally, we do not want to create a web site .. we only want to create
virtual directories. A web site locator record should be all that we need.

- Troy

On Wed, Jul 1, 2009 at 3:23 PM, Mike Carlson (DEV DIV) <
[hidden email]> wrote:

> Does your website have a component associated with it?
>
> The log sounds as though you're using a website locator record (which is
> simply a website with no associated component), and the website it's trying
> to locate on the machine doesn't exist (in which case the install is
> intended to fail). If you want the website to be created if it doesn't
> exist, the website must be associated with a component.
>
> Thanks,
> Mike Carlson
>
> -----Original Message-----
> From: troy hostetter [mailto:[hidden email]]
> Sent: Wednesday, July 01, 2009 11:54 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] WriteMetabaseChanges: Error 0x80070057: failed to
> create web application
>
> Mike -
>
> Installed version 3.0.5419, built msi, and am now getting this error during
> install:
>
> Action 18:36:40: StartMetabaseTransaction. Starting IIS Metabase
> Transaction
> Action 18:36:40: RollbackMetabaseTransaction. Rolling back IIS Metabase
> Transaction
> Action 18:36:40: CommitMetabaseTransaction. Committing IIS Metabase
> Transaction
> Action 18:36:40: ConfigureIIsExec.
> ConfigureIIsExec: A matching web object in memory was found, but the web
> object in memory has no associated base
> ConfigureIIsExec: Error 0x80070002: Failed to find Web base
> ConfigureIIsExec: Error 0x80070002: Failed to get base of web:
> WS__kCTools.WebServices for VirtualDir
> ConfigureIIsExec: Error 0x80070002: failed while processing WebVirtualDirs
> Error 26004. Failed while processing WebVirtualDirs. (-2147024894
> )
> MSI (s) (78!98) [18:37:50:712]: Product: kCTools (64 bit) -- Error 26004.
> Failed while processing WebVirtualDirs. (-2147024894 )
>
> Action ended 18:37:50: InstallFinalize. Return value 3.
> Action 18:37:50: Rollback. Rolling back action:
> Rollback: ConfigureIIsExec
> Rollback: Committing IIS Metabase Transaction
> Rollback: Rolling back IIS Metabase Transaction
> Rollback: Starting IIS Metabase Transaction
> Rollback: Copying new files
> Rollback: Creating folders
> Rollback: Deleting services
> Rollback: Stopping services
> Rollback: Updating component registration
> Action ended 18:38:07: INSTALL. Return value 3.
>
> Thanks,
> - Troy
>
> On Wed, Jul 1, 2009 at 12:51 PM, Mike Carlson (DEV DIV) <
> [hidden email]> wrote:
>
> > A *lot* has changed in the IIS custom actions since WiX v3.0.4805,
> > including an error that looks very similar to this. First, I would
> upgrade
> > to the latest WiX 3.0 build (v3.0.5419) and see if you still have a
> problem
> > after that.
> >
> > Thanks,
> > Mike Carlson
> >
> > -----Original Message-----
> > From: troy hostetter [mailto:[hidden email]]
> > Sent: Wednesday, July 01, 2009 9:31 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: [WiX-users] WriteMetabaseChanges: Error 0x80070057: failed to
> > create web application
> >
> > We are getting the following error and are not sure why. We have been
> > successful at creating virtual directories in several other environments
> > (development, integration, etc.), however the environment we are
> currently
> > deploying to is having issues :(
> >
> > Action 14:41:11: StartMetabaseTransaction. Starting IIS Metabase
> > Transaction
> > Action 14:41:11: RollbackMetabaseTransaction. Rolling back IIS Metabase
> > Transaction
> > Action 14:41:11: CommitMetabaseTransaction. Committing IIS Metabase
> > Transaction
> > Action 14:41:11: WriteMetabaseChanges. Installing Metabase Keys and
> Values
> > WriteMetabaseChanges: Error 0x80070057: failed to create web
> application:
> > /Root/SecurityAutomation
> > Error 26105. Failed to create web application. (-2147024809
> > /Root/SecurityAutomation )
> > MSI (s) (CC!30) [15:56:04:702]: Product: kCTools (64 bit) -- Error 26105.
> > Failed to create web application. (-2147024809
> > /Root/SecurityAutomation )
> >
> > WriteMetabaseChanges: Error 0x80070057: failed to create ASP App
> > Action ended 15:56:04: InstallFinalize. Return value 3.
> > Action 15:56:04: Rollback. Rolling back action:
> > Rollback: Installing Metabase Keys and Values
> > Rollback: Committing IIS Metabase Transaction
> > Rollback: Rolling back IIS Metabase Transaction
> > Rollback: Starting IIS Metabase Transaction
> > Rollback: Copying new files
> > Rollback: Creating folders
> > Rollback: Deleting services
> > Rollback: Stopping services
> > Rollback: Updating component registration
> > Action ended 15:56:22: INSTALL. Return value 3.
> >
> > Here is our WiX IIS settings:
> >
> > <iis:WebAppPool Id="WAP__kCTools.ApplicationPool.Uber"
> > Name="[kCTools.ApplicationPool.Name.Uber]" />
> > <iis:WebSite Id="WS__kCTools.WebServices"
> > Description="[kCTools.WebServices.WebSite]">
> > <iis:WebAddress Id="WA__kCTools.AllUnassigned"
> > Port="[kCTools.WebServices.Port]" Header="[kCTools.WebServices.Header]"
> />
> > </iis:WebSite>
> >
> > The IIS Web site on which we are creating the virtuals exists. We are
> able
> > to manually create virtuals. The local hosts file is set to resolve the
> > WebSite name we want to create our virtual on. We are passing in the
> above
> > MSI properties via a mst file, and have verified they exist and are
> > properly
> > set.
> >
> > We are using WiX version 3.0.4805.
> >
> > Any ideas about what else we may consider looking at?
> >
> > - Troy
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > WiX-users mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > WiX-users mailing list
> > [hidden email]
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
> ------------------------------------------------------------------------------
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> WiX-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

Mike Carlson (DEV DIV)

Re: WriteMetabaseChanges: Error 0x80070057: failed to create web application

Reply Threaded

Make sure the IP, Port and Header all exactly match the website on the machine. These are the 3 things we use to determine if we've found the right website or not.

Thanks,
Mike Carlson

-----Original Message-----
From: troy hostetter [mailto:[hidden email]]
Sent: Wednesday, July 01, 2009 6:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WriteMetabaseChanges: Error 0x80070057: failed to create web application

No .. it does not have an associated component. The website does exist on
the server. Here's what we have in the IIS metabase file .. so it does
exist:

<IIsWebServer Location ="/LM/W3SVC/1438500861"
AuthFlags="0"
LogExtFileFlags="LogExtFileDate | LogExtFileTime |
LogExtFileClientIp | LogExtFileUserName | LogExtFileServerIp |
LogExtFileMethod | LogExtFileUriStem | LogExtFileUriQuery |
LogExtFileHttpStatus | LogExtFileWin32Status | LogExtFileBytesSent |
LogExtFileBytesRecv | LogExtFileTimeTaken | LogExtFileServerPort |
LogExtFileUserAgent"
LogFileLocaltimeRollover="TRUE"
LogFilePeriod="1"
LogFileTruncateSize="20971520"
LogPluginClsid="{FF160663-DE82-11CF-BC0A-00AA006111E0}"
SSLCertHash="501969bd0101e2920f6410edf638a8059065e040"
SSLStoreName="MY"
SecureBindings="16.230.41.151:89:"
ServerAutoStart="TRUE"
ServerBindings="16.230.41.151:88:"
ServerComment="webservice.sharepoint.com"
>
</IIsWebServer>

My iis:WebSite and iis:WebAddress tags point to the ServerComment and port.

I recall seeing this suggestion on another post, however when i associate a
component to the locator record, it requires a Directory element and I am
unsure what value to place here. Our web site is a root web site in IIS, on
which we want to create several virtual directories.

Ideally, we do not want to create a web site .. we only want to create
virtual directories. A web site locator record should be all that we need.

- Troy

On Wed, Jul 1, 2009 at 3:23 PM, Mike Carlson (DEV DIV) <
[hidden email]> wrote:

Lian Jiang

How to dynamically get current locale that my msi is built in?

Reply Threaded

Hi,

I have a wixproj which specifies "<Cultures>en-us;es-es</Cultures>". As you know, compiling this wixproj will create two MSIs located in en-us folder and es-es folder respectively.

My installer installs a UI product and need to place the corresponding resource file to the installation folder. For example, the en-us version MSI should put the en-us resource of the UI product to the installation folder.

Right now, I am hard code the locale names and put all locales' resources to the installation folder like:

<DirectoryRef Id="RESOURCE_en-us">
<Component Id='enusComponent' Guid='7251f24a-ebf5-4833-9dfb-275ee9b0f9e7' Location='local' DiskId='1' Win64='$(var.Win64AttributeValue)'>
<File Id='RES_en-us'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\en-us\resources.dll' />
</Component>
</DirectoryRef>
<DirectoryRef Id="RESOURCE_es-es">
<Component Id='enusComponent' Guid='7251f24a-4424-4833-adaa-27424b0f9e7' Location='local' DiskId='1' Win64='$(var.Win64AttributeValue)'>
<File Id='RES_es-es'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\es-es\resources.dll' />
</Component>
</DirectoryRef>

This is obvious a bad solution since it packs all locales resources for any locale's MSI. I would like pack only the corresponding locale resource for one MSI. But how can I dynamically get the current locale that the MSI is built? Is there any global variable exposing locale information?

Appreciate your help!

Thanks
Lian

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

Bob Arnson-6

Re: How to dynamically get current locale that my msi is built in?

Reply Threaded

Lian Jiang wrote:
> This is obvious a bad solution since it packs all locales resources for any locale's MSI. I would like pack only the corresponding locale resource for one MSI. But how can I dynamically get the current locale that the MSI is built? Is there any global variable exposing locale information?
>

No because it's something that happens at link time, not compile time.

--
sig://boB
http://joyofsetup.com/

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

Lian Jiang

How to dynamically get current locale that my msi is built in?

Reply Threaded

In reply to this post by Mike Carlson (DEV DIV)

Lian Jiang

Re: How to dynamically get current locale that my msi is built in?

Reply Threaded

Thanks for any suggestion.

-----Original Message-----
From: Lian Jiang
Sent: Friday, July 03, 2009 7:50 AM
To: General discussion for Windows Installer XML toolset.
Cc: Lian Jiang
Subject: How to dynamically get current locale that my msi is built in?

Hi,

I have a wixproj which specifies "<Cultures>en-us;es-es</Cultures>". As you know, compiling this wixproj will create two MSIs located in en-us folder and es-es folder respectively.

My installer installs a UI product and need to place the corresponding resource file to the installation folder. For example, the en-us version MSI should put the en-us resource of the UI product to the installation folder.

Right now, I am hard code the locale names and put all locales' resources to the installation folder like:

<DirectoryRef Id="RESOURCE_en-us">
<Component Id='enusComponent' Guid='7251f24a-ebf5-4833-9dfb-275ee9b0f9e7' Location='local' DiskId='1' Win64='$(var.Win64AttributeValue)'>
<File Id='RES_en-us'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\en-us\resources.dll' />
</Component>
</DirectoryRef>
<DirectoryRef Id="RESOURCE_es-es">
<Component Id='enusComponent' Guid='7251f24a-4424-4833-adaa-27424b0f9e7' Location='local' DiskId='1' Win64='$(var.Win64AttributeValue)'>
<File Id='RES_es-es'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\es-es\resources.dll' />
</Component>
</DirectoryRef>

This is obvious a bad solution since it packs all locales resources for any locale's MSI. I would like pack only the corresponding locale resource for one MSI. But how can I dynamically get the current locale that the MSI is built? Is there any global variable exposing locale information?

Appreciate your help!

Thanks
Lian

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

Sunkesula, Srivardhan

How to compare two properties which are in different wxs?

Reply Threaded

Hi,

Can anyone help me in how to compare two properties from different wxs
files?
Based on the equality of two properties I need to pop-up an error
message.

Thanks &Regards,
Srivardhan.

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

Lian Jiang

Re: How to dynamically get current locale that my msi is built in?

Reply Threaded

In reply to this post by Lian Jiang

Problem solved. Thanks.

-----Original Message-----
From: Lian Jiang [mailto:[hidden email]]
Sent: Sunday, July 05, 2009 8:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to dynamically get current locale that my msi is built in?

Thanks for any suggestion.

-----Original Message-----
From: Lian Jiang
Sent: Friday, July 03, 2009 7:50 AM
To: General discussion for Windows Installer XML toolset.
Cc: Lian Jiang
Subject: How to dynamically get current locale that my msi is built in?

Hi,

I have a wixproj which specifies "<Cultures>en-us;es-es</Cultures>". As you know, compiling this wixproj will create two MSIs located in en-us folder and es-es folder respectively.

My installer installs a UI product and need to place the corresponding resource file to the installation folder. For example, the en-us version MSI should put the en-us resource of the UI product to the installation folder.

Right now, I am hard code the locale names and put all locales' resources to the installation folder like:

<DirectoryRef Id="RESOURCE_en-us">
<Component Id='enusComponent' Guid='7251f24a-ebf5-4833-9dfb-275ee9b0f9e7' Location='local' DiskId='1' Win64='$(var.Win64AttributeValue)'>
<File Id='RES_en-us'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\en-us\resources.dll' />
</Component>
</DirectoryRef>
<DirectoryRef Id="RESOURCE_es-es">
<Component Id='enusComponent' Guid='7251f24a-4424-4833-adaa-27424b0f9e7' Location='local' DiskId='1' Win64='$(var.Win64AttributeValue)'>
<File Id='RES_es-es'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\es-es\resources.dll' />
</Component>
</DirectoryRef>

This is obvious a bad solution since it packs all locales resources for any locale's MSI. I would like pack only the corresponding locale resource for one MSI. But how can I dynamically get the current locale that the MSI is built? Is there any global variable exposing locale information?

Appreciate your help!

Thanks
Lian

------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/blackberry
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

Raj, Vijay

Wix v2 to v3

Reply Threaded

In reply to this post by Lian Jiang

Rob men, had posted some tips how to migrate from wix v2 to wix v3: http://bit.ly/l5fGK

Cheers'
Vijay Raj | ESD - IT Services, TI-India.
Weblog<http://www.msigeek.com/> | RSS Feed<http://feeds.feedburner.com/msigeek> | Twitter<http://twitter.com/msigeek>

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

Blair-2

Re: How to dynamically get current locale that my msi is built in?

Reply Threaded

In reply to this post by Lian Jiang

I tested something like this and it seemed to work:

Add a value (<String Id='Culture'>en-us</String>) in your .wxl files and set
the value to the appropriate value (es-es) in your translated .wxl file.
Then do something like this:

<Directory Name="!(loc.Culture)" Id="RESOURCE"/>
...
<Component Id='resComponent' Guid='*' Location='local' DiskId='1'
Win64='$(var.Win64AttributeValue)' Directory='RESOURCE'>
<File Id='RES'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\!(loc.Culture)\resources.dll'
/>
</Component>

You will need to also use a !(loc.LCID) or similar string to set the
Product/@Language value from your wxl files as well.

Note that I usually never use the Windows Installer UI (and the WixUI, by
extension), so I don't know if those values are already supplied for you.

-----Original Message-----
From: Lian Jiang [mailto:[hidden email]]
Sent: Sunday, July 05, 2009 8:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to dynamically get current locale that my msi
is built in?

Thanks for any suggestion.

-----Original Message-----
From: Lian Jiang
Sent: Friday, July 03, 2009 7:50 AM
To: General discussion for Windows Installer XML toolset.
Cc: Lian Jiang
Subject: How to dynamically get current locale that my msi is built in?

Hi,

I have a wixproj which specifies "<Cultures>en-us;es-es</Cultures>". As you
know, compiling this wixproj will create two MSIs located in en-us folder
and es-es folder respectively.

My installer installs a UI product and need to place the corresponding
resource file to the installation folder. For example, the en-us version MSI
should put the en-us resource of the UI product to the installation folder.

Right now, I am hard code the locale names and put all locales' resources to
the installation folder like:

<DirectoryRef Id="RESOURCE_en-us">
<Component Id='enusComponent'
Guid='7251f24a-ebf5-4833-9dfb-275ee9b0f9e7' Location='local' DiskId='1'
Win64='$(var.Win64AttributeValue)'>
<File Id='RES_en-us'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\en-us\resources.dll' />
</Component>
</DirectoryRef>
<DirectoryRef Id="RESOURCE_es-es">
<Component Id='enusComponent'
Guid='7251f24a-4424-4833-adaa-27424b0f9e7' Location='local' DiskId='1'
Win64='$(var.Win64AttributeValue)'>
<File Id='RES_es-es'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\es-es\resources.dll' />
</Component>
</DirectoryRef>

This is obvious a bad solution since it packs all locales resources for any
locale's MSI. I would like pack only the corresponding locale resource for
one MSI. But how can I dynamically get the current locale that the MSI is
built? Is there any global variable exposing locale information?

Appreciate your help!

Thanks
Lian

----------------------------------------------------------------------------
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize

details at: http://p.sf.net/sfu/Challenge
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

Lian Jiang

Re: How to dynamically get current locale that my msi is built in?

Reply Threaded

Thanks Blair. I am using the similar technique as you described.

-----Original Message-----
From: Blair [mailto:[hidden email]]
Sent: Wednesday, July 08, 2009 11:03 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] How to dynamically get current locale that my msi is built in?

I tested something like this and it seemed to work:

Add a value (<String Id='Culture'>en-us</String>) in your .wxl files and set
the value to the appropriate value (es-es) in your translated .wxl file.
Then do something like this:

<Directory Name="!(loc.Culture)" Id="RESOURCE"/>
...
<Component Id='resComponent' Guid='*' Location='local' DiskId='1'
Win64='$(var.Win64AttributeValue)' Directory='RESOURCE'>
<File Id='RES'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\!(loc.Culture)\resources.dll'
/>
</Component>

You will need to also use a !(loc.LCID) or similar string to set the
Product/@Language value from your wxl files as well.

Note that I usually never use the Windows Installer UI (and the WixUI, by
extension), so I don't know if those values are already supplied for you.

-----Original Message-----
From: Lian Jiang [mailto:[hidden email]]
Sent: Sunday, July 05, 2009 8:45 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to dynamically get current locale that my msi
is built in?

Thanks for any suggestion.

-----Original Message-----
From: Lian Jiang
Sent: Friday, July 03, 2009 7:50 AM
To: General discussion for Windows Installer XML toolset.
Cc: Lian Jiang
Subject: How to dynamically get current locale that my msi is built in?

Hi,

I have a wixproj which specifies "<Cultures>en-us;es-es</Cultures>". As you
know, compiling this wixproj will create two MSIs located in en-us folder
and es-es folder respectively.

My installer installs a UI product and need to place the corresponding
resource file to the installation folder. For example, the en-us version MSI
should put the en-us resource of the UI product to the installation folder.

Right now, I am hard code the locale names and put all locales' resources to
the installation folder like:

<DirectoryRef Id="RESOURCE_en-us">
<Component Id='enusComponent'
Guid='7251f24a-ebf5-4833-9dfb-275ee9b0f9e7' Location='local' DiskId='1'
Win64='$(var.Win64AttributeValue)'>
<File Id='RES_en-us'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\en-us\resources.dll' />
</Component>
</DirectoryRef>
<DirectoryRef Id="RESOURCE_es-es">
<Component Id='enusComponent'
Guid='7251f24a-4424-4833-adaa-27424b0f9e7' Location='local' DiskId='1'
Win64='$(var.Win64AttributeValue)'>
<File Id='RES_es-es'
Vital='yes'
KeyPath='yes'
Name='resources.dll'
Source='$(var.Binaries_PATH)\es-es\resources.dll' />
</Component>
</DirectoryRef>

This is obvious a bad solution since it packs all locales resources for any
locale's MSI. I would like pack only the corresponding locale resource for
one MSI. But how can I dynamically get the current locale that the MSI is
built? Is there any global variable exposing locale information?

Appreciate your help!

Thanks
Lian

----------------------------------------------------------------------------
--
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize

details at: http://p.sf.net/sfu/Challenge
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users