Hi,
This appears to be a security policy issue related to the account under which your test site runs. Your test.com works because it's the only site that has sufficient permission.
Our library needs to start child process at run time (in order to run the native browser engine inside the child process), at runtime it follows these logic to start the child process. If any of the following step succeed, then it will succeed:
1. If EnableEOWP is not set to true (default), it will try to use Windows\System32\rundll32.exe. This can fail if you have security policy that prevents your application from reading System32 directory, or from starting application in that folder;
2. If step 1 fail or EnableEOWP is set to true, then it will try to use eowp.exe by:
2.a. Look for eowp.exe inside bin folder and try to start it. This can fail if you have security policy that prevents your application from starting application in that folder (it's impossible that your application won't have read permission in that folder, otherwise your application DLLs won't be loaded);
2.b. If eowp.exe does not exist in the bin folder, we will try to create automatically in your temp folder. Again, if you have security policy that prevents your application from starting application in temp folder, then this step will fail;
It appears that all the above steps have failed in your environment. The key to resolve your issue is that you must find a location in your system where your application is allowed to start an exe. The following steps is an example of how this issue can be resolved/tested:
1. Create a dedicated folder on your system. For example, "c:\NoRestrictionHere";
2. Place an exe inside that folder. For testing purpose, you can create a simple console application test.exe;
3. Configure your folder permission to allow everyone to have execute permission in this folder;
4. Inside your application, call Process.Start("c:\\NoRestrictionHere\\test.exe") and see if it succeed;
If the above steps succeed, you can then place eowp.exe inside that folder and call
Code: C#
EO.Base.Runtime.InitWorkerProcessExecutable("c:\\NoRestrictionHere\\eowp.exe");
This does not create the exe file (since it's already there), but it tells our library where to look for it.
As part of troubleshooting process, you may also want to check your Windows event log to see if you can find any clues about exactly why your application was not allowed to eowp.exe at the first place.
Your code to collect log is correct --- however if you do not provide any log file name at all (pass null) when you call StopAndSaveDiagnosticLog, then the log will be sent to our server. If you do provide a file name, then the log will be saved to the log file and it will NOT be sent to our server. In that case the return value will be 0.
Thanks!