November Happy Hour will be moved to Thursday December 5th.
AI OnAI Off
November Happy Hour will be moved to Thursday December 5th.
Sounds likely, your database is already updated to the new version when you run the update on your second instance. I don't think you can prevent EPi from trying to update the database without editing the scripts, but a silly way to do it would be to point the 2nd and 3rd instances to temporary copies of the old db.
Hi,
We are having a application installed in Development environment which is having 3 instances.
All the instances are using same EPiServer database.
We decided to upgrade our website.
So, when upgraded one development instance, the process completed smoothly without any problem.
When tried to upgrade the second instance, the operation ended with the following error message:
At C:\Program Files\EPiServer\Framework\6.0.318.113\Install\System Scripts\Install Site (SqlServer).ps1:82 char:25
+ Execute-EPiSqlSvrScript <<<< `
System.ApplicationException: Invalid database version detected
at EPiServer.Install.SqlServer.Installers.EPiServerSqlScriptInstaller.ExecuteQuery(String nodeName, String query)
at EPiServer.Install.SqlServer.Installers.EPiServerSqlScriptInstaller.ExecuteQueryFromNode(String nodeName)
at EPiServer.Install.SqlServer.Installers.EPiServerSqlScriptInstaller.CheckConditions()
at EPiServer.Install.SqlServer.Installers.EPiServerSqlScriptInstaller.InstallInternal(IDictionary stateSaver)
at EPiServer.Install.SqlServer.Installers.EPiServerSqlScriptInstaller.Install(IDictionary stateSaver)
at EPiServer.Install.InstallationManager.Install(Installer installer)
at EPiServer.Install.SqlServer.SqlServerInstallationManager.ExecuteDatabaseScript(String sqlServerName, Nullable`1 sqlServerPort, String databaseName, String loginName, String loginPassword, String scriptFilePath, Boolean avoidDbTransaction, Boolean isEPiServerScript, IDictionary parameters)
at EPiServer.Install.SqlServer.Cmdlets.ExecuteSqlScriptCmdlet.ProcessRecord()
at System.Management.Automation.Cmdlet.DoProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
So, we are thinking that this problem raised because of the database sharing among the various instances.
Can you please check suggest some ideas to upgrade all the instances to same(from 5 to 6) version.
Thanks.
Best Regards,
Kishore T