Roger that.

Duane T. Doutel
Doutel Software Services, LLC

-----Original Message-----
From: wix-users-requ...@lists.sourceforge.net
[mailto:wix-users-requ...@lists.sourceforge.net] 
Sent: Thursday, March 17, 2011 4:02 PM
To: wix-users@lists.sourceforge.net
Subject: WiX-users Digest, Vol 58, Issue 102

Send WiX-users mailing list submissions to
        wix-users@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/wix-users
or, via email, send a message with subject or body 'help' to
        wix-users-requ...@lists.sourceforge.net

You can reach the person managing the list at
        wix-users-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific than
"Re: Contents of WiX-users digest..."


Today's Topics:

   1. Re: Installer for version 3.6.1511.0 fails. (Kevin Burton)
   2. Re: Multifeature filetype association (The Eligible Bachelors)
   3. Re: Error 26201. Error -2147467259: failed to     create  SQL
      database (kim)
   4. Trouble upgrading from 3 to 3.5 on VS 2005 (Skip Sailors)
   5. Re: Error 26201. Error -2147467259: failed to create      SQL
      database (Mike Rerick)


----------------------------------------------------------------------

Message: 1
Date: Thu, 17 Mar 2011 12:26:21 -0500
From: Kevin Burton <kev...@buyseasons.com>
Subject: Re: [WiX-users] Installer for version 3.6.1511.0 fails.
To: General discussion for Windows Installer XML toolset.
        <wix-users@lists.sourceforge.net>
Message-ID:
        
<27acc7e8b541c04cac722b5e9eb4c95a0cc3a86...@mercury.asgard.buyseasons.com>
        
Content-Type: text/plain; charset="us-ascii"

This doesn't help you with your problem but I have had a lot of weird
problems since installing IE9. I am not sure how to rollback but I think I
need to.

-----Original Message-----
From: du...@doutel.com [mailto:du...@doutel.com]
Sent: Thursday, March 17, 2011 12:24 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installer for version 3.6.1511.0 fails.

I note that someone is having the same problem with the 1504 build. I'm
wondering if perhaps the IE9 RTW is the culprit. These are the relevant
lines from the log file (I've attached the full log file, as well):

 

[1F08:18C4][2011-03-16T12:43:31.835-05:00]: Caching executable from:
C:\Users\Duane\Desktop\Wix36.exe to: C:\ProgramData\Package
Cache\{25c5ee84-5c84-498b-bfe1-381a2bc52edd}\WiX36.exe

[1990:0B0C][2011-03-16T12:43:31.965-05:00]: Download engine HTTP 200 HEAD to
<http://wix.sourceforge.net/releases/3.6.1511.0/data/Wix36.msi>
http://wix.sourceforge.net/releases/3.6.1511.0/data/Wix36.msi

[1990:0B0C][2011-03-16T12:43:31.965-05:00]: Error 0x80072f76: Failed to get
size of download.

[1990:0B0C][2011-03-16T12:43:31.965-05:00]: Error 0x80072f76: Failed to get
size and time for URL:
<http://wix.sourceforge.net/releases/3.6.1511.0/data/Wix36.msi>
http://wix.sourceforge.net/releases/3.6.1511.0/data/Wix36.msi

[1990:0B0C][2011-03-16T12:43:31.965-05:00]: Error 0x80072f76: Failed to
download URL using wininet.

[1990:0B0C][2011-03-16T12:43:31.966-05:00]: Error 0x80072f76: Failed to
download payload.

[1990:0B0C][2011-03-16T12:43:31.966-05:00]: Error 0x80072f76: Failed to
acquire payload.

[1990:0B0C][2011-03-16T12:43:31.967-05:00]: Error 0x80072f76: Failed to
cache packages.

[1F08:18C4][2011-03-16T12:43:31.967-05:00]: Removing cached bundle:
{25c5ee84-5c84-498b-bfe1-381a2bc52edd}, from path: C:\ProgramData\Package
Cache\{25c5ee84-5c84-498b-bfe1-381a2bc52edd}

[1990:0B0C][2011-03-16T12:43:31.970-05:00]: Apply complete, result:
0x80072f76 restart: No

[1990:0B0C][2011-03-16T12:43:35.830-05:00]: Shutting down, exit code: 0x0

 

Best!

Duane T. Doutel

Doutel Software Services, LLC

 




------------------------------

Message: 2
Date: Thu, 17 Mar 2011 11:23:18 -0700 (PDT)
From: The Eligible Bachelors <theeligiblebachel...@yahoo.com>
Subject: Re: [WiX-users] Multifeature filetype association
To: wix-users@lists.sourceforge.net
Message-ID: <818676.79514...@web121805.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1

Thanks for the great ideas.

I tried to figure out how to suppress this specific error, but was unable
to.

Then I tried your idea of moving the RegistryValue into the master component
and it worked. I am able to install and uninstall the optional components
and associations work as expected. It's a little messy on the registry, but
it gets it done.

Thanks!


--- On Thu, 3/17/11, David Watson <dwat...@sdl.com> wrote:

> From: David Watson <dwat...@sdl.com>
> Subject: Re: [WiX-users] Multifeature filetype association
> To: wix-users@lists.sourceforge.net
> Date: Thursday, March 17, 2011, 9:04 AM You will get the ice 69 error 
> because windows installer can't know for sure if that feature is being 
> installed. If you can guarantee in all situations that the main 
> feature will be installed when you install the optional feature, you 
> can ignore (suppress) the error.
> 
> What should also work is that you could leave the ProgId and Extension 
> in the optional component and to write the verb in with a registry 
> element in the main component. I did this recently to share the 
> file-type and icon between two products (the file-type registration 
> was in a shared
> msi) but only allow
> the main application to do something when you clicked a registered 
> file type.
> 
> As the #mainExe is in the same feature as the .exe then you won't get 
> an ice
> 69 yet you get the same functionality.
> 
> You may need to check what happens when only component A is installed, 
> I never had that scenario so I'm not sure what would happen to the 
> file ascociation.
> 
> 
> Your e.g. modified.
> 
> <Component Id="A">
> ? <File Id="MainEXE" name="Main.exe"
> Source="$(var.BINDIR)/Main.exe"/>
> 
>  <RegistryValue Root="HKLM" Id=" MainEXEVerb"
> Action="write"
> ? ? ? ? ? ? ? ?
> ? ?
> ???Key="Software\Classes\extfile\shell\open\command"
> ? ? ? ? ? ? ? ?
> ? ? ???Value ='"[#MainEXE] "%1"'
> ? ? ? ? ? ? ? ?
> ? ? ???Type="expandable"
> />? ? ? 
> 
> ? ...
> 
> <Component Id="B">
> 
> ? ...
> ? <ProgId Id='extfile' Description='Ext file'> ? ? <Extension Id='ext'
> ContentType='application/ext' />
> ? </ProgId>
> ? ? ? 
> </Component>
> 
> 
> -----Original Message-----
> From: The Eligible Bachelors [mailto:theeligiblebachel...@yahoo.com]
> 
> Sent: 16 March 2011 21:03
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Multifeature filetype association
> 
> Ok. So I have removed the property with the file search.
> Now it looks like:
> 
> <Component Id="A">
> ? <File Id="MainEXE" name="Main.exe"
> Source="$(var.BINDIR)/Main.exe"/>
> ? ....
> </component>
> 
> ? ...
> 
> <Component Id="B">
> 
> ? ...
> ? <ProgId Id='extfile' Description='Ext file'> ? ? <Extension Id='ext'
> ContentType='application/ext'>
> ? ? ? <Verb Id='open' Command='Open'
> TargetFile='[MainEXE]' Argument='"%1"'
> />
> ? ? </Extension>
> ? </ProgId>
> ? ? ? 
> </Component>
> 
> 
> Produces
> ? "Unresolved reference to 'File:[MainEXE]' in section ...
> ? 
> If I then change it to TargetFile='[#MainEXE]', I get the same error.
> 
> If I change it to TargetProperty='[#MainEXE]', I get:
> 
> ICE69: Mismatched component reference. Entry 
> 'reg1099EB9499BDFA8BA8EBB7D10C985FE0' of the Registry table belongs to 
> component 'B'. However, the formatted string in column 'Value' 
> references file 'MainEXE' which belongs to component 'A'. Components 
> belong to different features (LGHT0204)
> 
> 
> 
> 
> 
> > You need to use either [#fileid] for a long path or [!fileid] for a 
> > short path. Since it's the same MSI there should be no
> need
> > to mess
> > about with Properties just change the TargetProperty
> to
> > reference the
> > File Id of the executable.
> > 
> > The ICE69 error is because there's no File with Id of "MAINEXEC" in 
> > your MSI. If the File Element of main.exe has Id="Main.exe"
> use
> > [#Main.exe].
> > See http://msdn.microsoft.com/en-us/library/aa368609.aspx
> > 
> > Actually having looked at the Verb syntax you could
> drop
> > the
> > TargetProperty attribute & use the TargetFile
> attribute
> > instead & point
> > it at the File Id of Main.exe. It may achieve the
> exact
> > same thing as
> > above but it should be better syntactically since the package is 
> > installing the executable & the (optionally) the
> file
> > type.
> > 
> 
> 
> ? ? ? 
> 
> ----------------------------------------------------------------------
> -------
> -
> Colocation vs. Managed Hosting

> A question and answer guide to determining the best fit for your 
> organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> SDL PLC confidential, all rights reserved.
> If you are not the intended recipient of this mail SDL requests and 
> requires that you delete it without acting upon or copying any of its 
> contents, and we further request that you advise us.
> SDL PLC is a public limited company registered in England and Wales.? 
> Registered number: 02675207.
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire 
> SL6 7DY, UK.
> 
> 
> ----------------------------------------------------------------------
> --------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit for your 
> organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 


      



------------------------------

Message: 3
Date: Thu, 17 Mar 2011 12:04:46 -0700 (PDT)
From: kim <contactme...@gmail.com>
Subject: Re: [WiX-users] Error 26201. Error -2147467259: failed to
        create  SQL     database
To: wix-users@lists.sourceforge.net
Message-ID: <1300388686430-6182144.p...@n2.nabble.com>
Content-Type: text/plain; charset=us-ascii

Can someone please help me with this issue?

I checked that Network Service account was not having full control
permission on C:\Program Files\Microsoft SQL Server folder and subfolders
where is the default path to create database.

Still database creation is failing with this error (as mentioned in subject
of this post)

I am installing my application on XP machine and database is SQL Server
2008. Verbose log and Event viewer do not provide any more info except this
same error message

I am really stuck here with no clue to proceed further!

thanks!

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Error-26201-Er
ror-2147467259-failed-to-create-SQL-database-tp6163225p6182144.html
Sent from the wix-users mailing list archive at Nabble.com.



------------------------------

Message: 4
Date: Thu, 17 Mar 2011 12:26:59 -0700
From: "Skip Sailors" <ssail...@wpc-edi.com>
Subject: [WiX-users] Trouble upgrading from 3 to 3.5 on VS 2005
To: <wix-users@lists.sourceforge.net>
Message-ID:
        <ca4a5f26aca3a042814eb81570a1835e01c8c...@sato.wpc.wpcdev.net>
Content-Type: text/plain;       charset="us-ascii"

List,

 

I am sure this is a FAQ, but I had trouble finding anything obvious.
Can you help me find the right thing to read.

 

I have a project that used WiX 3 and Votive to build an installer for a .NET
2.0 application using Visual Studio Professional 2005.  We haven't had to
upgrade this product yet, but yesterday we found that we need an upgrade for
existing customer.  I tried to add an Upgrade element to the installer, and
a MajorUpgrade element.  The compiler complained that the MajorUpgrade
element is an unexpected child of Product.  After minimal fussing, I
thought, well, I will upgrade from 3.0 to 3.5 WiX and see if it helps.

 

It didn't help.  Now I get a message when opening the solution that "The
application for 'Setup.wixproj' is not installed."  I just installed it!
Please help me find the right document that will explain to me what I am
missing.  What do I have to do so that my IDE can find the new WiX?

 

TIA

 

Skip Sailors, Consultant

Washington Publishing Company

ssail...@wpc-edi.com <mailto:ssail...@wpc-edi.com> 

Cell: 425.753.4601

Fax: 425.562.2245

www.wpc-services.com <http://www.wpc-services.com/> 

 



------------------------------

Message: 5
Date: Thu, 17 Mar 2011 12:30:47 -0700
From: Mike Rerick <mrer...@iwsinc.com>
Subject: Re: [WiX-users] Error 26201. Error -2147467259: failed to
        create  SQL database
To: "General discussion for Windows Installer XML toolset."
        <wix-users@lists.sourceforge.net>
Message-ID:
        <aanlktik4slz8hptjmtvz5pywzhzzewk7bpdmgbfgr...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

I have seen this error when the username or password is incorrect.

How are you trying to access the database: via windows or server
authentication?

If you are trying to access sql express via a user name (probably sa?) and
password, did you install SQL Express in mixed mode and specify a sa
password?

If you are using windows authentication, don't specify a user or password.



This is some code that I use to do database installs on sql express 2005 and
sql server 2005.

I have custom screens in my installer that get values for these properties
(You could hard code values for them):
   SQLSERVER_AUTHENTICATION (Windows or Server)
   SELECTEDSQLSERVER (name of the database server to use
[MyComputer\SQLEXPRESS])
   DBAUSERNAME (usually sa, can be any user with the correct admin
permissions)
   DBAPASSWORD (admin user password)

        <util:User Id="SQLAdminUser" Name="[DBAUSERNAME]"
Password="[DBAPASSWORD]"/>
        <Binary Id="CreateDbSqlSCript"
SourceFile="some-path-to-scripts\db_create.sql"/>

        <ComponentGroup Id="CreateDBServerAuth">
          <Component Id="CreateDatabaseServer" Directory="INSTALLDIR"
Guid="{DF7D8FA0-893A-4fe6-B875-EE95592311F6}">
              <Condition>
               (NOT OLDERVERSIONBEINGUPGRADED) AND (NOT Installed) AND
(SQLSERVER_AUTHENTICATION = "Server")
              </Condition>
              <CreateFolder Directory="INSTALLDIR"/>
              <sql:SqlDatabase Id="SqlDbServer" Database="my-db-name"
                               Server="[SELECTEDSQLSERVER]"
User="SQLAdminUser"
                               CreateOnInstall="yes" DropOnUninstall="no">
              </sql:SqlDatabase>
          </Component>
        </ComponentGroup>
        <ComponentGroup Id="CreateTablesDataServerAuth">
          <Component Id="CreateDatabaseTablesAndDataServer" DiskId="1"
KeyPath="yes"
                     Directory="INSTALLDIR"
Guid="{B71DCA42-40AC-4316-9853-36FD28F77500}">
              <Condition>
                (NOT OLDERVERSIONBEINGUPGRADED) AND (NOT Installed) AND
(SQLSERVER_AUTHENTICATION = "Server")
              </Condition>
              <sql:SqlScript  Id="script1" BinaryKey="CreateDbSqlSCript"
SqlDb="SqlDbServer"
                              User="SQLAdminUser" ExecuteOnInstall="yes"
ExecuteOnUninstall="no"
                              ContinueOnError="no" Sequence="1"/>
                                       . . .
          </Component>
        </ComponentGroup>

        <ComponentGroup Id="CreateDBWindowsAuth">
          <Component Id="CreateDatabaseWindows" Directory="INSTALLDIR"
Guid="{9B653419-930D-4134-8C3B-7588DEA154CF}">
              <Condition>
               (NOT OLDERVERSIONBEINGUPGRADED) AND (NOT Installed) AND
(SQLSERVER_AUTHENTICATION = "Windows")
              </Condition>
              <CreateFolder Directory="INSTALLDIR"/>
              <sql:SqlDatabase Id="SqlDbWindows" Database="my-db-name"
                               Server="[SELECTEDSQLSERVER]"
CreateOnInstall="yes"
                               DropOnUninstall="no">
              </sql:SqlDatabase>
          </Component>
        </ComponentGroup>
        <ComponentGroup Id="CreateTablesDataWindowsAuth">
          <Component Id="CreateDatabaseTablesAndDataWindows" DiskId="1"
KeyPath="yes"
                     Directory="INSTALLDIR"
Guid="{098D6F93-4964-4989-A467-92A37719C4A8}">
              <Condition>
                (NOT OLDERVERSIONBEINGUPGRADED) AND (NOT Installed) AND
(SQLSERVER_AUTHENTICATION = "Windows")
              </Condition>
              <sql:SqlScript  Id="script1" BinaryKey="CreateDbSqlSCript"
SqlDb="SqlDbWindows"
                              ExecuteOnInstall="yes" ExecuteOnUninstall="no"
                              ContinueOnError="no" Sequence="1"/>
                                         . . .
          </Component>
        </ComponentGroup>


Hope this helps.
      *Mike Rerick*
      *Sr. Software Engineer*

[image: Google Docs] <http://www.iwsinc.com>*ImageWare Systems, Inc.*
      9200 S.E. Sunnybrook Blvd., Suite 170
      Clackamas, OR   97015

      Office: (503) 353-8068  Fax: (503) 353-8065 On Thu, Mar 17, 2011 at
12:04 PM, kim <contactme...@gmail.com> wrote:

> Can someone please help me with this issue?
>
> I checked that Network Service account was not having full control 
> permission on C:\Program Files\Microsoft SQL Server folder and 
> subfolders where is the default path to create database.
>
> Still database creation is failing with this error (as mentioned in 
> subject of this post)
>
> I am installing my application on XP machine and database is SQL 
> Server 2008. Verbose log and Event viewer do not provide any more info 
> except this same error message
>
> I am really stuck here with no clue to proceed further!
>
> thanks!
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Error-26
> 201-Error-2147467259-failed-to-create-SQL-database-tp6163225p6182144.h
> tml Sent from the wix-users mailing list archive at Nabble.com.
>
>
> ----------------------------------------------------------------------
> --------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit for your 
> organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>

The information contained in this transmission contains potentially
privileged, export controlled and/or confidential information of Imageware
Systems, Inc. or its customers or partners.  It is intended only to be read
by the person(s) named above and for no other purpose.  You are hereby
notified that any dissemination, distribution, duplication of this
communication or use of its contents for any purpose not authorized
expressly by Imageware Systems, Inc. is strictly prohibited and could lead
to both civil and/or criminal penalties.  If you are not the intended
recipient, you are prohibited to review the contents herein and please
contact the sender by reply e-mail and destroy all copies of the original
message.  To reply to our e-mail administrator directly, please send an
e-mail to emailad...@iwsinc.com


------------------------------

----------------------------------------------------------------------------
--
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit for your
organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d

------------------------------

_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


End of WiX-users Digest, Vol 58, Issue 102
******************************************


------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to