Thanks for the reply Phil.
All data sources are pointing to the correct DB instance. Since it processes fine in VS I know those connections are good.
The data source impersonation was set to "Default", I changed it to "ImpersonateServiceAccount", but still received the error. The SSAS service account does have access to the datasource.
-Brian
The annoying thing is that I had this error not so long ago ... and, you know how it is, I can't remember how I solved it.
I'll post back if my memory manages to dredge up anything useful.