Systems Affected

This hotfix should be applied to any installation of the TMCore SharePoint Module 3.1 downloaded before 15th March 2010. If you downloaded your copy of the software from our site on or after this date, the hotfix is included in the package and you do not need to apply it again.
To determine if your system is affected, check the File Version property of the assembly NetworkedPlanet.SharePoint in the GAC (browse to C:\Windows\ASSEMBLY, locate the NetworkedPlanet.SharePoint assembly, right-click and choose Properties. The File Version can be found on the Version tab above Description and Copyright). This hotfix updates the File Version of the NetworkedPlanet.SharePoint assembly to 2.1.6.0 - if the file version shown is greater than or equal to 2.1.6.0, then you do not need to apply this hotfix.

Pre-Requisites

Upgrade to TMCore SP5 (if running an earlier version) to avoid issues with faceted search components in the SharePoint Module.

Upgrade Instructions

1. Download the Hotfix 6 package.
2. The package is provided in a compressed ZIP file. Unzip the package on a machine in the server farm.
3. Upgrade the NPSharePoint.wsp solution. The exact command-line you use will depend on how you want to schedule the upgrade, but will be similar to:

stsadm -o upgradesolution -name NPSharePoint.wsp -filename NPSharePoint.wsp -allowgacdeployment -allowcaspolicies -local

4. Restart IIS and Windows SharePoint Services Timer

Change Log

• ENHANCEMENT: Optimized update of associated topic fields to reduce the number of database writes required when saving a SharePoint list item.

  Added more logging of SharePoint object close and disposal.

• ENHANCEMENT: Added check to ItemUpdated event receiver to check whether a double event was caused by a check-in. If so, do not do processing for check-in events.
• BUGFIX: Amended the site deletion code so that topics for sub sites are correctly marked as superceded if the site is the root site of a site collection. This allows the WebCleanUp timer task to successfully remove any topics of the superceded sites on its next run.
• BUGFIX: Site deletion - if a site deletion fails in SharePoint for any reason, the WebCleanUp timer task that runs 2 minutes after the delete event will now also check whether the site still exists and if so set the psi back to PUBLISHED.

Systems Affected

This hotfix should be applied to any installation of the TMCore SharePoint Module 3.1 downloaded before 10th December 2009. If you downloaded your copy of the software from our site on or after this date, the hotfix is included in the package and you do not need to apply it again.
To determine if your system is affected, check the File Version property of the assembly NetworkedPlanet.SharePoint in the GAC (browse to C:\Windows\ASSEMBLY, locate the NetworkedPlanet.SharePoint assembly, right-click and choose Properties. The File Version can be found on the Version tab above Description and Copyright). This hotfix updates the File Version of the NetworkedPlanet.SharePoint assembly to 2.1.4.0 - if the file version shown is greater than or equal to 2.1.4.0, then you do not need to apply this hotfix.

Upgrade Instructions

1. Download the Hotfix 4 package.
2. The package is provided in a compressed ZIP file. Unzip the package on a machine in the server farm.
3. Upgrade the NPSharePoint.wsp solution. The exact command-line you use will depend on how you want to schedule the upgrade, but will be similar to:

stsadm -o upgradesolution -name NPSharePoint.wsp -filename NPSharePoint.wsp -allowgacdeployment -allowcaspolicies -local

4. Upgrade the NPOfficeServer.wsp solution. Use the following STSADM command:

stsadm -o upgradesolution -name NPOfficeServer.wsp -filename NPOfficeServer.wsp -allowgacdeployment -allowcaspolicies -local

5. Run the following stsadm command:

stsadm -o copyappbincontent

6. Restart IIS and Windows SharePoint Services Timer
7. Reactivate the NPDiagnostics feature by running the stsadm command:

stsadm -o activatefeature -name NPDiagnostics -force

8. Upgrade Enterprise Services to the version included with the hotfix, the new version of Enterprise Services is 1.1.2.0

9. Restart the Topic Map Index Service

Change Log

• BUGFIX: One hop and two hop web parts were intermittently returning Deadlock errors. These have
  now been changed to sleep and retry up to a maximum of three times when encountering
  deadlock issues with the database.
• ENHANCEMENT: Url Mappings can now feature more than one publish URL for a web application by using
  the zones set up when extending the SharePoint web application.
• ENHANCEMENT: Additional diagnostic logging has been added to Url Mapping. The NPDiagnostics
  feature must be reactivated on the farm for this to take affect.
• FEATURE: The stsadm remapurls command now has an optional parameter which when used skips the url
  remapping on content type to topic type mappings.
• NOTE: The new hotfix of Enterprise Services has been included with this hotfix. This fixes issues with
  results display and ordering when using advanced faceted search restriction sets.

• FEATURE: Changed NPItemBase feature so that TopicId field can be indexed by SharePoint search
• FEATURE: New stsadm command 'upgradeitembase' which can be used after activating/reactivating
  NPItemBase to update any TopicId fields created before activation
  so that they can be indexed by SharePoint Search.
  An optional parameter can be specified (-updatelistitems) which will iterate through all
  list items and set the value of the topic id field.
• BUGFIX: Fixed bug that prevented the AdvancedFacetedSearchResultsWebPart from rendering correctly
  when adding SharePoint field information and the number of results exceeded the
  configured maximum.
• BUGFIX: Fixed bug caused by exceptions being thrown when deactivating NPItemBase encountered
  sealed or readonly content types.
• BUGFIX: ExtendedXsltWebPart now logs to the correct category - NP - WebParts
• BUGFIX: Fixed a bug with the AdvancedFacetedSearchResultsWebPart that prevented the web part
  from displaying additional SharePoint field content if security filtering was disabled.