>> ODBC 3.0 is installed on the new machine.
>> Both a system and user DSN are set up for Emerald (case sensitive).
>You should only have one System DSN.
We HAVE to have more -- there's a web server running Cold Fusion into
Access databases on this machine, and it requires an Access System DSN for
that. There have to be MULTIPLE system DSN's on this machine, for various
type of databases.
>> ODBC *is* working, as an Access application via Cold Fusion works.
>How about Access or Cold FUsion to SQL Server via ODBC?
Untested. No need for it at this time, and we have no application that is
ready or able to test such a thing.
>> I have connected to the SQL machine, sharing C$ as an administrator.
>> I have used SQL Ent. Manager to Manage Logins, giving this user both
>> permit and default access to Emerald (but not to master).
>> Serv-U still says it can't load the .DLL. It works on our old server, but
>> not here. Any clues? I'm sure I have mirrored everything, but can't
>> figure out where the hole is....
>Sounds like you might have ODBC problems. What account is serv-u
>running as (system or specified user?).
Specified user (an Administrator) -- we don't run it as a service, we
AutoAdminLogin and run it from the startup Group. It is this Admin that
has an account in the SQL server, and has permissions to the Emerald
database. This is also how it is set up on the NT 3.51 box that is working
now. (This one is NT 4.0).