asked on 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):
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\ts
I overcame the problem by exchanging these files in C:\Windows\rdcbDb against backup copies, (200 kb smaller) but the problem might return.
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\ts
I overcame the problem by exchanging these files in C:\Windows\rdcbDb against backup copies, (200 kb smaller) but the problem might return.
Windows Server 2012Databases
Last Comment
McKnife
ASKER
Hi.
There's your screenshot:
![Screenshot]()
I 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.
There's your screenshot:
I 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.
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
Dan
ASKER
"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.
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.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
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.
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.
*** 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