SQL Express can be a pain to install silently, the trick is to run it from
the command line without the silent switch on until you are sure you have the
right parameters.
I suspect you will at least need to add the /IACCEPTSQLSERVERLICENSETERMS
parameter.
-Original Message-
From: Daniel
Done. Thanks!
What are your thoughts on using Burn like this to be both an installer and
autoupdate? Good idea, bad idea...?
Chris
On Tue, Mar 20, 2012 at 9:51 PM, Rob Mensching r...@robmensching.com wrote:
Please open a bug (with all this information) to track the issue.
On Tue, Mar 20,
PS: When you discover the correct set of parameters, let us know here.
There is a plan afoot to pre-bake the silent install of a bunch of well
known redists so you can use them by just doing PackageGroupRef Id=x at
the correct place in your Chain.
On Wed, Mar 21, 2012 at 3:33 AM, David Watson
Hello.
Recently we have some problem with bundle maintaining. Here is use case:
1. Customer gets cd-layout and renames bundle from OldName to NewName.
2. Then he installs some 2 products from bundle.
3. Then he deletes one and tries to install it again.
Boom! Bundle failed
Those links were for different errors - that hex code must be generic
I'm getting my friendly neighborhood DBA to help. He pointed me to folder
C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log
(Since this is SQL Server 2008 R2 Express). Which creates a folder for each
My comment below wasn't entirely correct - the MSI Package WAS uninstalled -
but the SQL Express instance wasn't. I have verified that the command line in
the UninstallCommand does work when run manually - it seems it wasn't called
when I did the uninstall...
-Original Message-
From:
As of WiX 3.6.2719.0, the standard MSU exit codes are not being handled
properly by MsuPackage. In particular, the burn bootstrapper does not
notice when an MSU indicates a reboot is required and instead just moves on
to the next package.
--
View this message in context:
7 matches
Mail list logo
