顯示具有 SQL 標籤的文章。 顯示所有文章
顯示具有 SQL 標籤的文章。 顯示所有文章

2017年2月15日 星期三

Upgrading to SQL 2014: Report Server version mismatch

Symptom
=============
If you have recently upgraded your SQL Server Reporting Services instance from SQL 2012 SP2 to SQL 2014, you may hit the following error message when trying to access your report server:
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is ‘163’. The expected version is ‘162’. (rsInvalidReportServerDatabase).

Cause
========
As part of a hotfix for SQL 2012 SP2 CU5, a change was made which resulted in a new ReportServer database version. Since this fix was made after the SQL2014 release, if your SQL2012 SP2 server is on CU5 or later, then it will have a higher database version than what SQL2014 RTM expects.

Solution
=========
We are porting the fix in the next cumulative update for SQL 2014, CU7. In order to fix the version mismatch, you should install CU7 or later onto your SQL2014 instance, which will allow the Reporting Services instance to correctly recognize the new database version.

Notes
======
If you have not yet upgraded, you can determine whether you will run into this issue by executing the following query against your ReportServer database:
SELECT MAX([DbVersion]) FROM [dbo].[DBUpgradeHistory] 

2015年9月6日 星期日

SQL Server 2008 R2 SP2升級到SP3 失敗

[請您參考以下的說明]   
1.       現階段暫時使用其他具有管理員權限的帳號登入後,已經可以正常安裝相關更新。
2.       針對Kerberos Token大小的問題建議可以透過底下方式將大小調整成48000以減少此類問題發生。
步驟:
1)      打開regedit.exe
2)      找到HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters , 並在右邊新增一個DWORD , 命名為 MaxTokenSize , 並設定其值為48000 (十進位)

3)      設定完成後重新開機讓該值生效即可