BizTalk RFID is compatible only with BizTalk Server 2006 R2, and cannot be installed with any previous version of BizTalk Server.

BizTalk RFID uses MSMQ to store and forward messages. When BizTalk Server 2006 is installed, an MSMQ-related adapter (the BizTalk Message Queuing adapter) is also installed. We recommend that you do not run both standard Message Queuing (MSMQ) and BizTalk Message Queuing (MSMQT) on the same computer. For more information about the compatibility of MSMQ and the MSMQT adapter on the same computer, refer to the BizTalk Server documentation.

Before installing BizTalk RFID on your computer, do the following:

• Ensure that the computer meets the system requirements for BizTalk RFID. For more information, see Prerequisites for Installing BizTalk RFID.
  
  
• Ensure that you follow the supported configurations while setting up BizTalk RFID. For more information, see Supported Configurations.
  
  
• Review all BizTalk RFID installation options and prepare to make the appropriate selections when running Setup. For more information, see BizTalk RFID Setup Components and Types of Installation.
  
  

Computers running Windows Server® 2003 must have Internet Information Services (IIS) 6.0 installed to enable provider code to run as distinct worker processes.

You must configure IIS to work with ASP.NET.

The port number that RFID Services uses has changed from 8081 (in the previous version) to 7891. You must add 7891 to the list of exceptions in Windows Firewall.

You can change the port number by making the appropriate configuration modifications in the rfidServices.exe.config file located in the ..\Microsoft BizTalk RFID\bin\ folder. After installing BizTalk RFID, you can see the RFID Manager documentation located in the ..\Microsoft BizTalk RFID\Documentation\ folder for more information about providing a port to connect.

The minimum hardware requirements for BizTalk RFID installation are:

• 133 megahertz (MHz) or higher Intel Pentium-compatible CPU
  
  
• 512 megabytes (MB) of RAM
  
  
• 6 gigabytes (GB) disk space
  
  
• CD-ROM or DVD-ROM drive
  
  
• Windows Server 2003 Service Pack 1 (SP1) or Windows® XP SP2-compatible super VGA (800 x 600) or higher-resolution monitor
  
  

The recommended hardware requirements for BizTalk RFID installation are:

• 733 megahertz (MHz) or higher Intel Pentium-compatible CPU
  
  
• 1 gigabyte (GB) of RAM
  
  
• 40 gigabytes (GB) of disk space
  
  
• Windows Server 2003 SP1 or Windows XP SP2-compatible super VGA (1024 x 768) or higher-resolution monitor
  
  
• Microsoft mouse or compatible pointing device
  
  

Install the following software before you begin installing BizTalk RFID:

• Windows XP SP2 32-bit, Windows Server 2003 SP1 or higher, or Windows Vista® 32-bit
  
  
• Microsoft Internet Information Services (IIS) 6.0 on Windows Server 2003 computers
  
  
• Web Services Enhancements (WSE) 3.0, if you choose Complete installation. WSE is required by the BizTalk RFID SDK. You can download WSE 3.0 from http://go.microsoft.com/fwlink/?LinkID=93064.
  
  
• Microsoft Message Queuing service (MSMQ), if you choose to install RFID Server. MSMQ is a Windows component and can be installed by using Add/Remove Windows Components in Add or Remove Programs from Control Panel.
  
  
• Any one of the following database software, if you choose to install RFID Server, and want to install the database component of BizTalk RFID on the same computer:
  
  
  • Microsoft SQL Server™ 2005 with Service Pack 2
    
    
  • Microsoft SQL Server 2000 with Service Pack 4
    
    
  • Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) release A version 8.00.760 or higher
    
    

    Note
    The SQL Server or MSDE database must be available and configured to support Windows authentication.

• Microsoft Management Console (MMC) 3.0 RTM version
  
  
• World Wide Web Publishing Service on Windows Server 2003 computers
  
  

For details about how to install any of the software prerequisites listed above, refer to their respective installation guides.

You need the following permissions to successfully install BizTalk RFID:

• You must belong to the Administrators group on the computer on which you want to install BizTalk RFID.
  
  
• You must have Administrator rights for the SQL Server instance.
  
  

RFID Manager may not accept an identifier assigned to a new Web site, if it is a very large number. Use these commands to modify the identifier of the Web site if necessary:

CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs STOP_SERVER W3SVC/<Large_WebsiteID>
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs MOVE W3SVC/<Large_WebsiteID> W3SVC/<New_WebsiteID>
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs START_SERVER W3SVC/<New_WebsiteID>

For example, if the Web site identifier that RFID Manager does not accept is 51829689933, and you would like to assign a new identifier 1987, you need to run the following commands:

CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs STOP_SERVER W3SVC/51829689933
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs MOVE W3SVC/51829689933 W3SVC/1987
CSCRIPT %SYSTEMDRIVE%\Inetpub\AdminScripts\adsutil.vbs START_SERVER W3SVC/1987

Possible Cause

Any error while removing BizTalk RFID can cause service account credentials to be deleted.

Solution

Find the service named MSBizTalkRFID, set the service account to Local System, and then try to remove the installation.

Symptom

Uninstalling fails with error message: "The installation source for this product is not available. Verify that the source exists and that you can access it."

Possible Cause

Setup.exe cannot run if the version of the RfidServices.msi package is different from that of the original installation.

Solution

Run Setup.exe from the directory where the product was originally installed and select the Remove option.

If this doesn't solve the problem, you can attempt to repair the installation by using the Repair option when setup is run from Add or Remove Programs. If the Repair option isn't available when setup is run from Add or Remove Programs, you may be able to access it by clicking Click here for support information in the Add or Remove Programs entry for Microsoft BizTalk RFID. After repairing the installation, attempt to uninstall BizTalk RFID.

Possible Cause

This error can occur if the removal of a Beta 2 version of the ASP.NET Framework did not delete old entries from the registry.

Solution

1. Locate the following subkeys in the registry:
   
   
   • HKEY_CLASSES_ROOT\CLSID\{7D23CCC6-A390-406E-AB67-2F8B7558F6F6}\InprocServer32
     
     
   • HKEY_CLASSES_ROOT\CLSID\{FD5CD8B1-6FE0-44F3-BBFB-65E3655B096E} \InprocServer32
     
     
   • HKEY_CLASSES_ROOT\CLSID\{FEDB2179-2335-48F0-AA28-5CDA35A2B36D}\InprocServer32
     
     
2. Expand the InProcServer32 subkey, and delete any entries not named 2.0.0.0 (for example, delete 2.0.36.0).
   
   
3. Restart IIS.
   
   

Symptom

Installation fails with error message: "An error occurred during the installation of assembly component {A0B265D0-E711-4106-91E1-67843687C8A1}. HRESULT: 0x80070005".

Possible Cause

This can be due to a recent credentials change for the logged-in user.

Solution

Cancel the installation, restart the computer, and try the installation again.

Symptom

Installation fails with an error message: "((Error)) GacAssembly:Failed to GAC the Dll.:-1".

- OR -

Installation fails and the log file has an entry: "Access denied. You might not have administrative credentials to perform this task."

Possible Cause

The global assembly cache (GAC) might be in an unstable state.

Solution

Restart the computer, and try to install BizTalk RFID again.

Symptom

Installation of BizTalk RFID succeeds, but the MSBizTalkRFID service fails to start.

Possible Cause

Various conditions can cause this problem to occur. Check the following list of solutions to ensure that BizTalk RFID is installed correctly.

Solution

Check the following on your computer:

• Ensure that the user name specified for the RFID Service account has administrator privileges on the computer.
  
  
• Ensure that the user name specified for the RFID Service account has access to the SQL server that you specified during installation.
  
  
• Ensure that the user name specified for the RFID Service account has the "Logon as a service" right enabled.
  
  
• The RFID service is dependent on the following services. Check if any of these services failed to start:
  
  
  • The SQL server (or a particular instance of SQL Server) that you mentioned during installation
    
    
  • Message Queuing
    
    
• In Administrative Tools, click Event Viewer, and then click Application. Locate messages with Source as BizTalkRFID and Event equal to 1500. View these messages for further information about why the RFID service failed to start.
  
  
• In Administrative Tools, click Event Viewer, and then click System. Locate messages with Source as Service Control Manager and Event equal to 7000 or 7038. View these messages for further information about why the RFID service failed to start.
  
  
• Check to determine if the SQL server was added correctly as a dependency of the RFID service.
  
  
• The Rfid.Config file and the RfidServices.exe.Config file might have been corrupted. Duplicates of these files are located in the \bin folder of BizTalk RFID, and are named as Rfid.Config.Initial and Rfidservices.exe.config.initial. Delete the corrupted files and rename the duplicate files to Rfid.Config and RfidServices.exe.Config respectively.
  
  

Symptom

In the Setup RFID Service Account page of BizTalk RFID Setup, the user name appears as .\RfidSvcAcc or .\RfidUsrAcc, and then the installation process fails.

Possible Cause

The computer may be in an unstable state.

Solution

Restart the computer and then try installing BizTalk RFID again.

Symptom

After you install BizTalk RFID, you receive the error "The dependency service or group failed to start", and the MSBizTalkRFID service fails to start.

Possible Cause

The MSBizTalkRFID service depends on Message Queuing, which in turn depends on the Distributed Transaction Coordinator (DTC) service. If the DTC service is using LocalSystem as the Service Account, then the DTC service will not start.

Solution

At the command prompt, run the following command:

sc qc msdtc

• If the displayed value of SERVICE_START_NAME is LocalSystem, then perform the following steps.
  
  
  1. At the command prompt, run the following command:
     
     net stop msdtc
     
     
  2. At the command prompt, run the following command:
     
     msdtc -uninstall
     
     
  3. Open Registry Editor and delete the HKLM\Software\Microsoft\MSDTC key.
     
     
  4. At the command prompt, run the following command:
     
     msdtc -install
     
     
  5. At the command prompt, run the following command:
     
     net start msdtc
     
     
  6. At the command prompt, run the following command:
     
     net start MSMQ
     
     
  7. At the command prompt, run the following command:
     
     net start BizTalkRFID
     
     
• If the displayed value of SERVICE_START_NAME is NetworkService, contact Microsoft Support for further assistance.
  
  

Symptom

After you install BizTalk RFID, you receive the error "Socket Address in use," and the MSBizTalkRFID service fails to start.

Possible Cause

The MSBizTalkRFID service uses the default Web Services Enhancements port 7891. If any other Web service application has been loaded before the RFID service, then port 7891 is already in use and the MSBizTalkRFID service will not start.

Solution

Do one of the following:

• If possible, change the port that the Web service application uses.
  
  
• Alternatively, change the port that the RFID service uses.
  
  

To change the port that the RFID service uses, use the following steps.

1. Edit the Rfid.config file located in the \bin folder of BizTalk RFID to include the following code fragment:
   
   

   <rfidStore>    <connectionString>Persist Security Info=False;Integrated Security=SSPI;database=RFIDSTORE;server=YOURSERVERNAME</connectionString> </rfidStore> <wsConfiguration><wSPort>8092</wSPort></wsConfiguration> <!-- insert this line of code -->

2. RFID administration tools use the default WSE port 7891, and changing this port in the rfid.config file will cause RfidClientConsole.exe and RFID Manager to fail. To resolve this, create and place the RfidClientConsole.exe.config and mmc.exe.config files in the \bin folder of BizTalk RFID. Both these files need to have the following content:
   
   

   <?xml version="1.0" encoding="utf-8" ?> <configuration>   <configSections>     <section name="microsoft.web.services2" type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration, Microsoft.Web.Services2, Version=2.0.3.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />   </configSections>   <microsoft.web.services2>         <messaging>           <executionTimeout value="300" />             <transports><add scheme="soap.tcp"><defaultPort value = "8092"/></add></transports>         </messaging>   </microsoft.web.services2> </configuration>

   Note
   The mmc.exe.config file will redirect the snap-in to communicate to the server using the new port only if RFID Admin UI.msc is opened from the \bin folder of BizTalk RFID. This will not work if the snap-in is added explicitly to mmc.exe.

   Note
   If you write your own program using the RFID client proxies—for example, DeviceManagerProxy—you need to explicitly set the proxy port to the same port that the server is using.

Symptom

After you install BizTalk RFID, RFID Manager does not appear in the Start menu.

Possible Cause

The correct option to install RFID Manager may not have been selected during installation.

Solution

RFID Manager is packaged with the RFID Tools and Client Connector component of BizTalk RFID Setup. If you have chosen Custom setup during installation, use the steps listed under Modifying or Repairing BizTalk RFID Installation to view the Custom page. On the Custom page, ensure that the RFID Tools and Client Connector component is not cleared.

Symptom

When trying to install BizTalk RFID, you get the error message, "Verify that you have sufficient privileges to install system services," even though you have administrator privileges on your computer.

Possible Cause

This is probably because the previous version of BizTalk RFID is not completely removed from your computer.

Solution

Uninstall any previous version of BizTalk RFID, restart your computer, and then try installing BizTalk RFID on your computer again.

Symptom

When installing BizTalk RFID, you get an error message saying Setup was unable to create the RFID Store database.

Possible Cause

The user specified may not have sufficient privileges, or previous installations of SQL Server may not have been removed completely.

Solution

Perform the following steps:

1. Ensure that the user who installed BizTalk RFID had the required permissions to create the database in SQL Server.
   
   
2. Ensure that any previous installation removals of SQL Server have completed successfully, by removing the MDF files associated with the SQL Server instance. The MDF files can be found in a folder that has the instance name in the SQL Server installation directory.
   
   

Symptom

You receive errors related to DTC, MSDTC, or remote transaction manager if you configure the RFIDsink database on a remote SQL server.

Possible Cause

Configuration steps to assign a remote SQL server as the RFIDsink database may not have been completed.

Solution

You need to complete some initial configuration steps to enable the remote RFIDsink database to work with BizTalk RFID. For more information about these steps, see Preparing to Set up a Remote RFIDsink Database.

Symptom

You are unable to connect to a BizTalk RFID service on a remote computer from a client computer.

Possible Cause

Windows Firewall may be restricting access from and to BizTalk RFID.

Solution

You need to allow Rfidservices.exe through the Windows firewall on the RFID server. To do this, click Start, click Control Panel, and then double-click Windows Firewall. On the Exceptions tab, click Add Program, browse to the location of RfidServices.exe, and then click Open. In the Add a Program dialog box, click OK. On the Exceptions tab, click OK.

Symptom

Setup fails with the error "((ERROR)) Failed to execute immediate command line: "C:\Program Files\BizTalk RFID\bin\ManagedCustomActions.exe "RegisterOOBEventhandlers" %temp%\RegisterOOBEventhandler 0XFFFFFFFF -"

Possible Cause

The BizTalk RFID service may have been successfully installed, but failed to start after installation. This can occur if old data exists in the RFIDstore database.

Solution

Review the file %TEMP%\ RfidRegisterOobEventhandlers*.log for additional information about why this failure occurred. In addition, inspect the event logs for more information.

Symptom

After a fresh install of BizTalk RFID, providers or processes fail to start and you see system event log entries like:

A process serving application pool 'Contoso03b708f3-b811-45b4-869f-4587aee86241' reported a failure. The process id was '6312'. The data field contains the error number.

The data field contains the number 80070005.

Possible Cause

IIS does not recognize the identity of the application pool.

Solution

Restart the World Wide Web Publishing service (w3svc).

Symptoms

The BizTalk RFID installation fails with the error message: Failed to execute deferred command line: "C:\Program Files\BizTalk RFID\bin\ManagedCustomActions.exe" "CreateWMINamespace" "%Temp%\rfidwmi":0xFFFFFFFF".

Cause

The Windows Management Instrumentation (WMI) service may be disabled, or may not be running.

Resolution

Enable the WMI service if it is disabled, and then start the WMI service.

Symptoms

If you choose to cancel Setup while uninstalling BizTalk RFID, actions performed during the procedure will not be rolled back.

Cause

This is by design.

Resolution

If you ran the uninstallation by mistake, and want to keep the product on the computer, reinstall it.

Symptoms

During installation with SQL Server authentication type for the RFID configuration database (RFIDstore), the following error message is displayed: "Setup has succeeded, but the service could not be started. Please look at the event viewer for more information". The event viewer has the error: "Cannot open database "RFIDSTORE" requested by the login. The login failed."

Cause

The specified SQL Server user for the SQL Server type authentication is associated with a low-privileged role. For example, the role associated with the SQL Server user may be "Public".

Resolution

To start BizTalk RFID after the installation is complete, the SQL Server user (specified in the Database System and RFID Configuration Database Information page of the setup wizard) must have permissions to:

1. Connect to the RFID configuration database
   
   
2. Execute stored procedures on the RFID configuration database.
   
   

To grant the required permissions, execute the following queries in SQL Server:

USE [RFIDSTORE]
SP_GRANTDBACCESS [SQLUser]
GRANT EXECUTE TO [SQLUser]   

Symptoms

On a Windows Vista computer, Setup fails with the error: "Could not access VBScript runtime for custom action", and then the failed installation process rolls back.

Cause

During installation, BizTalk RFID requires the VBScript engine. When Windows Vista is installed on a computer, by default, the VBScript engine is available on the computer, but is not registered.

Resolution

Manually register the VBScript engine on the computer. To register the VBScript engine, run the following command in a Command Prompt window with Administrator privileges:

regsvr32 vbscript.dll

Symptom

BizTalk RFID functions normally, but log files do not have any log entries.

Cause

A custom tool can have a file handle to a log file. When the log file reaches the file size limit, BizTalk RFID attempts to rotate the log file. If the custom tool file handle is active when BizTalk RFID attempts to rotate the log file, the logger stops writing information to the log file.

Solution

Restart the BizTalk RFID service, or the affected provider or process. For more information, refer to the KB article: http://support.microsoft.com/kb/939440/en-us.

-----------------------------------------------------------------------------------------------

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2007 Microsoft Corporation. All rights reserved.

Microsoft, BizTalk, SharePoint, Windows, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.