Registered: 1398911567 Posts: 161
Reply with quote #1
Recently I had a "oh no" moment when our AP operators called to say they were receiving a message that our Readsoft license had expired. An urgent call to the Readsoft Support Desk, a temporary license file and 10 minutes later, AP were back on the system. But IT were a bit red-faced at this oversight and I thought it would be useful to share our lessons learned with other Readsoft Users.
What will we be doing differently next time? 1. Locate the license.dat file in the Flexlm directory of the Readsoft Server 2. Check the date that the license expires 3. Put a reminder in a few people's calendar to contact Readsoft a couple of weeks before the license expires if a new one has not been received. Note that Readsoft automatically send the license file about 4 weeks prior to expiry, however our experience shows this is not a foolproof process! Readsoft forgot to send the file and diligence was required at our end to check that the file was received. When I asked around, no-one knew who Readsoft was sending the file to (in previous years). So a good idea to proactively follow it up with Readsoft Support before license expiry. Now that you have the reminder set up, what do you do when you receive the new license file? 1. Stop your Transfer and Interpret services 2. In your old license file in the Flexlm directory, there will be the SERVER name at the top of the file. Copy the server name and rename the old licence file to something like license.dat.old 3. Open the new license file and paste the server name 4. Copy the new license file to the Flexlm directory 5. Using lmtools.exe click the Start/Stop/Reread tab 6. Select Force Server Shutdown 7. Click Stop Server 8. Wait 5 seconds then click Start Server 9. Wait 5 seconds then click ReRead License file 10. Copy the license.dat file to the Readsoft global path (the one where your eiglobal.ini is stored) 11. Restart the Transfer and Interpret Services 12. Test by opening Verify to determine that the application opens Note that I have thrown in stopping the services (not in Readsoft's documentation) because our Collector service stopped working after I stopped the Server. So probably a good idea to also stop your services and restart them, just to be sure. *** P.S I cut and paste the above steps into the calendar invite so the instructions are there too! __________________ Cheryl LinkedIn:
Registered: 1401866415 Posts: 5
Reply with quote #2
I would like to request for information in applying the new license file in the ECC6 system. Thanks Greg
Registered: 1398911567 Posts: 161
Reply with quote #3
We are on ECC6 too and maintain the license file per the above instructions. Kind regards __________________ Cheryl LinkedIn:
Senior Expert Member
Registered: 1452502418 Posts: 59
Reply with quote #4
I think you are asking for the cockpit license, is that right? You have two licenses, one for Invoices module (interpret, transfer, etc), and another one on ECC6 for Readsoft Cockpit (where you manage and post invoices). The license for cockpit is managed through transaction /cockpit/c46, you should receive the key from Readsoft then insert the code on that transaction. Hope that helps. Kind Regards. Ignacio.
Registered: 1399483819 Posts: 1
Reply with quote #5
Thanks for the thread Cheryl and all. A big help recently.