Data Sources
The BizTalk Server RFID framework provides management and monitoring data through:
- Event logs
- Windows Management Instrumentation (WMI)
- Performance counters
 Note |
|---|
| Some of the events that are relevant during operations are mentioned in the following sections. BizTalk Server RFID raises a comprehensive set of WMI and event log messages. Refer to Microsoft.SensorServices.Rfid.Management Namespace (http://go.microsoft.com/fwlink/?LinkId=157103) for more details. |
Device-related events
DeviceConnectionAttemptFailedEvent | Occurs when an attempt to open a connection to a device fails. |
DeviceConnectionDownEvent | Occurs when a device connection goes down. |
DeviceConnectionFailureEvent | Occurs when a device temporarily goes down after connecting successfully. |
Antenna event
SourceDownEvent | Occurs when the source is down. |
Event schema
| Name | Description |
|---|---|
Description | Gets a description of the event (inherited from ManagementEvent) |
DeviceInfo | Gets the device information. |
DeviceName | Gets the name of the device (inherited from ServerDeviceManagementEvent) |
EventLevel | Gets the event level (inherited from ManagementEvent) |
EventLevelId | Gets the event ID (inherited from ManagementEvent) |
EventType | Gets the event type (inherited from ManagementEvent) |
EventTypeDescription | Gets the event type description (inherited from ManagementEvent) |
EventTypeId | Gets the event type ID (inherited from ManagementEvent) |
OccuranceTime | Gets the time the event occurred (inherited from ManagementEvent) |
VendorSpecificData | Gets vendor-specific data (inherited from RfidEventBase) |
RFID process-related events
ProcessPausedEvent | Occurs when a process gets to the event collection state. |
ProcessStoppedEvent | Occurs when a process completely stops. |
Event schema
| Name | Description |
|---|---|
Description | Gets a description of the event (inherited from ManagementEvent) |
EventLevel | Gets the event level (inherited from ManagementEvent) |
EventLevelId | Gets the event ID (inherited from ManagementEvent) |
EventType | Gets the event type (inherited from ManagementEvent) |
EventTypeDescription | Gets the event type description (inherited from ManagementEvent) |
EventTypeId | Gets the event type ID (inherited from ManagementEvent) |
OccuranceTime | Gets the time the event occurred (inherited from ManagementEvent) |
ProcessName | Gets or sets the process name (inherited from ProcessManagementEvent) |
VendorSpecificData | Gets vendor-specific data (inherited from RfidEventBase) |
BizTalk Server RFID service-related errors
| EventID | Description | Cause |
|---|---|---|
1500 | The Microsoft BizTalk RFID service failed to start: %1. Resolve the issue that is causing the exception, and then restart the BizTalk RFID service. | Check if the dependent services (SQL, MSMQ, BizTalkRuleEngineService) are started. |
Device-related errors
| EventID | Description | Cause |
|---|---|---|
1013 | The attempt to connect to device %1 failed continuously %2 time(s). The error message for the last failure is: %3. This device is being disabled. To use the device again, re-enable it manually. | Check the device connectivity for any issues. Look at the service and device provider logs. |
RFID process-related errors (Event sources = MSBizTalkRFID and Task category = ProcessManager)
| EventID | Description | Cause |
|---|---|---|
3007 | The RFID process engine %1 encountered an error of type %2. The service will attempt to restart this process engine automatically, unless this was because of a known fatal error. Additional information: %3. If this is due to a known fatal error, resolve the issue, and then start the provider or process manually. | If you see this error due to “ThresholdBreached” it is probably due to errors in the event handler. Verify the RFID process logs. The RFID process is restarted based on the Error-handling policy knobs setup. |
3014 | The process %3 has already been automatically restarted %1 times in the last %2 minutes. It will not be restarted now. Identify the exception that is causing the process shutdown from the process and service logs. Resolve the issue that is causing the exception, and then restart the process manually. | This problem is an effect of the previous issue. This requires further analysis of why the RFID process was restarted. |
| Performance object | Counter | Description |
|---|---|---|
RFID:Devices | Number of errors raised | Number of errors raised by a device. |
RFID:Devices | Downtime | Duration for which a device has been down after a connection error. |
RFID:Processes | Process uptime | Amount of time that has elapsed since a process was started. |
RFID:Processes | Tags suspended | Number of events that have been sent to the suspended queue (tags that caused failures). |
RFID:Processes | Tags processed | Total number of events that have completed processing. |
RFID:Processes | Tags in queue | Total number of events that are currently queued for processing. |
| Note |
|---|
| RFID processes do not have instance counters. Therefore the values for processes are cumulative across all instances. |
- The RFID Management Events Model (http://go.microsoft.com/fwlink/?LinkId=152797)
- Listening to Management Events (http://go.microsoft.com/fwlink/?LinkId=152796)
- How to Monitor BizTalk RFID Using Performance Counters (http://go.microsoft.com/fwlink/?LinkId=152798)
