EDN Admin
Well-known member
Hello,
In order to diagnose stability issues with our software, we have reduced the problem by building an application that loads/unloads infinitly a native C++ dll (rebased) through a network share. After a while (sometimes 5 minutes, sometimes 15 jours), the
LoadLibrary fails with the error 999: ERROR_SWAPERROR: Error performing inpage operation. Im suspecting a problem with the network share or network latency is causing LoadLibrary to fail. Our original problem consists of great instability with our software
when it is ran on a Terminal Server with its files (executable, dll, etc.) accessed through a network share. The software crashes, with no recognizable pattern, with an EXCEPTION_IN_PAGE_ERROR. Procmon simply informs us of a "Network Error". Wireshark informs
us that no network requests to the file server are done when the application crashes...very strange. If we copy the files locally, on the Terminal Server, all runs well. Since we do not have any control on how the paging of the dll is done, we tried to simulate
it through infinite calls to LoadLibrary. Are both problems related? Anyone with any ideas?
The Terminal Server is as follows: Item Value OS Name Microsoft Windows Server 2008 Standard Version 6.0.6002 Service Pack 2 Build 6002 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name TSM-NB-OS66 System
Manufacturer HP System Model ProLiant BL460c G1 System Type x64-based PC Processor Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2332 Mhz, 4 Core(s), 4 Logical Processor(s) Processor Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2332 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date HP I15, 10.07.2009 SMBIOS Version 2.4 Windows Directory C:Windows System Directory C:Windowssystem32 Boot Device DeviceHarddiskVolume1 Locale Norge Hardware Abstraction Layer Version = "6.0.6002.18005" User Name NSB-BILadministrator
Time Zone W. Europe Standard Time Installed Physical Memory (RAM) 32,0 GB Total Physical Memory 32,0 GB Available Physical Memory 27,6 GB Total Virtual Memory 48,1 GB Available Virtual Memory 44,5 GB Page File Space 17,1 GB Page File Cagefile.sys
The file server is as follows: OS Name Microsoft Windows Server 2008 R2 Standard Version 6.1.7600 Build 7600 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name NSBBILFIL1 System Manufacturer HP System Model ProLiant
DL380 G6 System Type x64-based PC Processor Intel(R) Xeon(R) CPU E5504 @ 2.00GHz, 2000 Mhz, 4 Core(s), 4 Logical Processor(s) Processor Intel(R) Xeon(R) CPU E5504 @ 2.00GHz, 2000 Mhz, 4 Core(s), 4 Logical Processor(s) BIOS Version/Date HP P62, 30.03.2010 SMBIOS
Version 2.6 Windows Directory C:Windows System Directory C:Windowssystem32 Boot Device DeviceHarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "6.1.7600.16385" User Name Not Available Time Zone W. Europe Standard Time Installed
Physical Memory (RAM) 8,00 GB Total Physical Memory 7,99 GB Available Physical Memory 5,09 GB Total Virtual Memory 16,0 GB Available Virtual Memory 13,1 GB Page File Space 7,99 GB Page File Cagefile.sys
Thanks in advance,
David Fabi
<
David Fabi Director, Technologies GIRO Inc. 75 Port-Royal East, Office 500 MontrÃal, QuÃbec, Canada H3L 3T1 www.giro.
View the full article
In order to diagnose stability issues with our software, we have reduced the problem by building an application that loads/unloads infinitly a native C++ dll (rebased) through a network share. After a while (sometimes 5 minutes, sometimes 15 jours), the
LoadLibrary fails with the error 999: ERROR_SWAPERROR: Error performing inpage operation. Im suspecting a problem with the network share or network latency is causing LoadLibrary to fail. Our original problem consists of great instability with our software
when it is ran on a Terminal Server with its files (executable, dll, etc.) accessed through a network share. The software crashes, with no recognizable pattern, with an EXCEPTION_IN_PAGE_ERROR. Procmon simply informs us of a "Network Error". Wireshark informs
us that no network requests to the file server are done when the application crashes...very strange. If we copy the files locally, on the Terminal Server, all runs well. Since we do not have any control on how the paging of the dll is done, we tried to simulate
it through infinite calls to LoadLibrary. Are both problems related? Anyone with any ideas?
The Terminal Server is as follows: Item Value OS Name Microsoft Windows Server 2008 Standard Version 6.0.6002 Service Pack 2 Build 6002 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name TSM-NB-OS66 System
Manufacturer HP System Model ProLiant BL460c G1 System Type x64-based PC Processor Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2332 Mhz, 4 Core(s), 4 Logical Processor(s) Processor Intel(R) Xeon(R) CPU E5410 @ 2.33GHz, 2332 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date HP I15, 10.07.2009 SMBIOS Version 2.4 Windows Directory C:Windows System Directory C:Windowssystem32 Boot Device DeviceHarddiskVolume1 Locale Norge Hardware Abstraction Layer Version = "6.0.6002.18005" User Name NSB-BILadministrator
Time Zone W. Europe Standard Time Installed Physical Memory (RAM) 32,0 GB Total Physical Memory 32,0 GB Available Physical Memory 27,6 GB Total Virtual Memory 48,1 GB Available Virtual Memory 44,5 GB Page File Space 17,1 GB Page File Cagefile.sys
The file server is as follows: OS Name Microsoft Windows Server 2008 R2 Standard Version 6.1.7600 Build 7600 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name NSBBILFIL1 System Manufacturer HP System Model ProLiant
DL380 G6 System Type x64-based PC Processor Intel(R) Xeon(R) CPU E5504 @ 2.00GHz, 2000 Mhz, 4 Core(s), 4 Logical Processor(s) Processor Intel(R) Xeon(R) CPU E5504 @ 2.00GHz, 2000 Mhz, 4 Core(s), 4 Logical Processor(s) BIOS Version/Date HP P62, 30.03.2010 SMBIOS
Version 2.6 Windows Directory C:Windows System Directory C:Windowssystem32 Boot Device DeviceHarddiskVolume1 Locale United States Hardware Abstraction Layer Version = "6.1.7600.16385" User Name Not Available Time Zone W. Europe Standard Time Installed
Physical Memory (RAM) 8,00 GB Total Physical Memory 7,99 GB Available Physical Memory 5,09 GB Total Virtual Memory 16,0 GB Available Virtual Memory 13,1 GB Page File Space 7,99 GB Page File Cagefile.sys
Thanks in advance,
David Fabi
<
David Fabi Director, Technologies GIRO Inc. 75 Port-Royal East, Office 500 MontrÃal, QuÃbec, Canada H3L 3T1 www.giro.
View the full article