SYSTEM ERROR WindowWndProc Exception code: C0000006 IN_PAGE_ERROR when using FIMS
  • 27 Jun 2023
  • Contributors
  • Dark
    Light
  • PDF

SYSTEM ERROR WindowWndProc Exception code: C0000006 IN_PAGE_ERROR when using FIMS

  • Dark
    Light
  • PDF

Article summary

When using FIMS, I receive a SYSTEM ERROR, "SYSTEM ERROR WindowWndProc Exception code: C0000006 IN_PAGE_ERROR Fault address: 0FBA30C6 01:003F20C6 N:\dlc\bin\prow32.dll Protrace Generated" and then FIMS shuts down.

 

Steps To Duplicate:
  1. Log into FIMS
  2. Take action in FIMS (switching between modules, records, etc.)
  3. Error message appears (seemingly at random) and FIMS shuts down, losing any unsaved work.
Answer:
This error typically occurs on terminal or remote desktop servers and is typically usually caused by a loss of connection between the workstation and the database server.

To resolve do the following:

1. If using group policy to map the N drive, check the group policy for the N drive mapping and make sure it is set to update rather than replace, then push out that change to the workstations.

2. For terminal and remote desktop servers, it is recommended that they have their own Progress installation so that these types of network issues can be mitigated. If the terminal\remote desktop server has its own Progress installation then it does not have to go across the network for the prowin32 executable, it will run that locally. It will of course still have to go across the network to read\write from the database. Please see the following:
How to upgrade the remote desktop server to Progress 11.7.15

See also the following:
https://knowledgebase.progress.com/articles/Article/P2997

 
3.  The error C0000006 is an indication from windows that an attempt was made to communicate with a network resource that no longer exists. Windows will time out idle connections.

To resolve:

Enter this command on the workstations with this issue, then monitor for a couple days to see if the issue clears up:

> net config server /autodisconnect:-1

This will prevent Windows from disconnecting the drives, so the network resource should stay available to us. This article from Microsoft has some more detail:

Mapped drive is disconnected - Windows Client | Microsoft Learn

This would just be typed at a command prompt on the client machine. It is going to change a system setting that windows uses for drive disconnection. It should hold through a reboot - It changes the following Registry Key on the client:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\autodisconnect . The -1 will be represented by 0xffffffff

Was this article helpful?