Gradience Pro / Enterprise - Exclusive use of the database is required...

 You have exceeded the maximum number of users...

  •  An Enterprise license allows unlimited simultaneous users at a single business site.
  •  A Professional license only allows up to 5 simultaneous users at a single business site.

Note:  This 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.

Note:  Make sure that any user that utilizes the software has exited Gradience before continuing.

This article offers you the following three options...

Option One:

Note:  The steps below can only be run while physically at the computer where the database resides. 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. You may encounter difficulty trying to run this through a remote tool like RDP.

1. At the machine hosting the data...

  • On Windows 7, on Server 2008 and 2008 R2 click Start All Programs > Gradience Maintenance Database Monitor.
  • On Windows 8, Windows 10, and Server 2012, click Start All Apps > Gradience Database Monitor.

2. Log in as you would log into the software. Please be patient. You will [not] see the spinning wheel or an hourglass. For a few moments it will appear as if nothing is happening and then the Database Monitor will open. 

3. Click the Connections button on the right and then click Clear Inactive.

4. To close out of the Database Monitor click File > Exit.

If the issue persists please go to www.gradiencesupport.com and click on Submit a Request. This will open up a support ticket. Please provide your account number if you know it to help speed a response and please provide as much detail as possible about the issue. 

Option Two:

1. Sever the connection to the database at the machine where the database is by opening Services and stopping Firebird.

2. Rename the database by going to where your database is (hrware.gdb) and renaming it hrware1.gdb.

3. Re-point the software by going to c:\programdata\gradience and opening the Hrware.ini file. The first few lines will look like one of the two examples shown below.

4. Change HRWARE.GDB to HRWARE1.GDB.

5. Restore the connection to the database at the machine where the database is by opening Services and restarting Firebird.

6. At the machine where the database is, do one of the following...

On Windows 7, on Server 2008 and 2008 R2 click...
Start All Programs > Gradience Maintenance DB Monitor.

On Windows 8, Windows 10, and Server 2012, click...
Start All Apps > Gradience Database Monitor.

7. Log in as you would log into the program and be patient while it opens as it may not open immediately.

8. Click Connections > Clear Inactive and then click File > Exit.

9. Sever the connection to the database once again. At the machine where the database is, open Services and stop Firebird just as you did before and then close-out of Services.

10. Change the name of the database back to what it was originally. Go to where your database is located and change the name from hrware1.gdb back to hrware.gdb again. 

11. Point the software back to the original database name. At the machine where the database is go to c:\programdata\gradience and open the Hrware.ini file.

12. Restore the connection to the database. At the machine where the database is, open Services and start Firebird.

13. Open the Gradience program.

If the issue persists, go to www.gradiencesupport.com and click on Submit a Request to open a support ticket. Please give your account number if you know it and provide as much detail about the issue as you can. 

Option Three:

If the inactive connections apper to remain after trying Option One and Option Two, follow the steps below.

1. Sever the connection to the database at the machine where the database is by opening Services and stopping Firebird.

2. Rename the database by going to where your database is (hrware.gdb) and renaming it hrware1.gdb.

3. Re-point the software on the server [and] on each legitimate client workstation by going to [each] of them and going to c:\programdata\gradience and opening the Hrware.ini file. The first few lines will look like one of the two examples shown below.

4. Change HRWARE.GDB to HRWARE1.GDB.

5. Restore connectivity to the database by going to the machine where the database is and opening Services and restarting Firebird.

Even though the [list] of inactive connections may remain, the number of clents permitted by your license will be able to connect to the database simultaneously.

 

 

 

 

 

 

 

Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.