SQL Log expansion vs Post Cost to G/L Batch

Dear all, I sometime back posted here about failure to complete the Post Cost to G/L Batch Job. Basically, the batch job runs endlessly. Funny here, that hapenns when it reaches a specific item. I was able to find useful help from all you guys, and thanks. However, I after some struggle managed to get the hotfixes up to 23, and applied them. Incidentally, the batch job has still failed to finish. I suspect that it could have something to do with the Transaction Log files size of 7110 and the file growth of only 1% that the client has set. Does anyone have experience with this kind of thing in an SQL server environment? I appreciate the assistancem, Robert