|
Known Issues, Troubleshooting, and Upgrading |
  
|
|
Known Issues, Troubleshooting, and Upgrading |
|
Known Issues
| 1. | Do not install over an existing installation. If applicable, uninstall the previous version first before installing a new version. See the Upgrades section below for more information. |
| 1. | Stop all file collaboration jobs and close the PeerLink Hub client application. |
| 2. | Stop the PeerLink Broker, PeerLink Hub, and PeerLink Agent services on all systems. |
| 3. | Backup the "Hub\workspace\jobs" folder relative to the installation directory of the PeerLink Hub. |
| 4. | Uninstall the PeerLink Hub by launching the uninstall.exe application located in the PeerLink Hub installation directory. Delete any folders/files that may be left behind by the uninstaller. |
| 5. | Uninstall all Agents by launching the uninstall.exe application located in the PeerLink Agent installation folder. Delete any folders/files that may be left behind by the uninstaller. |
| 6. | Run the new installer for the PeerLink Hub. |
| 7. | Run the new installer for the PeerLink Agent on all the participating servers. |
| 8. | Copy the backup copy of the "jobs" folder into the "Hub\Workspace\" folder (again, relative to the installation directory of the PeerLink Hub). |
| 9. | Restart the "PeerLink Hub Service" from the Windows Service Panel (services.msc). |
| 10. | Launch the "PeerLink Hub Client" application |
| 11. | Start the desired jobs. |
| • | Error code 13011 The specified main mode authentication list was not found. The fPolicy Server connects to the NetApp device but fails on registration with error above. The NetApp ONTAP console shows an error message similar to the following: User DOMAIN\COMPUTER$ denied access - missing required capability: ‘(Not in a local group.)’ |
Reason |
Agent running under local system account. |
Solution |
Change the Agent service account to a domain user account. |
| • | Error code 14001 Error registering fpserver.dll Side-by-Side error The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more details. If two instances of fpservice.dll are loaded on same machine then only one dll can register successfully. However it will not receive any events. If the issue occurs on a 2008 server, it is possible that the system does not have the correct C++ runtime libraries which are noted in the Windows Event Viewer. The solution is to install the following Microsoft Visual C++ 2005 runtime library (must be 32 bit): http://www.microsoft.com/downloads/en/details.aspx?familyid=766A6AF7-EC73-40FF-B072-9112BAB119C2&displaylang=en |
Note: PeerLink is a 32 bit application and will require the 32 bit Microsoft Visual C++ 2005 runtime library.
| • | Error code 13003 Error 13003 creating FPolicy POLICYNAME : User DOMAIN\USER does not have capability to invoke API fpolicy-create-policy. (13003) |
Reason |
Unable to register and create a policy due to insufficient privileges. |
Solution |
The PeerLink Agent service account must be a Domain User with Domain Backup Operator privileges and must either be a Domain Administrator or be a member of the Local Admin Group on the Filer. You can add a domain user to the Local Admin Group of the Filer with the following ONTAP command (where domainUserName represents the name of the user account):
useradmin domainuser add domainUserName -g administrators |