ID: Q182448
The information in this article applies to:
This article contains the most frequently asked questions (FAQs) on the Microsoft Internet Finance Server Toolkit (MIFST).
Q: I just installed MIFST, and I get an error in the Ping tool. (April 3, 1998)
A: Try the following procedure. Section 2.5.4 in installing the translation server omits this step:
Using Regedt32.exe, open the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib.
The documentation was corrected in MIFST and 1.01
Q. I have trouble stopping and restarting IIS when MIFST has been running. (April 3, 1998)
A1. Using the Event Viewer can hold the Ofx_audit_com.dll open until the Event Viewer is closed. This may prevent copying over another version of the DLL, and also impact stopping and restarting IIS since the DLL does not unload correctly.
A2. Ofx_Counters_com.dll does not unload correctly if the SNMP service is running. This may cause problems stopping and starting IIS. To be sure that IIS is completely stopped before restarting, use Task Manager and verify that the Inetinfo.exe process has ended. This may make restarting the WWW service work correctly.
Q: Sockets Resource Manager sample code is not included in the product. (March 23, 1998)
A: It is available upon request (a Knowledge Base article is pending).
UPDATED! Q: Requests from Quicken are rejected by MIFST. (May 15, 1998)
A: Quicken uses a linefeed only (instead of carriage-return/linefeed) to separate the OFX headers. This was fixed in MIFST 1.01; OFX headers that use only a linefeed as a separator are now accepted by MIFST.
Q: How do I use the "Validate FII OFX Response" option? (March 23, 1998)
A: This will cause a 400 application error to be returned if there are any errors in the response, and the response to be written to the log file. You can use the Parser Shell Tool to see exactly what the error is.
Q: Where do I get the Parser Shell Tool? (March 23, 1998)
A: Download the tool from the following Web site:
http://www.microsoft.com/industry/finserv/mifst/tools.htm
A: MIFST 1.0 was designed and tested for IIS 3.0. Testing with IIS 4.0 has begun, and no problems have been found so far.
Q: Can I install the Web Development Kit and Translation Server on the same system? (March 23, 1998)
A: This is an unsupported configuration. It is not tested for, and most reports are that it does not work. Each component (Web kit, TS, and Security Server) must be on its own machine.
NEW! Q: Stopping the Web server, then restarting, may cause MIFST to go into Forced Pause mode. (May 15, 1998)
A: This can occur due to a DLL not unloading properly. To avoid, make sure that the Inetinfo.exe process terminates. In IIS3, shutting down the WWW, FTP, and Gopher services should cause INETINFO to stop. For IIS 4, use the command NET STOP IISADMIN to end the Inetinfo.exe process. Check Task Manager to make sure that the Inetinfo.exe process has ended.
NEW! Q: What is Forced Pause mode? It is preventing me from restarting my MIFST server. (May 15, 1998)
A: Forced Pause mode generally means that there is not enough disk space for the audit log, or that other problems are preventing the audit log from working. Freeing additional disk space, then stopping and restarting Inetinfo.exe, should allow you to clear the Forced Pause check box in the Gateway Administration Tool.
NEW! Q: The Getting Started Guide tells me to copy the Sqlsrv32.dll from my SQL Server system to the Translation Server, but the Sqlsrv32.dll on the Translation Server is newer than the one on the SQL Server system. Which one should I use? (May 15, 1998)
A: Use the latest version. If you installed OLEDBSDK 1.5 on the Translation Server, then you may have a more recent DLL than SQL Server.
NEW! Q: When I have Internet Explorer 4.0 installed on the Security Server, the number of connections to my translation server is limited to two. I made the registry changes described in the MIFST 1.01 Release Notes, but it did not help. How do I remove this limitation? (May 15, 1998)
A: The Release Notes omit the step of granting permission to the registry entries to the anonymous MIFST account. Without doing this, the registry entries will likely have no effect. Use RegEdit32 to grant full access to these registry keys to the anonymous MIFST account.
NEW! Q: OFX Ping fails when I use HTTPS, but not when I use HTTP. I have a valid certificate on the Translation Server (or Security Server). (May 15, 1998)
A: If the error that OFX Ping displays is a 12038 error from HttpSendRequest, it may be that the Common Name (CN) used in your server certificate does not match the server name used to access the Translation or Security Server. For instance, if you obtained a certificate with a CN of your server's Internet domain name, but are accessing the server from your local network using a different name, you may encounter this error.
Q: How do I get the Translation Server to use my custom FII component? (March 23, 1998)
A: There are two registry settings to set. The following lines can be placed in a .reg script file, substituting the CLSIDs of your custom FII. Double-clicking the .reg file causes the new registry settings to be entered:
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OFX_Gateway]
"FI_Interface_Component"="{EFABEA05-9140-11D0-B091-00AA006C588C}"
"FI_Interface_Module"="{EFABEA07-9140-11D0-B091-00AA006C588C}"
A: You may have seen this function documented in an SDK Errata. There is a known memory leak that occurs any time this function is called. Get_Entity_Path's functionality can be achieved by the use of other Parser object functions, and it should not be used at this time.
UPDATED! Q: Why does the parser hang (in an infinite loop) after returning from the FI frame? (May 15, 1998)
A1: This may be due to an invalid aggregate tag. Make sure that all aggregate objects are set to the proper name.
A2: This problem was resolved in MIFST 1.01.
Q: Why don't the SDK Samples compile? (March 23, 1998)
A1: Set Visual C++ directories to point to necessary libraries and header files.
A2: Remove the old SDK before installing new one, to make sure that old files are not being used.
Q: How can I turn off MIFST Crash Recovery? (March 23, 1998)
A: You can't. When using Lite Synchronization, Crash Recovery is required by the OFX Specification. When using Full Synchronization, it is not required, but the current version of MIFST offers no way to disable it. See pages 40 - 43 of the Gateway Development Guide and section 6.10.2 of the OFX Specification.
UPDATED! Q: How can I add a custom installation OCX to the Gateway Administrator, as mentioned on page 58 of the Gateway Development Guide? (May 15, 1998)
A: At this time, no documentation is available for this. This ability has not been fully implemented at this time, and it is unlikely it will be added in the future.
Q: How can I use Directory Services to store and retrieve my custom FII information? (March 23, 1998)
A: Within the FII component, you can use the Directory Services component. From outside the FII, you would need to directly call the stored procedures in the Directory Services database. There is no SDK available for the stored procedures at this time.
Q: Why does the ping tool terminate when a response is received? (March 23, 1998)
A: If the response is greater than 65K (the maximum size for a text box), this will occur.
Q: IParser::Validate() succeeds on a response that MIFST rejected as an error. Why? (March 23, 1998)
A: The successful return just means that the function did not encounter an unexpected error; it does not indicate that the response itself is valid OFX. To test for errors, you must call IParser->get_Validate_Error_Count().
UPDATED! Q: When I correct a password in a request and resend it, the Translation Server rejects the request. Why? (May 15, 1998)
A1: This problem was fixed in MIFST 1.01. In the case of an incorrect password, the response will not be stored in Crash Recovery. If the problem occurs on a site that has not been upgraded, use the procedure below to recover.
A2 : The previous request with the incorrect password is still in Crash Recovery. If the new request has the same NEWFILEUID, the CRC value for the new request will not match that of the previous request (since the passwords are different). This is an ambiguity in the OFX specification, and a resolution is being worked on. Once the Crash Recovery cleanup tasks have removed the previous request, the new one will succeed. For development purposes, you run the following ISQL commands to remove just the problem request from Crash Recovery, assuming that you know the NEWFILEUID (substitute this where you see NEWFILEUID below):
1. In the Crash Recovery List Database, the following will return the
Server and Database in which the data is stored. Make note of this.
CrashRecoveryIndexGet @FILEUID = "NEWFILEUID"
the entry from the Crash Recover list database:
CrashRecoveryIndexDel @FILEUID = "NEWFILEUID"
database the following will delete the actual Crash Recovery Database
entry:
OFX_Header_Del @FILEUID = "NEWFILEUID", @DeleteFlag="Y"
A1: The queue must be non-transactional. Verify that you did not check this box when creating the queue.
A2: The following two lines in CCustomAuditQueue::Initialize() are in the wrong order. Reverse them to avoid the assertion:
CEventLoggerX::Register();
CEventLoggerX::Set_Instance( _Module.GetModuleInstance() );
A: This can occur if the Parser is not registered properly. Running RegSvr32 on OFX_Parser_COM.dll may fix this.
NEW! Q: The SignedOn property of the Base object is always true after calling Base.SignOn(), even if the signon fails. Why is this? (May 15, 1998)
A: This is a bug in the OFXDataAccess object. You can easily reproduce this functionality for yourself, by checking Err.Number after calling SignOn(), and setting a Session variable to indicate success or failure.
Q: Does the IOFXParseAndBuild interface support crash recovery? How do you get/put OLDFILEUID/NEWFILEUID information? (March 23, 1998)
A: The client-side IOFXParseAndBuild interface does not support crash recovery, so you cannot specify OLDFILEUID/NEWFILEUID.
Q: In the OFX Headers, the Web client requests are hard-coded with SECURITY TYPE = NONE. Will this be a problem if your Gateway is expecting a different security type? (March 23, 1998)
A: This will be fixed in the next version of MIFST.
Q: The Web client requires a valid SSL connection with the OFX server. How do I handle this if I don't want to test with one? (March 23, 1998)
A: If your OFX server does not have a valid certificate, you will need to follow the instructions on page 8 of the Web Development Guide to turn off the SSL verification.
Q: In the ParseAndBuild object of the Web client, the pointer pofxDoc- >pofxBankingRSV1->psyncrs->ptrnrs is not valid [is null] after the Parse() method call. Why? (March 23, 1998)
A: This is a bug in this release of MIFST. The next element in the structure, pofxDoc->pofxBankingRSV1->psyncrs->szINCIMAGES, will contain the pointer to ptrnrs.
Additional query words: kbmifst
Keywords : kbfaq
Version : WINNT:3.0
Platform : winnt
Issue type : kbprbLast Reviewed: June 8, 1998