• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

error on location verify

I

iiesolutions

Guest
Creation date Wednesday, September 12, 2007 12:48:09 PM
Level Warning
Source System
Class name SWsoft.SiteBuilder.BO.Facade.Publish.LocationChecker
User name iiesolutions
Representative
IP address 24.64.223.204
Requested URL /Admin/SiteMgmt/SiteList.aspx?SiteID=553b6332-1514-4cad-b372-21617ec7f2fd
Referrer URL
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; InfoPath.1; .NET CLR 3.0.04506.30)
Message Publish Location checker, DeleteProbeFiles step error
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at SWsoft.SiteBuilder.Repository.Resources.ResourceItemsCollection`2.GetItemRecursively(PathEx path)
at SWsoft.SiteBuilder.Repository.Resources.ResourceItemsCollection`2.get_Item(String name)
at SWsoft.SiteBuilder.BO.Facade.Publish.LocationChecker.DeleteProbeFiles()
 
If you still have this issues with publishing could you check and post the exception which is displayed before this one? As I figured out from developers exception(DeleteProbeFiles) is not the real one and in next 4.1 there will not be such exception any more.
Let me know more details here.
 
Back
Top