Gradience Pro / Enterprise - Runtime Error 217 on a Client Workstation after Windows 10 Update 1709

These instructions specifically apply to a client workstation.

If you are not sure whether the affected computer is…

  • A Client or...
  • A Standalone, or…
  • A Server,

…please determine this first before proceeding with the steps below because the solution involves installing a specific release of version 11 and you may be running another release on another machine or may even be running version 12 on another machine. 

How to Verify whether this machine is a Server or a Client or a Standalone...

1. Go to C:\ProgramData\Gradience and open the Hrware.ini file. 

2. Very near the top, you will see a line that begins with...

Server= ...Whatever follows the equal sign is the computer hosting the data.

If you see anything other than the word Localhost, it means that your machine is a Client Workstation. If it says Localhost, it means that this is either a standalone or a server but [not] a client.

  • If you are certain that no one else can use Gradience from another computer to access the data, you have a standalone. If this is the case, please click here for the correct instructions.
  • If you are [not] the only one using the software but you saw Localhost, it means that this is a server so please click here for the correct instructions.

Version 12 Users Have two Options...

Option One for version 12 Users:

If you had previously used version 11 and upgraded to version 12 but have been running version 12 for only a short while or you have not done much data entry since using version 12, you may want to consider reverting back to version 11. If you do this, you will have to restore a backup that you made while you were using version 11 so any data entered while using version 12 will have to be re-entered but at least you can continue using Gradience on Windows 10.

Option Two for version 12 Users:

If you have been running version 12 for many months or have never run anything other than version 12, It will not be possible to revert to version 11 because you will have no version 11 backup that you can restore. For this situation, we can offer you a workaround below that will allow you to remain on version 12.

Workaround for Option Two Above...

You can open up a Windows 7 VM [virtual machine] on your Windows 10 computer. Install version 12 on that. Before installing on the VM, you should open the[actual] Windows 10 computer and go to C:\ProgramData and copy the Hrware.ini file. Then open the VM and go to C:\ProgramData and create a Gradience folder there. Then paste-in the copied Hrware.ini file. [Then] click here to install version 12 as a Client on the VM and it will automatically be pointed to the data.

Version 11 Users...

IMPORTANT! Since the computer with the problem is a client workstation, it stands to reason that at least one other computer/server is running Gradience, ...perhaps more. Because of this fact, you MUST ensure that they [all] are running the [same] iteration of version 11!

The solution for the Runtime Error 217 involves installing version 11.0.1606.29, which came out on June 29, 2016 so your other computer(s) will have to be running this same iteration too.
The 16 refers to the year 2016.
The 06 refers to the month of March.
The 29 refers to the day-of-the-month.

CAUTION! If the full, multi-digit version of Gradience that is running on other computers differs,  you MUST update Gradience on that machine/those machines to version 11.0.1606.29

If the other computers are not running this particular release of version 11 and you install this release of version 11 on the affected client workstation, you will be introducing a scenario where you have [different releases] of version 11 touching the [same] data. This could potentially corrupt your data beyond repair!

So... Your first step is to verify the full, multi-digit version number of Gradience on [each] of the other computers. You can find the fullmulti-digit version number inside the software by clicking Help > About. There are also two ways to view the version from [outside] the software.

1. Go to Programs & Features to view it on the list. If it shows Gradience Professional, it will also give the version number. If it doesn't have the words Gradience Professional disregard it and go to step 2 below.

2. Go to C:\Program Files (x86)\Gradience and open the Common folder. Then scroll down to and right-click on GCore.exe and click on Properties > Details to view the fullmulti-digit version number. 

Any machines that are running a version of Gradience that is older than 11.0.1606.29 will have to have Gradience updated to this version so that all machines will match what you will be installing on the affected machine. Please click here to install version 11.0.1606.29 wherever else it is needed including the server if necessary.

IMPORTANT! Steps 1 through 5 below are unique to the affected machine. Do not follow steps 1 through 5 at other computers where you are merely bringing the version 11 up to the latest release. 

Resolving the Issue at the Affected Machine…

1. Go into Services and stop Firebird.

2. Go to Programs and Features and uninstall Firebird and Gradience [if you see them].

3. Go to C:\Program Files and delete the firebird folder [if you see one].

4. Go to C:\Program Files (x86) and delete the firebird folder [if you see one].

5. Go to C:\ProgramData and delete the firebird folder [if you see one].

6. Please click here to reinstall Gradience as a [Client]. Disregard any message you see a message about restarting the machine.

7. Attempt to open the software once again. If you need further assistance, please go to www.gradiencesupport.com and click on Submit a Request. When you submit your request, please be clear as to the following facts...

1. The full, multi-digit version number for Gradience.

2. The number of computers that are running Gradience.

3. The operating systems of the computers/server running Gradience.

4. The account number [if known] of the organization running the software.

5. The name of & main business phone number of the organization running the software.

6. The sales order number [if known] for the software license purchase. 

7. If the software was purchased through a reseller such as Office Depot, or Staples, or SHRM, or Quill, or Amazon, etc., please send us a scanned copy of the receipt. We are only authorized to render support to those for whom we can verify a current software license.

 

 

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.