• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Mailmng.exe SOAP failed

J

JeffT

Guest
I am migrating sites from 8.1.1 Plesk to 9.2 Plesk and last night I had a rash of Smartermail mailboxes which did not move properly. Besides that fact that the mailbox was not created on the destination server, what exactly does this error mean?


Event Type: Error
Event Source: mailmng.exe
Event Category: None
Event ID: 1
Date: 7/16/2009
Time: 9:28:55 PM
User: N/A
Computer: SERVER
Description:
SOAP failed. Failed in sending message
at (SmarterMail::checkResult line 175)
at execute console command --add-mailname(vconsoleapp::start line 129)
at execute "C:\Program Files (x86)\Parallels\Plesk\/admin/bin/mailmng" --add-mailname "--domain-name=domain.com" "--mailname=mailbox"(vconsoleapp::run line 140)
Execute file name: C:\Program Files (x86)\Parallels\Plesk\admin\bin\mailmng.exe
 
Hello,

If any change to mail server configuration using Plesk control panel results in the following error message:

SOAP failed. Failed in sending message at (SmarterMail::checkResult line 175)

It usually means that the SmarterMail Web Server is stopped. Please, make sure that it is started. More information can be found at the following link:

http://kb.odin.com/en/1437

Thank you
 
I checked and the Smartermail Web Server was running. If the Smartermail Web Server was not running, my phone would be ringing off the hook.

What seems to have corrected the issue is from Home/Server Components and selecting Refresh.

I did a test migration of a domain and it did migrate (like it did before this error).
 
Upon further review, this did not correct the issue.

Any help would be appreciated.
 
Back
Top