Can't Send mail using MultiServer Admin

Hi,

I have a Master server which I want to use to handle jobs for our Production Servers. the master server has Outlook installed but the Target servers do not. I need to find a way to get the job to send a mail confirming whether the job has succeeded or failed but without having a mail client installed on any of the target servers. Currently the actual backups do run but the send mail section fails with the following error.

xp_sendmail: Procedure expects parameter @.user, which was not supplied. [SQLSTATE 42000] (Error 17985). The step failed.

I can't see any parameter @.User on BOL, it may be that using sendmail is not the best way foward here

Any ideas anyone?

Hi, I had this problem when I migrated my server to new hardware. I had not yet set up the Outlook account which SQL Server uses to send the mail on the new hardware. You have to login to your box with the same account that you use for the SQL Server startup service and create an outlook profile on that account before you can send the mail using xp_sendmail. Hope this helps!|||

Hi Jason,

Thanks for the response, we don't want to install an Outlook client on the target servers which was cauing the problem, I managed to resolve the issue by using smtp instead

Regards

Lisa

|||

how do you set up the smtp on your target server? I'd like to do the same but have not any idea, I am a newbie in both SQL and network. Thanks.

|||Try using http://www.sqldev.net/xp/sp_smtp_sendmail.htm

Can't Send mail using MultiServer Admin

Hi,

I have a Master server which I want to use to handle jobs for our Production Servers. the master server has Outlook installed but the Target servers do not. I need to find a way to get the job to send a mail confirming whether the job has succeeded or failed but without having a mail client installed on any of the target servers. Currently the actual backups do run but the send mail section fails with the following error.

xp_sendmail: Procedure expects parameter @.user, which was not supplied. [SQLSTATE 42000] (Error 17985). The step failed.

I can't see any parameter @.User on BOL, it may be that using sendmail is not the best way foward here

Any ideas anyone?

Hi, I had this problem when I migrated my server to new hardware. I had not yet set up the Outlook account which SQL Server uses to send the mail on the new hardware. You have to login to your box with the same account that you use for the SQL Server startup service and create an outlook profile on that account before you can send the mail using xp_sendmail. Hope this helps!|||

Hi Jason,

Thanks for the response, we don't want to install an Outlook client on the target servers which was cauing the problem, I managed to resolve the issue by using smtp instead

Regards

Lisa

|||

how do you set up the smtp on your target server? I'd like to do the same but have not any idea, I am a newbie in both SQL and network. Thanks.

|||Try using http://www.sqldev.net/xp/sp_smtp_sendmail.htm

Can't Send mail using MultiServer Admin

Hi,

I have a Master server which I want to use to handle jobs for our Production Servers. the master server has Outlook installed but the Target servers do not. I need to find a way to get the job to send a mail confirming whether the job has succeeded or failed but without having a mail client installed on any of the target servers. Currently the actual backups do run but the send mail section fails with the following error.

xp_sendmail: Procedure expects parameter @.user, which was not supplied. [SQLSTATE 42000] (Error 17985). The step failed.

I can't see any parameter @.User on BOL, it may be that using sendmail is not the best way foward here

Any ideas anyone?

Hi, I had this problem when I migrated my server to new hardware. I had not yet set up the Outlook account which SQL Server uses to send the mail on the new hardware. You have to login to your box with the same account that you use for the SQL Server startup service and create an outlook profile on that account before you can send the mail using xp_sendmail. Hope this helps!|||

Hi Jason,

Thanks for the response, we don't want to install an Outlook client on the target servers which was cauing the problem, I managed to resolve the issue by using smtp instead

Regards

Lisa

|||

how do you set up the smtp on your target server? I'd like to do the same but have not any idea, I am a newbie in both SQL and network. Thanks.

|||Try using http://www.sqldev.net/xp/sp_smtp_sendmail.htm

Cant modify or delete an existing job

Folks, i have rebuilt my old server machine and i've restored the MSDB over the new machine. Now when i try to edit or delete any of the jobs that come from the RESTORE; i get the following error message:

I never setup multiserver administration.
However i can create and delete new jobs.
How do i remove these older jobs.

Howdy!This happened to me once, when a machine was renamed. I think it is as simple as updating the sysjobs table to reflect the new server name (originating_server column). Make sure you have a good backup, before you do this, however.|||sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.

Thanx, MCrowley. I would try this when the users are off the machine.

Howdy.|||My experience was the exact same as MCrowley's; I think I went in and hand-edited the jobs in the msdb database (through EM; it was a long time ago). You may need to set the switch to allow updating of system tables, but I don't recall that I had to do that.

Regards,

hmscott

sorry: the error message is:
error 14274: Cannot add, update, or delete a job that originated from anMSX server.

Thanx, MCrowley. I would try this when the users are off the machine.

Howdy.|||i am squared. thanx.

USE MASTER
GO
sp_configure 'allow updates' ,1
GO
RECONFIGURE WITH OVERRIDE
GO
USE MSDB
go
update sysjobs set originating_server='myserver'
GO
USE MASTER
GO
sp_configure 'allow updates' ,0
GO
RECONFIGURE WITH OVERRIDE

--HOWDY!|||Just had the same problem on a rebuilt server - the above script sorted it out.

thanks,
Paul.

can't manully start jobs

The job in SQL server agent won't manully start after installed SP3 for SQL
server 2000. But scheduled jobs are runing fine automatically.
Thanks for any reply.What errors do you get? What is in the SQLAgent.out file in
the Log directory?
-Sue
On Mon, 7 Nov 2005 08:16:15 -0800, new
<new@.discussions.microsoft.com> wrote:

>The job in SQL server agent won't manully start after installed SP3 for SQL
>server 2000. But scheduled jobs are runing fine automatically.
>Thanks for any reply.|||This may be a given, but make sure that the EM registration for this instanc
e
has the proper rights to exe jobs. If you are using Windows Authentication o
n
this registration, then make sure the win login you are using has sa. Some
permission levels allow you to view jobs, but can not execute them.
Thanks,
Rick MCP
"new" wrote:

> The job in SQL server agent won't manully start after installed SP3 for SQ
L
> server 2000. But scheduled jobs are runing fine automatically.
> Thanks for any reply.

can't manully start jobs

The job in SQL server agent won't manully start after installed SP3 for SQL
server 2000. But scheduled jobs are runing fine automatically.
Thanks for any reply.
What errors do you get? What is in the SQLAgent.out file in
the Log directory?
-Sue
On Mon, 7 Nov 2005 08:16:15 -0800, new
<new@.discussions.microsoft.com> wrote:

>The job in SQL server agent won't manully start after installed SP3 for SQL
>server 2000. But scheduled jobs are runing fine automatically.
>Thanks for any reply.
|||This may be a given, but make sure that the EM registration for this instance
has the proper rights to exe jobs. If you are using Windows Authentication on
this registration, then make sure the win login you are using has sa. Some
permission levels allow you to view jobs, but can not execute them.
Thanks,
Rick MCP
"new" wrote:

> The job in SQL server agent won't manully start after installed SP3 for SQL
> server 2000. But scheduled jobs are runing fine automatically.
> Thanks for any reply.

can't manully start jobs

The job in SQL server agent won't manully start after installed SP3 for SQL
server 2000. But scheduled jobs are runing fine automatically.
Thanks for any reply.What errors do you get? What is in the SQLAgent.out file in
the Log directory?
-Sue
On Mon, 7 Nov 2005 08:16:15 -0800, new
<new@.discussions.microsoft.com> wrote:
>The job in SQL server agent won't manully start after installed SP3 for SQL
>server 2000. But scheduled jobs are runing fine automatically.
>Thanks for any reply.|||This may be a given, but make sure that the EM registration for this instance
has the proper rights to exe jobs. If you are using Windows Authentication on
this registration, then make sure the win login you are using has sa. Some
permission levels allow you to view jobs, but can not execute them.
Thanks,
Rick MCP
"new" wrote:
> The job in SQL server agent won't manully start after installed SP3 for SQL
> server 2000. But scheduled jobs are runing fine automatically.
> Thanks for any reply.