Transaction log error

whats the initial file size set to ? 450MB per chance?
the problem with autogrowth is that even if you do 10% and you're writing to it heavily, when you have a small file, with a small autogrowth and a lot of items being written, you're constantly performing an autogrow.

Also what backup are you using to back up the database? is it doing the truncation of the file before the shrink?

Initial Size if 503 MB

Growth 10%.

Restrict: 2GB

I am using SQL Maintenance jobs to backup the DB.

Backup occurs at 12:00AM (Daily)

Shring job runs at 1:00 AM (weekly)

sounds like you're running a database backup but you're not backing up and truncating the log files

Log Transaction backup occurs rightafter the DB backup.

Shring DB runs every Sunday Morning at 1:00AM.

I also ran ShrinbDB  without success.

here's a really good article for you http://www.symantec.com/docs/TECH74666

follow these steps and you should be good!

That's the article I used to set it up initially:)

give this a shot:

USE EvServer01ExchMVS01_1;
GO
SELECT file_id, name
FROM sys.database_files;
GO
DBCC SHRINKFILE (1, TRUNCATEONLY);

it returns:

However,  DBCC SQLPERF(logspace) still shows

I changed the DB to Simple from Full and it dropped down, Any issues with me using Simple versus Full?

simple mode doesnt allow for point in time recover, hense the trans logs got wiped out when you set it to simple. full mode writes all the transactions (changes) to the logs before being commited to the database. in the event you need to restore from backup, you can restore your full database from the last time you backed it up and play forward all the log files you want to get it back to a specific point in time.