LoadFromSQLServer failed

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ashsa
    New Member
    • Feb 2007
    • 45

    LoadFromSQLServer failed

    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 LoadFromSQLServ er 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..
  • iburyak
    Recognized Expert Top Contributor
    • Nov 2006
    • 1016

    #2
    Did you try running stored procedure alone from query analyzer?

    Comment

    • ashsa
      New Member
      • Feb 2007
      • 45

      #3
      Originally posted by iburyak
      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 ??

      Comment

      • iburyak
        Recognized Expert Top Contributor
        • Nov 2006
        • 1016

        #4
        Originally posted by ashsa
        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.

        Comment

        Working...