[Equest-users] eQuest installation Error

Brian Fountain bfountain at greensim.com
Sun Mar 22 13:58:15 PDT 2020 

Kathryn,

I second Nick's observation about opening in DOE-2.3 instead of 2.2.  
You can set the version of DOE either within eQUEST in the Tools menu or 
by changing the DOE2Version keyword in eQUEST.ini in your eQUEST data 
directory.

/        [preferences]//
//        ; SAC 11/16/10 - added this new entry that controls toggle of 
DOE2 Version, DOE2Version = 0 for DOE 2.2,=1 for DOE Refrigeration,=2 
for DOE 2.3//
//        DOE2Version=2//

/If a file is created in 2.3, there will be brackets around these keywords:

    PEOPLE-SCHEDULE  = ( "E1GFBldg Occup Sch" )
    AREA/PERSON      = ( 400 )
    PEOPLE-HG-LAT    = ( 200 )
    PEOPLE-HG-SENS   = ( 250 )

In 2.2, there are no parentheses for those keywords.  That is likely the 
source of the error.  2.2 is seeing the brackets around the schedule 
U-name and giving up.

Regards,

Brian
//
On 22/03/2020 3:28 p.m., Kathryn Kerns via Equest-users wrote:
>
> Nick I tried opening the previously created eQuest.7175 files I 
> attached with eQuest 3.65 and that created the same error.  There 
> should not be anything wrong with the schedule name. I am wondering if 
> the eQuest.7175 msi file might not be executing properly. I wonder if 
> this is the result of not having correct admin permissions on the new 
> laptop?
>
> I will talk it over with the tech staff that gave me the laptop on 
> Monday. Has anyone had similar problems with the eQuest3.65.7175 
> program downloading?
>
> *From:* Nicholas Caton <Nicholas.Caton at se.com>
> *Sent:* Sunday, March 22, 2020 12:17 PM
> *To:* Kathryn Kerns <kathryn.kerns at bceengineers.com>; 
> equest-users at onebuilding.org
> *Subject:* RE: eQuest installation Error
>
> Hi Kathryn,
>
> I initially replicated your error on trying to open, then did 2 things 
> (you may only need to do one) and it opened just fine:
>
>  1. Observing the INP file didn’t seem to be off after investigating
>     the BDL error, I renamed all instances of the offending schedule
>     just to be safe
>  2. I tried switching my eQuest installation to open in doe23 from doe22.
>
> One or both of those did the trick!  I would try #2 first as the 
> easiest/most likely remedy.
>
> ~Nick
>
> *Nick Caton, P.E., BEMP*
>
> Senior Energy Engineer
>
> Energy and Sustainability Services
> Energy Performance Contracting
>
> 	
>
> D
> M
> E
>
> 	
>
> 913 . 564 . 6361
>
> 785 . 410 . 3317
>
> _nicholas.caton at se.com <mailto:nicholas.caton at se.com>_
>
> 	
>
> 15200 Santa Fe Trail Drive
> Suite 204
> Lenexa, KS 66219
>
> *From:* Equest-users <equest-users-bounces at lists.onebuilding.org 
> <mailto:equest-users-bounces at lists.onebuilding.org>> *On Behalf Of 
> *Kathryn Kerns via Equest-users
> *Sent:* Sunday, March 22, 2020 2:02 PM
> *To:* equest-users at onebuilding.org <mailto:equest-users at onebuilding.org>
> *Subject:* [Equest-users] FW: eQuest installation Error
>
> [External email: Use caution with links and attachments]
>
> ------------------------------------------------------------------------
>
> Ok, it appears I sent this e-mail to the incorrect address. I still 
> need some help. The original attached files were created with eQuest 
> 3.65-7175 on a laptop with Windows 10. I now have a new laptop with 
> Windows 10 which has a recently downloaded version of eQuest 
> 3.65-7175. This new laptop and recently downloaded version of eQuest 
> 3.65-7175 will not run the previously created eQuest 3.65-7175 
> projects. I cannot figure it out except that the newer eQuest 
> 3.65-7175 downloaded program appears to be functioning like the older 
> eQuest 3.65 and saves files to the older eQuest 3.65 file locations. 
> It does not make any sense. The newer laptop is an HP. The older 
> laptop was an ACER. Anybody know what is going on?
>
> *From:* Kathryn Kerns
> *Sent:* Friday, March 20, 2020 3:27 PM
> *To:* Equest-users <equest-users-bounces at lists.onebuilding.org 
> <mailto:equest-users-bounces at lists.onebuilding.org>>
> *Cc:* jglazer at gard.com <mailto:jglazer at gard.com>; Jeff.Hirsch at DOE2.com 
> <mailto:Jeff.Hirsch at DOE2.com>
> *Subject:* FW: eQuest installation Error
>
> Forgot to attach the BDL
>
> *From:* Kathryn Kerns
> *Sent:* Friday, March 20, 2020 2:58 PM
> *To:* Equest-users <equest-users-bounces at lists.onebuilding.org 
> <mailto:equest-users-bounces at lists.onebuilding.org>>
> *Cc:* jglazer at gard.com <mailto:jglazer at gard.com>; Jeff.Hirsch at DOE2.com 
> <mailto:Jeff.Hirsch at DOE2.com>; ncholas.caton at se.com 
> <mailto:ncholas.caton at se.com>; James Moler 
> <James.Moler at bceengineers.com <mailto:James.Moler at bceengineers.com>>
> *Subject:* eQuest installation Error
>
> Everyone I have been using eQuest for years, put for some reason I 
> can’t get eQuest 3.65.7175 loaded onto a new laptop to open previously 
> created eQuest models  also created with eQuest 3.65.7175 on another 
> laptop. The error I get is:
>
> Doesn’t matter which previously created eQuest 3.65.7175 project I 
> pick, I get the same type of error. I created a new project, Project 
> 1, and it seems to work although the program saved it to eQuest 3.65 
> Projects instead of eQuest D23 projects.
>
> Old laptop had Windows 10 and new laptop has Windows 10. Anybody have 
> some suggestions? Never had a problem downloading and using eQuest 
> before. Attached is example *.pd2 and *.inp that generates error.
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> ______________________________________________________________________
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
> 	Virus-free. www.avg.com 
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> _______________________________________________
> Equest-users mailing list
> http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
> To unsubscribe from this mailing list send  a blank message to EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20200322/a3e8096e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 105977 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20200322/a3e8096e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 235323 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20200322/a3e8096e/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 1794 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20200322/a3e8096e/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 8477 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20200322/a3e8096e/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 74806 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20200322/a3e8096e/attachment-0003.png>

More information about the Equest-users mailing list