It's very hard for us to help you in this situation but basically it boils down to you running these checks and finding out what is causing the program to hang;
* Use something like procexp to see if the setup.exe process is spawning any child processes that are running in the background * Ensure your quoting is not screwing up the install process, in your first example you have quoted the responseFile path arg but you don't need this quoted. * Try and replicate this through another WinRM session like PowerShell's Invoke-Command or Enter-PSSession * Use Ansible become on the task to escape the boundary of the WinRM logon and run through a psuedo-interactive process * See if there is any logging you can enable on the Oracle installer, this could tell you the stage it is up to and what it may be waiting on As for why you cannot see it when running through Ansible, Ansible uses a completely separate session to run your processes as any normal interactive logon. This is not unique to Ansible but how Windows treats things like network logons such as WinRM. Thanks Jordan -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/e2e0f876-862d-4b74-a045-93f0f74355fd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
