Does this help? Do you need anything else from me? On Tuesday, February 28, 2017 at 10:18:08 AM UTC-5, Justin Dugan wrote: > > The event log shows an install failure with code 1603. The application log > shows the following: > > [000433][06:45:02:0024] > [15][ExecuteSequence.InstallDatabase][CreateConnection] > [000434][06:45:02:0397] [16][SQLServer.CreateConnection][CreateConnection] > SqlExceptionLogin failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. > [000435][06:45:02:0397] > [14][StandardActions.DisplayRollBackError][DisplayRollBackError] > [000436][06:45:02:0397] [14][StandardActions.DisplayRollBackError]Login > failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. > [000437][06:45:02:0398] [13][ExecuteSequence.InstallExecuteSeq] > > Again, the installer runs fine if executed via powershell directly on the > server. It's only failing if executed via ansible. > > Thanks, > > Justin > > On Tuesday, February 28, 2017 at 8:35:10 AM UTC-5, J Hawkesworth wrote: >> >> I would think the authentication delegation may be working - you may be >> able to examine the security event log on the SQLServer and see if there is >> a successful logon from whatever user ansible is connecting as. >> but I think its possible that SQL Server has other requirements but worth >> checking the event log. >> Also, does the installer write a log file or write to the event log. It >> might be possible to determine why is failing from the installer's own >> logging. >> >> Hope this helps, >> >> Jon >> >> >> >> On Monday, February 27, 2017 at 10:15:15 PM UTC, Justin Dugan wrote: >>> >>> The delegation is working (at least for Windows shares). The installer >>> file is copied from a Windows file share before the install occurs and this >>> completes successfully. Is it possible for the delegation to work for a >>> file share and fail for SQL Server? >>> >>> On Saturday, February 25, 2017 at 12:33:01 PM UTC-5, J Hawkesworth wrote: >>>> >>>> Rdp to the server and connecting to sql server is just one hop. >>>> Connecting from ansible to server and from server to sql server is a >>>> second >>>> hop, which is where the delegated credential becomes important. >>>> >>>> If you want to check if delegation is working, you could try writing a >>>> file to a share on a second machine from ansible via your windows server. >>>> >>>> It's been a while since I installed SQL Server, but if I recall there >>>> is/was a Surface Area configuration tool where you can set various options >>>> regarding things like ports and available authentication protocols. If >>>> that is still a thing, that might be worth looking at too. >>>> >>>> Jon >>>> >>>>
-- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/f242c7c1-71cf-4e96-a60d-224580455f6b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
