Azure Stream Analytics作业测试失败（发送时出错）

Hey there, let's work through fixing this send error you're hitting while following the Azure Stream Analytics tutorial. Since you're new to Event Hubs and Stream Analytics, I'll break down the most common pitfalls and easy checks you can do to get things working.

First, Fix Your Configuration File (Most Likely Culprit!) #

From what you described, there's a common mix-up in the telcodatagen.exe.config settings that's probably causing this:

• EventHubName value: You said you put your Event Hubs Namespace here—but this should be the specific Event Hub instance name you created inside the namespace, not the namespace itself. For example, if your namespace is my-eventhub-ns and your Event Hub is my-telco-eventhub, the line should be:

  <add key="EventHubName" value="my-telco-eventhub"/>
  

• Connection String: Double-check that you're using the connection string from the shared access policy you created, and that you removed the EntityPath parameter from the end. A valid connection string should look like this (no ;EntityPath=xxx):

  Endpoint=sb://your-namespace.servicebus.windows.net/;SharedAccessKeyName=your-policy-name;SharedAccessKey=your-primary-key-value
  

Verify Your Shared Access Policy Has Send Permissions #

Even if you created the policy, it might not have the right permissions to send data:

• Go to your Event Hub namespace in the Azure portal.
• Under Settings, select Shared access policies.
• Click on the policy you used for the app.
• Make sure the Send checkbox is checked. If not, enable it, save changes, and update your config file with the policy's connection string if needed.

Check if Network Restrictions Are Blocking You #

If your Event Hub namespace has network restrictions turned on, your local machine might be blocked:

• In the Azure portal, go to your Event Hub namespace.
• Under Settings, select Networking.
• If it's set to "Selected networks" or "Private endpoints only", switch it to "All networks" temporarily to test. If the app works after this, you can add your local IP address to the allowed list later for security.

Test Your Connection String Directly in Azure #

To rule out issues with the app itself, test your connection string using Azure's built-in tool:

• Go to your specific Event Hub instance in the portal.
• Select Process data > Send and receive messages.
• Paste your connection string into the field and click Connect. If this fails, your connection string is definitely invalid. If it works, the problem is with the app's setup.

Double-Check for Typos in the Config File #

XML is picky about formatting—small typos can break everything:

• Make sure there are no extra spaces around the values in the <add key="..." value="..."/> lines.
• Confirm all quote marks are closed properly, and there are no missing XML tags.

Try Running CMD as Administrator #

Sometimes local security permissions can block the app from making network connections. Right-click Command Prompt, select Run as administrator, then re-run the command:

telcodatagen.exe 1000 0.2 2

If none of these steps fix the error, try looking for verbose logging options in the config file—some versions of the app let you enable detailed logs that will show the exact underlying error (like authentication failure, timeout, etc.). That can help narrow things down further.

内容的提问来源于stack exchange，提问作者KEID07