Error message generating report: Could not find file "C:\Program Files (x86)\Bentley\WaterCAD\x64\QuadrantCurvesPredefined.txt"

Product(s): WaterGEMS, WaterCAD
Version(s): 10.02.00.XX
Area: Modeling

Problem

When trying to print a report from the Pump Definition dialog, the following error message occurs:

System.IO.FileNotFoundException: Could not find file "C:\Program Files (x86)\Bentley\WaterCAD\x64\QuadrantCurvesPredefined.txt".

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
...

Solution

This known issue (defect # 998429) occurs because of missing files related four-quadrant curves in the installation folder. While four-quadrant curves are not used in WaterGEMS and WaterCAD, there is a Transient tab in the Pump Definition for times that a model might be opened in HAMMER to run a transient analysis.

This issue has been resolved starting with CONNECT Edition Update 3 (10.03.00.69). For information on upgrading, see this article.

For older versions, you can use the following workaround:

1) Find a copy of the files QuadrantCurves.txt and QuadrantCurvesPredefined.txt. If you have HAMMER installed, you can find these files at C:\Program Files (x86)\Bentley\HAMMER. If you don't have these files, you can download then from this link (must be signed in first.) Alternatively, you can contact Bentley Technical Support to get these. 

2) Once you have these files, browse to C:\Program Files (x86)\Bentley\WaterCAD or C:\Program Files (x86)\Bentley\WaterGEMS and copy the files to this location. Also open the "x64" folder and copy the files there as well.

3) Once that is done, restart the product and the error should no longer occur.

Recommended
Related