Neverfail for SharePoint Plug-in v201.5.4 - Release Notes

Follow

Summary

This Knowledgebase article provides information about this specific release of Neverfail for SharePoint Plug-in.


More Information

The Neverfail for SharePoint Plug-in provides file and registry filters that replicate critical data and monitor the performance of critical components of the SharePoint server.

Supported Versions and Platforms

  • Microsoft SharePoint 2010 Enterprise, Standard and Foundation Edition on
    • Windows Server 2012 R2 x64 (Standard and Datacenter)
    • Windows Server 2012 x64 (Standard and DataCenter)
    • Windows Server 2008 x64 SP2 (Standard and Enterprise)
    • Windows Server 2008 R2 (Standard and Enterprise)
  • Microsoft SharePoint 2007 Sp1, Sp2 Enterprise and Standard, and
  • Microsoft SharePoint Services 3.0 SP1, SP2
    • Windows Server 2008 x64 SP1, SP2 (Standard and Enterprise)
    • Windows Server 2003 x86 and x64 SP1, SP2 (Standard and Enterprise)
  • Microsoft FASTSearch for SharePoint 2010 Enterprise Edition
    • Windows Server 2008 x64 SP2 (Standard and Enterprise)
    • Windows Server 2008 R2 (Standard and Enterprise)

New Features

  • Neverfail for FASTSearch Server Plug-in v201.5.1 is bundled and licensed with the Neverfail for SharePoint Plug-in v201.5.4 for full support of SharePoint
  • Auto deploy capability for Assemblies  and Web Solution Packages
  • Neverfail Heartbeat v6.6.0 supports SQL Server 2008 file streams used for remote BLOB storage (which can be enabled when using SharePoint 2010)

Neverfail Plug-ins

  • Deploy Neverfail for SharePoint on all servers running SharePoint components and services
  • Deploy Neverfail Plug-in for FASTSearch separately on a server running FAST Search Server 2010 for SharePoint
  • Deploy Neverfail for IIS on Front End Web Servers, and Index Servers if the IIS role is present
  • Deploy Neverfail for File Server on Search Service Servers providing file share content
  • Deploy Neverfail for SQL Server on Database Servers

Changed Features

  • None

Issues Fixed

  • After installing Office Professional Plus 2010 Web Part the following exclusion file filter will need to be created C:\ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI\ OWSSVR.DLL.

Known Issues

The following are known issues in Neverfail for SharePoint Plug-in V201.5.4

  1. Installation Issues
    1. SharePoint deployed with a remote SQL Server database.

      In order to check the availability of the Exchange server and deploy web parts, a lookup is performed on the SQL Server database, this requires the service account used to run NfServerr2 (default LocalSystem) to include permissions to access the database. Add a user 'Domain\SPMachineName$' with db_owner permissions on the SharePoint Databases SharePoint_Config and WSS_Content.
  2. Operational Issues
    1. Enable plug-in configuration to protect Search Indexes - ‘Protect Search Index Files’
    2. To protect the SharePoint backup directory follow the advice in Knowledge Base article #664 - 'Neverfail for SharePoint – Application Module – Feature List'
    3. Changes made to the service account (username or password) used to run SharePoint services after the install of Neverfail, should be made on the Passive server otherwise services will fail to start.
    4. The Administrator must close any SharePoint WorkSpaces that are opened on the local SharePoint Server before performing a switch over. Failure to do so will cause an out-of-sync to be reported on some files in the folder C:\USERS\USER.DOMAIN\APPDATA\LOCAL\MICROSOFT\OFFICE\Groove\System\. This does not apply when the WorkSpace is opened from a remote server.
    5. SharePoint Foundation Search V4 and SharePoint Server Search does not start on the Secondary server after a switchover (Ref-12376).
      Workaround: Re-enter the Username and Password for the services that failed to start. See Knowledgebase article #2305 - Services added after Neverfail for SharePoint is installed May Fail to Start After A Switchover/Failover .
    6. With SharePoint Services 3.0, the default web parts do not display after a switchover (Ref-12338).
      Workaround: Reset the permissions of the folders indicated in Knowledgebase article #2306 - After a Neverfail for SharePoint Switchover SharePoint Services Default Web Parts Do Not Display
    7. Virtual Bytes can trigger a rule each time the rule is checked (EN-859).
    8. Replication may stop when creating a new SharePoint 2010 web Application (Ref-12321).
      Workaround: Restart replication after creating the new SharePoint 2010 web Application or stop Neverfail Heartbeat before creating the new SharePoint 2010 web Application. See Knowledgebase article #2307 - Replication Stops When Creating a New SharePoint 2010 Application With Neverfail for SharePoint Installed .
    9. After a switchover, Neverfail for SharePoint reports a service has failed when the service is running (Ref-12082).
      Workaround: After performing a switchover, clear the Application Health status. See Knowledgebase article #2308 - After a Switchover Neverfail for SharePoint Reports a Service Has Failed to Start When the Service is Running .
    10. After a switchover, a warning “SharePoint Cannot connect to the configuration database.” event occurs (EN-679).
    11. The Search service doesn’t work after switch over (EN-680).
  3. Uninstall /Reinstall
  • Uninstalling Neverfail Heartbeat leaves the SharePointNFPlugin key in registry (EN-681).

Supporting Documentation

  • None

Installation Information

Note: If SharePoint is installed in a custom install path, please see Knowledgebase article #2312 - Office SharePoint Server Search Service Fails to Start on the Secondary Server after a Switchover With Neverfail for SharePoint Installed .

  1. Initial installations of Neverfail for SharePoint Plug-in should be performed using the Neverfail Setup process. Subsequent uninstall / reinstalls and upgrades may be performed using the Application -> Plug-ins tab of the Neverfail Heartbeat Management Client.
  2. Configuring Exchange Availability Rule & Auto Deploy of Web Parts
    • If SQL Server is remote then these rules and tasks require a lookup on the SQL Server database, this requires the service account used to run NfServerr2 (default LocalSystem) to include permissions to access the database. Add a user 'Domain\SPMachineName$' with db_owner permissions on the SharePoint Databases SharePoint_Config and WSS_Content.

      Note: 'Domain\SPMachineName$' must be added before the first switchover to allow web parts to be deployed on the Secondary server.
  3. For uninstall and reinstall instructions, please refer to Knowledgebase article #1861 - How to Upgrade Neverfail Plug-ins .


Applies To

Neverfail for SharePoint Plug-in V201.5.4


Related Information

None

KBID-2077

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.