#OXYGEN XML EDITOR 10.0 PC#

Do you have another properties file that logs more diagnostics? I see that you have instrumented the License Server with log4j and there is a 'log4j.properties' file in the directory. I also verified that the License Server was listening on port 12346 both times using SystemInternals 'tcpview'. I even double checked running the client on a different workstation (after pointing to the License Manager on the new Server). I could change the way the License Manager ran as a Windows Service or as an application and the client would not work the first way but always ran the second way. The behavior was always repeatable and I even re-booted the Server (being after hours at the time). I put back the original license file and the client worked again.

Then, as expected, I got an error message when I tried to run the OxygenXML client against the Oxygen License Server running as an application (started from the batch script). I tested the license file by adding a couple of spurious characters. I used the standard settings for License Manager installation and then copied the license file to the 'licenses' directory. I made no changes to the batch files and I executed them from double-clicking on the batch files from Windows Explorer. And all I was doing on the Server was running the batch files in the License Manager directory to start/stop it as a windows service and to run it as an application. What was changing was how I ran the OxygenXML License Manager on the server.

#OXYGEN XML EDITOR 10.0 PC#

I would start OxygenXML on my PC to see if it would start and then shut it down. For this problem, I made no changes to the client settings after I initially entered them.

Oxygen xml editor 10.0