I think there may some confusion here between the database transaction
logs, and the SQL Server error
You can shrink the transaction logs, but as far as I know you can only limit the number
of error logs maintained by the system. A new error log is created every time SQL Server starts, and the logs are eventually 'recycled'.
You might want to look at the reasons why your error logs are so big - if they are big it either means there are lots of errors in them, or you haven't restarted SQL Server in a long
Custom Apps, Inc.