Error Code 59 for Networks

Edition dated 20-3-2019

When you installed our Wordshark or Numbershark program and activated the licence, the licence was verified against a location and a machine, and a resultant code placed in registry and licence file. The registry is used by the program to find its various elements.

If wishing to move the shared data folder (wordshark-shared or numbershark-shared), either within a single server or when migrating to a new server, you need to deactivate first, then uninstall the C-Server or S-Server, reinstall to the new location and then reactivate at the new location. 

Moving the shared folder without following this process has upset the licencing and registry entries, resulting in Error 59. This error indicates that a licence & config file are missing from the shared folder OR are reported to be in an incorrect location.  

This error is common to:  Wordshark & Numbershark, v4.10 and v5, activated network product.

This error occurs when the program is unable to find the XML file that should be on the root of the wordshark-shared or numbershark-shared program folder on the server, OR the XML file is expected to be found in a different location. This may happen for several reasons. The most common are:

At, or shortly after, initial install:

• If you have installed from a disk or server files that are weeks/months old,  we recommend uninstalling the program and reinstalling the program and Management tools using the latest MSIs, also available from the above link.
  
• The program has not yet been activated in order to authorise the program to run. The install instructions and Troubleshooting Guide need to be revisited:  www.wordshark.co.uk/support/net500 (Version 5) or www.wordshark.co.uk/support/net400 (Version 4).  
  
• After installing the server components of the program, the program needs to be activated via by the Manager,  and is then monitored by the Service. If the Manager and Service have not been installed, then the install needs to be completed as per the install instructions.
  
• The Manager and Service require .net Framework 3.5 (see our “Minimum Specification” section in the instructions) in order to run. If you have Server 2008 or 2012 you may find you have .net Framework 4 or 4.5. These are not adequate. Refer to our Troubleshooting guide.
  

After the program has been working as intended:

The programname-shared folder has been moved, or the path changed: 

• If either is required, then the path must also be changed from within our network MANAGER 1.0.33 (from Nov 14) or later, and also in the desktop icon properties / Shortcuts tab “Start in”. Ensure UNC paths are used throughout.
  
• If you have an earlier MANAGER, then this is not possible. Instead, you will need to repair the damaged registry entries and recreate the licence files.  
  
• First, move the whole folder back to its original position: The program will attempt a self – repair. See if this works for Admin users.
  
• Second, deactivate your licence. Please open your White Space MANAGER, click on [programname], and click on the “Change” button, and agree to deactivate.
  
• Uninstall the C-Server or S-Server for [programname] to remove the registry entries.
  
• Reinstall, to create a new [programname]-shared folder. Share and ensure correct permissions. Whilst reinstalling, it is worth using the latest MSIs from the download site for your program/version (see initial documentation).
  
• Restart the SERVICE and MANAGER: Check to see that these have picked up the new UNC path.
  
• Activate the licence from within MANAGER.
  
• At that stage, make a copy of the old [programname]-shared folder.
  
• DELETE from the copy of the old [programname]-shared folder the files “options.sha” and the “XML” file in the root of the folder.  Also delete the subfolders except “Resources” [if present]. 
  
• Move all of the remaining contents of the copy of the [programname]-shared folder into the new [programname]-shared folder. 
  
• Run the program and test.
  

The server is temporarily not functioning, or communication to it has been lost.

The XML file may have been deleted. This will normally self-repair after restart of the program. If it does not, open the MANAGER and reactivate the program.

There are quite a large number of things that could go wrong in this process. Please be ready to contact us. We can help better if you  send us the diagnostics & other details listed in the network install instructions and here