I use SQL Profiler to diagnose things like this. Get a trace going and run your MSI against it and you can see the exact sql that is sent to the server and the servers responses.
-----Original Message----- From: Yan Sklyarenko [mailto:yansklyarenko+...@gmail.com] Sent: 07 October 2011 09:00 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] ExecuteSqlStrings fails with the Error 0x80004005: failed to connect to database: 'master' Thanks for the suggestion, Michael! >> To determine the true reason for the failure, the administrator can look in the server's error log where a corresponding entry will be written. Could you please point out where I can find this "server's error log" referenced here? -- Yan On Fri, Oct 7, 2011 at 10:12 AM, Michael Osmond <mosm...@baytech.com.au>wrote: > Hi > > Looks like an Access Denied to me. > > Try the following to work out what is going on; > > This is from an MS Blog > > If the server encounters an error that prevents a login from succeeding, > the client will display the following error mesage. > > Msg 18456, Level 14, State 1, Server <server name>, Line 1 > Login failed for user '<user name>' > > Note that the message is kept fairly nondescript to prevent information > disclosure to unauthenticated clients. In particular, the 'State' will > always be shown to be '1' regardless of the nature of the problem. To > determine the true reason for the failure, the administrator can look in the > server's error log where a corresponding entry will be written. > > An example of an entry is: > > 2006-02-27 00:02:00.34 Logon Error: 18456, Severity: 14, State: 8. > 2006-02-27 00:02:00.34 Logon Login failed for user '<user name>'. > [CLIENT: <ip address>] > The key to the message is the 'State' which the server will accurately set > to reflect the source of the problem. In the example above, State 8 > indicates that the authentication failed because the user provided an > incorrect password. The common error states and their descriptions are > provided in the following table: > > ERROR STATE ERROR DESCRIPTION > 2 and 5 Invalid userid > 6 Attempt to use a Windows login name with SQL Authentication > 7 Login disabled and password mismatch > 8 Password mismatch > 9 Invalid password > 11 and 12 Valid login but server access failure > 13 SQL Server service paused > 18 Change password required > > State 16 = Does not have access to database. > > Regards > > Michael > > > -----Original Message----- > From: Yan Sklyarenko [mailto:yansklyarenko+...@gmail.com] > Sent: Friday, 7 October 2011 5:06 PM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] ExecuteSqlStrings fails with the Error 0x80004005: > failed to connect to database: 'master' > > Hello WiX Community, > > I have the following problem. > > I have a number of SqlString elements which run "CREATE DATABASE ... FOR > ATTACH" kind of queries. It fails to run on SQL 2008 (I tested on R2, but > it > seems that pure 2008 is also affected), DEFAULT INSTANCE ONLY. I mean, if I > specify any named instance (like .\SQ:EXPRESS) it works perfectly fine. > This > is the excerpt from the log file: > ... > MSI (s) (50:AC) [20:36:07:604]: Executing op: > ActionStart(Name=ExecuteSqlStrings,Description=Executing SQL Strings...,) > Action 20:36:07: ExecuteSqlStrings. Executing SQL Strings... > MSI (s) (50:AC) [20:36:07:604]: Executing op: > > CustomActionSchedule(Action=ExecuteSqlStrings,ActionType=25601,Source=BinaryD ata,Target=**********,CustomActionData=**********) > MSI (s) (50:80) [20:36:07:604]: Invoking remote custom action. DLL: > C:\Windows\Installer\MSI7A5C.tmp, Entrypoint: ExecuteSqlStrings > ExecuteSqlStrings: Entering ExecuteSqlStrings in > C:\Windows\Installer\MSI7A5C.tmp, version 3.6.2005.0 > ExecuteSqlStrings: Error 0x80004005: failed to connect to database: > 'master' > Error 26203. Failed to connect to SQL database. (-2147467259 master ) > MSI (s) (50!C4) [20:36:26:646]: Product: MyProduct 2.0 - trunkdefaultsql -- > Error 26203. Failed to connect to SQL database. (-2147467259 master ) > CustomAction ExecuteSqlStrings returned actual error code 1603 (note this > may not be 100% accurate if translation happened inside sandbox) > Action ended 20:36:26: InstallFinalize. Return value 3. > ... > > I tested on both WiX 3.5 (release build) and WiX 3.6 (latest available, > 2201). > > Has anyone seen this before? What could be the reason? I tried reporting > this as an issue, but developers responded that it doesn't sound like a WiX > issue... > > Thanks in advance, > > -- Yan > > ----------------------------------------------------------------------------- - > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2dcopy2 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ----------------------------------------------------------------------------- - All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ 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. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
