Recipient name becomes <unknown sender>

Our SQL Server was moved to a new domain. A stored procedure that emails ou
t
with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
Outlook w/o the sender name in "From" column like it used to. In its place
now is <unknown sender>.
Please help.
Gracias
LaEsmeraldaLaEsmeralda wrote:
> Our SQL Server was moved to a new domain. A stored procedure that emails
out
> with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
> Outlook w/o the sender name in "From" column like it used to. In its pla
ce
> now is <unknown sender>.
> Please help.
> Gracias
> LaEsmeralda
What name would you usually see in the from field? It sounds like it's
more of an Outlook problem than it's a SQL server problem. When you send
out emails from Outlook, it will use your Exchange server to resolve the
name into what ever name is in the Global Addresse Book. SInce you've
moved your SQL server to a new domain, it could be that Outlook isn't
able to resolve the name. What happens if you open Outlook on the SQL
server (with the profile that are used for sending out emails) and then
send an email from there. Will you then get the correct name in the
"from" field?
Regards
Steen|||Outlook works normally.
"Steen Persson (DK)" wrote:

> LaEsmeralda wrote:
> What name would you usually see in the from field? It sounds like it's
> more of an Outlook problem than it's a SQL server problem. When you send
> out emails from Outlook, it will use your Exchange server to resolve the
> name into what ever name is in the Global Addresse Book. SInce you've
> moved your SQL server to a new domain, it could be that Outlook isn't
> able to resolve the name. What happens if you open Outlook on the SQL
> server (with the profile that are used for sending out emails) and then
> send an email from there. Will you then get the correct name in the
> "from" field?
> Regards
> Steen
>

Recipient name becomes <unknown sender>

Our SQL Server was moved to a new domain. A stored procedure that emails out
with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
Outlook w/o the sender name in "From" column like it used to. In its place
now is <unknown sender>.
Please help.
Gracias
LaEsmeraldaLaEsmeralda wrote:
> Our SQL Server was moved to a new domain. A stored procedure that emails out
> with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
> Outlook w/o the sender name in "From" column like it used to. In its place
> now is <unknown sender>.
> Please help.
> Gracias
> LaEsmeralda
What name would you usually see in the from field? It sounds like it's
more of an Outlook problem than it's a SQL server problem. When you send
out emails from Outlook, it will use your Exchange server to resolve the
name into what ever name is in the Global Addresse Book. SInce you've
moved your SQL server to a new domain, it could be that Outlook isn't
able to resolve the name. What happens if you open Outlook on the SQL
server (with the profile that are used for sending out emails) and then
send an email from there. Will you then get the correct name in the
"from" field?
Regards
Steen|||Outlook works normally.
"Steen Persson (DK)" wrote:
> LaEsmeralda wrote:
> > Our SQL Server was moved to a new domain. A stored procedure that emails out
> > with sender's address as [@.v_from = 'abc@.abc.com'] suddenly appears in
> > Outlook w/o the sender name in "From" column like it used to. In its place
> > now is <unknown sender>.
> > Please help.
> > Gracias
> > LaEsmeralda
> What name would you usually see in the from field? It sounds like it's
> more of an Outlook problem than it's a SQL server problem. When you send
> out emails from Outlook, it will use your Exchange server to resolve the
> name into what ever name is in the Global Addresse Book. SInce you've
> moved your SQL server to a new domain, it could be that Outlook isn't
> able to resolve the name. What happens if you open Outlook on the SQL
> server (with the profile that are used for sending out emails) and then
> send an email from there. Will you then get the correct name in the
> "from" field?
> Regards
> Steen
>

Receiving "Error: 18456" when for a specific user who has rights via AD Group

I have a user who is a domain admin and has rights based on a group
policy (OURDOMAIN\Developers) to access the SQL Server. He can access
other Sql Servers, and every other member of the group can access all
boxes. So its a case of a specific users cannot access a specific
box. Below is the error message he is getting:
TITLE: Connect to Server
--
Cannot connect to SQLDEV1.
--
ADDITIONAL INFORMATION:
Login failed for user 'OURDOMAIN\user'. (Microsoft SQL Server, Error:
18456)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
--
BUTTONS:
OK
--
SQL2005 Ent SP1 on Win03
Any ideas would be appreciated.Hi
"Keeper of the Bits" wrote:
> I have a user who is a domain admin and has rights based on a group
> policy (OURDOMAIN\Developers) to access the SQL Server. He can access
> other Sql Servers, and every other member of the group can access all
> boxes. So its a case of a specific users cannot access a specific
> box. Below is the error message he is getting:
>
> TITLE: Connect to Server
> --
> Cannot connect to SQLDEV1.
> --
> ADDITIONAL INFORMATION:
> Login failed for user 'OURDOMAIN\user'. (Microsoft SQL Server, Error:
> 18456)
> For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
>
> SQL2005 Ent SP1 on Win03
> Any ideas would be appreciated.
>
Maybe you are seeing http://support.microsoft.com/kb/925744/en-us I believe
3152 is the latest version you can download if you want to move past SP2.
John|||You can more details about login failures from the SQL
Server error log on SQL Server 2005. Check the log for the
State - there will be a line similar to:
Logon Error: 18456, Severity: 14, State:18
Then check the corresponding description for that state in
the following article:
http://msdn2.microsoft.com/en-us/library/ms366351.aspx
-Sue
On 13 Apr 2007 12:06:22 -0700, "Keeper of the Bits"
<styree@.creditsolutions.com> wrote:
>I have a user who is a domain admin and has rights based on a group
>policy (OURDOMAIN\Developers) to access the SQL Server. He can access
>other Sql Servers, and every other member of the group can access all
>boxes. So its a case of a specific users cannot access a specific
>box. Below is the error message he is getting:
>
>TITLE: Connect to Server
>--
>Cannot connect to SQLDEV1.
>--
>ADDITIONAL INFORMATION:
>Login failed for user 'OURDOMAIN\user'. (Microsoft SQL Server, Error:
>18456)
>For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
>--
>BUTTONS:
>OK
>--
>
>
>SQL2005 Ent SP1 on Win03
>Any ideas would be appreciated.