Problem With SQL Server Job

Hi,
We have jobs successfully running on the server. Now we moved the server to a different IP address(still the same machine).
I modified the DTS which has been scheduled as a job. In the DTS I modified the server IP address. Now when I ran the job I am getting the error message as " DTSRun: Loading... Error: -2147467259 (80004005); Provider Error: 17 (11) Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
If I run the DTS itself it is working fine. But it is not working as a job.
But if I create a new job with the same DTS, the job runs fine without any error.
I have logged into the machine with my own user account.
Please some advise on this.

ThanksAre you trying to run the encrypted job that DTS created originally? If so, the GUID points to the previous version, not the one you modified. If you change the IP and let DTS create a new job, it should be OK. Or, manually create an uncrypted job with DTSRUN (details are in BOL).|||When you run it it runs under the context of your id, which has authority to right to the drives...

When it's scheduled it runs under the context of the sql server agents account, which does not have rights...

And because you made it an ip...it's leaving and coming back in to itself...and has to authenticate...

Grant the accounts the rights to the drive...|||Yes. I am running the encrypted job. But when I replaced this encrypted string with the new encrypted string (after I created the new job from the modified DTS), the job successfully ran.
If we use DTSRUN we need to provide the username and password in the code which will be seen by other users when they check the properties of the job.
So we are using the encrypted method.
If we want to user the encryption methodology, and if there are 100s of jobs, do we have to recreate each job from the DTS and replaced the encryption string or there is any easier method?
If we use DTSRUN method and if we provide username and password for sa in that string, will it be seen by otherusers when they try to open the job?

Thanks|||Is the SQLAgent a Windows user? If so, use the /E switch for a trusted connection.

Yes, you will have to create a new job for each encrypted string. Or script out one job, gather all the encrypted strings, and mass produce them.|||Does it have to be DTS?

Can't they be sprocs?

Or is it too late?sql

Problem with SQL (Job cannot run, Job status not updated)

Hi All,

I would need your help please.

I just installed a new fresh SQL server under Windows 2000 Advanced server SP 4

1. Firstly i tried to run normal database backup to a folder by select backup database then run manually and it ran very well. Then i tried to run it with schedule as sql backup job to the same folder. After the job was showed in the sql jobs list, i tried to run it manually by clicking start job. When i refresh the screen under the status field it says "executing job step '0 (unknown)" then in about 5 seconds the status turned into "not running". And i cannot find any error in the log and in the last run job status. The SQLSERVERAGENT is running, the strange thing is another job which is only to update the database can run with the scheduler very well.

2. Whenever i run job then after it finished the last run job status is always unknown.

What will be the solution for the conditions above, please help (

Thank you very much in advance

Best Regards

Felix

Just restart the sql server agent and see......may be the agent might have been in hanged state.........but i am not sure about it.....|||

Hi deepak,

Thank you very much

I can only try the solution tomorrow morning, just to make sure.

I have tried to run another jobs which is not backup job by using sqlserveragent as well and its working well.

So with this information perhaps you have other opinition please let me know.

I will let you know how it goes tomorrow morning, wish me luck

many thanks

Felix

sql

Problem with sending email

This is the first time I am setting up an operator so that I can get job
notifications to my email. When I create an operator any type in my address
and click test. It gives me the following error:
Problem occoured while attempting to resolve the address 'my email address'.
Mapi error code number -2147221233
ThanksThe first thing would be to check to ensure that SQL Mail has been setup
correctly as typically the MAPI errors occur as a result of an incorrect
configuration. The KB Article
http://support.microsoft.com/default.aspx?scid=kb;en-us;263556 describes how
to Configure SQL Mail and the KB article
http://support.microsoft.com/kb/315886/EN-US/ details Common SQL Mail
Problems.
- Peter Ward
WARDY IT Solutions
"Amit" wrote:
> This is the first time I am setting up an operator so that I can get job
> notifications to my email. When I create an operator any type in my address
> and click test. It gives me the following error:
> Problem occoured while attempting to resolve the address 'my email address'.
> Mapi error code number -2147221233
> Thanks

Problem with Scheduled Jobs

I have a scheduled T-SQL job that I need to run as a different user than
system. I am running into two problems. 1, no matter who the owner is, the
job still runs as system (the SQL Server Agent User). The 2nd part is that
the "run as" is grayed out, so I can't attempt to set the step to run as a
different user.
How can I solve the problem, without changing the user that hte SQL Server
Agent runs as?
Thanks.
A job will run under the security context of the SQL Agent
service if the job is owned by a sysadmin. If it's not owned
by a sysadmin, it will run under the security context of the
proxy account. So those are your options.
-Sue
On Tue, 13 Sep 2005 09:12:08 -0400, "Kevin Antel"
<kevina@.cqlcorp.com> wrote:

>I have a scheduled T-SQL job that I need to run as a different user than
>system. I am running into two problems. 1, no matter who the owner is, the
>job still runs as system (the SQL Server Agent User). The 2nd part is that
>the "run as" is grayed out, so I can't attempt to set the step to run as a
>different user.
>How can I solve the problem, without changing the user that hte SQL Server
>Agent runs as?
>Thanks.
>

Problem with Scheduled Jobs

I have a scheduled T-SQL job that I need to run as a different user than
system. I am running into two problems. 1, no matter who the owner is, the
job still runs as system (the SQL Server Agent User). The 2nd part is that
the "run as" is grayed out, so I can't attempt to set the step to run as a
different user.
How can I solve the problem, without changing the user that hte SQL Server
Agent runs as?
Thanks.A job will run under the security context of the SQL Agent
service if the job is owned by a sysadmin. If it's not owned
by a sysadmin, it will run under the security context of the
proxy account. So those are your options.
-Sue
On Tue, 13 Sep 2005 09:12:08 -0400, "Kevin Antel"
<kevina@.cqlcorp.com> wrote:
>I have a scheduled T-SQL job that I need to run as a different user than
>system. I am running into two problems. 1, no matter who the owner is, the
>job still runs as system (the SQL Server Agent User). The 2nd part is that
>the "run as" is grayed out, so I can't attempt to set the step to run as a
>different user.
>How can I solve the problem, without changing the user that hte SQL Server
>Agent runs as?
>Thanks.
>

Problem with Scheduled Jobs

I have a scheduled T-SQL job that I need to run as a different user than
system. I am running into two problems. 1, no matter who the owner is, the
job still runs as system (the SQL Server Agent User). The 2nd part is that
the "run as" is grayed out, so I can't attempt to set the step to run as a
different user.
How can I solve the problem, without changing the user that hte SQL Server
Agent runs as?
Thanks.A job will run under the security context of the SQL Agent
service if the job is owned by a sysadmin. If it's not owned
by a sysadmin, it will run under the security context of the
proxy account. So those are your options.
-Sue
On Tue, 13 Sep 2005 09:12:08 -0400, "Kevin Antel"
<kevina@.cqlcorp.com> wrote:

>I have a scheduled T-SQL job that I need to run as a different user than
>system. I am running into two problems. 1, no matter who the owner is, th
e
>job still runs as system (the SQL Server Agent User). The 2nd part is that
>the "run as" is grayed out, so I can't attempt to set the step to run as a
>different user.
>How can I solve the problem, without changing the user that hte SQL Server
>Agent runs as?
>Thanks.
>

Problem with replication job schedule

We have recently setup a snapshot replication on a SQL Server 2000 server.
It's an unusual replication, since it's replicating from one database to
another on the same server (because of the interaction between two 3rd party
applications).
My problem is that when I set the job schedule's "enabled" setting to "yes"
(through the snapshot agent properties under the "schedules" tab) the job
runs at the scheduled time (daily at 11:00 PM) and has a status of
successful, but the "enabled" setting changes to "no" and I have to reset it
to "yes" the next day.
Another orginization that has a similar setup has been using this method for
a few years without a problem, so I assume this should work.
I'm not seeing anything unusual in the logs. Is there anything else that I
can look at to narrow down the problem? Has anyone come across this type of
problem before?
Oh brother. I was about to respond back with:
It is set to "Recurring" with "Occurs every 1day(s), at 11:05:00 PM".
But when I clicked on the "Change" button to examine it more closely I saw
the duration was set to "End Date" of the current date, rather than "No End
Date". Someone else had setup the replication and I assumed it was set up
properly because of what I was seeing on the other screen. I should have
caught that. Thanks for the response. I might not have checked that more
closely for quite a while.
"Paul Ibison" wrote:

> David - is the job set on a recurring schedule. It sounds like it is set on
> a schedule to execue one time only.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
>