Develop Reference

the service instance will remain suspended until administratively resumed or terminated following error exception type initializer

I am getting the above error, exception type initializer.
Could please give what type of take an action to resolved this issue.
I got following error when am trying to drop a file in receive location and I did resumed in biztalk admin console it shows same error in event application logs.

You are getting this error due to your logging component, your logging component is trying to load itself via a static constructor most likely and failing there. It looks like it depends on Microsoft enterprise logging block, make sure you have all dependencies installed in GAC properly or check your logging component configuration to see why it's failing. It's not related to BizTalk issue.

Unhandled Exception in System.Transactions stops Windows Service during network instability

We are running an NServiceBus-based service, using the NServiceBus.Host.exe host process.
Twice in production during the last few months the Windows Service has suddenly stopped, leaving the following event in the Application Event Log:
Application: NServiceBus.Host.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Stack:
at System.Transactions.TransactionState.ChangeStatePromotedPhase0(System.Transactions.InternalTransaction)
at System.Transactions.Phase0VolatileDemultiplexer.InternalPrepare()
at System.Transactions.VolatileDemultiplexer.PoolablePrepare(System.Object)
at System.Transactions.Oletx.OletxVolatileEnlistment.Prepare(System.Transactions.Oletx.OletxVolatileEnlistmentContainer)
at System.Transactions.Oletx.OletxPhase0VolatileEnlistmentContainer.Phase0Request(Boolean)
at System.Transactions.Oletx.OletxTransactionManager.ShimNotificationCallback(System.Object, Boolean)
at System.Threading._ThreadPoolWaitOrTimerCallback.PerformWaitOrTimerCallback(System.Object, Boolean)
We got this error during a period with some minutes of network instability (e.g. lots of timeouts against the database, which are visible in our log4net log files)
Any ideas as to what is failing here?
We see no fatal errors in our log4net logfiles.
Versions:
Windows Server 2008 R2
.NET Framework 4.5.2
NServiceBus 4.7.5
NHibernate 3.3.3.4001 (used for saga, subscription and timeout persister)
SQL Server 2012

It seems the behavior you see is related to how NHibernate handles the TransactionCompleted event. This questions is also somehow related to this question.
The AdoNetWithDistributedTransactionFactory registers an anonymous delegate on the TransactionCompleted event. This event gets fired on a background thread by using ThreadPool.QueueUserWorkItem. If that operation throws an exception due to connectivity issues with your database server (i.ex. due to a network partition) this exception gets raised as an unobserved exception on the AppDomain. UnhandledExceptions tear down the AppDomain and therefore also the NServiceBus.Host.
The best possible workaround for that would be to register an UnhandledException handler on the current AppDomain like the following
AppDomain.CurrentDomain.UnhandledException += OnUnhandledException
private static void OnUnhandledException(object sender, UnhandledExceptionEventArgs e)
{
LogManager.GetLogger(typeof(AppDomain)).Fatal(“Unhandled exception”, e.ExceptionObject as Exception);
}
More information see
When this fixed the intermediate problem it would make sense to find the root cause of the connection issues with your database server in combination with NHibernate

Exception Debugging using Unity IOC

I'm having issues getting good Exception information when using Microsoft.Practices.Unity to load some classes dynamically.
The code is on a remote server and I'm using ELMAh to capture errors. I see the exceptions but the exception information stops at DynamicModule.ns.Wrapped_IMyClass_GUID.MyFunction().
I've pushed debug classes to the server so I see the line numbers up to that point but I can't get the line numbers for these dynamically loaded classes.
Is there a setting I'm missing somewhere that allows the real inner exception information to be displayed?

Unity includes all the chain of the errors in the InnerException, of each one. For example if you have a chain of dependency like this: Service1 dependes on Service2 depends on Service3
and, if Unity failed to instanciate Service3 due to a resolution error, you'll get a resolution failed exception of Service1 having an InnerException of type resolution failed exception of Service2 having an InnerExcepetion of type resolution failed exception of Service3.

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.