# ANSIBALLZ\_WRAPPER is not recognized as the name \\r\\nof a cmdlet **URL:** \ **Category:** Ansible Developer\ **Tags:** windows, ubuntu\ **Created:** [February 28, 2018, 7:16am UTC](https://forum.ansible.com/t/ansiballz-wrapper-is-not-recognized-as-the-name-r-nof-a-cmdlet/26865 "2018-02-28T07:16:28Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Guillem\_Sola](https://avatars.discourse-cdn.com/v4/letter/g/e5b9ba/32.png) [@Guillem\_Sola](https://forum.ansible.com/u/Guillem_Sola)\ **Post date:** [February 28, 2018, 7:16am UTC](https://forum.ansible.com/t/ansiballz-wrapper-is-not-recognized-as-the-name-r-nof-a-cmdlet/26865/1 "2018-02-28T07:16:28Z")
Hi, I’m trying to run some integration tests from ubuntu against a windows10 host with ./ansible-test windows-integration -v win\_xml --allow-destructive Test tasks starts but it complains fatal: [windows10]: FAILED! =\> {“msg”: "winrm send\_input failed; \nstdout: Unable to initialize device PRN\r\nUnable to initialize device PRN\r\nUnable to initialize device PRN\r\n\nstderr ANSIBALLZ\_WRAPPER : The term ‘ANSIBALLZ\_WRAPPER’ is not recognized as the name \r\nof a cmdlet, function, script file, or operable program. I haven’t been able to find what this wrapper is about Any clue? ---
**Author:** ![tkuratom](https://avatars.discourse-cdn.com/v4/letter/t/b19c9b/32.png) [@tkuratom](https://forum.ansible.com/u/tkuratom)\ **Post date:** [February 28, 2018, 5:49pm UTC](https://forum.ansible.com/t/ansiballz-wrapper-is-not-recognized-as-the-name-r-nof-a-cmdlet/26865/2 "2018-02-28T17:49:49Z")
This looks like the module is being run via powershell but it’s being treated as a new-style python module (which is wrapped in a python wrapper script before being executed on the remote machine). What is this win\_xml module you’re trying to test? Maybe it’s not being recognized as a powershell script? -Toshio ---
**Author:** ![Guillem\_Sola](https://avatars.discourse-cdn.com/v4/letter/g/e5b9ba/32.png) [@Guillem\_Sola](https://forum.ansible.com/u/Guillem_Sola)\ **Post date:** [February 28, 2018, 6:32pm UTC](https://forum.ansible.com/t/ansiballz-wrapper-is-not-recognized-as-the-name-r-nof-a-cmdlet/26865/3 "2018-02-28T18:32:16Z")
The win\_xml module lives in a forked repo and has been pending to be merged for some months [https://github.com/ansible/ansible/pull/26404](https://github.com/ansible/ansible/pull/26404). I'm using it in my deployments and I was considering continuing the original work to see if it can be merged. It is a PS module but with what you have said I will check if it something is not correctly defined. Maybe I haven't initialized the test appropriately as I was trying to use the xml modules test to unify test criteria. ---
**Author:** ![jborean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jborean/32/1525_2.png) [@jborean](https://forum.ansible.com/u/jborean)\ **Post date:** [February 28, 2018, 9:00pm UTC](https://forum.ansible.com/t/ansiballz-wrapper-is-not-recognized-as-the-name-r-nof-a-cmdlet/26865/4 "2018-02-28T21:00:39Z")
Are you able to share your test/integration/inventory.winrm file as it seems like some of the config is breaking the winrm/powershell plugins. Here is an example one that I use ` [2016] SERVER2016.domain.local [windows:children] 2016 [windows:vars] ansible\_user=vagrant-domain@DOMAIN.LOCAL ansible\_password=password ansible\_connection=winrm ansible\_port=5986 ansible\_winrm\_transport=kerberos ansible\_winrm\_server\_cert\_validation=ignore [localhost] 127.0.0.1 ansible\_connection=local [winrm:children] windows [testhost\_binary\_modules:children] windows ` I’m no expert on XML but I believe the API that was being used in the module wasn’t as fully featured as the XPath option in PowerShell and it’s little support for namespaces may cause issues down the line. Thanks Jordan ---
**Author:** ![Guillem\_Sola](https://avatars.discourse-cdn.com/v4/letter/g/e5b9ba/32.png) [@Guillem\_Sola](https://forum.ansible.com/u/Guillem_Sola)\ **Post date:** [February 28, 2018, 9:12pm UTC](https://forum.ansible.com/t/ansiballz-wrapper-is-not-recognized-as-the-name-r-nof-a-cmdlet/26865/5 "2018-02-28T21:12:02Z")
Your help is really appreciated and it’s helping me understand better how the testing framework works. It ended up being my fault (what else) I confused the include tests tasks and it was doing the setup with the copy instead of win\_copy command. Maybe the test runner is forcing everything to go through PS as I was not able to see at first sight that I was trying to execute a python command. Thanks ---
**Author:** ![jborean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jborean/32/1525_2.png) [@jborean](https://forum.ansible.com/u/jborean)\ **Post date:** [February 28, 2018, 11:35pm UTC](https://forum.ansible.com/t/ansiballz-wrapper-is-not-recognized-as-the-name-r-nof-a-cmdlet/26865/6 "2018-02-28T23:35:05Z")
No worries, when you run the windows-integration tests it will load the inventory file I mentioned. You can’t use Python modules on Windows hosts as it will either fail with a send input error or the one you see with ANSIBALLZ. Glad you got it working though, good luck with the testing. Thanks Jordan