Compartilhar via

Banking Alerts Installation, Deployment, and Known Issues

  • Artigo
  Microsoft Speech Technologies Homepage

This topic describes installing the Banking Alerts reference application, deploying Banking Alerts to Microsoft Speech Server (MSS), and known issues concerning Banking Alerts.

Installing Banking Alerts

To install the Banking Alerts application, first install the prerequisite software, and then install the Banking Alerts software.

Install Prerequisite Software

Before installing the Banking Alerts reference application, install the following prerequisites (in any order):

  • Either the Microsoft Speech Application SDK Version 1.1 (SASDK) Sample Applications and Documentation
    - or -
    The complete SASDK
  • Microsoft SQL Server 2000, Service Pack 3a, Developer Edition or Evaluation Edition
  • Microsoft Message Queuing (MSMQ)

Note  To use Banking Alerts with Telephony Application Simulator (TASim), install MSMQ on the same computer as the Banking Alerts reference application. For a computer running Windows Server 2003, see Step 3 of the instructions explaining how To deploy Banking Alerts to MSS.

To install MSMQ on a computer running Windows XP

  1. In Control Panel, double-click Add or Remove Programs.
  2. Click Add/Remove Windows Components.
  3. Select Message Queuing, click OK, and click Next.
  4. Click Finish, and then close the Add or Remove Programs window.

After the previously listed prerequisites are installed, install the following prerequisites in the order listed:

  1. Microsoft SqlXml 3.0, Service Pack 3 (SP3)
  2. Microsoft SQL Server Notification Services (SSNS) Standard Edition Version 2.0, Service Pack 1

Remarks

  • See Microsoft Speech Application SDK Installation for information on installing the SASDK.
  • When installing SQL Server 2000, the Installation Definition window of the installer prompts the user to select an installation type. Select Server and Client Tools as the installation type. In the Instance Name window of the installer, verify that the Default check box is selected before continuing the installation. After installing SQL Server 2000, start the server before installing Banking Alerts. Visit the SQL Server 2000 Evaluation Edition page to download an evaluation edition of SQL Server 2000.
  • When installing SqlXml 3.0 SP3, the user may be prompted to install Microsoft SOAP Toolkit 2.0 SP2. The toolkit is not a requirement for Banking Alerts, and the message can be safely ignored. Visit the SqlXml 3.0 Service Pack 3 (SP3) page to download SqlXml 3.0 SP3.
  • See How to Obtain SQL Server Notification Services for information on obtaining SSNS.
  • Installing Banking Alerts on a computer that hosts Active Directory is not supported.
  • Visual Studio .NET 2003 is not a prerequisite for installing and running Banking Alerts. However, because the source code for Banking Alerts is contained in a Visual Studio .NET 2003 solution file, developers who want to view the source code must also have Visual Studio .NET 2003 installed.

Install Banking Alerts Software

After the prerequisite software is installed, ensure that SQL Server is running, and then use the following procedure to install the Banking Alerts reference application.

To install the Banking Alerts reference application software

  1. Go to the Banking Alerts directory located on the SASDK Version 1.1 CD at:

[CD_Drive:]\Redistributable Installers\Banking Alerts Reference Application

  1. Double-click setup.exe and follow the Installation Wizard instructions.

Remarks

Windows Server 2003 installs Internet Explorer Enhanced Security with the security settings for all Internet sites set to High. This causes Internet Explorer to display a security dialog when accessing Web sites. Banking Alerts connects to a simulated telephony server, TASim, on the host computer, which simulates an Internet-based telephony server connection. In order for TASim to function correctly, the base URL for the host computer must be added to Trusted Sites for Microsoft Internet Explorer.

To add the host computer's base URL to Trusted Sites for Windows Server 2003

  1. Start Microsoft Internet Explorer.

  2. From the Tools menu, select Internet Options.

  3. In the Internet Options dialog box, select the Security tab.

  4. Select Trusted Sites.

  5. Click Sites....

  6. In the Trusted Sites dialog box, enter the following URL in the Add this Web site to the zone edit box and click Add:

    http://ComputerName

  7. Click OK to accept the change.

 

Deploying Banking Alerts

Before deploying Banking Alerts to MSS, first open the Banking Alerts Transaction Simulator page and submit a single bill on the account for Lee Oliver, and then launch a simulated telephony interpreter. Verify that submitting the bill generates an event, and that Banking Alerts assigns the event to the simulated telephony interpreter. These steps are important because they:

  • Verify that Banking Alerts is correctly installed and functioning.
  • Create the private queue referred to in step 2 of the deployment instructions that follow.

See Enter Transactions and Submit Bills to Trigger Alerts for instructions on using the Transaction Simulator. See Open a Telephony Interpreter for instructions on opening a simulated telephony interpreter.

To deploy Banking Alerts to MSS

  1. Set the number of outbound channels for the Telephony Interface Manager (TIM) to 5.

  2. Add the computer running TAS to the Access Control List (ACL) for the Web server's Private outboundcallrequests queue. Set the access permissions to allow:

    Delete

    Receive Message

    Peek Message

  3. Install Microsoft Messaging Queue (MSMQ) on the computer running Telephony Application Services (TAS).

    Note  The instructions provided in this step apply only to computers running Windows Server 2003 because TAS supports only Windows Server 2003.

  4. Set the outbound notification message queue path on the computer running TAS. Use the following value, where WebServerName is the name of the Web Server:

    FormatName:DIRECT=OS:WebServerName\private$\outboundCallRequests

  5. Add the Web Server to the list of Trusted Sites on the computer running TAS.

  6. Restart TAS.

 

The procedures for performing these steps are described below.

Set the number of outbound channels for the TIM to 5

Note  See the documentation provided by the TIM software manufacturer for instructions on how to set the number of outbound channels. Ensure that the sum total of outbound channels plus inbound channels allocated using the TIM software does not exceed the total number of channels available.

Add the computer running TAS to the ACL for the Web server's queue

  1. On the Web server, right-click My Computer, and then click Manage.

  2. Expand Services and Applications, expand Message Queuing, expand Private Queues.

  3. Right-click outboundcallrequests, click Properties, and then click Security.

  4. Click Add. In the text box labeled Enter the object names to select, enter the following, where DOMAIN is the name of the network domain, and TelServerName is the name of the computer running TAS:

    DOMAIN\TelServerName$

  5. Click OK.

  6. In the outboundcallrequests Properties window, select the newly added user, and set the following permissions:

    Delete

    Receive Message

    Peek Message

  7. Click OK, and then close the console window.

Install MSMQ on the computer running TAS

  1. In Control Panel, double-click Add or Remove Programs.

  2. Click Add/Remove Windows Components.

  3. In the Windows Components Wizard, select Application Server, and then click Details.

  4. Select Message Queuing, click OK, and then click Next to complete the installation.

  5. In Control Panel, double-click Administrative Tools, and then double-click Computer Management.

  6. Expand Services and Applications, and then click Services.

  7. Right-click Message Queuing in the services list, and then click Properties.

    Note  Be sure to right-click the Message Queuing service in the services list on the right side of the window. Do not confuse it with the Message Queuing folder in the tree view.

  8. Click the Recovery tab, set the first, second, and subsequent failures to Restart the Service, and then click OK.

Set the outbound notification message queue path on the computer running TAS

  1. On the computer running TAS, click Start, select Programs, select Microsoft Speech Server 2004, and then click MSS Management Console.

  2. Expand Microsoft Speech Server, and click Default.

  3. In the list of servers in the pane on the right side of the console, right-click the name of the computer running TAS, click Properties, click Telephony Services Configuration, and then enter the following in the Notification Message Queue text box, where WebServerName is the name of the Web server:

    FormatName:DIRECT=OS:WebServerName\private$\outboundCallRequests

    Note  When cutting and pasting this string into the Notification Message Queue text box, ensure that no trailing space is included. A trailing space at the end of this string will cause the message queue to be unrecognizable.

  4. Click OK, and then close the console window.

Add the Web server to the list of Trusted Sites on the computer running TAS

  1. On the computer running TAS, click Start, select Programs, select Microsoft Speech Server 2004, and then click MSS Management Console.
  2. Expand Microsoft Speech Server, and click Default.
  3. Right-click the name of the computer running TAS, select All Tasks, and then click Configure Trusted Sites.
  4. Click Add and enter the following URL, where WebServerName is the name of the Web server: http://WebServerName
  5. Click OK twice, and then close the console window.

Restart TAS

  1. On the computer running TAS, click Start, select Programs, select Microsoft Speech Server 2004, and then click MSS Management Console.
  2. Expand Microsoft Speech Server, and click Default.
  3. Right-click the name of the computer running TAS and select Restart.
  4. After the Service Status column indicates that the computer running TAS is Running, close the console window.

 

Banking Alerts Known Issues

This section lists known issues, explanations, and suggested workarounds for problems that developers may encounter using the Banking Alerts setup (including installation, removal, and repair), or when running Banking Alerts.

  • Problem:
    Running the Banking Alerts installer produces either "Error 1303" or "Error 1001" during setup.

    Solution:
    Restart Internet Information Services (IIS) and run the installer again.

    To restart IIS

    1. Go to Start and click Run.
    2. In the Run command window, type iisreset.
    3. Click OK.

  • Problem:
    When a new user is added using the New Customer Enrollment page in one Internet Explorer window while the Transaction Simulator is running in a different Internet Explorer window, the new user does not appear in the Select user drop-down list box of the Transaction Simulator page. Clicking the Refresh button in the Internet Explorer window that is running the Transaction Simulator does not resolve this problem.

    Solution:
    Click the "Reload this page" link on the Transaction Simulator page to force the Banking Alerts application to reread information in the Banking Alerts database and display the new user in the Select user drop-down list box.

  • Problem:
    Under certain circumstances, events fail to appear in the Banking Alerts Queue Monitor after transactions are submitted in the Transaction Simulator. This can happen if Microsoft SQL Server Notification Services (SSNS) is installed before installing Microsoft .NET Framework 1.1.

    Solution:
    To correct this problem, do the following:

    1. In Control Panel, click Add or Remove Programs and remove the following programs:
      • Microsoft .NET Framework (English) v1.0.3705. Do not uninstall Microsoft .NET Framework 1.1 if it is already installed.
      • Microsoft SQL Server Notification Services 2.0 Service Pack 1
      • Banking Alerts
    2. If Microsoft .NET Framework 1.1 is not already installed, install it.
    3. Reinstall Microsoft SQL Server Notification Services 2.0 Service Pack 1.
    4. Restart IIS.
    5. Reinstall Banking Alerts.

    To restart IIS

    1. Go to Start and click Run.
    2. In the Run command window, type iisreset.
    3. Click OK.

  • Problem:
    The Banking Alerts Reference Application Setup may fail with the following error:

    There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.

    Solution:
    If SSNS is installed without the Engine, Client, or Database Components, the Banking Alerts installation will fail.

    Ensure that a supported version of SQL Server and SqlXml are installed, and then reinstall SSNS with all required components. See the installation prerequisites listed previously.

  • Problem:
    When attempting to repair the Banking Alerts installation, the following error message appears:

    There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.

    Solution:
    Instead of repairing the Banking Alerts installation, do the following:

    1. In Control Panel, click Add or Remove Programs and remove Banking Alerts.
    2. Restart IIS.
    3. Reinstall Banking Alerts.

  • Problem:
    When using the Banking Alerts Reference Application on a computer running Windows XP an HTTP Error 403 (forbidden) may occur.

    Solution:

    The version of IIS that is included in Windows XP is limited to ten connections. Due to the complexity of the Banking Alerts Reference Application, running the application on this Operating System may cause IIS to reach the ten-connection limit and refuse all subsequent connection requests until the service is restarted.

    To work around this problem, it may be necessary to bypass proxy servers on your network.

    To bypass proxy servers on your network

    1. Open Internet Options in Control Panel
    2. Click the Connections tab and click the LAN Settings… button.
    3. Select the check box for Bypass proxy server for local addresses
    4. Click OK

  • Problem:
    On computers that are not joined to a domain (computers that are a member of a workgroup), when a user starts Queue Listener, Queue Listener starts, and then stops and returns the following error:

    (35, 1) MSMQueueInfo: Access is denied.

    Solution:
    Queue Listener is a component of Banking Alerts. The architecture of Banking Alerts assumes a distributed, networked environment, and thus Banking Alerts and its components are not supported on computers that are not joined to a domain. Work around this issue by installing Banking Alerts on a computer that is a member of a domain.

  • Problem:
    Certain outbound notifications do not appear in the Triggered Call Queue (TCQ) after setting a delivery time for the notification by passing a DateTime object to the DeliverBefore method of the callRequestInfo object. In this scenario, the DateTime object contains a time relative to the DateTime.Now property as in the following example:

    callRequestInfo.DeliverBefore(DateTime.Now.AddHours(6))

    Solution:
    The callRequestInfo object is a member of the Tcq object. The Tcq object uses UTC (GMT) time to calculate time stamps. In contrast, the value of the DateTime.Now property is based on the host computer's local time setting. If the number of hours you add to the delivery time results in a negative value based on UTC time, the outbound notification is not added to the TCQ. For example, if the host computer is set to use Pacific Time (which is UTC -7 hours) and you add 6 hours to the delivery time, the Tcq object calculates the delivery time to be -1 hour (UTC -7 + 6 = -1 hour).

    Call the AddHours method on the DateTime.UtcNow property to set the delivery time as in the following example:

    callRequestInfo.DeliverBefore(DateTime.UtcNow.AddHours(6))

See Also

For information on administering TAS with MMC, see the following topics in the MSS documentation:

  • Administering Telephony Application Services
  • Defining TAS Configuration Settings