Please use the part that best applies to you.
PART ONE:
Option One: Run a database maintenance.
--NOTE-- The steps below can only be run while physically at the computer where the database resides. You may encounter difficulty trying to run this through a remote tool like RDP.
1. Your operating system determines where to go:
On Windows 7, on Server 2008 and 2008 R2 click...
Start > All Programs > Gradience > Maintenance > Database Maintenance.
On Windows 8, Windows 10, and Server 2012, click...
Start > All Apps > Gradience > Database Maintenance.
2. Click the Start button that appears at the lower left corner of the popup. This cannot be done remotely through RDP. You have to either be [physically] at the computer where the database resides or you need to remote into the console.
3. Close the DB maintenance utility when it is finished and try to open gradience again.
Option Two:
1.Uninstall Gradience. Remember the software does not [ contain ] any data. All of your data are in a database file that resides [ outside ] the software so uninstalling the software will not remove your data.
2.Click here to download the installation file for the latest iteration of version 12.
--CAUTION!-- If you are running Gradience on multiple computers you must ensure that you are running the [same] iteration of the [same] version on all of those computers including the server. Otherwise you risk corrupting the data beyond repair.
PART TWO:
When attempting to restore a backup this error may occur:
The likely cause is database corruption. Please do the following:
1. Reopen Gradience and once inside, click File > Maintenance > Back up Database.
2. Close out of Gradience and try to restore the backup you just made. If the restore goes through successfully where it failed when attempting to restore the [other] backup, it would indicate that the backup that would not restore is corrupt.
SOLUTION: Restore a different backup.
PART THREE:
When opening Gradience version 12 for the first time while the database is still empty this error may occur:
"Errors encountered during system update:
[FireDAC][Phys][FB]Dynamic SQL Error
SQL error code = -104
Token unknown - line 1, column 51
("
Solution:
Go to C:\Programdata\Gradience on the server and delete the new, blank database altogether but leave the Gradience folder there and then uninstall Gradience and then reinstall Gradience. This time though even though you are at the server, install it as a standalone. Then launch it to see whether the error occurs. If not, enter the product key and get all the way into the software. Then close out.
Now, go to the client and go to C:\ProgramData\Gradience and open the Hrware.ini file. When it opens, the 3rd or 4th line from the top will say:
SERVER=
Following the equal sign you will see the name of the server. Change that to Localhost.
The 2nd line from the top should be:
PATH=
If what follows the equal sign is:
C:\ProgramData\Gradience\Hrware.gdb
Leave it alone.
If some other drive letter or folders appear in the path, jot down what that is and change it to:
C:\ProgramData\Gradience\Hrware.gdb
Save whatever changes were made and do not concern yourself with additional lines further down in the file. Just close-out of it.
Now, uninstall Gradience and then reinstall Gradience as a standalone. Then launch it to see whether the error occurs. If not, enter the product key and get all the way into the software. Then close out.
Now, while still at the client workstation, go to C:\ProgramData\Gradience and open the Hrware.ini file. When it opens, the 3rd or 4th line from the top will say:
SERVER=
Following the equal sign you will see Localhost. Change it back to the name of the server.
The 2nd line from the top should be:
PATH=
Make sure what follows the equal sign is whatever was there originally. You should have jotted that down earlier.
Save whatever changes were made and do not concern yourself with additional lines further down in the file. Just close-out of it.
Reopen the software at the client workstation and the error should no longer occur.
Comments
Article is closed for comments.