In order to update your current Extradium for SharePoint 2013/2016 installation to a more recent Extradium release, please sign in here on the RioLinx web site and download the Extradium_Standard_2013.zip file.
The detailed update instructions are available below:
- If you made any modification to the default Extradium resource files, please back up any Extradium resource file (exs.[LCID].resx files in any Extradium-enabled web application’s App_GlobalResources folder) you may have modified.
- If you made any style sheet modification, please back up the ExtradiumCustom.css file in the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\[LCID]\STYLES folder(s)
- Stop or at least pause any search crawl that might run or start running during the update. Search crawls can severely impact the performance of your farm during an upgrade (because of its dependency on IIS properly running) so it is important to disable any search crawl that might run during an Extradium update.
- Stop the World Wide Web Publishing Service (for instance with “net stop w3svc”) on all web front-end servers in your SharePoint farm in order to avoid any lock error on Extradium files that are upgraded.
- Restart the SharePoint Timer Service on all web front-ends (including those that are not load-balanced, if any).
- Extract the Extradium_Standard_2013.zip file on a SharePoint server running the Central Administration site and run Extradium2013Setup.exe or UpgradeExtradium.bat.
Note: you should run the upgrade file once and only on a SharePoint server running the Central Administration site since SharePoint takes care of automatically updating all of the other servers.
- (Optional) Compare the Extradium resource files you have backed up in step #1 with the new resource files. If no key has been added, you can safely overwrite the resource files. Otherwise, you must incorporate all your customizations into the new resource files.
- Restart the World Wide Web Publishing Service (for instance with “net start w3svc”)
- Restart your search crawls
- Connect to the Database Configuration page in the Extradium Administration Site, check the Upgrade database schema checkbox and press the OK button.
- Verify the License Information page to make sure you have updated your installation to the expected Extradium version number.
Important Note: in some instances, SharePoint might not be refreshed with the latest Extradium assemblies and might continue to use the (cached) previous ones. In order to fix this issue, you can try the following fixes:
- Recycle the SecurityTokenServiceApplicationPool on each Web Front End server
- If that does not work, stop IIS on each Web Front End server, delete the content of the C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files folder and restart IIS