none
No connection could be made because the target machine actively refused it 168.63.113.48:443

    Question

  • Hi,

    We are running a cloud service, that read and write data in the Azure Storage (Tables & Blobs).

    This week-end, we had the following error, when trying to read some data from a Table:

    Exception Message = No connection could be made because the target machine actively refused it 168.63.113.48:443

    The stack is the following:

    System
    Exception.StackTrace =    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)
       at System.Net.HttpWebRequest.GetResponse()
       at Aspectize.AzureStorage.REST.RestHelpers.SendRequest(AccountInfo account, Uri uri, String httpMethod, Object body)

    ...

    We don't understand where this problem comes from:

    - the application works well most of the times

    - we didn't change anything in the code neither in the configuration

    - this bug happened about 20 times last week-end (between Friday 14/11 and Sunday 16/11)


    Thanks for any help,

    Regards

    Monday, November 18, 2013 6:16 PM

All replies

  • Hi Nicolas,

    Thanks for posting!

    I apologize for this large inconvenience. From the DashBoard (http://www.windowsazure.com/en-us/support/service-dashboard/) , Azure compute has maintained.

    I guess it may bring this error to your project.

    If I am misunderstanding, please let me know.

    Thanks

    Regards,

    Will


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, November 19, 2013 5:30 AM
    Moderator
  • Hi Will,

    Thank you for your reply, the reporting is mentionning issues on the 18th.

    We had the bug on the 15th, 16th, and 17th.

    I guess it's the same issue but how could we be sure ?

    do you know if we could have more info ? and what about the IP adress 168.63.113.48 ? 

    Regards,

    Tuesday, November 19, 2013 10:03 AM
  • Hi Nicolas,

    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Best Regards,

    Will


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, November 25, 2013 7:10 AM
    Moderator
  • Do you have your storage analytics logs turned on? It would provide more information on the error? can you share that logs?
    Tuesday, November 26, 2013 5:45 PM
  • No, storage analytics are not turned on...
    Friday, December 06, 2013 10:51 AM
  • Hello,

    I had the same error this night and this morning:

    12/6/2013 10:59:22 PM  Exception Message = No connection could be made because the target machine actively refused it 168.63.113.48:443 

    12/6/2013 11:14:33 PM Exception Message = No connection could be made because the target machine actively refused it 168.63.113.48:443 

    12/7/2013 6:37:48 AM Exception Message = No connection could be made because the target machine actively refused it 168.63.113.48:443 

    12/7/2013 7:39:50 AM Exception Message = No connection could be made because the target machine actively refused it 168.63.113.48:443 

    I activate the storage log... but it's very difficult to go further with such incomprehensible and unpredictible errors.

    Have you any kind of explanation of such errors ?

    thanks to your help, 

    Saturday, December 07, 2013 8:11 AM
  • It's very strange the IP adress is the same, where as it is not the same storage as the previous ones...
    Saturday, December 07, 2013 8:12 AM
  • Can you provide you email so I can send u a package to upload the storage logs?

    Wednesday, December 11, 2013 4:06 PM
  • Hello,

    My email is nicolas.roux@aspectize.com

    The problem occured also last night at 01:52:29 am

    Thanks for your help

    Sunday, December 15, 2013 1:23 PM
  • Hello, 

    The problems occured again last night, on different storage:

    16/12/2013 17:15:12

    16/12/2013 17:15:23

    12/16/2013 5:15:13 PM

    12/16/2013 8:49:15 PM

    12/16/2013 9:46:00 PM12/16/2013 11:32:31 PM

    (time are in different format, it happens on different servers and storage)

    Thanks for your help,

    Tuesday, December 17, 2013 8:22 AM
  • I have 2 other occurrence of the problem:

    12/17/2013 3:00:27 PM

    12/17/2013 3:49:38 PM

    don't know if it helps...

    Tuesday, December 17, 2013 4:14 PM