5.

10
SUPPORT NOTES

TABLE OF CONTENTS

1.0 Overview ......................................................................................................................................... 7

Change Log ........................................................................................................................................................7
Applicable Software ......................................................................................................................................... 11
Software Downloads ........................................................................................................................................ 12

2.0 Current Bugs ................................................................................................................................ 13

Bug 51-01 – Error in 90.1 Baseline Fan Power Calculation ............................................................................ 13

2.1 Fixed Bugs ................................................................................................................................... 14

Bug 50-01 – Error in TimeWeightedOccupancy Calculation ........................................................................... 14
Bug 50-04 – Error Importing Certain Weather Files ........................................................................................ 15
Bug 50-05 – Psychrometrics Report Preheat Coil Outlet Incorrect ................................................................. 17
Bug 50-02 – Error in Publish to ECAT / Tag Export ........................................................................................ 18
Bug 50-03 – Problems in Space Data Converting Old Projects ...................................................................... 19
Bug 49-12 – Input Power for AC/WC Heat Recovery with Low Loads ............................................................ 21
Bug 49-01 – Some Air Systems Missing in Project Library List ...................................................................... 22
Bug 49-02 – Invalid OA Requirements Not Trapped for 62.1-2010 ................................................................ 23
Bug 49-03 – Plant Using Hi+Low Sequencing and Shared Tower Produces Incorrect Condenser Pump
Results ............................................................................................................................................................. 24
Bug 49-04 – Main Window List View is Blank ................................................................................................. 25
Bug 49-05 – Error: Cannot find tower record in database for record #0 ......................................................... 26
Bug 49-06 – Building Wizard Error 9 – Subscript out of Range ...................................................................... 27
Bug 49-07 – Building Simulation - Index out of bounds (Bad Electric Rate) ................................................... 28
Bug 49-08 – Example Problem Results Out of Sync with Archive .................................................................. 28
Bug 49-09 – GBXML Import Assigns Incorrect Windows / Doors ................................................................... 30

HAP Support Notes rev. 501_05 -- Page 1 of 218

 Bug 49-10 – Error Calculating DHRC Heat Recovery with Variable Speed Condenser Pump ...................... 31
Bug 49-11 – File not found: EW_AirSys_Base_05.2.gif .................................................................................. 32
Bug 48-01 – Error 91 When Simulating Chilled Water Plant ........................................................................... 33
Bug 48-02 – Error 3265 When Running Full Wizard Session ......................................................................... 33
Bug 48-03 – Error in Std 62.1 Calculation for PFPMBX Air Terminals ........................................................... 36
Bug 48-04 – Error in Std 62.1 Calculation for SFPMBX Air Terminals. .......................................................... 37
Bug 48-05 – Error on Vent Sizing Summary for Single-Space Systems Calculated per Std 62.1. ................. 38
Bug 48-06 – Error in Std 62.1 Calculation for 15 F Heating Delta-T ............................................................... 39
Bug 48-07 – Error 11: Division by Zero during System Design Calculations .................................................. 40
Bug 48-08 – Error in Std 62.1-2010 Calculations for VAV .............................................................................. 41
Bug 48-09 – A-Factor Button Obscures Other Inputs ..................................................................................... 43
Bug 47-01 – Error 6 Overflow for SHW Plant Design Calculations ................................................................. 44
Bug 47-02 – Air System Design Calculations Not Run Automatically for Generic Plants ............................... 45
Bug 47-03 – Error: Unable to load schedule data ........................................................................................... 46
Bug 47-04 – Error 91 ‘Object variable or with block variable not set’ When Loading an Existing Plant ......... 47
Bug 47-05 – Dehumidification Heating Coil not Correctly Recognized ........................................................... 47
Bug 47-06 – Air System Space List Shows Blank Line ................................................................................... 49
Bug 47-07 – Hot Water Plant Using Heat Pumps Erases Linked Geothermal Source ................................... 50
Bug 47-08 – Generic SHW Plants and Generic Changeover Plants Are Not Listed ...................................... 51
Bug 47-09 – Air System Cooling Capacity Control Option Spontaneously Reset........................................... 52
Bug 47-10 – Plant Secondary Pump Flow Displayed Incorrectly in Metric ..................................................... 53
Bug 47-11 – Remote Plant Secondary Pump Flow Saved Incorrectly in Metric ............................................. 54
Bug 47-12 – Insufficient Cooling for System without HW Coils ....................................................................... 55
Bug 47-13 – Error 440 Occurs During Plant Energy Simulation ..................................................................... 57
Bug 47-14 - HAP Encountered a Problem and Needs to Close – Tablet / Touch Screen .............................. 58
Bug 46-00 – 2PFC and 4PFC Terminals with Electric Heating Consume no Energy ..................................... 60
Bug 45-01 - "Error 380 - Invalid Property Value" ............................................................................................. 61

3.0 Common Errors – International Edition Issues.......................................................................... 63

Error e400 - Invalid Authorization Code .......................................................................................................... 63
Error 7 - Corrupt Header .................................................................................................................................. 64
Errors 106 and 109 .......................................................................................................................................... 65
Error 31 - Unknown Error Posted 21 ............................................................................................................... 67
Internal Error 201-M327A While Running AuthCode.exe ................................................................................ 68

3.1 Common Errors – North American Demo Version Issues ........................................................ 69

Troubleshooting 90-Day Demo Problems ....................................................................................................... 69
“The 90-Day Trial Period Has Expired. Please Contact Carrier” ..................................................................... 70
HAP and Block Load Demo Versions Cannot be Active on a Computer at the Same Time ........................... 71
Error e400 - Invalid Authorization Code .......................................................................................................... 72
Error 106 .......................................................................................................................................................... 73

HAP Support Notes rev. 501_05 -- Page 2 of 218

 Error 109 .......................................................................................................................................................... 74
Error 7 - Corrupt Header .................................................................................................................................. 75
Error 31 - Unknown Error Posted 21 ............................................................................................................... 76
Internal Error 201-M327A While Running Authcode.exe ................................................................................ 77

3.2 Common Errors – Installation ..................................................................................................... 78

Installation Problem: This Software Requires Service Pack 4 ........................................................................ 78
Installation Problem: You Must be the Administrator... ................................................................................... 79
Installation Aborted: Internal Error ................................................................................................................... 80
"Out of Disk Space" Error While Installing ....................................................................................................... 81
"SSNVC100.EXE Handle is Invalid" Error ....................................................................................................... 82
Installer Appears to Hang After copying COMDLG32.OCX ............................................................................ 83
"Apex True DBGrid" Error While Installing ...................................................................................................... 84
"This Patch Can Only be Used to Update Existing Installations" Error ........................................................... 86
"Dynamic Link Library WININET.DLL Could Not Be Found" Error .................................................................. 87
Unable to see Network Drives ......................................................................................................................... 88
“Fatal Error 3633 loading data: Can’t load DLL: MSJTER35.DLL”.................................................................. 91
Cannot Find HAP in Windows 8 Start Menu / Screen ..................................................................................... 92
Error: This Package Has Expired and Cannot Run ......................................................................................... 95
Cannot find EDDUVHS.EXE During Installation (Webroot Antivirus) ............................................................. 96
Signature is Corrupt or Invalid while Downloading .......................................................................................... 97

3.3 Common Errors – Program Startup ............................................................................................ 98

Carrier Programs Group Does Not Appear on Start Menu .............................................................................. 98
Can't Start Program. No HAP Icon Exists ....................................................................................................... 99
This Program is not Registered with Configuration Services ........................................................................ 100
"Missing Application or Project Related data" Error ...................................................................................... 101
Unable to Run File Integrity Checkers ........................................................................................................... 102
Error 429 While Starting Program ................................................................................................................. 103
"Initialization Has Failed" Error Upon Startup ................................................................................................ 104
"Can't Open Database Created with Previous Version" Error ....................................................................... 106
"Jet VBA File Failed to Initialize When Called" Error ..................................................................................... 107
Microsoft Installer Launches When Starting HAP ......................................................................................... 108
HAP Main Window not Visible on Startup ..................................................................................................... 114
Error 429 in frmMain CheckFileStatus While Starting HAP ........................................................................... 115
Error 429 in frmMain CheckFileStatus ........................................................................................................... 116
Error 3 While Creating New Project ............................................................................................................... 117
The Field is too Small to Accept the Amount of Data… Error ....................................................................... 118
Run-Time Error 372 During Startup ............................................................................................................... 119
About Windows User Account Control (UAC) Warnings ............................................................................... 121
Automation Error – The Network Name Cannot Be Found ........................................................................... 125

HAP Support Notes rev. 501_05 -- Page 3 of 218

 Error on Starting HAP - Missing File SSNSystemDefault17.RO ................................................................... 127
GetE20ConfigData – ActiveX Component Can’t Create Object .................................................................... 128

3.4 Common Errors – Program Operation ..................................................................................... 129

General Protection Fault When Editing Data................................................................................................. 129
Error Opening Weather Data ......................................................................................................................... 130
"Runtime Error 50003. Unexpected Error." ................................................................................................... 131
"Error in Calculate: Subscript Out of Range" While Running System Design Calcs ..................................... 132
Main Window Items Out of Synch with Project Data ..................................................................................... 133
Zero Lighting & People Loads Shown on Air System Design Load Summary .............................................. 134
Display Problems While Running HAP .......................................................................................................... 135
Error 429: ActiveX Component Can't Create Object ..................................................................................... 137
Error 429 While Retrieving HAP v4.0 Data .................................................................................................... 138
Error 429 While Retrieving HAP v3.2 Data .................................................................................................... 139
Error 429 While Saving Weather Data .......................................................................................................... 140
Error 429 While Loading Simulation Weather Data ....................................................................................... 141
Error 429 While Running System Design Calculations ................................................................................. 142
"TerSave: Could Not Open the File" Error When Viewing Reports ............................................................... 143
"Error 6" During System Design Calculations ................................................................................................ 144
"Error 6 in cAirSysAnnual DXEquipCalcs" ..................................................................................................... 145
How to Interpret Program Error Messages .................................................................................................... 146
Error 6 in cSimEngine Calculate .................................................................................................................... 148
"Failed to Load the Plant" Error When Editing Plants ................................................................................... 149
Error 364 When Requesting Reports ............................................................................................................ 150
Error 6 in cSimEngine ZoneAnalysis ............................................................................................................. 151
Common Pitfall Involving Plants Linked to a Building ................................................................................... 152
Error 6 in cDesignLoad AssignSystemSizing ................................................................................................ 153
Windows Installer Launches when Running HAP ......................................................................................... 154
Program Hangs When Requesting Reports on Windows NT........................................................................ 155
Energy Consumption for Dehumidification Reheat Not Calculated in Simulation ......................................... 156
The Object Invoked Has Disconnected from its Clients ................................................................................ 157
"The Changes You Requested to the Table Were Not Successful..." Error when Publishing Data .............. 158
"Error 0 in Calculate" During System Design Calculation for a VVT System ................................................ 159
Building Footprint Diagram Labels in Building Wizard not Readable ............................................................ 160
Tree Panel on Left Side of Main Screen is Not Responsive ......................................................................... 161
"Navigation to the Webpage has been Cancelled" Error When Displaying Help .......................................... 162
Boiler Plant Simulation Results Differ Between v4.5 and v4.6 ...................................................................... 165
Unable to see Network Drives When Saving a Project ................................................................................. 166
Error 521: Can’t Open Clipboard ................................................................................................................... 167
HAP Seems to Freeze (Window Off-Screen) ................................................................................................ 170

HAP Support Notes rev. 501_05 -- Page 4 of 218

 Dealing with Windows that are Located Off-Screen ...................................................................................... 171
HAP Main Window Location Problems in a Networked Installation .............................................................. 172
HAP “Not Responding” When Selecting Files or Printing (Antivirus) ............................................................ 173
Errors Loading gbXML – Missing SSNhapXMLAdapter53.mdb .................................................................... 175
“MAPI” Error Sending Email to Sales Engineer ............................................................................................. 176
Error 339 - Component or one of its dependencies not correctly registered: a file is missing or invalid....... 178
Text Cut-Off (Spaces Screen, Schedule Screen, etc.) .................................................................................. 182
Transfer Function Generation Failure can Corrupt Roof / Wall Inputs .......................................................... 183

3.5 Common Errors - Printer and Reports Operation .................................................................... 184

Problems Printing Huge Report Packages .................................................................................................... 184
Common Printer Workaround Procedures .................................................................................................... 185
Errors When Printing ..................................................................................................................................... 187
Air System Input Report contains Incorrectly Formatted Tables ................................................................... 189
Unable to View More than One Report in Report Viewer .............................................................................. 190
System Psychrometrics Report - No Data Points Plotted ............................................................................. 191

3.6 Common Errors – Data Management ....................................................................................... 192

Common Pitfall Retrieving From Previous Version ....................................................................................... 192
Project Folder Still Exists After Deleting Project ............................................................................................ 193
"Exception: Access Violation Has Occurred" ................................................................................................. 194
"Runtime Error 3343 - Unrecognizable Database Format" ........................................................................... 196
"The Field is too Small to Accept...Data..." Error ........................................................................................... 197
"Device Not Ready" Error While Opening Project ......................................................................................... 198
Error 32 While Opening a Project .................................................................................................................. 199
RegisterAppData While Saving a Project ...................................................................................................... 200
"Runtime Error 3024" While Opening a Project ............................................................................................. 201
"Database has Reached its Maximum Size" Error While Opening a Project ................................................ 202
"Type Mismatch" Error While Retrieving Archive Data .................................................................................. 203
Error 33 While Saving a Project .................................................................................................................... 204
“Could Not Lock File" Error 3050 When Opening Project ............................................................................. 205

3.7 Common Errors – Networks ...................................................................................................... 206

How to Convert from Standalone to Network Shared ................................................................................... 206
How to Convert From Network Shared to Standalone .................................................................................. 208
Configuring HAP for Dual Mode (Standalone and Network) Operation ........................................................ 210
How to Migrate Projects to a New Data Server ............................................................................................. 212

3.8 Common Requests and Information......................................................................................... 217

Status of ASHRAE Std. 140 Documentation & EPACT Submission ............................................................. 217

HAP Support Notes rev. 501_05 -- Page 5 of 218

HAP Support Notes rev. 501_05 -- Page 6 of 218
1.0 Overview
Change Log

Edition Date Description

HAP510_02 Aug 11, 2017 Added Bug 51-01 – Error in 90.1 Baseline Fan Power Calculation
Initial release of support notes for HAP 5.10.
Added Transfer Function Generation Failure can Corrupt Roof / Wall Inputs
HAP510_01 Aug 9, 2017
Updated Microsoft Installer Launches When Starting HAP
Updated Errors When Printing
Updated Troubleshooting 90-Day Demo Problems and Error e400 - Invalid
Authorization Code to remove inaccurate references to company name
(no longer used).
Corrected a number of cases where “HAP 4.x” was referred to but which could
HAP501_05 June 13, 2017 also apply to HAP 5.
Added document revision # to document footer.
Added product logo to document heading.
Corrected page number placement.
Updated Bug 50-04 – Error Importing Certain Weather Files
HAP501_04 April 27, 2017
Updated Microsoft Installer Launches When Starting HAP
Updated Status of ASHRAE Std. 140 Documentation & EPACT Submission
Added Bug 50-05 – Psychrometrics Report Preheat Coil Outlet Incorrect
HAP501_03 January 12, 2017
Moved Bug 47-14 - HAP Encountered a Problem and Needs to Close – Tablet /
Touch Screen from Common Errors to Fixed Bugs section.
November 3,
HAP501_02 Added Bug 50-04 – Error Importing Certain Weather Files
2016
Initial release of support notes for HAP 5.01. (Not distributed.)
Also:
Simplified Error e400 - Invalid Authorization Code
Added details to Error 7 - Corrupt Header
Added details to Error 31 - Unknown Error Posted 21
Added Bug 50-02 – Error in Publish to ECAT / Tag Export
HAP501_01 N/A
Added Bug 50-03 – Problems in Space Data Converting Old Projects
Updated Microsoft Installer Launches When Starting HAP
Updated additional workaround in Unable to see Network Drives
Added Text Cut-Off (Spaces Screen, Schedule Screen, etc.)
Updated Error Number 339 - Component or one of its dependencies not
correctly registered: a file is missing or invalid (minor editorial changes)

Updated Errors 106 and 109 for recent changes to HVACPartners.

Re-categorized Bug 45-01 - "Error 380 - Invalid Property Value" (previously was
not listed as a bug).
HAP500_03 August 24, 2016
Updated Microsoft Installer Launches When Starting HAP
Removed section “Bug Status Table”
Added Bug 50-01 – Error in TimeWeightedOccupancy Calculation
Updated "Jet VBA File Failed to Initialize When Called" Error
Updated Unable to see Network Drives
Added Bug 49-12 – Input Power for AC/WC Heat Recovery with Low Loads
HAP500_02 August 2, 2016 Added Software Downloads section
Re-categorized Bug 45-01 - "Error 380 - Invalid Property Value"; previously was
not listed as a bug.
Renamed “About HAP Tech Support” section to “1.0 Overview”

HAP Support Notes rev. 501_05 -- Page 7 of 218

Edition Date Description

Initial release of support notes for HAP 5.0. Also:

Updated Error 521: Can’t Open Clipboard
HAP500_01 June 27, 2016
Updated "Exception: Access Violation Has Occurred"
Updated Status of ASHRAE Std. 140 Documentation
Updated Bug 49-06 – Building Wizard Error 9 – Subscript out of Range
(formerly listed as just a support note)
HAP491_13 April 26, 2016
Added Signature is Corrupt or Invalid while Downloading
Added Bug 49-10 – Error Calculating DHRC Heat Recovery with Variable
Speed Condenser Pump
HAP491_12 April 13, 2016 Updated Error 521: Can’t Open Clipboard with an additional workaround.
Updated Errors 106 and 109 with additional info.
Corrected document “title” (metadata)
Updated "Runtime Error 3024" While Opening a Project
HAP491_11 Feb. 19, 2016
Updated HAP “Not Responding” When Selecting Files or Printing (Antivirus)
Added “Error setting printer selection”
Added Cannot find EDDUVHS.EXE During Installation (Webroot Antivirus)
Updated Status of ASHRAE Std. 140 Documentation
HAP491_10 Jan. 13, 2016
Updated Unable to see Network Drives to clarify Windows versions
General updates to remove overly-specific references to Windows versions

Updated Unable to see Network Drives for Windows 10.

Updated Error Number 339 - Component or one of its dependencies not
correctly registered: a file is missing or invalid (minor editorial changes)
Notes and additional details added to HAP “Not Responding” When Selecting
Files or Printing (Antivirus)
HAP491_09 Nov. 23, 2015
Added Bug 49-09 – GBXML Import Assigns Incorrect Windows / Doors
Updated Standard Workaround for Errors 7, 106 and 109
Restored missing change log history.
Fixed change log order - Most recent entry at top of list.

Added Error Number 339 - Component or one of its dependencies not correctly
HAP491_08 Oct. 6, 2015 registered: a file is missing or invalid
Corrected some missing images.
HAP491_07 Sept. 14, 2015 Added Bug 49-08 – Example Problem Results Out of Sync with Archive
Added Bug 49-07 – Building Simulation - Index out of bounds (Bad Electric
HAP491_06 Sept. 9, 2015
Rate)
HAP491_05 Sept. 9, 2015 Added Error: This Package Has Expired and Cannot Run
HAP491_04 August 13, 2015 Added “MAPI” Error Sending Email to Sales Engineer
Added HAP Main Window Location Problems in a Networked Installation
HAP491_03 July 14, 2015
Added Errors Loading gbXML – Missing SSNhapXMLAdapter53.mdb
HAP491_02 June 24, 2015 Sync-up with HAP v4.90 support notes.
HAP491_01 June 1, 2015 Initial release of support notes for HAP v4.91.
HAP490_11 June 24, 2015 Added Bug 49-06 – Building Wizard Error 9 – Subscript out of Range
HAP490_10 June 22, 2015 Added HAP “Not Responding” When Selecting Files or Printing (Antivirus)
HAP490_09 June 10, 2015 Added Bug 48-09 – A-Factor Button Obscures Other Inputs

HAP Support Notes rev. 501_05 -- Page 8 of 218

Edition Date Description

Added Status of ASHRAE Std. 140 Documentation

Added HAP Seems to Freeze
HAP490_08 May 18, 2015
Added Dealing with Windows that are Located Off-Screen
Updated HAP Main Window not Visible on Startup
HAP490_07 May 8, 2015 Restored numerous missing images.
Updated Bug 49-01
HAP490_06 Feb 13, 2015
Added File not found: EW_AirSys_Base_05.2.gif
Added Bug 49-04 – Main Window List View is Blank
HAP490_05 Feb. 4, 2015
Added Bug 49-05 – Cannot find tower record in database for record #0
HAP490_04 Jan. 19, 2015 Updated Bug 49-01 – Some Air Systems Missing in Project Library List
General updates:
Updated Unable to see Network Drives When Saving a Project
Updated Unable to see Network Drives for Install

Removed obsolete references to CDROMs:

Updated Installation Problem: This Software Requires Service Pack 4
Updated Installation Problem: You Must be the Administrator...
Updated "Out of Disk Space" Error While Installing

Removed Unable to Read HAP CD:

HAP490_03 Jan. 12, 2015 Updated This Program is not Registered with Configuration Services
Updated How to Convert from Standalone to Network Shared
Updated Error e400 - Invalid Authorization Code
Updated Can't Start Program. No HAP Icon Exists
Updated Unable to Run File Integrity Checkers
Updated Error 429 While Starting Program

Added Configuring HAP for Dual Mode (Standalone and Network) Operation
Added GetE20ConfigData – Active X Component Can’t Create Object
Added Bug 49-02 - Invalid OA Requirements Not Trapped for 62.1-2010
Added Bug 49-03 – Plant Using Hi+Low Sequencing and Shared Tower
Added Bug 49-01
HAP490_02 Dec. 24, 2014
Added Error on Starting HAP - Missing File SSNSystemDefault17.RO
HAP490_01 Dec. 1, 2014 Initial release of support notes for v4.90.
HAP480_09 April 7, 2014 Added Bug 47-12 – Insufficient Cooling for System without HW Coils
HAP480_08 April 4, 2014 Added Bug 48-2 – Error 3265 When Running Full Wizard Session
HAP480_07 Feb 26, 2014 Updated About Windows User Account Control (UAC) Warnings
HAP480_06 Feb 10, 2014 Added Automation Error – The Network Name Cannot Be Found
HAP480_05 Jan 31, 2014 Added About Windows User Account Control (UAC) Warnings
HAP480_04 Jan 21, 2014 Added Error 521: Can’t Open Clipboard
HAP480_03 Nov 25, 2013 Updated Com Err – Error 364 when Requesting Reports.
HAP480_02 Nov 25, 2013 Added Bug 48-1 – Error 91 When Simulating Chilled Water Plant
HAP480_01 Oct. 31, 2013 Initial release of support notes for v4.80.
HAP470_18 April 7, 2013 Added Bug 47-13
HAP470_17 April 7, 2013 Added Bug 47-12
HAP470_16 April 3, 2013 Added Bug 46-00
HAP470_15 Nov 25, 2013 Update Com Err – Error 364 When Requesting Reports

HAP Support Notes rev. 501_05 -- Page 9 of 218

Edition Date Description

HAP470_14 Oct. 31, 2013 Updated bug section to indicate fixes made in HAP v4.80
Updated ComErr - HAP Encountered a Problem and Needs to Close – Tablet /
HAP470_13 Oct. 10, 2013
Touch Screen
HAP470_12 Sept. 10, 2013 Added bugs 47-10 and 47-11.
Updated ComErr - "Navigation to the Webpage has been Cancelled" Error
HAP470_11 July 31, 2013
When Displaying Help (added screenshots)
Updated ComErr – HAP Window not Visible on Startup
Added Networks – How to Convert From Network-Shared to Standalone
HAP470_10 July 19, 2013 Added ComErr – “Fatal Error 3633 loading data: Can’t load DLL:
MSJTER35.DLL”
Added bugs 47-7, 47-8, and 47-9
HAP470_09 June 29, 2013 Added ComErr – Run-Time Error 372 during Startup
HAP470_08 June 12, 2013 Added ComErr – The Field is Too Small to Accept the Amount of Data…
HAP470_07 June 6, 2013 Updated ComErr – Unable to See Network Drives For Installation
HAP470_06 June 5, 2013 Updated ComErr – Unable to See Network Drives When Saving Project
Added Bugs 47-3 , 47-4, 47-5, and 47-6
HAP470_05 June 3, 2013
Update ComErr – Error 364 When Requesting Reports
HAP470_04 May 24, 2013 Updated ComErr – HAP Window not Visible on Startup
HAP470_03 May 21, 2013 Added Bug 47-2
Added Bug 47-1
HAP470_02 May 13, 2013
Updated ComErr – Unable to see network drives for installation
HAP470_01 May 1, 2013 Initial release of support notes for v4.70.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 10 of 218

Applicable Software
Revised: August 9, 2017
This support notes document covers the following versions of HAP and SDL. Further information about each
version can be found in the release sheet for that program.
 HAP 5.10: Released worldwide in August 2017.
 HAP System Design Load 5.10: Only available in the US and Canada. Released in August 2017.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 11 of 218

Software Downloads
Revised: October 12, 2016
Current and past versions of the software can be downloaded from the links below. “n/a” indicates that no
download is currently available.
Recommend copying the entire row of the table into an email to customers.
Note: New features documents are the same for all editions so are only listed once.

North America Customer Downloads Sales Office Downloads New Features Docs
HAP v5.10 installer release sheet HAP v5.10 installer release sheet HAP v5.10 new features
SDL v5.10 installer release sheet SDL v5.10 installer release sheet SDL v5.10 n/a
HAP v5.01 installer release sheet HAP v5.01 installer release sheet HAP v5.01 new features
SDL v5.01 (*1) (*1) SDL v5.01 (*1) (*1) SDL v5.01 (*1)
HAP v5.00 installer release sheet HAP v5.00 installer release sheet HAP v5.00 new features
SDL v5.00 installer release sheet SDL v5.00 installer release sheet SDL v4.91 n/a
HAP v4.91 installer release sheet HAP v4.91 TBD TBD HAP v4.91 new features
SDL v4.91 installer TBD SDL v4.91 TBD TBD SDL v4.91 n/a
HAP v4.90 installer TBD HAP v4.90 installer release sheet HAP v4.90 new features
SDL v4.90 TBD TBD SDL v4.90 TBD TBD SDL v4.90 TBD
HAP v4.80 installer TBD HAP v4.80 TBD TBD HAP v4.80 new features
SDL v4.80 TBD TBD SDL v4.80 TBD TBD SDL v4.80 n/a
HAP v4.70 TBD TBD HAP v4.70 TBD TBD HAP v4.70 TBD
SDL v4.70 installer TBD SDL v4.70 TBD TBD SDL v4.70 n/a

International Customer Downloads Trial Downloads

HAP v5.10 installer release sheet HAP v5.10 installer release sheet
HAP v5.01 installer release sheet HAP v5.01 installer release sheet
HAP v5.00 installer release sheet HAP v5.00 installer release sheet
HAP v4.91 installer release sheet HAP v4.91 installer release sheet
HAP v4.90 TBD TBD
HAP v4.80 TBD TBD
HAP v4.70 TBD TBD

(*1) There was no release of SDL v5.01.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 12 of 218

2.0 Current Bugs
Bug 51-01 – Error in 90.1 Baseline Fan Power Calculation
Date: Aug 11, 2017
Versions: HAP 5.10, SDL 5.10
Corrected in: HAP 5.10, SDL 5.10

Problem Has Been Resolved

Please Reinstall HAP 5.10 or later to eliminate problem.
Summary: A calculation error may result in an incorrect supply fan power value, in certain cases. The reported
design fan power would differ from HAP 5.0, and would differ substantially between 90.1-2007 and -2010.
Discussion: This is a bug in the HAP logic regarding baseline fan power calculation. The bug causes a special
case intended only for heating-only SZCAV systems to take effect in certain other cases. Specifically, the problem
can occur in the following circumstances:
 Project using to 90.1-2010
 Air system using the 90.1 Appendix G Fan Power option for the supply fan
 Central system type other than heating-only single zone CAV
(Any other cases are unaffected.)
The result of this error is that fan power is typically undersized. This is a design calculation problem (visible on the
System Sizing Summary report) but also subsequently affects annual energy simulations.
Workaround: The problem has been fixed in HAP and SDL. Any customer experiencing this issue should do the
following:
 Re-download and run the HAP or SDL installer for 5.10
 Run HAP or SDL
 Open the affected project.
 Open the weather settings for the project, and then just click OK. This will force all air systems, etc., to be
recalculated.
 Re-run reports.

Build Numbers:
Program Original build (with the bug) Fixed in build
HAP 5.1 HAP 5.1.0.13 HAP 5.1.0.14
SDL 5.1 SDL 5.1.0.14 SDL 5.1.0.15
(See Help > About screen to check build number)

(Bug # 25609)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 13 of 218

2.1 Fixed Bugs
Bug 50-01 – Error in TimeWeightedOccupancy Calculation
Date: July 13, 2016
Versions: HAP v4.9x, HAP v5.00, HAP v5.01
Corrected in: HAP v5.10

Problem Has Been Resolved

Please Install HAP 5.10 or later to eliminate problem.
Summary: During system design calculations the following error is received:
Error Number: 0
Description: Subscript out of range

Source:
frmMain.mnuReportDesign_Click
HAP.frmMain.DoAppReport
HAPCalc50.SC_Controller.Run()
HAPCalc50.ASD_Calculations.Calculate()
HAPCalc50.ASD_Calculations.SizingController()
HAPCalc50.ASD_Calculations.SizeSpcCFMFirst()
HAPCalc50.ASD_Calculations.fnVentilationSpec()
HAPCalc50.ASD_Calculations.SizeASHRAEStd62_Since_2004()
HAPCalc50.ASD_Calculations.TimeWeightedOccupancy()
SSNDataHandler19.SCH_Schedule.HourlyValue [PropertyGet]
HAPDataHandler19
Because of this the design calculations are not completed.
Discussion: This is a flaw in the way HAP has implemented rule 6.2.6.2 of ASHRAE Std. 62.1 This rule
determines the time period over which a time-weighted average occupancy is meant to be calculated. In certain
circumstances this calculation results in the error.
The calculation is based, in part, on the volume of the space. If the space has an unusually tall (though valid)
height – typically > 50 ft or 15 m – this problem may occur.
Workaround: In all cases observed so far, reducing the space height by a small amount avoids the problem. This
should be done incrementally, gradually working downwards until the problem does not occur.
If infiltration was specified in terms of ACH, before any modification to the ceiling height is made, infiltration must
instead be specified in terms of CFM. The CFM value will already be displayed, and it just needs to be re-entered
manually.
(Bug # 24686)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 14 of 218

Bug 50-04 – Error Importing Certain Weather Files
Date: Nov. 3, 2016
Versions: HAP v5.00, 5.01
Corrected in: HAP v5.10

Problem Has Been Resolved

Please Install HAP 5.10 or later to eliminate problem.
Summary: When importing certain weather files one of the following errors occur:

OR:

Simulation Weather File Translator

Subscript out of range
clsSimWthrTranslator
ValidateSourceFile

Because of this the file cannot be imported.

Discussion: This occurs for IWEC, IWEC2, TMY2, TMY3 files. This does NOT occur for EPW (EnergyPlus) or
HAP’s own HW1 format. It is a software bug which is anticipated to be fixed in HAP v5.10.
Workaround: If the user supplies the file to SSN we can manually process the file and send back an archive.

(Bug # 24867)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 15 of 218

HAP Support Notes rev. 501_05 -- Page 16 of 218
Bug 50-05 – Psychrometrics Report Preheat Coil Outlet Incorrect
Date: Jan. 12, 2017
Versions: HAP 5.01 and earlier, SDL 5.00 and earlier.
Corrected in: HAP v5.10

Problem Has Been Resolved

Please Install HAP 5.10 or later to eliminate problem.
Summary: The CFM value for Preheat Coil Outlet is incorrect on the air system design Psychrometrics Report.
This is only a cosmetic reporting error. Air system performance is calculated correctly.

Discussion: The error is that the coil load is appearing in the wrong cell and is overwriting the CFM value. The
correct CFM value should equal the value shown for Vent-Return Mixing. See two examples below.

Example 1: The value 53096 shown in the airflow cell is really the preheat coil load in BTU/hr that
should be 2 columns over in the Sensible Heat column. The airflow for the preheat coil should have
displayed as 1275 CFM in this case.

Example 2: This sample incorrectly shows the preheat coil airflow as zero, because zero is the BTU/hr
preheat coil load. The airflow should display as 4688 CFM in this case.

Workaround: Use the value from the Vent-Return Mixing line item.

(Bug # 25036)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 17 of 218

Bug 50-02 – Error in Publish to ECAT / Tag Export
Date: August 26, 2016
Versions: HAP v5.00
Corrected in: HAP v5.01

Problem Has Been Resolved

Please Install HAP v5.01 or later to eliminate problem.

Summary: When publishing sizing results to ECAT the following error is received:
Error Number: 0
Description: Subscript out of range

Source:
frmMain.mnuProject_ExportEquipmentTags_Click
HAP.CTAGDataLink.BuildTagLinks
HAP.CTAGDataLink.GenerateSystemTags
HAPDataHandler19.WTH_Weather.DesDB [PropertyGet]

Because of this the publication of results is not completed. This does not occur for all systems, only in specific
cases.
Discussion: This occurs only when the peak month for a cooling coil happens to be the winter / heating design
condition.
Workaround: There is no workaround that the end user can perform. However, a fix is available in Syracuse and
if a project archive is provided we can run the publish procedure here and return the results.

(Bug # 24647)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 18 of 218

Bug 50-03 – Problems in Space Data Converting Old Projects
Date: October 18, 2016
Versions: HAP v5.00
Corrected in: HAP v5.00 (installer was corrected), HAP v5.01

Problem Has Been Resolved

See workarounds to eliminate problem.
Summary: The HAP50SPC.dat file is left in a read-only status following project conversion. This may show up in
several different ways:
1. Bad or blank data when editing an existing space:

2. An error when saving the project: “Error 5 - Access is denied”

3. An error during air system calculations:
Error Number: 0
Description: Division by zero
Source:
frmMain.mnuReportDesign_Click
HAP.frmMain.DoAppReport
HAPCalc50.SC_Controller.Run()
HAPCalc50.ASD_Calculations.Calculate()
HAPCalc50.ASD_Calculations.AirSysDesignSimController()
HAPCalc50.AE_Engine.ZoneAnalysis()

HAP Support Notes rev. 501_05 -- Page 19 of 218

Discussion: When HAP 5.0 was first released there was a problem in the installer. The installer was corrected a
few hours after release but nonetheless some customers had downloaded it. The problem arises sporadically.
The specific problem in the installer was that the file HAP50SPC.dat within the file E20-
ii\HAP50\CODE\HAP50.zip was set to READ-ONLY. The corrected installer eliminated this issue.

Workaround 1: This fix involves replacing one file in the HAP installation. It may be more suitable for a user who
is technically confident.
Instructions:
Step 1: Provide the customer with HAP50.zip from the HAP50\CODE folder.
Step 2: On the customer’s PC:
1. Close HAP
2. Rename the file E20-II\HAP50\CODE\HAP50.zip to HAP50_old.zip
3. Copy the new HAP50.zip file to the same location.

Step 3: Go to Project Cleanup, below.

Workaround 2:
1. Reinstall HAP 5.0.
2. The customer will require their customer number / access code for this.
3. Afterwards, go to Project Cleanup, below.

Project Cleanup: This is a final step required after either workaround above.
On the customer’s PC:
1. Go to the folder of the project which was converted, i.e., c:\e20-ii\Projects\<project-name>
2. Make sure HAP50SPC.DAT is NOT set to read-only. (Right-click file, select properties).
3. Do this for all projects already converted.

(Bug # 24511)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 20 of 218

Bug 49-12 – Input Power for AC/WC Heat Recovery with Low Loads
Date: July 13, 2016
Versions: HAP v4.9x, HAP v5.00
Corrected in: HAP v5.01

Problem Has Been Resolved

Please Install HAP v5.01 or later to eliminate problem.
Summary: In certain cases the input power for a heat recovery plant can be overstated. This issue can occur only
when ALL the following are true:
 Heat recovery plant using air-cooled chillers having water-cooled heat recovery condensers
 Hour of simulation where heat recovery is possible
 Hour of simulation where the cooling load is less than the minimum % load column in the water-cooled
performance map
 The lowest capacity column in the water-cooled performance map is > 0% (i.e., it ends at 20%)
 ECAT data is being used for air-cooled operation (not HAP default data, and not user-entered data)
Discussion: In these circumstances, the program incorrectly assumes a minimum unloading of 0% even though
the performance map does not go that low, e.g., only to 20%. Therefore in hours with loads less than the actual
minimum of 20%, the input power at 20% is incorrectly used.
The actual overall impact on annual energy usage depends on the specifics of the plant loads.
Workaround: If possible, adjust the performance map to include extra columns as close to 0% as possible.
However, in many instances this is not possible due to limitations of the user interface. In those cases the optimal
solution is to manually enter the air-cooled performance data rather than using the ECAT data. If the CD5 data is
loaded into CSO, then the map is visible, and can be utilized for this procedure. Alternately, load lines from ECAT
can be run.
Since this re-entry of data may be time consuming, it is recommended to first inspect the plant results to
rd
determine if this issue is occurring, and if it is, to what extent. 3 level support can assist with this.

(Bug # 24517)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 21 of 218

Bug 49-01 – Some Air Systems Missing in Project Library List
Date: December 24, 2014
Updated: January 19, 2014
Versions: HAP v4.90, SDL v4.90
Corrected In: HAP v4.91, SDL v4.90

Problem Corrected
Please Re-Install SDL v4.90 or HAP v4.91 or later to eliminate
problem
Note: This problem existed in the original release of SDL490, but an updated installer was made available that
eliminated the issue. Users should download and reinstall SDL.
In case there is any doubt whether a user has the up-to-date version, ask them to view the Help > About screen.
The CORRECTED SDL will show build number 4.90.0.38. An earlier number would have the problem.

Summary: This problem occurred in SDL, or also in HAP with energy analysis features turned off.
A user creates a new air system and saves it (clicks ‘OK’). When they view the Systems project library, they do
not see the air system in the list. However the correct number of air systems is shown on the project summary
view (when you click the top node in the navigation tree).
Discussion: What normally seems to happen is that the first air system is shown, but no others are listed. Data
for all air systems is actually saved correctly, but is rendered inaccessible by this problem.
This is a bug in the way the project library screen attempts to layout the data shown for the air systems. An
internal error occurs after the first system is displayed which effectively cancels the display of the remaining air
systems.
Workaround – SDL: There is no workaround in SDL itself that the user can undertake to show the missing air
systems all at once. But there are other options:
1. Save multiple copies of the project, each having only one system. After saving the project under a new
name, deleting the only air system shown will expose the next one. This can be repeated until the desired
air system is the first in the list, and therefore is displayed. This is not ideal, but could be useful in an
“emergency” situation.
2. Use HAP v4.90 instead. HAP would need to be installed using the normal installer, and new access
codes would have to be provided to the customer.
rd
As of Dec 23 , 2014, a potential fix is being tested with one customer and may result in a fixed release if
successful.

Workaround – HAP: Since this issue only occurs when energy analysis features are turned off, the user should
turn them on even if they are not needed. They can do this from View Menu > Preferences > General Tab.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 22 of 218

Bug 49-02 – Invalid OA Requirements Not Trapped for 62.1-2010
Date: January 8, 2015
Versions: HAP v4.90, SDL v4.90
Corrected In: HAP v4.91

Problem Has Been Resolved

Please Install HAP v4.91 or later to eliminate problem.
Summary: For the following set of conditions HAP fails to detect an error in user input data and performs design
calculations for an air system that yields incorrect ventilation sizing results:
a. One or more spaces specify an outdoor air requirement with units of CFM (L/s) or % of supply air,
b. The spaces are linked to an air system in which the ventilation calculation method is ASHRAE Standard 62.1-
2010.
In this situation, HAP should refuse to calculate the air system and display a Calculation Error Report indicating
the outdoor air requirement units for the space are incompatible with Standard 62.1-2010.
Due to an error in the program, HAP does not detect the error and performs the system design calculation. The
outdoor air ventilation sizing is incorrect because any CFM or % of supply air requirements are omitted from the
calculation.
Workaround: The only workaround available is to self-monitor the input data. Do not select ASHRAE Standard
62.1-2010 ventilation calculations for a system serving spaces with CFM or % of supply air outdoor air
requirements.
Note:
1. Invalid OA requirements situations are correctly trapped when using ASHRAE Standards 62.1-2004 and 62.1-
2007. The error is not trapped only when using ASHRAE Standard 62.1-2010.
2. This check is not relevant when using ASHRAE Standard 62-2001.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 23 of 218

Bug 49-03 – Plant Using Hi+Low Sequencing and Shared Tower Produces
Incorrect Condenser Pump Results
Date: January 9, 2015
Versions: HAP v4.90, and prior versions
Corrected In: HAP v4.91

Problem Has Been Resolved

Please Install HAP v4.91 or later to eliminate problem.
Summary: A Sequenced Hi+Low chiller plant having a shared cooling tower will produce inaccurate results for
condenser pump energy in some hours.
These are hours are indicated by having zero condenser pump energy but nonzero tower fan energy. Depending
on the scenario, this can lead to very large inaccuracies in the pump energy.
Workaround: There is no exact workaround possible, but by configuring the plant to have one tower for each
chiller correct results will be produced.
Note 1: This may also affect HW plants using water-source heat pumps, although an issue in this case has not
actually been observed.
Note 2: This was first observed in HAP v4.90, but based on source code comments it seems probable that this
bug has existed for quite some time. Therefore it should be assumed to exist in any version of HAP likely to still
be in use.
(Bug 22216)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 24 of 218

Bug 49-04 – Main Window List View is Blank
Date: January 20, 2015
Versions: HAP v4.90, SDL v4.90
Corrected In: HAP v4.91

Problem Has Been Resolved

Please Install HAP v4.91 or later to eliminate problem.
Summary: If a user chooses the View Menu > List option (or from the toolbar), the main screen list will be blank.
Example showing List view:

Example showing Details view:

Workaround: Use one of the other view options.

Note: This bug was fixed in the new installer of SDL v4.90 on January 19, 2015. See Bug 49-01 for more
information.
(Bug 22073)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 25 of 218

Bug 49-05 – Error: Cannot find tower record in database for record #0
Date: February 4, 2015
Versions: HAP v4.90
Corrected In: HAP v4.91

Problem Has Been Resolved

Please Install HAP v4.91 or later to eliminate problem.
Summary: A hot water plant created from the Equipment Wizard using an air-source heat pump will produce an
error when energy simulations are run:

Error Number: -2147221504

Description: Cannot find tower record in database for record #0

Source:
CIDOReport.CreateContext()
SSNHAPCalc490.SC_Controller.Run()
SSNHAPCalc490.frmProgress.Calculate()
SSNHAPCalc490.PS_Controller.Calculate()
SSNHAPCalc490.PS_Controller.SimulatePlant_HotWater()
SSNHAPCalc490.PS_Controller.SetupPlant_HotWater()
SSNHAPCalc490.PS_Controller.SetupSourceWaterLoop_HW()
SSNDataHandler18.TWR_CoolingTower.Load()

This prevents the energy simulation from being run.

Discussion: The underlying problem is that the Equipment Wizard creates the plant with an incorrect input data
related to cooling towers (which are irrelevant for an air-source heat pump plant). This incorrect input data leads
to the error message.
This will not occur for any other type of plant or plant equipment created from the Wizard. It will also not occur if
you create the same plant manually using the detailed HAP inputs.

Workaround: The wizard will create a plant such as ‘ALT1 - Hot Water Plant’. The user should edit this plant and
then re-save it without making any changes. This will cause the bad data to be removed. Afterwards, energy
simulations should work as expected.
(Bug 22366)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 26 of 218

Bug 49-06 – Building Wizard Error 9 – Subscript out of Range
Date: June 24, 2015
Versions: HAP v4.90, SDL 4.90
Corrected In: HAP 5.0

Problem Has Been Resolved

Please Install HAP v5.0 or later to eliminate problem.
Summary: When completing the Building Wizard or when running the Building Wizard input report, the following
error is shown:

(Error 9 subscript out of range BWR_GenerateReport)

After OK the error, HAP functions normally. Project data was correctly created from the Building Wizard.

Discussion: This only occurs when the HAP project contained one or more wall or roof assemblies, AND one of
those assemblies was selected in the Building Wizard.
This error will always occur in that scenario because the BW input report is always shown. It will only occur in a
Full Wizard Session if the input report is selected manually.
The error is essentially a nuisance message, because it only affects the report generation. All other aspects of the
Building Wizard seem to be unaffected.

Workaround: Run the Full Wizard Session, use only the Building Wizard, and do not view the input report. This
will avoid the error.
(Bug 22817)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 27 of 218

Bug 49-07 – Building Simulation - Index out of bounds (Bad Electric Rate)
Date: Sept. 9, 2015
Versions: HAP v4.91
Corrected In: HAP 5.0

Problem Has Been Resolved

Please Install HAP v5.0 or later to eliminate problem.
Summary: When running building simulations, the following error is shown:
The following error has occurred.

Please contact Carrier Software Systems for assistance.

Error Number: 5
Description: Index out of bounds

Source:
CIDOReport.CreateContext()
SSNHAPCalc490.SC_Controller.Run()
ListSubItems

Discussion: There is a problem with the electric rates screen which can allow invalid data to be saved for a
complex electric rate. For a complex rate, at least one ‘step’ is required on the Energy Charges tab. If you go to
that tab and remove all the steps, then click OK, and error will be shown.
However, if the user has a complex rate and does the following steps, bad data can be saved:
1. Create a new complex electric rate; e.g., use the Utility Rate Wizard and select an EIA state.
2. Open the rate in HAP.
3. Set the type to simple. Then without clicking anything else, set it back to complex.
4. Click OK
5. Open the rate again.
6. Visit the energy charges tab.
7. No steps are listed.
If a rate created in this manner is used in a building simulation, the above error should result.

Workaround: Delete the rate with the bad data, and recreate a new rate with correct data. Then attach the new
rate to the building.
(Bug 23539)
Back to Table of Contents

Bug 49-08 – Example Problem Results Out of Sync with Archive

Date: Sept. 14, 2015
Versions: HAP v4.91
Corrected In: HAP 5.0

HAP Support Notes rev. 501_05 -- Page 28 of 218

 Problem Has Been Resolved
Please Install HAP v5.0 or later to eliminate problem.
Summary: If a customer compares the example problem PDF to calculation results from the example archive,
they will notice a difference in results.
Discussion: The HAP49_Example.E3A archive file included in the HAP v4.91installer is incorrectly out of sync
with the project used to create the example PDF report. This leads to small numerical differences in some results.
An error was introduced into the archive after the PDF was created.
Workaround: SSN has a correct archive which should be supplied to the customer for verification. This archive
should produce identical results as the PDF.

(Bug 23552)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 29 of 218

Bug 49-09 – GBXML Import Assigns Incorrect Windows / Doors
Date: Oct. 27, 2015
Versions: HAP v4.91 and earlier, SDL v4.91 and earlier
Corrected In: HAP 5.0, SDL 5.0

Problem Has Been Resolved

Please Install HAP v5.0 or later to eliminate problem.
Summary: In certain cases, the GBXML import will assign the same window or door over and over again to
different spaces, instead of linking difference windows / doors to each space. This only occurs when there are a
series of windows or doors in the GBXML will very long and similar names.
Discussion: HAP has a limitation of 30 characters (letters, numbers, punctuation, etc.) in window and door
names. When the name of a window or door in GBXML is longer than that, HAP truncates the name.
Furthermore, if more than one truncated name would not be unique, HAP will append a number to each name
such as (1), (2), etc.
The bug occurs only when both of those conditions occur. The result is that several spaces may be linked to
window or door (1) instead of the later numbered items.
Note: this has only been observed to occur with GBXML from Autodesk Revit, which apparently generates quite
long names.
Workaround: There is no workaround within HAP. However, if names <= 30 characters can be used that will
avoid the problem. This will be fixed in a later release.

(Bugs 23639 & 23642)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 30 of 218

Bug 49-10 – Error Calculating DHRC Heat Recovery with Variable Speed
Condenser Pump
Date: Apr. 1, 2016
Versions: HAP v4.90, HAP v4.91, BSO v1.40
Corrected In: HAP 5.0

Problem Has Been Resolved

Please Install HAP v5.0 or later to eliminate problem.
Summary: In certain cases, a DHRC plant with variable flow/variable speed condenser will fail to calculate with
the following error:
Error Number: 6
Description: Overflow

Source:
modWizards.RunCalculations
SSNHAPCalc4901.SC_Controller.Run()
SSNHAPCalc4901.frmProgress.Calculate()
SSNHAPCalc4901.PS_Controller.Calculate()
SSNHAPCalc4901.PS_Controller.SimulatePlant_HeatRecovery()
SSNHAPCalc4901.PS_Controller.SimulateHour_Cooling
SSNHAPCalc4901.PE_ChillerPlant.Calculate
SSNHAPCalc490

Discussion: This is a plant calculation bug that should be limited to a parallel DHRC plant with variable speed
condenser pumps. This occurs when there is a calculation hour where the DHRC can handle all the cooling load.
In this circumstance, the calculation does not correctly handle the fact that the required condenser pump flow is
zero. (In the constant-speed pump case the calculation is different and this error does not occur.)
This issue should be limited to only DHRC plants because in all the other water-cooled heat recovery cases the
condenser flow cannot be zero if there is a nonzero cooling load.
This error may not always occur, but operating conditions such as a northern climate may produce a load pattern
which makes this bug more likely.

Workaround:. If the user changes to a constant flow / constant speed condenser then it calculates without errors.
They may want to discount the pump energy somewhat to make up for the difference.

(Bugs 23995)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 31 of 218

Bug 49-11 – File not found: EW_AirSys_Base_05.2.gif
Date: February 9, 2015
Revised: June 1, 2015
Versions: HAP v4.90
Corrected In: HAP v4.91

Problem Has Been Resolved

Please Install HAP v4.91 or later to eliminate problem.
Summary: When using the Equipment Wizard, the user receives an error message such as the following:
Error Number: 76
Description: Path not found: 'Wizards\EW_AirSys_Base_05.2.gif'
Source:
frmEW1.Form_Activate()
SSNHAPWizards17.frmEW1.DisplayFullPicture()
SSNHAPWizards17.frmEW1.DisplayBaseDiagram
SSNHAPWizards17.frmEW1.LoadBaseImageIfNeeded

Discussion:
NOTE: A permanent workaround for this was included in HAP v4.91. Problem should no longer occur.
This has been reported about once a month recently (early 2015). When the customer checks, normally the file
referred to is actually present on their computer, despite the message.
The root cause of this problem is not yet known.

Workaround: First, the user should check:

1. The file exists: C:\E20-ii\ENVIRO\Wizards\EW_AirSys_Base_05.2.gif
(May need to substitute another drive for C: or the filename from the error message if not the same as this one)
2. The user has normal (read) permissions on the file AND permissions for the folder it is in.

If the file is missing, HAP should be reinstalled.

If permissions are incorrect, they should be corrected.

If neither of those is an apparent problem, in some cases a reinstallation of HAP has fixed the problem.

(Bug 22454)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 32 of 218

Bug 48-01 – Error 91 When Simulating Chilled Water Plant
Date: November 25, 2013
Versions: HAP v4.80
Corrected In: HAP v4.90

Problem Has Been Resolved

Please Install HAP v4.90 or later to eliminate problem.
Summary: When running the plant simulation for a chilled water plant, the simulation halts and displays the
following error message. Because of this error, the simulation cannot be completed.

Discussion: This specific error occurs when all of the following conditions are present in the chilled water plant:
1. On the Configuration Tab, free cooling has been selected, and
2. On the Configuration Tab, the cooling tower configuration is “one tower for each water-cooled chiller”, and
3. On the Schedule of Equipment tab all of the chillers linked to the plant are air-cooled chillers.
Because free cooling is specified and no heat rejection equipment is specified on the Schedule of Equipment tab,
the program lacks complete information to simulate free cooling and that leads to the error.
Workaround: If the user did not intend to use water-side economizer with this plant, the Free Cooling box should
be unchecked. Then rerun the simulation. It will run without errors now.
If the user did intend to use water-side economizer with this plant, the following changes must be made to
properly model the equipment:
1. On the Configuration Tab, change the cooling tower configuration to “one tower shared by all water cooled
chillers”. For an air-cooled chiller plant this option refers to the use of one shared heat rejection device to
provide free cooling.
2. On the Schedule of Equipment Tab, select a heat rejection device (cooling tower, dry-cooler, or geo/well
source) in the Shared Cooling Tower item.
3. Then rerun the simulation. It will run without errors this time.

Back to Table of Contents

Bug 48-02 – Error 3265 When Running Full Wizard Session

Date: April 4, 2014
Versions: HAP v4.80
Corrected In: HAP v4.90

HAP Support Notes rev. 501_05 -- Page 33 of 218

 Problem Has Been Resolved
Please Install HAP v4.90 or later to eliminate problem.
Summary: The user clicks “Full Wizard Session” from the Wizards menu, or clicks the equivalent toolbar button.
As soon as the wizard screen comes up, they receive the following error:

[Error 3265 Item not found in this collection]

Discussion: This is a result of bad data in an underlying data file used by the Equipment Wizard. The bad data is
only known to originate in the set of ASHRAE schedules and climate zone archives which was installed with HAP
v4.8 (in the C:\E20-II\ARCHIVES folder). This error has not been observed under any other circumstances.
In order for this error to occur, the user must first retrieve the project data from one of these archives, then run the
Equipment Wizard. If the Equipment Wizard is never run, no problem will occur.
It is also possible for this error to occur with a project or project archive that originated as one of the ASHRAE
archives. (If opened a long time later, that relationship might not be obvious any longer.)
Note that although these same archives are distributed with System Design Load, the Equipment Wizard is not
part of SDL, so this problem does cannot affect SDL.

Workaround: There are several approaches to get around this error:

1. If the user’s project has important data in it, they should either:
a) Create a new project, and then use Project Menu > Import … to copy all data from the original project to
the new one. The bad data will not be imported.
OR
b) Archive their project and send it to support. We can repair this issue and send the fixed project back to
them.

2. If the user retrieves data from an ASHRAE archive, saves that as a new project, and then imports from that
project into their working project, the error will not occur. (This is typically how many users use the archive data
anyway.)

3. Supply the user with a corrected copy of the archive files:

1. The user should delete the following files from the C:\E20-II\ARCHIVES folder:
a. HAP48_ASHRAE-90-1-2007-Zone-1.E3A
b. HAP48_ASHRAE-90-1-2007-Zone-2.E3A
c. HAP48_ASHRAE-90-1-2007-Zone-3.E3A

HAP Support Notes rev. 501_05 -- Page 34 of 218

 d. HAP48_ASHRAE-90-1-2007-Zone-4.E3A
e. HAP48_ASHRAE-90-1-2007-Zone-5.E3A
f. HAP48_ASHRAE-90-1-2007-Zone-6.E3A
g. HAP48_ASHRAE-90-1-2007-Zone-7.E3A
h. HAP48_ASHRAE-90-1-2007-Zone-8.E3A
i. HAP48_Schedules.E3A
2. A ZIP file of corrected archives can be downloaded from the following location:
http://www.docs.hvacpartners.com/idc/groups/public/documents/software/hap48-climate-archives.zip.
3. Once downloaded, the user should open the ZIP file in WinZIP (or similar) and extract all the E3A files to
the C:\E20-II\ARCHIVES folder.
4. They can then retrieve data from the replaced archives and should have no further issues.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 35 of 218

Bug 48-03 – Error in Std 62.1 Calculation for PFPMBX Air Terminals
Date: October 16, 2014
Versions: HAP v4.80, SDL v4.80
Corrected In: HAP v4.90

Problem Has Been Resolved

Please Install HAP v4.90 or later to eliminate problem.
Summary: In certain situations, ventilation airflow calculated per ASHRAE Standard 62.1-2004, -2007 or -2010
for a system containing parallel fan powered mixing box (PFPMBX) air terminals will be incorrect. There are two
errors occurring. When the error occurs, it could overstate or understate the ventilation requirement for the air
system.
Discussion: There are two potential errors. Conditions required for the first error to occur are:
 Ventilation sizing method is the Standard 62.1-2004, -2007 or -2010 ventilation rate procedure
 Zone air terminal type is parallel fan powered mixing box
 The delta-T between heating design supply air temperature for the air terminal and the occupied zone
heating setpoint is =< 15 F.
For these conditions HAP sets Ez to 0.8. Per Standard 62.1, it should be set to 1.0.
Standard 62.1 specifies that Ez be set to 1.0 if the delta-T between heating supply temperature and room
temperature is =< 15 F. When the delta-T is > 15 F, Ez must be set to 0.8. Currently the HAP ventilation sizing
algorithm sets Ez to 0.8 for PFPMBX air terminals regardless of delta-T.
For a case where Ez is set to 0.8 when it should be 1.0, the space outdoor airflow rate, Voz, will be overstated.
That will ultimately result in the system outdoor air intake airflow requirement, Vot, being overstated.
The second error occurs under the following conditions:
 Ventilation sizing method is the Standard 62.1-2004, -2007 or -2010 ventilation rate procedure
 Zone air terminal type is parallel fan powered mixing box
During the Standard 62.1 calculation for a PFPMBX zone, the space primary airflow, V pz, must be checked to
verify it is equal to or larger than the space outdoor airflow, Voz. For this check, the program is incorrectly
comparing Vpz and the space design airflow rate, Vdz. For a PFPMBX terminal operating at the heating design
condition (per Std 62.1), Vdz will always be larger than Vpz. As a result Vpz gets set to an inflated value and this
ultimately can result in a calculated system outdoor air intake airflow, Vot, that is smaller than required. This is
because the ratio of required ventilation airflow to primary airflow is smaller than the correct value would be.
Workaround: There is no workaround in v4.8.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 36 of 218

Bug 48-04 – Error in Std 62.1 Calculation for SFPMBX Air Terminals.
Date: October 16, 2014
Versions: HAP v4.80, SDL v4.80
Corrected In: HAP v4.90

Problem Has Been Resolved

Please Install HAP v4.90 or later to eliminate problem.
Summary: Ventilation airflow calculated per ASHRAE Standard 62.1-2004, -2007 or -2010 for a system
containing series fan powered mixing box (SFPMBX) air terminals will be incorrect. When the errors occur, they
could either overstate or understate the ventilation requirement for the air system.
Discussion: There are two errors. Conditions required for both are:
 Ventilation sizing method is the Standard 62.1-2004, -2007 or -2010 ventilation rate procedure
 Zone air terminal type is series fan powered mixing box
For the first error, when evaluating the design heating condition, HAP incorrectly sets the space primary airflow,
Vpz, to the maximum design primary airflow rather than to the minimum airflow. Standard 62.1 requires all
variable air volume systems be evaluated at both cooling and heating design conditions in which minimum
primary airflow rate is used.
For the second error, the calculation for a SFPMBX zone must check the space primary airflow, V pz, rate to verify
it is equal to or larger than the space outdoor airflow, Voz. For this check, the program is incorrectly comparing Vpz
and the space design airflow rate, Vdz. For a SFPMBX terminal operating at the heating design condition (per Std
62.1), Vdz will always be larger than Vpz. As a result Vpz gets set to an inflated value and this ultimately results in a
calculated system outdoor air intake airflow, Vot, that is smaller than required. This is because the ratio of
required ventilation airflow to primary airflow is smaller than the correct value would be.
Workaround: There is no workaround in v4.8.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 37 of 218

Bug 48-05 – Error on Vent Sizing Summary for Single-Space Systems
Calculated per Std 62.1.
Date: October 16, 2014
Versions: HAP v4.80, SDL v4.80
Corrected In: HAP v4.90

Problem Has Been Resolved

Please Install HAP v4.90 or later to eliminate problem.
Summary: For the following set of conditions the Ventilation Sizing Summary report displays incorrect values of
“Uncorrected Outdoor Airflow Rate” in section 1 of the report, and “Uncorrected Outdoor Airflow Rate” in section
2. Note that the “Design Ventilation Airflow Rate” is correctly displayed in spite of this error. Conditions required
for the error are:
 Ventilation sizing calculation method is Standard 62.1-2004, -2007, or -2010.
 The air system contains one zone
 The zone contains one space.
 A diversity factor of less than 100% is specified on the Zone Components Tab, Thermostats data view.
Discussion: For the set of conditions listed above, HAP correctly performs the Standard 62.1 calculation,
delivering a correct value of outdoor air intake airflow, Vot. However, when it generates the Ventilation Sizing
Summary report, the “Uncorrected Outdoor Airflow Rate”, Voz, values are adjusted based on the diveristy factor
for the system and therefore displayed incorrectly. Per Standard 62.1 a single-space air system does not include
any adjustments for diversity factor.
Workaround: To avoid this error, make sure the diversity factor specified for the system is set to 100%.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 38 of 218

Bug 48-06 – Error in Std 62.1 Calculation for 15 F Heating Delta-T
Date: October 25, 2014
Versions: HAP v4.80, SDL v4.80
Corrected In: HAP v4.90

Problem Has Been Resolved

Please Install HAP v4.90 or later to eliminate problem.
Summary: For certain types of air systems with design heating supply air temperature specified exactly 15 F
higher than the occupied heating thermostat setpoint, HAP was incorrectly setting the air distribution effectiveness
for Standard 62.1 calculations to 1.0 instead of 0.8. For example, error could occur if the occupied thermostat
setpoint was 70 F and the heating supply temperature was 85 F.
When the error occurred the ventilation outdoor intake airflow (Vot) could be overstated or understated depending
on system and airflow conditions.
Discussion: The following conditions are required for the error to occur:
 Air system type is one of the following:
Single Zone CAV, with central heating coil
Dual Duct CAV, 2-Deck Multizone or 3-Deck Multizone, with heating capability
VVT, with central heating coil
2-Pipe or 4-Pipe Fan Coils, with heating capability
Packaged or Split DX Fan Coils, with heating capability
Variable Refrigerant Flow, with heating capability
WSHP, GSHP or GWSHP
Active Chilled Beams or Induction Beams with heating capability
 Ventilation calculation method is ASHRAE Standard 62.1 (2004, 2007 or 2010 editions)
 Design heating supply temperature is exactly 15 F higher than occupied heating thermostat setpoint.
 The heating design condition establishes the worst case outdoor air intake airflow (Vot)
For these conditions the program incorrectly set the air distribution effectiveness (Ev) to 1.0 instead of 0.8.
Depending on specific system conditions this could result in the outdoor intake airflow Vot being overstated or
understated.
Workaround: The error can be avoided by increasing the heating supply temperature by a small amount such as
0.1 F to make the supply-to-room delta-T slightly larger than 15 F.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 39 of 218

Bug 48-07 – Error 11: Division by Zero during System Design Calculations
Date: October 25, 2014
Versions: HAP v4.80, SDL v4.80
Summary: While running system design calculations the program halts and displays the following error message:

Discussion: This error only occurs for the following situations:

 The system type is “2-Fan Dual Duct VAV” or “1-Fan Dual Duct VAV”
 The ventilation calculation method is “ASHRAE Standard 62.1-2004”, “ASHRAE Standard 62.1-2007”, or
“ASHRAE Standard 62.1-2010”.
 The central heating coil design supply air temperature is exactly 15 F greater than the occupied heating
thermostat setpoint. For example, the heating setpoint is 70 F and the heating supply temperature is 85 F.
Workaround: You can avoid the error by increasing or decreasing the heating supply temperature by 1 F.
Note: While correcting this error in HAP v4.9, an error was discovered in the ASHRAE Std 62.1 calculation
algorithm for 2-Fan Dual Duct VAV and 1-Fan Dual Duct VAV systems. For the heating design condition, the
program is incorrectly setting the space design supply airflow rate (Vdz) for Std 62.1 calculations. In some cases
this will have no effect if the cooling design condition was setting the worst case outdoor air intake airflow (Vot) for
the system. In other cases where the design heating condition sets the worst case Vot, it is possible this error
could cause Vot to be understated or overstated in different situations.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 40 of 218

Bug 48-08 – Error in Std 62.1-2010 Calculations for VAV
Date: November 15, 2014
Revised: November 22, 2014
Versions: HAP v4.80, SDL v4.80

RETRACTED – Not an Error

Summary: This issue was originally identified as a program error on November 15. This bug report was retracted
on November 22, 2014.
Originally it appeared that for variable air volume air systems in which the ventilation sizing method was set to
”ASHRAE Std 62.1-2010”, the ventilation sizing results were incorrect and the ventilation airflow would be
understated. This would only affect VAV, 1-Fan Dual Duct VAV, 2-Fan Dual Duct VAV and VVT air systems. The
original assessment was due to two changes in Appendix A of Standard 62.1-2010:
1. One change involves the definition of the system primary airflow, Vps. Previously Vps was simply the sum of
primary zone airflow rates, Vpz. For a VAV system which is sized at minimum terminal airflow, Vps was the
sum of zone minimum airflow rates. But Standard 62.1-2010 contains the additional statement:
Note: For VAV system design purposes, Vps is the highest expected system primary airflow at the design
conditioned analyzed.
On the surface this suggests Vps should be the maximum supply fan airflow rate for the VAV system rather
than the sum of the zone minimum airflows. However the phrase “at the design condition analyzed” is
ambiguous. Since ventilation rates are still to be determined generally at the minimum zone airflow settings
to identify worst case conditions, the “design conditions analyzed” could mean minimum flow.
The Standard gives no more clarification of this. The ASHRAE Standard 62.1-2010 User’s Manual never
mentions Vps or this issue, so it does not clarify the issue either. The Standard 62.1-2010 62MZCalc
spreadsheet does however show the calculation of Vps in row 43 of the spreadsheet:
Vps = (Vpsd) x (Ds)
where:
Vpsd is the design primary supply fan airflow rate – meaning maximum fan flow at design.
Ds is the percent is the percent of total design airflow at condition analyzed, which accounts for VAV box turn
down.
If Vps was intended to be the maximum supply fan airflow rate, then there would be no reason to distinguish
between Vps and Vpsd. The use of Ds indicates Vps must be synchronized with the turndown of VAV boxes
used for individual zone calculations. Therefore our conclusion is that 62MZCalc indicates Vps is the system
airflow when VAV boxes are turned down, and not at maximum fan flow.
Furrther, if you did interpret the standard as requiring Vps to be the maximum design supply fan airflow rate,
our tests indicated this would result in the outdoor air intake flow (Vot) increasing by a factor of 2 to 3 in many
VAV systems versus required Vot flows from Standards 62.1-2004 and 62.1-2007. That doesn’t seem
reasonable since 62.1 is a mature standard and there have not been complaints that it seriously
underventilates VAV spaces. Also, the Appendix A calculations represent the physics of air dilution in a
multiple zone system. Those physical principles make sense if Vps is the sum of Vpz values, but not if Vps is
the design supply fan airflow rate. By these two reality checks, we believe our conclusion about the
calculation of Vps is correct.
2. The second change was the reformulation of the equation for calculating zone ventilation efficiency, Evz.
In 2004 and 2007 editions, Evz is calculated as:
Evz = (Fa + XsFb –ZdFc) / Fa
In 2010 the equation for Evz was modified as:
Evz = (Fa + XsFb – ZpzEpFc) / Fa
However it turns out the new term (ZpzEp) is equivalent to the old term (Zd) if you expand the terms. So the
old and new equations are actually the same algebraically.

HAP Support Notes rev. 501_05 -- Page 41 of 218

Therefore our final conclusion is that even though language and equation formulation have changed, outdoor
ventilation intake (Vot) ventilation rates calculated with 62.1-2010 will be the same as for 62.1-2004 and 62.1-
2007.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 42 of 218

Bug 48-09 – A-Factor Button Obscures Other Inputs
Date: June 10, 2015
Versions: HAP v4.80, HAP v4.90
Corrected In: HAP 5.0

Problem Has Been Resolved

Please Install HAP v5.0 or later to eliminate problem.
Summary: The 90.1 A-Factor calculations button is located in the wrong place, obscuring the fan configuration
selection options, as shown:

HAP v4.70 – Correct Layout HAP v4.80 – Incorrect Layout

Workaround: If the Fan Type dropdown has focus (is highlighted) and the user presses the TAB key ONE TIME,
then the Configuration options will receive input even though this is not displayed. The RIGHT-ARROW or LEFT-
ARROW keys can be used to select between the two options. The option selected is not shown, but can be checked
by viewing the input report for the air system.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 43 of 218

Bug 47-01 – Error 6 Overflow for SHW Plant Design Calculations
Date: May 13, 2013
Revised: October 31, 2013
Versions: HAP v4.70, System Design Load v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: When running plant design calculations for a "Service Hot Water", or a "Hot Water Plant" or "Steam
Plant" that serves both space and SHW loads, the calculation halts and displays an error message:
HAP47
Error Details:
Number: 6
Description: Overflow
Source:
CIDOReport.CreateContext()
SSNHapSimCtrl470.CSimControl.Run()
SSNHapSimCtrl470.frmProgress.Calculate()
SSNHapPltDesCtrl470.CPltDesignLoad.Calculate
SSNHapPltDesCtrl470.CDesignSHW.Initialize
SSNHapPltDesCtrl470.CDesignSHW.DetermineMaxDesignDayOccupancy
SSNHapPltDesCtrl470
Due to this error design calculations are not completed and no output is generated. Note that this error can also
appear when running plant or building simulation calculations if a plant design calculation is required as part of
that overall calculation.
Discussion: This error occurs when the plant containing the SHW system uses the following
 Consumption Max Rate is defined in units of "gal/person/day" or "L/s/person/day".
 The air systems linked to the plant serve a large occupant population. For example, the initial report of
this error was for a system serving about 1450 occupants.
Note that both conditions must be present for the error to occur. Use of the "gal/person/day" option in a building
with a smaller occupant count does not trigger the error.
Workaround: Define Consumption Max Rate with different units of measure such as gpm or L/s. To make this
change, the following steps are required
1. Edit the plant.
2. On the Systems tab select the air systems in the right-hand box and press the Remove button. The right
hand box should now be empty.
3. On the Service Hot Water tab change the Max Rate units to "gpm" or "L/s". It will also be necessary to
calculate the flow rate (gpm or L/s) that is equivalent to the original specification of gal/person/day or
L/s/person/day.
4. Select or create a fractional schedule defining the hourly profile of service hot water use.
5. Save the plant
6. Perform plant design calculations.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 44 of 218

Bug 47-02 – Air System Design Calculations Not Run Automatically for
Generic Plants
Date: May 21, 2013
Revised: October 31, 2013
Versions: HAP v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: When design sizing calculations are run for any ‘generic’ type of plant, air system design sizing is not
run automatically. This can result in inaccurate plant sizing if the air system results are out of date.
Discussion: HAP uses air system design calculations as the basis for plant design sizing calculations. Normally
when plant design calculations are run, HAP will first check the status of the design calculations for any linked air
systems to make sure they are up to date, and will re-run them if needed.
Calculations may be out of date if any detail of the air system has been changed. This includes details of its linked
spaces, schedules, etc. However, because of this bug HAP does not first check that the air system design
calculations are up to date when sizing of a ‘generic’ plant is performed. Therefore the air system design
calculation will not be run automatically and the plant results could be incorrect.
Notes:
a. If air system design calculations are up to date, plant design results will be correct.
b. This error does not affect any non-generic plant types.
c. This error does not affect the Generic Service Hot Water plant type since it does not serve air system
coils.
Workaround: As long as the air system design calculations have been performed, the plant sizing results will be
correct. Therefore the workaround for this issue is to manually view the air system design reports. Steps:
1. Edit the generic plant and note the linked air systems on the Systems Tab.
2. Close the plant screen.
3. Highlight each of the linked air systems in the HAP main window. (This can be done as a group, or
individually)
4. Choose ‘Print/View Design Results’ from the Reports menu.
5. Click the ‘Preview’ button.
6. Air system reports will be displayed. HAP will perform design sizing calculations if needed.
7. Close the report viewer.
8. Similarly, view the design results for the generic plant(s) of interest. This will now include the latest air
system design results.

Note that it may be ambiguous if the air system design calculations are up to date or not. If in doubt, view any of
the system design reports for the air system(s) in question.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 45 of 218

Bug 47-03 – Error: Unable to load schedule data
Date: June 3, 2013
Revised: October 31, 2013
Versions: HAP v4.70, System Design Load 4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: When running plant design calculations for a plant that serves SHW loads, the calculation halts and
displays an error message:
HAP47
Error Details:
Number: -2147221504
Description: Unable to load schedule data.
Source:
CIDOReport.CreateContext()
SSNHapSimCtrl470.CSimControl.Run()
SSNHapSimCtrl470.frmProgress.Calculate()
SSNHapPltDesCtrl470.CPltDesignLoad.Calculate
SSNHapPltDesCtrl470.CPltDesignLoad.BuildOccupancyProfile()
SSNHapPltDesCtrl470
Due to this error design calculations are not completed and no output is generated. Note that this error can also
appear when running plant or building simulation calculations if a plant design calculation is required as part of
that overall calculation.
Discussion: Space occupancy data is tabulated in order to support the option to determine SHW usage based on
occupancy. This tabulation occurs whenever SHW is used, even if the occupancy option was not selected. This
error occurs only if one or more spaces are defined with zero occupancy, and therefore have no schedule
assigned. The relevant set of linked spaces is those linked to any air systems served by the plant which provides
service hot water.
Workaround: A fractional ‘people schedule’ needs to be added to any linked spaces which lack one. In order to
not influence air system loads, the schedule should be defined at 0% for all hours. HAP will not allow a space to
have a schedule if it has zero occupancy, so we need to set the number of occupants to any value > 0. This will
not affect calculation results since the schedule itself was defined at 0% for all hours which is equivalent to having
zero occupancy.
This alteration to spaces can be most easily done using the search & replace feature once the schedule is
created. Specific steps:
1. Select only the spaces with no occupancy
2. Start search & replace (View menu > Replace)
3. Internals tab > search for “Occupancy (people”) > replace with “1” > click Apply
4. Internals tab > search for “People Schedule” > replace with the new 0% schedule name > click OK

Following this change, the error should no longer occur when plant calculations are run.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 46 of 218

Bug 47-04 – Error 91 ‘Object variable or with block variable not set’ When
Loading an Existing Plant
Date: June 3, 2013
Revised: October 31, 2013
Versions: HAP v4.70, System Design Load 4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem
Summary: When loading an existing plant, the following error is displayed:
The following error condition occurred.
Please contact Carrier Software Systems for assistance.

Error Details:
Number: 91
Description: Object variable or with block variable not set

Source:
frmPlant.Form_Unload
HAP47

A series of errors then follows this initial one, with no recourse but to terminate the program using Windows Task
Manager.
Discussion: When this error occurs, the program is unable to recover, and this causes additional errors to be
displayed. Windows Task Manager must be used to end the HAP47.exe program, after which HAP can be
restarted.
The cause of this error is that one or more of the air systems linked to the plant no longer contain coils which
match the plant output. For example, a Chilled Water Air Handler air system has been changed to a Packaged
Rooftop. The chilled water coils which were originally present in the air system are no longer present, but the air
system is still linked to a Chiller Plant. This can also occur for hot water coils or steam coils.
Notes:
1. This issue cannot occur when creating a new plant, because only matching air systems will be listed at that
time.
2. It is possible to double-check which air systems are linked to the plant by displaying the input data report
(Reports menu > View Input Data). This will not cause the error.
Workaround: Once this error has occurred, HAP must be terminated as noted above. Afterwards, reload HAP
and the project which was being worked on. In order to prevent the error from occurring again, there are several
procedures which can be used:
1. Delete the plant: If the air system in question was the only one linked to the plant, the plant is no longer
needed.
2. Delete and re-create the plant. This may only be suitable if the plant definition was not heavily customized.
3. Modify the air system to temporarily add back the missing coil. Then, open the plant and remove the air system
on the Systems Tab. Finally, modify the air system to again remove the coil.
In order to prevent this issue from occurring in the future, first remove an air system from any linked plants, and
second modify the air system. This will avoid the error.
Back to Table of Contents

Bug 47-05 – Dehumidification Heating Coil not Correctly Recognized

Date: June 3, 2013
Revised: October 31, 2013

HAP Support Notes rev. 501_05 -- Page 47 of 218

Versions: HAP v4.70, System Design Load 4.70, HAP v4.6, System Design Load 4.6

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: If the dehumidifier is the only use of either steam or hot water in an air system, that system will not be
correctly recognized as having a steam or hot water coil. This will prevent it from being selected for plants.
Discussion: Based on how an air system is configured, HAP categorizes the type of heat exchange coils it uses.
There can be one or more coils of three types: chilled water, hot water, or steam. When configuring a plant, HAP
determines which air systems are relevant and can be linked to the plant based on this categorization. If
dehumidification is the only component of an air system to use of either hot water or steam, HAP does not
correctly recognize the coil. Therefore, the air system cannot be linked to the plant. If any other component uses
the same heating source, this issue does not occur.
Notes: This does not affect cases where the dehumidifier uses a heat source other than hot water or steam (such
as electric or fuel-based dehumidifiers).
Workaround: An additional air system component should be enabled using the same heat source, but configured
to have zero effect on the calculations. For example, for a Packaged Rooftop air system using hot water for the
dehumidifier, the component “Preheat Coil” could also be enabled, but with its monthly schedule set so that all
months are “off”.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 48 of 218

Bug 47-06 – Air System Space List Shows Blank Line
Date: June 3, 2013
Revised: October 31, 2013
Versions: HAP v4.70, System Design Load v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: When adding spaces to an air system, in some instances spaces previously added will be shown as
blank in the list. This is a display issue as no data has been altered, but may be confusing.
Discussion: This issue is caused by a bug in how the text colors in the space list are set. In some instances the
text color is set to the same as the background, making the text effectively invisible. This can occur, for instance,
with the following sequence of steps:
1. Create several spaces
2. Create a new air system
3. Add the first space to the list
4. Add the second space to the list
5. Increase the multiplier of the second space – the first space added will seem to disappear.
Notes: None
Workaround: Clicking on another tab of the air system window and then back to the Zone Components > Spaces
tab will restore the list. The list is also correctly displayed when an existing air system is re-opened from the main
window. The total list of spaces can be displayed using the air system input report, which is not affected by this
issue.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 49 of 218

Bug 47-07 – Hot Water Plant Using Heat Pumps Erases Linked Geothermal
Source
Date: July 19, 2013
Revised: October 31, 2013
Versions: HAP v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: The user converts a project from HAP 4.6 or earlier. They then modify an existing hot water plant to
use water-source heat pumps, and link a geothermal source (i.e., “cooling tower”) to the plant and save it. When
they reload the plant later, the linked geo source is gone. Alternately, they receive a validation error when
attempting to simulate the plant.
Discussion: This issue occurred because a bug in the conversion process from HAP 4.6 to HAP 4.7 data. This
bug causes invalid data to be stored with the hot water plant definition.
Notes: None
Workaround: The plant must be recreated by the user. The project as a whole however is valid and can be used.
Only hot water plants which will use water-source heat pumps will need to be recreated. After creation, the new
plants may need to be added to any buildings in the project. Once complete, the original plants can be deleted,
and the new plants used for all purposes.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 50 of 218

Bug 47-08 – Generic SHW Plants and Generic Changeover Plants Are Not
Listed
Date: July 19, 2013
Revised: October 31, 2013
Versions: HAP v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: When HAP is running with energy analysis features turned off, Generic SHW plants and Generic
Changeover plants will not be listed in the HAP main window. These plants can be created and saved, but then
will fail to be displayed in the list.
Discussion: None.
Notes: None.
Workaround: If these types of plants need to be used, HAP should be run with energy analysis features turned
on (even though they may not be required). That will ensure all plant types are listed.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 51 of 218

Bug 47-09 – Air System Cooling Capacity Control Option Spontaneously
Reset
Date: July 19, 2013
Revised: October 31, 2013
Versions: HAP v4.70, SDL v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: A user creates an air system and sets the central cooling coil capacity control option to one of the
‘reset’ options. The air system is then saved. When the user later opens the air system again, the control option
has been reset to “Cycled or staged capacity, fan on” which was not what they had selected.
Discussion: This bug occurs at the moment when the air system is reloaded for editing. The user’s control option
is correctly saved when the air system window is closed, and it will be used correctly for all calculations. In
addition, if the air system input report is viewed, this will confirm that the option was saved correctly.
Notes: None.
Workaround: Although there is no way to avoid this bug, as long as the user saves the air system with the
correct control option no further problems should occur. They will need to change its value each time the open
and save the air system. If changes are not needed, the user should view the air system using the input report, or
click ‘cancel’ instead of OK if viewing the details through the air system screen.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 52 of 218

Bug 47-10 – Plant Secondary Pump Flow Displayed Incorrectly in Metric
Date: September 10, 2013
Revised: October 31, 2013
Versions: HAP v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: When running HAP using metric units, the secondary pump flow rate on the plant screen distribution
tab displays the wrong value. This occurs for any plants which use boilers, heat pumps, or chillers (not generic or
remote plants).
Discussion: This is the result of an error in how the value is converted to metric for display purposes. The
underlying data stored in the HAP project is not affected. This can be confirmed by viewing the input report for the
plant, which will show the correct value.
Notes: In some cases the flow rate is not known at design-time, such as when all chillers, boilers, or heat pumps
in the plant did not have flow rates specified in like units. In these cases, there is no issue in the display. This
issue also does not pertain to any type of “generic” plant, as these plants do not use the distribution tab at all. For
remote plants, see Bug 47-11.
Workaround: Run HAP in US / English units, or use the plant input report for reference since the secondary
pump flow is shown for informational purposes only, and is not editable.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 53 of 218

Bug 47-11 – Remote Plant Secondary Pump Flow Saved Incorrectly in
Metric
Date: September 10, 2013
Revised: October 31, 2013
Versions: HAP v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: When running HAP using metric units, the secondary pump flow rate entered by the user for any
remote source plant will be saved incorrectly. Subsequent re-loading of the plant will show a different value than
what was entered.
Discussion: This is the result of an error in how the value is converted to/from metric. The internal data storage
format for a HAP project is in English units, therefore a conversion is required whenever a plant is saved. The
error is introduced at the time the plant is saved.
Notes: None.
Workaround: Run HAP in US / English units when the plant is edited. If the plant is saved when in English units,
the correct value will be saved. For reference, the conversion factor between Metric and English is 1 L/s = 15.85
GPM. Therefore in English units, enter the value in GPM which is 15.85 times the desired value in L/s.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 54 of 218

Bug 47-12 – Insufficient Cooling for System without HW Coils
Date: April 7, 2014
Versions: SDL v4.70, SDL v4.80, HAP v4.70, HAP v4.80
Corrected In: HAP v4.90

Problem Has Been Resolved

Please Install HAP v4.90 or later to eliminate problem.
Summary: For a 2-pipe fan coil air system with electric terminal heating, many of the systems (zones) will not
hold to their cooling setpoint and have temperatures floating very high for many hours per year (perhaps
thousands).
Though much less likely, this could also occur for a chilled water air handling unit.
This would be evident on the design and/or simulation results, as shown below.
Design Reports > Hourly Zone Loads Report:

Simulation Reports > Zone Temperature Report:

Discussion: There is a flaw with the way air system data is being saved for a 2-pipe system.
When the user creates a new 2PFC system, the 2-pipe changeover settings (on the Air System / Equipment tab)
are defaulted to “used”. If the user changes the system from HW-based heating to electric heating the 2-pipe
settings no longer have any relevance, since changeover is not needed when the pipes are not used for both HW
and CW. As a result the 2-pipe settings are hidden on the Equipment tab.
However the flaw is that the underlying data saved with the air system is NOT reset to “off” in that case. As a
result, this bad data causes the calculations to act as though cooling is not available for many hours of the
simulation.
This could happen for a CW AHU system as well, but that is much less likely since the 2-pipe option is OFF by
default for that system type. A user would have had to manually turn it on, but then change all coil heating
sources to electric for this bug to occur.

HAP Support Notes rev. 501_05 -- Page 55 of 218

Workaround: To ensure that 2-pipe settings are correctly saved:
1. Open the air system in question
2. Temporarily change the terminal heating source to HW (Zone Components Tab / Common Data):

3. Uncheck the 2-pipe changeover “Used” option (Equipment Tab / Changeover Controls):

then:

4. Change the heating source back to Electric:

5. 2-pipe settings are again hidden, but correct data will be saved.
6. Run calculations as normal.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 56 of 218

Bug 47-13 – Error 440 Occurs During Plant Energy Simulation
Date: June 26, 2014
Versions: HAP v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem
Summary: Plants with water-cooled chillers may receive the following errors when running energy simulations:

[Error number 440: Automation error]

[Run-time error '11': Division by zero [bridged error from unspec.unspec.unspec]]

Discussion: This is a user interface bug which causes invalid data to be saved. When a user visits the plant
configuration tab, the cooling tower setting is automatically and incorrectly reset to “individual”. This occurs when
opening a previously saved plant or just clicking through the user interface. This may leave cooling tower
equipment selections in an inconsistent state when the plant is saved. The error occurs during the simulation due
to this bad data.
Note that this bug appears to be somewhat obscure, in that it was first reported in the field in June 2014, though
HAP v4.7 was released in 2012.

Workaround: None known.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 57 of 218

Bug 47-14 - HAP Encountered a Problem and Needs to Close – Tablet /
Touch Screen
Date: October 6, 2010
Revised: October 31, 2013

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem
Summary: Either during the HAP startup sequence or later during program operation, the program halts and
displays the following error message:

Carrier Hourly Analysis Program v4.x

Carrier Hourly Analysis Program v4.x has encountered a problem and needs to close. We are sorry for
the inconvenience.

To see what data this error report contains Click Here.

If you click the "Click Here" item, further information appears:

Error Signature
AppName: HAP46.EXE
AppVer: 4.50.0.42
ModName: COMCTL32.OCX
ModVer: 6.0.81.5
Offset: 00020151
Note: For computers running Windows 7 or later the "click here" option is typically not offered.

In some cases the following error message is displayed instead:

(“HAP47.exe has stopped working”). When the user clicks “close the program”, HAP is no longer running.

Discussion. Originally this issue was observed on tablets, but with the release of Windows 8, many desktop and
laptop computers are starting to offer touch screen features as well which also have this problem.
The error message is a Windows generated message. The error signature information indicates there is a
problem with the Microsoft supplied software component COMCTL32.OCX which is used by HAP.

Workarounds.

HAP Support Notes rev. 501_05 -- Page 58 of 218

1. HAP v4.8 has been reported to fix this issue, but testing has been limited at time of release (November, 2013).
This note is being left “open” until this can be confirmed.
2. There are reports on the web of compatibility problems between the COMCTL32.OCX file and tablet PCs.
Microsoft offers a solution that includes upgrading to v6.0.81.6 of this file – see
http://support.microsoft.com/kb/896559. NOTE: CARRIER CANNOT RECOMMEND THIS SOLUTION. Because
we are not able to test the solution on a tablet or touch screen PC we cannot advise whether this is a safe,
effective solution. The Microsoft solution appears to involve upgrading a number of the key operating system files
including COMCTL32.OCX and once installed the upgrade cannot be uninstalled. Therefore there may be
significant risk involved in trying this solution. Only a person with IT training and Windows expertise should
evaluate whether this solution is safe to apply and whether it will have any effect on the problem. Even if this
solution is safely applied, there may be incompatibilities between the Tablet PC and other Microsoft-supplied files
that prevent the software from running properly

Notes. This is not a problem with Windows 8 computers in general – it is specific to those with touch screens.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 59 of 218

Bug 46-00 – 2PFC and 4PFC Terminals with Electric Heating Consume no
Energy
Date: April 3, 2014
Versions: HAP v4.60, v4.61, v4.70

Problem Corrected
Please Install HAP v4.80 or later to eliminate problem

Summary: When a 2 or 4 pipe fan coil air system uses electric heating in the terminals, it will have a "Terminal
Heating Coil Input" of zero for all hours in the simulation results. This will affect building energy use as well, for
any buildings linked to such an air system.
Discussion:
None.
Workaround: Using hot water as the source of terminal heating plus a hot water plant with an electric boiler
should give a similar result of energy use at the building level. Make sure to reduce other sources of plant energy
such as pumps to zero.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 60 of 218

Bug 45-01 - "Error 380 - Invalid Property Value"
Date: February 10, 2000
Revised: July 27, 2016
Corrected in: HAP v5.01, SDL v5.10 (due out early 2017)

Problem Has Been Resolved

Please Install HAP v5.01 or later to eliminate problem.

Summary: While running HAP, the following error message appears:

Error 380 - Invalid Property Value
This error appears while performing the following actions within HAP:
 Creating a new schedule or editing an existing schedule from the main program window.
 Creating a new schedule or editing an existing schedule via the space input form.
 Creating a new system or editing an existing system from the main program window.
 Creating a new plant or editing an existing plant from the main program window.
 Using the Rotate option on the Edit Menu in the main program window.

Diagnosis: We have found two causes for this problem, both involving fonts. Thus, the first step in dealing with
this problem is to determine which cause applies. The cause will determine the workaround solution.
1. From the Windows desktop press Start, choose Settings and then choose Control Panel.
2. In the Control Panel double click on the Fonts icon.
3. Inspect the list to see if there is an entry “MS San Serif” or “MS Sans Serif Regular”. Fonts are usually listed
alphabetically. If you can’t find the MS San Serif icon, then the MS San Serif font is not installed on your
computer. This is one cause of the Error 380 message.
4. Next, click on the View Menu on the menu bar of the Fonts window and choose the Options item.
5. In the Options dialog, click on the True Type tab.
6. On the True Type tab, check to see if the box next to “Show only True Type fonts” is checked. If it is checked,
this may be causing the Error 380 message.
7. At this point leave the Font window open. It is used in the workarounds for both causes.

Workaround for Missing Font. If you found that the font was missing from your computer, use the following
procedure to install it.
1. Obtain the MS San Serif font installation file (SSERIFFE.FON) from Carrier Software Systems and save it to a
temporary folder on your hard disk.
2. Run Windows Explorer. If it starts in full screen mode, change it to window mode by pressing the middle of
the three buttons in the upper right-hand corner of Explorer.
3. Position the Windows Explorer and Fonts windows so both are visible on your computer screen at the same
time.
4. Use Windows Explorer to locate the SSERIFFE.FON file that you saved to your hard disk in step #1 above.
Click once on the SSERIFFE.FON file name and hold the left-hand mouse button down. Then drag the file and
drop it on the Font window. When the file is dropped on the Font window, a message should appear indicating
the font is being installed. When installation is finished, you should see an “MS Sans Serif Regular” icon in
your Fonts window.
5. Close the Fonts window.

HAP Support Notes rev. 501_05 -- Page 61 of 218

6. Close Windows Explorer.
7. Try running HAP and see if you can create or edit schedule data. If so, the problem has been resolved.

Workaround When “Show Only True Type Fonts” is Marked:

1. In the Fonts Window click on the View Menu and choose the Options item.
2. In the Options dialog, click on the True Type tab.
3. On the True Type tab, uncheck the box for “Show Only True Type Fonts…”.
4. Then press the OK button to save this change.
5. Then reboot your computer when prompted.
6. After rebooting, run HAP and see if you can create schedules or edit existing schedule data. If you can,
“Show Only True Type Fonts” was the culprit.

(Bug 22970)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 62 of 218

3.0 Common Errors – International Edition Issues
Error e400 - Invalid Authorization Code
Date: April 24, 2014
Revised: January 6, 2015
Summary: The first time HAP is run, the customer number and authorization code are entered. When the user
presses OK the following error appears:
Invalid authorization code. Please try again. (e400)
This error occurs because one or more of the following was incorrectly specified:
 Company Name
 Customer Number
 Authorization Code
Workaround. Use the following procedure to correct this problem:
1. Return to the Enter Authorization Code screen and re-enter the customer number and authorization code.

2. Before pressing [OK] compare the Company Name (shown on the screen), the customer number, and the
authorization code with the e-mail you received that contained this information. Each item must match the
data shown on the e-mail exactly. Any differences in characters, extra spaces, punctuation, and capitalization
can cause the validation of the authcode to fail.
 One common error involves the character "0" in the authorization code. This is a zero, not the letter "O".

3. If you find the customer number or authorization code contain errors, it is easy to correct your inputs on the
screen and then continue.

4. If you find the company name is incorrectly specified, the following steps are needed to correct the name:
 Exit the software.
 From the Windows desktop press Start and choose All Programs > Carrier E-CAT and E20-II Programs >
Utilities > Change Company Name
 Press [OK] on the Change Company Name title screen.
 On the Change Company Name screen, enter the corrected company name and press the [CHANGE
COMPANY NAME] button.
 Start HAP again.
 On the Enter Authorization Code screen the revised company name will appear. Enter your customer
number and authorization code. Press [OK].

5. Once company name, customer number and authorization code are correctly specified, you will be able to
press [OK] and have the authorization information accepted.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 63 of 218

Error 7 - Corrupt Header
Date: March 14, 2012
Revised: September 22, 2016
Versions: HAP International Edition, HAP North American Trial Version
Summary: When starting the program, the following error message appears:
Authorization Error.
Please make a note of the following error and contact technical support for assistance
Number: 7
Description: Corrupt Header
Module: frmAuthCode
Method: cmdOK_Click
This error can occur in the following two situations:
 The program is being started for the first time and you have entered the customer number and
authorization code on the Enter Authorization code screen. When you press the OK button the error
appears.
 =OR= The software was previously run and successfully authorized. At a later time when you try to start
the program the error message appears and prevents the program from running.
Workaround:
1. Start Windows Explorer
2. Navigate to the C:\E20-II\Enviro folder. Note that this folder will always be on C: drive even if HAP was
installed to a different drive.
3. In that folder erase the ZOEBRD01.DAT file and the ZOEBRD01 subfolder. In some situations this file or
folder will not be present. If so, simply continue on.
4. From the Windows desktop press Start and then choose Settings > Control Panel > Date and Time
5. In the Date and Time window verify the computer date is correct. If it is not correct, specify the correct date
and then press OK to save the change.
6. Start HAP and enter the authorization code information. The authorization should be accepted this time.

Further Workaround for Error 7. If you have an Error 7 and the 6-step procedure above did not resolve the
problem, we have found the following additional steps below may be needed to resolve this error. This involves a
situation where there are multiple copies of ZOEBRD01.DAT and ZOEBRD01 on the computer or on connected
drives, and one of these additional copies is corrupt. There should only be one copy of these in the C:\E20-
II\ENVIRO folder. But we’ve found rare situations where additional copies existed. The solution is to locate every
excess copy of the file or subfolder and erase each copy found.
1. Start Windows Explorer
2. In the left-hand tree panel navigate to the C: root folder.
3. In the search field in the upper right of the Explorer window type ZOEBRD01 and press ENTER. The
computer will search for any copies of ZOEBRD01.DAT and ZOEBRD01 on the entire C: drive and will
display any copies found anywhere on the drive.
4. If any copies are shown in the search results (right-hand panel in Explorer), erase each copy found.
5. If your computer has a D: drive (or any other) partition on your hard disk, repeat steps 2-4 for that drive
instead of C: drive.
6. If your computer is connected to external drives or network drives, repeat steps 2-4 for each of these
connected drives instead of C: drive.
7. Finally, after all connected drives have been searched and excess copies of the file or subfolder deleted, start
HAP and enter the authorization code information. The Error 7 should be eliminated now.
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 64 of 218

Errors 106 and 109
Date: March 14, 2012
Revised: September 22, 2016
Versions: HAP International Edition, HAP North American Trial Version

Summary: This topic describes the standard workaround procedure used to correct either of the following
problems. When starting the program, the following error message appears:
Authorization Error.
Please make a note of the following error and contact technical support for assistance
Number: 106
Description: Internal Error 106-L344A
Module: frmAuthCode
Method: cmdOK_Click
OR – When starting the program the following error message appears:
Authorization Error.
Please make a note of the following error and contact technical support for assistance
Number: 109
Description: Internal Error 109-L343A
Module: frmAuthCode
Method: cmdOK_Click
These error messages could appear in two different kinds of situations:
 The program is being started for the first time and you have entered the customer number and
authorization code on the Enter Authorization code screen. When you press the OK button the error
appears.
 =OR= The software was previously run and successfully authorized. At a later time when you try to start
the program the error message appears and prevents the program from running.

Workaround:
Note – the steps below require providing the customer with a ZIP file which is posted on HVACPartners. It has a
3 month duration so is constantly being updated. Always best to download the current copy for use.
 After logging in to HVACPartners, navigate to Products & Solutions > Software > eDesign Suite >
International eDesign.
 The link for the authcode.zip is in the bottom of the first table (figure below). The password for the file is
also listed in that location.

HAP Support Notes rev. 501_05 -- Page 65 of 218

Customer instructions: Use the following steps to resolve the problem:
1. From the Windows desktop press Start and then choose Settings > Control Panel > Date and Time
2. In the Date and Time window verify the computer date is correct. If it is not correct, specify the correct date
and then press OK to save the change.

3. Save the Authcode.ZIP file provided by Carrier to your hard disk. This ZIP contains a patch program that is
valid for one month at a time. Therefore it must be obtained from Carrier technical support each time this error
arises to ensure you have a copy of the file that is valid for the current month.
4. Unzip the file to produce one file named Authcode.exe
5. Double-click the Authcode.exe file to run it. Follow the simple instructions which appear on the screen.

6. Start HAP and enter the authorization code information. The authorization should be accepted this time.

Further Information for Errors 106 and 109. If you have an Error 106 or 109 and the 9-step workaround
procedure above is not successful, one further issue to investigate is permissions in the Windows registry. Two
warnings:
Warning 1 - You will need administrative rights to edit the registry. This means logging in as the computer
administrator, or having admin rights with your own login ID.
Warning 2 - Only a qualified individual should edit the registry. If the registry is improperly modified, that can
cause serious computer operating problems.
1. Edit the Windows Registry
2. Navigate to HKEY_LOCAL_MACHINE > Software > Carrier > MDG001
3. Right-click on this registry node and select Permissions in the pop-up menu.
4. In the Permissions window make sure the user login ID who will be running HAP on this computer has Full
Permissions for this registry node.
5. After fixing the Permissions, log in under the user ID, start HAP and enter the authorization code information.
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 66 of 218

Error 31 - Unknown Error Posted 21
Date: March 14, 2012
Summary: When starting the program, the following error message appears:
Authorization Error.
Please make a note of the following error and contact technical support for assistance
Number: 31
Description: Unknown Error Posted 21
Module: frmAuthCode
Method: cmdOK_Click
This error can occur in the following two situations:
 The program is being started for the first time and you have entered the customer number and
authorization code on the Enter Authorization code screen. When you press the OK button the error
appears.
 =OR= The software was previously run and successfully authorized. At a later time when you try to start
the program the error message appears and prevents the program from running.
Workaround: The most likely cause of this error is that the computer user does not have full file access rights to
the C:\E20-II\Enviro folder on the computer. Therefore to resolve this problem:
1. Verify with your computer administrator that your login ID has full file access rights to C:\E20-II\Enviro. Full
rights allow reading, writing, creation and deletion of files in that folder. Alternately, try copying a file into
C:\E20-II\Enviro. If insufficient rights exist, an error message will appear when you try to paste the file into
C:\E20-II\Enviro.
2. Once you have file access rights for this folder, start HAP. It should run this time.
If file access rights do not resolve the error, additional possible causes of this error are as follows. Contact Carrier
technical support for assistance if any of these are the source of the problem.
a. There is a problem with the operation of C: drive.
b. The computer does not have a drive designated as C:.
c. There is a previous installation of Carrier software on the computer and somehow the authcode files for that
software were written to a drive other than C:, and that other drive is not accessible.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 67 of 218

Internal Error 201-M327A While Running AuthCode.exe
Date: March 14, 2012
Summary: When starting the Authcode.exe patch program as part of the Standard Workaround for Errors 7, 106
and 109., the program halts and displays the following error message:
Authcode Cleanup Program
Internal Error 201-M327A
This prevents the Authcode.exe program from running.
Workaround: This error can be due to two different problems. The problem and the solution for each case are
described below.
Problem 1 - Authcode.exe File has Expired
The Authcode.exe patch program used to correct Errors 7, 106 and 109 is a limited duration program. Each
version of the program will only run for one month; a new version is issued at the start of each month. If you
are using an old version of this program that has expired, then the "Internal Error 201-M327A" error will occur
when you try to run the program. The solution is to obtain the current version of Authcode.exe from Carrier
and use that. Note that Authcode.exe is distributed in a ZIP file and the name of the ZIP file indicates the
version. For example the file Authcode_2008_Oct.ZIP contains a version of Authcode.exe that is valid for
October 2008.
Problem 2 - Computer Date Setting is Incorrect
If you are using the current version of Authcode.exe, valid for the current month, but the computer date setting
is incorrect, the "Internal Error 201-M327A" error will occur.
Example: It is October 2008 and you are using the Authcode.exe version valid for October 2008.
However, the computer date is incorrectly set to January 2010. The Authcode.exe program validates itself
against the computer date, and therefore believes it is January 2010. Therefore the program believes it has
expired and will not run.
The solution in this case is to input the correct date for the computer. To do this:
a. From the Windows Desktop press Start and choose Settings > Control Panel > Date and Time
b. In the Date and Time window, enter the correct date and press OK to save the setting.
c. Then run the Authcode.exe program.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 68 of 218

3.1 Common Errors – North American Demo Version Issues
Troubleshooting 90-Day Demo Problems
Date: March 14, 2012
Summary: The HAP Demonstration Version is a special 90-Day Demo version of HAP that are given to
prospective customers in the US and Canada. The prospective customer can run the program for 90 days while
evaluating it and deciding whether to license it. To run the 90-Day Trial version, the user must enter an
authorization code (obtained from Carrier) the first time the program is started. This topic explains how to
troubleshoot situations where a customer enters the authorization code and the program rejects it displaying an
“Invalid Authorization Code” message.
Troubleshooting Procedure:
1. Make sure the authorization code entered is correct. It must match the authorization code e-mailed to the
customer by Syracuse.
a. Note that the hyphens in the authorization code are optional. The code will be accepted with or without
the hyphens.
b. Make sure that any “0” character is a zero, not an “o”. The authorization code will contain only numerals
and the letters A thru F.
2. Make sure the demo code shown in the authorization code window exactly matches the e-mail sent to the
customer by Syracuse.

3. If the authorization code and demo code are entered correctly and the authorization code is still rejected,
check the date setting for the computer. If it is not set to today’s date, that may be causing the problem.
Resetting it to the correct date will resolve this problem.
Example: One customer inadvertently had the computer date set to sometime in the future. Because the 90-
day trial period is based on the date and time the authorization code is generated, a date beyond the end of
the trial period prevented the authorization code from being accepted.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 69 of 218

 “The 90-Day Trial Period Has Expired. Please Contact Carrier”
Date: March 14, 2012
Summary: A customer has been successfully running the demonstration version of HAP for some time. At some
point the customer tries to start the program and receives an error message:
The 90-day trial period has expired...Please contact Carrier”
This error must be incorrect because the 90-day trial period has not ended yet.
Workaround. The cause of this error is not known, but the problem can be resolved using the Standard
Workaround for Errors 7, 106 and 109.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 70 of 218

HAP and Block Load Demo Versions Cannot be Active on a Computer at
the Same Time
Date: March 14, 2012
Summary: It is currently not possible to have demo versions of HAP and Block load active on a computer at the
same time. That is, you cannot alternate between programs on the same computer nor can they be run
simultaneously.
Example: The following example illustrates the problem:
1. The HAP demo version is installed.
2. The first time the HAP demo version is started, it asks for the authorization code. The code is successfully
entered and the program runs.
3. The Block Load demo version is installed.
4. The first time the Block Load demo version is started, it informs you the demonstration period has expired,
and the program cannot be run.
The Block Load demo version has not really expired of course. Instead, there is a limitation that prevents demo
versions of two different programs from being run on a computer at the same time.
Workaround: While you cannot alternate between the HAP and Block Load demos or run them simultaneously
on a computer, you can activate a second demo program as follows:
1. Run Windows Explorer and navigate to the C:\E20-II\ENVIRO folder.
2. In this folder, erase the ZOEBRD01.DAT file and the ZOEBRD01 subfolder.
3. Start the program (HAP or Block Load) and enter the authorization code as requested. The program will then
run.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 71 of 218

Error e400 - Invalid Authorization Code
Date: March 14, 2012
Summary: The first time HAP is run, the demo code and authorization code are entered. When the user presses
OK the following error appears
HAP47
Invalid authorization code. Please try again. (e400)
This error occurs because one or more of the following is incorrectly specified:
 Demo Code
 Authorization Code
Workaround. Use the following procedure to correct this problem:
1. Return to the Enter Authorization Code screen and re-enter the demo code and authorization code.
2. Before pressing OK compare the demo code and the authorization code with the e-mail you received that
contained this information. Each item must match the data shown on the e-mail exactly. Any differences in
characters, extra spaces, punctuation, and capitalization can cause the validation to fail.
 One possible error involves the character "0" in the authorization code. This is a zero, not the letter "O".
3. If you find the demo code or authorization code contain errors, it is easy to correct your inputs on the screen
and then continue.
5. Once demo code and authorization code are correctly specified, you will be able to press OK and have the
authorization information accepted.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 72 of 218

Error 106
Date: March 14, 2012
Summary: When starting the program, the following error message appears:
Authorization Error.
Please make a note of the following error and contact technical support for assistance
Number: 106
Description: Internal Error 106-L344A
Module: frmAuthCode
Method: cmdOK_Click
This error can occur in the following two situations:
 The program is being started for the first time and you have entered the demo code and authorization
code on the Enter Authorization code screen. When you press the OK button the error appears.
 =OR= The software was previously run and successfully authorized. At a later time when you try to start
the program the error message appears and prevents the program from running.
Workaround. To resolve this problem use the Standard Workaround for Errors 7, 106 and 109.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 73 of 218

Error 109
Date: March 14, 2012
Summary: When starting the program, the following error message appears:
Authorization Error.
Please make a note of the following error and contact technical support for assistance
Number: 109
Description: Internal Error 109-L343A
Module: frmAuthCode
Method: cmdOK_Click
This error can occur in the following two situations:
 The program is being started for the first time and you have entered the demo code and authorization
code on the Enter Authorization code screen. When you press the OK button the error appears.
 =OR= The software was previously run and successfully authorized. At a later time when you try to start
the program the error message appears and prevents the program from running.
Workaround. To resolve this problem use the Standard Workaround for Errors 7, 106 and 109.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 74 of 218

Error 7 - Corrupt Header
Date: March 14, 2012
Summary: When starting the program, the following error message appears:
Authorization Error.
Please make a note of the following error and contact technical support for assistance
Number: 7
Description: Corrupt Header
Module: frmAuthCode
Method: cmdOK_Click
This error can occur in the following two situations:
 The program is being started for the first time and you have entered the demo code and authorization
code on the Enter Authorization code screen. When you press the OK button the error appears.
 =OR= The software was previously run and successfully authorized. At a later time when you try to start
the program the error message appears and prevents the program from running.
Workaround. To resolve this problem use the Standard Workaround for Errors 7, 106 and 109.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 75 of 218

Error 31 - Unknown Error Posted 21
Date: March 14, 2012
Summary: When starting the program, the following error message appears:
Authorization Error.
Please make a note of the following error and contact technical support for assistance
Number: 31
Description: Unknown Error Posted 21
Module: frmAuthCode
Method: cmdOK_Click
This error can occur in the following two situations:
 The program is being started for the first time and you have entered the demo code and authorization
code on the Enter Authorization code screen. When you press the OK button the error appears.
 =OR= The software was previously run and successfully authorized. At a later time when you try to start
the program the error message appears and prevents the program from running.
Workaround: The most likely cause of this error is that the computer user does not have full file access rights to
the C:\E20-II\Enviro folder on the computer. Therefore to resolve this problem:
1. Verify with your computer administrator that your login ID has full file access rights to C:\E20-II\Enviro. Full
rights allow reading, writing, creation and deletion of files in that folder. Alternately, try copying a file into
C:\E20-II\Enviro. If insufficient rights exist, an error message will appear when you try to paste the file into
C:\E20-II\Enviro.
2. Once you have file access rights for this folder, start HAP. It should run this time.
If file access rights do not resolve the error, additional possible causes of this error are as follows. Contact Carrier
technical support for assistance if any of these are the source of the problem.
a. There is a problem with the operation of C: drive.
b. The computer does not have a drive designated as C:.
c. There is a previous installation of Carrier software on the computer and somehow the authcode files for that
software were written to a drive other than C:, and that other drive is not accessible.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 76 of 218

Internal Error 201-M327A While Running Authcode.exe
Date: March 14, 2012
Summary: When starting the Authcode.exe patch program as part of the Standard Workaround for Errors 7, 106
and 109., the program halts and displays the following error message:
Authcode Cleanup Program
Internal Error 201-M327A
This prevents the Authcode.exe program from running.
Workaround: This error can be due to two different problems. The problem and the solution for each case are
described below.
Problem 1 - Authcode.exe File has Expired
The Authcode.exe patch program used to correct Errors 7, 106 and 109 is a limited duration program. Each
version of the program will only run for one month; a new version is issued at the start of each month. If you
are using an old version of this program that has expired, then the "Internal Error 201-M327A" error will occur
when you try to run the program. The solution is to obtain the current version of Authcode.exe from Carrier
and use that. Note that Authcode.exe is distributed in a ZIP file and the name of the ZIP file indicates the
version. For example the file Authcode_2008_Oct.ZIP contains a version of Authcode.exe that is valid for
October 2008.
Problem 2 - Computer Date Setting is Incorrect
If you are using the current version of Authcode.exe, valid for the current month, but the computer date setting
is incorrect, the "Internal Error 201-M327A" error will occur.
Example: It is October 2008 and you are using the Authcode.exe version valid for October 2008. However,
the computer date is incorrectly set to January 2010. The Authcode.exe program validates itself against the
computer date, and therefore believes it is January 2010. Therefore the program believes it has expired and
will not run.
The solution in this case is to input the correct date for the computer. To do this:
a. From the Windows Desktop press Start and choose Settings > Control Panel > Date and Time
b. In the Date and Time window, enter the correct date and press OK to save the setting.
c. Then run the Authcode.exe program.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 77 of 218

3.2 Common Errors – Installation
Installation Problem: This Software Requires Service Pack 4
Date: Oct. 6, 2008
Updated: January 6, 2015
Summary: While installing HAP the following error message appears:
Installation Problem:
This software requires Service Pack 4 or later when running on Windows NT v4.0.
When you press the OK button in the message box, the installation terminates.
Discussion: Microsoft has released several updates to the Windows NT v4.0 operating system. It refers to these
updates as “Service Packs”. They typically contain bug fixes for the operating system. If the Windows NT
operating system is being used, then HAP requires that the Service Pack 4 edition (or a later edition) of Windows
NT v4.0 be installed. Windows Internet Explorer v4.0 or later is also required.
Workaround: If this error message is encountered, we recommend the following workaround procedure:
1. When the error message appears, press the OK button to exit from the message box.
2. Obtain the current Windows NT Service Pack from Microsoft and install it on your computer.
3. If necessary, install Windows Internet Explorer v4.0 or later.
4. Install the HAP software again.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 78 of 218

Installation Problem: You Must be the Administrator...
Date: Oct. 6, 2008
Updated: January 6, 2015
Summary: While installing HAP the following error message appears:
Installation Problem:
You must be the administrator or have administrative rights to install this software on Windows NT.
When you press the OK button in the message box the installation terminates.
Discussion: Windows NT, 2000 and XP all require you to log on to your computer. Typically, all workstations
have an “Administrator” user ID which provides full read/write access to all parts of the local hard disk. Other user
IDs may be restricted in their access to certain parts of the hard disk.
While installing HAP and related software, certain DLLs and other software components which reside in the
Windows\SYSTEM32 folder (or equivalent) must be installed. Typically, you must be logged in to the workstation
as the “Administrator” user in order to have the proper read/write access to update these system files. The HAP
installer requires that you be logged in as “Administrator” to ensure that all software components can be
successfully installed.
If this error message is encountered, we recommend the following workaround procedure:
1. When the error message appears, press the OK button to exit from the message box.
2. Use the Start / Shutdown / Shutdown Computer option to restart the computer. As it reboots, log in as the
Administrator user.
3. Install the software again.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 79 of 218

Installation Aborted: Internal Error
Date: Oct. 6, 2008
Summary: When starting the CD installation (using the Start/Run option and entering d:\SETUP.EXE), the blue
background for the installation screen appears, immediately followed by the error:
Installation Aborted
Internal Error
The installation procedure halts at this point.
Discussion: This error is typically due to one of five problems with the computer:
1. DOS Environment Variable TMP Pointing to Non-Existent Folder. DOS environment variable settings are
still used, even on Windows computers. One of these is the TMP variable. You can examine environment
settings by displaying a DOS prompt and entering the command SET. For example, the most common
assignment for the TMP variable is TMP=C:\WINDOWS\TEMP If the designated folder does not exist, it will
cause the Internal Error message in the install software we are using. If this is the problem, the solution is to
modify the DOS Environment settings to specify a valid folder. For example, if you want to specify C:\TEMP
as the temporary folder, the command would be SET TMP=C:\TEMP Then rerun the installation.
2. DOS Environment Variable TMP Pointing to an Inaccessible Folder. The DOS environment variable TMP
points to a folder to which the user does not have proper read, write, create, destroy rights. To investigate
this, display a DOS prompt and enter the command SET. Write down the folder assigned to the TMP variable
in the environment settings. Then determine whether the user has full access rights to the folder. If the user
doesn’t, either obtain the necessary access rights to the designated folder or assign TMP to a different folder
to which you have full access rights.
3. DOS Environment Variables TMP and/or TEMP Missing. To determine whether the TMP and TEMP
environment variables have been set, display a DOS prompt and enter the command SET. Scan the settings
which are displayed. If there is no TMP=… or TEMP=… variable displayed, this could be the cause of the
problem. These settings must be added to the DOS environment.
First use Windows Explorer to verify that a C:\WINDOWS\TEMP folder exists. Then use NotePad to add the
following commands to the AUTOEXEC.BAT file:
SET TMP=C:\WINDOWS\TEMP
SET TEMP=C:\WINDOWS\TEMP
Save AUTOEXEC.BAT and reboot the computer. Then try installing the HAP software.
4. Bad or Missing VER.DLL File. This cause is unlikely, but if you eliminate causes #1 and #2 above, use the
Start/Find option to search for VER.DLL on the hard disk. If no VER.DLL file is found, you know this is the
culprit and the file needs to be obtained. Currently we do not have information on how or where to obtain a
copy of VER.DLL to replace a missing or bad file. Please contact Syracuse for further assistance.
5. Bad or Missing DDEML.DLL File. This cause is also unlikely, but if you eliminate causes #1 and #2 above,
use the Start/Find option to search for DDEML.DLL on the hard disk. If no DDEML.DLL file is found, you know
this is the culprit and the file needs to be obtained. Currently we do not have information on how or where to
obtain a copy of DDEML.DLL to replace a missing or bad file. Please contact Syracuse for further assistance.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 80 of 218

"Out of Disk Space" Error While Installing
Date: Oct. 6, 2008
Revised: January 6, 2015
Summary: While installing HAP the installation halts, and the following error message appears:
Out of Disk Space.
Workaround: Diagnostic procedures differ depending on whether the user is installing on the local hard disk or is
installing on a network server drive.
If installing on a local hard disk:
1. Use Windows Explorer to check the amount of free disk space. If the amount of disk space is small (less than
25MB) it is likely that more free disk space is needed. Note that it is very difficult to determine the true amount
of free disk space because Windows caches memory to the hard disk. Therefore, free disk space is very
volatile. The more free space available, the less likely this “out of disk space” problem is. Some computer
specialists suggest that a bare minimum of 100 MB should be kept free to ensure smooth operation.
If installing on a network server:
1. Use Windows Explorer to check the amount of free disk space on the local hard disk for the workstation
computer.
2. Use Windows Explorer to check the amount of free disk space on the network server drive.
3. Determine how much of the user’s allocation of network drive space is remaining.
For example, there may be 2 GB of disk space free on the server, but a user may only have 1 MB out of his
50MB allocation on the server remaining. It is the remaining portion of the user’s allocation on the server that
is important - and can lead to “out of disk space errors”.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 81 of 218

"SSNVC100.EXE Handle is Invalid" Error
Date: Oct. 6, 2008
Summary: A user begins installing the HAP software. During installation of Windows Configuration Services, the
installation halts and displays the following error message:
H:\E20-II\SSNVC100.EXE
Handle is Invalid
After clearing this error message, a second message appears:
Could not execute SSNVC100
Workaround: This error has occurred once. The computer was running McAfee Virus Scanner software. When
the McAfee software was disabled, the problem disappeared.
It should only be necessary to disable McAfee temporarily since the SSNVC100 program is only used while
installing or uninstalling Carrier software. It is not used while running HAP.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 82 of 218

Installer Appears to Hang After copying COMDLG32.OCX
Date: December 26, 2001
Revised: Oct. 6, 2008
Summary: A user begins installing HAP. Message windows indicate that various tasks are being performed such
as copying files. Installation proceeds to a point where the message window says "Copying COMDLG32.OCX".
This message window is visible for a long period of time (possibly 30 seconds or longer). Because the installation
does not seem to be proceeding, the user believes the installation has halted and the computer is locked up. The
user reboots the computer at this point.
Discussion: One portion of the installation procedure involves copying files from the CD to the computer. The
last file copied in this sequence is COMDLG32.OCX. When this file has been copied the next portion of
installation involves "registering" files with the Windows operating system. On certain computers registering files
can take a long time. Because the installation software does not display a special message while it is registering
files, the "Copying COMDLG32.OCX" message remains on the screen. If it takes a long time to register files,
users get the mistaken impression that the installation has halted.
Solution: When the "Copying COMDLG32.OCX" message appears, wait for the installation to run and finish
registering files. While it may appear the computer is locked up, it has not. The installation will run through if given
enough time.
On most computers, registering files takes 20 seconds or less. However we have encountered a few computers
where registration took as long as 5 minutes and one where it took 17 minutes. The length of time required to
register files depends on the size and complexity of the Windows registry file. As the registry file becomes larger
and more complex, it takes longer to register file information. While it is very unusual for registration to take 5 to
15 minutes, this behavior has been observed in a handful of cases.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 83 of 218

"Apex True DBGrid" Error While Installing
Date: October 21, 2001
Revised: June 12, 2017
Applies to: HAP 4. (Not HAP 5.0 or later)

Summary: While installing HAP, the following error message appears:

This version of Apex True DBGrid Data Bound Grid requires GRDKRN32.DLL version 1.10.090 or higher.
After pressing the OK button to clear the error message, program installation continues and a message will
appear stating the program was successfully installed.
However, if you run HAP and try to edit weather data, the same error message will appear and will prevent you
from editing weather data.

Discussion: "Apex True DBGrid" and GRDKRN32.DLL are two of many 3rd party software components used in
the HAP program. The error message appears because the computer already includes a different version of the
GRDKRN32.DLL file (v5.0 or later) which is incompatible with version HAP requires.
The problem is that Component One Inc. (formerly Apex Software) and Microsoft have released two different and
incompatible versions of the GRDKRN32.DLL file. Normally when changes are made to a DLL file so that it is no
longer compatible with prior versions of software, its name is changed so it will not cause other software programs
to fail. For some reason Component One and Microsoft neglected to do this. However, GRDKRN32.DLL happens
to be a particular type of DLL file that permits multiple copies to exist on a single computer. Therefore, by putting
the copy of GRDKRN32.DLL required by HAP in the \HAPxx\CODE folder along with an accompanying file we
can resolve the problem with HAP while at the same time avoiding any problems with the other software
programs on the computer that use the later, incompatible version of GRDKRN32.DLL.

Workaround:
1. Shut down any other programs that are running.
2. Save the GRDKRN32.ZIP file provided by Carrier to the \E20-II\HAP4x\CODE folder. For example, if you
installed HAP v4.60 on C: drive, you would save GRDKRN32.ZIP to the C:\E20-II\HAP46\CODE folder.
3. Use WinZip (or equivalent) to unzip the file. This will produce one file named GRDKRN32.DLL.
4. Now navigate to the C:\WINDOWS\SYSTEM32 folder or equivalent.
5. Copy the TDGB32.OCX file from \WINDOWS\SYSTEM (or equivalent) to the \E20-II\HAP46\CODE folder.
6. Next, from the Windows desktop press the Start button and choose the Run option.
7. In the Run dialog enter the following command:
c:\windows\system32\regsvr32.exe c:\e20-ii\HAP46\code\tdbg32.ocx
If your version of Windows uses a different folder for Windows system files (such as WINNT\SYSTEM32),
substitute those folder names in the command.
After pressing OK a message should appear saying the file TDGB32.OCX was successfully registered. If a
different message appears at this point, stop here and contact Software Systems for assistance.
8. Run the File Integrity Verification Report for HAP v4.x (via Start, Run, Carrier E-CAT and E20-II Programs,
Diagnostics). When the report is displayed find the TDGB32.OCX item. Its status should be "OK". If instead
this item in the report lists "Different" or an error message, stop here and contact Software Systems for
assistance.
9. Finally, run HAP and try to edit weather data. If the Weather Form appears without any errors, the problem
has been solved.
Note: If the error reappears in the future it is due to the fact that another program is open on your computer that
is using the later version of GRDKRN32.DLL. While you can install two different versions of GRDKRN32.DLL on a
single computer, both cannot be running in the computer's memory at the same time. In order to run HAP
successfully, the other program that uses GRDKRN32.DLL must be shut down. Since it is difficult to tell which

HAP Support Notes rev. 501_05 -- Page 84 of 218

programs might be using GRDKRN32.DLL, you should shut down other programs one by one until the problem
with HAP is resolved.
Note to Support Staff: The GRDKRN32.ZIP file referred to above is provided in an e-mail template.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 85 of 218

"This Patch Can Only be Used to Update Existing Installations" Error
Date: October 2, 2002
Revised: Oct. 6, 2008
Summary: The patch installation will not run on computers which do not have the proper version installed. An
incompatibility between the patch file and the currently installed version of HAP is the most common installation
problem for patch updates. When an incompatibility exists, the installation will halt with the following error
message:
This patch can only be used to update existing installations of HAP <versions listed here>. Neither version can
be found on drive <install drive listed here>, so the patch installation cannot be run.
Discussion: For customers in the US and Canada minor updates to HAP are offered as patch install files that
can be downloaded from the www.commercial.carrier.com web site. Patch files install only those software
components that were changed in the update. As a result, the patch can only be installed on computers which
already contain the specific version(s) of HAP that the patch was designed to update.
Workaround: To troubleshoot these problems:
1. Verify that HAP is installed on the target drive listed in the error message. If it is not installed, that may be the
problem. For example the user has HAP installed on D: drive, but specified C: drive when installing the patch.
If so, the solution is to rerun the patch installation and specify D: as the install drive.
2. If HAP is installed on the target drive, determine its version. Do this by starting the program and noting the
program name and version number displayed on the title screen. It is important to differentiate between HAP
and HAP System Design Load.
3. Determine whether the patch file being run is compatible with the edition of HAP installed on the target drive.
The following table defines these compatibilities. If the files on the user's computer are incompatible, this table
can be used to determine which patch file should be used instead. Note that problems most commonly occur
when a customer is trying to patch HAP with the System Design Load patch or System Design Load with the
HAP patch.
Patch Will Replace
<no patches issued yet>

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 86 of 218

"Dynamic Link Library WININET.DLL Could Not Be Found" Error
Date: November 6, 2003
Revised: Oct. 6, 2008
Summary: While installing HAP, the installation program halts and displays the following error message one or
more times in succession:
The dynamic link library WININET.DLL could not be found in the specified path c:\temp; c:\winnt\system32;
c:\winnt\system; c:\winnt...
After pressing OK to clear the error messages, the installation proceeds and appears to finish successfully.
Discussion: This error occurs on computers using the Windows NT operating system when certain key Windows
files are missing. Typically the key files will be missing if Microsoft Internet Explorer v4.0 or later has not been
installed on the computer. While the installation appears to finish successfully, certain software components
required by HAP have not been properly installed because of the error. You will be unable to generate reports if
the problem is not corrected.
Workaround: To correct this problem use the following procedure:
1. Make sure the computer is using Windows NT service pack 4 or later. If not, upgrade Windows to the latest
NT service pack.
2. Make sure the computer has Microsoft Internet Explorer v4.0 or later installed. If not, install it.
3. Reinstall HAP.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 87 of 218

Unable to see Network Drives
Date: October 6, 2010
Revised: July 1, 2016
Summary: A user is attempting to install HAP to a network drive (or possibly locate a project on a network drive).
When the drive selection window appears, the drive selection drop down list does not list the desired network
drives. Often no network drives are listed at all.
Discussion: This error appears to have multiple possible causes, ranging from Windows security settings to
antivirus software blocking software operation. The causes and solutions we've identified so far are listed in the
workarounds below. A particular customer could have any one of these and so should try each until a solution is
found. Note that there may be other causes we have not yet identified, so it is possible a customer could try all the
workarounds and not find a solution.
Workaround: Multiple customers have reported success with the following procedure which is documented in the
following Microsoft article: http://technet.microsoft.com/en-us/library/ee844140 and reproduced in this attachment:

Some Programs
Cannot Access Network Locations When UAC Is Enabled.pdf

This article describes a scenario where a user has mapped a network drive as a normal non-administrative user,
but because of Windows User Access Control (UAC), is running the HAP installer with administrator privileges,
this difference causes the problem.
The solution Microsoft recommends is to modify the Windows registry as follows.
(NOTE: Use caution. Editing the registry incorrectly has the possibility of causing serious operating
problems on your computer.)
1. Edit the Windows Registry
2. Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > Current Version >
Policies > System
3. Create a new DWORD entry with the name EnableLinkedConnections and value equal to 1
4. Restart your computer
5. Run the HAP installer and specify a network drive as the destination drive.
(Bug 22968)

Alternative Procedures: If the workaround above is unsuccessful, the following procedures may be tried as well.

Alternative Workaround 1 - Windows Firewall

This solution involves temporarily turning off Windows Firewall, then installing to the network drive, then turning
Windows Firewall back on. Note that temporarily turning Windows Firewall off leaves your computer vulnerable for
a short period of time. This should only be done by someone proficient with Windows concepts and operation.
1. Temporarily turn Windows Firewall off.
2. Install the Carrier software to the desired network drive.
3. Reactivate Windows Firewall.
The customer who reported this solution noted that once steps 1, 2, 3 are done it is subsequently possible to
install to the network drive with Windows Firewall on.
This customer also reported he also changed the Windows security setting for encryption from 128-bit encryption
to a lower level of encryption prior to turning the firewall off. It is not clear whether this encryption change is
required for this firewall workaround to be successful.

HAP Support Notes rev. 501_05 -- Page 88 of 218

Alternative Workaround 2 – Anti-Virus, Anti-SpyWare, Anti-MalWare Software
Multiple customers have reported that anti-virus, anti-spyware or anti-malware software running on their computer
was blocking access to network drives. The general solution approach was as follows:
1. Temporarily turn the program off or change its security settings to a lower level.
2. Start HAP. Enter data. Save the project to the desired folder on a network drive. Exit HAP.
3. If you are successful doing this it means the anti-virus, anti-spyware or anti-malware program is causing the
problem.
4. Turn the anti-virus, anti-malware or anti-spyware software back on, or restore it to original settings since you
don't want it to be permanently off or at reduced settings. Then study the software to see if there is a
permanent adjustment to settings that will allow HAP to access network drives. For example, sometimes a
software program like HAP can be put on a "white list" and the software subsequently allows HAP to access
network drives because you've designated HAP as a program which can safely be permitted to do this.
Customers have so far reported success with this approach for the following security programs. Given this
experience it is possible other software packages not on the list could also cause this problem.
 Symantec Endpoint
 Comcast Constant Guard
 ESET Smart Security

Alternative Workaround 3 - Manually Mapping Drive via CMD.EXE

A customer tried Workarounds 1 and 2 and neither was successful in resolving the problem. Later he found that
manually remapping the drive via CMD.EXE and the NET USE command solved the problem. Apparently due to
the Windows security settings on his computer network, this approach was necessary to avoid the problem.
This may have been related to the issue discussed in this Microsoft article:
http://support.microsoft.com/kb/937624 and reproduced in the attachment:

Programs may be
unable to access some network locations after you turn on User Account C

The success of this procedure is probably tightly related to the specific configuration of the desktop computer and
the computer network. As a result, it may not work on some computer systems.
Steps in this workaround:
1. From the Windows desktop press Start
2. In the "Search programs and files" field at the bottom of the Start Menu enter CMD
3. The Programs window will appear listing one item titled CMD. Right-click this item.
4. In the pop-up menu that appears choose the "Run as Administrator" option.
5. The "User Account Control" window will appear. It contains a message "Do you want to allow the following
program to make changes to this computer?" Click the Yes button at the bottom of the window. Note that you
must be the Administrator to do this. You can log in as Administrator from this window if necessary.
6. In the Command Prompt window enter a NET USE command to map the desired network drive. For example
net use \\<computername>\<sharename>
7. Still in the Command Prompt window, switch to the drive containing the program CD or the installer files and
execute the SETUP.EXE installer file. This time the installation procedure should display the drive mapped in
#6 as one of the destination drive options.

Alternative Workaround 4 – Map Drive Letter as a Filesystem Link

HAP Support Notes rev. 501_05 -- Page 89 of 218

This approach may work but is not yet as well tested as the primary workaround (EnableLinkedConnections).
Rather than relying on Windows network drive mapping, it instead creates a filesystem “link” to the network
location, which then functions in much the same way.
Steps:
1. Create a new folder on PC where HAP is installed, for instance c:/Shares
2. Create symbolic links to network folder(s) using the command prompt:
mklink /d "c:\Shares\HAP Files1" “\\server\HAP Files1”
mklink /d "c:\Shares\HAP Files2" "\\server\HAP Files2"
mklink /d "c:\Shares\HAP Files3" “\\server\HAP Files3”

If this does not work with an error such as “The symbolic link cannot be followed because its type is
disabled”, you may need to enable this type of filesystem link first:
 Enable this with your local or group policy
o Computer\System\Filesystem\Selectively allow the evaluation of a symbolic link --> allow local to
remote
 Alternately, you can enable local to remote links by running this in a command prompt as an administrator
/ elevated permissions:
o fsutil behavior set SymlinkEvaluation L2R:1

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 90 of 218

 “Fatal Error 3633 loading data: Can’t load DLL: MSJTER35.DLL”
Date: July 19, 2013
Revised: July 19, 2013
Summary: This error occurs when running the HAP installer. It occurs while the installer is running the program
“xycfgfix”. After clicking “OK” to the error, the installation may superficially appear to complete; however HAP does
not run successfully.
Discussion: This error occurs because there is a problem with the installation of Microsoft Data Access
Components (MDAC) on the user’s PC. These components are system components, not Carrier software, and
are normally present and functional on any modern Windows PC. When this error occurs it indicates that the
installation of these components has somehow become corrupt. However, there are instructions the user can
follow which may correct their installation.
Notes: This error has been reported for XBuilder as well; see XBuilder Support Notes item 10 for additional
workarounds. The workaround below has been used for issues in the HAP installation.
Workaround:

A. Locate the file mdac.inf located in C:\WINDOWS\inf

B. Right mouse click on the mdac.inf file and click Install
C. When prompted for files, browse to the C:\WINDOWS\ServicePackFiles\i386
or the
C:\i386
directory path.

D. When prompted for the 'handler.reg' file, either point to the C:\WINDOWS\i386 or load the file from the
i386 directory on the Windows XP install CDROM.
E. The Windows XP Service Pack 2 (or later) MDAC should now be reinstalled.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 91 of 218

Cannot Find HAP in Windows 8 Start Menu / Screen
Date: September 30, 2014
Revised: N/A
Summary: Windows 8 has a different style of start menu than prior versions. In some cases it can either be
confusing where to locate Carrier programs such as HAP, or HAP is actually not listed in the menu.
Discussion:
 It is unknown why HAP (or any other program) would no longer be listed in the start menu. It is possible
that a user has “un-pinned” it (see below). Windows 8 has a more fluid idea of what is listed in the Start
Menu than prior versions. This allows programs to be added/removed easily from the menu, separate
from whether or not they are installed.
 It has been verified that a fresh install of HAP will appear in the Windows 8 start menu.
 Understanding of Windows 8 is evolving; there may be other / similar cases to this which require different
solutions.
Workaround:
The user may have a Start screen which looks like this:

HAP itself is not listed (though in this example some of our other programs are). The user should do the following:

HAP Support Notes rev. 501_05 -- Page 92 of 218

1. On the same screen above, search for HAP by just starting to type “hourly” – this should produce a result
similar to the following:

2. Right-click on “Hourly Analysis Program v4.80” which will bring up a menu of choices at the bottom of the
screen. Click the “pin to start” option:

HAP Support Notes rev. 501_05 -- Page 93 of 218

3. When the user next visits the start screen, HAP should appear:

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 94 of 218

Error: This Package Has Expired and Cannot Run
Date: Sept. 9, 2015
Summary: A user tries to install HAP, but while the installer is running receives the following error:

[This package has expired and cannot run]

Discussion: This is known only to happen within Carrier / UTC when using the edition of the installer specifically
designed to run on CSC PCs (known as the “sales office” edition). That edition contains special features to allow it
to be installed on CSC PCs without running into a security violation.

Workaround: There are three potential scenarios that could lead to this error:
1. The user may have an out of date installer. Although SSN always updates our installers to the latest CSC
requirements, someone could have an older version archived, or on their PC already, etc. They should
download it fresh from HVACPartners to ensure they have the latest installer (and delete any others).
2. The installer file might be corrupt. The user should delete it, download a new copy (from HVACPartners) and
try again.
3. Something in the way CSC manages PC security could have changed. This is unlikely, as it has only occurred
one or two times (ever). However in those cases, it may have changed with little or no warning.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 95 of 218

Cannot find EDDUVHS.EXE During Installation (Webroot Antivirus)
Date: Jan. 13, 2016
Summary: A user tries to install HAP, but while the installer is running receives the following error:

[…Cannot find ‘EDDUVHS.exe’…]

Discussion: This occurs because the antivirus software on the user’s PC deletes the EDDUVHS file before the
installer is done using it. Only the Webroot SecureAnywhere antivirus has been known to do this.
Note: A support ticket is open with Webroot to hopefully eliminate this problem eventually.

Workaround: The most appropriate recourse is for the user to disable Webroot, perform the installation, and then
re-enable Webroot.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 96 of 218

Signature is Corrupt or Invalid while Downloading
Date: April 26, 2016
Summary: A user tries to download HAP, but receives the following error from their web browser:

[the signature of filename is corrupt or invalid]

Other variations of this basic error message may also occur.
This prevents the download from working.

Discussion: Our EXEs contain information known as a “certificate” which identifies Carrier (or UTC) as the
publisher of the software. However, the format of that information is out of date and therefore some browsers do
not accept it.
This error does NOT indicate that there is a virus, or that there is something materially wrong with the file being
downloaded.

Workaround: There are two approaches two solve this issue:

1. Try an alternative web browser. The browsers from Microsoft (Internet Explorer or Edge) seem most
prone to this problem. Firefox or Chrome may avoid the issue.
2. Provide an alternative download link to the customer. These will install the identical version of HAP but do
not contain the certificate information mentioned above:
 Full install:
TBD

 HAP v4.91 Demo / Trial:

http://dms.hvacpartners.com/docs/1004/public/01/e20-hap491d-u.aspx

 Block Load 4.16 demo/trial:

http://dms.hvacpartners.com/docs/1004/public/04/E20-BLK416D-U.aspx

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 97 of 218

3.3 Common Errors – Program Startup
Carrier Programs Group Does Not Appear on Start Menu
Date: February 19, 1999
Revised: Oct. 6, 2008
Summary: A user successfully installs HAP on a computer using Windows 98. When the user tries to run HAP,
he or she finds that there is no “Carrier E-CAT and E20 Programs” group on the Start/Programs menu.
Discussion: The content of the Start/Programs menu is normally based on the tree structure of the
\WINDOWS\START MENU\PROGRAMS folder. However, certain configurations of Windows can place the
\START MENU\PROGRAMS folder in a different location. The HAP installation is designed to determine which
\START MENU\PROGRAMS folder on the computer is the valid one when multiple copies exist. However, it
appears the installer software is unable to identify the correct \START MENU\PROGRAMS folder in certain cases
on Windows 98 computers.
Workaround: Because the installation writes a complete set of information for the Carrier E-CAT and E20
Programs group to the \WINDOWS\START MENU\PROGRAMS folder, the workaround simply requires
identifying the correct location of the PROGRAMS folder and then moving the information that was installed.
Please use the procedure below
1. Run Windows Explorer.
2. In Explorer, choose the Find option on the Tools Menu. Then choose the “Find Files or Folders” option. In the
Find dialog:
 For “Named” enter START MENU
 For “Look In” make sure the root directory of C: is specified (assuming C: is the boot drive).
 Make sure the “Include subfolders” item is checked.
Then press the Find Now button.
3. All instances of files or folders containing the word “Start” will be reported. Sort through this list and find all
items which are folders whose name is includes “Start Menu”. One will be
C:\WINDOWS\START MENU\PROGRAMS. There should be at least one other folder item which contains the
phrase \START MENU\PROGRAMS. Write down the full path for each of these Start Menu folder items. Then
exit from the Find dialog.
4. Back in Windows Explorer, navigate to each of the \START MENU\PROGRAMS folders reported by your
Find. Identify which of these items contains all of the program groups and items that normally appear on your
Start/Programs menu.
For example, \WINDOWS\START MENU\PROGRAMS will contain at least a “Carrier E-CAT and E20
Programs” group, but may not contain anything else. One of the other instances of the
\START MENU\PROGRAMS folders will contain the full set of groups and items that you see when you press
the Start button and choose the Programs option. This will be the correct location of all Start/Programs
information on your computer.
5. Move the “Carrier E-CAT and E20 Programs” folder and all its subfolders from
\WINDOWS\START MENU\PROGRAMS to the other \START MENU\PROGRAMS folder which contains your
normal Start/Programs items. Drag and drop is typically the easiest way to move the folder and its sub-folders
in one step.
6. Exit Windows Explorer. On the Desktop, press Start and choose Programs. You should now see a Carrier E-
CAT and E20 Programs group on your Programs Menu. Within this group will be an item used to start HAP
v4.3 as well as a diagnostics item.
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 98 of 218

Can't Start Program. No HAP Icon Exists
Date: February 9, 1999
Revised: January 6, 2015
Summary: After installing software, a user tries to run HAP. There is a “Carrier E-CAT and E20-II Programs”
group on the Start/Programs menu, but it only contains a “Diagnostics” subgroup. There is no “Hourly Analysis
Program…” program item. Thus, the program can’t be started.
Discussion: The lack of an "Hourly Analysis Program" item in the "Carrier E-Cat and E20-II Programs" group
indicates the installation process terminated before it was completed. HAP was either not installed or was only
partially installed.
Troubleshooting Procedure:
1. If the installation was explicitly terminated before it was complete, reinstall both Configuration Services and
HAP using the downloaded installer EXE file.
2. If error messages appeared during installation, take screenshots of all error messages and contact Carrier
Software Systems technical support for assistance.
3. If no error messages appeared, send the following two files to Carrier Software Systems technical support at
[email protected] along with a complete description of the problem:
<Drive>\E20-II\HAPxx\INSTALL.LOG where xx is the HAP version.e.g., HAP50
<Drive>\E20-II\CSI21\INSTALL.LOG

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 99 of 218

This Program is not Registered with Configuration Services
Date: February 19, 1999
Revised: January 6, 2015
Summary: HAP has been installed on a network server. The program runs successfully for a number of weeks or
months. Suddenly at some point the program cannot be started from any network terminal. The program fails to
start and displays either of the following two error messages:
This program is not registered with Configuration Services. Please contact Software Systems for assistance.
or
Missing application or project related data for HAPxx. Please contact Software Systems for assistance.
This problem occurs when the HAP software on the network server is uninstalled from one of the workstations.
Each workstation has uninstall items for HAP and Configuration Services. So any workstation user can uninstall
HAP from the server, provided the user has read/write access to the \E20-II folder on the server (which they
usually do). Sometimes this happens when a user wants to uninstall the software from a particular workstation
and doesn’t realize the uninstall option deletes the software BOTH on the local workstation and the central server.
Workaround: To correct this problem, use the following procedure.
1. Choose one workstation (any workstation will do if you do not know which workstation HAP was originally
uninstalled from).
2. Copy the HAP installation (setup) EXE to the computer.
3. Run the setup program.
This will replace the software that was deleted from the network server. Make sure you specify the same
server drive originally used to install the program when asked for an install drive.
5. At this point all workstations should be able to run HAP again.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 100 of 218

"Missing Application or Project Related data" Error
See This Program is not Registered with Configuration Services.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 101 of 218

Unable to Run File Integrity Checkers
Date: March 25, 1999
Revised: January 6, 2015
Summary: Software is successfully installed and HAP can be successfully run. However, when the user attempts
to run either of the File Integrity Verification programs, the File Integrity program window appears and displays the
window title bar, the print button and column headings for the grid, but the grid is empty. No file integrity
information is provided.
Diagnostic Procedure:
1. Use Windows Explorer to locate the following files:
 d:\e20-ii\enviro\chkcrc32.exe where “d” is the install drive.
 d:\e20-ii\enviro\ssncrc32.dll
 d:\e20-ii\enviro\csi21.crc
 d:\e20-ii\hap4n\code\hap4n.crc where ‘n’ is the HAP version; e.g. ‘8’ for HAP v4.80
If all four files exist, please create a ZIP containing all four files, attach the ZIP to an e-mail and send it to
Carrier Software Systems technical support along with a full description of the problem. Send the e-mail to
[email protected].

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 102 of 218

Error 429 While Starting Program
Date: May 5, 1999
Revised: January 6, 2015
Summary: HAP software is successfully installed. When the user tries to run HAP for the first time the following
error occurs:
HAPxx
Run time error 429:
Active X component can’t create object.
This error occurs before the program title screen appears. Therefore, only the Windows desktop is visible behind
the error message window.
Workaround: This error typically indicates a problem with one of the Windows DLL files HAP relies upon. We
have found that this error message can be caused by a variety of different DLL problems. Therefore a user should
first try reinstalling HAP. If that does not solve the problem, the following diagnostic procedure should be run to
collect information to help determine how to solve the problem.
Diagnostic Procedure:
1. Generate the File Integrity Verification report for HAP: From the Windows desktop press Start, choose
Programs, choose Carrier E-CAT and E20-II Programs, choose Diagnostics and finally choose “Report for
Hourly Analysis Program vx.x”.
2. A diagnostic report will appear on your screen. When the display is complete press the “Save to File” button in
the upper left. A message will appear telling you the name and location of the file that is created. Please make
a note of the name and location.
3. Create an e-mail to be sent to Carrier Software Systems Technical support at
[email protected]. This e-mail must contain the following information:
a. Customer name, company name, phone number.
b. Version of Windows being used on the computer.
c. Is the computer connected to a network. If so, what is the network operating system?
d. Did the Error 429 occur the first time the program was run, or was the program running properly for a
period of time before the error appeared.
In addition, attach the following files to the e-mail:
a. The file integrity report you saved to file in step 2 above.
b. The HAP install log file - \E20-II\HAPxx\INSTALL.LOG
c. The Configuration Services install log file - \E20-II\CSI21\INSTALL.LOG

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 103 of 218

"Initialization Has Failed" Error Upon Startup
Date: May 7, 1999
Revised: Oct. 6, 2008
Summary: The HAP software installed successfully ran properly for several months, but one day stopped working
in the following manner:
 A user clicks on the HAP start menu item or icon.
 The HAP title screen appears with the “initializing” status message in the lower left.
 Startup halts with the following error message:
HAPxx
Initialization has failed. Program cannot be started. Contact Software Systems for assistance.
This is the only error message that appears.
Discussion: Before HAP can start a series of checks are run to make sure the HAP and its software
infrastructure are intact and ready for operation. This is called “initialization”. There are many reasons why
initialization can fail. For the vast majority of them the “initialization has failed” message will be preceded by one
or more error messages explaining the specific reason for the failure. In a small minority of cases, only the
“initialization has failed” message appears. The diagnostics and workaround provided below ONLY apply to the
situation in which “initialization has failed” is the only message that appears.
Diagnostic Procedure: First, perform the following diagnostics to determine whether the workaround is
appropriate for the user’s specific conditions. If conditions are not appropriate for the workaround, then the
information gathered below will be useful when consulting with Syracuse to determine an alternate course of
action.
1. Verify the conditions leading to the error.
a. Verify that the title screen appeared before the error and displayed the “initializing” message.
b. Verify that no windows or error messages appeared prior to the “Initialization has failed” error message.
2. Gather the following basic information about the computer environment:
a. What operating system is being used on the desktop computer?
b. Is the computer connected to a network? If so, what is the network operating system (with version).
c. Has HAP been installed to the network server or to the local workstation? Specify drive letter for the
install drive. Was HAP installed for “standalone” or “network” mode?
d. Did the “Initialization has failed” error occur the first time HAP was run, or had HAP run successfully for a
period of days or weeks before the error appeared?
e. If HAP ran properly for a period of time before the error appeared, when was the last time HAP ran
properly? Has any new software or hardware been installed or upgraded in the interval between the last
time HAP ran properly and the appearance of the error message?
3. Supplemental questions for network installations only.
a. How many workstations are running HAP from the server?
b. Do all workstations experience the “Initialization has failed” error in exactly the same way?
c. If only some workstations have the “Initialization has failed” error, are there any common characteristics for
the workstations failing versus those that are not failing?
d. For at least one user and workstation experiencing the problem, verify that the user has read, write, create
and destroy file privileges for the E20-II, E20-II\ENVIRO and E20-II\HAPxx\CODE folders on the server.
Workaround: If the results of the diagnostic work are as follows, then use the workaround to resolve the problem.
Otherwise, consult with Syracuse to determine an alternate course of action.
1. The HAP title screen appears before the error and displays the “initializing” message.
2. The “Initialization has failed” message is the only error message that appears.
3. If installed to a network server, then all users running HAP experience the same problem.

HAP Support Notes rev. 501_05 -- Page 104 of 218

Under these conditions it is likely either the \E20-II\E20XYCFG.MDB or the \E20-II\ENVIRO\PRJXY000.MDB
database files have been damaged and can no longer be used. If so, the workaround is to restore the damaged
file.
1. First, send copies of the database files to Syracuse via e-mail for inspection
([email protected]). When the software has been installed on a desktop computer or on a
server for “network – all data shared”, send two files:
d:\E20-II\E20XYCFG.MDB
d:\E20-II\ENVIRO\PRJXY000.MDB
where “d” is the install drive. When software has been installed on a network server for “network – all data
private” mode there will be multiple copies of prjxy*.mdb and all must be sent:
d:\E20-II\E20XYCFG.MDB
d:\E20-II\ENVIRO\PRJXY*.MDB
Syracuse will examine the files to determine if one or more are damaged, missing data or contain bad data.
2. If a damaged file is found we may be able to repair it and send it back. If so, simply replace the damaged file
with the repaired copy and you’ll be back in business.
3. If a damaged file is found and can’t be repaired, the quickest solution is to recover a copy of the file from the
most recent hard disk or network server backup and replace the damaged file with the recovered copy.
4. If a damaged file is found, it can’t be repaired, and no backups exist, we may be able to reconstruct it if the
user can provide sufficient information to allow reconstruction. Consult with Syracuse for details.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 105 of 218

"Can't Open Database Created with Previous Version" Error
Date: February 10, 2000
Revised: Oct. 6, 2008
Summary: When trying to start HAP, startup fails and the following error message appears:
GetE20ConfigData()
Can’t open a database created with a previous version of your application.
Workaround: Try reinstalling Configuration Services and HAP. In the few cases of this error we have
encountered reinstalling solved the problem.
If reinstalling fails, perform the standard diagnostic tests below to gather data and then send the data to Syracuse
for review.
Standard Diagnostic Procedure:
1. Identify the version of Windows running on the computer.
2. Determine whether the software has been installed on a server or the local workstation drive.
3. Run the File Integrity Verification report for HAP and save the report to a disk file.
4. Gather the following files and e-mail to Syracuse for review along with a description of the problem. E-mails
should be sent to [email protected].
Files to Attach:
The file integrity report saved as a disk file in step 3 above.
\e20-ii\e20xycfg.mdb
\e20-ii\csi21\install.log
\e20-ii\hapxx\install.log

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 106 of 218

"Jet VBA File Failed to Initialize When Called" Error
Date: February 1, 2001
Revised: July 12, 2016
Summary: While starting HAP the following error message appears:
The Jet VBA file (VBAJET.DLL for 16 bit versions or VBAJET32.DLL for 32-bit versions) failed to initialize
when called. Try reinstalling the application that returned the error.
It is also possible this error will appear while installing HAP.
Workaround Procedure: This error is the result of problems with one or more Microsoft DLL files on the user's
computer. Please use the following steps to diagnose and resolve the problem:
1. Generate the File Integrity Verification Report for HAP. To generate these reports:
 From the Windows desktop, press Start, choose Programs, choose Carrier E-CAT and E20-II Programs
and then choose the Diagnostics item in this group.
 In the Diagnostics group, select “Report for Hourly Analysis Program v4.x”. When the report appears
press the Save to File button. Make a note of the name and location of the saved file.
When the report is still displayed, check the VBAJET32.DLL item.
 If its status is listed as "OK", continue to step #2 below.
 If its status not “OK”, compare the Version Found and Version Shipped items. If Version Found is higher
than Version Shipped, then go to step #2 below. If the versions are the same or the Version Found is
earlier than the Version Shipped then try reinstalling HAP to see if this solves the problem.
2. The next step is to send the File Integrity Verification Report from step #1 to Syracuse for evaluation. E-mail
the file along with a description of the problem to [email protected].
3. There may be more than one cause for this error:
 VBAJET32.dll may be missing
 EXPSRV.dll may be missing or not properly registered (this is a dependency of DB access components)
see https://support.microsoft.com/en-us/kb/196057 for details.
 The customer may need to manually search their PC for these files and provide details.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 107 of 218

Microsoft Installer Launches When Starting HAP
Date: July 26, 2002
Revised: April 27, 2017
NOTE TO SSN SUPPORT: Please see new diagnostic procedure located below. Would like to try this for a while
to see if it helps to pinpoint the root cause of this issue.
Summary: A user starts HAP. During the start-up sequence the installer program for another program such as
AutoCAD executes and begins installing that program. Or in the middle of running HAP the installer program for
another program like AutoCAD may launch. This is a known issue which has been documented by Microsoft and
AutoDesk.
This problem has been observed if you have any of the following installed on your computer, and one of these
programs is damaged:
 AutoCAD
 Architectural Desktop
 Roxio Easy CD Creator
 Microsoft Office
 Sage 300
This problem might also involve other programs.
Explanation: Microsoft has a product called “Microsoft Installer” (MSI). MSI provides installation services for
other programs as well as “auto-repair” features which allow MSI to detect when a program is damaged and then
automatically repair that damage. Many software vendors use MSI to install and auto-repair their software.
However, MSI is prone to activating its auto-repair feature at the wrong time.
Example: AutoCAD is a program which uses MSI. When HAP is started or is running, MSI may activate and try to
repair AutoCAD if MSI detects AutoCAD is damaged. This happens even though there is no apparent association
between HAP and AutoCAD, or between HAP and MSI.

<see next page>

HAP Support Notes rev. 501_05 -- Page 108 of 218

Workaround (AutoCAD): AutoCAD has a repair tool you can run manually. One customer reported:
“I actually was able to fix the problem knowing MSI was detecting errors in the AutoCAD files. AutoCAD
has a repair tool … I simply ran the 5 minute repair from the control panel and then HAP opens perfectly.”

Furthermore, we received the following specific guidance from AutoDesk on Aug 26, 2016 regarding their
products:

Workaround (General): The short term solution to the problem is to press the cancel button on the MSI message
windows which ask you to insert a program installation CD. You may have to press the Cancel button several
times as MSI can be persistent about trying to auto install the program.
The long term solution in some cases is to run a complete reinstall of the damaged program. For example, if MSI
is trying to reinstall Microsoft Office, then Office should be reinstalled. Once damage to the other program is
eliminated, MSI will stop trying to auto install it when you start or run HAP.
This type of problem has the potential to recur until Microsoft and/or other vendors involved provide updates to fix
this problem.
If possible, perform steps in the next section to collect additional information specific to the problem.
General Diagnosis: Collecting additional information may help us to solve the problem:
1. Look in the Application section of the computer's event log. To locate this:
a. Click Start Menu
b. Type ‘event’ in the search field and wait for the Start menu to search.
c. Click the “Event Viewer” item.

HAP Support Notes rev. 501_05 -- Page 109 of 218

 2. The events we are interested in are displayed with source "MsiInstaller". They will also have a
date/time which should correspond to when the problem occurred.

Example:

3. If there are any events like that, send a screenshot of the information for that event, which will look
something like this:

Further Information:
 https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Windows-
Installer-displayed-unexpectedly.html
 https://knowledge.autodesk.com/support/autocad-map-
3d/troubleshooting/caas/sfdcarticles/sfdcarticles/2010-Unexpected-installer-launches.html
 http://www.installsite.org/pages/en/msifaq/a/1037.htm
General Diagnosis (2):

HAP Support Notes rev. 501_05 -- Page 110 of 218

This procedure will turn on advanced Windows logging in order to capture details of the problem.
Steps:
1. Start menu > click “Run…”
2. Type regedit and click OK

3. Registry Editor will start

4. Using the tree on the left, navigate to
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer (see screenshot)

HAP Support Notes rev. 501_05 -- Page 111 of 218

5. Once the Installer entry is highlighted, see if there is a “Logging” entry in the right
a. If so, record the current value, which may be something like “eo”
b. Then choose Edit menu > “Modify…”

6. If NOT, create a “Logging” entry using Edit menu > New String Value

and

7. Set the value of the “Logging” entry to be: voicewarmupx and click OK.

8. Leave the registry editor running, but you can minimize it out of the way

9. Do whatever causes the errant installer (for AutoCAD, Office, etc.) to run
a. If possible, let the installer run to completion once it starts
10. Now we will look for log files created
11. Start menu > Run…
12. Type %temp% and press enter
13. A folder window should open
14. Look for any files named like MSIxxxx.LOG where xxxx will refer to a program being installed
15. ZIP up all these files and send them to Carrier for evaluation
16. Back in Registry Editor, double click the Logging entry again
17. Change its value back to “eo” or whatever it was originally. This will turn logging off.

HAP Support Notes rev. 501_05 -- Page 112 of 218

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 113 of 218

HAP Main Window not Visible on Startup
Date: July 28, 1999
Revised: July 19, 2013
Summary: This problem manifests itself in two ways:
1. A user starts HAP. The program title screen appears, but the program does not appear behind the title
screen. When the user presses the OK button on the title screen, the HAP main program window still does
not appear. However, a HAP icon appears on Windows taskbar.
=OR=
2. A user starts HAP. The program starts successfully in full screen mode (HAP occupies full screen). When the
user clicks the "Restore Down" button in the upper right to go to "windowed mode" the program disappears
from the screen. A HAP icon appears on Windows taskbar. Clicking on the taskbar restores HAP to full
screen. But it is not possible to display HAP on the screen in windowed mode.
Discussion: This problem is due to the main program window being positioned far off the view area for the
monitor.
When HAP is run in windowed mode, the software records settings for the HAP window - its height and width, and
the coordinates that define its position of the left-hand and top edges of the window on the display monitor.
In one instance we discovered the coordinate for the left hand edge of the HAP main window was stored as -
36000 meaning it was far off the visible portion of the display monitor. We speculate this erroneous setting may
have been stored if the computer crashed while running HAP, or the user turned off the computer while still
running HAP.
In another instance, HAP was installed on a computer network and one of the network users was running with
dual monitors. Shifting HAP to the second of the dual monitors on one workstation made it impossible to display
HAP in windowed mode on other workstations using a single-monitor setup.

Workaround 1: See Dealing with Windows that are Located Off-Screen.

Workaround 2: If the first workaround is unsuccessful, the problem can be solved by editing the configuration
database which stores user settings.
The following steps are required:
1. ZIP the \E20-II\ENVIRO\PRJXY000.MDB file.
2. Attach the ZIP to an e-mail to [email protected]
3. Carrier will revise the contents of the file to specify a window position that is visible on the display monitor and
then send the modified file back.
4. The modified file can be unzipped and placed back in the \E20-II\ENVIRO folder.
5. Finally, run HAP.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 114 of 218

Error 429 in frmMain CheckFileStatus While Starting HAP
Date: October 13, 2009
Revised: November 30, 2009

Problem Has Been Resolved

See information in Workaround Section below.
Summary: While starting HAP the program halts and displays the following error.
Number: 429
Description: Active X component can't create object.
Module: frmMain
Method: CheckFileStatus
This error prevents the program from starting.
Discussion. If a file integrity report is generated, the status column for item 37 (BASEX32.DLL) and item 38
(BASEX232.DLL) will contain messages like "the specified module cannot be found". Beginning in late summer
2009 we have been receiving reports that anti-malware software (possibly only the software MalwareBytes) is
identifying these two HAP files as being infected with a Trojan Downloader virus. We have retested the two files
and verified that they are not infected. When this happens, the anti-virus or anti-malware software will quarantine
or remove the files. In either case that prevents HAP from using the files during startup and leads to the Error 429.
Workaround. During October 2009 Carrier worked with MalwareBytes.Org and confirmed that the MalwareBytes
software was generating a false positive - falsely identifying BASEX32.DLL and BASEX232.DLL as files infected
with viruses. MalwareBytes.Org subsequently updated their software so it will no longer identify these two files as
malware. If you are experiencing this problem on your computer, you can use the following steps to resolve it:
1. Start MalwareBytes.
2. From the main screen click the Update tab.
3. On the Update tab click the "Check for Updates" button.
4. When the update confirmation message appears, verify that it says you have been updated to a database
version 3070 or higher. If so, the problem is resolved.
Note: If BASEX32.DLL or BASEX232.DLL had been quarantined or erased by MalwareBytes, you will need to
reinstall HAP v4.51 in order to restore these two files.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 115 of 218

Error 429 in frmMain CheckFileStatus
Date: October 17, 2011

Summary: During startup the program halts and displays the following error message:
Number: 429
Description: Active X component can't create object.
Module: frmMain
Method: CheckFileStatus
As a result of this error the program fails to start.
Discussion. This error usually indicates the BASEX232.DLL file used by HAP is missing or damaged, or there is
a problem with launching Configuration Services.
Workaround. The recommended workaround procedure is as follows:
1. Reinstall X Builder Framework first and then reinstall HAP. Reinstalling these two programs will install clean,
reliable copies of BASEX232.DLL and Configuration Services and this usually will correct the problem.
2. Start HAP to verify the program successfully starts.
3. If HAP fails to start, generate a file diagnostic report and send to Carrier Software Support:
a. From the Windows desktop press Start and choose Programs > Carrier E-CAT and E20-II Programs >
Diagnostics > Report for Hourly Analysis Program v4.x
b. After the report finishes displaying on the screen click the "Save As File" button in the upper left. A
message will appear indicating the path and name for the TXT file that was created. Make a note of this
information.
c. Attach the TXT file that was created in "b" to an e-mail and submit to Carrier Software Support.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 116 of 218

Error 3 While Creating New Project
Date: April 2, 2012
Summary: When starting HAP for the first time on a new computer, HAP will automatically create a new, untitled
project. In rare cases creation of the project fails and the following error is displayed.
Error 3. Cannot find path. Error creating application file(s) in project work area. Project Data Server
initialization complete. However, there was an error creating a new project.
As a result of this error the program fails to start.
Discussion. New untitled projects are created in a subfolder beneath the Windows "Temporary" folder. Most
Windows computers have a Temporary folder configured on the hard disk that Windows and other programs such
as HAP will use for temporary data storage. If no Temporary folder has been configured on a computer, HAP will
not be able to create a new project on its first startup and this error will occur.
Workaround. To determine whether a Temporary folder has been configured, and to correct the problem if one
has not been configured, please use the following steps:
1. From the Windows desktop, right-click the "My Computer" icon. Select the Properties item in the pop-up menu
that appears.
2. In the Properties window click the Advanced tab.
3. On the Advanced tab click the Environment Variables button which appears toward the bottom of the tab.
4. In the Environment Variables window that appears next examine the "User Variables" section which is in the
upper half of the window.
a. If the list of User variables does not include a variable named TEMP, then
 Click the New button found just below the User Variables table.
 In the New User Variable window that appears specify the Variable Name as TEMP and for Variable
Value specify a valid drive and folder path on the computer to which your user login ID has full access
rights. Then press OK.
b. On the other hand, if the list of User Variables already has a variable named TEMP, verify the drive and
path listed for this variable is valid and that your user login ID has full access rights to it. If a TEMP folder
has been specified for Windows but does not exist or has restricted access, this Error 3 problem can still
occur. If the path is not valid or you don't have access to it, use the Edit button to change the path to a
folder that exists and to which you have full access.
c. Next check the list of User variables to see if it includes a variable named TMP. If it does not:
 Click the New button found just below the User Variables table.
 In the New User Variable window that appears specify the Variable Name as TMP and for Variable
Value specify a valid drive and folder path on the computer to which your user login ID has full access
rights. Then press OK.
d. On the other hand, if the list of User Variables already has a variable named TMP, verify the drive and
path listed for this variable is valid and that your user login ID has full access rights to it. If a TMP folder
has been specified for Windows but does not exist or has restricted access, this Error 3 problem can still
occur. If the path is not valid or you don't have access to it, use the Edit button to change the path to a
folder that exists and to which you have full access.
5. After making any needed changes, click OK to close the Environment Variables window.
6. Then click OK on the System Properties window to close that window.
7. You will then return to the Windows Desktop. Start HAP and verify the problem has been resolved.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 117 of 218

The Field is too Small to Accept the Amount of Data… Error
Date: June 12, 2013

Summary: After installing HAP, a user starts HAP for the first time. During startup, the program halts and displays
the following message:
SaveProjectProperties()
The field is too small to accept the amount of data you attempted to add. Try inserting or posting less
data.
Due to this error the program cannot be started.
Discussion. This error has been reported twice. Both were customers located in Mexico, both were using
Windows 8 computers and running with Spanish regional settings. The error occurs because the computer uses a
peculiar format for the date. On all previous versions of Windows the internally stored date requires no more than
24 characters to display. There is a database file used in all Carrier projects (eDesign and E-CAT) that stores the
date and limits this information to 24 characters. In these two instances the odd formatting of the date required
more than 24 characters so the date could not be stored, hence the error. To date we have not seen this problem
on Windows 8 computers elsewhere in the world so this may be a very isolated problem.
Workaround. There are two workarounds:
1. Install X Builder Framework v1.05j or a newer version. As of June 12, 2013 v1.05j had not yet been released.
Release date will either be June 28 or July 26.
2. Contact Software Systems / Syracuse. We can provide a file to insert into the \E20-II\ENVIRO folder which
will fix the problem.

Note:
a. This error can occur in any Carrier eDesign or E-CAT program. It is not limited to HAP.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 118 of 218

Run-Time Error 372 During Startup
Date: June 29, 2013
Revised: October 31, 2013
Corrected In: HAP v4.80

Problem Has Been Resolved

Please Install HAP v4.80 or later to eliminate problem.

Summary: After installing HAP, a user starts HAP for the first time. During startup, the program halts and displays
the following message:
HAP47
Run-time error 372
Failed to load control 'RichTextBox' from RICHTX32.OCX. Your version of RICHTX32.OCX may be
outdated. Make sure you are using the version of the control that was provided with your application.
Due to this error the program cannot be started.
Discussion. This error has been seen on Windows 7 and later computers. RICHTX32.OCX is a Microsoft file that
was a standard Windows component present on Windows XP computers, but apparently is not always present on
Windows 7 or newer. We do not install this component, so if it not already present on the computer, you will get
this error. Most customers do not encounter this problem. Only a subset of users are affected.
This Microsoft software component is only used in one place in HAP – on the "What's New" window that appears
at startup. If this window is turned off, the problem can be avoided. Therefore the workaround described below
involves sending a file to Syracuse in which we'll switch off the display of the "What's New" window.
Workaround.
1. Place the \E20-II\ENVIRO\PRJXY000.MDB file in a password-protected ZIP file.
2. Attach the ZIP file to an e-mail and send to [email protected] Be sure to include the
password for the ZIP in the e-mail.
3. Carrier software support will modify the MDB file to switch off the display of the What's New window and then
send the MDB back in a new ZIP file.
4. When you receive the modified file, unzip the file and place the modified PRJXY000.MDB file in your \E20-
II\ENVIRO folder. It will overwrite the original file.
5. Start HAP. The program should start without errors this time.
Note that the password-protected ZIP above is required for the file to pass through Carrier's e-mail security filters.
Some customers have had success with a simpler approach: Renaming PRJXY000.MDB to PRJXY000.ABC and
attaching the renamed file to an e-mail. In that case the procedure is as follows:
1. Rename the \E20-II\ENVIRO\PRJXY000.MDB file to PRJXY000.ABC
2. Attach this PRJXY000.ABC file to an e-mail and send to [email protected]
3. Carrier software support will modify the file to switch off the display of the What's New window and then send
the file back to you.
4. When you receive the modified file, place it in the \E20-II\ENVIRO folder. It will overwrite the original file.
Rename the file to PRJXY000.MDB
5. Start HAP. The program should start without errors this time.

Note:
a. This error could affect HAP v4.7, v4.6 and v4.5. Those are the only versions containing a What's New window
that uses the Microsoft RICHTX32.OCX software component.

HAP Support Notes rev. 501_05 -- Page 119 of 218

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 120 of 218

About Windows User Account Control (UAC) Warnings
Date: January 31, 2014
Revised: February 26, 2014
Summary: When starting HAP (and most other eDesign programs) the user is requested to confirm that they
want the program to “make changes to this computer” with a screen such as the following:

If the user clicks “Yes” HAP will start normally. If they click “No” HAP will not start.

Discussion: User Account Control (UAC) was introduced in Windows Vista and is also part of later versions. A
UAC prompt can appear if a program does one of a long list of “nonstandard” operations on the computer. Since
eDesign software predates Windows Vista, HAP and other programs do in fact fall into this category. However,
this does not indicate that they are performing incorrectly or in a harmful way. It does mean that they have not
been modified in all respects to conform to more recent Windows standards.

In some cases, users have received a more stringent UAC prompt requiring an administrator to login, such as one
of the following:

HAP Support Notes rev. 501_05 -- Page 121 of 218

If this is what a user reports, they should be asked to provide a screenshot and a careful accounting of the steps
they took to generate the login request, because this is an unusual circumstance. If they really are getting an
administrator login request, that is due to the settings on their PC, not specifically because of any attribute of HAP
or any other eDesign software. There is nothing SSN can do to change this, although their IT personnel may be
able to.

HAP Support Notes rev. 501_05 -- Page 122 of 218

Windows User Account Control has several levels of strictness. Most computers seem to require HAP users to
confirm that they want to run the software, but not actually provide credentials to do so. But Windows can be
set to operate with that stricter setting.
To check this (From Windows 7):
View / edit security policies by running the Windows program SECPOL.MSC (type that at Start / Run and
press [ENTER]).
Navigate to the correct settings area (Local Policies / Security Options / User Account Control …) as shown:

View the “Behavior of the elevation prompt for administrators” setting:

HAP Support Notes rev. 501_05 -- Page 123 of 218

Effects of this setting:
Setting UAC Behavior
“Prompt for credentials” Password required
“Prompt for consent” UAC prompt shown, but no password will be needed
“Elevate without prompting” There should be no UAC prompt at all

Workaround: There is no workaround that would cause HAP to behave in a UAC-compliant manner. However, it
is possible to disable UAC entirely for the user’s PC, via the Control Panel. However this is not recommended
since UAC does serve a good purpose. Such a change would normally require administrative permissions on the
PC. Simply clicking “Yes” should be all that is necessary in most cases.

Notes: While it may be possible to modify HAP to behave in a UAC-compliant way, this work has not been
performed since it seems likely to entail substantial changes to the program.
(Bug 22969)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 124 of 218

Automation Error – The Network Name Cannot Be Found
Date: February 10, 2014
Revised: n/a
Summary: When attempting to open HAP, the user receives the following error:

[Error -2147024829 automation error the network name cannot be found]

After the error, HAP does not start.

Discussion:
In the case where this was observed, it was because HAP and/or X-Builder had been installed to a network server
which was replaced by a new computer having a different network name.
Both the old and new server were mapped to the same local drive letter (Q:) so that superficially all file locations
looked the same both before and after the server change. However this was insufficient for Windows to load the
programs correctly.

Workaround:
Reinstall X-Builder and/or HAP to the network location which refers to the current, active, functioning file server
(e.g., the Q: drive in this example).

Notes:
For instance:
The server once was \\STORAGE\MECHDATA\
But is now called \\MEPC-DATA01\MECHDATA\

However, Windows itself recorded the actual old server name in the registry associated with several X-Builder
components used by HAP.

For example, after the server move one component location was still set to:
\\STORAGE\MECHDATA\E20-II\XBF11\CODE\XBREQUESTHELPER.DLL

HAP Support Notes rev. 501_05 -- Page 125 of 218

But the “STORAGE” server no longer existed. This detail was revealed by a standard diagnostics report.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 126 of 218

Error on Starting HAP - Missing File SSNSystemDefault17.RO
Date: December 24, 2014
Revised: N/A
Summary: The user starts HAP v4.90 and receives the following error message:

Error: The following application file is missing.

[C:\E20-II\HAP49\CODE\SSNSystemDefault17.RO]

This normally seems to occur for a customer who has done a new install of HAP, though other scenarios are
possible.

Discussion: The “missing” file is not actually used by HAP v4.90, which indicates that the installation itself was
incorrect.
HAP actually uses a file called SSNSystemDefault18.RO, but relies on a database installed by X-Builder
Framework to determine which files constitute a HAP project. The database lists the wrong filename, which
indicates that the XBF installation is incorrect and/or that the XBF installer had an error when running.
This has occurred to 3-4 customers in the month of December, 2014; a root cause is not yet known.

Workaround: Reinstalling the latest XBF seems to resolve the problem.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 127 of 218

GetE20ConfigData – ActiveX Component Can’t Create Object
Date: January 8, 2015
Revised: N/A
Summary: A user starts HAP or any eDesign program. During startup the following error message appears:
E20GetConfigData()
ActiveX component can’t create object.
After pressing OK a second error message appears:
HAP49
Initialization failed.
Program cannot be started. Please contact Software Systems
After pressing OK, the program terminates.

Discussion: The “ActiveX component” error means that one or more software components HAP relies on for
startup is missing, damaged or not registered with the operating system. Because HAP requires many Carrier-
created and third-party components for operation, there could be any number of different specific causes for this
error. The first steps in diagnosing this problem with customers should be the following:
1. Confirm the errors occur during startup of the program.
2. Ask for screen images showing any error messages which appear.
3. Ask for a file diagnostic report for the program. This can show is if particular software components are
missing, damaged or not registered.
These steps should be completed first. Based on the findings, Carrier may recommend further steps below.
The location of this error (Procedure Name = E20GetConfigData) means it is likely the error involves Microsoft
components involved with reading and writing database files. Therefore a next step is typically:
4. Unregister and reregister the Microsoft file DAO350.DLL. Ideally this should be done by someone proficient
with computer operating systems such as the company IT person, if available.. DAO350.DLL could exist in
one of a number of different places on the computer depending on the operating system version. So the task
is to locate the file, unregister it and then reregister it. Finally start HAP to determine if the error is eliminated.
If this does not eliminate the problem the next step is to search for the Microsoft file msrdo20.DLL. We recently
found an instance of this error due to the fact this Microsoft file, which is usually installed with the operating
system, was missing from the computer. This part of the diagnosis involves the following steps.
5. Running Windows Explorer as Administrator, run a file search on the computer C: drive for msrdo20.dll.
6. If no copies of this file are found, Carrier will supply a copy of the file along with instructions. This file will to
be placed in the correct folder (depending on operating system version) and then registered. As before this
should ideally be done by someone proficient with operating system principles such as the computer IT
person, if available.
7. Finally start HAP to determine if the problem is eliminated.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 128 of 218

3.4 Common Errors – Program Operation
General Protection Fault When Editing Data
Date: February 24, 1999
Revised: Oct. 6, 2008
Summary: HAP installs and runs OK. From the main program window the user attempts to edit any of the
categories of data by clicking on an item in the list view (right-hand) panel. When the user does this the following
error occurs:
General Protection Fault
Discussion: This error has been encountered only on computers running McAfee CrashGuard software. If
CrashGuard is temporarily turned off, the problem disappears. Therefore the error appears to be a conflict
between CrashGuard and HAP.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 129 of 218

Error Opening Weather Data
Date: February 26, 1999
Revised: October 31, 2013
Summary: From the HAP main program window a user double clicks on the “weather properties” item in the right-
hand panel to display the weather form. The following error message appears:
Error opening weather data.
After pressing the OK button to clear this error message, another message appears:
There was a problem loading weather data.
Workaround: This problem has been observed when running HAP on a computer network using Windows NT
Server. HAP has been installed on the server computer and is run from workstations connected to the server.
The problem is due to access rights assigned to the database file containing design weather data for HAP. This
file resides in the \E20-II\HAPxx\CODE folder and is named HAPxxWTH.MDB. Read, write, create and destroy
file privileges must be assigned to this CODE folder for all users of HAP. Otherwise the weather database file
cannot be accessed and these errors will occur.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 130 of 218

"Runtime Error 50003. Unexpected Error."
Date: April 14, 1999
Revised: Oct. 6, 2008
Summary: This error occurs in two situations. First when you choose to create a new default schedule, the
following error message appears:
Profile
Run time error 50003. Unexpected error.
Second, when you choose to create a new default system, the following error message appears:
HAPChkBx
Run time error 50003. Unexpected error.
We have found the error is sometimes due to a mismatched set of OLEAUT32.DLL and OLEPRO32.DLL
Windows files.
Diagnostic Procedure: Use the following procedure to diagnose the problem:
1. Identify the version of Windows being used.
2. Run the File Integrity Verification report for HAP and print the file integrity report.
3. Check the integrity data for the OLEAUT32.DLL and OLEPRO32.DLL items.
4. If the status for both files is OK, then the workaround procedure listed below does not apply. In this case
contact Software Systems technical support for assistance.
5. If the status both files are is other than OK, then the workaround procedure listed below does not apply. In
this case contact Software Systems technical support for assistance.
6. If one file is marked OK and one file is not OK, we may be able to offer a workaround that will solve the
problem. Please contact Syracuse for further information. It involves replacing one of the OLE*.DLL files to
restore a matched set. We are not publishing the workaround at this point because (a) it has only been used
in one case, (b) versions of files that need to be replaced depend on the operating system, (c) there is the
potential for the workaround to cause problems operating other programs.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 131 of 218

"Error in Calculate: Subscript Out of Range" While Running System Design
Calcs
Date: February 10, 2000
Revised: Oct. 6, 2008
Summary: While running system design calculations, the following error message appears:
HAP47ASD
Error in Calculate: Subscript out of Range
This error halts the calculations and they cannot be completed.
Discussion: This error has only been reported once. Inspection of the user’s project data files found that the
design weather data file (HAP47WTD.DAT) had been destroyed. Because HAP could not acquire weather profiles
from the file, the subscript out of range error occurred.
While the one instance of this problem was due to a missing weather file, it could occur if other files in the project
folder had been destroyed. A “subscript out of range” error could also be due to other causes, but the missing file
issue should be ruled out first before examining other possible causes.
Workaround: To diagnose and work around this problem, please use the following steps:
1. When the error occurs, save and close the project you are currently working with.
2. Run Windows Explorer and display a list of files in the folder containing the project you were working with.
3. Make sure the folder contains at least the following core set of files. In addition to making sure the file name
appears, also check to make sure the file size is not 0 bytes. Either a missing file or a zero byte file size will
lead to the subscript out of range problem.
HAP47WTD.DAT
HAP47SPC.DAT
HAP47A00.DAT
HAP47P00.DAT
HAP47B00.DAT
HAP47SCH.DAT
HAP47WAL.DAT
HAP47ROF.DAT
HAP47WIN.DAT
HAP47DOR.DAT
HAP47SHD.DAT
HAP47CHL.DAT
HAP47TWR.DAT
HAP47BLR.DAT
HAP47ERT.DAT
HAP47FRT.DAT
HAP47PRF.DAT
HAP47INX.DAT
4. If the HAP47WTD.DAT file is missing or zero-length, it can be replaced by creating and saving a new project,
and then copying the HAP47WTD.DAT file from this new project folder into the original project folder. Then
run HAP, open the problem project and re-specify its weather data.
5. If files other than HAP47WTD.DAT are missing, it may or may not be possible to rehabilitate the data because
the rest of the files are interrelated. If one of the other files is missing, contact Carrier Software Systems for
assistance in determining whether the project data can be repaired.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 132 of 218

Main Window Items Out of Synch with Project Data
Date: February 22, 2000
Revised: Oct. 6, 2008
Summary: The right-hand panel of the main program window in HAP displays lists of items in each category of
data you’ve created for a project (e.g., spaces, walls, roofs, windows, etc…).
A user reported that when he double-clicked on an item in the main program window to edit its data, the data that
appeared had a different name and different characteristics than those listed on the main program window.
Example: The main program window shows a space named “Conference Room 204” with a floor area of 836 sqft.
If you double-click on this item to edit its data, the space data that appears has a name “Classroom 736” with a
floor area of 1200 sqft. The space data is out of synch with the item list shown on the main program window.
Discussion: This problem was the result of data files from two different projects being mixed in a single project
folder. The most likely way this would happen is by files being copied between project folders using Windows
Explorer.
A project consists of a number of DAT files containing the input data for each space, system, wall, roof, window,
etc… in the project plus a database file which serves as an index for the project. The index database contains the
names and reference information for all items in a project (spaces, systems, etc…) plus information about
linkages between items (e.g., walls linked to spaces, etc…).
If DAT files from one project folder are copied into another project folder, it creates a situation where the
information in the DAT files is out of synch with data in the index database. Once this happens the project data
becomes unusable and cannot be rehabilitated. While it is possible design calculations may run for this set of
data, calculation results will not be useful. Further, it is likely many strange error messages will appear while using
the project data.
Workaround: Never use Windows Explorer or DOS commands to copy files from one project folder into another.
If files from two project folders are combined, the project data will become unusable. There is no way to
rehabilitate project data when this happens.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 133 of 218

Zero Lighting & People Loads Shown on Air System Design Load Summary
Date: February 22, 2000
Revised: Oct. 6, 2008
Summary: A user runs system design calculations and generates the Air System Design Load Summary Report.
In the design cooling column of this report the lighting quantity and load appear as zeroes. The people quantity
and load also appear as zeroes. However, the user has specified lighting and people quantities and the schedules
for lighting and people have non-zero values for the hour shown on the Air System Design Load Summary.
Workaround: The most likely culprit is the “Diversity Factor”. Edit the air system data and go to the Zone
Components tab, Thermostat data view. If the diversity factor shown in this data view is 0%, that is the culprit.
Change this value to 100% to restore lighting and people loads.
Discussion: The diversity factor is used to specify a reduced quantity of lighting and people loads for the system
performance calculation. This is most often used for school applications where the people in the building move
from place to place. For these applications zone airflow rates are sized for each individual classroom based on
maximum lighting and occupancy. But, because the rooms in the building are not all simultaneously occupied at
maximum levels, the quantity of people and lights for each room are “diversified” when sizing the central cooling
coil.
A diversity factor of 75% means that 75% of the specified people and lighting heat gains are considered for the
system performance calculation which is used to size the central cooling coil.
A diversity factor of 100% means that 100% of the specified people and lighting heat gains are considered - i.e.,
no diversity is considered.
A diversity factor of 0% means that none of the specified people and lighting heat gains are considered. Users
often mistakenly specify 0% thinking this eliminates the diversity factor from consideration in the calculation. This
assumption is wrong.
(Bug 22971)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 134 of 218

Display Problems While Running HAP
Date: April 27, 2000
Revised: Oct. 6, 2008
Summary: A variety of problems can occur with the information shown on the computer display monitor while
running HAP. The problems encountered thus far have involved the “font size” specification in the Display
Properties dialog accessed via Windows Control Panel.
Two users have reported problems which are summarized below. A general diagnostic procedure is provided at
the end of this topic.
 Case #1 - User reports that the right-hand portions of input forms are not visible. For example, on the Space
form the last visible tab is “Floors”. The “Partitions” tab is not visible. On the “Internals” tab the last few
characters along the right-hand side of the form are chopped off.
It turned out the display monitor settings for the user’s computer were set to “Custom” font size. With Custom
font size, the user specifies size as a percentage of normal font size. The specified percentage was
178925687% which is clearly a corrupt value. When we re-specified custom font size as 125% the problem
disappeared.
 Case #2 - User reports that portions of text in input forms are chopped off or overwriting adjacent text. For
example, on the System Form, Zone Components tab, Space Assignments data view, the “Prev” and “Next”
buttons below the zone name are not visible because the zone name appears to overwrite the buttons. In the
“Remove” button the bottom of the letters “R”, “e”, “m” and “o” are visible along the top of the button, and the
letters “ve” appear along the left margin of the button. It appears that the word “Remove” was too large to fit in
the button, so the text wrapped to two lines
Inspection of the user’s display monitor settings did not indicate any problems. “Small Fonts” had been
specified as the font size. As an experiment, we changed this to “Large Fonts”. This solved the problem. It’s
possible that the problem might remain solved if the setting is returned to “Small Fonts” at this point because
the nature of the problem suggests that some aspect of the display settings were corrupted and the act of
changing font size reset and therefore eliminated this corruption.
General Diagnostic Procedure. Whenever unusual display problems such as those described above occur, use
the following procedure. This procedure serves to gather data about the display monitor and its settings. It also
attempts a simple workaround which is often successful.
1. Determine the current display monitor settings
 From the Windows desktop, press Start and choose Settings.
 On the Settings Menu choose Control Panel.
 In the Control Panel double click on the “Display” icon.
 In the Display Properties dialog, click on the Settings tab.
 Note the Color Palette, Desktop Area and Font Size items. Note any other items which appear (certain
monitors and drivers may display extra information).
2. Evaluate Font Size Setting. The typical choices in the Font Size list are “Small Fonts”, “Large Fonts” and
“Other”. In some situations the list may include “Custom” with a percentage listed. In other situations there is a
Custom button that can be pressed to display the current custom font size percentage, if Custom font size is
in use.
If Custom or Other font size options are used, the typical settings are 75%, 100%, 125%, 150% 175% and
200%. Anything else is suspicious, especially if it is a strange value like 178925687% or –31676%. If an
unusual size is found, try changing to 100% or 125% font size. Then press OK to save the change. Typically
you’ll have to reboot. Then run HAP and see if the problem persists.
If the Custom setting is OK, or if small or large font size is already in use, try changing to one of the other font
size settings. For example, change small fonts to large fonts. When you press OK to save the setting, you’ll
have to reboot. Then run HAP and see if the problem persists.
In either of these attempted workarounds, the user may not want to permanently use the new setting (such as
a change from small to large fonts). If so, try changing back to the original settings. It’s possible the act of
changing settings eliminates corrupted display monitor information so the original settings may work OK now.

HAP Support Notes rev. 501_05 -- Page 135 of 218

3. If changing the Font Size does not solve the problem, collect some further information about the display
monitor and then consult with Syracuse:
 From the Settings tab of the Display Properties dialog, report settings for the Color Palette, Desktop Size,
and Font Size. Specify % if Custom or Other is used. Also report any other items shown on the Settings
tab.
 Specify the type of monitor (make, model).
 Specify name of video adapter card (if available)
 Specify name of video driver (if available).

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 136 of 218

Error 429: ActiveX Component Can't Create Object
Date: June 21, 2002
Revised: Oct. 6, 2008
Summary: “Error 429: ActiveX Component Can’t Create Object” can occur in different situations each with a
different cause. The known instances of Error 429 are listed below. Click on the desired item to display complete
information about the error condition and its workaround.
Error 429 While Starting Program
Error 429 While Retrieving HAP v4.0 Data
Error 429 While Retrieving HAP v3.2 Data
Error 429 While Saving Weather Data
Error 429 While Loading Simulation Weather Data
Error 429 While Running System Design Calculations
If the Error 429 occurs in a situation other than those listed above, the use the following procedure to generate
diagnostic information and then contact Carrier Software Systems technical support for assistance:
1. Generate the File Integrity Verification report for HAP: From the Windows desktop press Start, choose
Programs, choose Carrier E-CAT and E20-II Programs, choose Diagnostics, and finally choose “Report for
Hourly Analysis Program”.
2. A diagnostic report will appear on your screen. When the display is complete press the “Save to File” button in
the upper left. A message will appear telling you the name and location of the file that is created. Please make
a note of the name and location.
3. Attach the diagnostic file to an e-mail and send it to [email protected]. The e-mail should
include your name, company name and phone number, as well as a description of the steps leading up to the
error message.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 137 of 218

Error 429 While Retrieving HAP v4.0 Data
Date: June 27, 2002
Revised: Oct. 31, 2013
Summary: While converting data from HAP v4.0, the program halts and displays the following error message:
HAP40241: TranslateSystems
Fatal error while translating system.
Error 429 – ActiveX component can’t create object.
When the OK button is pressed to close the window containing this message, as second error message appears:
HAP v4.0 to v4.3 Translation
Retrieval of HAP v4.0 data failed.
Workaround: Use the following steps to correct this problem.
1. Reinstall HAP
Explanation: This error occurred when a new version of HAP is installed and then HAP v4.0 is later uninstalled.
Uninstalling v4.0 removes certain software components that later versions need to operate.
Note that the error only occurs in certain situations where HAP v4.0 is uninstalled. The two most common
situations are where the new HAP and v4.0 were installed on different drives, and when HAP v4.0 had been
installed second. In most cases uninstalling HAP v4.0 does not cause problems.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 138 of 218

Error 429 While Retrieving HAP v3.2 Data
Date: June 27, 2002
Revised: October 31, 2013
Summary: While converting data from HAP v3.2, the program halts and displays the following error message:
HAP32240: Main
Fatal error in main translator procedure.
Error 429 – ActiveX component can’t create object.
When the OK button is pressed to close the window containing this message, as second error message appears:
HAP v3.2 to v4.3 Translation
Retrieval of HAP v3.2 data failed.
Workaround: Use the following steps to correct this problem.
1. Run Windows Explorer
2. Navigate to the \E20-II\HAPxx\CODE folder on the drive on which HAP is installed.
3 Double-click on the Patch_For_HAP40_Uninstall.EXE file found in this folder. This launches an installer
program which reinstalls several software components needed by HAP that were uninstalled during the HAP
v4.0 uninstall.
Explanation: This error occurs when a newer version of HAP is installed and then HAP v4.0 is later uninstalled.
Uninstalling v4.0 removes certain software components that later HAP versions need to operate.
Note that the error only occurs in certain situations where HAP v4.0 is uninstalled. The two most common
situations are where the new version of HAP and v4.0 were installed on different drives, and when HAP v4.0 had
been installed second. In most cases uninstalling HAP v4.0 does not cause problems.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 139 of 218

Error 429 While Saving Weather Data
Date: June 27, 2002
Revised: October 31, 2013
Summary: After entering weather data a user presses the OK button to save the data and return to the main
program window. The program halts and displays the following error message:
Error Details:
Number: 429
Description: ActiveX component can’t create object.
Error Source Details:
Library: SSNWeatherObj10
Module: CWeather
Method:CalcDesignTempsA
When the OK button is pressed to close this message, you will be returned to the weather form. You will not be
able to save the weather data due to this error.
It is also possible the following error message can appear in the same situation, with the same causes:
Error Details:
Number: -2147220999
Description: Automation Error
Error Source Details:
Library: SSNWeatherObj10
Module: CWeather
Method:CalcDesignTempsA
Workaround: This error is typically due to uninstalling HAP v4.0. All 4.x versions of HAP use the PSYCH32.DLL
file for psychrometric calculations. When HAP v4.0 is uninstalled, in certain situations it will uninstall
PSYCH32.DLL. Therefore later versions 6 can no longer use the file and this leads to the Error 429. To correct
this problem:
1. Reinstall the newer version of HAP

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 140 of 218

Error 429 While Loading Simulation Weather Data
Date: June 27, 2002
Revised: October 31, 2013
Summary: While entering weather data a user goes to the Simulation tab and uses the “Select City” to select a
simulation weather file. After choosing a city, the program begins to add data for the city to the project but halts
with the following error message:
Error Details:
Number: 429
Description: ActiveX component can’t create object.
Error Source Details:
Library: SSNWeatherObj10
Module: CWeather
Method: CalcSimWeather
When the OK button is pressed to close this message, you will be returned to the weather form. The simulation
weather data has not been added to the project.
It is also possible the following error message can appear in the same situation, with the same causes:
Error Details:
Number: -2147220999
Description: Automation Error
Error Source Details:
Library: SSNWeatherObj10
Module: CWeather
Method: CalcSimWeather
Workaround: This error is typically due to uninstalling HAP v4.0. All 4.x versions of HAP use the PSYCH32.DLL
file for psychrometric calculations. When HAP v4.0 is uninstalled, in certain situations it will uninstall
PSYCH32.DLL. Therefore later versions 6 can no longer use the file and this leads to the Error 429. To correct
this problem:
1. Reinstall the newer version of HAP

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 141 of 218

Error 429 While Running System Design Calculations
Date: June 27, 2002
Revised: October 31, 2013
Summary: While running system design calculations, the program halts and displays the following error
message:
Error Details:
Number: 429
Description: ActiveX component can’t create object in AirSysDesign SimController
Error Source Details:
Library: HAP46SCM
Module: CSimControl
Method: Run()
When the OK button is pressed to close this message, you will be returned to the main program window.
Calculations were not completed.
It is also possible the following error message can appear in the same situation, with the same causes:
Error Details:
Number: -2147220999
Description: Automation Error
Error Source Details:
Library: HAP46SCM
Module: CSimControl
Method: Run()
Workaround: This error is typically due to uninstalling HAP v4.0. All 4.x versions of HAP use the PSYCH32.DLL
file for psychrometric calculations. When HAP v4.0 is uninstalled, in certain situations it will uninstall
PSYCH32.DLL. Therefore later versions 6 can no longer use the file and this leads to the Error 429. To correct
this problem:
1. Reinstall the newer version of HAP

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 142 of 218

"TerSave: Could Not Open the File" Error When Viewing Reports
Date: August 2, 2002
Revised: Oct. 6, 2008
Summary: While running HAP a user requests display or printing of reports. Before the reports are displayed or
printed the following error appears:
TerSave
Could not open the file.
The error can also occur when saving a report as a disk file. In this case the error occurs after the Save-to-File
option is selected.
This error only occurs for the specific situations described below:

When Viewing Reports: When Printing Reports When Saving a Report to a

Disk File
Weather Weather Spaces, Schedules
System (Input, Design, Sim) System (Input, Design, Sim) Walls, Roofs, Windows, Doors
Plant (Input, Design, Sim) Plant (Input, Design, Sim) Shades, Chillers, Clg Towers
Building (Input, Sim) Building (Input, Sim) Boilers, Electric Rates
Fuel Rates

Discussion: This error occurs when the project folder is located more than 11 levels deep in the folder tree
structure. One of the software components (TER32.DLL) cannot deal with file paths longer than 106 characters.
HAP minimizes this problem by using the short version of file paths, abbreviating each folder name with no more
than 8 characters. However, if a project folder lays more than 11 levels deep, the sum of folder names in the path
will exceed 106 characters and this error will occur.
Workaround: The project folder must not be located more than 11 folder levels deep in the folder tree structure.
(Bug 22972)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 143 of 218

"Error 6" During System Design Calculations
Date: August 2, 2002
Revised: Oct. 6, 2008
Summary: While running system design calculations for an air system the calculation halts and displays one of
the following error messages:
Error Details:
Number: 6
Description: Overflow in CSimEngine Calculate()
or
Error Details:
Number: 6
Description: Overflow in CDesignLoad fnCFMByRatio()
As a result calculations are not completed and system design results cannot be displayed.
Workaround: The “Error 6” can occur for a number of reasons. Three situations described below have been
identified thus far:
* The system is Single Zone CAV. It provides both cooling and heating. One or more spaces served by the
system never has cooling or heating load. This results in a zero peak sensible load for the space or the zone and
leads to the overflow error.
* The system is Single Zone CAV, cooling-only. One or more spaces served by the system never have a
cooling load. For example: the space does not have lights, electric equipment, people, walls, roofs, windows
or doors. This results in a zero peak sensible cooling load for the space or the zone and leads to the overflow
error.
* The system is Single Zone CAV, heating-only. One or more of the spaces served by the system never
has a heating load. For example, the space has no walls, roofs, windows, doors, infiltration, slab floor or
partitions. This results in a zero design heating load and leads to the overflow error.
* The system is one of the multiple-zone system types (VAV, Dual Duct, Fan Coil, etc...). One or more of
the zones in the system never has a cooling or heating load. This results in a zero peak sensible load for the
zone and leads to the overflow error.
To work around the problem first identify the spaces having no load. If the zero load condition is a mistake, then
add elements to the space to correct the problem. Spaces used in a system with both cooling and heating
capability must have either a cooling load or a heating load for at least one hour. Spaces used in a system with
cooling-only capability must have a cooling load for at least one hour. Spaces used in a heating-only system must
have at a heating load at the winter design condition.
If it is intentional that the space has no load, then user-defined sizing should be used. In this situation, the supply
airflow rate for the zone and possibly the system are dictated by air motion or ventilation requirements instead of
load conditions. Therefore airflow rates must be entered manually with user-defined sizing rather than using the
computer-generated sizing option. For computer-generated sizing, the program assumes airflows are based on
peak load conditions. Consequently spaces and zones must have loads for these calculations to run successfully.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 144 of 218

"Error 6 in cAirSysAnnual DXEquipCalcs"
Date: October 2, 2002
Revised: May 25, 2011
Corrected In: HAP v4.51

Problem Has Been Resolved

Please Install HAP v4.51 or later to eliminate problem.
Summary: While running an air system simulation the calculation halts and displays the following error message:
Error Details:
Number: 6
Description: Overflow in cAirSysAnnual DXEquipCalcs()
Discussion: There may be multiple causes for this error. Currently the only situation where this error has been
seen is where a problem with humidity levels occurs. Zones served by an air system contained very large
negative miscellaneous latent loads (i.e. a latent loss representing refrigeration cases in this case). During
summer months latent gains from occupants, infiltration and ventilation were larger than the latent loss so positive
humidity levels resulted. During winter months ventilation and infiltration components became losses (due to
lower outdoor humidity levels). As a result, in winter months latent losses exceeded latent gains resulting in
negative humidities in the zone. This is a physically impossible condition and results in the overflow error.
Workaround: The negative miscellaneous latent load must be adjusted so it will not cause negative humidity
levels in the winter. There are two ways to do this. One is to reduce the miscellaneous latent load input. This will
reduce the latent loss for all times of year. The second approach is to modify the schedule used for the latent loss
so latent losses are smaller during days in the cooler part of the year. Scheduling features are provided so
different schedule profiles can be used at different times of year.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 145 of 218

How to Interpret Program Error Messages
Date: September 4, 2002
Revised: Oct. 6, 2008
Summary: Sometimes during program operation, particularly while running design calculations or energy
simulations, an unexpected program error occurs. HAP notifies the user about the error using a message box that
has the following appearance. The information in this message box is primarily intended for use by Carrier
technical support to diagnose the problem. However, understanding how information is provided in this message
box may allow you to diagnose problems yourself to some extent. This topic explains how to read the information
in the message box.
HAP41
Number: 6
Details: Overflow in cSimEngine Calculate()
The information shown in the message box is as follows:
Error Details – This section describes what error occurred and the particular software component and software
procedure where the error occurred.
Number – The reference number for the error that occurred. Typically this is only useful to Carrier technical
support.
Description – Uses the format Error Description + Class Module Name + Procedure Name.
* The Error Description is a text description of the error condition.
* Class Module Name is the name of the software component in which the error occurred. Knowing
which program calculations are performed in which modules can help you pinpoint the part of a
calculation procedure where the error occurred, and this may give you a clue about what type of input
data to examine for conditions that caused the error. A partial list of class modules and their associated
calculations is provided below.
* Procedure Name lists the particular subroutine or function in which the error occurred.
Table 1. Partial X-Ref List of Class Modules and Calculations

Class Module Calculation

cAirSysAnnual Air system energy simulation
cBldSimController Building simulation
cBoilerUnit Plant simulation: boiler performance
cChillerPlant Plant simulation: chiller plants.
cChillerUnit Plant simulation: chiller performance
cCoolingTower Plant or System simulation: cooling tower performance
cDesignLoad Air system design calculation
cEnergyCost Building simulation: cost calculations.
cHwBoilerPlant Plant simulation: HW boiler plants.
cPltSimController Plant simulation.
cPump Plant simulation: pump performance.
cRemoteSource Plant simulation: remote source plants.
cSimEngine Both air system design and simulation
cStmBoilerPlant Plant simulation: steam boiler plants

Error Source Details – This section describes which software component and procedure was controlling
program operation when the error occurred. Usually this information is much less useful than the Error Details
section because it does not describe the exact location of the error. For all errors occurring during a design or
energy simulation calculation, it usually displays the same information, similar to that shown above.
Library – The name of the software component.

HAP Support Notes rev. 501_05 -- Page 146 of 218

 Module – The class module within the component.
Method – The subroutine or function which had control at the time the error occurred.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 147 of 218

Error 6 in cSimEngine Calculate
Date: December 4, 2002
Revised: Oct. 6, 2008
Summary: While running an air system simulation, the simulation halts and displays an error message that
includes the following information:
Error Details:
Number: 6
Description: Overflow in cSimEngine Calculate()
We have seen this error for only one set of very specialized conditions described below. It is possible for an
overflow error in this particular module to be due to other causes. The following is only one known possibility.
The simulation being run was a garage space in Fairbanks, Alaska. The space had no internal latent gains or
losses and no ventilation air. There was no cooling coil. A small amount of infiltration air was specified. Therefore,
the only latent heat flow for the system was due to infiltration. In mid-winter extremely cold, dry outdoor conditions
occur. For the given set of space and system conditions this weather resulted in indoor humidity conditions that
were physically impossible. This caused the psychrometric calculations to fail and resulted in the overflow error.
This particular problem was solved by adding 1 BTU/hr of miscellaneous latent heat gain in the space inputs.
Apparently this was enough to keep the psychrometric calculations from failing.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 148 of 218

"Failed to Load the Plant" Error When Editing Plants
Date: December 4, 2002
Revised: Oct. 6, 2008
Summary: A user opens a project and then double-clicks on a plant item to edit its data. The program halts and
displays the following error message.
frmPlant.Edit
Failed to load the plant.
After pressing OK to clear the message the program returns to the main window. The plant cannot be edited.
This error has been seen once and was due to a damaged copy of the E20XYCFG.MDB database file. This
database contains a list of data files which comprise a HAP project. Each time a project is opened, the list is used
to determine which files are copied from the project folder to the temporary working folder. Each time a project is
saved the file list is used to determine which files are copied back to the project folder for permanent storage.
If this file list information becomes damaged, then the set of files copied for a Project/Open or Project/Save will be
incomplete. In the one case where we have seen this error, several items in the file list in E20XYCFG.MDB had
been destroyed. As a result neither plant nor building data could be entered or edited, design and simulation
report selections were not saved, and system design calculation results were not saved. Therefore the “failed to
load the plant” error is only one of several possible error messages that could appear. Others are described below
When trying to edit or enter building data:
frmBuilding.Edit
Failed to load the building.
When trying to display system design results for a system that had been previously calculated:
HAP46
An error occurred while loading design data.
After this error the program hangs and must be shut down with Task Manager.
For the one case where this error was seen, we were not able to determine what caused the E20XYCFG.MDB file
to be damaged.
Workaround: Reinstall the program. This will re-establish a complete file list in E20XYCFG.MDB. Note that a full
install of the program must be run. Running a patch update alone will not restore the file list in E20XYCFG.MDB.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 149 of 218

Error 364 When Requesting Reports
Date: January 23, 2003
Revised: October 31, 2013
Summary: A user is working with a project and chooses the option to “Print/View” weather, system design,
system simulation, plant design, plant simulation or building simulation reports. Before the report selection dialog
appears the program halts and displays the following message:
Error Details
Number: 364
Description: Object was unloaded.

Error Source Details

Library: SSNHapReptObj11
Module: cReportOptions
Method: Show()

After pressing OK to clear the message the program returns to the main window. Reports cannot be generated.
Workaround: This error occurs because the HAPxxRPT.DAT (where x is the version number; eg ‘8’ for HAP
v4.80) file in the project folder is damaged and contains corrupt information. This DAT file contains your most
recent selections from the report selection dialogs. The solution to the problem is to replace this DAT file with a
new, clean copy of the file. This will cause you to revert to the original default report selections. But, since report
selections are not nearly as important as other project data such as spaces or systems, loss of this selection data
is not critical.
To replace the damaged file with a new, clean copy of the file:
1. Make sure HAP has been closed before working through this procedure.
2. Run Windows Explorer.
3. Navigate to the \E20-II\HAPxx\CODE folder on your computer, where “xx” is the HAP version such as “48” for
HAP 4.8.
4. Copy the SSNHapReptDefault11.RO file from \E20-II\HAPxx\CODE to the project folder containing the project
that generates the “Error 364”.
5. In this project folder, delete the existing copy of the HAPxxRPT.DAT file.
6. Then rename the SSNHapReptDefault11.RO file you copied into the folder in step 4 as HAPxxRPT.DAT.
7. Run HAP and verify that you can now generate weather, system design, system simulation, plant design,
plant simulation, or building simulation reports.
Note: The most common causes for damage to the DAT file are a computer crash or power outage while HAP is
running. If neither of these events occurred, then a different computer operating event is likely to be the culprit,
but it is usually very difficult to identify exactly what that event was.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 150 of 218

Error 6 in cSimEngine ZoneAnalysis
Date: January 23, 2003
Revised: Oct. 6, 2008
Summary: A user is generating system design reports for a VVT air system and the program is performing
calculations prior to showing the report. At the end of “Task 3 of 3: Coil Sizing” in the calculation the program halts
and displays the following error message:
Error Details
Number: 6
Description: Overflow in cSimEngine ZoneAnalysis()

Error Source Details

Library: HAP46SCM
Module: cSimControl
Method: Run()

After pressing OK to clear the message the program returns to the main window. The calculation is not completed
and system design results cannot be displayed.
Discussion: This error occurs when no cooling loads or heating loads ever occur in one or more of the zones
served by the VVT system. As a result the peak zone sensible load is 0 BTUh and the zone airflow rate is sized
for 0 CFM. This later results in the “overflow” error during system calculations.
Workaround: To resolve this error:
1. Evaluate the spaces served by the system and identify which spaces have no load elements.
2. Once spaces that do not have loads are identified, either revise the space inputs to correct the problem, or
remove these spaces from the system.
3. Then rerun the system design calculation for the VVT air system.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 151 of 218

Common Pitfall Involving Plants Linked to a Building
Date: January 23, 2003
Revised: Oct. 6, 2008
Summary: Due to a particular sequence of events that involves linking systems, plants and buildings, users may
experience two types of problems when working with buildings:
1. The building inputs show systems linked to the building that should not be linked or does not show systems
that should be linked.
2. When generating building simulation reports, the calculation halts with an error 32 (“chilled water coils in an
air system have no source of chilled water”), error 34 (“hot water coils in an air system have no source of hot
water”) or error 36 (steam coils in an air system have no source of steam”). However, the cause for these
errors is not apparent.
Discussion: These errors can result from the following sequence of events:
1. A user enters systems.
2. A user enters plants and in doing so links systems to plants.
3. A user enters buildings and in doing so links plants to buildings. When plants are linked to the building, the
program automatically links all systems served by the plants to the building.
4. Later a user edits the inputs for a plant already linked to a building and changes the set of systems served by
that plant.
When systems linked to the plant are changed in step #4, the program is not able to automatically update building
information concerning systems linked to the building via plants. As a result, if you view the building input data
you’ll see the original set of linked systems shown. Your changes in system-to-plant linkages will not be shown.
Further, if you try to generate building simulation reports, you will get the errors 32, 34 and/or 36 because the
information about building-plant-system links in building data is out of synch with the modified plant data.
Workaround: Users should observe the following rule:
If systems linked to a plant are modified, and that plant is already linked to a building, the building inputs must be
modified as explained below before generating building simulation reports:
1. Edit the buildings which include the plant that was modified.
2. On the Plants tab deselect all plants.
3. Switch to any other tab in the Building form.
4. Immediately switch back to the Plants tab and reselect the plants.
This resets the system linkages for the building and updates them to reflect the latest plant-system linkage
information.
(Bug 22973)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 152 of 218

Error 6 in cDesignLoad AssignSystemSizing
Date: May 30, 2003
Revised: Oct. 6, 2008
Summary: While running system design calculations the program halts and displays the following error
message:
Error Details
Number: 6
Description: Overflow in cDesignLoad AssignSystemSizing

Error Source Details

Library: HAP46SCM
Module: cSimControl
Method: Run()

After pressing OK to clear the message the program returns to the main window. The calculation is not completed
and system design results cannot be displayed.
Discussion: This error can occur when a large plenum heat gains exists at the same time very low plenum
airflows exist. In the single instance of this problem a user had specified the minimum airflow for a VAV box as
0%. HAP requires airflow in the VAV box so it overrides the 0% and uses 1% instead. This results in very low
supply and return plenum airflows when the zone has a net heat loss. The 70% roof and 30% lighting heat gain to
the plenum resulted in extremely high plenum temperatures which caused a psychrometric calculation to fail.
Workaround: Specify realistic minimum airflow values for zone air terminals. Typically the minimum airflow will
be determined by a CFM/person ventilation rate, or an air flow that maintains minimum air changes in the zone, or
some similar criteria.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 153 of 218

Windows Installer Launches when Running HAP
Date: July 26, 2002
Revised: Oct. 6, 2008
Summary: A user is running HAP. At some point during operation, such as when reports are requested, the
installer program for another program such as AutoCAD or Microsoft Office executes and begins installing that
program. This error occurs even though there is no connection between HAP and the other program that is trying
to install. However, this is a known problem with Microsoft software that has been documented by Microsoft. This
type of problem can occur if you have any of the following installed on your computer, and one of these programs
is damaged:
* AutoCAD
* Architectural Desktop
* Roxio Easy CD Creator
* Microsoft Office
This problem could involve other programs. Those listed above are the only programs we have seen involved with
this problem so far.
Explanation: Microsoft has a product called “Microsoft Installer” (MSI). MSI provides installation services for
other programs as well as “auto-repair” features which allow MSI to detect when a program is damaged and then
automatically repair that damage. Many software vendors use MSI to install and auto-repair their software.
However, MSI is prone to activating its auto-repair feature at the wrong time – such as when another program
written using the Microsoft Visual Basic programming language is started or is already running.
Example: AutoCAD is a program which uses MSI. HAP v4 was written using Visual Basic. However, when HAP
is started or is running, MSI may activate and try to repair AutoCAD if MSI detects AutoCAD is damaged. The
repair involves reinstalling AutoCAD which is why AutoCAD installation messages begin appearing when you start
HAP. This happens even though there is no association between HAP and AutoCAD, or between HAP and MSI.
Workaround: The short term solution to the problem is to press the cancel button on the MSI message windows
which ask you to insert a program installation CD. You may have to press the Cancel button several times as MSI
can be persistent about trying to auto install the program.
The long term solution is run a complete reinstall of the damaged program. For example, if MSI is trying to
reinstall AutoCAD, AutoCAD should be reinstalled. Once damage to the other program is eliminated, MSI will stop
trying to auto install it when you start or run HAP.
This type of problem has the potential to recur until Microsoft updates MSI to fix this problem.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 154 of 218

Program Hangs When Requesting Reports on Windows NT
Date: November 6, 2003
Revised: Oct. 6, 2008
Summary: While running HAP a user chooses an option to print or view reports. At this point the program hangs
and must be closed using Windows Task Manager.
Discussion: This error occurs on computers using the Windows NT operating system when certain key Windows
files are missing. Typically the key files will be missing if Microsoft Internet Explorer v4.0 or later has not been
installed on the computer.
Workaround: To correct this problem using the following procedure:
1. Make sure the computer is using Windows NT service pack 4 or later. If not, upgrade Windows to the latest
NT service pack.
2. Make sure the computer has Microsoft Internet Explorer v4.0 or later installed. If not, install it.
3. Reinstall HAP.
4. Run HAP and generate reports.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 155 of 218

Energy Consumption for Dehumidification Reheat Not Calculated in
Simulation
Date: November 6, 2003
Revised: Oct. 6, 2008
Summary: A simulation is being run for an air system having the following characteristics:
* System type is Water Source Heat Pump
* A common ventilation unit is used.
* The common ventilation unit is a water source heat pump.
* The common ventilation unit includes dehumidification control.
Inspection of simulation results shows that dehumidification reheat loads are calculated for the common
ventilation unit but no energy consumption reheat duty is calculated.
Discussion: The sole source of heat in the common ventilation unit is the water source heat pump. When the unit
is cooling and dehumidifying the water source heat pump is in cooling mode. Heating cannot be supplied because
the heat pump cannot simultaneously cool and heat. Therefore, the program cannot calculate energy
consumption for the dehumidification reheat. Ideally the program should prevent the use of a water source heat
pump for common ventilation unit when dehumidification control is specified.
Workaround: In the common ventilation unit change the cooling source to air-cooled DX and the heating source
to one of the available options. Then rerun the simulation. Energy results will be correct when this is done.
Note: A similar problem can occur in a single-zone CAV packaged rooftop heat pump, and a single-zone CAV
split DX AHU heat pump where dehumidification control is used.
(Bug 22974)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 156 of 218

The Object Invoked Has Disconnected from its Clients
Date: March 7, 2005
Revised: Oct. 6, 2008
Summary: From the HAP main window, the user double-clicks the “new default plant” option to create a new
plant or double-clicks an existing plant to edit its data. Before the plant input window appears the program halts
and displays an error message:
Runtime error –2147417848 (80010108)
Automation Error
The object invoked has disconnected from its clients.
If you press OK to clear the error message window, the plant input window will appear, but it is largely empty.
Data for the plant is not shown, and parts of the user interface are not shown either. It is not possible to create or
edit plant data.
Workaround. In the few cases where this error has been encountered, the workaround has been to:
1. Install Windows 2000 service pack 4 (or later) when the computer is running Windows 2000.
2. Install Windows XP service pack 2 (or later) when the computer is running Windows XP.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 157 of 218

"The Changes You Requested to the Table Were Not Successful..." Error
when Publishing Data
Date: Oct. 6, 2008
Summary: In certain situations when a user selects the Publish feature, selects systems and plants to be
published, and then presses the OK button on the Publish window, the following error message appears:
clsProjectDataServer.ExportTagData
The changes you requested to the table were not successful because they would create duplicate values in
the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data,
remove the index, or redefine the index to permit duplicate entries and try again.
This error prevents equipment sizing requirements from being published.
Explanation: This error has been seen on computers running Microsoft Internet Explorer v7.0. In most cases this
means the Windows Vista operating system is being used. But we have also seen cases where Internet Explorer
v7.0 is installed on Windows XP systems.
The cause of the error is not yet known and is still being investigated. Further information will be posted when
available.
Workaround: Until the cause is determined we cannot offer a workaround.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 158 of 218

"Error 0 in Calculate" During System Design Calculation for a VVT System
Date: Oct. 6, 2008
Summary: For certain conditions, the following error message will appear when running system design
calculations for a VVT type of air system:
HAP46
Error Details:
Number: 0
Description: in CDesignLoad Calculate()
Explanation: "Error 0" messages can result from a variety of conditions. For a VVT air system a common culprit
involves the duct heat gain specification. For certain operating conditions a large duct heat gain may result in very
hot or very cold conditions that cause psychrometric calculations to fail.
Workaround: Try setting the duct heat gain input to 0% and rerun the calculation. If this eliminates the error, it
may be possible to use duct heat gain values greater than 0% but smaller than the original heat gain % you
specified.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 159 of 218

Building Footprint Diagram Labels in Building Wizard not Readable
Date: Oct. 6, 2008
Revised: October 13, 2009
Summary: When running the Building Wizard, the zone name labels that appear in the building footprint diagram
on Wizard screen 1 and on the report are misaligned with the diagram. The labels should each appear within the
borders of the zone. Instead, many of the labels are shifted, some entirely outside the boundaries of the footprint
diagram.
Explanation: An incompatibility with certain kinds of display monitor settings causes this problem. The display
monitor is divided into units called "pixels". Pixels are subdivided into units called "twips". The twip/pixel ratio
varies as a function of monitor resolution and a variety of other monitor settings. The software positions the zone
labels using screen measurements in twips. The software is assuming standard twip/pixel ratios based on screen
resolution. So it will successfully position the labels as resolution changes. But when any of several other monitor
settings are changed to non-standard values, problems positioning the labels can occur. These settings include:
(1) Font Size - "Normal" is the standard setting. Using "Large Fonts", "Extra Large Fonts", "Small Fonts”, or
"Custom Font" can sometimes cause this problem.
(2) DPI Setting - "Normal" is the standard setting. Using other settings can sometimes cause this problem.
(3) Wide Screen Mode - This can result in different twip/pixel ratios in the X-direction and Y-direction which
sometimes can cause problems positioning the labels.
These are the three settings we have encountered that can cause problems, but it is possible other settings can
cause the problem too.
Workaround: Adjusting monitor settings to determine whether any setting is causing the problem. To do this:
1. From the Windows Desktop press Start and then choose Settings > Control Panel.
2. In Control Panel double click the Display item.
3. In the Display Properties window, first go to the Appearance tab. Check the Font Size item in the lower right.
If it is not "Normal", change to "Normal", click Apply to apply the setting and the run HAP to see if this
resolves the problem.
4. In the Display Properties window, to the Setting tab, click the Advanced button and inspect the DPI Setting
item. If it is not "Normal", change to "Normal", click OK to return to Display Properties and then click Apply to
apply the setting. Finally run HAP to see if this resolves the problem.
5. If the monitor is operating in Wide Screen mode, determine whether this mode can be temporarily disabled. If
it can, run HAP to see if this resolves the problem.
If one of these tests identifies the cause of the problem, the next step is to determine whether it is practical to run
in the Normal setting. For example, non-standard Font Size or DPI setting may be necessary for text to be
readable on high-resolution monitors. Because the problem with zone labels is cosmetic, it may be more
important to keep the original monitor settings in place than to have the zone labels appear properly.
(Bug 22976)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 160 of 218

Tree Panel on Left Side of Main Screen is Not Responsive
Date: January 23, 2009
Revised: October 31, 2013
Corrected In: HAP v4.80

Problem Has Been Resolved

Please Install HAP v4.80 or later to eliminate problem.

Summary: A user runs HAP and finds the tree panel on the left side of the main screen is not responsive.
Clicking on any item in the left-hand panel has no effect. For example, clicking on Air Systems in the left panel
should display the list of air systems in the project in the right-hand list panel. Due to this problem, nothing
happens when clicking on Air Systems or any other item in the left hand panel. As a result it is impossible to do
anything productive with the program.
Workaround: This problem has been reported 2 or 3 times. In each case the user was working on a computer
workstation that used two or more monitors. HAP was being run on one of the secondary monitors. When the
monitor configuration is changed to run HAP on the primary monitor, the problem disappears.
Note: This problem appears to have been caused by bugs in older Microsoft components which HAP used before
version 4.80. These components originally were distributed with Visual Basic 5, the predecessor to the
programming language now used by HAP (Visual Basic 6).

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 161 of 218

"Navigation to the Webpage has been Cancelled" Error When Displaying
Help
Date: October 25, 2010
Revised: July 31, 2013
Summary: A user attempts to display content from the HAP help system by any means (Help Menu, Help
buttons, F1 help, Help item in Start Programs menu). The help system appears. The table of contents panel on
the left is visible. In the right-hand panel where the help topic should appear there is a message like "Navigation
to the webpage has been cancelled". Due to this error, help information cannot be viewed.

Discussion: The HAP help system uses the "HTML Help" format. While this is the help format recommended by
Microsoft, there are features in Microsoft Windows which can block the ability of the computer to display material
in these help files. Resolving this problem involves adjusting security settings in Windows to unblock access to
HTML help material. Two workarounds are described below.
Workaround 1: Unblocking access to HTML Help via the HAPxx.CHM Properties window:
1. Start Windows Explorer
2. Navigate to the \E20-II\HAPxx\Code folder.
3. Locate the HAPxx.CHM file in this folder and right-click the file.
4. Choose "Properties" on the pop-up menu.
5. In the Properties window, click on the General Tab.

HAP Support Notes rev. 501_05 -- Page 162 of 218

 (Generic screenshot)

6. In the lower portion of this tab look to see if the following material appears:
Security: This file came from another computer and might be blocked to help protect this computer.
Then to the right of this message an "Unblock" button appears. Click the Unblock button and then press OK to
save the change and exit the Properties window.
Note: If there is no Unblock button, then your version of Windows does not provide this blocking feature, and
Workaround 2 must be used.

Workaround 2: Unblocking access to HTML Help via the Windows Registry

This workaround requires modifying the Windows Registry file.
Important Note: If the modification to the registry is not done correctly, it can cause serious operating problems
for your computer. Therefore, only someone trained in working with the Registry, such as your IT staff, should
make this change. The person making the modification must be logged in with full administrative rights. It is a
good idea to make a backup copy of the registry before performing any modifications. The following Microsoft
Knowledgebase article describes how to back up the registry: http://support.microsoft.com/kb/322756/
The procedure for modifying the registry to correct the HTML Help problem is described in the following Microsoft
Knowledgebase article: http://support.microsoft.com/kb/896054. See the "Example 2" section in this article -- this
contains the specific data needed to modify the registry to correct the HTML Help problem.

Notes:
Even though the error message refers to displaying a "web page", HAP does not use web-based help files. The
HTML help file used by HAP is stored in the \E20-II\HAPxx\CODE folder on your computer. The reason for this

HAP Support Notes rev. 501_05 -- Page 163 of 218

misleading message is Windows features and security settings appear to deal with HTML Help files in the same
manner regardless of whether they are on your hard disk, a network drive or a web site.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 164 of 218

Boiler Plant Simulation Results Differ Between v4.5 and v4.6
Date: April 2, 2012
Summary: A user converts a project created in HAP v4.5 to v4.6 format. The project contains hot water or steam
boiler plants using boilers for which a user-defined part-load curve was defined. In HAP v4.6 simulation
calculations are rerun for the boiler plant. The user compares the HAP v4.6 results with the original HAP v4.5
results and observes boiler energy consumption has changed. In some situations the change in energy use is
very large, with HAP v4.6 showing much lower energy use than HAP v4.5.
Discussion: This not an error. Rather the difference in results is due to a change in the boiler plant simulation
algorithm. In HAP v4.6 a 10% minimum load assumption was implemented in the algorithm. When the boiler part-
load ratio is below 10%, the boiler runs at 10% and cycles on and off to meet the load. In HAP v4.5, the boiler was
assumed to be able to modulate all the way down to 0% load without cycling. The following example illustrates
how differences in boiler energy consumption can occur due to this change.
Example:
Hot Water Boiler Plant
Boiler Full Load Capacity - 1000 MBH.
Plant consists of a single hot water boiler.
Boiler uses a user-defined part-load efficiency curve in which the efficiency at 10% load is 60% and the
efficiency at 0% load is 0%.
Consider an hour when the plant load is 40 MBH, or 4% load.
HAP v4.5 Calculation - Because the boiler is assumed to be able to modulate to 0% load without cycling, the
algorithm interpolates between the 10% and 0% points in the user-defined curve to obtain an efficiency of
24% at 4% load. The boiler input energy is then 40 MBH / 0.24 = 166.7 MBH.
HAP v4.6 Calculation - Because the boiler is assumed to have a 10% minimum load, the boiler will operate at
10% load for 40% of the hour and will be off for the remainder of the hour. When operating at 10% load, the
boiler efficiency is 60% and the energy input is 40 MBH / 0.60 = 66.7 MBH. Because the boiler is cycled on
for only 40% of the hour, the energy input for the hour is 66.7 MBH x 0.40 = 26.7 MBH.
Therefore the imposition of the 10% minimum load in this case causes the modeled boiler energy use to drop
from 166.7 MBH to 26.7 MBH. If a large number of hours per year exist with boiler part-load ratios below 10%,
this can result in large changes in boiler annual energy use between v4.5 and v4.6.
In this particular example, the user may have been assuming HAP v4.5 modeled cycling between 10% and
0% load and therefore specified a 0% efficiency for 0% load. However, HAP v4.5 interpolated between the
10% and 0% points rather than cycling the boiler. It is only in HAP v4.6 where cycling below 10% is modeled.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 165 of 218

Unable to see Network Drives When Saving a Project
Date: June 18, 2012
Revised: December 24, 2014
Summary: A user has installed HAP to his local hard disk drive (e.g., C: or D: drive). The user is attempting to
save a project to a network drive. However, the "Save Project As" window will not display any of his connected
network drives. Therefore, he is unable to specify a folder on the network drive as the storage location of the
project.
Discussion: See workarounds in Unable to see Network Drives for Install, which has essentially the same cause
and solution.
(Bug 22968)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 166 of 218

Error 521: Can’t Open Clipboard
Date: January 21, 2014
Revised: June 27, 2016
Summary: While HAP is already running, the user receives an error message such as the following:

[Error 521 – Can’t open clipboard]

This has been observed to occur while reports are being generated but it is possible it could occur at other times.
The user does not have to do a “copy”, “cut”, or “paste” operation using the clipboard in order to trigger this
problem. After the error is received, the report is not generated correctly and in some cases HAP needs to be
killed and restarted.

NOTE: As of HAP 5.0 this problem should be eliminated permanently. The clipboard is no longer used in
the way which sometimes led to this problem.

Discussion: This error does not cause reported results to be incorrect. It could cause the report to malfunction
so only part of the report appears, but the results shown on any report that does generate are correct.
The cause of the error seems to be that another program has “locked” the Windows clipboard for its own use and
not yet released it. Such locks are meant to exist only for a very short period of time, but a buggy program might
not unlock things after it has done its work.
It is not known what other specific program running on the user’s PC causes this problem, although anecdotally
Microsoft Office / Excel / Outlook have been identified as a possibility. More experience with the problem is
necessary to determine this.

Workaround 1 – Clear Microsoft Office / Excel Clipboard

1. Start Microsoft Excel
2. At the main window, click the Home tab.
3. On the Home ribbon (see Figure), in the Clipboard section (far left), click the little box with the arrow just to
the right of “Clipboard”
4. The Clipboard pane will appear below (see Figure below).
5. If there are items shown in the white box in this panel (Figure below shows a graph and a screen image),
then press the Clear All button. The white panel will change to show a message “clipboard is empty”.
6. Start HAP and try to generate reports.

HAP Support Notes rev. 501_05 -- Page 167 of 218

 Excel Clipboard Example

Workaround 2 – Try Again

The error could be a case of very bad timing in which case simply performing the operation again might work
successfully. E.g., try to view the report again.

Workaround 3 – Systematically Close Other Programs

Assuming there is one other program which is causing this problem, closing that program should resolve the
issue. It is recommended to close other programs one by one, and re-test for the problem after each one. This
may identify which specific program is causing the problem.

Workaround 4 – Logout / Login –or– Reboot

If the other workarounds are unsuccessful, logging out and back may clear the problem. Failing that, a reboot may
be required.

Workaround 5 – Send Project to Carrier

If for some reason this problem persists and the workarounds above do not work, send the project archive to
Carrier and a list of the reports to generate, and we could generate, save as RTF / Word files and send back.
This is only an interim solution meant as a last resort.

Notes: The Windows “clipboard” is the area of computer memory used whenever the user performs “copy”, “cut”,
and “paste” operations. That memory area is shared among all running programs. Windows carefully controls
access to the clipboard so that two programs cannot simultaneously try to access the shared memory area, which
could result in garbled information.

HAP Support Notes rev. 501_05 -- Page 168 of 218

In some instances the clipboard can also be used internally by a running program, which the user would not
normally be aware of. HAP does this sometimes (particularly in running reports) which leads to the error.
(Bug 17096)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 169 of 218

HAP Seems to Freeze (Window Off-Screen)
Date: May 29, 2015
Revised: n/a
Summary: The user performs an action in HAP after which the HAP windows become totally unresponsive. No
keyboard action or mouse action seems to have any effect. The program appears to be totally frozen. Killing the
process via Windows Task Manager is the only obvious way out.
Discussion: This problem is most likely due to a window being opened off the screen. For example:
* The user selects Project menu > Retrieve Archive Data
* HAP appears to freeze
* What has really happened is that the file selection window has opened and is waiting for user input.
* The program waits for the user to complete that window before allowing any other actions.
This can happen most often with laptops which sometimes use a dual monitor setup, and other times do not, or
are hooked to different screens at different times, such as projectors etc.
Workaround: See Dealing with Windows that are Located Off-Screen.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 170 of 218

Dealing with Windows that are Located Off-Screen
Date: May 29, 2015
Revised: n/a
Summary: For various reasons, HAP windows can sometimes be opened off to the side of the screen so that
they are not visible.

Discussion: Note that this issue is not unique to HAP but are a common pitfall on Microsoft Windows.
Keyboard commands can be used to move them back to the visible area. There are two workarounds. The first is
easiest but may not work for all program windows. The second should work in all cases but has more steps.

Note that it is a very good idea to practice this with a VISISBLE window first, so it makes sense. These are
standard Windows keyboard operations, not specific to HAP, so using a window such as Explorer would be useful
practice.

Workaround 1: Use [WINDOWS KEY] commands to relocate the HAP program window:
Note: These key commands should work in recent versions of Microsoft Windows but may not be supported in old
versions or with very old keyboards.
1. Start HAP
2. Click OK on the initial windows, until the problem occurs and the HAP main window is not visible.
3. Press [WINDOWS KEY] + [UP ARROW] (at the same time). This should maximize HAP to fill the screen.
4. As an alternative, pressing [WINDOWS KEY] + [RIGHT ARROW] or + [LEFT ARROW] can be used to move
the HAP window to the visible portion of the display. Which one is needed may depend on where the HAP
window is actually located.

Note: The [WINDOWS KEY] typically looks like or .

Workaround 2: Use key commands to activate mouse movement of the window:

1. Make sure HAP is still the active program (should be shown as selected on the Windows task bar)
2. Press ALT-SPACE to bring up the system menu of the active window (you won't see it because it is off
screen)
3. Press R to select the "Restore" menu choice to ensure the windows isn't is maximized (you cannot move
it if it is maximized)
4. Press ALT-SPACE again, then M to select the "Move" menu choice.
5. Press one of the arrow keys to initiate the movement.
6. Now just use the mouse to place the window where you want.

(Instructions from http://superuser.com/questions/53585/how-to-move-windows-that-open-up-offscreen)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 171 of 218

HAP Main Window Location Problems in a Networked Installation
Date: July 14, 2015
Revised: n/a
Summary: Moving HAP to the second monitor, and closing it from there, causes HAP to open on the secondary
monitor for everyone, including those that have 1 monitor. Employees with 1 monitor cannot see HAP on the
secondary monitor, because they don’t have the second monitor to see it.

Discussion: One of the settings HAP saves every time you run it is the location of the main window on your video
monitor. When you have a network installation you have one set of HAP settings, so if one users moves the
location of the main window, that will affect all users. If one user moves the main window to a secondary monitor,
then HAP will try to start on a secondary monitor for all users. If a user doesn’t have two monitors, he won’t be
able to see the main window anymore.

Workaround 1: Users can fairly easily move the HAP main window to the main screen by following instructions in
Dealing with Windows that are Located Off-Screen. This requires only user training, no change to installation etc.

Workaround 2: The program only saves window settings when you actually close / exit HAP. So there should be
no issue with users working on the secondary monitor as long as they move it to the primary before closing it. If
someone forgets to do that, they need only run it again, move it, and then exit again.

Workaround 3: Software could be installed locally on each workstation. That way the user has settings that are
specific to the workstation and don’t affect anyone else.
Data can still be saved on and shared via the network, but a small amount of extra effort is needed to save to the
network and share across the network when installed locally.
(Bug 23064)

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 172 of 218

HAP “Not Responding” When Selecting Files or Printing (Antivirus)
Date: June 15, 2015
Revised: January 14, 2016
Summary: The user attempts to select a file, such as an archive, and HAP seems to freeze up. Or, they try to
bring up the printer settings. The Windows Task Manager then reports HAP as “Not Responding”.

Discussion: This issue has certain very specific attributes which help to distinguish it from other cases. The usual
sequence of events are:
1. User ran HAP (any version)
2. Initially the program works normally.
3. The user attempts to select a file – such as to retrieve an archive, choose simulation weather data, etc. (Note –
this does not occur when simply opening a project – it is specific to explicit FILE operations).
Alternately, they selecting one of the options to show the printer selections.
4. At the moment the file selection or print setup window should have appeared, HAP “freezes” and becomes
unresponsive.
5. Run Windows Task Manager (from Start menu or press [CTRL]+[SHIFT]+[ESC])
6. Look for the HAP entry. This should be listed as “not responding”, as in these examples:

(Example Windows 7 and Windows 10 screenshots)

7. The PC was running certain antivirus software: either BitDefender, or Security manager AV Defender by N-
able.

If all the above steps are not observed then this support note probably does not apply. Instead, it is possible a
window is opening off the screen – see Dealing with Windows that are Located Off-Screen instead.

Workaround: Ending the program in Task Manager and then restarting it gets around the immediate issue of
HAP being frozen. Any work which is not saved most likely cannot be recovered.
Following that, the user should:
3. Disable their antivirus software. They may need admin rights and/or support of their IT group to do this.
4. Try HAP again and confirm that the problem is fixed.
5. Log a support ticket with the antivirus software vendor. We cannot do this for them, as we have no
relationship with the antivirus vendors.

HAP Support Notes rev. 501_05 -- Page 173 of 218

Note – we are actively working on getting in touch with the antivirus vendors to get this permanently fixed. As of
Nov. 2015, this seems to have been accomplished with AV Defender. BitDefender is not yet resolved.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 174 of 218

Errors Loading gbXML – Missing SSNhapXMLAdapter53.mdb
Date: July 14, 2015
Revised: n/a
Summary: The user loads a gbXML file. At some point in the import process, they receive an error like:

(clsResource.OpenResources() Could not find file ‘\Wizards\SSNhapXMLAdapter53.mdb’)

As a result the import process fails.

Discussion: This has occurred to several customers, all of whom were importing gbXML produced by Revit
software. It is not known if other sources of gbXML could produce the same problem, but this seems possible.
There are two related problems occurring here:
1. HAP error display does not work correctly in this case, so the correct error message is not shown.
There is no real problem with any missing files.
2. The actual problem is that some details in the gbXML file are invalid or at least outside of what HAP
can handle. All the cases seen so far have failed because of invalid wall assembly data. The program
internally runs into the error “Transfer function coefficients could not be generated for this assembly of
material layers. Generally this problem occurs when the overall thermal resistance or thermal
capacitance of the assembly is too small or too large.” This error can also occur when entering wall or
roof data manually.

In one case the gbXML file provided by the customer showed an unrealistically small layer thickness. It is
expected that other cases of this problem would have similar issues. Invalid layer thickness or material properties
could cause this problem.

Workaround: The construction assemblies should be examined for correctness. If necessary, the gbXML file can
be examined in Syracuse to determine which assembly is causing the problem.
Note that one customer reported that upgrading the version of Revit in use resolved the issue. It is possible that
some version(s) of Revit could be producing gbXML with incorrect assembly details. However this has not been
confirmed. Specifically, the customer reported that upgrading to Autodesk Revit 2015 Update Release 8 fixed the
problem in their case.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 175 of 218

“MAPI” Error Sending Email to Sales Engineer
Date: August 13, 2015
Revised: n/a
Summary: The user chooses Send Email to Sales Engineer, and receives an error like:

(An error occurred while creating the e-mail message. MAPI error number 2 / Unspecified)

This error occurs after the archive has been saved. As a result the email process fails.

Discussion: This has been known to occur within UTC on CSC-managed PCs, but it is possible it could occur to
an external (non-UTC) customer also.
Since HAP requires passing through the Windows User Access Control prompt when it starts, it runs with different
permissions than the user’s email program, and that causes the error.

Workaround: This workaround uses Microsoft Outlook as the example – but may work for any email software
which is not web-based (for web-based email, see below). Depending on the program, the user may have to take
separate steps to identify the EXE file which is needed. SSN support can help with this.
1. Close any running windows of the email program
2. Run Windows Explorer (Start menu > click Computer or My Computer)
3. In the top of the Explorer window, paste the path:
C:\Program Files (x86)\Microsoft Office\Office14
Note – this path may vary from PC to PC. If in doubt, search C: drive for OUTLOOK.EXE
4. Right-click on OUTLOOK.EXE and select Run as Administrator (see figure below)

HAP Support Notes rev. 501_05 -- Page 176 of 218

 5. Click yes to the prompt
6. When Outlook starts, try the HAP email feature again

For web-based email, assuming the user has it setup to integrate with their PC (which is often not the case), then
the program to run as administrator would be their web browser. E.g., iexplore.exe, firefox.exe, etc.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 177 of 218

Error 339 - Component or one of its dependencies not correctly
registered: a file is missing or invalid
Date: October 6, 2015
Revised: n/a
Summary: This error typically appears when HAP starts, but might occur during operation. The error message
looks like:
The following error has occurred.

Please contact Carrier Software Systems for assistance.

Error Number: 339

Description: Component 'MSCOMCTL.OCX' or one of its dependencies not correctly
registered: a file is missing or invalid

Source:
Module1.Main
HAP49

----------
ID: HAP49-491 10/5/2015 3:09:41 PM on CHELSEA

The specific component referred to can vary. Past examples have included: MSCOMCTL.ocx, TABCTL32.ocx,
MSRDO20.dll, etc.

Discussion: HAP requires a number of program files, called “components” to be installed correctly on each
user’s computer. The HAP and XBF installers normally take care of this. However, sometimes an installed file
gets deleted or its installation information (“registration”) corrupted. This typically happens with files like
MSCOMCTL.ocx which is a shared Microsoft component that many programs rely on.

Workaround: Use the following steps to clarify the problem and provide a fix. Recommend working through each
workaround one-by-one until a solution is found.
Workaround 1: Send Carrier a diagnostics file. That may allow pinpointing of the problem. (Refer to instructions
elsewhere to do this).
Workaround 2: Reinstall XBF, and then reinstall HAP. In many cases this resolves the issue.
Workaround 3: If re-installation did not work, there is a possibility that the file is missing.
To locate the file:
 Click the Start Menu
 Note the “search folders and files” text box at the bottom of the Start Menu
 To use the search function, just start typing the problematic filename as shown:

HAP Support Notes rev. 501_05 -- Page 178 of 218

  (MSCOMCTL.ocx used as an example)
 Then press enter. A new Explorer window should open.
 When the search is complete, take a screenshot of the results window and send that back to Carrier in
email.

Workaround 3A: If the file was missing:

 Since the re-install did not work, Carrier may need to manually provide the missing file.

Workaround 3B: If the file was found on their PC, it needs to be re-registered.
Instructions to install software component:
(Note that cases below where text needs to be typed in can also be done by copying from an email, right-
clicking into the command prompt window, and pasting)
1. Assume that the path to the component is c:\windows\system32\mscomctl.ocx.
o Substitute the correct path and filename from the file search, as needed.
o Note – path would be in c:\windows\syswow64 for 64-bit Windows.

2. Go to the Start Menu >

a. Type cmd in the search box > Right-click on cmd.exe and select Run as Administrator (see
screenshot below)
b. Click OK/yes or Enter administrator password as needed
c. Command prompt (text) window should open up

HAP Support Notes rev. 501_05 -- Page 179 of 218

3. Registration steps:
a. On 32-bit Windows:
At the command prompt type:
c:\windows\system32\regsvr32.exe C:\Windows\system32\mscomctl.ocx then press ENTER

b. On 64-bit Windows:
At the command prompt type:
c:\windows\syswow64\regsvr32.exe C:\Windows\syswow64\mscomctl.ocx then press ENTER

HAP Support Notes rev. 501_05 -- Page 180 of 218

 Example command prompt:

c. A message should appear indicating the file was successfully registered. If not, try the next
command (alternative possible file location).

4. Run HAP to see if the problem still occurs.

If the above workarounds have not been successful, ask for an additional diagnostic report and escalate to Level
3 support.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 181 of 218

Text Cut-Off (Spaces Screen, Schedule Screen, etc.)
Date: Sept. 16, 2016
Revised: n/a
Summary: Text on one or more screens appears to be cut-off, such as:

.
This has been observed in the Schedules & Spaces screens but could occur in other places.

Discussion: This is a Windows bug or flaw, apparently first introduced in Windows 7 but which still occurs in
Windows 10. Full details: http://www.rlvision.com/misc/windows_7_font_bug.asp

Workaround: As published in the link above, use the following steps to fix the issue.
Note – since this involves registry editing, customers should be cautious and/or to ask their IT people to assist if
they are not confident in doing this themselves.

 Open the start menu and type regedit and then press [Enter].
 Locate the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts
 Find the value MS Sans Serif 8,10,12,14,18,24
 Change from SSERIFF.FON to SSERIFE.FON
 Find MS Serif 8,10,12,14,18,24
 Change from SERIFF.FON to SERIFE.FON
 Finally find Courier 10,12,15
 Change from COURF.FON to COURE.FON
 Restart the computer for the changes to take effect.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 182 of 218

Transfer Function Generation Failure can Corrupt Roof / Wall Inputs
Date: July 13, 2017
Summary: If a Transfer Function Generation Failure error is received when saving a roof or wall, its data may
become partly corrupted.
Discussion: There are cases where a roof or wall assembly fails to save because the Transfer Function
Coefficient Generator (TFCG) cannot calculate coefficients. This is usually because one or more assembly layers
are extremely thin and the error can be avoided by increasing the thickness of one of the layers until the assembly
saves successfully.
HOWEVER in this circumstance, reopening the assembly for editing may show that one of the layer thicknesses
has been automatically changed to an incorrect value. Examples: increasing from 0.034-inches to 0.403-inches in
one case, and from -0.034-inches to 58.061-inches in another case.
Resolution: In any case where the wall or roof won’t save due to this error, the user should assume that wall or
roof is immediately corrupted. Continuing to adjust roof or wall data until it does save may end up saving
corrupted data which will later affect load calculations.
The user should cancel out when this occurs, then re-edit the wall or roof correctly.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 183 of 218

3.5 Common Errors - Printer and Reports Operation
Problems Printing Huge Report Packages
Date: April 20, 1999
Revised: Oct. 6, 2008
Summary: A user generating a report containing several hundred pages reported that only a portion of the report
printed. The complete package of pages did not print. Data was printed to a network printer.
Discussion: Due to its unusual nature, we have not reproduced the error, but we can speculate about its cause.
The user said 15 systems were selected in a batch and every report option was selected. Without knowing
specific details, this could have produced anywhere from a few hundred to over 24,000 pages in the report
package.
When generating reports, HAP creates an RTF document for each report requested. When the report is printed
information from these RTF documents are spooled to the printer. When the report package involves hundreds of
pages, it is possible to run out of disk space either on a local drive or the spool drive. We believe that if you run
out of disk space, a portion of the report will not be printed. Some network systems may generate an error, but
others may not.
Workaround: Be mindful of print spool file size requirements when printing. If disk space is limited, limit the size
of report packages being printed.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 184 of 218

Common Printer Workaround Procedures
Date: October 21, 2001
Revised: Oct. 6, 2008
Summary: Sometimes while generating printed reports with HAP a problem can occur:
 No report is generated at the printer, even though you selected the print option and no error messages
appeared.
 The material on the printed report is garbled.
 An error message appears saying the report cannot be printed because the printable area is too small.
These problems can be due to any one of several problems involving the computer and the printer driver being
used. Workarounds that are commonly successful are described below.
Workaround #1: In some cases the presence of .TMP files on the computer is interfering with printer operation.
Because this is easy to test, it is the first possibility to eliminate when resolving problems:
1. Run Windows Explorer and use the File Find feature to search for all *.TMP files on C: drive.
2. Delete any *.TMP files that are found. Note that your computer may refuse to delete certain .TMP files that
are currently in use. This is OK.
3. Then try generating the printout with HAP. If the problem persists, continue with the next workaround.
Workaround #2: If TMP files were not the cause of the problem, the most likely culprit is a problem with the
printer driver. There are three possibilities: (1) the printer driver may be damaged in subtle or not so subtle ways,
(2) the printer driver may be an old version that has a bug in it, (3) there may be an incompatibility between the
printer driver and HAP.
The first recommendation is to install a new, clean copy of the printer driver to see if this resolves the printing
problem. In the majority of cases, this workaround has solved the printer problem.
1. Obtain the latest version of your printer driver. The best place to obtain this is from the printer manufacturer's
web site. For example, Hewlett-Packard provides drivers for all of its printers freely on its web site.
2. Download the printer driver install file to your computer.
3. Follow the manufacturer's instructions for installing the printer driver. Note that we are not replacing the
existing printer driver. We are only installing a new copy. If this solves the problem, you can delete the original
driver at your discretion. If this does not solve the problem, then we will erase the new driver that you installed
since it is not useful.
4. After installing the new driver, designate this printer driver as the default printer. To do this:
a. From the Windows desktop, press Start, choose Settings and then choose Printers.
b. In the Printers dialog, right-click on the printer driver icon for the new driver you installed.
c. On the pop-up menu that appears, choose the "Set as Default Printer" item.
5. Then try generating HAP printouts again.
6. If the problem persists, then erase the new driver that you installed in step 3 above and its associated files.
Since this did not solve the problem there is no need to keep the files around. Also remember to reset the
default printer to your original driver.
Workaround #3: If installing a clean new driver did not solve the problem, it is possible there is a incompatibility
between the printer driver and HAP. If so, the solution is to install the "parent" driver for a family of printers. Printer
drivers typically are developed for "families" of related printers. The most basic or "parent" driver will work for all
printers in a family. Subsequent drivers for a particular printer in a family may enable special additional features,
but in doing so may introduce incompatibilities with certain software programs. Therefore, a solution is to install
the "parent" driver for the family of printers to see if it solves the problem.
1. Obtain the parent driver for your family of printers. The best place to obtain this is from the printer
manufacturer's web site. The following common "parent" drivers can be used:
 All Hewlett Packard Laserjet Printers: Parent Driver = HP LaserJet III or HP LaserJet IV
 All Hewlett Packard B&W Deskjet Printers: Parent Driver = HP Deskjet 500
 All Hewlett Packard Color Deskjet Printers: Parent Driver = HP Deskjet 550C

HAP Support Notes rev. 501_05 -- Page 185 of 218

  Laser printer by another manufacturer: Parent Driver = HP LaserJet II
2. Download the printer driver install file to your computer.
3. Follow the manufacturer's instructions for installing the printer driver. Note that we are not replacing the
existing printer driver. We are only installing a new driver. If this does not solve the problem, then we will
erase the new driver that you installed.
4. After installing the new driver, designate this printer driver as the default printer. To do this:
a. From the Windows desktop, press Start, choose Settings and then choose Printers.
b. In the Printers dialog, right-click on the printer driver icon.
c. On the pop-up menu that appears, choose the "Set as Default Printer" item.
5. Then try generating HAP printouts again.
6. If the problem persists, then erase the new driver that you installed in step 3 above and its associated files.
Since this did not solve the problem there is no need to keep the files around. Also remember to reset the
default printer to your original driver.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 186 of 218

Errors When Printing
Date: February 19, 2016
Revised: August 9, 2017
Summary: The user tries to view or print any report from HAP and receives an error similar to the following:
Error Number: -2147221504
Description: Error setting printer selection.

Source:
CIDOReport.BuildReport()
HAP.PrintingControl.SetPrintOptions_TER
HAP49
(Several variations of errors have been observed, this is just an example.)

Discussion: The root cause is unknown. But the workaround below appears to be successful in resolving it.

Workaround: In cases where this has occurred, we have advised users to try the following steps to narrow down
the problem. It seems that this is usually effective in clearing up the problem, for unknown reasons.
1. Change to another printer and try to print. The XPS or PDF printer is acceptable for this step.
2. Change back to the original printer, and try again.

Detailed steps:
1. In HAP, select the “Print Setup” option on the Report Menu.
2. In the Print Setup window that appears, open the Name drop-down list and select a different printer
(screen image below). If you have an XPS or PDF printer device option like the last two items in the
screen image below, that often is a good option to select. After selecting a new printer device press OK.

3. Back in HAP, generate the report which previously failed. Typically the report will generate OK.
4. Select the “Print Setup” option on the Report Menu again.
5. In the Name drop-down list, reselect your original printer device. Then press OK.

HAP Support Notes rev. 501_05 -- Page 187 of 218

 6. Back in HAP, generate the report which previously failed. In the previous instances of this error, the
report will now generate OK. Apparently switching to a different printer device and then switching back to
the original printer resets something in the Windows operating system which cures the problem.

If this procedure is not successful, please ask your customer to provide details about what happens:
 In step 2 what was the new printer device selected?
 In step 3 did the report generate successfully?
 In step 5 what was the new printer device selected?
 In step 6 please provide a screen image of the error that appeared, even if it was the same as the original
error.

HAP Support Notes rev. 501_05 -- Page 188 of 218

Air System Input Report contains Incorrectly Formatted Tables
Date: September 1, 2006
Revised: Oct. 6, 2008
Summary: A user generates the Air System Input Report for a terminal type of air system (fan coils, water source
heat pumps). In this report one or more of the tables that list zone-by-zone information about thermostat settings,
terminal performance and zone sizing results may be incorrectly formatted. The proper number of columns are
shown in the table, but all text and numeric data is squeezed into the left-most column of the table. As a result the
tables span many pages and are unreadable.
Discussion: This exact cause of this problem is unknown at this time, but a workaround solution is known (see
below). It appears the error occurs when the computer is running v8.x of the TER32.DLL and TOC.OCX report
writing software components, but the error does not occur if the computer is running v10.x of these same
components.
Workaround:
1. First generate the File Integrity Verification Report for HAP. Locate the TER32.DLL and TOC.OCX line items
(near the bottom of the report) and verify that the version found for TER32.DLL is v8.0.3.5 and for TOC.OCX
is 8.0.0.4. If so, continue. However, if the version found is not a v8.x version, contact Carrier technical support
for assistance.
2. Install the v10.0.3.9 version of TER32.DLL and v10.0.0.9 of TOC.OCX. There are two ways to do this:
a. Install XBuilder Framework v1.02j. XBuilder installs the v10.x versions of these two components along
with the rest of the XBuilder software. XBuilder can be downloaded from the Carrier internet site. It is the
management software used with Carrier E-CAT Builder programs.
b. Use the TER10_Patch_Update.EXE. This patch installer only installs TER32.DLL v10.0.3.9 and
TOC.OCX v10.0.0.9. It is available upon request from Syracuse.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 189 of 218

Unable to View More than One Report in Report Viewer
Date: January 23, 2009
Summary: A user runs HAP and asks the program to generate a batch of system design reports -- either multiple
reports for a single system, or reports for multiple systems. The report viewer appears and displays the first
report. When the user presses the Next Report button on the toolbar, the program immediately closes and returns
to the Windows desktop.
Workaround: This problem has been reported 2 or 3 times. In each case the user was working on a computer
workstation that used two or more monitors. HAP was being run on one of the secondary monitors. When the
monitor configuration is changed to run HAP on the primary monitor, the problem disappears.
Note: This problem appears to be due to specific monitor configuration settings. We have customers successfully
running HAP on secondary monitors in a multiple-monitor set-up. This problem only occurs on a subset of these
configurations. It is not known what specific monitor configuration settings lead to this problem in some cases,
and avoid the problem in other cases.
(Bug 22977)
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 190 of 218

System Psychrometrics Report - No Data Points Plotted
Date: November 30, 2009
Summary: A user generates the System Psychrometrics Graph report for an air system. The psychrometric chart
background (X and Y axes, RH lines, saturation line) appear but no psychrometric points or process lines are
plotted. The upper right may or may not show an index of psychrometric points such as "1. Central Cooling Coil
Outlet".
Discussion: The two most common explanations for this behavior of the System Psychrometrics Graph report
are:
1. Graph is Generated for a System OFF Hour. The System Psychrometrics Graph is generated for specific
month/hour combinations. If the month/hour requested is an hour in the unoccupied period when the system
is OFF, there will be no psychrometric points or process lines to plot. The graph will therefore be empty. To
check this, inspect the fan/thermostat schedule for the air system to see if the hour plotted is in the
unoccupied period. The tabular version of the System Psychrometrics report can also be generated to
determine if the system is ON or OFF for the selected hour.
2. There is no Data to Plot Because all Humidities are Zero. If simplified conditions were specified for the
system and its spaces so that there is:
a. No internal moisture gains or losses (i.e. no occupants and no miscellaneous latent gains or losses)
b. No ventilation airflow.
c. No infiltration airflow.
In a situation like this the program has no basis for calculating moisture levels in the system and all system
state points will have a specific humidity equal to zero. When this happens there is no meaningful data to plot
on the psychrometric graph and the graph is empty. This set of conditions essentially represents a perfectly
sealed box -- no moisture can go into or out of the building and no moisture is generated inside the building.
The fastest way to determine if this is the case is to inspect the tabular version of the System Psychrometrics
report for the same month/hour. Check to see if the humidity values are zero or non-zero. If zero, then check
your air system and space definitions to see if there is ventilation airflow, infiltration airflow, occupants or
miscellaneous latent gains. If none are present, then this explains why the humidities are zero.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 191 of 218

3.6 Common Errors – Data Management
Common Pitfall Retrieving From Previous Version
Date: February 9, 1999
Revised: Oct. 6, 2008
Summary: While using the “Convert HAP v3.2 Data” option on the Project Menu, the translation process
terminates and the following error message appears in the translation report:
Fatal Error HAP32 data folder does not contain a complete set of data files
No HAP v3.2 data is recovered.
Discussion: Typically this problem is due to one of three causes:
1. Source Folder Incorrectly Identified. When you choose the Convert HAP v3.2 Data option on the Project
Menu, the program asks you to identify the folder containing the HAP v3.2 data you want to retrieve. A
common mistake is to choose the folder one level above the folder containing your data. The folder selection
dialog displays a tree image of the folder structure on your hard disk. Navigate to the desired folder and then
double-click on the folder name so the folder icon has the appearance of an open (rather than closed) folder.
Users often make the mistake of thinking that if the folder name is visible or highlighted, the folder is selected.
However, a folder is only selected if its icon is an open folder.
Readers should note that the full path to the folder you’ve selected is listed toward the bottom of the dialog.
Before pressing the OK button, check this path to make sure it is correct.
2. Attempting to Convert Data Directly From an Archive File. It is not possible to convert v3.2 data directly
from an archive file. The v3.2 archive file must first be converted to working data using the Retrieve option in
HAP v3.2. Then it can be converted into HAP v4.x. Thus, if you select a folder containing only an archive file,
or select a floppy disk drive containing an archive file as the source of v3.2 data, the error message will
appear because the full set of unarchived files is not found.
3. HAP v3.2 Data Set is Missing Files. The third possibility is that the HAP v3.2 data set is damaged and is
missing files. As explained in the on-line help system, the following five files must exist in the HAP v3.2 folder:
HAP32WTD.DAT, HAP32CAL.DAT, HAP32SCH.DAT, HAP32MTL.DAT, HAP32SPC.DAT and
HAP32INA.DAT. When working with System Design Load v1.2 data, substitute SDL12 for HAP32 in these file
names.
Depending on which files are missing, it may or may not be possible to reconstruct the data set and retrieve it
into HAP v4.x. If HAP32SCH.DAT, HAP32MTL.DAT or HAP32SPC.DAT are missing the dataset cannot be
reconstructed. If any of the other files are missing, use HAP v3.2 to create a new data set in a new folder.
Then copy the data files that are present in the original HAP data set into the new v3.2 data folder. If
WTD.DAT was missing, weather data has been lost and will be reset to defaults. If CAL.DAT was missing,
day type names have been lost and will be reset to defaults. If INA.DAT was missing, all air system data has
been lost.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 192 of 218

Project Folder Still Exists After Deleting Project
Date: April 14, 1999
Revised: Oct. 6, 2008
Summary: After deleting a project a user notices that the project folder still exists. Often, deleting a project erases
the project data files as well as the project folder.
Discussion: When a project is deleted, there are three reasons for the project folder not being erased.
1. The project contains data from Carrier applications other than HAP. For example, a project can contain data
for multiple E20-II and E-CAT programs such as HAP, AHUBuilder, Air Terminal Selection, etc… If the
project folder contains data from other programs it cannot be erased because that would destroy the data
from the other programs.
If you wish to destroy all data in a project, the project must be deleted from each program having data in the
project folder.
2. If the project folder contains files in addition to those created by Carrier E20-II or E-CAT programs, the
additional files will not be deleted. Further, the folder cannot be deleted if it still contains files. Typically this
happens when a user adds files to a project folder manually (via Windows Explorer) or using other software
such as Word or Excel. When this situation occurs a warning message appears during the project/delete
procedure informing the user that the project folder can’t be erased.
If you wish to erase the project folder, this must be done via Windows Explorer.
3. There are rare situations which occur on Windows NT and Windows 98 operating systems that lead to this
problem. When a project is open, all the project files are placed in a temporary working folder named
~HAP46, one level below the project folder. When the project is closed (by opening another project or by
exiting the program), all the files in ~HAP46 are erased and the ~HAP46 folder itself is deleted. We have
observed some cases on Windows NT and 98 systems in which the ~HAP46 folder is not erased when a
project is closed. The cause of this is unknown. If you later delete the project, the project folder will not be
erased because it contains the ~HAP46 subfolder. Again, a warning message should appear during the
project/delete process to inform the user that the project folder can’t be erased.
If you wish to erase the project folder, this must be done via Windows Explorer.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 193 of 218

"Exception: Access Violation Has Occurred"
Date: May 5, 1999
Revised: June 27, 2016
Summary: Software is successfully installed and run. However, when the user tries to open an existing project,
save a project or save entities within a project, the following error message appears:
HAP46.EXE
Exception: Access Violation Has Occurred
Address: <lots of letters and numbers here>
Program operation halts. Prior to this error occurring, the software had been working properly.
Workaround: Several customers have encountered this error. For most we have been able to resolve the
problem using the workaround procedure below. This procedure uses a file provided by Microsoft to update a
group of Windows system DLL files on the desktop computer. Because this procedure solves the problem, it
indicates the problem is due to damaged, mismatched or invalid Windows system DLL files being present on the
computer.
1. Shut down all programs currently running.
2. Download the VBRUN60.EXE patch file from the following internet web site:
http://support.microsoft.com/support/kb/articles/q192/4/61.asp
Note that this internet address must not use the standard “www.” prefix. When the web page appears, scroll
the page down until the VBRUN60.EXE download item appears. Then click on this item to download the file.
You’ll be asked to specify a folder on your hard disk to receive the file.
3. Run Windows Explorer and navigate to the folder you saved VBRUN60.EXE into in step #2. Then execute
VBRUN60.EXE by double-clicking on the file name. This EXE will update a series of Windows system DLL
files on your computer.
4. Shut down the computer and reboot to activate the new Windows system DLL files.
5. Once the computer has restarted, run HAP and try opening and saving projects. The “Access Violation”
should not occur now.
6. In the event that this workaround does not solve the problem, please continue to the Diagnosis section below
to gather further information about your computer.
Diagnosis: In order to investigate this problem further, the following information needs to be collected and the
following tests need to be run.
1. Gather the following basic information about the computer environment:
a. What version of Windows is being used? Go to Control Panel and double-click on the System icon. The
General tab in the System Properties dialog lists the full Windows version.
b. Is the computer connected to a network? If so, what is the network operating system?
c. Has the software been installed to a network server drive or a local hard disk drive? What is the drive
letter for the install drive?
d. Did the error occur the first time the program was run, or did the program work properly for a period of
days or weeks before the error appeared?
e. If the program worked for a period of time, did any event coincide with the appearance of the error?
Examples might include a hardware upgrade or a software upgrade on the local workstation or on the
network server.
2. Investigate the scope of the problem. Determine whether the error occurs in each of the following situations:
a. Opening a project from the Open Project dialog that appears when you start HAP.
b. Opening a project from the Open option on the Project Menu. In order to do this, press the New button in
the Open Project dialog that appears when you start HAP. This creates a new project and takes you to
the main program window. You can then use the Project Menu.
c. Saving a project. In order to do this, press the Cancel button in the Open Project dialog that appears
when you start HAP. Then go to the Project Menu and choose the Save or Save As option.

HAP Support Notes rev. 501_05 -- Page 194 of 218

 d. Saving entities. Press the New button in the Open Project dialog that appears when you start HAP. Then
try entering and saving simple entities such as weather, windows, doors or shades.
3. Run the File Integrity Verification for HAP and save the resulting report resulting report to a disk file using the
“Save to File” button in the upper left of the report window.
4. Investigate saving and opening of projects.
a. Start HAP. In the Open Project dialog, press the New button to create a new project.
b. From the Main Program Window, go to the Project Menu and choose the Save As option. Name the
project and press OK to save the project. The “Exception: Access Violation Has Occurred” error will
occur.
c. Run Windows Explorer and examine the folder you designated for the project. Does it exist? If so, at least
part of the save procedure had executed before the error occurred.
d. Does the project folder contain the following files? If all files are present, then a large part of the save
procedure executed before the error occurred (xx refers to the version; e.g., ‘47’ for HAP v4.70):
HAPxxA00.DAT
HAPxxB00.DAT
HAPxxBLR.DAT
HAPxxCHL.DAT
HAPxxDOR.DAT
HAPxxERT.DAT
HAPxxFRT.DAT
HAPxxINX.MDB
HAPxxP00.DAT
HAPxxPRF.DAT
HAPxxROF.DAT
HAPxxSCH.DAT
HAPxxSHD.DAT
HAPxx2SPC.DAT
HAPxxTWR.DAT
HAPxxWAL.DAT
HAPxxWIN.DAT
HAPxxWTD.DAT
PROJECT.E3P
PROJECT.LDB
PROJECT.MDB
e. Does the project folder contain a ~HAPxx sub-folder? If so, delete this sub-folder. If the ~HAPxx folder
does exist, then nearly all of the save procedure executed before the error occurred.
f. Run HAP again. At the Open Project dialog, select the project you saved in step “b” above. The
“Exception: Access Violation Has Occurred” error will occur again.
g. Run Windows Explorer. Inspect the project folder to see if a ~HAP46 subfolder exists. If it exists, then the
error occurred in the final 25% of the open procedure. If it does not exist, then the error occurred in the
first 75% of the open procedure.
5. At this point, discuss the data you’ve gathered so far with Carrier Software Systems technical support.
Results of these diagnostics (including the file integrity report) can be e-mailed to
[email protected].
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 195 of 218

"Runtime Error 3343 - Unrecognizable Database Format"
Date: August 12, 1999
Revised: October 31, 2013
Summary: HAP was installed successfully and has been running smoothly for some period of time. At some point
a user chooses the Project/Open option to open a project. After a project is chosen the following error message
appears:
HAP46
Runtime Error 3343 - Unrecognizable database format in d:\path\~HAP46\HAP46inx.mdb
In this error message “d:\path” is the drive and path pointing to the folder containing the project. After the user
presses OK to clear the error message, a message will appear saying the project could not be opened.
Discussion: This error occurs when the HAP46INX.MDB database has been damaged in some way and cannot
be read by HAP. This typically happens when the computer crashes at the same time a HAP project is being
saved. Microsoft Access provides tools for repairing damaged databases. In many cases the database can be
repaired to resolve this problem.
The HAP46INX.MDB database contains index data which lists all the data items (walls, roofs, windows, spaces,
etc…) in a project and defines linkages between these items. Without this database no project data can be used.
Workaround: Use WinZIP or equivalent to produce a ZIP of all HAP files in the project folder and then e-mail this
ZIP to Software Systems in Syracuse ([email protected]). Syracuse will attempt to repair and
validate the files. Notes:
* If the user is uncertain of the project folder location, ask the user to generate the error message again.
The project path will be the portion of “d:\path\~HAPxx\HAPxxINX.mdb” prior to the “~HAPxx” (xx being the
HAP version).
* Make sure the resulting ZIP is 5.0 megabytes or less. Carrier’s e-mail system will not accept attached files
larger than 5.0 megabytes.
* Attach this ZIP to an e-mail and send it to [email protected].
If it is not possible to send the entire project contents to Syracuse, please use the following procedure to send the
HAP46INX.MDB for the project by itself:
* Locate the HAPxxINX.MDB in the project folder. If the user is uncertain of the project folder location, ask
the user to generate the error message again. The project path will be the portion of
“d:\path\~HAPxx\HAPxxINX.mdb” prior to the “~HAPxx”, where ‘xx’ is the HAP version.
* Attach this HAPxxINX.MDB file to an e-mail and send the e-mail to [email protected].

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 196 of 218

"The Field is too Small to Accept...Data..." Error
Date: February 10, 2000
Revised: Oct. 6, 2008
Summary: While saving a project the program halts and displays the following error message:
SaveProjectProperties()
The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less
data.
Workaround: Check the short date format specified in the Windows Regional Settings. If the short date format
contains more than 24 characters, it will cause this error. To inspect the short date format, use the following
procedure:
1. From the Windows desktop, press Start and choose Settings.
2. On the Settings Menu choose Control Panel.
3. In the Control Panel, double-click on the Regional Settings icon.
4. In the Regional Settings window, click on the Date tab. On this tab, inspect the “Short date style” item.
Windows offers six standard short date formats. The offerings for English (US) settings are shown below as
an example. All six of these conform to the 24-character limit imposed by Carrier software. However, users
can also create customized date formats which contain more than 24 characters, and this will lead to the “field
is too small” error message.
Standard Windows short date formats for English (US) settings:
m/d/yy Example: 2/9/00
m/d/yyyy Example: 2/9/2000
mm/dd/yy Example: 02/09/00
mm/dd/yyyy Example: 02/09/2000
yy/mm/dd Example: 00/02/09
dd-mmm-yy Example: 9-Feb-00

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 197 of 218

"Device Not Ready" Error While Opening Project
Date: January 22, 1999
Revised: Oct. 6, 2008
Summary: If you save a project to a floppy disk drive, remove the floppy disk and then try to open an existing
project that is stored on your hard disk, a “Device Not Ready - Retry?” error message will appear.
Discussion: The “Device Not Ready - Retry?” message is the first in a series of odd messages that will appear
from this point forward until you exit from HAP. When the “Device Not Ready - Retry?” error message appears, if
you replace the disk in the drive and press the OK button in the error message box, the disk drive will run for
awhile and then the existing project will be successfully opened.
If instead you do not replace the disk and press the No button in the error message box, a DOS session will be
launched and the screen will turn blue. To seasoned Windows users this is frightening because it usually
indicates a system failure. However, in this case you can press the ESC key to cancel. The DOS session will be
closed, you’ll return to HAP and your existing project will be successfully opened.
In either case you will receive the “Device Not Ready - Retry?” error message for each subsequent project you
open. For these subsequent cases, press the No button and the project will be opened successfully. In these
subsequent cases the blue DOS screen does not appear.
When you close HAP, you will also receive the “Device Not Ready - Retry” error message. When you later restart
HAP the problem will be resolved.
Workaround: If you encounter this error, we recommend exiting from HAP and then restarting. Otherwise you will
be plagued by the “Device Not Ready” error message each time you open a project.
Further, users should not store projects on floppy disks. Once several spaces and systems are defined and
design calculations are run, HAP project data will require more than 1.44 MB of disk space and this will lead to
“out of disk space” error messages. Projects should be stored on a hard disk or network drive, or on high-capacity
removable media such as ZIP drives.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 198 of 218

Error 32 While Opening a Project
Date: February 29, 2000
Revised: October 31, 2013
Summary: A user selects the Open option on the Project Menu to open an existing project. The following error
message appears:
bFileCopy()
Error 32 - The process cannot access the file because it is being used by another process.
Error Copying File
From: C:\E20-II\Projects\Sample\HAP46INX.MDB
To: C:\E20-II\Projects\Sample\~HAP46\HAP46INX.MDB
When you press OK to clear this error message, a second error message appears:
Error Opening Project
Error 5 - Access is Denied
When you press OK to clear this error message, the program returns to the main program window. The project
has not been opened.
Discussion: This error has been encountered once by someone running HAP v4.03 on a Windows 98 computer.
We suspect the error can occur using any version of Windows, and using any version of HAP since v4.0.
The problem is due to corrupted data in the HAP46INX.MDB database file contained in the project. Fortunately
the corrupted data can be removed using database repair software (see Workaround below).
Prior to the error message appearing, the user may observe peculiar program behavior. Examples include:
* Inability to save individual data items. For example, when saving space data, the user received a
message:
Could not save the space.

The most likely reason for this type of failure is a name conflict with an existing space. Try changing its name.

However, there is no name conflict so the space data cannot be saved.

* Calculations would not run. The user selected a system and chose reports. Calculations started, but then
suddenly halted and returned the user to the main program window. No error message appeared.
Currently we do not know how the database file becomes corrupted.
Workaround: Archive the project in which the problem occurs and send it via e-mail to
[email protected]. We will run database software to repair and compact the HAP46INX.MDB
database, make a new archive file and return it to the sender.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 199 of 218

RegisterAppData While Saving a Project
Date: March 23, 2000
Revised: Oct. 6, 2008
Summary: When a user chooses the Save option on the Project Menu the following error message appears:
RegisterAppData()
The changes you requested to the table were not successful because they would create duplicate values in the
index, primary key or relationship. Change the data field or fields that contain duplicate data, remove the index
or redefine the index to permit duplicate entries and try again.
As a result of the error message, the project cannot be saved. This error can also occur when using the Save As
option.
Discussion: This error has been encountered once so far and it was due to a corrupted copy of the
PRJXY000.MDB file. This file contains an index of all projects. When you save a project, an entry in the database
needs to be updated. Because the file is corrupt, the entry cannot be updated and the error occurs.
Workaround: The first step is for Syracuse to confirm that the PRJXY000.MDB file is corrupt. Use WinZIP or
equivalent to ZIP this file (found in \E20-II\ENVIRO) and then send to [email protected] by e-
mail.
If we confirm that the database is corrupted, there is a chance Syracuse can repair the file and send it back to
eliminate the problem.
If the file cannot be repaired, the user needs to use the following procedure to create a new, clean copy of
PRJXY000.MDB (or equivalent on a network/private configuration):
1. Rename the corrupted copy of PRJXY000.MDB to PRJXY000.BAK
2. Start HAP. The program will go directly to the main window and will create a new, untitled project.
3. Save the untitled project, naming it TEMP or JUNK. This is a temporary measure.
4. Choose the Open option on the Project Menu.
5. In the Open Project window press the Find button.
6. In the Find window, make sure the search path is correct. For example if all your projects were stored in
D:\E20-II\Projects, the search path should be D:\E20-II\Projects. Once the search path is correct press the
Search button.
7. Projects found by the search will be listed in the Search Results box. Place a check mark next to each project
you want to add to your index. When finished, press OK.
8. You will then be returned to the Open Project Window and will see all your projects listed in the index. Any
project can then be opened.
9. Finally, erase the temporary project saved in step 3.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 200 of 218

"Runtime Error 3024" While Opening a Project
Date: February 12, 2002
Revised: Jan. 25, 2016
Summary: When a user attempts to open a project the following error message appears:
Runtime Error 3024: Couldn't find file path\filename.
where path\filename is the path and name of the file that could not be found.
Discussion. When this has happens it is typically the HAPxxINX.MDB file that is missing (or damaged). This file
exists in the project folder, but might not be copied to the working project folder when a project is opened.
Information in the E20XYCFG.MDB database informs HAP which files must be copied to the working project
folder each time a project is opened. Somehow information has been removed from the E20XYCFG.MDB and the
result is that HAPxxINX.MDB is no longer moved to the working project folder.
Workaround. Make an archive of the project and send it to [email protected]. Syracuse will
inspect the project, attempt to correct it, and send it back.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 201 of 218

"Database has Reached its Maximum Size" Error While Opening a Project
Date: February 12, 2002
Revised: Oct. 6, 2008
Summary: HAP has been installed on a network. The software has worked smoothly for some period of time.
One day all users begin encountering the following error message when attempting to open a project:
Database has reached its maximum size.
This error prevents all network users from opening projects.
Discussion. In the single case where this happened the user determined that the PRJXY000.MDB file (found in
\E20-II\ENVIRO) had a file size of 1 gigabyte (1,048,576 kB). 1 gigabyte is the maximum size for database files of
this type. There is no reason this database file should be so large.
We obtained a copy of the file. Inspection showed that the database was corrupted. We were able to extract
information from the database and transfer it to a new, clean copy of the database. At the end of this work the file
size was 128 kB. We could find no evidence in the original file that it had held massive amounts of data. It
appears that some event on the network corrupted the file and caused its size to expand to 1 gigabyte. There was
no indication what event caused the damage to occur. Two possibilities are a network transmission problem or a
network crash occurring while the software was writing to the database file.
Workaround. When this error occurs use Windows Explorer to inspect the file sizes of the four databases
involved in opening a project:
\E20-II\E20XYCFG.MDB
\E20-II\ENVIRO\PRJXY000.MDB
HAPxxINX.MDB (found in the project folder for the project being opened)
Project.MDB (also found in the project folder for the project being opened)

If any of these files are unusually large (larger than 5,000 kB) contact Carrier Software Systems technical support
to arrange for inspection of the file ([email protected] or 800-253-1794).

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 202 of 218

"Type Mismatch" Error While Retrieving Archive Data
Date: 6/18/2002
Revised: Oct. 6, 2008
Summary: A user attempts to retrieve data from a HAP v4.3 archive file. After choosing the file from the Retrieve
dialog, the process immediately halts with the following error message:
GetProjectFileSpecFromE3PFile()
Type Mismatch
No data is retrieved.
Workaround: The archive file must be sent to Carrier in Syracuse for rehabilitation. E-mail the E3A archive file to
[email protected] with full description of the steps leading up to the error and the error message
itself.
Discussion: This error only occurs when an archive file is created using one language edition of Windows and is
then retrieved using a different language edition of Windows.
Example: An engineering firm has a branch office in Lima, Peru which creates an archive file on a computer
running a Spanish edition of Windows. The branch office sends the archive by e-mail to their home office in the
United States where an attempt to retrieve the data is made using a computer running the English edition of
Windows. The difference in editions – Spanish versus English – causes the problem.
Specifically, there is control information in the Project.E3P file (one of the components of the archive) which is
stored as “True” or “False” text strings. When data is created on a computer using Spanish Windows, the
computer automatically writes the word “Verdadero” rather than “True”. As long as the archive is used on a
computer using Spanish Windows, no problem occurs. If retrieval is attempted on a computer running any other
language version of Windows, the computer will not be able to interpret the meaning of “Verdadero” and the “Type
Mismatch” error occurs.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 203 of 218

Error 33 While Saving a Project
Date: November 18, 2002
Revised: Oct. 6, 2008
Summary: While saving a new project for the first time the program halts and displays the following error
message:
WritePPS()
Unable to write string [Project Name = name] to file d:\path\project.e3p
Error 33 – The process cannot access the file because another process has locked a portion of the file.
The project is not saved.
Discussion: We have only one report of an error like this. The customer was running a network installation of
HAP and saving data to the network drive. If data was saved to a local drive (C: for example), the error did not
occur. The conclusion was that some aspect of the network operating system was interfering with writing of the
PROJECT.E3P file.
PROJECT.E3P is written using procedures in the KERNEL32.DLL file. This is one of the core files for the
Windows operating system. It seems unlikely that KERNEL32.DLL is damaged. The more likely possibility is that
the network operating environment conflicts with the commands KERNEL32.DLL is trying to execute. It is possible
that network cache settings are contributing to the problem. The customer did not know how to determine whether
this was the case so a cause could not be determined with certainty.
Workaround: At this time the only known solution is to save the project to a different drive. In the original report
of this problem, the customer wound up saving projects to a shared local drive. That way all network users could
share data and the problem saving data to the network drive was avoided.
Note: If this problem surfaces again, please contact Syracuse so we can get details and try to track this problem
further.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 204 of 218

 “Could Not Lock File" Error 3050 When Opening Project
Date: January 23, 2003
Revised: July 7, 2014
Summary: The program halts with the following error message (or similar):

GetDataFromJobTable()
Error 3050
Could not lock file.
(Note that the specifics of this message will vary depending on the exact circumstances of the error.)
Discussion: This error often occurs when opening a project, or during program startup. When it occurs on
startup, the program may be unusually slow. (The program title screen appears immediately after clicking on the
icon or start item, but takes 1-2 minutes for the OK button on the title screen to be enabled.)
This error can also occur at other times, since it involves a problem opening database files which are used for
many program functions.
This error will occur on computers on which the user does not have full file access privileges to the E20-II folder
and its subfolders. The Windows operating system permits multiple “user profiles” to be established on a single
workstation. The file access rights of each “user profile” can be controlled and limited. If a user is running with a
“user profile” that does not provide read, write, create and destroy file privileges (or the equivalent) to the \E20-II
folder and/or its subfolders, HAP will experience the problems listed above.
To start and to open projects, HAP must open database files in the \E20-II folder and its subfolders. Working with
a database file requires that a “lock” file be created. If the user does not have create and write privileges to the
folder containing the database, errors will occur. If the user does not have “destroy” privileges, the database
cannot be closed afterwards.
Resolution:
1. Save the project and exit HAP.
2. Grant full file privileges to the \E20-II folder and all its subfolders.
3. In the \E20-II\HAP4?\CODE folder look to see if you have any .LDB files. If so erase them.
4. In the project folder, look to see if you have any .LDB files. If so erase them.
5. In the project folder make sure there is not a ~HAP4? folder. If there is, that indicates the project didn’t close
correctly. See if you can manually erase that folder.
6. Run HAP and try the operation which produced the error again.
Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 205 of 218

3.7 Common Errors – Networks
How to Convert from Standalone to Network Shared
Date: November 29, 2000
Revised: January 6, 2015
Summary: Originally HAP is installed on the local hard disk for each program user. Later a user decides they
would like to install HAP on the network server to permit data sharing.
Workaround: The following steps are required.
Note: If Carrier 32-bit Windows programs in addition to HAP need to be converted to "Network - All Data Shared",
then the data archive, data retrieval, program uninstall and program reinstall steps below need to be repeated for
each Carrier 32-bit Windows program, not just HAP.
1. Have each user archive all of his or her existing projects.
 First use the Open option on the Project Menu to open a project.
 Then use the Archive option on the Project Menu to archive the project. You will be asked to specify a
folder location and name for the archive file.
Repeat these two steps for each project.
Archiving combines and compresses all data files comprising a project. This creates a backup file for the
project. We recommend placing all archive files in a common location on the network. Later in the procedure
these archives will be restored.
2. After a user has archived all his or her projects, each project can be deleted to free up disk space. Use the
Delete option on the Project Menu to do this.
3. Next, uninstall HAP from each workstation:
 From the Windows desktop press Start, choose Settings and then choose Control Panel.
 In the Control Panel, double-click on the “Add/Remove Programs” icon.
 In the Add/Remove Programs dialog click on “Hourly Analysis Program v4.x” and then press the
“Add/Remove” button.
 Wait for the first uninstall dialog to appear. On this dialog choose the “Automatic” option. Then press
Next, and then press Finish. HAP will be uninstalled.
 If no other Carrier E-CAT or E20-II Windows programs are installed on the workstation, you can also
uninstall Configuration Services. Therefore, once you are returned to the Add/Remove Dialog, click on
the “E-CAT / E20-II Configuration Services” item and then press the “Add/Remove” button.
 Wait for the first uninstall dialog to appear. On this dialog choose the “Automatic” option. Then press
Next, and then press Finish. The Configuration Services software will be uninstalled.
4. Install HAP to the network server from each workstation that must have access to the program. The
procedure below must be repeated on each workstation because during installation certain software
components (DLLs, OCXs) must be installed to the local C: drive, while the majority of the software is
installed to the network server.
 Copy the HAP setup program to the workstation.
 Run the setup program.
 As the installation proceeds, specify the server drive as the destination drive for installation.
5. Restore all the projects archived in step #1. After starting HAP, the following steps need to be repeated for
each archived project:
 Choose New on the Project Menu to create a new, untitled project.
 Choose "Retrieve HAP v4.x Data" on the Project Menu. In the Retrieve dialog choose the archive file to
be retrieved. When archive file details are shown, press the Retrieve button to proceed.
 After you are returned to the HAP main program window, choose the Save option on the Project Menu.
You will be asked to name the project (the default will be the project name from the archive file), and you
will be asked to specify a folder where project files will be stored.

HAP Support Notes rev. 501_05 -- Page 206 of 218

6. HAP is now installed and configured for network operation. For further information on installing, running and
maintaining the software on a network, please refer to the Network Primer document on the Carrier website.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 207 of 218

How to Convert From Network Shared to Standalone
Date: July 19, 2013
Revised: n/a
Summary: A user who ordinarily uses HAP in a network configuration has a need to run HAP in a standalone
configuration. For instance, they may need to take a laptop to a customer site and operate the software without
having access to their office network.
Workaround: The following steps are required. There are two scenarios:

1. Computer not yet set up on network

XBuilder and HAP can be installed as normal. The projects list that appears when the user opens a project is a
local list that is specific to their computer. The user can add all the projects stored on the network to this local list
using the Find feature on the Open Project window. The network projects do not show up automatically.

2. Computer has already been set up on network

If X Builder and HAP are installed to the network drive, then the projects list that appears when the user opens a
project is a shared list on the network drive. As users add projects in a network install, the project is added to the
network project list and all network users automatically can see it – they do not need to do anything to see the
network projects.
To reconfigure X Builder and HAP to use the local laptop drive when it was previously installed to the network, the
following steps are needed:
1. X Builder only allows itself to be installed one place at a time. The fastest way to disable this and allow it
to be reinstalled to the laptop is to edit the Windows registry as follows. Note: You will need administrative
rights to do this. May be best to get the user’s computer administrator to do this if uncertain about how to
edit the registry.
a. Start the registry editor.
b. Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Carrier > XBF11 (see figure below)

HAP Support Notes rev. 501_05 -- Page 208 of 218

 c. Erase the XBF11 node and all its sub items.
d. Exit the registry editor.
2. Install X Builder specifying the local laptop drive as the destination.
3. Install HAP specifying the local laptop drive as the destination.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 209 of 218

Configuring HAP for Dual Mode (Standalone and Network) Operation
Date: January 7, 2015
Situation: User requires a procedure to install HAP to local drive for use away from office and then still use the
network version when at the office.
Procedure: HAP does not support this scenario directly, but it can be done by using the How to Convert from
Standalone to Network Shared and How to Convert From Network Shared to Standalone procedures, with some
caveats.
To move to standalone operation:
1. Follow the How to Convert From Network Shared to Standalone procedure.
2. Launch HAP on your local computer and connect your projects
a. Start HAP
b. The program will take you directly to the main window.
c. Choose the Save option on the Project Menu to save the empty project as “TEMP” or “JUNK”
d. Choose the Open option on the Project Menu. Click the Find button on the right.

e. On the Find All Projects window, click Change to specify a search path that points to the location
of your network projects.
i. For example, if you store your projects on H: drive and you use the standard default
location that HAP uses, you would choose “H:\E20-II\Projects” as the search path.
ii. On the other hand, if you and colleagues store HAP projects in many different locations
on the network drive, you may need to specify a different search path like “H:\” so it will
search the entire network drive. After specifying the search path, press the Search
button.
f. After searching, the software will show a list of all the projects it found. Select all the projects for
addition to your project list.
g. Finally Press Add to add the selected projects to your list. You’ll be returned to the Open Project
window and will see a list of all the projects.

HAP Support Notes rev. 501_05 -- Page 210 of 218

 3. You’re now ready to run with a local copy of the software.
4. Caveats:
a. All your projects are currently on the network. If you disconnect your laptop you won’t be able to
access them. If you need to access projects when disconnected, you’ll need to save a copy to
your local hard disk, or make an archive and take it with you.
b. Over time you may wind up with a mix of projects you’ve saved to your local drive and projects
saved to the network drive. When disconnected you’ll only be able to access files on the local
drive.
c. If you have colleagues in the office who are creating projects on the network, and you want access
to these projects, you’ll periodically need to run the Find procedure to add these projects to your
project list. Because you’re running HAP locally, you have your own personal project list and it
won’t update automatically when one of your colleagues creates a new project.

To move to network operation:

1. Follow the How to Convert from Standalone to Network Shared procedure.

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 211 of 218

How to Migrate Projects to a New Data Server
Date: August 16, 2014
Situation: HAP and other Carrier projects are stored on a network server so that all engineers in the office can
access the data in one central location. The current network server containing the project data is being taken out
of service and all data on the server is being moved to a new server. For this situation the steps shown in the
Procedure section below need to be performed to make sure users can access project data once the new server
is turned on and the old server is turned off.
Note: The procedure below only covers migration of project data. If HAP is also installed on the same server, it
will need to be moved to the new server. This is covered in a separate procedure.
Basic Concepts: Its useful to understand the following basic software data storage concepts when applying this
workaround:
1. A “project” consists of a group of files in a single folder. The files function as a matched set. Therefore, its
important to keep all files in a project folder together. If any file is omitted or erased, its possible the project
will become unusable.
2. Carrier software maintains a project index which lists all the projects you’ve created or worked with and their
drive and path location. With this index, you can simply select a project from a pick list and the software
knows where to find the data. During a server migration, this drive and path information becomes invalid and
needs to be re-created. The Carrier software contains features for automating this process – that is
reconnecting projects to the index after project folders are moved to a new location.
Procedure:
1. Copy all the Carrier project folders from the old server and paste onto the new server.
Notes:
a. If your engineers were using the default location for all their projects, all projects will be found in sub
folders beneath \E20-II\Projects. In this case, copy all the subfolders beneath Projects and paste under
an \E20-II\Projects folder on the new server.
b. On the other hand, if engineers were choosing different locations for their projects, then those project
folders need to be located and then moved to the new server.
c. A “project” is a group of files in a single folder. Therefore, its critical to copy the complete folder to keep
the project intact. If any files in the folder are omitted, the project may become unusable.
2. Rename the PRJXY000.MDB file to PRJXY000.BAK
Notes:
a. If your engineers are running a network copy of HAP, go to the \E20-II\ENVIRO folder on the server drive
where HAP is installed, and rename the PRJXY000.MDB file in this folder to PRJXY000.BAK.
b. If your engineers are running local copies of HAP (HAP installed on their laptop or desktop computer),
then on each workstation the PRJXY000.MDB file in \E20-II\ENVIRO needs to be renamed to
PRJXY000.BAK
c. The PRJXY000.MDB contains an index of projects – the name of the project and the drive and path
location of the project folder. Since all the projects have been moved to a different server, the drive and
path location information is no longer valid. We’ll rebuild this information in step 3. But first we need to
reset this project index so its empty and the software can build a new set of project index data. After
renaming the file to .BAK, the next time you launch the software it will create a new index file and then we
can repopulate it with the new project locations. If this step is not done, then the software will keep
pointing to the projects on the old server. When the old server is turned off, you’ll begin getting “network
path not found errors” as a result.
3. Regenerate the project index data.
Steps:
a. Start Carrier Electronic Catalog – From the windows desktop press Start and choose All Programs >
Carrier E-CAT and E20-II Programs > Carrier Electronic Catalog. Note that Electronic Catalog contains
features for finding and reconnecting projects of any type. You could run HAP and it offers a similar
feature, but it will only reconnect projects containing HAP data. Because its possible projects contain

HAP Support Notes rev. 501_05 -- Page 212 of 218

 data from HAP as well as other Carrier programs, using Carrie Electronic Catalog is safest as it will be
able to reconnect all projects, regardless of their content.
b. From the main window choose the “Open File” option on the File Menu.
c. In the Open Project window click the “Find” button on the right (Figure 1).
d. In the Find All Projects window (Figure 2) click the “Change” button in the “Search Path” section. Choose
a new search path. For example, if the new server is designated as K: drive, you could choose the root of
K: as the search path. The software will then search all folders on K: for projects. While this guarantees
you catch all projects where ever they are located, if K: is large the search could take a long time. On the
other hand, if all the projects are together in one location like K:\E20-II\Projects, you could specify that
location for a faster search. Note that you want to specify a search path that is at least 1 folder level
above the individual project folders.
e. On the Find All Projects window (Figure 2) press the Search button. The software will search for all
Carrier projects and then display them in the Search Results section (Figure 3).
f. When the search is finished, check the box for each found project you want to reconnect to your
index. Likely you want to check all the boxes. If so, press the “Select All” button on the right to do this.
(Figure 3)
g. Once the project boxes are marked, press the Add button on the right. All of these projects with their new
drive and path information will be added to your project index. The software will automatically take you
back to the Open Project window and show you the list of connected projects (Figure 4).
h. Exit Carrier Electronic Catalog.
NOTE – If your engineers are using a network copy of HAP (HAP installed on the network), then steps 3a –
3h above need to be done once because there is one project index file on the server shared by all
users. On the other hand, if your engineers are using local installs (one per laptop or desktop
workstation), then the steps 3a – 3h above need to be repeated on each workstation. In the latter case
each workstation has its own project index and each needs to be regenerated separately.
4. Run HAP and verify you can access the projects on the new server.

HAP Support Notes rev. 501_05 -- Page 213 of 218

Figure 1. Open Project Window

Figure 2. Find All Projects Window – Before Searching

HAP Support Notes rev. 501_05 -- Page 214 of 218

Figure 3. Find All Projects Window – After Searching

HAP Support Notes rev. 501_05 -- Page 215 of 218

Figure 4. Open Project Window – After Searching and Connecting Projects

Back to Table of Contents

HAP Support Notes rev. 501_05 -- Page 216 of 218

3.8 Common Requests and Information
Status of ASHRAE Std. 140 Documentation & EPACT Submission
Date: May 18, 2015
Revised: Dec 13, 2016
This support note documents the current status of ASHRAE Std. 140 tests and documentation for HAP,
submission to DOE for EPACT, and some background information which may be useful to help understand how
Std. 140 is used, and to provide information to customers.

HAP Testing Status:

Each release of HAP needs to be evaluated against the Std. 140 test cases individually.
Also note that there is a distinction between running the Std. 140 tests and submitting a version of HAP to DOE
for record keeping purposes related to tax incentives. This has been done for some versions, and not others. See
discussion below for more information.
The following table summarizes current status in these areas:

Software Version Std. 140 Test Results DOE Submission for EPACT
HAP 5.01 Included with program Completed Dec 8, 2016
HAP 5.00 Included with program Completed Dec 8, 2016
HAP 4.91 Included with program Completed November 14, 2015 (2)
HAP 4.90 (1) Completed November 14, 2015 (2)
HAP 4.80 Not available Submission not done
HAP 4.70 (1) Submission not done
HAP 4.61 (1) Submission not done
HAP 4.60 (1) Submission not done
HAP 4.51 (1) Submission not done
HAP 4.50 (1) Submitted July 26, 2011
HAP 4.41 Not available Submitted April 10, 2009
HAP 4.40 Not available Submitted April 10, 2009
HAP 4.34 (1) Submitted August 10, 2007
HAP 4.31 (1) Submitted August 16, 2006
HAP 4.30 (1) Unknown
HAP 4.22 (1) Unknown
HAP 4.21 (1) Unknown
HAP 4.20 (1) Unknown
HAP 4.11 and earlier Not available Unknown
(1) Available on request from Syracuse.
(2) Listed on federal government’s “Qualified Software for Calculation Commercial Building Tax Deductions”
web site: http://energy.gov/eere/buildings/qualified-software-calculating-commercial-building-tax-
deductions

IRS Certification Background:

1. Congress passed legislation to include an “Energy Efficient Commercial Building Tax Deduction” in the
Internal Revenue Service tax code. This deduction is described in IRS Code 179D.

HAP Support Notes rev. 501_05 -- Page 217 of 218

 Reference: http://www.gpo.gov/fdsys/pkg/USCODE-2010-title26/pdf/USCODE-2010-title26-subtitleA-chap1-
subchapB-partVI-sec179D.pdf

2. The IRS provided details for qualifying for the tax deduction in two Notices in 2006 and 2008. These notices
describe a procedure for using a building simulation software tool to predict the energy cost of a reference
baseline building and the proposed building (including energy conservation measures). If the cost savings of
proposed versus baseline exceeds a certain threshold, the building owner qualifies for the tax deduction.

Reference: IRS Notice 2006-52 : http://www.irs.gov/irb/2006-26_IRB/ar11.html

Reference: IRS Notice 2008-40 : http://www.irs.gov/irb/2008-14_IRB/ar12.html

3. It was delegated to the Department of Energy (DOE) to establish rules for certifying building simulation
software tools that can be used to perform the energy cost predictions. Those rules include testing the
software according to ASHRAE Standard 140 – Standard Method of Test for the Evaluation of Building
Energy Analysis Computer Programs, documenting test results and attesting to technical features of the
software.

Reference: http://energy.gov/sites/prod/files/2013/12/f5/qualified_software.pdf

Submission to DOE vs. Public Distribution:

4. After we submit the certification package (certification letter, test results, other information), the DOE will
approve the submission and then list the new HAP version on their web page of qualified software. As part of
that web posting, they will also post an excerpt of our letter attesting to technical features.

References:
Qualified software website: http://energy.gov/eere/buildings/qualified-software-calculating-commercial-
building-tax-deductions

Sample posting of certification letter for HAP v4.50: http://energy.gov/sites/prod/files/2013/12/f5/qs_hap_v4-

50.pdf

5. We also produce a short report that describes the test results in plain English and provide this to our software
customers. The documentation submitted to DOE is very technical and hard for a layman to
understand. This plain English report helps to communicate the results and their significance to our
customers who do not necessarily understand the arcane testing procedures.

One final note: Congress has reauthorized the 179D tax deduction through the 2014 tax year. Our customers
need certification that current versions of HAP are valid for 179D so they can perform the tax deduction
analysis for building owners still filing returns for the 2014 tax year. Congress is currently [Dec 2016]
considering whether to extend 179D to 2017 or later tax years.

Further Information: DOE FAQ sheet:

http://apps1.eere.energy.gov/buildings/publications/pdfs/corporate/commercial_tax_179d_faqs.pdf

HAP Support Notes rev. 501_05 -- Page 218 of 218