{"id":1464,"date":"2012-09-13T10:30:07","date_gmt":"2012-09-12T23:30:07","guid":{"rendered":"http:\/\/support.cybersecure.com\/?p=1464"},"modified":"2012-09-13T10:37:46","modified_gmt":"2012-09-12T23:37:46","slug":"microsoftodbc-sql-server-driversql-serverwrite-on-xxxx-failed-665failed-to-retrieve-text-for-this-error-reason-15105","status":"publish","type":"post","link":"http:\/\/support.cybersecure.com\/?p=1464","title":{"rendered":"[Microsoft][ODBC SQL Server Driver][SQL Server]Write on “XXXX” failed: 665(failed to retrieve text for this error. Reason: 15105)"},"content":{"rendered":"

Error<\/h2>\n

[Microsoft][ODBC SQL Server Driver][SQL Server]Write on “XXXX” failed: 665(failed to retrieve text for this error. Reason: 15105)<\/span><\/p>\n

Cause<\/h2>\n

We’ve found this is caused by a heavily fragmented filesystem on the volume where the spooling folder is located.<\/p>\n

Resolution<\/h2>\n
    \n
  1. Run a Windows defrag operation on the volume where the spooling folder is located.<\/li>\n
  2. Alternatively, pick a different, less fragmented volume to spool the database to.<\/li>\n<\/ol>\n

    References<\/h2>\n