Please find a transcript of our system report below. Appreciate all feedback. Thank You.
1. Symptoms
2. Window Event Viewer, Captured Event Logs
1) Application Error
* English Translation in Detail
Faulting Application Name: o_server.exe, Verson: 5.60.54.763, Timestamp: 0x52260a1e
Faulting Module Name: MSVCR100.dll, 버전: 10.0.40219.325, Timestamp: 0x4df2be1e
Exception Code: 0xc0000005
Fault Offset: 0x00001ed7
Faulting Process ID: 0x684
Faulting Application Start time: 0x01cfa2504b9e2c10
Faulting Application Path: D:\RBMnet\RBMSuite\Sys\o_server.exe
Faulting Module Path: C:\Windows\system32\MSVCR100.dll
Report ID: 2182c253-0f32-11e4-8bb1-d05099114ad8
2) Windows Error Reporting
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab ID: 0
Problem signature:
P1: o_server.exe
P2: 5.60.54.763
P3: 52260a1e
P4: MSVCR100.dll
P5: 10.0.40219.325
P6: 4df2be1e
P7: c0000005
P8: 00001ed7
P9:
P10:
Attached Files:
C:\Users\CSISERVERS\AppData\Local\Temp\WEREFDA.tmp.appcompat.txt
C:\Users\CSISERVERS\AppData\Local\Temp\WERF2D7.tmp.WERInternalMetadata.xml
C:\Users\CSISERVERS\AppData\Local\Temp\WERF2D8.tmp.hdmp
C:\Users\CSISERVERS\AppData\Local\Temp\WERFCA9.tmp.mdmp
This file is available at.
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_o_server.exe_ceda1d4b76c61a568b1432d47305c951e206b45_cab_15affd13
Anaylsis Symbol:
Rechecking for solution: 0
Report Status: 4
3) Csimtdbmgr
The description for Event ID 2 from source Csimtdbmgr cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event
The following information was included with the event:
thread(3048): [LC1209] Error - MTDBMgr.cpp (-5111) serverHandler() - Connection failed with Dserver-deokso; Value: -5111 network error code: 10054
요소가 없습니다
4) Windows Error Reporting
Attached files:
These files may be available here.
Analysis symbol:
Report Status: 0
5) “CsiO_Server”
The description for Event ID 2 from source CsiO_Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
thread(4672): [LC0059] Informational - GuiThread.cpp (0) Logging thresholds:
'File' @ 'INFORM'
'Application Log' @ 'ERROR'
'Console' @ 'NONE'
3. Recent Status
1) Confirmed that, event log is visible before the communication is broken.
2) When we exit from program (My Application Software) and re-start, then My Application Software is receiving the OPC data, it means that OPC and My Application Software is communicating between them well.
3) This error occurs when the connection between the OPC is not broken, and seems to have the restored together, My Application Software attempts to forcibly reconnect but no response. To get response we must restart the program.
4) Window and program reinstalled, data request time is reconfigured (change the data requested time to longer) but the situation is same
5) Most of time it occur between 10 hours, but we confirmed that this occurs at approximate when it is more than 24 hours.
4. System Information
1) PC : I7 – 4770 CPU, 8GB Ram
2) OS : Windows 7 Professional 64Bit (Korea)
3) MHM version : 5.60
4) CSI 6500 Firmware Version : 3.20d
5) Application Program Tool : LabVIEW 2013
Whenever client/server communications are in question, the first test is to use another client and see if you can reproduce the results. If you cannot, then it might indicate a problem with your client. In the error logs you have presented, the visual C component (MSVCR100.dll) of the client application is throwing the error, again suggesting a client problem.
The network error code 10054 indicates the server is resetting the connection. Have you checked the even log on the server (Dserver-deokso)?
In reply to Youssef.El-Bahtimy:
Thank You for reply.
From recent situation it is a little bit difficult to install a separate client PC to conduct a test, but I will format the PC and reinstall the window to conduct the test
I am trying to take below actions for conducting test, so requesting to guide me regarding this problem and if possible please let me know the solution.
First of all I will reinstall the MSVCR100.dll file.
Regarding Network code 10054, I was able to find the relevant information at below link.
support.microsoft.com/.../en-us
“An application may receive the 10054 error when the application receives data from a connection on a computer that is running Windows 7 or Windows Server 2008 R2 if a TDI filter driver is installed. For example, a TDI filter driver is installed when you install McAfee VirusScan”
Have you ever experience a similar scenario with OPC program (such as TDI filter driver is installed with MHM SW)., if yes then please let me know the solution.
In addition, I would like to know, does OS language make any problem, currently we are conducting test on Korea language OS
Finally, I will try to display the data via OPC Browser to check whether the data is broken, I would like to know does it help me to resolve the problem.
Again Thanks for your reply and hope to get support.
In reply to ASJ:
Sorry, when I said use another client, I meant client software application; you can use the same PC, just a different application. OSI's PI OPC Tool is an excellent test client, but you also try Matrikon OPC explorer, both can be procured easily.
If you've installed DeltaV OPC Remote software on the client PC (you would have to in order to make it talk), make sure you are using the correct version to account for the 64-bit client PC per the follwoing article NK-1300-0140.
www3.emersonprocess.com/.../carticle.asp
The following article NK-1200-0286 describes how OPC DA clients can experience memory leaks causing failure over time. This may describe the symptom you are seeing of failure after 24 hours of run time.