The issue seems to be a mismatch with the ScreenOS proxy-id configuration versus the Cisco ACL setup. This kb walks through how to identify where to look based on the details of the message.
https://kb.juniper.net/InfoCenter/index?page=content&id=KB9517
Basically the remote and local subnets configured in the Cisco ACL need to match the subnets in ScreenOS.
In policy vpn those are in the security policy you setup under
Policy > Policies
The ones you have selected to be associated with this vpn
In route vpn these are setup as proxy-id on the ike object
vpns > AutoKey IKE
Select proxy-id next to your phase 2 entry