It looks like the way the old IOS dealt with certain lines of your ACLs has changed from one version to the next.
I would remove each one, one at a time, and re-add them back in. Make sure to remove them from any access-groups on interfaces that may be in use or you may lock yourself out, or run each ACL add/delete as a script so that each can complete if it does isolate you from the device.
Example:
A file you apply as:
copy tftp://192.168.0.123/acltest1.txt running-config
and the file will look like this inside (but with the lines you are wanting to use):
no ip access-list extended MY_ACL
ip access-list extended MY_ACL
permit ip host 192.168.0.112 192.168.0.0 0.0.255.255
permit ip host 192.168.0.113 192.168.0.0 0.0.255.255
deny ip any any log-input
!
end
Make sure you use something like Notepad++ that will let you set the EOL to a Unix style.
It should let you see which ACL the current IOS has an issue with and then remove or review them until you can find the line that is causing the error.
I get those on purpose when I apply a baseline script written to work on a couple of different IOSes, the older ones fail on the lines they don't know how to import and the newer ones just complain that you have already set it by displaying that error. I expect it to error on each but for different reasons but it lets me maintain one baseline script instead of 5 so I'm fine with it.
ip access-list extended MY_ACL
permit ip 192.168.1.0 0.0.0.255 192.168.0.0 0.0.0.255
permit ip 192.168.0.0 0.0.0.255 192.168.1.0 0.0.0.255
deny udp any any eq 3544 log-input
deny udp any any eq 3544 log
deny udp any eq 3544 any log-input
deny udp any eq 3544 any log
deny ip any any log-input
deny ip any any log
The above will do it every time. (as it should :) )
