Remote Desktop Session host: connecting impossible due to "The transaction log for database 'RDCms' is full "

Hi experts.

Our terminalserver 2012 R2 stopped to accept new connections. Active connections remained active at the same time.
Nothing was changed but I found this in the application eventlog (event occurs at the same time the problem started):
Event ID 9002
"The transaction log for database 'RDCms' is full due to 'CHECKPOINT'."
Source: MSSQL$MICROSOFT##WID

What should that mean? The files that the WID uses are in C:\Windows\rdcbDb and are less than 200 MB of size. Connecting to \\.\pipe\MICROSOFT##WID\tsql\query in SLQ management studio 2012, I can verify that the maximum size is 2 TB, so why do 200 MB pose a problem?

I overcame the problem by exchanging these files in C:\Windows\rdcbDb against backup copies, (200 kb smaller) but the problem might return.
LVL 63
McKnifeAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dan McFaddenSystems EngineerCommented:
That means that the transaction log associated with the database RDCms has reach its configured max limit.  You need to do a full backup of the database and/or increase the limits for the transaction log.

*** not trying to be sacastic ***

What has a max size of 2TB?  Can you post a screen cap of the file properties of the database?

Also, right click on the database in SSMS, select reports then click disk usage, post that too please.

Dan
McKnifeAuthor Commented:
Hi.
There's your screenshot:
ScreenshotI saw that thread on Technet but it is not useful since the "solution" was not described, he just mounted the DB and it started working again.

Also: why would I need to do anything like full backups on that DB, this should not be needed, never heard of it and I have been administering Terminal servers for almost 15 years.
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

Dan McFaddenSystems EngineerCommented:
Can't say anything about TS, but when a db complains that a transaction log is full, its usually because there is something limiting its growth (config or available disk) and to clear it, you need to take a backup thru SSMS, this allows the transactions in the log to be permanently flushed and saved to the db file.

Dan
McKnifeAuthor Commented:
"there is something limiting its growth (config or available disk)" - but there is no such limit configured, nor is the disk anywhere next to full. I don't know what to think, I mean, I can set that DB to autoshrink and such and back it up once but will this permanently help? What is the reason I would need to do it at all?

Imagine, that log is logging logons to our TS. Worldwide there will be millions of TS' that are being used much heavier than ours, but I never saw anyone having to deal with this.
McKnifeAuthor Commented:
By the way, trying to back it up fails:
--
TITLE: Microsoft SQL Server Management Studio
------------------------------

Backup failed for Server '\\.\pipe\MICROSOFT##WID\tsql\query'.  (Microsoft.SqlServer.SmoExtended)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.3000.0+((SQL11_PCU_Main).121019-1325+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Backup+Server&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

Failed to flush the commit table to disk in dbid 5 due to error 2601. Check the errorlog for more information. (Microsoft SQL Server, Error: 3999)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2100&EvtSrc=MSSQLServer&EvtID=3999&LinkId=20476

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
McKnifeAuthor Commented:
I am giving up on this as it seems the file was just corrupted and no logic behind this error.
I restored it from backup more than 2 weeks ago and it has grown over the size that windows was complaining about the last time but this time without problems.
Thanks for participating.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.