Hi Gaurav,
Holidays add a little delay to my investigation but I did some new test.
Here are conclusion or test result:
We create a new windows application on MSVC++ 2012 (VC11).
We use it as a stand alone application.
We start the application on the same machine (VM based) as previous.
The application Work.
We stopped it.
We start the application again and fail.
We wait.............
We start the application again and work.
While our application is running, we decide to run the SAM1.3.1 diagnostic tools.
- All green except for the last test (Sentinel Key Communication)
We start another instance of our Application.
- Failed to work even if the other instance is still working.
Conclusion are:
- Only one application can read the key. The application is holding something that prevent any other process to read it.
- It is NOT dependent of the running context (Run as Admin doesn't change the behavior)
If we call RNBOsproReleaseLicense, a second application can run in parallel. But we do not know (or understand what will be the affected on any other attempts to read/write into the key with the same "initialization". Do we need, after RNBOsproReleaseLicense, to recall RNBOsproFormatPacket and RNBOsproInitialize or the "environment" is preserved and we can just access the key again (and RNBOsproReleaseLicense after reading)?
Thank for your help and hope this will help you to help us!
Olivier