Thanks Jon! Hopefully this proves that delegation is properly set up.
SWServer = The server where the application installer is executed
DBServer = The SQL Sever
[jdugan@centos7 ansible]$ ansible -m raw -a 'New-Item -path
"\\DBServer\test\test" -type file -force' CDG --limit=SWServer
SWServer | SUCCESS | rc=0 >>
Directory: \\DBServer\test
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 03/20/2017 10:47 0 test
On Tuesday, March 14, 2017 at 1:36:35 PM UTC-4, J Hawkesworth wrote:
>
> 1603 is unfortunately a generic 'something went wrong' message and so is
> of little value when working out what is failing.
>
> The anonymous user login failure is the issue. Presumably when you run
> install interactively your current logged on user is used and your
> installer continues.
>
> So it sounds like your ansible session credentials aren't available when
> installer runs via ansible.
>
> I suggest you attempt to write to a temporary share on the sql server via
> ansible to prove or disprove that delegation is working for you. I think
> just reading from a share might not prove whether the delegation is working
> - writing a file using a UNC style path (i.e. \\someswrver\share\ ) would
> be a better test.
>
> From the information available it seems the user credentials aren't
> available so I think first step is proving delegation is correctly set up.
>
> Hope the helps,
>
> 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/47ff9831-81a9-4e9b-a449-3e5e65c13619%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
