Software: Support
Common Problems
PFC2D and PFC3D Version 4.0 report a FishTank-related Startup Error
At startup, if a problem occurs when the FishTank variable is set, an error will be reported in the program, similar to the one shown below.
The code is still FULLY FUNCTIONAL and operable in every respect when this error is reported. The aspect of program operation that this situation affects is the use of the %fist% variable, which is a convenience — and not a necessity — for calling FISH files.
This error occurs if the file "fist_new.dvr" is not in the location specified in the file "fist_load.dat."
Diagnosing and correcting this situation to avoid seeing the error message at startup can be done using the following steps.
1. Find the file "fist_load.dat". This is located as follows:
c:\program files\itasca\pfc2d400\fist_load.dat
[PFC2D, 32-bit version on a 32-bit machine, or 64-bit version on a 64-bit machine]
c:\program files (x86)\itasca\pfc2d400\fist_load.dat
[PFC2D, 32-bit version on a 64-bit machine]
c:\program files\itasca\pfc3d400\fist_load.dat
[PFC3D, 32-bit version on a 32-bit machine, or 64-bit version on a 64-bit machine]
c:\program files (x86)\itasca\pfc3d400\fist_load.dat
[PFC3D, 32-bit version on a 64-bit machine]
IMPORTANT: the locations shown above correspond to the default installation locations for PFC2D and PFC3D. In the event the user has changed this location at the time of installation, it will be necessary in step 3. to replace the portion of the paths above corresponding to "c:\program files\itasca" with the location the user specified at the time of installation.
2. Read the file "fist_load.dat" and determine if the file "fist_new.dvr" is in the location that it specifies. The contents of the file are the same for PFC2D and PFC3D. They are:
;fname: fist_load.dat %fist%, PFC2D/3D
;
; ===========================================================================
def ft_setenv
if dim = 2 then
environment('fist') = 'C:\\Program Files\\Itasca\\pfc2d400\\fist'
else
environment('fist') = 'C:\\Program Files\\Itasca\\pfc3d400\\fist'
end_if
end
ft_setenv
call %fist%\fist_new.dvr
; ===========================================================================
return
;EOF: fist_load.dat
Read the file and note that the "fist" variable has been set to:
c:\program files\itasca\pfc2d400\fist for PFC2D, and
c:\program files\itasca\pfc3d400\fist for PFC3D
3. If the file "fist_new.dvr" is not in the folder specified by the "fist" variable, then change the appropriate line(s) in the "fist_load.dat" file to specify the location of the "fist_new.dvr" file (hint: if the default installation path was changed, then the file will be located in the user-specified installation path plus the portion "pfc2d400\fist" OR "pfc3d400\fist"). You MUST use double slashes (\\) to separate folder names when specifying the path in the "fist_load.dat" file.
4. Try starting PFC2D or PFC3D again after "fist_load.dat" has been edited. If the error message still appears, contact Itasca for further assistance.
PFC2D and PFC3D 4.0 Startup
The above description of the error occurring at startup may be more fully understood by examining how PFC2D and PFC3D start, which is as follows.
When the program starts, if the working directory is the folder where the executable is located (and this is the case when using the shortcut on the "Start" menu), then the file "pfc3d.ini" that is also in that folder is automatically executed. This file calls "fist_load.dat", which is in the folder one directory level up from the folder that contains the EXE and INI files. The file "fist_load.dat", as seen above, performs a test to determine whether the currently executing code that called it is PFC2D or PFC3D. Based on the result of that test, it sets the "fist" variable to the path it expects to contain the FishTank that is appropriate to use. The last action performed by the "fist_load.dat" file is to call the file "fist_new.dvr", and note that the call is made using the "fist" variable (which is designated with the notation %fist%). The file "fist_new.dvr" first defines the function "ft_PrintVersion" that can be used to provide diagnostic information about the FishTank. Then it calls two FISH files, "fishcall.fis" and "udm_types.fis" (and note, if you examine "fist_new.dvr", that these calls are made using the %fist% variable), and then it executes the "ft_PrintVersion" function. So, this sequence is understood schematically:
Typically, the error that is under examination in this topic occurs inside "fist_load.dat" when a faulty path is designated for locating the "fist_new.dvr" file. It is this path that the user must manually fix by editing the "fist_load.dat" file to point to the proper location of the "fist_new.dvr" file.
An error dialog occurs during installation with a message like "Error 2753. The file 'drvinstlauncher.exe.B391C18A_...' is not marked for installation."
This error, shown in the dialog below, is a known, unresolved bug.
The image shown above is from a FLAC installation; this error may occur during installation of any Itasca code.
This error does not affect installation in any way. As can be seen, the only available reponse to the dialog is to dismiss it by pressing "OK". After this is done, the code installation will comlpete without error, and the code, upon completion of the installation, is fully operational. Users are advised to ignore this error and proceed with the use of their software without further delay.
An error dialog appears at startup with the message "This application has failed to start because the application configuration is incorrect. Re-installing the application may fix the problem".
The error occurs when the correct (or sufficiently up-to-date) version of the C++ runtime is not present. To fix the problem, visit the "Updates" page for your code. Review the page carefully and look out for any information involving a required C++ runtime update. Obtain the appropriate C++ runtime update as needed — note there are 32-bit and 64-bit runtimes, so be sure to obtain the correct one for your computer — install the update, and try your code again.
"The key Update utility (update.exe) reports "Cannot open PASSWORD.ICG" when I try to update."
On trying to update, an error occurs and is reported as shown below. Note in case depicted the program shows a failed attempt to update a FLAC3D key; however, a similar error can occur with any Itasca program. The critical indicator for this particular problem is when the program reports "Cannot open PASSWORD.ICG", as seen in the second line from the bottom.
With this problem, copy the folder that containes the Update utility AND the password.icg file to a new, unprotected location (for instance, "c:\temp") and try running the Update utility again from the new location.
Is there a way to check out the utilization of a network key (whether it is present, how many licenses are in use, etc.)?
Yes, by typing
http://ser.ver.ip.add:6002
into the address bar of a browser, where ser.ver.ip.add is the IP address of the server where the key is attached. If the server software is properly installed on the server, and the key is present and detected by the server software, a page indicating key usage will appear in your browser.
