By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,843 Members | 2,311 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,843 IT Pros & Developers. It's quick & easy.

LoadFromSQLServer failed

ashsa
P: 45
Hi

We have a job scheduled every morning 03:00 which has been running for years without any issue. However, it failed today saying in the log that LoadFromSQLServer failed. The work of the job is to call a stored procedure via isql which in turn executes a set of dts packages to load data from file to the db. I tried executing the individual dts via spExecuteDTS and the same result.
When I tried executing these dts individually from enterprise manager, they ran fine without any problem. The login credentials used were the same as in the scheduled job. Any clue where the problem is ?

I have to ensure that the overnight update does not fail tomorrow.
Thanks in advance..
Sep 16 '08 #1
Share this Question
Share on Google+
3 Replies


iburyak
Expert 100+
P: 1,017
Did you try running stored procedure alone from query analyzer?
Sep 16 '08 #2

ashsa
P: 45
Did you try running stored procedure alone from query analyzer?
stored procedure alone from query analyzer worked..

However when a dts was executed through an sp_executeDTS(), it failed.
Apparently it turned out to be a problem with the buffer cache on the server and the issue was gone after restarting the server..

Its still strange .. isnt it ??
Sep 22 '08 #3

iburyak
Expert 100+
P: 1,017
stored procedure alone from query analyzer worked..

However when a dts was executed through an sp_executeDTS(), it failed.
Apparently it turned out to be a problem with the buffer cache on the server and the issue was gone after restarting the server..

Its still strange .. isnt it ??
One of my servers has unrelated problem and we noticed that it resolves a problem with server reboot. We found that solution requires significant expanse which we were not ready for, basically we need to replace existing server. So identifying a problem led to solution. Now, we reboot server on schedule once a week which gives us a breathing room and time to schedule nonemergency server replacement.

Thanks for respond.
Good Luck.
Sep 22 '08 #4

Post your reply

Sign in to post your reply or Sign up for a free account.