Hi,
We have a one-way trust between two domains, say A and B. B trusts A. Both domains have SQL Servers and both have services accounts from their own domain. The service accounts have the same name and different passwords. (In the old days this was a bad idea, but it worked if the passwords in each domain are the same. But this is not the old days, but perhaps it's still a bad idea?)
Anyway, using my domain A desktop and domain A user account, I can connect using SSMS to the SQL Server in domain B. DDL and DML works as expected. However, if I try to use sp_database_mail with a query, it fails with parameter error of some sort. I normally suspect permissions when I see this. I'm a sysadmin, so I was a little surprised.
If I create a job to run the procedure that uses sp_database_mail, it works fine. About this time we started having issues with domain A production machines. It turned out that my testing in domain B locked the domain A service account. I find it odd that a server in domain B that has no domain A service accounts would try to use a domain A account of the same name. The domain B account would have worked.
I think I'm in a different forest. I see NTLM rather than Kerberos being used.
Is our environment not configured correctly? Use a proxy account even if it is the same as the SQL Service account? Change the service account names in domain B?
Thanks
Randy in Marin