Post reply

SSIS Package Error

  • August 20, 2014 at 6:56 am

    #397226

    Hi All,

    I received an error from my ETL package last night. This package has run for a little over a month with no issues and this morning I got the following error messages:

    Error: The buffer manager cannot write 4 bytes to file "C:\Users\dwsqlsrv\AppData\Local\Temp\2\DTS{3AA5B6D2-65B8-4056-BFD2-B19175E6F77C}.tmp". There was insufficient disk space or quota.

    Information: The buffer manager failed a memory allocation call for 10485760 bytes, but was unable to swap out any buffers to relieve memory pressure. 1 buffers were considered and 0 were locked. Either not enough memory is available to the pipeline because not enough are installed, other processes were using it, or too many buffers are locked.

    I have tried researching this issue online but I have not come across anything that provides a viable solution. Anyone have a suggestion of what is causing this issue? I have more than enough available space in my C: drive and I have set my database log files to auto growth. (Suggestion from other posts)

    Please let me know if you have any ideas.

    Thanks

  • August 20, 2014 at 7:25 am

    #1739564

    Is it possible that the error message means what it says?

    "There was insufficient disk space or quota."

  • August 20, 2014 at 7:27 am

    #1739566

    I have 65 GB of free space. This data flow that is failing is very small in cache size and used to complete in roughly 30 secs.

  • August 20, 2014 at 7:30 am

    #1739569

    What about RAM?

    Thanks

  • August 20, 2014 at 7:40 am

    #1739576

    I have 16 GB of RAM installed on this server with 4GB available. Also, there are no other users on this server. I run only SQL Server and SSIS here.

  • August 21, 2014 at 8:00 am

    #1739901

    So I don't really know what is actually being fixed, but by rebooting the server, the ETL process now runs successfully when I run it manually and when run as part of the nightly scheduler. Perhaps there is a hung process or other programs running that are absorbing the resources?

    Any other thoughts as to how rebooting a server fixes this issue? I have seen many postings about this error, but with no resolutions.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Cookies on SQLServerCentral

This website stores cookies on your computer.

These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.

To find out more about the cookies we use, see our Privacy Policy