Highlighted
Absent Member.
Absent Member.
2917 views

Winform application setup

Jump to solution

Hi,

Recently we have migrated from netexpress dialogs to visual cobol dialogs. Our application was setup based on network share mode(as per instructions from Micro Focus) so that users from client work station can ping the application hosted in the windows 2012 server.

Now we are trying to convert dialogs to winforms. I have deployed winform executables to the server and it works good in the server but the application crashes when i try to ping from work station.

I am assuming that the same application setup should work for winform as well. Is there anything i need to take care of ?

---------------------------------

ERROR :

Version=1
EventType=APPCRASH
EventTime=131274350239260298
ReportType=2
Consent=1
ReportIdentifier=b3c704dd-cd46-11e6-9e4e-40a8f04619b3
IntegratorReportIdentifier=b3c704dc-cd46-11e6-9e4e-40a8f04619b3
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=WI100.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=58643056
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.23392
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=56eb2fb9
SigDevil.Name=Exception Code
SigDevil.Value=e0434352
Sig[7].Name=Exception Offset
Sig[7].Value=0000845d
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=\\testtaris\Taris\WI100.exe
UI[3]=WI100.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UIDevil=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=\\testtaris\Taris\WI100.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Program Files\McAfee\DLP\Agent\fcagpph32.dll
LoadedModuleDevil=C:\Windows\system32\USER32.dll
LoadedModule[7]=C:\Windows\system32\GDI32.dll
LoadedModuleMusic=C:\Windows\system32\LPK.dll
LoadedModule[9]=C:\Windows\system32\USP10.dll
LoadedModule[10]=C:\Windows\system32\msvcrt.dll
LoadedModule[11]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[12]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[13]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[14]=C:\Windows\system32\RPCRT4.dll
LoadedModule[15]=C:\Windows\system32\SHELL32.dll
LoadedModule[16]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[17]=C:\Windows\system32\ole32.dll
LoadedModule[18]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[19]=C:\Windows\system32\PSAPI.DLL
LoadedModule[20]=C:\Windows\system32\VERSION.dll
LoadedModule[21]=C:\Windows\system32\IMM32.DLL
LoadedModule[22]=C:\Windows\system32\MSCTF.dll
LoadedModule[23]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[24]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[25]=C:\Windows\system32\MSVCR110_CLR0400.dll
LoadedModule[26]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\51e2934144ba15628ba5a31be2dae7dc\mscorlib.ni.dll
LoadedModule[27]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[28]=C:\Program Files\Imprivata\OneSign Agent\ISXHookInit.dll
LoadedModule[29]=C:\Program Files\Imprivata\OneSign Agent\ISXHook.dll
LoadedModule[30]=C:\Program Files\Imprivata\OneSign Agent\ISXUtils.dll
LoadedModule[31]=C:\Program Files\Imprivata\OneSign Agent\isxtrace_dll.dll
LoadedModule[32]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[33]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[34]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[35]=C:\Windows\system32\Secur32.dll
LoadedModule[36]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[37]=C:\Windows\system32\MSVCP100.dll
LoadedModule[38]=C:\Windows\system32\MSVCR100.dll
LoadedModule[39]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[40]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23545_none_5c06d189a00e2c29\gdiplus.dll
LoadedModule[41]=C:\Windows\system32\WS2_32.dll
LoadedModule[42]=C:\Windows\system32\NSI.dll
LoadedModule[43]=C:\Windows\system32\NETAPI32.dll
LoadedModule[44]=C:\Windows\system32\netutils.dll
LoadedModule[45]=C:\Windows\system32\srvcli.dll
LoadedModule[46]=C:\Windows\system32\wkscli.dll
LoadedModule[47]=C:\Windows\system32\SAMCLI.DLL
LoadedModule[48]=C:\Windows\system32\USERENV.dll
LoadedModule[49]=C:\Windows\system32\profapi.dll
LoadedModule[50]=C:\Program Files\Imprivata\OneSign Agent\ISXCrypt.dll
LoadedModule[51]=C:\Windows\system32\CRYPT32.dll
LoadedModule[52]=C:\Windows\system32\MSASN1.dll
LoadedModule[53]=C:\Program Files\Imprivata\OneSign Agent\ISXComm.dll
LoadedModule[54]=C:\Program Files\Imprivata\OneSign Agent\ISXSendKeys.dll
LoadedModule[55]=C:\Windows\system32\OLEACC.dll
LoadedModule[56]=C:\Windows\system32\ntmarta.dll
LoadedModule[57]=C:\Windows\system32\WLDAP32.dll
LoadedModule[58]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\Comctl32.dll
LoadedModule[60]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=WI100.exe
AppPath=\\testtaris\Taris\WI100.exe

Tags (1)
0 Likes
1 Solution

Accepted Solutions
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Winform application setup

Jump to solution

I believe that you had opened up a support incident for this behavior and it had been resolved by setting the system PATH to include the bin folder on the network share. Is this correct?

View solution in original post

0 Likes
7 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Winform application setup

Jump to solution

I am assuming that by "ping from the workstation" you mean "run from the workstation".

The most likely cause is that the workstation either does not have all the prerequisite software installed, or the prerequisites are at the wrong version. Ensure the correct versions of Visual COBOL (or COBOL Server) and the .NET Framework are installed on the workstation.

If the server and workstation are running different versions of Windows, that could also be an issue.

There are other possible causes, but we don't have much information here to diagnose the problem. You have at least two third-party products injecting code into the application (McAfee and Imprivata); either could be the root cause. There may be other dependencies that aren't immediately obvious.

0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Winform application setup

Jump to solution

We do not install cobol server on windows  workstation, its installed on windows 2012 server and configured to work on network share mode.

Our old visual cobol dialog application works but doesn't work for new winform application developed using visual cobol 2.3

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Winform application setup

Jump to solution

I'm not sure that's a supported configuration, but to be honest that's really not my area. I suspect you'll have to wait until next week when more MF employees are in the office.

Raising a Support Incident through your Customer Care representative would probably be a good idea.

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Winform application setup

Jump to solution

In order to run a .NET application from a network server there is additional setup required due to how assemblies are located and the trust issues involved.

Take a look at the KB article here:

0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Winform application setup

Jump to solution

I did copy all the files located in  "C:\Program Files (x86)\Micro Focus\COBOL Server\redist\v4.0" to my application folder.

All my programs with doesn't require ODBC conneection works good when executed from windows 2012 server(cobol server installed) and across network (cobol server not installed).

Only programs making ODBC calls seems to fail with this error.

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

RE: Winform application setup

Jump to solution

I believe that you had opened up a support incident for this behavior and it had been resolved by setting the system PATH to include the bin folder on the network share. Is this correct?

View solution in original post

0 Likes
Highlighted
Absent Member.
Absent Member.

RE: Winform application setup

Jump to solution

Yes, that's correct. Thanks for your help.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.