Where are you going to run SBADMCL? On Client or Server? You should match the same version that is locally installed. So 5.2.0 on Client and 5.2.4 on Server. Unless for whatever reason you prefer to keep non-matching versions?
We're trying to run sbadmcl for autoboot on the client. We get the following error:
Dll version: 126.96.36.199
>>>>Connecting to "Safeboot Database"
>>This application (SBADMDLL) is not licensed for this database
ResultDescription: License Invalid
not sure how knowing the modules would help?
there are a couple of possible reasons for "licence invalid"
a) your bought the product without a licence for the scripting API (check the licence information in SBAdmin/EEM - it will tell you if SBAdmcl is licenced in the addons list)
b) your licence has expired - perhaps you are trying to connect to a db running an eval licence, and the db is more than 30 days old?
Either way, the licence info screen in EEM/SBAdmin will tell you.
The licence is always checked by SBAdmCL when running database side commands.
All I can think of is that the copy he is running is connecting to a database where the license is expired, perhaps an evaluation db etc.
If an EEPC installation set was created before sbadmcl was added to the license, can you add the three sbadmcl files to the encrypted machine after sbadmcl has been added to the license?