RE: Custom Archives - SOWeb
Hi James,
You seem to have two separte issues here.
The first, dealing with SetOrderBy is quite straight forward. If you have created your own archive provider (by inheriting from IArchiveProvider), then you are responsible for accepting the arguments passed into SetOrderBy and determine how best to construct your query(ies) and process the results based on the array of ArchiveOrderByInfo.
The second, dealing with tangled persisted archive control configuration is tricky.
Two things:
- Don't reuse the same names (gui, context, subcontext, etc) as you are essentially hijacking the other archive controls and messing with their state. It's even mentioned in the docs... Don't do that. ;-)

- These column configurations are persisted in the database. This is mentioned in the docs I referenced earlier:

What's not mentioned in the docs however is that if/when you do change these keys, you have to either update the offending row in the SuperListColumnSize table, or simple purge all rows in that table with your associate ID. When building these myself, I tended to do the latter.
This should correct your sign-in issue. If not, you're going to need to provide more logging details than "throwing a DCF error..." :-)
Hope this helps!