Fix Server Error in Application - Unable to read data from the transport connection(ASPX)
Budget: ₹100 – ₹400 INR
We have an old inventory and order management system built for SQL Server using .NET Framework (ASP.NET).
The system is designed to send notification emails to users at different stages of use (e.g. when an order is submitted).
We believe that a recent update to the server is causing the application's email sending function to fail. Attached is an example of the error message received when the user clicks "Finalise Order" (the button that submits the order to the database and prompts the emails to be generated).
These days we do not rely on the email function very much. So our main concern is to stop the Error message from happening.
We need:
1. An investigation to see if the email bug can be easily fixed. If so, then fix it.
2. If not, then we are happy to have the email function disabled and some minor cosmetic changes made to the user interface so that users are not expecting to see emails generated.
3. We may also seek some additional bug fixes and minor updates going forward.
The system was originally developed and maintained by a developer who has recently suffered a health problem. He will not be available to help us with these issues, so we are looking for a developer to support us going forward.
We are also considering creating a new up-to-date version 2.0 of the same system. We expect about 80% of the current functionality to be retained, and the remaining 20% to be replaced with some new features. A spec is being developed and Version 1.0 can be used as a prototype.
The system is designed to send notification emails to users at different stages of use (e.g. when an order is submitted).
We believe that a recent update to the server is causing the application's email sending function to fail. Attached is an example of the error message received when the user clicks "Finalise Order" (the button that submits the order to the database and prompts the emails to be generated).
These days we do not rely on the email function very much. So our main concern is to stop the Error message from happening.
We need:
1. An investigation to see if the email bug can be easily fixed. If so, then fix it.
2. If not, then we are happy to have the email function disabled and some minor cosmetic changes made to the user interface so that users are not expecting to see emails generated.
3. We may also seek some additional bug fixes and minor updates going forward.
The system was originally developed and maintained by a developer who has recently suffered a health problem. He will not be available to help us with these issues, so we are looking for a developer to support us going forward.
We are also considering creating a new up-to-date version 2.0 of the same system. We expect about 80% of the current functionality to be retained, and the remaining 20% to be replaced with some new features. A spec is being developed and Version 1.0 can be used as a prototype.