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 Server Agent.

SQL Server 2000 sp3 on Windows 2003. I am getting the
following error in the sql server agent log and I am not
able to run any of my jobs. sql server lightweight pooling
setting is set to 0.
[298] SQLServer Error: 18452, Login failed for
user '(null)'. Reason: Not associated with a trusted SQL
Server connection. [SQLSTATE 28000]
Thanks in Advance.
I have gotten this sometime when I use windows logins as the owner of a job.
I think it has something to do with our domain controller being unavailable
sometimes. When error occurs I have changed the owner to a sql server login
and the problems goes away.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Obaid" <anonymous@.discussions.microsoft.com> wrote in message
news:5fb401c42dff$58db8b70$a601280a@.phx.gbl...
> SQL Server 2000 sp3 on Windows 2003. I am getting the
> following error in the sql server agent log and I am not
> able to run any of my jobs. sql server lightweight pooling
> setting is set to 0.
> [298] SQLServer Error: 18452, Login failed for
> user '(null)'. Reason: Not associated with a trusted SQL
> Server connection. [SQLSTATE 28000]
> Thanks in Advance.
|||If you server is in Mixed Mode set the owner of the job to be SA instead of the creater. Otherwise set the owner to be the same Network ID that SQLServer is running as.
Jeff Duncan
MCDBA, MCSE+I
sql

Problem with SQL Server Agent.

SQL Server 2000 sp3 on Windows 2003. I am getting the
following error in the sql server agent log and I am not
able to run any of my jobs. sql server lightweight pooling
setting is set to 0.
[298] SQLServer Error: 18452, Login failed for
user '(null)'. Reason: Not associated with a trusted SQL
Server connection. [SQLSTATE 28000]
Thanks in Advance.I have gotten this sometime when I use windows logins as the owner of a job.
I think it has something to do with our domain controller being unavailable
sometimes. When error occurs I have changed the owner to a sql server login
and the problems goes away.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Obaid" <anonymous@.discussions.microsoft.com> wrote in message
news:5fb401c42dff$58db8b70$a601280a@.phx.gbl...
> SQL Server 2000 sp3 on Windows 2003. I am getting the
> following error in the sql server agent log and I am not
> able to run any of my jobs. sql server lightweight pooling
> setting is set to 0.
> [298] SQLServer Error: 18452, Login failed for
> user '(null)'. Reason: Not associated with a trusted SQL
> Server connection. [SQLSTATE 28000]
> Thanks in Advance.|||If you server is in Mixed Mode set the owner of the job to be SA instead of the creater. Otherwise set the owner to be the same Network ID that SQLServer is running as
Jeff Dunca
MCDBA, MCSE+I

Problem with SQL Server Agent.

SQL Server 2000 sp3 on Windows 2003. I am getting the
following error in the sql server agent log and I am not
able to run any of my jobs. sql server lightweight pooling
setting is set to 0.
[298] SQLServer Error: 18452, Login failed for
user '(null)'. Reason: Not associated with a trusted SQL
Server connection. [SQLSTATE 28000]
Thanks in Advance.I have gotten this sometime when I use windows logins as the owner of a job.
I think it has something to do with our domain controller being unavailable
sometimes. When error occurs I have changed the owner to a sql server login
and the problems goes away.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Obaid" <anonymous@.discussions.microsoft.com> wrote in message
news:5fb401c42dff$58db8b70$a601280a@.phx.gbl...
> SQL Server 2000 sp3 on Windows 2003. I am getting the
> following error in the sql server agent log and I am not
> able to run any of my jobs. sql server lightweight pooling
> setting is set to 0.
> [298] SQLServer Error: 18452, Login failed for
> user '(null)'. Reason: Not associated with a trusted SQL
> Server connection. [SQLSTATE 28000]
> Thanks in Advance.|||If you server is in Mixed Mode set the owner of the job to be SA instead of
the creater. Otherwise set the owner to be the same Network ID that SQLSer
ver is running as.
Jeff Duncan
MCDBA, MCSE+I

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.
>