I'm getting this error too on a new machine that we've just started using. Tried resetting the maps and checked permissions on the local Recorder folders. The other thread mentioned doesn't help because it tackles the "Beyond System Limits." error.

Charlie, did you ever get to the bottom of this one?

How did you delete all your maps? Was it via the Recorder UI, or did you simply delete the files present in the filesystem?

Thanks Charlie. I've just done that and it worked. Glad we don't keep anything important in those maps....

I'm being bitten by this again, only this time someone has set up a map they don't want to lose, so I'm stuck.

Does anyone know a non-destructive solution to this problem? I currently can't use the Report Wizard because of it.

As a start it is worth looking at the Mapping section of the Network Installation Guide.  If there are corrupt polygon layers you can remove these, without affecting anything. However, once  a polygon layer is corrupt though there is nothing you can do to recover it.

Just run into this. Did anyone come up with a workaround/solution?

Any chance of  sending me the file that is causing the problem. Finding ways of making the mapping more stable is something I would like to look at if we get funding for next year.

At the moment it seems that once the default polygon layer is corrupt then there isn'' t anything that can be done about it apart from resetting the map. One problem with new installation may be that the users does not have sufficient permission to write  to the object sheet folder of R6. This causes the database to be updated, but not the underlying map file.  This then causes an error when the layer is next accessed. One way to test this is to create a new polygon layer then close Recorder. If the layer isn't there (or is listed, but can't be selected) when Recorder is opened again then there is a permissions problem.   

One thing which can be done to reduce problems is never to us the Default Polygon,  but create  new polygon layer(s) for all work.  Also when importing a new file,  first test  it by adding it to a new  polygon layer created for the purpose .  This way you will be able to delete the problem layers without having to reset the map.