我在使用部署中心升级时,我在升级时会升级一个等待超时错误。
我已经尝试在C: Program Files(X86) Episerver shared install install extint extinal einterverinstall.exe.config中添加以下配置:
<appSettings>
<add key="commandTimeout" value="600"/>
</appSettings>
但无济于事。
我不想求助于手动升级,还有一种方法可以覆盖连接超时吗?
事先感谢您的任何帮助。
编辑:
升级日志(太长了,所以我将其剪切只是以显示错误消息):
....
Executing database script "C:Program Files (x86)EPiServerCMS7.0.586.1UpgradeDatabasesql 007_0000_0041_0000to0007_0000_0147_0000.sql"
An error has occured and the transaction will be rolled back
Rolledback
The wait operation timed out
The wait operation timed out
An unhandled error has occured:
The wait operation timed out
When executing
At C:Program Files (x86)EPiServerCMS7.0.586.1UpgradeSystem ScriptsUpgrad
e Site Database (SqlServer).ps1:9 char:2
+ Execute-EPiSqlSvrScript -EPiServerScript -ScriptPath $file -SqlServerName
$dbCo ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~
=
Get-EPiIsBulkInstalling
At C:Program Files (x86)EPiServerCMS7.0.586.1UpgradeSystem ScriptsUpgrade Site Database (SqlServer).ps1:9 char:2
+ Execute-EPiSqlSvrScript -EPiServerScript -ScriptPath $file -SqlServerName $dbCo ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out
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()
如果我没记错的话(自从我使用部署中心以来已经有一段时间),它使用web.config的ConnectionsTring来定义超时。
。请参见示例此处:https://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connection time time out(v=vs.110)9.aspx
我重新启动了网站,然后在DC中刷新了该站点,现在起作用。看起来这些设置在DC中被缓存。