When the PVS server receives UDP packets on its Streaming Login port, which do not contain expected PVS headers, the PVS StreamProcess will log event ID 204 with a message "CSSInitialContact::DispatchPacket received invalid opcode" followed by some hexadecimal characters.
The hexadecimal characters are derived from the UDP payload.
To investigate further the Hexadecimal can be decoded to printable ASCII to help with investigation.
Example Hexadecimal string: 6C6C6548

Network traces can be captured and viewed in Wireshark, with filters then applied to display only the packets containing this Hexadecimal:

The above two steps should enable PVS administrators to identify the source of the packets which result in the event ID 204 messages.
Non PVS packets arriving on the PVS login ports will cause PVS to generate these events.
PVS Login port monitoring is not possible via simple third-party network check, and attempting to do so by sending UDP packets to the PVS login port will result in these events being generated.
In a customer case, it was identified that a network monitoring program was incorrectly attempting to monitor PVS UDP login ports.
Removing the network monitoring program configuration to check PVS login ports eliminated the events.
A Citrix Provisioning (PVS) server may repeatedly log Event ID 204 messages ,in the application Event Log. similar to:
