This suggests that for running locally (using the Storage Emulator) you don't have to configure anything. Which is not the case. My application returned an Internal Server Error 500 "Error: connect ECONNREFUSED". The reason was that the Storage Emulator
was not running, which in turn, had as reason that I was missing SQL Server on my system. So now I have installed SQL Server 2008 R2 Express edition. Now, the storage emulator runs fine.
Still, I can't create or access Tables. from my NodeJS application. I get an error "Could not use table: InvalidInput". I guess it has to do with access to the SQL server, or non initialized SQL server. But I have no clue how to figure this out. Any ideas?
My NodeJS app itself works fine when deployed to Azure, so this really has to do with the Storage Emulator. I also installed
Azure Storage Explorer, in which I can create tables and entities locally without problem.
Based on my understand, the error "Could not use table: InvalidInput" occurs when you trying to use a operation that not supported by table storage service, i guess you made some mistakes with your code, how do you write Node.js application, try to
post your code to help us to fix your problems.
Sorry to hear you've run into trouble. Are you running your example directly in node.exe, or through the compute emulator? The how-to assumes you first used the PowerShell tools to create a hosted service and a WebRole and that you're running in the emulator.
If you are doing it that way, then you'll notice that the Web.config creates an "EMULATED" environment variable, which enables the azure package to work without specifying storage access settings. It should all work seamlessly.
If you want to try using the azure package directly with node.exe without going through the compute emulator, make sure you manually set the "EMULATED" environment variable.