-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
issue with win_msg module #533
Comments
It seems that error is coming from Windows Server itself. Are you facing this issue intermittently or everytime you run the task? |
Hello, I am facing the same error too.
Winver gives OS Build : Version 1607 (OS Build 14393.6897). The playbook looks like that :
My real message contains less than 120 characters (far from the 256 char limit) and the following behavior happens :
The message is sent to both servers and I am able to see it on both servers, but one task fails.
Do you have any idea on how to fix this problem ? |
I am getting this error after running the code on windows servers
error
{
"exception": "Error sending message to session Console : Error 2147500058 \nAt line:37 char:15\r\n+ $output = & msg.exe $msg_args 2>&1\r\n+ ~~~~~~~~~~~~~~~~~~~~~~~~\n + CategoryInfo : NotSpecified: (Error sending m...ror 2147500058 :String) [], RemoteException\n + FullyQualifiedErrorId : NativeCommandError\r\n\r\nScriptStackTrace:\r\nat , : line 37\r\n",
"msg": "Unhandled exception while executing module: Error sending message to session Console : Error 2147500058 ",
"_ansible_no_log": false,
"changed": false
}
The text was updated successfully, but these errors were encountered: