how can i call service from a ssl enabled website to a WCF service with basicHTTPBinding.
i am getting the error
The requested service, 'http://10.5.1.111/HRMSService/VehicleMaintenance/VehicleMaintenance.svc/test' could not be activated. See the server's diagnostic trace logs for more information.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ServiceModel.ServiceActivationException: The requested service, 'http://10.5.1.111/HRMSService/VehicleMaintenance/VehicleMaintenance.svc/test' could not be activated. See the server's diagnostic trace logs for more information.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using
Have you defined the correct bindings in Web.config?
Related
I have a client connecting to third part WCF Service (I have access to the web.config or service but not code).
The Third Party throws a SOAP Exception because the faulting assembly isn't marked as serializable - "Type Assembly not marked as serializable".
Is there anyway I can get the underlying exception detail that was thrown and not faulted on the WCF Service via configuration edit or other means?
You need to enable includeExceptionDetailInFaults in your web.config file.
Please check this.
I am getting the below error while trying to call an external service from my service which was hosted in IIS .
Error : An error occurred while receiving the HTTP response to ''. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
And I am not getting any error while trying to call the same external service from a console application.
Any suggestions will help. Thanks in advance.
Issue is with the firewall. When i try to call the external service from console application, the service call going through without any errors, as there was no IIS involved in calling the service. But when i call the external service from another service hosted in IIS, firewall comes to the picture.
i am getting this error " An error occurred while receiving the HTTP response to http://xxxxxx/CustomerService/. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details."
and i cannot proceed further.
How can i resolve this issue and i checked with the Service Logs also and Service Trace viewer also but i didn't understand
Why/When this is happened?
I am migrating a WPF application to Silverlight. My WPF application accesses a Web Service using BackgroundWorker. If there is any error while accessing the web service I get an extensive error message in my callback, for example
There was no endpoint listening at http://localhost:8080/services/registration
that could accept the message. This is often caused by an incorrect address or
SOAP action. See InnerException, if present, for more details.
In my Silverlight application, I am accessing the same web service asynchronously and now my error messages are not very useful, for example:
The remote server returned an error: NotFound.
The web service has not changed - I can see the faults coming from the server on Fiddler. So the question is how can I get more detailed error messages on the Silverlight client.
My callback in Silverlight application looks like this (I am accessing the error message from e.Error.Message):
private void AuthenticateUserCallback(object sender, AuthenticateUserCompletedEventArgs e)
{
if (e.Error != null)
{
this.StatusMessage = e.Error.Message;
}
...
}
This is limitation with Browser stack due to which SL cannot access the complete exception message. Look at MSDN article here
The approach is to wrap exception into meaningful faults (which means client will always get HTTP OK 200) and perform custom exception handling on the client side.
I have written a mvc that uses nservicebus to publish messages. This works fine under Cassini.
When trying to use IIS, I receive an error message when I call Create() to create the Bus.
Access to Message Queuing system is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Messaging.MessageQueueException: Access to Message Queuing system is denied.
I have set the anonymous access user on the IIS virtual directory to be my own domain account, which is a member of the administrators group on the local machine. I have granted this same user full permissions on the queue, as well as NETWORK SERVICE and ASPNET.
Any help with this problem will be greatly appreciated!
Solution was to delete the queues.
I tried using the FormatName in the MsmqTransportConfig section of my web.config, as recommended in Permissions error accessing MSMQ from ASP .Net Web Service. That did not work.
Deleting the queues did.