What are Suspended Instances in Microsoft BizTalk Server?
Get alerts and manage suspended instances in BizTalk (grouped by the BizTalk application name).
Empower yourself with Nodinite - you don't need to be a BizTalk Server Administrator to resolve issues with suspended instances. Nodinite makes it easy and secure.
Avoid the blame game - All sensitive operations records are in the Audit Log.
Solve problems swiftly - Nodinite features Remote Actions to help manage the suspended instances.
Statistics help you improve - Nodinite has built-in reports that help you improve your business with facts.
As a BizTalk professional, it's crucial to manage suspended instances. These instances are the result of operational errors or exceptions, and if not managed carefully, you risk losing business transactions. There are two types of suspended instances:
There are two types of suspended instances:
- Suspended instance(s) (resumable)
- Suspended instance(s) (not resumable)
Suspended instances for the selected BizTalk Server Application.
Warning
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 transaction flows are interrupted, which is probably bad for your business.
Important
The suspended messages may include 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
1. Suspended instance(s) (resumable)
The run-time creates an instance whenever the BizTalk Server initiates a process (e.g. receive, orchestrate, send). During processing, this instance has a different state, such as (not a complete list):
- Active Instance(s) - Still running and performing work
- Dehydrated Orchestration Instance(s)
- Ready to run Instance(s)
- Retrying Instance(s)
- Scheduled Instance(s)
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)
Each instance will have the actual payload (messages) and context properties. 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 are grouped into the following two Categories:
If your Monitor View allows the Remote Actions feature, you will find out the following operations exist 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 |
| Edit | Edit |
- Suppress (one, selected, all)
- Unsuppress (one, selected, all)
- 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
Related
Suspended instance(s) (resumable)
Suspended instance(s) (not resumable)