Develop Reference

BizTalk Error in event log on running request in SOAPUI

This is the error encountered in Event log of BizTalk Admin
xlang/s engine event log entry: Uncaught exception (see the 'inner
exception' below) has suspended an instance of service
'orchestration.AsyncOrchestration(ebb0442e-bff4-cd1c-f5dc-aff7c5086e57)'.
The service instance will remain suspended until administratively
resumed or terminated. If resumed the instance will continue from its
last persisted state and may re-throw the same unexpected exception.
InstanceId: 50fc5f8b-c9b9-44e1-9781-2a1391c145ec Shape name:
Expression_1 ShapeId: ddfccde4-3444-47c4-977d-228e66ffaae6 Exception
thrown from: segment 1, progress 17 Inner exception: Resolution of the
dependency failed, type =
"BizTalkComponents.Interface.ISsoSettingsReader", name = "(none)".
Exception occurred while: while resolving. Exception is:
InvalidOperationException - The current type,
BizTalkComponents.Interface.ISsoSettingsReader, is an interface and
cannot be constructed.
Are you missing a type mapping?

First, this has noting to do with SOAPUI or any specific client.
It seems that your deployment process has failed to include the SSO lookup components that are called in the failing Orchestration.
So, whichever set of component the app is using must be installed on the server.

System.net.webexception in system.dll

I have followed this tutorial to update a powerbi dashboard here.
I have copied all the code from Microsoft's website. Of course I have supplied my own clientId.
The console application successfully creates a dataset, but does not add rows to the table.
It fails here:
var response = (HttpWebResponse)request.GetResponse();
An unhandled exception of type 'System.Net.WebException' occurred in System.dll
Additional information: The remote server returned an error: (404) Not Found.

The URL you are querying is wrong or no longer exists. Check the documentation for the APIs you are querying to make sure you are properly constructing the URL.
Start here for PowerBI APIs: https://msdn.microsoft.com/library/dn877544.aspx

What's causing this exception?

What's wrong with this? I get the exception
An unhandled exception of type 'System.Net.WebException' occurred in System.dll
Additional information: An exception occurred during a WebClient request."
Here's the part of the code with the WebClient.
I need to learn how to use the code part properly one day....
http://pastebin.com/1Z90bvqB
Any answers are greatly appreciated.

(I'm not sure I agree with the ethics of the code itself, but ignoring that...) a WebException is caused by a line that connects to the internet, so either one of the lines like:
webClient.DownloadFile(String.Copy(WeepCraft), #"%appdata%\.minecraft\versions");
Or the line:
Process.Start("http://www.wirez.cf/");
In the latter case, unless I'm misunderstanding, is this actually a process you can start??
Anyway, around all the lines, you'll need to have a try/catch for WebException in case it can't connect for whatever reason (eg Internet down, wrong URL used, server returns HTTP Error code etc etc), and decide how to handle it.
It's a pretty common Exception whenever something tries to do a http request and the server can't be connected to for whatever reason.

System.Net.Sockets.SocketException when closing NamedPipeClientStream

After I try to close a pipe client, I see the following error in the output console:
A first chance exception of type 'System.Net.Sockets.SocketException' occurred in System.dll
What does it mean? How can I fix it?

See http://blogs.msdn.com/b/davidklinems/archive/2005/07/12/438061.aspx for an explanation of the "first chance exception".
What is a first chance exception?
When an application is being debugged, the debugger gets notified whenever an exception is encountered At this point, the application is suspended and the debugger decides how to handle the exception. The first pass through this mechanism is called a "first chance" exception.
Depending on the debugger's configuration, it will either resume the application and pass the exception on or it will leave the application suspended and enter debug mode. If the application handles the exception, it continues to run normally.

A first chance exception of type 'System.Xml.XmlException' occurred in System.Xml.dll

When I start my application (it is a client which connect with WCF to a Service) I see in the Output-Window of Visual Studio many lines with
A first chance exception of type 'System.Xml.XmlException' occurred in System.Xml.dll
I have turn on the throw of this Exception and see, that it occures, when the client calls the WCF-Service. The Message of the Exception is:
A name must not beginn with '<'
(in german: Ein Name darf nicht mit dem Zeichen '<', hexadezimaler Wert 0x3C, beginnen.)
Should I do something about this? Or is this normal? Can this be a performance issue?
Thanks for your help.
Best Regards, Thomas

I also got this exception after calling my wcf dataservic endpoint a couple of times. After some searching i found this post that was spot on:
https://social.msdn.microsoft.com/Forums/en-US/74813783-8666-40c4-a9fd-7953f7b6849c/invalid-xml-with-two-feed-elements-returned-after-a-few-requests?forum=adodotnetdataservices
When you have WCF tracing configured and you have set
logMessagesAtTransportLevel to true, you get this behavior
So i changed the configuration of my service and it worked.

This is normal. First chance exception messages indicate exceptions that were thrown and handled.
The ones you are getting is probably due to missing configuration info or serialization info in your assembly. The aforementioned might not be needed if everything is working fine.

9 changes out of 10 this is not a problem. It's common in those classes (and also in, e.g. Entity Framework) to throw exceptions when it's run. So I wouldn't worry about it too much.
I would worry if you can step into the code (i.e. you wrote the code yourself that throws the exception).
But I don't think that is the case.