Hi Michael, The property SQLSERVER is being set to '(local)\SQLEXPRESS' from within the MSI database, although if I edit this using Orca to some other value it gets reset back to the above value when the setup program is run (as observed from the log file).
I think that the above value is correct because I use this value in own WiX generated installation and everything installs just fine. I do not think that there is a problem with SQL Express as I have been using it for many months now without problem. What confuses me the most is why the same merge module works fine on my machine using my own WiX generated installer but does not work when it is integrated with the InstallShield setup program. The same property value is being used and it is run on the same PC using the same account. The problem must be something to do with what the setup program is doing. I cannot try SQL Profiler as this is not supplied with SQL Express (can I? If so, where do I get it from?). However I tried using Teratrax Performance Viewer which has some similar functionality, which at least lets me log failed connection attempts, but it reported nothing. I am still stuck. Is there any way to debug the steps that the installer is performing to see exactly where the error is generated and perhaps try some alternative values? John Michael Osmond wrote: > > John, > > Firstly what value is the property SQLSERVER being set to, and where is it > set? > > If that is okay, then i suspect it is a SQL Express set up issue. > > The 0x80004005 error could also be an access denied error from the file > system - it does not look like you are specifying a path to where the > database files are being located. When SQL server does something it > actually executes using the SQL Service account - so the creation of the > underlying database files are performed as that account not the installing > account - I have seen this cause some interesting file permission issues. > > Have you tried the InstallShield setup on different machines? > You could try running the SQL Profiler to trace what is happening in SQL > Express during the install. > You could also try using SQLCMD to do a Create Database on the problem > machine, just to see what happens. > > You are right about the User attribute, it lets WIX use an SQL User rather > than a Windows Account, as far as I know you can't disable Windows > Integrated Auth in SQL 2005, so for that reason I don't use the User > attribute. > > What role does the user doing the install have in the SQL Express system. > By default the Administrators group should be an SQL Admin - but you may > need to double check this. > > Hope this helps > > Michael > -- View this message in context: http://n2.nabble.com/Help%3A-%27Error-26201.Error--2147467259%3A-failed-to-create-SQL-database%27-tp3314870p3332575.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
