Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Error upgrading CMS6 R2 to CMS7
In case anyone else encountered this, turns out it's a bug with Deployment Center. If your site uses VPPs on a shared drive this error is generated, moving the VPPs to a local drive prevents the error. Apparentley this has been fixed and will be included in a future patch.
Mar 25, 2013 11:00
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
Hello,
I'm trying to upgrade a site from CMS6 R2 to CMS7 using deployment centre and get an error as follows:
At C:\Program Files (x86)\EPiServer\Framework\7.0.859.1\Install\System Scripts\Install Module Package.ps1:157 char:16
+ Add-EPiXmlBlock <<<< -TargetFilePath $packagesConfigPath -ElementXPath "/packages" -XmlBlock $packageRegistrationXml
System.ArgumentException: The path is not of a legal form.
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
at System.IO.Path.GetFullPathInternal(String path)
at System.IO.DirectoryInfo..ctor(String path)
at EPiServer.Install.Common.TempPath..ctor(Char hostDrive)
at EPiServer.Install.Common.FileBackup..ctor(FileInfo file)
at EPiServer.Install.Xml.Installers.XmlInstallerBase..ctor(InstallationManager installationManager, String targetFilePath, Dictionary`2 namespaces)
at EPiServer.Install.Xml.Installers.AddXmlBlockInstaller..ctor(InstallationManager installationManager, String targetFilePath, String elementXPath, XmlNodeList xmlNodes, Dictionary`2 namespaces)
at EPiServer.Install.Xml.XmlInstallationManager.AddXmlBlock(String targetFilePath, String elementXPath, String xmlBlock, Dictionary`2 namespaces)
at EPiServer.Install.Xml.Cmdlets.AddXmlBlockCmdlet.ProcessRecord(XmlInstallationManager xmlInstallationManager)
at EPiServer.Install.Xml.Cmdlets.XmlInstallationCmdlet.ProcessRecord()
at System.Management.Automation.Cmdlet.DoProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
The packages.config file exists but only contains an empty <packages> node. Anyone encountered this and/or know how to fix?
Thanks,
Mark