Search Engine: Elastic

Article ID: 131016, created on Jun 19, 2017, last review on Jun 19, 2017

  • Applies to:
  • Operations Automation 7.0

Symptoms

Plesk Client provisioning fails, the problem report shows the following

[2017/06/16 11:01:54] [INFO] [18604] [HSPC::MT::BM::Subscription::PleskClientSubscription::service_sync] Errors occurred during domain creation: Error occurred while updating client on Plesk node: Cannot add IP address '203.0.113.2' to Plesk server IP pool: ifmng failed: Execute netsh interface ipv4 add address "Ethernet 2" 203.0.113.2 255.255.255.0 failed[1]: Element not found

at (execExtUtilChecked line 137)

at Unable to add IP address(IFmng::IPManager::addIP line 286)

at execute console command --add(vconsoleapp::start line 122)

at execute "C:\Program Files (x86)\Plesk\admin\bin\ifmng" --add "\"Ethernet 2\"" 203.0.113.2 255.255.255.0(vconsoleapp::run line 139)

(Error code 1) 

Cause

Outdated information is returned from Plesk. For instance, "Ethernet 2" has been renamed but Reread IP button was not pressed in Plesk.

Resolution

To actualize IP addresses information log in to the Plesk interface by clicking Log in to Plesk under Top > Service Director > Plesk Manager > Nodes > the Plesk node in question and there go Home > Tools and Settings > IP Addresses and press Reread IP.

See also

Error: Execute netsh interface ipv4 add address "Local Area Connection" 203.0.113.2 255.255.0.0 failed[1]: The object already exists. (Error code 1)

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 0871c0b47b3b86ae3b1af4c2942cd0ce 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF