Hello all,
I am having a VERY intermittent problem that has been discussed here, but
perhaps not in the context of my experience (or at least I didn't find it),
and the things people are suggesting aren't seeming to resonate with my
problem. I hope you will forgive me if I'm wrong, but allow me to explain....
I have this job in SQL Server 2005 that runs every day from 7 am to 9 am
every 5 minutes. This job has been running for about a year. I'm thinking
its run thousands of times (24X365=8760 times) without a single change, or
problem. Then, since 2/6, we have recieved the following error twice, once
on 2/6 and once on 2/12; but its run 165 or more times perfectly fine between
these two dates.
The package isn't too complicated, it uses Oracle as an ODBC connection to
grab some data, it uses Access for some other data to retrieve, and it
imports a flat text file and writes what it finds from each of these sources
to a SQL Server 2005 table. It also reads some other SQL Server 2005 table
to read from as well.
Here is the error message:
Message
Executed as user: VANCOUVER\cvnt32sqlserveragent. Microsoft (R) SQL Server
Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C)
Microsoft Corp 1984-2005. All rights reserved. Started: 8:05:56 AM Could
not load package "\ACH totals from Direct Debit Run" because of error
0xC0014062. Description: The LoadFromSQLServer method has encountered OLE DB
error code 0x80004005 (Unable to complete login process due to delay in
opening server connection). The SQL statement that was issued has failed.
Source: Started: 8:05:56 AM Finished: 8:06:39 AM Elapsed: 42.969
seconds. The package could not be loaded. The step failed.
There is a proposed fix out there on the net that says that I should do the
following, but me and my server admin are scratching our heads wondering why
this would resolve it.
http://www.sqlservercentral.com/Forums/Topic455318-148-1.aspx
Here is what they said...
The solution recommended was adding this:
127.0.0.1 crl.microsoft.com
to the hosts file on the server.
I asked our network services people if they could do that,
and since it was added, I haven't had any problems with login timeouts (yet).
Can anyone confirm that this will fix it, and if so, can you explain what
its doing to fix it? We don't know what this "127.0.0.1
crl.microsoft.com" would do.
If you don't believe this is the fix, what is the fix?
Thanks,
Keith
FAQ
Search
Profile
Private Messages
Log in
