<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Vorformatiert Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Sprechblasentext Zchn";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;
mso-fareast-language:EN-US;}
span.HTMLVorformatiertZchn
{mso-style-name:"HTML Vorformatiert Zchn";
mso-style-priority:99;
mso-style-link:"HTML Vorformatiert";
font-family:"Courier New";
mso-fareast-language:DE;}
span.E-MailFormatvorlage19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.E-MailFormatvorlage20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.SprechblasentextZchn
{mso-style-name:"Sprechblasentext Zchn";
mso-style-priority:99;
mso-style-link:Sprechblasentext;
font-family:"Tahoma","sans-serif";
color:black;
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=DE link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Hi David,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>thank you very much for your answer. I did several more test simulations on different PCs.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>The error message that I mentioned occurred due to strange simulation results on some PCs but is located at a forcing function (Type 14). You are right, if I turn the debug mode flag off, the simulation will finish (this flag was equally “on” at each PC) but of course the strange results persist. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I checked the content of the release folder, but the content was also the same on each PC.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>The problem that I realized is that the simulation only works if I run the simulation as network administrator, if I do that as a local PC administrator the problems will occur. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I have never had such a problem concerning user permissions and it always worked well with local PC administration permissions (for reading, writing and installation).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Have you ever heard about it? I am really not sure if it is a problem in our network or if it is a windows permission problem.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Kind regards<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Tobias<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span lang=EN-US style='color:#1F497D;mso-fareast-language:DE'>Dipl.-Ing. </span><span style='color:#1F497D;mso-fareast-language:DE'>Tobias Henzler<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:DE'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:DE'>University of Stuttgart<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:DE'>Institut für Gebäudeenergetik (IGE)<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:DE'>Pfaffenwaldring 35<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:DE'>70569 Stuttgart<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D;mso-fareast-language:DE'>Germany<o:p></o:p></span></p></div><p class=MsoNormal><span style='color:#1F497D'>Mailto: tobias.henzler at ige.uni-stuttgart.de<o:p></o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:DE'>Von:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:DE'> David BRADLEY [<a href="mailto:d.bradley@tess-inc.com">mailto:d.bradley@tess-inc.com</a>] <br><b>Gesendet:</b> Mittwoch, 8. </span><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:DE'>Januar 2014 23:09<br><b>An:</b> TRNSYS users mailing list at the Solar Energy Lab, UW-Madison; </span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:DE'><a href="mailto:tobias.henzler@ige.uni-stuttgart.de"><span lang=EN-US>tobias.henzler@ige.uni-stuttgart.de</span></a></span><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext;mso-fareast-language:DE'><br><b>Betreff:</b> Re: [TRNSYS-users] Problem with DLL on several computers<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span lang=EN-US>Tobias,<br> I would be very surprised if this error had anything to do with the operating system. In a Trnsys16 component, you had to reserve the number of outputs that you wanted your Type to use and you did so by a command that looked something like:<br><br>INFO(6) = 12<br><br>if you wanted to reserve 12 outputs. The error you are getting is that some component is reserving a certain number of outputs for itself and then is setting an output that is outside of the reserved range. The following would cause the error:<br><br>INFO(6) = 12<br>...<br>OUT(14) = someVariable<br><br>The error message should mention the Unit and Type number of the component that is causing the problem. Please send me that information and I may be able to help you look a bit further.<br><br>I have two guesses as to why the error occurs on some computers but not on others. First, the check that is generating the error can be turned off by changing the "debug mode" flag in the simulation control cards. In the Studio, open the control cards tool (where you set the simulation start and stop times) and scroll down to the field that says "debug mode" Debug mode may be turned off on one computer but not the other. Second (more likely) there is another DLL in the ..\TrnsysXX\UserLib\DebugDLLs\ or ..\TrnsysXX\UserLib\ReleaseDLLs\ directory of one of the computers but not the other. <br>Kind regards,<br> David<br><br><br><br><o:p></o:p></span></p><div><p class=MsoNormal><span lang=EN-US>On 1/8/2014 09:10, Tobias Henzler wrote:<o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span lang=EN-US>Dear TRNSYS-Users,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>I am currently working on several type programming projects with FORTRAN in CVF. It usually works fine and there is no problem in using it with different versions (TRNSYS 16_1, 17_0) and on several PCs.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Now a strange error occurred with one type as it does not work equally on different PCs. The DLL is of course the same, and the configurations are also equal.<o:p></o:p></span></p><pre><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>In that special case, it works on XP-Mode properly meanwhile on Win7 the results differ extremely and an error occurs (TRNSYS Message 427). The problem exists on some PCs with Win7, but works on others with Win7:</span><span lang=EN-US><o:p></o:p></span></pre><p class=MsoNormal><span lang=EN-US style='font-family:"Arial","sans-serif";mso-fareast-language:DE'> </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt'> "An OUTPUT from the specified component model has been written to the </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt'>global OUT array in a location beyond the allocated number of outputs </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt'>from this model. Please check the component carefully to insure that </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt'>INFO(6) is set correctly. The simulation has been aborted to avoid </span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:10.0pt'>problems caused by over-writing the outputs from other component models"</span><span lang=EN-US><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>I do not think that it is a problem of WinXP/Win7. In my opinion it might also be a problem with missing components that are supposed to be located in the system folder.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Has anyone ever had a problem with a DLL not working equally on different PCs?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Best regards and thanks in advance<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>Tobias<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>University of Stuttgart<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US>mailto: Tobias.henzler at ige.uni-stuttgart.de<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-language:DE'><br><br><br><o:p></o:p></span></p><pre><span lang=EN-US>_______________________________________________<o:p></o:p></span></pre><pre><span lang=EN-US>TRNSYS-users mailing list<o:p></o:p></span></pre><pre><a href="mailto:TRNSYS-users@cae.wisc.edu"><span lang=EN-US>TRNSYS-users@cae.wisc.edu</span></a><span lang=EN-US><o:p></o:p></span></pre><pre><a href="https://mailman.cae.wisc.edu/listinfo/trnsys-users"><span lang=EN-US>https://mailman.cae.wisc.edu/listinfo/trnsys-users</span></a><span lang=EN-US><o:p></o:p></span></pre></blockquote><p class=MsoNormal><span lang=EN-US style='font-size:12.0pt;font-family:"Times New Roman","serif";mso-fareast-language:DE'><br><br><o:p></o:p></span></p><pre><span lang=EN-US>-- <o:p></o:p></span></pre><pre><span lang=EN-US>***************************<o:p></o:p></span></pre><pre><span lang=EN-US>David BRADLEY<o:p></o:p></span></pre><pre><span lang=EN-US>Principal<o:p></o:p></span></pre><pre><span lang=EN-US>Thermal Energy Systems Specialists, LLC<o:p></o:p></span></pre><pre><span lang=EN-US>22 North Carroll Street - suite 370<o:p></o:p></span></pre><pre><span lang=EN-US>Madison, WI 53703 USA<o:p></o:p></span></pre><pre><span lang=EN-US><o:p> </o:p></span></pre><pre><span lang=EN-US>P:+1.608.274.2577<o:p></o:p></span></pre><pre><span lang=EN-US>F:+1.608.278.1475<o:p></o:p></span></pre><pre><a href="mailto:d.bradley@tess-inc.com"><span lang=EN-US>d.bradley@tess-inc.com</span></a><span lang=EN-US><o:p></o:p></span></pre><pre><span lang=EN-US><o:p> </o:p></span></pre><pre><a href="http://www.tess-inc.com"><span lang=EN-US>http://www.tess-inc.com</span></a><span lang=EN-US><o:p></o:p></span></pre><pre><a href="http://www.trnsys.com"><span lang=EN-US>http://www.trnsys.com</span></a><span lang=EN-US><o:p></o:p></span></pre></div></body></html>