Feb 8, 2019 - User-defined license not found - level defined in level.txt. You may find it useful to review the Sentinel RMS License Manager log file, given.
I figured it out what was going on no thanks to Etap's support people.Etap 7.5 is using a new hasp license manager program. If you try to load the 7.5 license manager program with the hasp is plugged into the USB port (as it normally would be) the ETAPS.INI file doesn't configure properly. The file is missing the:HASP after the pc name. As example, 'My pc:HASP'.
What you get is a license manager not running or HASP unrecognized error message box popup.I'm not a programmer but it appears that if the older license manager is running and sees a hasp plugged in, it doesn't allow the new license manager to load.The fix, as it turned out, is simple. Unplug the hasp then install the 7.5 license manager. Then plug in the hasp. Good to go.I relayed this to Etap support and was told arrogantly they tested the license manager and found no issues.
I asked if they tested on a XP machine. Not a Windows 7 machine. There was no response to my question.
Not surprising.I spent several days, numerous email and phone calls to Etap support and got very little help. This was further hindered because the support people at Etap don't speak English very well so there is a real communication problem.I started out with Etap 6.0 and like the software.
With 7.0 then 7.1 and now 7.5 releases the software took a turn for the worst IMHO. There seems to be a decline in support as well.I just downloaded EasyPower 9 demo. Really nice software.
They really did their homework and put together a killer package. It blows the doors off of Etap. I had a technical question and called Easypower support and actually spoke to someone that spoke english and emailed me a detailed explanation on how the function worked compete with examples. Wow!I'm now considering trashing Etap and going with Easypower 9. I have the green hasp key and running Etap 7.5 on a XP machine, sp3.
As I said the fix is easy. Just unplug the key before loading the new license manager. I had problems with 7.1 that turned out to be a batch of defective CD's that wouldn't run on Windows 7 that were inadvertently shipped to customers. Not all customers got the bad CD's.
Only ones with company names A thru E. I was hoping 7.5 would fix the lousy cable library that is confusing and as far as I can see doesn't agree with any NEC table I can find.
I made my own cable library using NEC tables. I figured it out what was going on no thanks to Etap's support people.I relayed this to Etap support and was told arrogantly they tested the license manager and found no issues. I asked if they tested on a XP machine. Not a Windows 7 machine. There was no response to my question. Not surprising.I spent several days, numerous email and phone calls to Etap support and got very little help. This was further hindered because the support people at Etap don't speak English very well so there is a real communication problem.I started out with Etap 6.0 and like the software.
With 7.0 then 7.1 and now 7.5 releases the software took a turn for the worst IMHO. There seems to be a decline in support as well.I just downloaded EasyPower 9 demo. Really nice software. They really did their homework and put together a killer package. It blows the doors off of Etap. I had a technical question and called Easypower support and actually spoke to someone that spoke english and emailed me a detailed explanation on how the function worked compete with examples.
Wow!I'm now considering trashing Etap and going with Easypower 9.We have used ETAP continuously for seven years and never encountered a problem the technical support people did not solve quickly, and also never encountered an 'arrogant' answer.
Network License Server Setup Network License Server SetupIncluded on the CD-ROM is the HASP Driver and HASP License Manager Setup. Once these are installed, insert the Network USB Key in an open USB Port on the License Server.Install the driver from the CDROM (CDDrive:License Server SetupHASP DriverHASPUserSetup.exe).Install the License Manager from the CD-ROM (CDDrive:License Server SetupHASP License ManagerImsetup.exe). Setup License Server ManuallyAfter successfully running the setup for the license server, if you chose to manually install the device driver for the security key and launch the license manager software, follow the steps below. Install the Device Driver:.
Open a DOS box and run HINSTALL -i from the directory to which you installed the license server. After you receive a confirmation that the driver installed successfully, reboot the workstation. Start the License Manager Software:From the directory to which you installed the license server, run NHSRVW32.EXE. A window will appear and show the network protocols to which the license manager will listen for license requests.Please Note: You need to install the device driver only once. However, you must launch the license manager program each time you reboot the key server.
To automatically start the license manager each time you reboot the system, create and place an icon for NHSRVW32.EXE in the workstation’s startup folder. Find a License Key Server on a Routed NetworkIn order for a workstation to run the network version of ProModel properly, the workstation must check out a license from a license server. To make a license request, the workstation sends a broadcast message out on the network and awaits a response from the license server. If the license server and the workstation running ProModel are on the same sub net of a routed network (or on the same network of a non-routed network), the license server receives the request and responds. Due to the nature of routed networks, if the license server and workstation running ProModel are not on the same sub net of a routed network, the key server will not receive the license request broadcast.To resolve this problem, the workstation must send a license request directly to the computer on the network set up as the license server.
To identify which computer on the network is the license server, you must create and store a text file called NETHASP.INI in the directory to which you installed ProModel on the workstation or file server.For TCPIP-based networks the NETHASP.INI file must contain the following linesNHCOMMONNHTCPIP=Enabled;NHTCPIPNHTCPIPMETHOD=TCPNHSERVERADDR= Please Note: If you followed step 8 in the network installation instructions for ProModel, the NETHASP.INI file is generated automatically.© 2012 ProModel Corporation. 556 East Technology Avenue. Orem, UT 84097. Support: 888-776-6633.