Help shape the future of CMS PaaS release notes! Take this quick survey and share your feedback.
Help shape the future of CMS PaaS release notes! Take this quick survey and share your feedback.
I've started getting the same error. Windows Server 2008 R2 + SQL Server Enterprise 2008.
I raised a case with technical support and the official response I received was that the EPiServer Deployment Center has a minor bug in it that causes installation of the database to fail if you have already pre-created the database on your database server.
My quick solution was to remove the database I'd created but left the user and security I'd created in place, and then let the EPiServer Deployment Center recreate the database for me as part of the installation.
Hey presto, solved. Hopefully EPiServer will fix this bug soon.
Hi Rob, did you get a bug number from support? I am trying to look up the status of this bug..
Hi Per, I wasn't given one no, however you're welcome to the case number (192691) if that'll help you track down the right people to talk to internally.
Found it (22282), the behaviour was determined as "by design" and hence split into a fix and an feature request. The fix is already done and warns you when trying to install into an existing empty database and a feature request to support this scenario.
I'm trying to install Episerver R2 on my workstation, but I get the following errormessage during the installation process :
Error - Invalid object name 'tblPageType'.
--
At C:\Program Files\EPiServer\CMS\5.2.375.236\Install\System Scripts\Install Database (SqlServer).ps1:149 char:30+ Set-EPiBuiltInPageTypePaths <<<< -SqlServerName $wizard.Database.DatabaseServerName -SqlServerPort $wizard.Database.DatabaseServerPort -DatabaseName $wizard.Database.DatabaseName -LoginName $wizard.Database.InstallerDatabaseLoginName -LoginPassword $wizard.Database.InstallerDatabaseLoginPassword -UiPath "~$uiPath" -AvoidDbTransaction
--
I have an existing empty database that I'm trying to use.
Thanks for any tips on how to solve this.