[Migrated content. Thread originally posted on 25 April 2012]
Hi,
Our MF cobol code exes and dlls are running (backend services) in windows 2003 R2 server. Its been 6 years and there are no changes made to it. When we try to set up a new environment in a different windows 2003 R2 server, it is failing with signal 11 (error name is mentioned in the subject) after processing few policies. Can anyone provide the right way to approach this problem? Is it anything access related issue?
It is working fine, if we do the same set up in XP desktop machines.
What is this SQLSVR32? Is it a dll or method? I am unable to find any dlls with this name instead there are versions of SQLSRV32.dlls are present in the machine.
I don't know on which version of MF cobol, the exes/dlls are built. If there is any way to identify, please let me know that too.
Thanks in advance
Anton
[Migrated content. Thread originally posted on 25 April 2012]
Hi,
Our MF cobol code exes and dlls are running (backend services) in windows 2003 R2 server. Its been 6 years and there are no changes made to it. When we try to set up a new environment in a different windows 2003 R2 server, it is failing with signal 11 (error name is mentioned in the subject) after processing few policies. Can anyone provide the right way to approach this problem? Is it anything access related issue?
It is working fine, if we do the same set up in XP desktop machines.
What is this SQLSVR32? Is it a dll or method? I am unable to find any dlls with this name instead there are versions of SQLSRV32.dlls are present in the machine.
I don't know on which version of MF cobol, the exes/dlls are built. If there is any way to identify, please let me know that too.
Thanks in advance
Anton
SQLSVR32.OBJ is a Net Express object module that is linked into your programs to provide run-time support for programs using embedded SQL statements.
You should look at possible differences between the Windows 2003 system on which it runs fine and the one on which it is failing, especially in the area of database software versions installed, ODBC drivers etc.
When the program fails with the 114 error it should be creating a file named MFDEBUG.LOG in the applications folder.
Can you please post the contents of this file so that we can look at it?
This file can tell us what product version that you are using as well as information about programs on the call stack at the time the error occurred.
Thanks.
[Migrated content. Thread originally posted on 25 April 2012]
Hi,
Our MF cobol code exes and dlls are running (backend services) in windows 2003 R2 server. Its been 6 years and there are no changes made to it. When we try to set up a new environment in a different windows 2003 R2 server, it is failing with signal 11 (error name is mentioned in the subject) after processing few policies. Can anyone provide the right way to approach this problem? Is it anything access related issue?
It is working fine, if we do the same set up in XP desktop machines.
What is this SQLSVR32? Is it a dll or method? I am unable to find any dlls with this name instead there are versions of SQLSRV32.dlls are present in the machine.
I don't know on which version of MF cobol, the exes/dlls are built. If there is any way to identify, please let me know that too.
Thanks in advance
Anton
One possibility is Windows Data Execution Protection (DEP), which can cause protection faults, which in turn become RTS 114 errors under the MF COBOL runtime.
These faults often indicate actual bugs, but there are cases where a valid COBOL module built with an older product version simply is not compatible with DEP. (Typically this is because the runtime wants to execute code it's loaded into a data segment.)
You can read more about DEP in
this MSDN article, among others.
You can specify programs for which DEP should not be enabled. See for example:
http://technet.microsoft.com/library/cc700810.aspx#XSLTsection124121120120Your Windows system administrator should be familiar with DEP - it's a standard Windows system administration task.
[Migrated content. Thread originally posted on 25 April 2012]
Hi,
Our MF cobol code exes and dlls are running (backend services) in windows 2003 R2 server. Its been 6 years and there are no changes made to it. When we try to set up a new environment in a different windows 2003 R2 server, it is failing with signal 11 (error name is mentioned in the subject) after processing few policies. Can anyone provide the right way to approach this problem? Is it anything access related issue?
It is working fine, if we do the same set up in XP desktop machines.
What is this SQLSVR32? Is it a dll or method? I am unable to find any dlls with this name instead there are versions of SQLSRV32.dlls are present in the machine.
I don't know on which version of MF cobol, the exes/dlls are built. If there is any way to identify, please let me know that too.
Thanks in advance
Anton
Hi, I checked for MFDEBUG.LOG, but it is not present in the server where it runs/fails. Also, I have added the EXEs on DEP exclude list. but still, the problem is not rectified.
Also, in some other server, for one user (login id), it is working, but on the same server, for another user, it fails. Do any one have any clues on what could cause this issue?
[Migrated content. Thread originally posted on 25 April 2012]
Hi,
Our MF cobol code exes and dlls are running (backend services) in windows 2003 R2 server. Its been 6 years and there are no changes made to it. When we try to set up a new environment in a different windows 2003 R2 server, it is failing with signal 11 (error name is mentioned in the subject) after processing few policies. Can anyone provide the right way to approach this problem? Is it anything access related issue?
It is working fine, if we do the same set up in XP desktop machines.
What is this SQLSVR32? Is it a dll or method? I am unable to find any dlls with this name instead there are versions of SQLSRV32.dlls are present in the machine.
I don't know on which version of MF cobol, the exes/dlls are built. If there is any way to identify, please let me know that too.
Thanks in advance
Anton
Hi, I checked for MFDEBUG.LOG, but it is not present in the server where it runs/fails. Also, I have added the EXEs on DEP exclude list. but still, the problem is not rectified.
Also, in some other server, for one user (login id), it is working, but on the same server, for another user, it fails. Do any one have any clues on what could cause this issue?
[Migrated content. Thread originally posted on 25 April 2012]
Hi,
Our MF cobol code exes and dlls are running (backend services) in windows 2003 R2 server. Its been 6 years and there are no changes made to it. When we try to set up a new environment in a different windows 2003 R2 server, it is failing with signal 11 (error name is mentioned in the subject) after processing few policies. Can anyone provide the right way to approach this problem? Is it anything access related issue?
It is working fine, if we do the same set up in XP desktop machines.
What is this SQLSVR32? Is it a dll or method? I am unable to find any dlls with this name instead there are versions of SQLSRV32.dlls are present in the machine.
I don't know on which version of MF cobol, the exes/dlls are built. If there is any way to identify, please let me know that too.
Thanks in advance
Anton
Hi, I checked for MFDEBUG.LOG, but it is not present in the server where it runs/fails. Also, I have added the EXEs on DEP exclude list. but still, the problem is not rectified.
Also, in some other server, for one user (login id), it is working, but on the same server, for another user, it fails. Do any one have any clues on what could cause this issue?
[Migrated content. Thread originally posted on 25 April 2012]
Hi,
Our MF cobol code exes and dlls are running (backend services) in windows 2003 R2 server. Its been 6 years and there are no changes made to it. When we try to set up a new environment in a different windows 2003 R2 server, it is failing with signal 11 (error name is mentioned in the subject) after processing few policies. Can anyone provide the right way to approach this problem? Is it anything access related issue?
It is working fine, if we do the same set up in XP desktop machines.
What is this SQLSVR32? Is it a dll or method? I am unable to find any dlls with this name instead there are versions of SQLSRV32.dlls are present in the machine.
I don't know on which version of MF cobol, the exes/dlls are built. If there is any way to identify, please let me know that too.
Thanks in advance
Anton
The possibilities are almost unlimited. A 114 indicates a memory protection violation; that means your program has done something that has undefined behavior. It could be almost anything.
There are any number of reasons why the behavior might differ among users. It's not clear from your description whether the program is actually running under the user's account (earlier you described it as "backend services", which typically do not run under the end-user's account), but in any case there's little point even in speculating.
I believe at this point you need to open a support incident with Micro Focus Customer Care. Be aware, though, that it's quite possible that the problem is due to a bug in your application.
