- Veeam Support Knowledge Base
- Veeam ONE: No Collection Data within Monitor, or Collection Stops Updating.
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 | 12 | 12.1 | 12.2 | 12.3 | 13 | 13.1 |
| Published: | 2012-01-18 |
| Last Modified: | 2025-04-10 |
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
Oops! Something went wrong.
Please, try again later.
Challenge
Cause
This is due to the following database error involving a 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 a record number is generated 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 Microsoft SQL Server Express 10GB database size limitation.
For more information: https://www.veeam.com/kb2357
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.