A nice presentation has been given on the TechEd in Australia. On this site you can find the presentation and the demo code.
Tag Archives: RFID
BizTalk Server 2009 – RFID
A while ago I blogged about RFID and how to set it up with BizTalk Server 2006 R2. Today I took some time to port it to BizTalk Server 2009. The steps I mentioned in the old post are still in place, with some additions:
* 3.7.0.0 for Microsoft BizTalk Server 2009 (same as the beta version)
* When building Phidget_BizTalkDSPI_src I received the next error:
—— Build started: Project: PhidgetDSPI, Configuration: Debug Any CPU ——
“%RFIDINSTALLDIR%\bin\rfidclientconsole.exe” registerprovider “Phidget Provider” Microsoft.PhidgetDevices.DSPI
“%RFIDINSTALLDIR%\bin\rfidclientconsole.exe” stopprovider “Phidget Provider”exit 0
Command failed, reason Access is denied. You need to be a member of the built-in Administrators group on the server to be able to perform this operation.
Remote message Access is denied. You need to be a member of the built-in Administrators group on the server to be able to perform this operation.
Command failed, reason Access is denied. You need to be a member of the built-in Administrators group on the server to be able to perform this operation.
Remote message Access is denied. You need to be a member of the built-in Administrators group on the server to be able to perform this operation.
C:\Windows\Microsoft.NET\Framework\v3.5…
etc
…
c:\Windows\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3397,13): error MSB3073: ” exited with code 1.
Done building project “PhidgetDSPI.csproj” — FAILED.
========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ==========
* To fix this problem: Turn User Account Control off (and reboot the machine)
* Before building DupElim: Change the Target Platform from the project: DuplicateTagIdsElimination to .Net FrameWork 3.5
* “Run EventHandlerSampleSetup.cmd” throwed an error, but when starting FilterProcess manually in the RFID Manager then there was no problem.
So: The import went ok in this cmd-file. But the “%exe% -m localhost startprocess FilterProcess” throwed an error.
BizTalk RFID 2009 – PhidgetRFID
Below are the steps I used to get my BizTalk RFID up and running with respect to PhidgetRFID. You have to use 3.6.0.0 for BizTalk Server 2006 R2, and 3.7.0.0 for BizTalk Server 2009 Beta
Make sure the Microsoft BizTalk RFID Service is running!
Download Phidget software (http://www.phidgets.com/downloads.php?os_id=1)
Copy the Phidget21.NET.dll to the GAC
Start RFID-full.exe and check if your Reader is working. If not, make sure it is connected to your computer (or Virtual Machine). You don’t need to install this device. Windows will recognize it and installs it as a Human Interface Device.
Download “”BizTalk RFID Device Provider (DSPI) for Phidget Devices”. (this version works with the PhidgetRFID): http://blogs.msdn.com/irvingd/pages/biztalk-rfid-device-provider-dspi-for-phidget-devices.aspx
Build Phidget_BizTalkDSPI_src against the right BizTalk.RFID version (3.6.0.0 for BizTalk Server 2006 R2). The original Dll is build against BizTalk Server 2006 R2 Beta (3.0.0.0).
Copy the Dll’s Microsoft.PhidgetDevices.dll and Microsoft.PhidgetDevices.DSPI.dll to the GAC
Copy these Dll’s also to the folder: PhidgetPackage (where PhidgetProvider_Install.cmd resides)
Change the file PhidgetProvider_Install.cmd
Microsoft.PhidgetsDevices.DSPI must be Microsoft.PhidgetDevices.DSPI
Run PhidgetProvider_Install.cmd
Install DupElim (Duplicate Eliminator): http://go.microsoft.com/fwlink/?LinkId=99664 (This sample eliminates duplicates from TagReadEvents and TagListEvents)
Change the file FilterProcess.xml. Change 3.0.0.0 to 3.6.0.0
Build: DuplicateTagIdsElimination.csproj (against the BizTalk.RFID assemblies 3.6.0.0)
Run EventHandlerSampleSetup.cmd
Open RFID Manager
The Device Providers must contain a Phidgets Provider
Add your reader to the Devices
Below Processes the DupElim creates a dummy process. Change this one, or Add a new one and use as component besides the SqlSink the DupElim component.
After starting all, your reader will receive events (tags) and put it in SQL Server in the TagsEvent table.
This works for me. If you have still some problems, then you can have a look at:
http://blogs.msdn.com/irvingd/pages/biztalk-rfid-device-provider-dspi-for-phidget-devices.aspx
http://blogs.objectsharp.com/cs/blogs/matt/archive/2007/06/09/biztalk-r2-rfid-and-working-with-a-real-reader-device-phidget.aspx
If you use custom accounts for the Service and the Worker Process, then make sure these accounts are added in SQL Server. The Service account must have access to the RFIDSTORE. The Worker Process must have access to the ‘rfidsink’ database.
As I blogged earlier I had problems with BizTalk RFID 2009 (Beta, 3.7.0.0). But after following the steps above I managed to get BizTalk RFID up and running (use .Net Framework 2.0). I had only 1 small problem 
my database ‘rfidsink’ was not created. This database is installed with BizTalk RFID, but something went wrong or it is really a beta product. Finally I took the rfidsink database from BizTalk Server 2006 R2. And as I can see now, it works all fine :’-) Now I can focus on the real process.
I you have any suggestions or questions let me know.
Vincent: thanks for your support
BizTalk RFID Phidgets Provider
I was playing around this week with this technology and finally past the Provider configuration in RFID Manager. It is very important that you build the “PhidgetDSPI” against your .Net Framework and BizTalk RFID components (3.6.0.0 for BizTalk Server R2 / RFID). Make also sure that you install/copy the assembly Microsoft.PhidgetDevices.DSPI.dll and Microsoft.PhidgetDevices.dll to the GAC (else it will complain).
Note: if you use PhidgetProvider_Install.cmd, then search on Microsoft.PhidgetsDevices.DSPI and change to Microsoft.PhidgetDevices.DSPI. Note: manual works also…
