下载文档原格式
NO、0051Constraint equation 212 does not have a unique slave dof.和Constraint eqaution 171 has specified dof constraint at all node/dof 。
constraint equation dleted。
这一Warning常发生在边界约束条件与约束方程相互交叠的节点位置。
解决方法是不选边界约束位置节点，或不选约束方程位置节点。
第一个warning发生当节点位置对称边界条件与约束方程向冲突时。
第二个warning发生当节点位置约束条件与约束方程相冲突时。
NO、0052Term 4 （node 5000 rotz）on CE number 3331 is not active on any element。
This term is ignored。
这一warning发生当主节点坐标系与从节点坐标系不在同一个坐标体系下时。
例如主节点坐标系为总体直角坐标系，而从节点坐标系为总体圆柱体坐标系。
解决方法，就是保证二者坐标体系相一致。
NO、0053我建立接触对求解时出现下面提示：you may move entire target surface by X=-1.331532856E-04,Y=2.51086219E-04,Z=1.344714965E-04 to bring it in contact好像是移动目标面，但是不知如何移动，请高手指点说的是你的模型两个面根本就接触不上。
怎么移动？就是建模的时候，让目标面移动X=-1.331532856E-04,Y=2.51086219E-04,Z=1.344714965E-04 （相对于你当前的建模），就是说，新模型目标面的位置相对你原来的位置有X=-1.331532856E-04,Y=2.51086219E-04,Z=1.344714965E-04 的间隙距离，没有刚好接触。
Appendix B: ErrorMessages Listed below by code number are the error messages you may encounter when using LINGO. Suggestions for overcoming the errors are also included.0. THE MODEL GENERATOR RAN OUT OF MEMORY.LINGO’s model generator ran out of working memory. The model generator converts the textof your LINGO model to an expanded form suitable for an appropriate solver engine. Onmost platforms, you can increase the amount of working memory allocated to the modelgenerator. Note that memory set aside for LINGO’s model generator will not be available toLINGO’s various solver engines. Given this, you should not allocate an overly excessiveamount of memory to the generator.In Windows versions, select the LINGO|Options command, then the General tab, and in theGenerator Memory Limit box increase the amount of working memory. Press the Save buttonand then restart LINGO. You can verify the new memory allotment by issuing the Help|AboutLINGO command.On other platforms, use the following commands:SET MAXMEMB nFREEZEwhere n is the new memory allotment in megabytes. Exit LINGO and restart. Once LINGOrestarts, you can verify the new memory allotment with the MEM command.1. TOO MANY LINES OF TEXT IN THE MODEL.There are too many lines in the model’s text. For all practical purposes, the limit on total linesof text is large enough that this error message should never be encountered.2. TOO MANY CHARACTERS IN THE MODEL TEXT.There are too many characters in the model’s text. For all practical purposes, the limit on thenumber of characters is large enough that this message should never be encountered.3. OVERLENGTH LINE, CHARACTERS MAY HAVE BEEN LOST OFF END. USECARRIAGE RETURN TO BREAK UP OVER SEVERAL INPUT LINES.Input lines are limited to 200 characters. You will need to break up long input lines intoshorter ones.4. VALID LINES ARE 1 TO N. TYPE ‘ALL’ TO REFERENCE ALL LINES.The LOOK command expects a range of row numbers. If the range is invalid, you will get thismessage. Enter a new range with valid numbers.537538 APPENDIX B5. THERE IS NO CURRENT MODEL.Any command that makes sense only if there is a current model in memory will print thismessage if invoked without the presence of a model. You need to load a model with theFile|Open command in Windows or the TAKE command on other platforms, or enter a newmodel with the File|New command in Windows or the MODEL command on other platforms.6. TOO MANY NESTED TAKE COMMANDS.You have exceeded LINGO’s limit of ten nested TAKE commands within a command script.If possible, try combining some commands into a single file.7. UNABLE TO OPEN FILE: FILENAME.The file you tried to read doesn’t exist, or you misspelled its name. Try opening the file again.8. TOO MANY CONSECUTIVE COMMAND ERRORS. REVERT TO TERMINALINPUT.LINGO prints this message after having encountered a number of consecutive errors in acommand script. LINGO assumes that something has gone seriously awry, closes the scriptfile, and returns you to command level.9. NOTUSED.USED.10. NOT11. INVALID INPUT. A SYNTAX ERROR HAS OCCURRED.This is the generic error issued by the LINGO compiler when it detects a syntax error. InWindows, when you close the error box, the cursor will be on the line where the erroroccurred. Other versions of LINGO will try print out the general area where the error hasoccurred, but LINGO cannot always pinpoint the exact line. Examine this area for anyobvious syntax errors. If you are unable to find any obvious errors, a useful technique is tocomment out small sections of the model until the error goes away. This should give you agood idea of exactly where the error is occurring.Syntax errors may also occur if you are not invoking the correct compiler in LINGO. Mostusers will choose to build models using the native LINGO syntax, however, some users may prefer building their models using LINDO systax. LINGO can compile models written ineither native LINGO syntax or LINDO syntax. LINGO chooses the compiler based on amodel's file extension. LINGO models must have an extension of lg4 (the default) or lng.LINDO models must have an ltx extension. The default model extension may be set byclicking on: LINGO | Options | Interface | File Format. Each model window's title bardisplays whether it is a LINGO or LINDO model.PARENTHESIS.RIGHT12. MISSINGA LINGO expression is missing at least one closing right parenthesis. LINGO will point tothe end of the expression where the error occurred. Count the number of parentheses in thisexpression to verify if you have input the correct number, or, in Window use the Edit|Match Parenthesis command to find the unmatched parenthesis.ERROR MESSAGES 539 13. A SPECIFIED SPREADSHEET RANGE WAS NOT FOUND. RANGE_NAME.You specified a spreadsheet range titled RANGE_NAME that LINGO was unable to find.Check the spelling of the range name and be sure that the range is defined in the spreadsheet.14. NOT ENOUGH TEMPORARY OPERATOR STACK SPACE.LINGO uses a stack to temporarily hold operators and prefix functions during compilation of an expression. It is possible, though unlikely, that this stack will overflow. If so, try breakingup lengthy expressions, or adding parentheses to offending expressions.15. NO RELATIONAL OPERATOR FOUND.Each LINGO expression (with the exception of variable domain expressions) must containone relational operator (e.g., =, <, >). Check to be sure that all expressions contain relationaloperators.16. ALL MODEL OBJECTS MUST HAVE THE SAME PARENT SET FOR THISOPERATION.You have attempted to use an import or export function in the data section that involves twoor more attributes from different parent sets. Break the function into multiple calls, so eachinstance refers to attributes belonging to the same parent set.17. NOT ENOUGH INDEX STACK SPACE.LINGO uses a stack to keep track of indices referenced by set operators. It is possible, though unlikely, that this stack will overflow. The only way to remedy this situation is to rewrite thegiven expression, so it uses fewer indices.18. OUT OF SET STACK SPACE.LINGO uses a stack to keep track of sets referenced by set operators. This stack mayoverflow, though it’s unlikely. The only way to remedy this situation is to rewrite the givenexpression, so the maximum number of pending set operators is reduced.19. INVALID USE OF @INDEX FUNCTION.The @INDEX function expects an optional set name followed by a mandatory primitive setelement. Check to see that your arguments comply with these restrictions.20. IMPROPER USE OF SET NAME.A set name has been used in an improper manner. For instance, you may have attempted toset the name equal to a quantity. Check your model’s syntax.21. IMPROPER USE OF ATTRIBUTE NAME.This message is printed if an attribute name is used incorrectly. For instance, you may haveattempted to use it as a scalar (single value) variable. Check your model’s syntax.22. TOO MANY INEQUALITY OR EQUALITY RELATIONS.A constraint may have only one relational operator (i.e., =, <, or >). A two-sided constraintsuch as 2 < X < 4 is not permitted. Instead, write it as two one sided constraints: X > 2; and X < 4;.540 APPENDIX B23. IMPROPER NUMBER OF ARGUMENTS.LINGO’s predefined functions generally expect a specific number of arguments. You’ll getthis message if you are passing an incorrect number of arguments. Check the syntax of thefunction in question.NAME.SET24. INVALIDIf LINGO was expecting a set name and didn’t find it, you will get this message. Note that all sets must be defined in a sets section before they are referenced in a model expression.25. INVALID ARGUMENT LIST FOR AN @WKX() FUNCTION.The @WKX function is used to link with spreadsheet files. The argument list is incorrectlyspecified. Check the documentation for the syntax of the @WKX function.26. IMPROPER NUMBER OF INDEX VARIABLES.When using indices in conjunction with a set in a set operator function, LINGO checks to besure that you have specified the correct number of indices for the set. If not, it prints thismessage.27. THE FOLLOWING SPREADSHEET RANGE IS DISCONTINUOUS:RANGE_NAME.At present, LINGO only supports continuous ranges. Continuous ranges are simple,rectangular ranges. Discontinuous ranges are unions of two, or more, continuous ranges. You will need to break your discontinuous range up into a set of equivalent, continuous ranges.28. INVALID USE OF A ROW NAME.A row name may be input within brackets at the start of a constraint and may contain up to 32characters. This error message indicates some improper use. Check your model’s syntax. 29. INVALID NUMBER OF INITIALIZATION VALUES IN A DATA OR INITSTATEMENT.You must assign a value to every element of each array in a DATA or INIT statement. LINGO keeps track of the number of values you specified and checks this against the length of eacharray being assigned. If the two numbers don’t agree, LINGO prints this message.30. A GENERAL FAILURE OCCURRED WHILE ATTEMPTING A LINK TO EXCEL.LINGO attempted to open an OLE link to Excel, but was unsuccessful. Be sure that Excel isinstalled on your machine (version 5, or later). Also, if your machine is busy, this errormessage can occur because it is taking an excessive amount of time to load Excel. In whichcase, simply retry the action when the machine is less busy.31. INVALID ARGUMENT LIST FOR AN @TEXT() FUNCTION CALL.An instance of the @TEXT function has an invalid argument list. Check the documentation on this function for the correct syntax.32. ATTEMPT TO IMPORT A BLANK SET MEMBER NAME.You have attempted to import a set member name that is entirely blank. All set membernames must conform to standard LINGO naming conventions and may not be blank. Assign a nonblank name to the set member and retry.ERROR MESSAGES 541 33. INVALID ARGUMENT LIST FOR AN @OLE() FUNCTION CALL.Check the documentation on the @OLE function to determine the correct syntax.34. RANGE LENGTHS MUST BE IDENTICAL WHEN IMPORTING DERIVED SETS.You are importing a derived set from multiple ranges of varying lengths. When usingmultiple ranges, each range must contain the same number of cells. Adjust the sizes of theranges so they agree and retry.35. UNRECOGNIZED NAME IN AN OUTPUT FUNCTION.You have attempted to use an output function (e.g., @OLE or @ODBC) to export the value ofa variable that does not exist. Check your output functions to see if all the variables exist andthat they are spelled correctly.36. ATTEMPT TO IMPORT INVALID PRIMITIVE SET ELEMENT NAME: NAME.A primitive set name imported from an external source is invalid. Make sure the nameconforms to normal LINGO naming standards.37. NAME ALREADY IN USE: NAME. CHOOSE A DIFFERENT NAME.A model can’t use duplicate names. Select a new, unique name.38. THE ODBC SERVER RETURNED THE FOLLOWING ERROR MESSAGE:MESSAGE-TEXT.The ODBC server encountered an error. The text of the message will be displayed. In mostcases, the text of the message should help clarify the problem.39. THE FOLLOWING SET ELEMENT WAS NOT DERIVED FROM ITS PARENTPRIMITIVE SET: SET-ELEMENT.When defining a sparse derived set, LINGO checks each set element against the parent set. If the element is not found in the parent set, you will get this message. Please check the spelling and ordering of the set elements in the sparse derived set you are defining.40. INVALID NUMBER OF DERIVED SET INDEX ELEMENTS.If a sparse derived set is formed from, say, three primitive sets, then there must be a multipleof three primitive set element names in the explicit definition of the derived set. LINGOchecks this, and issues this message if there is not a match.41. OUT OF ATTRIBUTE INDEX SPACE.LINGO imposes a limit on the total number of primitive sets used in defining derived sets.The current limit is quite large and should not pose a problem.42. EXPLICIT VARIABLE IN A SET CONDITION FOR SET: SET_NAME.When using a conditional expression to define the members of a derived set, you cannotreference a variable that has not been fixed in a previous data statement. LINGO must be able to completely evaluate these conditional expressions during compilation so it knows the sizeof the set.542 APPENDIX B43. EXECUTOR ERROR IN SET CONDITION FOR SET: SET_NAME.LINGO prints this message if an arithmetic error occurred when it was trying to evaluate aconditional expression used to define the members of a derived set. Check all arithmeticoperations in the set definition in question.CONDITION.44. UNTERMINATEDEach conditional expression placed on a set operator must be terminated with a colon (:).LINGO prints this message if you fail to add one.45. INVALID ARGUMENT LIST FOR AN @ODBC FUNCTION CALL.You have a syntax error in an argument list of an @ODBC function call. Check thedocumentation on the @ODBC function to determine the proper syntax.NAME:FILENAME.FILE46. INADMISSABLEThe file name is either too long or it contains characters not permitted on this platform. Use a different file name and try again.47. TOO MANY FILES OPEN: NAME_OF_LAST_FILE.LINGO imposes a limit on the total number of files that can be opened simultaneouslythrough use of the @FILE command. You can try placing all the data in fewer files. Also,avoid using the LINGO end-of-record mark (~) at the end of files. This allows LINGO to“see” the end of the file, forcing it to close the file down, thus allowing for an additional open file.48. UNABLE TO OPEN FILE: FILENAME.LINGO prints this message when it is unable to open a file. Check the spelling of thefilename. Be sure a copy of the file exists on your disk and that the file is not open in another application.49. ERROR READING FILE: FILENAME.LINGO prints this message in case an error occurred while reading a file with the @FILEfunction. Check the file to be sure it is not damaged. Another possibility is that you do nothave read access to the disk or directory where the file resides.50. IMPROPER USE OF @FOR() FUNCTION.LINGO prints this message if you’ve attempted to nest an @FOR function inside some other set operator. You can nest @FOR functions within other @FOR s, and other set operatorswithin @FOR s, but nesting an @FOR inside any function other than another @FOR is notpermitted.51. RAN OUT OF GENERATOR MEMORY COMPILING MODEL.LINGO exhausted available generator memory compiling a model and was forced to halt. See error message 0 for suggestions on increasing the model generator’s allotment of workingmemory.52. IMPROPER USE OF @IN() FUNCTION.You passed incorrect arguments to the @IN function. Check the documentation on the @INfunction.ERROR MESSAGES 543 53. UNABLE TO LOCATE RANGE NAME: RANGE_NAME.You specified a range name in a spreadsheet interface function, which is either inadmissibleor was not found in the specified worksheet. Please check the worksheet file to be sure therange name exists as spelled.54. ERROR(N) READING SPREADSHEET FILE.LINGO encountered a read error while attempting to read a worksheet file. Check to see if the file has been corrupted, and be sure it is in a supported worksheet format.55. UNABLE TO OPEN @TEXT DATA FILE: FILENAME.You have specified a file as part of the @TEXT function that could not be opened. Check tosee that the file exists and that you have spelled the name correctly.56. ERROR READING FROM @TEXT DATA FILE: FILENAME.A read error was encountered when LINGO attempted to read data from a file specified in an@TEXT function. Check to be sure that the file is not corrupted.57. INVALID INPUT ENCOUNTERED IN @TEXT DATA FILE: TEXT_STRING.The @TEXT function may be used in the data section to read and write numeric values. Thiserror message results when nonnumeric data is encountered in a file being read with @TEXT.If you need to import nonnumeric data from a text file, use the @FILE function.58. NOT ENOUGH VALUES FOUND IN @TEXT DATA FILE: FILENAME.VALUES NEEDED.NM VALUES FOUND.The @TEXT function may be used in the data section to read and write numeric values. Thiserror message results when an insufficient number of data points were found in a file beingread with @TEXT. Add enough data to the file to fully initialize the attributes of interest. 59. TOO MANY VALUES ENCOUNTERED IN @TEXT DATA FILE: FILENAME.The @TEXT function may be used in the data section to read and write numeric values. Thiserror message results when too many data points were found in a file being read with@TEXT. Remove data from the file until you have the exact number required to initialize theattributes of interest.60. FILE NAME REQUIRED IN AN @TEXT() INPUT OPERATION.The @TEXT function may be used in the data section to read and write numeric values. Thiserror message results when an input file was not specified when attempting to read data points from a file using @TEXT.DISREGARDED.61. COMMANDLINGO prints this message when it was unable to interpret a command you typed at the colon prompt (:). Check the spelling of the command and that you are using correct syntax for thecommand.62. RAN OUT OF WORKSPACE IN MODEL GENERATION (N).LINGO ran out of working memory generating your model. Refer to error message 0 forstrategies to increase the model generator’s working memory allotment.544 APPENDIX B63. MODEL IS ILL DEFINED. CHECK FOR UNDEFINED INDICES AND/ORCONDITIONS IN EXPRESSION: EXPRESSION.LINGO will print this message for one of two reasons: 1) a conditional expression used toqualify a set operator function cannot be evaluated, or 2) a subscript expression cannot beevaluated. When we say an expression cannot be evaluated, we mean that one or morevariables in the expression are not fixed. LINGO will report the expression number, or rowname (if used), where the fault occurred. Please be sure to add constraints or data statementsto fix all the variables in the conditional or subscript expression in question. Also, if you areusing primitive set member names in the model’s equations, you must use the @INDEXfunction to get the index of the primitive set member. If you don’t use the @INDEX function, LINGO will treat the primitive set member as if it is a new scalar variable. You can haveLINGO check for primitive set names that are in use in both the data and the model equations by checking the Check for duplicate names in data and model box on the General Solver tabof the LINGO|Options command dialog box (or the SET CHKDUP 1 command on otherplatforms). Finally, if you would like to use primitive set names directly in your model’sequations (a practice we don’t recommend), you can force LINGO to allow this by checkingthe Allow unrestricted use of primitive set member names checkbox on the General Solver tab (or the SET USEPNM 1 command on other platforms).64. TOO MANY NESTED @FOR OPERATORS.LINGO maintains a stack to keep track of pending nested @FOR functions. Too many nested @FOR s could cause this stack to overflow, although it would be an unusual model thattriggers this error. You can avoid nesting some @FOR s by forming derived sets, and looping over a single derived set as opposed to many primitive sets.65. IMPROPER USE OF @WARN FUNCTION.You have used the @WARN function incorrectly. Check the documentation on @WARN todetermine where you went wrong.66. WARNING: TOTAL FIXED ROWS WITH NONUNIQUE ROOTS: NWhen LINGO generates a model, it determines if a variable can be solved for directly andsubstituted out of the model. These variables are referred to as being fixed, and the row in the model used to solve for a fixed variable is referred to as a fixed row. When LINGO solves for the value of a fixed variable in its fixed row, it will look around a neighborhood of thevariable’s value to determine if multiple roots exist, and display this message if any arefound. An example of an equation with such multiple roots would be: @SIGN(X ) = 1. Allnon-negative values of X would satisfy this relation. LINGO will display the names of up tothree variables and their corresponding fixed rows with this symptom. LINGO will continueto process the model, however. You should examine the model closely when this error occurs, because it would be unusual to find a well formulated model displaying this characteristic.Keep in mind that there might be a better solution involving a different value for the fixedvariable than was chosen by LINGO.ERROR MESSAGES 545 67. RAN OUT OF SPACE FOR ROW NONZERO LISTS.When LINGO generates a constraint, it stores the nonzero elements (coefficients) in a list.The size of the list is limited only by the amount of working memory allocated to LINGO’smodel generator. See error message 0 for strategies on increasing the model generator’sworking memory allotment.68. STRING ARITHMETIC NOT ALLOWED.You've attempted to perforn an arithmetic operation on a text object.69. UNDEFINED ARITHMETIC OPERATION IN CONSTRAINT: N.LINGO ran into an undefined arithmetic operation during execution (e.g., 1/0). Check theconstraints to be sure all operations are defined.70. SUBSCRIPT OUT OF RANGE ON ATTRIBUTE: ATTRIB.While executing your model, LINGO found a subscript that was out of range. For example, if you defined the attribute STAFF with the set /1..5/, then referencing STAFF(6) would result in this error message. Nonintegral subscripts will also generate this message. Please be sure your sets are defined across the intended range and that any subscript computations are correctlyspecified.71. IMPROPER USE OF A VARIABLE DOMAIN FUNCTION (E.G. , @GIN, @BIN,@FREE, @BND).This error results when the syntax of a variable domain function has been violated. Check the model’s use of these functions.72. UNABLE TO SOLVE FOR FIXED VARIABLE VAR_NAME IN CONSTRAINTCONSTRAINT_NAME.LINGO has determined that it should be able to solve for a particular variable in a given row.The root finder was not able to converge on a solution. Be sure a solution exists for the row(e.g., the expression: -1=x^.5, would have no real solution). If possible, rewrite the equationin the form x = f(.), where x appears only once and is on the left-hand side of the expression.LINGO is always able to solve expressions in this form, as long as the function is defined and evaluates to a real number (e.g., x = @LOG(-3) evaluates to an imaginary number; and x/0 isundefined). If this is not possible, then you might try solving the expression by some othermethod, and enter the variable’s value as a constant in LINGO.73. USER INTERRUPT DURING STRUCTURAL ANALYSIS.LINGO was interrupted during the model generation process before the solver was initiated.74. MAGNITUDE OF BOUND EXCEEDS: 1.E+21 ON VARIABLE: VARIABLE_NAME.You have entered a bound outside LINGO’s allowable limit. The magnitude of bounds inputusing @BND may not exceed 1019.75. CONFLICTING BOUNDS ON VARIABLE: VAR_NAME.LINGO has detected a bound on the named variable that is outside of the range of anotherbound. For instance, @BND(-6, X, 6), followed by @BND(-5, X, 5) would not yield this error.However, following it with @BND(7, X, 9) would.546 APPENDIX BMODEL.76. ERRORGENERATINGLINGO was unable to pass the model to the optimizer. If this error occurs, contact LINDOSystems technical support.77. ARITHMETIC ERROR GENERATING MODEL.LINGO was unable to generate the model due to an undefined arithmetic operation (e.g.,division by zero). Remove all undefined arithmetic operations from your model.USED.78. NOT79. NOT USED.80. NOT ENOUGH WORK SPACE GENERATING MODEL.LINGO ran out of working memory while trying to generate the model. Please refer tomessage 0 for strategies to increase the model generator’s working memory.FOUND.SOLUTION81. NOFEASIBLELINGO was unable to find a solution that simultaneously satisfies all the constraints. Checkthe model’s consistency. Try dropping constraints until the problem goes away to get an idea of where the trouble may lie. Also, check the solution report. Constraints contributing to theinfeasibility will have a nonzero dual price.82.UNBOUNDED SOLUTION.LINGO was able to increase the objective function without bound. Be sure that you haveadded all constraints to your model and that they have been input correctly.83. NOT USED.84. NOT ENOUGH LINEAR FORM SPACE - BREAK UP LONG EXPRESSIONS.LINGO exceeded a limit while trying to generate the nonzeros in a constraint. In general, this message should not occur. However, if you do encounter this message, contact LINDOSystems technical support.85. STACK OVERFLOW. EXPRESSION TOO COMPLEX.LINGO uses a stack to store temporary values while executing the expressions in a model.The default stack size is quite large. Thus, this message should not occur. Should you receive this message, however, contact LINDO Systems technical support.86. ARITHMETIC ERROR IN CONSTRAINT: CONSTRAINT.INSTRUCTION POINTER: NAn undefined arithmetic operation (e.g., 1/0 or @LOG(-1)) occurred while LINGO wasgenerating the model. If you have specified a row name for the constraint, LINGO will print the name of the constraint. If you haven’t specified row names in your model, you may want to add them to assist in tracking down this error. Check the referenced constraint for anyundefined operations.87. IMPROPER USE OF @IN FUNCTION.You have specified improper arguments for the @IN function. Refer to the documentation on this function for more details.88. SOLUTION IS CURRENTLY UNDEFINED.LINGO was not able to solve the model to completion for some reason. In which case, anyattempt to print out a solution will result in this message. Try re-solving the model anddetermining the reason LINGO was unable to solve the model.89. RUNTIME ERROR IN SOLVER ROUTINES. CONTACT LINDO SYSTEMS.An unexpected runtime error has occurred in LINGO's solver routines. Please contact LINDO Systems for assistance.90. USER INTERRUPT DURING MODEL GENERATION.The user interrupted LINGO while the model was being generated from input.91. INVALID RUNTIME PARAMETER VALUE.At runtime, LINGO will prompt for any variable set to equal a question mark in the datasection. If LINGO receives an invalid value, you will get this error message. Correct yourdata and try again.92. WARNING: THE CURRENT SOLUTION MAY BE NONOPTIMAL/INFEASIBLEFOR THE CURRENT MODEL.If you’ve solved a model and brought another model window to the front, LINGO prints this message to remind you that the solution you’ve asked for may not belong to the frontmostmodel window. LINGO also prints this message whenever you attempt to examine anonoptimal solution. For instance, when you’ve interrupted the solver, or when LINGOcouldn’t find a feasible answer. In the latter case, correct any errors in the model and re-solve.93. INVALID SWITCH IN COMMAND LINE.Some LINGO commands accept switches, or modifiers. If there was an error in one of thesecommand-line modifiers, LINGO will print this message. Refer to the documentation on thespecific command to learn the available modifiers.94. NOTUSEDError code not currently in use.95. THE SOLVER WAS INTERRUPTED PRIOR TO COMPLETION.The user interrupted the solver by clicking the Interrupt Solver button in the solver statuswindow. The solver will halt and return the best solution found up to this point.USED96. NOTError code not currently in use.97. UNRECOGNIZED MODEL SYNTAX NEAR LINE: N ON INPUT.This message will be generated if, during the translation of a LINDO model file in “TAKE”format, a command or other invalid model content is detected after the END statement. Thetranslated file up to this point will be displayed. Modify the LINDO file, so any commandsafter the END statement are removed.。
错误提示：在建立与服务器的连接时出错。
在连接到SQL Server 2005 时，在默认的设置下SQL Server 不允许进行远程连接可能会导致此失败。
(provider: SQL 网络接口, error: 26 - 定位指定的服务器/实例时出错)有段时间遇到上面问题，在网上查找了许多方案，但那些方案都没能够解决问题，在解决其他问题时，发现一些其他端倪，返回来解决此问题，将该问题解决。
总结了我的解决方案（即下文中的方案一），并且我把在网上搜索来的解决方案也汇总了一下，与大家分享。
分析：“在建立与服务器的连接时出错”说明与数据库服务器有关；“在默认的设置下SQL Server 不允许进行远程连接可能会导致此失败。
”说明与权限有关；“provider: SQL 网络接口”说明当前登录身份是网络接口；“error: 26 - 定位指定的服务器/实例时出错”说明定位不上指定的服务器实例。
方案一：1、查看数据库服务是否存在；2、右击数据库实例服务--属性—登陆，将登陆身份改为本地系统（local system）；3、启动服务；4、若启动、暂停、停止等选项都是灰色，请查看启动类型是不是“禁用”了，若“禁用”了，请改为“自动”，然后启动服务；方案二：首先请确认SQL SERVER EXPRSS已安装到本地计算机上，并且SQL SERVER (SQLEXPRESS)服务已经成功启动。
如果问题仍然存在，可以尝试开始->所有程序->MS SQL Server2005->配置工具->MS SQL Server2005外围应用配置器-> “服务和连接的外围应用配置器”，然后将“远程连接”配置为“同时使用TCP/IP 和named pipes”。
Analysis Services下远程连接选择"本地连接和远程连接"，应用后重启。
由于启动用户实例的进程时出错，导致无法生成SQL Server 的用户实例。
【篇一】错误用英语怎么说1.(不正确) wrong; mistaken; incorrect; erroneous2.(不正确的事物、行为等) mistake; error; blunder; fault; falsehood; [俚语] booboo例句：This philosophy has been proved incorrect .这种观点被证明是错误的。
Mistakes were corrected and gaps filled .错误改正了，缺点也弥补了。
The church was wrong in silencing galileo .教会压制伽俐略是错误的。
And suppose you misjudge the occasion ?假如你们错误地估计了场合呢?It is no use grieving about past errors .为以往的错误懊悔于事无补。
He makes mistakes , and that very often .他犯了错误，而且是常常犯。
It will prove his historic mistake .这肯定是他的一个历史性的错误。
Analogy may be a deceitful guide .类推方法有时不免导入错误的途径。
The accident was caused by human error .这一事故是人为错误造成的。
【篇二】错误的英文是什么错误的英文：errormistakemistaken参考例句：Incorrectness of reasoning or belief;erroneousness. 错误推理或信仰上错误;错误Unknown Error未知的错误A false ideal错误的理想A lapse of memory;a lapse in judgment.记忆的错误;判断上的错误Incorrectness of reasoning or belief; erroneousness. 推理或信仰上错误;错误Garbage in, garbage out.错误的输入必然导致错误的输出。
SpringSecurity源码解析上篇已讲述了Spring Security最简单的配置，本篇将开始分析其基本原理在上篇中可以看到，在访问 http://localhost:18081/user 时，直接跳转到登录页。
那Security是怎么做的呢？本篇主要讲述跳转到登录页前的处理⾸先来看⼀张时序图：通过上图可以看到，请求顺序为AbstractAuthenticationProcessingFilter -> AnonymousAuthenticationFilter -> ExceptionTranslationFilter -> FilterSecurityInterceptorAbstractAuthenticationProcessingFilter请求先进⼊ AbstractAuthenticationProcessingFilter 的doFilter()⽅法。
判断当前filter是否可以处理当前请求(也就是是否包含⽤户名密码信息)，如果是，则调⽤其⼦类UsernamePasswordAuthenticationFilter.attemptAuthentication() ⽅法进⾏验证(第⼀次请求时，没有⽤户名密码，是不会调⽤⼦类的)public void doFilter(ServletRequest req, ServletResponse res, FilterChain chain)throws IOException, ServletException {HttpServletRequest request = (HttpServletRequest) req;HttpServletResponse response = (HttpServletResponse) res;//判断当前的filter是否可以处理当前请求，不可以的话则交给下⼀个filter处理if (!requiresAuthentication(request, response)) {chain.doFilter(request, response);return;}if (logger.isDebugEnabled()) {logger.debug("Request is to process authentication");}Authentication authResult;try {//抽象⽅法由⼦类UsernamePasswordAuthenticationFilter实现authResult = attemptAuthentication(request, response);if (authResult == null) {// return immediately as subclass has indicated that it hasn't completed// authenticationreturn;}//认证成功后，处理⼀些与session相关的⽅法sessionStrategy.onAuthentication(authResult, request, response);}catch (InternalAuthenticationServiceException failed) {logger.error("An internal error occurred while trying to authenticate the user.",failed);//认证失败后的的⼀些操作unsuccessfulAuthentication(request, response, failed);return;}catch (AuthenticationException failed) {// Authentication failedunsuccessfulAuthentication(request, response, failed);return;}// Authentication successif (continueChainBeforeSuccessfulAuthentication) {chain.doFilter(request, response);}//认证成功后的相关回调⽅法，主要将当前的认证放到SecurityContextHolder中successfulAuthentication(request, response, chain, authResult);}认证成功后的回调⽅法：protected void successfulAuthentication(HttpServletRequest request,HttpServletResponse response, FilterChain chain, Authentication authResult)throws IOException, ServletException {if (logger.isDebugEnabled()) {logger.debug("Authentication success. Updating SecurityContextHolder to contain: "+ authResult);}//将认证结果保存到SecurityContextHolder中SecurityContextHolder.getContext().setAuthentication(authResult);rememberMeServices.loginSuccess(request, response, authResult);// Fire eventif (this.eventPublisher != null) {eventPublisher.publishEvent(new InteractiveAuthenticationSuccessEvent(authResult, this.getClass()));}//调⽤其它可扩展的 handlers 继续处理该认证成功以后的回调事件//实现AuthenticationSuccessHandler接⼝即可successHandler.onAuthenticationSuccess(request, response, authResult);}认证失败后的回调⽅法：protected void unsuccessfulAuthentication(HttpServletRequest request,HttpServletResponse response, AuthenticationException failed)throws IOException, ServletException {//清除SecurityContextHolder的中数据SecurityContextHolder.clearContext();if (logger.isDebugEnabled()) {logger.debug("Authentication request failed: " + failed.toString(), failed);logger.debug("Updated SecurityContextHolder to contain null Authentication");logger.debug("Delegating to authentication failure handler " + failureHandler);}rememberMeServices.loginFail(request, response);//调⽤其它可扩展的 handlers 处理该认证失败以后的回调事件//实现 AuthenticationFailureHandler 接⼝即可failureHandler.onAuthenticationFailure(request, response, failed);关于⾃定义 handlers ，可参考UsernamePasswordAuthenticationFilterUsernamePasswordAuthenticationFilter本⾝不是过滤器，⽽是继承了AbstractAuthenticationProcessingFilter才拥有过滤器的性能，其主要是验证⽤户名密码。
微软支持针对Windows Server 2008 Hyper-V的重点关注问题（第三季）（翻译）上一季我们的支持工程师发布了针对Hyper-V一系列问题，现在是对这些内容进行逐一的更新的时候了。
这些问题被分门别类地列入重点关注问题的范畴，并列出了可能的解决方案和必要的注释。
我想你们会注意到第三季的问题，相对于第一季和第二季没有太大变化。
但愿越来越多的人看到我们所做的更新，但愿这些问题的发生越来越少并最终全部消失。
对于第四季的结果，可能将有一个新的博客。
另外我想说，我们强烈建议在所有运行了Hyper-V 角色的服务器上安装Windows Server 2008 SP2。
部署、规划问题1：用户寻找Hyper-V的文档解决方法：Hyper-V TechNet Library提供了这方面的信息，它包含了到达几个产品小组博客的链接。
另外Microsoft Virtualization网站包含了快速获取现实可行的基于Hyper-V 解决方案的信息。
安装问题问题1：用户遇到了关于预览版Hyper-V的问题解决方法：更新为hyper-v的发行版本(KB950050)问题2：在Windows Update的最新更新都安装完毕或者KB950050安装之后，虚拟机启动失败，并出现以下错误提示信息：An error occurred while attempting to change the state of the virtual machine vmname . ‘ vmname ’ failed to initialize.Failed to read or update VM configuration.或者An error occurred while attempting to change the state of virtual machine vmname . " VMName " failed to initializeAn attempt to read or update the virtual machine configuration failed." VMName " failed to read or update the virtual machine configuration: Unspecified error (0x80040005).原因：这个问题是因为在测试版本的Hyper-V中创建的虚拟机配置与后面版本的Hyper-V 不兼容解决方法：按照KB949222所述的步骤进行操作。
AMOS错误提⽰An error occurred while attempting to fit the model. 拟合模型时出现⼀个错误。
The sample moment matrix is not positive definite. It could fail to be positive definite for any of the following reasons: 样本协⽅差矩阵是⾮正定矩阵。
由于下列原因不能正定。
1.The sample covariance matrix or the sample correlation matrix contains a data entry error.样本协⽅差矩阵或样本相关矩阵包含的数据有误。
2.The ovserved variables are linearly dependent (perhaps because the sample size is too small).观察变量因为样本太少产⽣线性相依的情形。
3.The sample covariance matrix or sample correlation matrix was computed from incomplete data using the method of ‘pairwise deletion’.使⽤成对删除法时，从不完全的数据估计出样本协⽅差矩阵或样本相关矩阵。
4.The sample correlation matrix contains correlation coefficients other than product moment correlations (such as tetrachoric correlations). 与产⽣动差相关相⽐，样本相关矩阵包含其他⽆关相关系数。
For maximum likelihood estimation only, it may be appropriate to check “Allow non-positive definite samples covariance matrices” in the “Analysis Properties” window, or to use the NonPositive method. ⽤最⼤似然法估计，应在“分析属性窗”⼝中适度检查“允许⾮正定样本协⽅差矩阵”，或使⽤⾮正定的⽅法。
美洲总部Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706USACisco AnyConnect 安全移动客户端 VPN 用户消息，版本 3.12012 年 10月 15 日本文档包含 AnyConnect 客户端 GUI 上显示的用户消息。
每则消息后附有说明，以及建议的用户和管理员操作（如果适用）。
对配置用于提供 VPN 接入权限的安全网关具有监控和配置权限的 IT 代表，建议的管理员操作适用。
注重新启动终端设备操作系统和 AnyConnect 有助于恢复某些错误。
本文档中的消息按字母顺序排序，以下消息除外：“本文档中未包含的消息”(Message not present in this document)说明 源自作为安全网关的思科自适应安全设备 (ASA) 5500 系列 的消息。
此错误消息可能包含任何错误字符串。
除非另有说明，其余消息均源自 AnyConnect 。
“已为您生成新的 PIN 码：PIN 。
”(A new PIN has been generated for you: PIN .)说明 服务器已生成新的个人识别码 (PIN)，用于与 SDI 身份验证令牌结合使用。
建议用户响应 无。
“在收到的服务器证书中检测到安全威胁。
VPN 连接将无法建立。
”(A security threat has been detected in the received server certificate. A VPN connection will not be established.)说明 在收到的服务器证书中检测到安全威胁。
威胁可能是空字符前缀攻击的结果。
建议用户响应 将此问题报告给您组织的技术支持部门。
建议管理员响应 提供有关获取 VPN 接入所需证书的说明。
“有发起 VPN 连接的用户以外的其他用户从本地登录计算机。
