Unable to truncate Microsoft SQL Server

[Erwin Linker]

Hi,

From one day to the next we have som issues with truncating SQL logging from one server: Veeam gives me the following error:

2-1-2019 23:36:31 :: Unable to truncate Microsoft SQL Server transaction logs. Details: Failed to call RPC function 'Vss.TruncateSqlLogs': Error code: 0x80004005. Failed to invoke func [TruncateSqlLogs]: Unspecified error. Failed to process 'TruncateSQLLog' command. CoInitialize() failed. HRESULT=0x80070008.

We i look in de guesthelper log i see the following:
2-1-2019 23:36:29 9808 Using default SQL provider 'sqloledb' to connect to SQL server
2-1-2019 23:36:29 9808 WARN Code = 0x80070008
2-1-2019 23:36:29 9808 WARN Code meaning = Not enough storage is available to process this command.
2-1-2019 23:36:29 9808 WARN Source =
2-1-2019 23:36:29 9808 WARN Description =
2-1-2019 23:36:29 9808 WARN COM error: Code: 0x80070008
2-1-2019 23:36:29 9808 WARN Instance 'SQLEXPRESS' connection problem: Code = 0x80070008
2-1-2019 23:36:29 9808 WARN Code meaning = Not enough storage is available to process this command.
2-1-2019 23:36:29 9808 WARN Source =
2-1-2019 23:36:29 9808 WARN Description =
2-1-2019 23:36:29 9808 WARN
2-1-2019 23:36:29 9808 WARN COM error: Code: 0x80070008.

On the server SQL Express is installed, anybody got a idea?

[Mike Resseler]

Hey Erwin,

How much memory does that SQL Express server have? That warning usually means you are out of memory on the box to perform the truncation (The not enough storage is available is a MSFT error code and falsely makes you think there is a disk storage issue)

Mike

[Erwin Linker]

Hi Mike,

The server has 8 GB memory where around 7 GB is in use. I will plan a restart of the server for 23:00 the backups normale starts around 23:30.

Thanks for the answer.

Erwin

[Andreas Neufert]

Hi Erwin,

thanks for sending this.
Based on search this issue is related to Memory or Pagefile.

Microsoft suggest here:
https://msdn.microsoft.com/en-us/library/ms837395.aspx
"Do one of the following, then retry the command: (1) reduce the number of running programs; (2) remove unwanted files from the disk the paging file is on and restart the system; (3) check the paging file disk for an I/O error; or (4) install additional memory in your system."

As well Microsoft mentions some other changes:
https://support.microsoft.com/en-us/hel ... ess-this-c

Another Application vendor said that it can happen when their application run on Express edition because of the 1GB memory limitation. They suggested to reboot the server, to back it up when the SQL server is not under load (no other user use it) or to upgrade to standard edition.

I would look into memory consumtion and pagefile placement. Maybe a disk is full ?
If it is a VM maybe adding more memory will help? But express edition is I think limited to 1GB Memory usage, maybe this is the bottleneck here.

Maybe Microsoft Support can help to identify the issue/bottleneck.

[Erwin Linker]

Hi,

A reboot of the machine solved the problem.

Thx for the response

[Andreas Neufert]

Thanks for the feedback. Potentially this issue will come again if the Application uses a lot of RAM intesive SQLinteractions and the 1GB RAM will become the bottleneck again.

Please monitor and if it happens regulary take actions according to the below mentioned tips.

Thanks.