This is all that I'm getting back from the install log:
-
Action 17:14:39: ExecXmlFile.
CustomAction ExecXmlFile returned actual error code 1603 (note this may not be
100% accurate if translation happened inside sandbox)
Action ended 17:14:39: InstallFinalize. Return value 3.
Action 17:14:39:
I'm pretty sure that there used to be, Martin, but I don't see it in v3; IIRC,
wildcard support was explicitly dropped "by design".
If you figure it out and I missed it somewhere, LMK! We wrote a custom MSBuild
task to rip through a directory tree and write out include files for WiX to do
this.
Joe, that smells like your MSI can't find either SQLCMD or your SQL script.
I'll bet it's the SQL script; it's either already removed before your call to
SQLCMD or you need to provide the full path to it.
-Original Message-
From: Joe Osman [mailto:joe.os...@tait.co.nz]
Sent: Sunday, Fe
e the Wix setup...)
Regards
Daniel
From: David Reed (SQL) (via Nabble)
[mailto:ml-user+60230-489561...@n2.nabble.com]
Sent: 29 January 2009 17:46
To: Daniel Schmitz
Subject: Re: [WiX-users] Wix - integrating Microsoft SSIS package into
setup
Been there, done that a few times. It depends on the packa
Been there, done that a few times. It depends on the package, Daniel. How are
the package configurations setup? Environment variables? User registry keys?
XML config files? I've used all three, including manipulating the XML files at
installation time to persist user selections made during setup
coming through as they should? Is there a WiX log
or a way to add one so that I can get a more detailed message?
Eric
-Original Message-
From: David Reed [mailto:david.r...@microsoft.com]
Sent: Monday, January 26, 2009 3:34 PM
To: General discussion for Windows Installer XML toolset.
S
DATABASE Suite FROM DISK = 'G:\Database\SuiteBlank.bak' WITH
MOVE 'Suite_Data' TO G:\ ...\Suite_Log.ldf',REPLACE
Eric Latendresse
-Original Message-
From: David Reed [mailto:david.r...@microsoft.com]
Sent: Friday, January 23, 2009 11:44 PM
To: General discussi
It really depends on what those 9k scripts are doing.
If your scripts are a raft of INSERT statements or other transactions, then you
can probably switch to CSVs and bulk load (much faster), which is what we do
with AdventureWorks now for SQL Server 2008 samples. The WiX3 code for ours is
check
Glad you got that working, Nicolas. You're following a path we're considering
for future releases of AdventureWorks (that's pretty much what we're doing for
the T-SQL scripts to build the databases now); thanks for sharing your
learnings. We're also considering PowerShell and/or DTF. We're leani
ckages available for downloads for non-Express
editions..
Arun Perregattur
-Original Message-----
From: David Reed [mailto:david.r...@microsoft.com]
Sent: Tuesday, January 13, 2009 4:50 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SQL Server 2008 Bootstra
It's in the VS 2008 SP1 SKU... but not in the patches. Here's a workaround from
the Express team blog:
http://blogs.msdn.com/sqlexpress/archive/2008/09/12/faq-installing-the-sql-server-2008-express-clickonce-bootstrapper-for-visual-studio-2008-sp1.aspx
HTH, Arun.
-Original Message-
Fr
If the identity running the installation doesn't have sysadmin privileges,
you're not going to be able to grant anything to yourself... Maybe I'm not
understanding the workflow that you're trying to achieve. We can take it
offline if you like.
-Original Message-
From: [EMAIL PROTECTE
ding to my ideas.
I'm newbie in Wix, so I'm only discovering magics of this beautiful
technology ;)
David Reed (SQL) wrote:
>
> I'm a little confused on the desired outcome. You're detaching the
> database on uninstall, instead of dropping it (which would delete the
>
I haven't peeked at the code, but based on your description, I'll bet that it's
closing and reopening connections for each SQL string instead of using
connection pooling, etc.
Fire up SQL Profiler and cap a trace of connection events during the
installation and that will tell you for sure what
I'm a little confused on the desired outcome. You're detaching the database on
uninstall, instead of dropping it (which would delete the files)... You're also
trying to drop the database elsewhere while the connection context is mapped to
the database you're trying to drop, which won't work (you
Nic, what I've been doing is using the sql:sqldatabase as an anchor outside a
component with "master" as the target database (since it's guaranteed to be
there and any authenticated user is guaranteed to be able to connect to it),
then I use the sql:sqlstring to restore the database from a compr
ver it is) for SSRS deployment, we would most
likely contribute it back to WiX directly or create a community project in
CodePlex.
David Reed | Program Manager - SQL Server Community & Samples, SQL Ranger,
MCA:Database
[EMAIL PROTECTED] | o: 425-703-0867 | m: 425-765-0487 |
http://blogs
I've got a set of features that I moved under a new parent feature, and the new
parent feature has a pair of options that A) don't make sense and B) I don't
want... but I don't see how to disable them in the v3 schema. They only appear
for the parent feature when it has children; other features
in solution explorer and in the resulting dialog add
> WixSqlExtensions.dll.
>
> Neil
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:wix-users-
> [EMAIL PROTECTED] On Behalf Of David Reed (SQL)
> Sent: Thursday, June 12, 2008 3:27 PM
> To: wix-users@lists
rosoft.com/wix/2006/wi";
xmlns:sql="http://schemas.microsoft.com/wix/SqlExtension";>
Once I get past that, I'll be able to sort through the redefine logical breaks
that came with 3.0.4130.0, but I guess I'm reverting to 3.0.4123.0 for now...
What new reference do I n
worded question was. Thanks for
stating it more clearly than I did!
From: Christopher Painter [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 08, 2007 17:05
To: Bob Arnson; David Reed (MCS - HOUSTON)
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Side-by-side installation questio
> From: Szentpali Janos
> Just curious :D Why would anyone want to have the same application
> installed many times on a single computer?
In a hosted environment where server consolidation is occurring, multiple
configurations of the same applications will coexist and execute concurrently,
compl
Howdy, again, folks. I have been trying to "reuse" a single installer to deploy
multiple "instances" of the same product to a single machine, and this seems to
be impossible with a single MSI. The installing user will specify the instance
name, path, etc, which distinguish it from other instance
Howdy, folks. I'm trying to accomplish the following (without success):
This creates an environment variable named [TARGETENV] *not* an environment
variable of the name specified in the installer form's edit field.
I can understand Id not supporting property expansion, but I'm hosed if Name
d
24 matches
Mail list logo
