Veeam ONE: No Collection Data within Monitor, or Collection Stops Updating.

KB ID: 1484
Product: Veeam ONE | 6.0 | 6.5 | 7.0 | 8.0 | 9.0 | 9.5 | 10 | 11
Published: 2012-01-18
Last Modified: 2022-02-03
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

Data collection stops within Veeam ONE Monitor, or there is no longer any new data from a certain point. 

Cause

This is due to the following database error involving lack of space in the primary file group for the database (.mdf file).  Here is a snippet from the Monitor Logs that you will see in the "VeeamDCS.log" or "VeeamDCS.number.log" where number is a generated number for separating the log files.

Inform  0x0BC0 alarms        "A database error (code:0x80040E14, ) has occured in context of { ? = CALL sp_triggered_alarm_save;1 (?, ?, ?, ?, ?, ?, ?) }. Error information follows"
Inform  0x0BC0 alarms        "Error record 1 of 1: Could not allocate space for object 'dbo.HistoryTriggAlarm' in database 'VeeamMonitor' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."
Inform  0x0BC0 alarms        "Throwing exception."
Error   0x0BC0 alarms        "IDispatch error #3092 (Source: Microsoft SQL Native Client, Description: Could not allocate space for object 'dbo.HistoryTriggAlarm' in database 'VeeamMonitor' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)"

Solution

The issue is usually caused by the SQL Server Express edition which limits the database size to 10GBs. For more information: https://www.veeam.com/kb2357

More information

Contact Veeam Technical support if any assistance is required.
Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.