Hi Satish, there is no one single cause for this type of error.
As IamAbhi pointed out, access the Inspection View for the service and see if anything displays that shows an exception.
Access the portal or console depending on the version of DevTest. What is the transaction count for this service? Try removing the service and redeploying. When you redeploy, does the service immediately turn "red" due to an error or does the status show as 'running'?
Some other common problems are:
- The endpoint is accessed using a transport that is not understood. For example, a tcp request hits the endpoint, but the VSM is an HTTP Listen step
- You have multiple services listening on the same endpoint port and the base path is NOT narrow enough to prevent the request from being handed off to more than one service
- Your base path is "/" and your environment has port scanning software that is attempting to breach the service to gain root level access, attempt an HTML or SQL injection, etc.
- Your VSM is throwing an exception (most likely in the Listen Step) due to a custom script or DPH error.
Please provide more details based on what you are able to research.