• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

publishing error

I

iiesolutions

Guest
I have finally figured out why none of my sites were not publishing correctly. In order to correctly verify location, the location for ftp publishing must be within IIS MS FTP root and not a virtual directory elsewhere. ie: if the default or main ftpsite in IIS is configured at c:\inetpub\ftproot\ then a site publish at c:\inetpub\ftproot\site1 will works. Even though you can configure a virtual ftp site anywhere like j:\, sitebuilder will not verify location correctly thus will not publish.

Now I am have another problem in that Module major-upgrade check failed on dynamic published site

Does anyone have any ideas on this


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 failed
SWsoft.SiteBuilder.BO.Facade.PublishException: Module major-upgrade check failed on dynamic published site (id='f0eac522-5ead-465c-89c8-0dcdfba55462') ---> SWsoft.SiteBuilder.Modules.Storage.Common.StorageException: WrongSiteId ---> System.Exception: Exception of type 'System.Exception' was thrown.
--- End of inner exception stack trace ---
at SWsoft.SiteBuilder.Modules.Storage.Proxies.ServiceUtil.InvokeService[T](ObjectMethodInvoker fun)
at SWsoft.SiteBuilder.Modules.Storage.Proxies.DataFacadeProxy.ForceLocalUpgrade()
at SWsoft.SiteBuilder.BO.Facade.PublishTask.<>c__DisplayClass2.b__0()
--- End of inner exception stack trace ---
at SWsoft.SiteBuilder.BO.Facade.PublishTask.<>c__DisplayClass2.b__0()
at SWsoft.SiteBuilder.BO.Facade.PublishHelper.CheckPublishExceptions(CheckPublishExceptionsMethod a_method)
at SWsoft.SiteBuilder.BO.Facade.PublishTask.Run(Object a_data)
 
This string in log:
SWsoft.SiteBuilder.Modules.Storage.Common.StorageException: WrongSiteId
tells that after publication in web.config (appSettings parameter with key 'SiteId') file you have invalid site id value.
Please ensure it has correct value.
 
Back
Top