1) The user you define in the ODBC connection on the machine running EmerAuth
ought to be a very privileged user. It SHOULD not harm you to make this
user "sa". (It took making it "sa" to get it to go on my end).
2) The user you define in the EAADMN.EXE program should NOT be "sa" -- it
should be a member of the EmeraldApps group. You will likely have to
create a NEW user in Emerald and make it a member of EmeraldApps.
Afterwards, verify that this user was created in SQL using Enterprise Mgr.
3) The "license load" issue is due to an omission in Emerald 2.5's early
upgrades -- not sure if it is corrected in the current version (Dale?).
The "EmeraldApps" Group does NOT have "Select" permission on the
Table "Liscenses" (sic -- yes, it is misspelled in Emerald), and thus
may be unable to verify your license. You will have to add this
permission using SQL E.M.
If these don't work, I'll have more details forthcoming when I sit down to
write "EmerAuth for Dummies" on Sunday or Monday.
At 10:34 AM 6/12/99 -0400, you wrote:
>.
> >
> > Grab the EmerAuth3.zip as well. It has updates to the DLL.
> >
>Ok.
>Ran 'EA Admin' from the Programs section off the start button
>and I could connect to the database using either of two ODBC
>connections. Everything seemed to work with the newest
>DLL (6/11/99) but when I look into the log I get
>(see below) when I stop and start on of the services.
>I have tried both with and without domain name. And am using the
>username/password that works on all machines. This is the same
>username/password combo that I am using on all 3 machines
>in SQL Enterprise Manager to register the server. (I have
>removed all 'Use Trusted Connection' on all three machines
>just in case)
>I have checked the local users, in the 'user manager for domain',
>of the mail machines and the user name does not appear so
>it is not picking up the wrong user. This would also be the
>case then I put the domain name in front of the user
>name. But I was trying everything.
>
>So what do I check next?????
>
>
>Jun 12 10:05:37 1999 DllMain Thread attach
>Jun 12 10:05:43 1999 VerifyUser Load License Failure
>Jun 12 10:13:40 1999 VerifyUser Load License Failure
>Jun 12 10:15:54 1999 VerifyUser Load License Failure
>Jun 12 10:17:34 1999 VerifyUser Load License Failure
>Jun 12 10:22:57 1999 DllMain Process detach
>Jun 12 10:22:57 1999 EmerSupp Close Shutting Down
>Jun 12 10:23:02 1999 EmerSupp::ReOpen -----------------------------------
>Jun 12 10:23:02 1999 EmerSupp::ReOpen Entering function
>Jun 12 10:23:02 1999 EmerSupp::ReOpen Registry ODBCDataSource read
>Jun 12 10:23:02 1999 EmerSupp::ReOpen Registry UserName read
>Jun 12 10:23:02 1999 EmerSupp::ReOpen Registry Password read
>Jun 12 10:23:02 1999 EmerSupp::ReOpen Registry ESID read
>Jun 12 10:23:02 1999 EmerSupp::ReOpen Initalizing Database Connections
>Jun 12 10:23:03 1999 EmerSupp License [Microsoft]
>[ODBC SQL Server Driver][SQL Server]Login failed- User: _ Reason:
>Not defined as a valid user of a trusted SQL Server connection.
>
> [Select DISTINCT Company, LiscenseID From Liscenses]
>Jun 12 10:23:03 1999 DllMain New process attach
>Jun 12 10:23:03 1999 GetConfig Select Type, Value, Data From Configs
>Where ConfigID = 61
>Jun 12 10:23:03 1999 GetConfig [Microsoft]
>[ODBC SQL Server Driver][SQL Server]Login failed- User: _ Reason:
>Not defined as a valid user of a trusted SQL Server connection.
>
> [Select Type, Value, Data From Configs Where ConfigID = 61]
>Jun 12 10:23:03 1999 DllMain Thread attach
> (48 dups. deleted to save space)
>Jun 12 10:23:03 1999 DllMain Thread attach
>Jun 12 10:24:00 1999 VerifyUser Load License Failure
>Jun 12 10:25:44 1999 VerifyUser Load License Failure