Users run on a terminal server. I have run cblcored from different users and see that they set the same entry under HKLM namly 2 for the key core_on_error. No dumpfile exept mfdebug.log is created - no cblcore.
No other occurance of the key core_on_error can be found in the entire registry
+2Users run on a terminal server. I have run cblcored from different users and see that they set the same entry under HKLM namly 2 for the key core_on_error. No dumpfile exept mfdebug.log is created - no cblcore.
No other occurance of the key core_on_error can be found in the entire registry
What product and version number are you running?
You might try setting the core_on_error tunable in a cobconfig file instead of using cblcored.
See: http://supportline.microfocus.com/documentation/books/nx51ws01/udtuts.htm#s004
Users run on a terminal server. I have run cblcored from different users and see that they set the same entry under HKLM namly 2 for the key core_on_error. No dumpfile exept mfdebug.log is created - no cblcore.
No other occurance of the key core_on_error can be found in the entire registry
NE 3.1, using cobconfig is difficult as it must be set per user, not system wide. Aftre a test i can say that doesn't work either.
Tested the demo cblcore and the exefile creates cblcore and mfdebug.log on my machine (XP)
On target (TS win 2008) no cblcore or mdfebug is created. cblcored is ran with dump prompt. No rts-rerror is showed either.
On other occations other app is creating mfdebug.log but thats all, bo cblcore as it should.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
