July 23, 2008 at 7:06 am
We use SQL server 2000. We have a DTS and a scheduled job to run this DTS nightly. It's to retrieve records from DB1 and insert into a table in DB2. It's been working great until two days ago. Our network people implemented "force change password" policy on staff logins. Since then, the job fails every night, but it's still working if running the DTS along.
The DB2 is inside the domain; I don't even know if this is relevant. Here is the job error message --
Executed as user: NASW\JGrimes. DTSRun: Loading... DTSRun: Executing... DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1 DTSRun OnError: DTSStep_DTSExecuteSQLTask_1, Error = -2147467259 (80004005) 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 Error Detail Records: 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 DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1 DTSRun: Package execution complete. Process Exit Code 1. The step failed.
Please help!!
July 23, 2008 at 8:34 am
tc (7/23/2008)
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 Error Detail Records: Error: -2147467259 (80004005); Provider Error: 17 (11) Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.Please help!!
There is the issue. Password changes have been enforced. Did the account that is running the SQL Server Agent have a password change or is it now set to expired due to the new policy or disabled due to a high number of failed logins? That would be the place to start. Do both DB1 and DB2 reside on the same server? Do they reside on the server where the DTS package is executing from?
-- You can't be late until you show up.
July 23, 2008 at 9:00 am
The password for the account used by SQL Server Agent was already changed, on the server machine (windows) and on SQL server Enterprise.
DB1 and DB2 are on separate servers, different boxes. We do "link servers" on DB1, linking to DB2, and visa versa. It's been like this since forever and never had problem. And both DTS and Job are set on DB1/Server1.
Thanks
July 23, 2008 at 9:25 am
Can you log onto the DB2 server using the account from the SQL server agent on DB1?
-- You can't be late until you show up.
July 23, 2008 at 9:37 am
DB2 has to be logged in as Administrator in order for something to run.
anyway, we changed the password "again" on the DB1 SQL Server Agent and somehow it works now.
Thanks Terry for the help!! 🙂
July 23, 2008 at 9:47 am
Glad you worked it out. Sometimes the most obvious solutions are the ones that'll bite the hardest. Now, about those network admins changing policies on you......:rolleyes:
-- You can't be late until you show up.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply