To resolve this issue, follow these steps.
Step 1: Verify the BizTalk RFID configuration
To verify the BizTalk RFID configuration, follow these steps:
- Start the BizTalk RFID Manager.
- Under RFID Services Administration, right-click the server that you want to view, and then click Properties.
- Verify the following settings for the server that is running IIS:
- The host IP address
Note By default, the host IP address is "localhost." - The port number for the Web site
- The Web site ID for the provider virtual directory
Step 2: Verify the IIS and ASP.NET configurations
Verify that the Web site is running
To verify that the Web site is running, follow these steps:
- Click Start, click Run, type Inetmgr.exe, and then click OK.
- Expand the server that you want to view, and then click Web Sites.
- In the details pane, verify that the Web site that you identified in the "Step 1: Verify the BizTalk RFID configuration" section is running.
Verify that the virtual directory exists in IIS Manager
Verify that the virtual directory for the provider exists in IIS Manager. Additionally, verify that the binary files for the provider are in the Bin folder.
Note You can determine the virtual directory for the provider by inspecting the provider .log file. By default, the provider .log file is located in the Microsoft BizTalk RFID\Providers\
ProviderName folder. The .log file contains an entry that resembles the following:
7| Info|041807 23:19:49|Current app pool is Acme1e6d0064-4b77-493f-8373-9ee8f4609dee|[Acme]
7| Info|041807 23:19:49|Current vdir is Acme1e6d0064-4b77-493f-8373-9ee8f4609dee|[Acme]
If the virtual directory does not exist in IIS Manager, delete the provider. Then, add the provider again. If the binary files for the provider do not exist in the Microsoft BizTalk RFID\Providers\
ProviderName\Bin folder, copy the files to the folder manually or delete the provider. Then, add the provider again.
Verify that anonymous authentication is enabled
The BizTalk Rfidservices.exe process uses the
wsHttpBinding binding to communicate with the IIS W3wp.exe process. In this scenario, anonymous authentication must be enabled and working on the virtual directory for the provider.
IIS may use another authentication method if anonymous authentication is not working correctly and if multiple authentication methods are enabled. To prevent this issue, enable only anonymous authentication for the virtual directory. To do this, follow these steps:
- Click Start, click Run, type Inetmgr.exe, and then click OK.
- Expand the computer name, expand Web Sites, and then expand the Web site that you identified in the "Step 1: Verify the BizTalk RFID configuration" section.
- Right-click the virtual directory for the provider, and then click Properties.
- On the Directory Security tab, click Edit under Authentication and access control.
- Click to select the Enable anonymous access check box.
- Click to clear all the check boxes under Authenticated access, and then click OK.
Verify that IIS 6.0 is configured to run in native mode
Because BizTalk RFID uses the IIS 6.0 worker process model to host providers, configuring IIS to run in IIS 5.0 isolation mode is not supported. To verify that IIS 6.0 is configured to run in native mode, follow these steps:
- Click Start, click Run, type Inetmgr.exe, and then click OK.
- Expand the computer name, right-click Web Sites, and then click Properties.
- On the Service tab, verify that the Run WWW service in IIS 5.0 isolation mode check box is not selected.
Verify basic IIS 6.0 functionality
To verify that IIS is working as expected, create a simple HTML page. Then, open the HTML page in IIS Manager. For example, use the following code to create a simple HTML page:
<html>
<head>Hello World.</head>
<body> Page successfully returned from IIS.</body>
</html>
Verify that the ASP.NET 2.0 Web service extension is enabled
For BizTalk RFID to work correctly, you must enable the ASP.NET 2.0 Web service extension in IIS.
Notes- BizTalk RFID setup verifies that the ASP.NET 2.0 Web service extension is enabled. However, a provider may not start as expected if the ASP.NET 2.0 Web service extension is disabled after the BizTalk RFID setup process is completed.
- The beta version of ASP.NET 2.0 is not supported. If the beta version of the ASP.NET 2.0 is installed on the server on which BizTalk RFID is installed, you must uninstall the beta version. Then, install the release version of ASP.NET 2.0.
To verify that the ASP.NET 2.0 Web service extension is enabled, follow these steps
- Click Start, click Run, type Inetmgr.exe, and then click OK.
- Expand the computer name, and then click Web Service Extensions.
- Verify that the status for the ASP.NET 2.0 Web service extension is set to "Allowed".
Note If the ASP.NET 2.0 Web service extension does not appear in the list of Web service extensions, you may have to register the ASP.NET 2.0 Web service extension with IIS.
Verify that the ASP.NET 2.0 Web service extension is enabled for the virtual directory
The Rfidservices.exe process communicates with the W3wp.exe process by using the Microsoft Windows Communication Foundation (WCF) infrastructure. Therefore, the virtual directory must be running under ASP.NET 2.0.
To configure the virtual directory to run under ASP.NET 2.0, follow these steps:
- Click Start, click Run, type Inetmgr.exe, and then click OK.
- Expand the computer name, expand Web Sites, and then expand the Web site that you identified in the "Step 1: Verify the BizTalk RFID configuration" section.
- Right-click the virtual directory for the provider, and then click Properties.
- On the ASP.NET tab, click 2.0.50727 in the ASP.NET version list.
Verify that the .svc extension is enabled
For BizTalk RFID to work correctly, you must enable the .svc extension in IIS. To verify that the .svc extension is enabled, follow these steps.
Note By default, the .svc extension is enabled at the Web site level, and this setting is inherited by the virtual directories.
- Click Start, click Run, type Inetmgr.exe, and then click OK.
- Expand the computer name, expand Web Sites, and then expand the Web site that you identified in the "Step 1: Verify the BizTalk RFID configuration" section.
- Right-click the virtual directory for the provider, and then click Properties.
- On the Virtual Directory tab, click Configuration.
- Under Application extensions, verify that the .svc extension is listed. Additionally, verify that the .svc extension is mapped to the following file:
Drive:\Folder\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
Note Drive represents the hard disk on which Windows is installed, and Folder represents the folder in which Windows is installed.
Verify the WCF and IIS configuration
To verify that WCF and IIS are working as expected, follow these steps:
- Click Start, click Run, type Inetmgr.exe, and then click OK.
- Expand the computer name, expand Web Sites, and then expand the Web site that you identified in the "Step 1: Verify the BizTalk RFID configuration" section.
- Click the virtual directory for the provider.
- In the details pane, right-click the .svc file, and then click Browse.
When you browse the .svc file in IIS Manager, you should receive a message that resembles the following:
This is a Windows� Communication Foundation service.
Metadata publishing for this service is currently disabled
If you receive a "Service Unavailable" error message when you try to browse the .svc file, use the following methods to troubleshoot the error message:
- Verify that the application pool for the virtual directory is running.
- Remove all unnecessary ISAPI filters from the Web site. Additionally, remove all unnecessary ISAPI filters at the Web site root.
- Use the Process Monitor utility to create a Process Monitor log. Then, inspect the log for "Access Denied" errors.
If you receive an "Error 401.3" error message when you try to browse the .svc file, use the Process Monitor utility to create a Process Monitor log. Then inspect the log for "Access Denied" errors. If the log contains an "Access Denied" error for the IUSR_
ComputerName account, follow these steps:
- Click Start, click Run, type Inetmgr.exe, and then click OK.
- Right-click the virtual directory for the provider, and then click Properties.
- On the Virtual Directory tab, click Configuration.
- Under Application extensions, click .svc, and then click Edit.
- Click to clear the Verify that file exists check box, and then click OK.
- Restart IIS.
Step 3: Verify the Windows SharePoint Services configuration
When the IIS Web site that hosts the provider is extended into Windows SharePoint Services, you may experience HTTP 404 errors when you try to access a file in the Web site or in the virtual directory. When this issue occurs, the provider will fail at startup.
To resolve this issue, exclude the virtual directory for the provider from Windows SharePoint Services. To do this, follow these steps.
- Start SharePoint Central Administration.
- Under Virtual Server Configuration, click Configure virtual server settings.
- Click Default Web Site, or click the Web site for the provider that has been extended by Windows SharePoint Services.
- Under Virtual Server Management, click Define managed paths.
- Under Add a New Path, type the name of the virtual directory for the provider in the Path box, click to select the Excluded path check box, and then click OK.
Note When you type the name of the virtual directory for the provider, type the name of the virtual directory as it appears in IIS Manager.
After you exclude the virtual directory for the provider from Windows SharePoint Services, you may receive an error message that resembles the following when you try to browse the .svc file in IIS Manager:
An error occurred loading a configuration file: Access to the path 'c:\inetpub\wwwroot\web.config' is denied.
To resolve this issue, follow these steps:
- Open the InetPub\WWWRoot folder.
- Right-click web.config, and then click Properties.
- On the Security tab, click IIS_WPG, click to select the Read check box, and then click OK.
Note If the IIS_WPG group does not appear under Group or user names, click Add, type IIS_WPG, and then click OK.