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.
