Non-port forwarding VIPs and port-forwarding VIPs to the same destination address are mutually exclusive!
Think of a non-port forwarding VIP as forwarding ALL ports, including the single port you already have defined in a port-forwarding VIP. Imagine traffic arriving for that destination port - which VIP should then respond?
This is ambiguous and as such not allowed.
@George:
just define one VIP for each port you want to expose to the public interface (I'm assuming that is what you meant). To facilitate the policy, group those VIPs into a VIP group and use that as the destination address in the policy.
Pretty straight forward and easy.