C0000006 External Exception Errors

C0000006 External Exception Errors

C0000006 on Local Area Network:

When receiving this error in a Local Area Network (LAN), it is generally an indication the station is no longer connected to the network and it has lost its connection to the server. It is recommended to troubleshoot the connection by checking cabling, any hub or switch and the Network Interface Card (NIC) on any station with this error. If this is happing on the entire network, the common devices such as the Server's NIC, network cable connecting the server to the switch or the switch could be the cause.

This error could also be caused by any anti-virus/firewall solutions that is not properly configured. Anti-virus solutions that inspect and delay the packet delivery or interrupt packet delivery over the network can be the culprit and cause disconnection from the databases.

We have also seen this error when other software such as RLI is accessed at the same time as Compulink on the same station.

C0000006 on Wireless Devices:

If you are receiving this error using a wireless device, it is generally an indication the station is no longer connected to the wireless network and the wireless signal has been lost. This error is not critical with most applications running locally such as Internet Explorer (Internet) and Microsoft word. Even if your wireless device loses connection for a fraction of a second, Advantage Software will no longer be connected to its source. Boosting the wireless signal may or may not help avoid dead spots in the wireless zone. It is recommended that you use Microsoft Remote Desktop (RDP/Terminal Services) to access your files on the server. Once an RDP session is used to facilitate the connection, if the wireless signal is lost, the Advantage software will continue to run on the server. By reconnecting to the session, the user can continue the database updates without interruption to Advantage software.

For Wide Area Network (WAN) and Terminal Server using Windows 2000 Server, see below.

Terminal Services Shared File Bug Fix
The network redirector mrxsmb.sys creates one data structure per computer for every user that accesses a shared file on a Win2K system. The redirector per-computer data structure causes problems when a Win2K system is configured as a Win2K Server Terminal Services server and multiple Terminal Services clients access the same file. To properly maintain connection information, the redirector needs one data structure for each client session. In the current implementation, when two or more Terminal Services clients open the same file and one of the clients closes the file, the redirector incorrectly closes the connection for all Terminal Services clients. You can find documentation about the unexpected behavior in two Microsoft articles: "Programs Run from Network Share on TS Close or Generate Errors" (http://support.microsoft.com/?kbid=294816) and "PRB: 'Error reading file' Error Message on Windows 2000 Terminal Services" (http://support.microsoft.com/?kbid=299603). Microsoft now has a permanent solution for this problem, which exists in all versions of Win2K through SP4. Call Microsoft Product Support Services (PSS) and ask for the June 4 version of the redirector components mrxsmb.sys and rdbss.sys. These new components have an option you can enable to create data structures on a per-user, rather than a per-computer, basis. On Terminal Services servers, after you install the new redirector, you need to activate the per-user data structure feature by modifying the registry. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRxSmb\Parameters registry subkey, and add the value entry MultiUserEnabled:REG_DWORD: 1 in the right pane. Note that this modification is unnecessary on Win2K systems that aren't configured as Terminal Servers. For more information about this problem and solution, read the Microsoft article "Problems When More Than One User Accesses the Same File Through Terminal Services" (http://support.microsoft.com/?kbid=818528).