在 SharePoint Server 2016 中疑難排解網站集合的升級問題Troubleshoot site collection upgrade issues in SharePoint Server 2016

摘要: 了解如何解決將網站升級至 SharePoint Server 2016 之後可能發生的問題。Summary: Learn how to address problems that may occur after you upgrade a site to SharePoint Server 2016.

將網站集合升級至 SharePoint Server 2016 時,偶爾會發生錯誤。本文有助您了解這些錯誤並予以解決。When you upgrade a site collection to SharePoint Server 2016, errors can occasionally occur. This article helps you understand those errors and address them.

查看升級狀態及記錄檔Check upgrade status and log files

升級狀態指示及記錄檔可告知您升級程序期間發生錯誤的地方。建議您謹慎檢閱升級記錄檔中的所有錯誤。警告不一定表示問題,但您應全部加以檢閱,以判斷是否有任何警告可能導致更多問題。Upgrade status indicators and log files should give you an indication of what went wrong during the upgrade process. We recommend that you carefully review all the errors in the upgrade log files. Warnings might not always indicate an issue, but you should review them all to determine whether any of them are likely to cause even more issues.

  1. 檢閱網站集合的升級狀態頁面。Review the upgrade status page for your site collection.

    在網站集合的 [網站設定]**** 頁面上,按一下 [網站集合管理]**** 區段中的 [網站集合升級]*。在 [網站集合升級]* 頁面上,按一下 [檢閱網站集合升級狀態]*On the *Site Settings page for the site collection, in the Site Collection Administration section, click Site collection upgrade. On the Site Collection Upgrade page, click Review Site Collection Upgrade Status.

  2. 如果頁面未呈現,請檢查 [網站設定]**** 頁面。如果 [網站設定]**** 頁面的運作正常,且升級已然成功,可能是主版頁面或首頁發生問題。如果 [網站設定]**** 頁面無法正常運作,請檢查網站集合升級記錄檔,以了解問題的相關資訊。If pages don’t render, check the Site Settings page. If the Site Settings page works and the upgrade has succeeded, there might be issues with the master page or home page. If the Site Settings page doesn’t work, check the site collection upgrade log file for information about the problem.

  3. 檢閱網站集合升級記錄檔。您可以從下列位置檢閱網站集合升級記錄檔:Review the site collection upgrade log files. You can review the site collection upgrade logs from the following locations:

    • 若為網站集合管理員: 網站集合升級的記錄檔也儲存在網站集合本身內部的 [維護記錄] 目錄中,位置是 http:///catalogs/MaintenanceLogs/YYYYMMDD-HHMMSS-SSS.txt,其中 _YYYYMMDD 是日期,而 HHMMSS-SSS 是時間 (24 小時制的時、分、秒及毫秒)。For site collection administrators: There are also log files for site collection upgrade stored inside the site collection itself, in the Maintenance Logs catalog at (http:///catalogs/MaintenanceLogs/YYYYMMDD-HHMMSS-SSS.txt , where _YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds).

    • 若為伺服器陣列管理員: 網站集合升級記錄檔與升級錯誤記錄檔位於 %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\16\LOGS。記錄檔的命名格式如下:SiteUpgrade- YYYYMMDD-HHMMSS-SSS.log,其中 YYYYMMDD 是日期,而 HHMMSS-SSS 是時間 (24 小時制的時、分、秒及毫秒)。如果您需要關於問題的詳細資訊,這些檔案系統記錄檔也可提供更多資訊。For farm administrators: The site collection upgrade log file and the upgrade error log file are located at %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\16\LOGS. The logs are named in the following format: SiteUpgrade- YYYYMMDD-HHMMSS-SSS.log, where YYYYMMDD is the date and HHMMSS-SSS is the time (hours in 24-hour clock format, minutes, seconds, and milliseconds). These file system logs have more information if you want details about issues.

常見問題Common issues

查看是否有下列任一問題導致升級錯誤、警告,或網站發生問題。Check to see whether any of the following issues are causing an upgrade error, a warning, or a problem in your site.

問:以前在頁面上看得到的 UI 控制項不見了Q: I don't see a UI control on the page that used to be there

  • 答: 將頁面重設為預設版本 (也就是重新建立映像)。A: Reset the page to the default version (that is, reghost it).

變更網站 UI 可能會在網站升級時產生問題。如果您自訂網頁,將 UI 控制項放置在非標準位置,則可將頁面重設為預設版本以復原控制項。Making changes to the site UI can cause problems in site upgrades. If a page was customized to place a UI control in a non-standard location, you can reset the page to the default version to recover the control.

若要重設頁面,您可以在 [網站設定] 頁面使用 [網站動作]**** 下的 [重設為網站定義]**** 連結,或是在 SharePoint Designer 中使用 [重設為範本]**** 命令。To reset the page, you can use the Reset to site definition link under Site Actions on the Site Settings page or use the Reset to Template command in SPDesigner_1st_NoVer.

問:大型清單上的檢視再也無法使用Q: The view on a large list is not working any longer

  • 答: 針對大型清單建立編製索引的欄、資料夾或新檢視。您可能需要將編製索引的欄新增到現有檢視。A: Create indexed columns, folders, or new views for large lists. You might have to add the indexed column to your existing views.

若清單很大,且使用者使用的檢視或執行的查詢超出限制或節流閾值,則不會允許檢視或查詢。您可以建立具有篩選檢視的索引欄、將項目分類到各資料夾、設定大型檢視之頁面上的項目限制,或使用外部清單。如需大型清單節流以及如何解決大型清單之問題的詳細資訊,請參閱 Office Online 上的管理含有許多項目的清單及文件庫If a list is very large, and users use a view or perform a query that exceeds the limit or throttling threshold, the view or query will not be permitted. You can create indexed columns with filtered views, organize items into folders, set an item limit on the page for a large view, or use an external list. For more information about large list throttling and how to address issues with large lists, see Manage lists and libraries with many items on Office Online.

問:我發現有關重複內容類型名稱的錯誤Q: I see an error about a duplicate content type name

  • 答: 將與預設名稱衝突的的內容類型或欄位重新命名。A: Rename content types or fields that conflict with default names.

自訂元素 (例如內容類型) 的名稱有時會與新版的名稱相衝突。Occasionally, custom elements (such as a content type) may have a name that conflicts with a name in the new version.

在升級記錄檔中,可能會看到如下錯誤:In the upgrade log files, you may see an error such as the following:

  • 無法啟動網站 (網站 URL) 上的網站集合功能。例外狀況:找到重複的內容類型名稱 「名稱」Failed to activate site collection features on site Site Url. Exception: A duplicate content type name "name" was found.

此錯誤表示已在 SharePoint Server 2013 Service Pack 1 (SP1) 將協力廠商內容類型新增到指定網站。升級至 SharePoint Server 2016 期間,其名稱與預設內容類型的名稱相同,因而產生衝突。將指定網站中的協力廠商內容類型重新命名為不同名稱,然後再執行升級。如需詳細資訊,請參閱 Office Online 上的建立或自訂內容類型This error indicates that a third-party content type was added to the specified site in SharePoint Server 2013 with Service Pack 1 (SP1). During upgrade to SharePoint Server 2016 its name conflicted with the default content type by the same name. Rename the third-party content type in the specified site to a different name and run upgrade again. For more information, see Create or customize a content type on Office Online.

注意

重新命名或移除內容類型,都可能造成與該內容類型相依的任一自訂停止運作。Either renaming or removing a content type can cause any customizations dependent on that content type to stop working.

問:「我的網站」看起來不美觀、行為不如預期,或是出現指令檔錯誤Q: My site looks ugly, doesn't behave as expected, or I see script errors

  • 答: 編輯頁面或將頁面重設為預設版本,或是移除或取代自訂檔案。A: Either edit the page or reset the page to the default version, or remove or replace the custom files.

    這些問題可能是自訂或內嵌 JavaScript 或 CSS 檔案的問題所造成。A problem with custom or inline JavaScript or CSS files can cause these issues.

問:我的網站中的自訂內容不見了或無法運作Q: Custom content in my site disappeared or doesn't work

  • 答: 變更主版頁面,或是變更內容使其不需要特殊區域。A: Change the master page, or change the content so that it doesn't require specific zones.

    主版頁面可能有不同的區域版面配置,而內容可能再也無法正確參照主版頁面。最後的解決手段就是將頁面重設為預設版本。不過,如果您重設頁面,可能會遺失區域特定內容。The master page might have different zone layouts and the content might no longer reference it correctly. As a last resort, you can also reset the page to the default version. However, if you reset the page, you might lose zone specific content.

問:我收到錯誤,指出無法轉譯控制項或頁面Q: I receive an error that says a control or page cannot render

  • 答: 執行下列操作之一:A: Do one of the following:

    • 如果新增了尚未安裝的網頁組件,請連絡伺服器陣列管理員予以安裝。如果新增了無法使用或不支援的網頁組件,請使用網頁組件維護檢視從頁面中移除網頁組件 (請移除而不是只關閉網頁組件)。If a Web Part was added that is not installed, contact the farm administrator to have it installed. If is a Web Part that is no longer available or not supported, then use the Web Part maintenance view to remove the Web Part from the page (remove, do not just close the Web Part).

    • 如果是直接編輯頁面,請再次編輯以移除控制項或網頁組件,或是將頁面重設為預設版本。If a page was directly edited, either edit it again to remove the control or Web Part or reset the page to the default version.

      頁面可能新增了尚未安裝或不再支援的網頁組件或其他控制項。可能是將網頁組件新增到區域,或是直接編輯頁面以新增控制項或直接內嵌網頁組件參照 (可能在主版頁面上)。A Web Part or other control might have been added to the page that is not installed or is no longer supported. Either a Web Part was added to a zone or the page was directly edited to add a control or Web Part reference directly inline (possibly on a master page).

      SharePoint 功能可能需要啟動。如需詳細資訊,請參閱 Office Online 上的啟用或停用網站集合功能以及開啟並使用網頁組件維護頁面A SharePoint feature may need to be activated. For more information, see Enable or disable site collection features and Open and use the Web Part Maintenance Page on Office Online.

問:我的升級網站完全沒有任何顯示;相反地,我透過相互關聯識別碼看見「未預期的錯誤」Q: My upgraded site does not render at all; instead, I see an "unexpected error" with a correlation ID

答: 您的自訂品牌可能使用包含自訂內容預留位置的自訂主版頁面。A: Your custom branding may use a custom master page that contains a custom content placeholder.

如果您的自訂主版頁面包含自訂內容預留位置,而且如果自訂頁面版面配置也包含此自訂內容預留位置,則錯誤可能會阻止您的網站在升級之後有任何呈現。相反地,升級之後,您可能會看見錯誤訊息「發生未預期的錯誤」。If your custom master page contains a custom content placeholder, and if custom page layouts also contain this custom content placeholder, then an error may prevent the home page of your site from rendering at all after upgrade. Instead, after upgrade, you may see the error message "An unexpected error has occurred."

另請參閱See also

概念Concepts

將網站集合升級至 SharePoint Server 2016Upgrade a site collection to SharePoint Server 2016