You can create a maintenance plan on the SQL server  to shrink db automatically  on a schedule.

Make sure backup is run daily as the transaction log  will keep filling up until a back of the log is issued

You have a few options


You can change the recovery model of your databases (I,.e from full  to simple)



If you do this you will loose the ability to do point  in time recovery on that database because to you don’t have any transaction log  backups

or

Configure your maintence plans to backup & shirnk the transaction logs , this should sort your problem out

You can also use this syntax to truncate sql  logs

DBCC ShrinkFile (Database_name, 2)

BACKUP LOG Database_name WITH TRUNCATE_ONLY

I went with your 2nd option last night of shrinking the logs and problem is resolved. Attached link  is a great article on how to shrink the logs for any of you interested in learning more to prevent this problem.
http://www.banmanpro.com/support/filegroupfull.asp