This topic lists the known issues for D3 Windows 10.2.
For a list of current known issues, refer to the Customer Service Discussion Forums at:
The what command displays an incorrect value for the amount of memory installed.
When upgrading from D3 9.2.x, the D3 10.2 Client installer leaves some old 9.2.x files installed on the machine. These can be safely deleted.
If you need to create more than 225 indexes on a file that came from a release prior to 10.2, then the account must be saved and restored prior to creating the additional indexes.
In D3 Windows 10.2, FSI to FSI communication is restricted to 10.2 releases. It is not possible to communicate from a 10.2 system to system with a release prior to 10.2. Conversely, a system running a release prior to 10.2 cannot communicate with a 10.2 system.
As of D3 Windows 9.2, both a case sensitive and a case insensitive index can exist on the same correlative. Because of this new ability, the index casing for a root statement must match the index casing of the Basic program in order for the Basic program to find the index. For example:
If you are running a Basic program with “casing off” (the default) and you attempt to access an index with a root statement, the index must be a case insensitive index in order for the root statement to succeed.
If you are running a Basic program with “casing on” and you attempt to access an index with a root statement, the index must be a case sensitive index in order for the root statement to succeed.
Previous to D3 Windows 9.2, the Basic program would find the index regardless of the index case.
This behavior does not apply to numeric indexes.
When using FSI HotBackup, do not encrypt a file in the FSIDM account if that file is going to be replicated to the secondary server. Doing so will result in incorrect data being written to that file in the FSIDM account on the secondary server.
If the set-dptr command is run on an encrypted file, the last characters of attribute 1 in the D-pointer for the file are updated, causing any subsequent decrypt-file calls to fail. As such, you should never run the set-dptr command on an encrypted file (that is, always use set-dptr prior to encryption). Should you need to recover from such a situation, you must run the encrypt-file command followed by the decrypt-file command.
If you are using OpenDB and you are upgrading to D3 Windows 10.2, you must also upgrade to OpenDB 3.4. OpenDB 3.4 is available in versions that allow using 32–bit ODBC drivers or 64–bit ODBC drivers. Contact your sales representative or customer support for details on obtaining the upgrade to OpenDB 3.4.
If you are using FlashConnect and you are upgrading to D3 Windows 10.2, you must also upgrade to FlashConnect 3.9 and the FlashConnect 3.9.1 account.
All servers on the network, whether a D3 Windows server or D3 Windows client is installed, MUST be running identical Microsoft Service Packs and/or identical Microsoft patches. Certain Microsoft Service Packs/patches that fix security issues with RPC buffer overruns can interrupt communications from FSI to FSI if one system has a Service Pack/patch and the other system does not.
Because shutting down Windows while D3 Windows is running may cause a loss of overflow, it is recommended that you ensure that D3 Windows is shut down prior to shutting down Windows.
In certain instances, printers may not be available to D3 until initialized by Windows, depending on the initialization string that is required by the printer driver.
ISQL is not supported on D3 Windows.
Mapped network drive resources may not be available to D3, even if the user that mapped the drive in Windows is the same user that is starting D3. If this is the case, map the drive directly from D3 using the net use command.
Ensure that these commands work from a MS-DOS prompt to verify that your command syntax is correct and that the drive can be successfully mapped.
Avoid any prompts requiring input as they will hang your D3 session when attempting to map the drive using !net use from TCL.
net use { drive letter:} \\{ machine name}\{ share name} { password}
/user:{ domain\user name}
net use I: \\svr-sup\robert password /user:admin\rlb
Once the resource is mapped from a MS-DOS prompt (with no prompts for input), you can delete the resource from the MS-DOS prompt. For example:
net use I: /delete
Then map it from TCL by inserting a ! before the command. For example:
!net use I: \\svr-sup\robert password /user:admin\rlb
You can set up a user on the destination system with a generic name and password and add this command to the user-coldstart macro to ensure the resource is properly mapped and available to D3 every time D3 is started.
For Windows 7 and Windows Server 2008, a new Windows RPC interface restriction (which is enabled by default) disallows the use of the following passthrough syntax:
fsi:[//machine.name]account,file,
To work-around this restriction, create a new DWORD Value named RestrictRemoteClients with a value set to 0 (zero )under the following registry key:
HKLM\Software\Policies\Microsoft\WindowsNT\RPC
For Windows 7, 2008 and later operating systems, you may encounter the message rpc4ns.dll is not supported. This is just a warning and does not affect the running of D3. As such, this message can be ignored.
Numeric indexes in the VME (both UNIX and Windows) only support integer numeric indexes, which includes dates that are stored in internal format. If you wish to create numeric indexes on decimal numbers, numeric data must be stored in scaled internal format (that is, with no decimal or thousands separators). This ensures correct behavior when accessing numeric indexes in the VME.
Starting with D3 9.1, the InstallShield application used to install and uninstall D3 requires that the entire D3Programs directory be removed during an uninstall. Because of this, any programs or files you have added to the directory will be deleted. As such, it is highly recommended that you backup these files prior to uninstalling.
Any function that returns a pointer, such as %malloc, must be type cast as a char*. For example:
x=char(*)%malloc(size)