You should not receive this error due to our components, however for the benefit of your application development, we have included some possible causes for this error below (not necessarily in order of most probable cause). There are a number of reasons why this error may occur when programming a .NET application:

1. The usual reason for this error appearing is due to there being a problem in running out of resources in an application, most likely due to a programming error.
2. If the error is occurring in code you have written, try the usual debugging techniques to reduce your code down until it works etc, isolating the problem areas. Look for possible infinite recursions. The error is known to occur when an infinite loop ends up using up so many resources that this error appears as a 'catch-all'.
3. This error has been known to be related to bad memory modules on a PC. Try swapping out the memory with known good memory modules.
4. The error can sometimes occur due to obfuscation being used that is obfuscating names that should not beobfuscated. Try the application without obfuscation and see if that works.
   
5. This error has been known to occur with older versions of the .NET components on Windows 2003 Server. You need to update your software to the latest version.
6. If you can run the demo applications, but have a problem with the ASP.NET application, then you should examine your IIS settings. Also ensure that all required DLLs are deployed to the applications bin directory.
   Before installation, we recommend backing up existing files and applications. You should also ensure that you keep a copy of your current DLLs etc. Then, quit all relevant applications including Visual Studio, Excel and Access. Uninstall the previous version of the software and then install the new version.

If you receive this error under different conditions, please contact us.