Windows Server Client Computer Backup Service Won't Start - One Possible Solution

I'd like to share this for future reference to everyone.

Just yesterday, I noticed that the Backup Status on all my client PCs in the Dashboard has become "Unknown". Reviewing the Event Viewer, two errors kept popping up;

0x26
   unexpected EOF
   X:\ServerFolders\Client Computer Backups\Commit.dat
   Reached the end of the file.

and

 d:\wssg_src\hsbs_colorado\backup\pc\util\diskfile.cpp
   438

When I checked Services, Windows Server Client Computer Backup Service has stopped. Restarting it fails and only resulted in generating the same errors as above.

I wasn't sure about the 2nd error so I just went ahead and dived into the "X:\ServerFolders\Client Computer Backups" folder and looked for "commit.dat". I renamed the file to "commit.dat.bak", and restarted the service. This time it started. I then had to close Dashboard (which still shows the Backup Status to be unknown). When Dashboard restarted, the Backup Status was back to normal for all clients. Whew!

I went back to the Client Computer Backups folder and found that WHS has recreated the commit.dat file. I am not sure as to what triggered this problem. The closest explanation I could surmise would be due to low disk space on where the client backup folder resides. It currently has 93GB of space left.

So there. I hope all WHS problems were this easy to fix.