Click here to Skip to main content
13,347,168 members (49,390 online)
Click here to Skip to main content
Add your own
alternative version

Tagged as


Posted 23 Jan 2013

'Unable to connect to the remote server' Error with Azure Table Storage

, 23 Jan 2013
Rate this:
Please Sign up or sign in to vote.
Azure's storage functionality error solved.

I have been playing around with Microsoft Azure. I was interested because one of my current development projects has a shoestring budget (read no budget). Microsoft Azure will allow for the hosting costs to increase with the site's success.

So it was time to have a go at using Azure's storage functionality to store the data for the site. To this end, I downloaded a couple of storage demonstrations to see how it works. With Azure being a beta and a fair new technology, looking at demos is often the best way of learning it. These demonstrations were Windows Azure Walkthrough: Simple Table Storage and Windows Azure Blog Source Code from PDC.

Both exhibited the same problem; and threw the following error

System.Data.Services.Client.DataServiceClientException: System.Net.WebException: Unable to connect to 
the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the 
target machine actively refused it      
 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)       
 at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)       
 at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, 
 Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, 
 Int32 timeout, Exception& exception)       
 --- End of inner exception stack trace ---       
 at System.Net.HttpWebRequest.GetRequestStream()       
 at System.Data.Services.Client.DataServiceContext.SaveAsyncResult.BeginNextChange(Boolean replaceOnUpdate)

The answer appears in the comments of the latter post. It turned out that the Table Service for the solution was not running. To check its status when running the Azure solution, two icons appear in the system tray labelled. It is the development storage we are interested in. To prevent this error, simply start the Table Service.


I found that once this had been started once, the error (so far) has not re-occurred, even with other projects.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Paul S. Chapman
Software Developer (Senior) Simplicita Online
United Kingdom United Kingdom
UK based IT Consultant. Started in 1985 selling home computers such as the Sinclair ZX Spectrum, BBC Model B and Commodore 64, and in 1987 moved into development, starting first with Torch Computers, developing software for the XXX UNIX Workstation.

Currently developing a new Azure/Silverlight based website/desktop applications for a new startup, hoping to launch in late 2009/early 2010

You may also be interested in...


Comments and Discussions

-- There are no messages in this forum --
Permalink | Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.180111.1 | Last Updated 23 Jan 2013
Article Copyright 2013 by Paul S. Chapman
Everything else Copyright © CodeProject, 1999-2018
Layout: fixed | fluid