What can cause an "unknown command received" or "parse format error"?

AMPS reports messages an 02-0030 message when it receives data on a Transport that does not match the format of the protocol configured for the Transport. At trace level, AMPS will also log information in a 12-0000 message.

The two most common reasons that this occurs are:

• An application that uses an AMPS client is using a different protocol for the transport than AMPS expects.

  For example, if the Transport is configured to use the amps protocol, the following connection string works:

  tcp://\<amps server\>:\<port\>/amps

  While this connection string, which uses the legacy nvfix protocol, produces unknown command received and parse format error messages:

  tcp://\<amps server\>:\<port\>/nvfix

• Another application is attempting to connect to AMPS. For example, if someone uses a web browser to connect to an AMPS Transport (rather than the Admin URL). AMPS will attempt to determine what protocol the application is using (for example, HTTP or telnet) and log that information to help in troubleshooting.

If an AMPS application is connecting using the wrong protocol, you can either update the client connection string to use the correct protocol, or update the Transport configuration to change the protocol for that Transport.