Skip to main content
Status: Delivered

We are receiving 'SER1005E CMN Invalid TCP/IP protocol header received:' and 'SER8104E CMN Unidentifiable message received, header is' errors
in our Changeman started task due to port scans. However, after discussed with Micro Focus we learned that these messages will not cause any problems and those are working as designed.

Since, these messages are not causing any problems, is it possible for an enhancement to represent these messages as ‘Warning’ instead of ‘Error’?


#Notification
Status: Delivered

We are receiving 'SER1005E CMN Invalid TCP/IP protocol header received:' and 'SER8104E CMN Unidentifiable message received, header is' errors
in our Changeman started task due to port scans. However, after discussed with Micro Focus we learned that these messages will not cause any problems and those are working as designed.

Since, these messages are not causing any problems, is it possible for an enhancement to represent these messages as ‘Warning’ instead of ‘Error’?


#Notification

We will look at this. and get back to you.

Status: Delivered

We are receiving 'SER1005E CMN Invalid TCP/IP protocol header received:' and 'SER8104E CMN Unidentifiable message received, header is' errors
in our Changeman started task due to port scans. However, after discussed with Micro Focus we learned that these messages will not cause any problems and those are working as designed.

Since, these messages are not causing any problems, is it possible for an enhancement to represent these messages as ‘Warning’ instead of ‘Error’?


#Notification

This will be implemented in SerNet 8.3 via CR 222002.

Terms & ConditionsAccessibility statement