Errors and warnings when creating/testing a library

This section quotes all errors and warnings that might occur when creating a custom library with user blocks or when testing library elements by executing the →SiL-test and/or →PiL-test.

"name" must not be used because it is a reserved keyword.
Solution: Correct the faulty term in the code so that it is not a keyword anymore. See "Reserved keywords in the library configuration" for a list of the keywords that must not be used.

Name too long. or
Maximum file length of "number" was exceeded. File name: "name"
Additional information: The maximum length for a library file results from: the file name of the library c onfiguration, the name of the library as specified in the library configuration, the 2 characters "__", the version of the library as specified in the library configuration and the extension .lib.mrclog
Solution: Shorten the specifications for the library as much as it is possible, e.g. specify a shorter name for the library as specified within the library c onfiguration .

The combination of the absolute project path, the platform toolkit name and the library configuration name exceeds the maximum length for the library name by number characters.
Solution: Shorten the specifications for the library as much as it is possible, e.g. specify a shorter name for the library as specified within the library c onfiguration or move the project so that it exists in a different (shorter) path .

Element "name" is a library block. Hence, it must not be used in other libraries.
Solution: Delete the statement specifying the block from the library configuration. If you want to use elements from other libraries, reference this library.

Failed to create directory "name"
Solution: Change the name of the named directory. Then try to generate the library again.

Failed to remove directory "name"
Solution: Make sure that not any of the files within the named directory are opened in any application. Then try to generate the library again.

Platform "name" does not exist.
Solution: In the library configuration, specify a platform provided in logi.CAD 3.

Option "name" is not supported.
Solution: Correct the named part in the library configuration . The possibilities are listed under: " Syntax for library configuration"

"name" is not a file or does not exist.
Solution: Correct the named part in the library configuration.

"name" is an invalid or a not supported path name.
Solution: Change the name of the named directory or of the named file so that the name is not a word reserved by the operating system or the name contains one of the characters reserved by the operating system.
Example 1 for Windows: Reserved words are: CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9
Example 2 for Windows: Reserved characters are: \ / : * ? " < > |

The validation has failed. No libraries have been generated.
Possibly existing, older files for the libraries (with the same name and the same version) are automatically deleted.
Solution: Open the library configuration on which base you want to generate the libraries. Fix all displayed errors. Then try to generate the library again.

Failed to generate ZIP file "name".
Solution: Check the messages that are displayed in the error log previous to this message. Fix the causes of those messages.

Copying "source" to "target" failed.
Solution 1: Make sure that the named target directory or the files in it are not required for a different purpose. Then delete this directory and try to generate the library again.
Solution 2: Make sure that you have the required copying permissions for the source files. Then try to generate the library again.

Failed to create "name".
Solution 1: Make sure that you have the required permissions for the directory in which the library is generated. Then try to generate the library again.
Solution 2: Contact the support team of logi.cals. Include your contact information, information on what you were doing in logi.CAD 3 and all messages listed in

the Error Log view, Problems view and/or PLC Logging view.

The library "name" with type "name" must contain at least one public element.
Solution, if you want to generate a logi.SAFE or logi.WEB library: Correct the content of the library configuration or of the library element so that a public library element is included (see "Declaration of the contents of the library" for the appropriate syntax). Then try to generate the library again.

Link to library "name" cannot be created. or
Link to library "name" cannot be removed.
Solution: Contact the support team of logi.cals. Include your contact information, information on what you were doing in logi.CAD 3 and all messages listed in

the Error Log view, Problems view and/or PLC Logging view.

Library "name" does not exist.
Solution 1, if you want to generate a logi.CAD 3 library: Create the library. Then try to deploy the library anew.
Solution 2, if you want to generate a logi.SAFE or logi.WEB library: Create the library (incl. SiL-/PiL-tests and release) as it is listed under "Creating and deploying a custom library". Then try to deploy the library anew.

The library "name" cannot be unpacked within the library cache.
Solution: Contact the support team of logi.cals. Include your contact information, information on what you were doing in logi.CAD 3 and all messages listed in

the Error Log view, Problems view and/or PLC Logging view.

The library configuration within the library "name" cannot be loaded.
As the library configuration is not required when using the elements from the library, this message can usually be ignored.
Solution, if the elements of the library cannot be used: Contact the support team of logi.cals. Include your contact information, information on what you were doing in logi.CAD 3 and all messages listed in

the Error Log view, Problems view and/or PLC Logging view.

There is no library provider for the library "name" referenced in "name".
Solution: Deploy the named library (see "Deploying the library").

The referenced library "name" is not installed.
Solution in order to fix the error within the library configuration: Install the referenced library with the required elements in the required version within the project as described under "Deploying the library".

The library "name" referenced in "name" cannot be installed. Reason: A different version of this library is already used in the project.
Solution: First delete the named library for the project as described under "Deleting already deployed libraries". Then install the required version of the library within the project as described under "Deploying the library".

The referenced library "name" cannot be restored.
Solution: Contact the person who gave you the current project. Ask for the specified library. Install this library as described under "Installing a library".

"name" appears to be manipulated. or
Failed to read "name". or
The CRC values for "name" could not be calculated.
This message informs system integrators about the state of the library, if this library is verified by using a command line tool.
Solution: Contact logi.cals, if you want to get more information on this possibility.

The element "name" already exists in the library configuration.
Solution: Delete the surplus element from the library configuration. Alternative: Use →namespaces in order to declare elements with a same name. Then enter the fully qualified name of the element within the libary configuration (see under "Declaration of the contents of the library").

The snapshot library "name" has not been updated because it is not provided by any library provider.
Solution: Contact the person who gave you the current project. Ask for the specified snapshot library. Install this library as described under "Installing a library".

The snapshot library cannot be deployed because the library provider does not support snapshot libraries.
Solution: Select a supported library provider when deploying the snapshot library. See "Arbeitsabläufe: Snapshot-Bibliotheken und/oder finalisierte Bibliotheken erstellen/verwenden" for details.

Due to "DEPLOY:=OBJECT" for a library element, the library configuration requires the specification "SUPPORTED_PTKS".
Solution: Insert this specification within the library configuration and complete it by a platform (see under"Declaration of information on creation and references for the library"). Alternative: Specify a different value for DEPLOY ( see under " Declaration of the contents of the library).

The POU "name" contains external variables. Hence, it must not be specified with "DEPLOY:=OBJECT" in the library configuration.
Solution: Delete all →external variables from the POU. Alternative: Specify a different value for DEPLOY ( see under " Declaration of the contents of the library).

The program "name" contains global variables. Hence, it must not be specified in the library configuration.
Solution: Delete all →global variables from the POU.

"name" is a program specified with "OBJECT". Programs must be specified with the default definition "DEPLOY:=SOURCE". or
"name" is a program specified with "INTERFACE". Programs must be specified with the default definition "DEPLOY:=SOURCE". or
"name" is an interface specified with "OBJECT". Interfaces must be specified with the default definition "DEPLOY:=SOURCE". or
"name" is an interface specified with "INTERFACE". Interfaces must be specified with the default definition "DEPLOY:=SOURCE". or
POUs with methods must be specified with the default definition "DEPLOY:=SOURCE" in the library configuration.
Solution: Specify the value SOURCE for DEPLOY at the faulty specification within the library configuration ( see under " Declaration of the contents of the library).

"BuiltInPlc" is used for specification "SUPPORTED_PTKS". Instead use "WindowsX86" and/or "LinuxX86".
Solution: Correct the platform that is entered within the library configuration.

The element "name" is ignored because of the library type "name". or
Specification "PTK_FOR_LIBRARY_BUILD" is required because of the library type "name". or
"name" is a vendor function. Vendor functions must not be used at all due to the library type "name". In contrast to this, vendor function blocks are supported with some restrictions. or
"name" is a program. Programs must not be used due to the library type "name". or
"name" must not be an expandable POU due to the library type "name". or
"name" must not be a POU using generic data types (ANY) due to the library type "name". or
"name" is a function with the default definition "VISIBILITY:=PUBLIC". But for the current library type "name", functions must be specified with "VISIBILITY:=PRIVATE". or
Data type "name" must be defined with "PRIVATE". or
The function block "name" contains the specifications "additionalObjects" and/or "additionalLibraries". Hence, the library configuration must use the specification "SUPPORTED_PTKS". or
POUs containing methods must not be used at all due to the library type "name". or
Interfaces must not be used at all due to the library type "name". or
Function blocks with the keyword "IMPLEMENTS" must not be used at all due to the library type "name".
Solution 1, if you want to generate a logi.SAFE or logi.WEB library: Correct the content of the library configuration or of the library element so that the restrictions for logi.SAFE or logi.WEB libraries are fulfilled (see "Peculiarities for logi.SAFE/logi.WEB libraries").
Solution 2: Correct the library type within the library configuration (e.g. to "LOGICAD") so that the restrictions are not valid.

The specification "PTK_FOR_LIBRARY_BUILD" must not be used due to the library type "LOGICAD".
Solution 1, if you want to generate a logi.CAD 3 library: Remove the statements from the library configuration.
Solution 2: Correct the library type within the library configuration (e.g. to "LOGISAFE") so that it is possible or required to use the statements.

Specifications "PTK_FOR_LIBRARY_BUILD" and "SUPPORTED_PTKS" must not be used at the same time.
Solution: Correct the statements within the library configuration so that the statements for the appropriate library type are correctly defined.

Test coverage could not be loaded for POU "name".
Solution 1, if you want to generate a logi.SAFE or logi.WEB library: Have the tests executed for the library elements but with test coverage.
Solution 2: Correct the library type within the library configuration (e.g. to "LOGICAD") for which tests are not required.

Test suite "name" has not been found. Expected position: "name" or
Test report "name" has not been found. Expected position: "name" or
Report for test coverage "name" has not been found. Expected position: "name" or
Log file "name" has not been found. Expected position: "name"
Solution 1, if you want to generate a logi.SAFE or logi.WEB library: Have the tests executed for the library elements but with test coverage.
Solution 2, if the required test execution files are located in a different p osition : Define the statement BASE_TEST_SOURCE and add the project-relative directory so that the test execution files for the library elements are found.
Solution 3: Correct the library type within the library configuration (e.g. to "LOGICAD") so that no tests are required.

The information of the code coverage is not available for POU "name".
Solution 1, if you want to generate a logi.SAFE or logi.WEB library: Have the tests executed for the library elements but with test coverage.
Solution 2: Correct the library type within the library configuration (e.g. to "LOGICAD") so that no tests are required.

The specification "SiLCoverageReviewed" is not necessary due to the full test coverage of POU "name".
Solution: Delete the keyword SiLCoverageReviewed (incl. its values) for the corresponding library element from within the library configuration.

The partial test coverage of POU "name" requires the specification "SiLCoverageReviewed" incl. comment. or
A comment must be specified.
Solution: Complete the keyword SiLCoverageReviewed for the corresponding library element within the library configuration. See "Declaration of the contents of the library" for details on the keyword.

Wrong format for fingerprint. The fingerprint is listed within the build report for the generated library. or
The fingerprint for "name" in library configuration "name" does not match the one within the build report.
Solution: Correct the →fingerprint that is specified with the keyword SiLCoverageReviewed for the corresponding library element within the library configuration. You find the fingerprint within the library generation report that is created when the library is generated. Best practice is to search within this HTML-file for the name of the library element and to copy its fingerprint to the clipboard. Afterwards paste the fingerprint after SiLCoverageReviewed.

The library "name" could not be released.
Solution: Contact the support team of logi.cals. Include your contact information, information on what you were doing in logi.CAD 3 and all messages listed in

the Error Log view, Problems view and/or PLC Logging view.

The release report could not be generated.
Solution: Contact the support team of logi.cals. Include your contact information, information on what you were doing in logi.CAD 3 and all messages listed in

the Error Log view, Problems view and/or PLC Logging view.

The SiL-test has been executed after the PiL-test. or
The fingerprint of the POU "name" could not be loaded from the SiL-test report. or
The fingerprint of the POU "name" could not be loaded from the PiL-test report. or
The fingerprint of the test suite "name" could not be loaded from the SiL-test report. or
The fingerprint of the test suite "name" could not be loaded from the PiL-test report. or
The SiL-test report could not be read. or
The PiL-test report could not be read. or
The test report "name" could not be found. or
The fingerprints of the POU "name" are not identical within the reports. or
The fingerprints of the test suite "name" are not identical within the reports. or
The version number of the library "Standard" could not be loaded from the SiL-test report of the POU "name". or
The version number of the library "Standard" could not be loaded from the PiL-test report of the POU "name". or
The version number of the library "Standard" is not identical within the reports of the POU "name". or
The version number of product could not be loaded from the SiL-test report of the POU "name". or
The version number of product could not be loaded from the PiL-test report of the POU "name". or
The version number of the test framework could not be loaded from the SiL-test report of the POU "name". or
The version number of the test framework could not be loaded from the PiL-test report of the POU "name". or
The library fingerprint could not be loaded from the SiL-test report of the POU "name". or
The library fingerprint could not be loaded from the PiL-test report of the POU "name". or
The library fingerprint is not identical within the reports of the POU "name". or
The version number of product is not identical within the reports of the POU "name". or
The version number of the test framework is not identical within the reports of the POU "name". or
The number of POUs in the library "name" differ from the number of test suites.
Solution: Create the logi.SAFE or logi.WEB library (incl. SiL-/PiL-tests and release) in the order as it is specified under "Creating and deploying a custom library". Mind that there are requirements for a successful release (see "Releasing the library")

.

The checksum of the library package "name" does not match the actual content because it has been modified.
Solution: Create the logi.SAFE or logi.WEB library (incl. SiL-/PiL-tests) as it is listed under "Creating and deploying a custom library". Do not manipulate the files, in particular the library package, that has been generated. Then try to execute the action for the library that has just failed.

Failed to load the library "name" to the device "name".
Solution: Contact the support team of logi.cals. Include your contact information, information on what you were doing in logi.CAD 3 and all messages listed in

the Error Log view, Problems view and/or PLC Logging view.
Include the output of the target system as well.

The library "name" could not be loaded because it has not been released. The release report "name" is missing.
Solution: Load a logi.SAFE or logi.WEB library that has been released and deployed to the project (see "Loading the released and deployed library on the target system").

You are trying to release the library "name" with the type "name". But the library has been generated with the type "LOGICAD".
Solution: Create the library anew. Then try to execute the action for the library that has just failed.

The platform "name" is specified for the library "name" whereas the platform "name" is specified for the device "name". However, the platform must be identical.
Solution: Load the logi.SAFE or logi.WEB library to the target system (= device) for which the →PIL-test has already been executed for the library as well.

The library "name" could not be loaded due to the library type "LOGICAD".
Solution: Create a logi.SAFE or logi.WEB library (incl. SiL-/PiL-tests, release, deployment) as it is listed under "Creating and deploying a custom library". Then try to load the library to the target system again.

Invalid ZIP-file.
Solution: Load a logi.SAFE or logi.WEB library that has been released and deployed to the project (see "Loading the released and deployed library on the target system")Do not manipulate the library package that has been generated. Then try to load the library to the target system again.

The PiL-test cannot be executed for the POU "name" because "VISIBILITY:=PRIVATE" has been defined within the library configuration for it.
Solution, if you want to generate a logi.SAFE or logi.WEB library and the PiL-test should be executed for the POU: Define the value PUBLIC for VISIBILITY. Then try to execute the PiL-test again (see "Loading and testing the library on the target system (= PiL-test)").

The command "name" has not been executed. The library "name" is of the type "name" while the library configuration specifies the type "name". or
The library "name" differs from the content of the library configuration. Generate the library anew.
Solution: Generate the library anew so that the generated library matches the content of the library configuration. Then try to execute the action for the library that has just failed .

The content of the library "name" could not be validated. Generate the library anew.
Solution: Generate the library anew. Then try to execute the action for the library again during the execution of which the warning has just occurred .

The additional file "name" was not found. Expected position: "name".
Solution: Copy the file into the specified folder.
Additional information: The position of the file is defined by the statement extraIncludes within a →vendor block and by the statement COMMON_SOURCE within the library configuration.

The file "name" within the library "name" is overwritten because it is copied repeatedly into the library.
Solution: Search for the include statements in which the mentioned file is specified. Check whether different files are specified. If yes, change the include statements so that the file is not copied repeatedly anymore.
Additional information: The section INCLUDE ... END_INCLUDE within the library configuration and/or the statement extraIncludes within a →vendor block specifies a file with the same name. As a consequence, the file is copied repeatedly into the library, when the library is generated.

Error when executing the SiL-test: The robot argument file could not be written. or
Error when executing the PiL-test: The robot argument file could not be written.
Solution: Contact the support team of logi.cals. Include your contact information, information on what you were doing in logi.CAD 3 and all messages listed in

the Error Log view, Problems view and/or PLC Logging view.

The fingerprint of the library ("number") that has been loaded onto the device differs from the fingerprint of the library ("number") for which the PiL-test should be executed.
Solution: Load the created library anew onto the device before you execute the PiL-test again.

"Name" is a method. Methods must not be specified in the library configuration.
Solution: Correct the mentioned specification within the library configuration – e.g. replace it with the function block in which the method is declared.

The PiL-test cannot be executed when the PLC is running. Stop the PLC before you execute the PiL-test.
Solution: Stop the PLC. The execute the PiL-test anew. Alternative: Contact the system integrator and check whether it is possible to change the configuration of the platform so that the PiL-test automatically stops the PLC.