Job fails after system IP Change

I have a job that runs a local package on my sql server. My server does
not have a static IP currently, but has had the same IP from my provider
for over 6 months. Recently my IP finally changed and my SQL job
started failing immediatly after. My job owner is setup as my local
Windows user account. I tried changing the owner to get the job working
again to no avail. Then I recreated the job and the job worked fine.
My question is, what ties the job to the old IP when the original job is
created? Is there a way around this?
--MB
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!What kind of error did you have ?
And what is the steps this job is performing ?
I mean what particularly performing local package ?
Regards
---
All information provided above AS IS.
"Michael Baker" <michael_baker@.advantexmail.net> wrote in message
news:uckAcr7oDHA.2588@.tk2msftngp13.phx.gbl...
> I have a job that runs a local package on my sql server. My server does
> not have a static IP currently, but has had the same IP from my provider
> for over 6 months. Recently my IP finally changed and my SQL job
> started failing immediatly after. My job owner is setup as my local
> Windows user account. I tried changing the owner to get the job working
> again to no avail. Then I recreated the job and the job worked fine.
> My question is, what ties the job to the old IP when the original job is
> created? Is there a way around this?
> --MB
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!|||Here is the error from the Job history:
Executed as user: HOME\SYSTEM. DTSRun: Loading... Error:
-2147467259 (80004005); Provider Error: 17 (11) Error string:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access denied. Error source: Microsoft OLE DB Provider for SQL
Server Help file: Help context: 0. Process Exit Code 1.
The step failed.
There is just one step to perform, so it failed on the first step.
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!