Yes, the db owner is the appropriate account (the same name annotated in the logs where AR Server states that it cannot connect to the database as this individual).
I'm curious as to whether or not the problem is the result of connecting to a new SQL 2005 server whereas our old method was connecting to a 2005 server that was upgraded from 2000. Further, because passwords are masked all over the place, I cannot be certain that the password for this database owner is the same as it was previously. We use the same password for pretty much everything in our development environment. Is there anywhere (either config files or Windows Registry) where I can check: - The name of the account ARS is attempting to use to connect to SQL - The password being used for said account - The SQL client/drivers being used to connect - etc. I've checked various *.cfg files in \CONF\ to no avail. Thanks, Ben _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
