Michael, I do have access to a standard edition of SQL Server and so I used the SQL Profiler from that to analyse what was happening during the install.
With my WiX generated installer I saw all the login, database creation and stored procedure addition stuff that I expected. However, when I used the InstallShield setup program the profiler was silent - it reported absolutely nothing; not even a failed login attempt (assuming that it does show such information). I guess that I am now going to have to debug the custom action. I downloaded the source code, but I have not built it yet as I do not have all the requisite tools. Do you have any idea where I should be looking for the Assert that you mention and how I ensure that the custom action is included in the installation? I just can't spot where the code is located in the source tree that defines the custom action nor can I find any documentation to that effect. John Michael Osmond wrote: > > John, > > I have not used merge modules, so not sure what they would do to the MSI. > > For debuging the custom action, you need to get the source code for WIX, > then there is a line (I think it is an Asert) at the start of each action > that you uncomment and compile the custom action. My understanding is > gets you a point in the install where you can attach the debuger (I have > not tried this myself). > > I didn't think of the fact that profiler is not in SQL Express. Do you > have a copy of SQL Standard or Developer, even on another machine? You > could use those, and connect to the Express instance on your machine (you > may need to change the Surface Area Configuration to allow remote > connections. > > Profiler is just a graphic interface into a number of stored procedures - > so you can actually setup traces from the stored procedures, and even > import the trace files into a table for examination. Check out > www.sqlservercentral.com there may be some pointers there (its a fairly > useful site of things SQL). > > The SQL below will create a standard profiler trace to a file then use > fn_trace_gettable to import the file into an SQL Table to do examine > (example of this also included). Not pretty, but may do what you need. > > ... stuff deleted ... > -- View this message in context: http://n2.nabble.com/Help%3A-%27Error-26201.Error--2147467259%3A-failed-to-create-SQL-database%27-tp3314870p3342473.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
