Amy,
Our DB installation process originally specified the SQL instance by name
regardless of it being the default instance or not. We discovered that if we
named the default instance (MSSQLSERVER) DB creation would fail with
"unknown error" after 10-15 minutes of churning along. Changing our proce
MAIL PROTECTED] On Behalf Of EdB
Sent: 18 October 2007 01:20
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] WiX v3 Sql Extension not executing SqlScript
I am able to use these elements successfully with 3.0.3328.0. This is the
first v3 build I've used so don't know if th
]
From: Chad Petersen [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 18, 2007 9:18 AM
To: Amy Rosewater; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] WiX v3 Sql Extension not executing SqlScript
You might try it to start with in a bit simpler format. Just have the
]
Sent: Thursday, October 18, 2007 9:18 AM
To: Amy Rosewater; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] WiX v3 Sql Extension not executing SqlScript
You might try it to start with in a bit simpler format. Just have the
ExecuteOnInstall="yes"
And
You might try it to start with in a bit simpler format. Just have the
ExecuteOnInstall="yes"
And remove the
ContinueOnError="no" RollbackOnUninstall="yes"
If it works then add back in one of those two at a time. You might find
the ContinueOnError="no" is causing a problem. They are
I am able to use these elements successfully with 3.0.3328.0. This is the
first v3 build I've used so don't know if there was an intentional change
between these releases.
Amy Rosewater wrote:
>
> Hi,
>
>
> Is this still an issue with the version 3.0.2925.0?
>
>
> I have a WiX v3 installat
6 matches
Mail list logo
