Error: External Exception C0000006
| Related Pages |
| Related Categories |
Contents
Scope of the Problem
The Microsoft Windows error "External Exception: C0000006" is displayed when using Newton by Agency systems.
This may also manifest itself in a “C00000C4 Application Crash” in the Windows Event Viewer Application tree.
Standard Client / Server Setup
Agency Systems is accessed through what is called a mapped network drive. This allows the application and data to be run and stored on a centralized server. If the connection is dropped you will either receive a 3000 Level Pervasive Error, or the c0000006.
Terminal Server Setup
Microsoft Terminal Server connections pose some differences due to the fact that multiple people login to the same server. For the Terminal Server to keep track of network resources, it uses what is called the SMB (Server Message Block) redirector, and FCB (File Control Block). The Microsoft Windows Server 2008 platform included a change from SMB 1.0 to 2.0 which started to cause the c0000006 exception error.
Agency Systems worked directly with Microsoft’s Escalation Engineers to identify the problem, reproduce the problem, and test workarounds. Microsoft has acknowledged the issue and their current position is that this will not be fixed due to the complexity of the code involved.
The issue does not occur in the Microsoft Windows Server 2003 platform.
Resolution: Standard Client / Server Setup
Agency Systems is a shared program that is located on your office's network. Due to this, our application is dependent on the network infrastructure that the program resides on. A c0000006 is a generic Microsoft Windows message that is returned when the application cannot access the shared network resource any longer.
This could be something as simple as the server reboot when the user was still in the system, or a power fluctuation. It could also be a sign of larger network issues.
Please see our Installation Environment and Network Requirements for additional details to optimize your network.
Resolution: Terminal Server Setup
The current workaround for this item is to run the Agency Systems programs from a local directory.
Separate Terminal and Data Server
If the Data server and Terminal Server are not the same machine, the \empire\programs\ directory will need to be loaded on the Terminal Server local disk.
This requires a special setup configuration provided by Agency Systems support.
Server List: \\SERVER-DATA \\SERVER-TS Data Shares: \\SERVER-DATA\APPS\ Terminal Server Disk List C: (Operating System) S: (Mapped Network drive \\SERVER-DATA\APPS\)
Original Data and Program Files Directory for Terminal Server Users
Original Data Directory for Terminal Server Users S:\empire\data\ Original Program Files Directory for Terminal Server Users S:\empire\programs\nempmain.exe
New Data and Program Files Directory for Terminal Server Users
New Data Directory for Terminal Server Users S:\empire\data\ New install Program Files Server for Terminal Server Users C:\empire\programs\nempmain.exe
This setup is typical for offices with mixed TS and Local users with existing client server infrastructure. This would allow the administrator to still use the stand-alone server for data storage, and allows LAN users to continue accessing the application entirely through the standard mapped network drive.
Parts of the application and data will be spanned across multiple servers that need to be considered for backups.
If the Data server and Terminal Server are the same machine, move the Agency Systems installation to the root of a second shared dedicated partition.
Disk List: C: (Operating System) D: (Second Data Disk/Partition) Data Shares: C:\APPS\ D:\ Original install physical path: C:\APPS\empire\programs\nempmain.exe New install physical path: D:\empire\programs\nempmain.exe
This allows for a standard Agency Systems setup and would requires little modification. This setup is typical for offices that are purchasing a new server with enough resources to handle the Terminal Server and application server in one.
