As MS SQL 2000 Analysis Server is the most unusual piece of the puzzle, I'm
curious if anyone else here has resolved a similar issue.

I'm having a strange problem with one user gets a "Database does not exist"
error when accessing an MS SQL 2000 Analysis Server OLAP database from a
read-only Excel 2003 pivottable on a Windows 2003 Standard Terminal Server
using the OLE DB provider for OLAP 8.0. The Terminal Server also has the MS
SQL PivotTable services installed (version unknown). All of the MSOLAP*.dll
files are from 2001 or 2002.

All access to the TS, the spreadsheet, and the OLAP data is through AD groups.

Other users can access the same spreadsheet/OLAP data with no problem.

The problem user can use the spreadsheet from her XP desktop, but company
policy prohibit users from doing that. (Bandwidth constraints mostly, but
non-negotiable in any case)

If we delete her TS roaming profile and she logs back in, she can sometimes
access the spreadsheet properly a time or two, then gets the same error
consistently after that. In fact, none of the Pivottable xls files work for
her, nor can she create a new one, but only on our Terminal servers (we have
4 load balanced TS servers)

I have copied her windows account in AD and using the copy of her account,
everything works fine.

I'd rather not delete her windows account and recreate it, but I'm not
seeing many other alternatives at this point.

Of course, the user is the secretary for owner of the company.

Can anyone point me to something we may be overlooking?