• Print
  • Share
  • Dark
    Light

Troubleshooting

  • Updated on 19 Nov 2018
  • 1 minute to read
  • Contributors

Installation

Issue Resolution
If you are using Visual Studio to deploy Atomic Scope Azure components, after you open the project file in Visual Studio, you may get the below error while deploying

image.png
  • Goto File and click Save All, a popup will appear to save the solution file.
  • Click Save
  • You will now be able to deploy without any errors.

Runtime errors


Issue Resolution
Microsoft.Azure.EventHubs.Processor.EventProcessorConfigurationException:
Encountered error while fetching the list of Event Hub PartitionIds --->
System.Net.Sockets.SocketException:
A connection attempt failed because the connected party did not properly respond after a period of time,
or established connection failed because connected host has failed to respond
Ignore this error
Microsoft.Azure.EventHubs.ReceiverDisconnectedException:
New receiver with the higher epoch of '6' is created hence current receiver with epoch '5' is getting disconnected.
If you are recreating the receiver, make sure a higher epoch is used.
Ignore this error

Running Samples

Issue Resolution
System.IO.FileNotFoundException: Could not load file or assembly 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified. File name: 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' Navigate to Atomic Scope InstallDir (Kovai Ltd\AtomicScope\Binaries) and GAC the file shown in the error
On Windows 10 Operating System, you might encounter the following error: There was a failure executing the receive pipeline: "AtomicScope.BizTalk.Samples.Pipelines.XMLReceivePipeline, AtomicScope.BizTalk.Samples.Pipelines, Version=1.0.0.0, Culture=neutral, PublicKeyToken=418c8017a5c745d7" Source: "XML disassembler" Receive Port: "rcvPort_HybridInbound" URI: "https://relayns.servicebus.windows.net/asrelay" Reason: Finding the document specification by message type "Binary" failed. Verify the schema deployed properly.

image.png
Update the message body property in the Messages tab of receive location mentioned in the error as shown in Figure
Was this article helpful?