Figured it out. the DetectCondition was what I was missing.
I have it working with SQL Server 2008 R2 , install remove works
correctly without issue.
Is it in the help documentation ? Maybe I missed it.
On Sat, May 26, 2012 at 12:12 PM, Rob Mensching wrote:
> Your ExePackage needs a DetectCondi
Your ExePackage needs a DetectCondition attribute to be detected.
On Fri, May 25, 2012 at 10:53 AM, Benjamin Bennett wrote:
> Nope that wasn't it . Nothing in the SQL server logs.
> Burn is checking if it is installed somehow and determining that it
> isn't installed.
>
> On Fri, May 25, 2012 at
Nope that wasn't it . Nothing in the SQL server logs.
Burn is checking if it is installed somehow and determining that it
isn't installed.
On Fri, May 25, 2012 at 11:16 AM, Richard Mayes wrote:
> Don't you have to specify what features to remove?
> http://msdn.microsoft.com/en-us/library/ms144259
Don't you have to specify what features to remove?
http://msdn.microsoft.com/en-us/library/ms144259(v=sql.100).aspx#Uninstall
Also to debug the Sql install check the logs that are created in the
installation dir (C:\Program Files (x86)\Microsoft SQL
Server\100\Setup Bootstrap\Log) they are very us
Notes I seen this
http://sourceforge.net/mailarchive/forum.php?thread_name=8701D1480741164DB71E42643C4A489F03380D86%40emeamail0305.global.sdl.corp&forum_name=wix-users
Depending on whether you are using SQL Server 2008 or SQL Server 2008 R2.
The option /IAcceptSQLServerLicenseTerms is NOT a val
5 matches
Mail list logo