- 3 minutes to read

What are Suspended Instances in BizTalk Server?

Get alerts and manage suspended instances in BizTalk (grouped by the BizTalk application name).

Suspended instances in BizTalk is the result of some operational error/exception. The underlying problem may be internal or external. You must carefully manage the suspended instances; otherwise, you may lose business transactions.

There are two types of suspended instances:

  1. Suspended instance(s) (resumable)
  2. Suspended instance(s) (not resumable)

Suspended resumable and not resumable
Suspended instances for the selected BizTalk Server Application

NOTE: If you do not deal with your suspended instances, you will get bad performance, and ultimately you will run out of disk space. Also worth mentioning is that business transactions flows are interrupted, which is probably is bad for your business.
The suspended messages may include very sensitive content, and any BizTalk Server Administrator may read (and potentially share) this information without any traces when working with the BizTalk Server MMC. With Nodinite, you can separate access using role-based security. For your protection, all sensitive operations are log audited

Stay secure - With Nodinite, you do not need to be a BizTalk Server Administrator to resolve issues with suspended instances.
Avoid the blame game - All sensitive operations records to the Audit Log.
Solve problems swiftly - Nodinite has support for Remote Actions to work with the suspended instances.
Statistics help you improve - Nodinite has built-in reports that help you improve your business with facts.


1. Suspended instance(s) (resumable)

Whenever BizTalk Server initiates a process (e.g. receive, orchestrate, send), the run-time creates an instance. During processing, this Instance has a different state such as (not a complete list):

These instances cannot be resumed, and the only option when there has been an error is eventually to terminate the instance (hence the name 'not resumable').

2. Suspended instance(s) (not resumable)

Together with each such instance, there will be the actual payload (messages) and context properties and whenever there is an error/exception these may be resumed (or Terminated) in which case another active instance is created (for the resume operation), and the old one will automatically be terminated.

Managing suspended instances

With the Nodinite BizTalk Server Monitoring Agent, suspended instances manifest by BizTalk application name as Resources grouped into the following two Categories:

  1. Suspended instance(s) (resumable)
  2. Suspended instance(s) (not resumable)

If your Monitor View allow the Remote Actions feature, you will find out the following operations exists to further work with the suspended instances (different for resumable and not resumable):

Suspended instance(s) (resumable) Suspended instance(s) (not resumable)
Manage (One, Selected, All) Manage (One, Selected, All)
Terminate all Terminate all
Details Details
  • Terminate (one, selected, all)
  • Resume (one, selected, all)
  • Download (payload)
  • Details
  • Context Properties
  • View suspended instance history
  • Metrics

Next step

Spool count health check
Statistics for Suspended instances
Monitor Views
Configuration

Suspended instance(s) (resumable)
Suspended instance(s) (not resumable)