Common failure messages

The following common failure messages issued by the device simulator, as well as the likely cause and solution, are covered in this section:

Problems not listed here may be network issues. For information on Sedona Framework networks, refer to the Niagara AX Sedona Framework Networks Guide.

No compatible platforms

If your Simulator Platform field displays the message shown in Figure A.4, then you do not have any Simulator Platform archives that provide a simulator SVM for the selected Simulator App File.

Figure A.4. No compatible platforms error message


No compatible platforms error message


To correct this problem, contact the vendor of the platform that your App specifies, and ask them to provide you with a simulator archive for that platform. Once you install this into your Sedona platform database you should see the proper Simulator Platform choice.

Missing kit

If you see the message shown in Figure A.5, most likely you do not have a necessary kit in your SEDONA_HOME/kits folder. This occurs when you do not have any versions of the required kit. The kits in your local database are organized into folders in the /kits directory where each folder name is based on a kit name. This error occurs because you do not have a folder for a specified kit.

Figure A.5. Missing kit error message


Missing kit error message


To correct this problem, install the missing kit with the necessary version (if specified in the app file’s <schema> section) into a folder bearing the same name as the kit. Place this folder under the SEDONA_HOME/kits folder.

Missing manifest

If you see the message shown in Figure A.6, most likely you do not have the necessary version of a particular kit in your SEDONA_HOME/kits folder. This occurs when you might have one or more versions of a particular kit installed in your Sedona Framework TXS installation, but the app you are trying to run in the Device Simulator specifies a version of the kit that you do not have. You will need that particular version to run this app.

Figure A.6. Missing manifest error message


Missing manifest error message


NoteYou may be able to get the app to run by removing the checksum=”xxxxxxxx” text in the <schema> section of the app. This will allow another version of the same kit to be used.

CautionIf you remove the checksum text in the schema and there are significant differences in the implementation of the specified version and the version you use, the app may not function correctly to provide the behavior you wish to simulate!

To correct this problem, install the missing version of the specified kit in to the proper folder in the SEDONA_HOME/kits folder.

Not a valid app

If you see the error message shown in Figure A.7, the ord specified in the Simulator App File field is not a valid Sedona app.

Figure A.7. Not a valid app error message


Not a valid app error message


NoteSpecify either a .sax or .sab file. No other file formats are valid.

To correct this problem, select a valid app file.

App contains validation error

If you see the error messages shown in Figure A.8, the app file contains some sort of validation problem. The specific problem with the app will be included in the error message, as well as the exception details. These examples illustrate two different parsing problems that you might see if the SAX file you are using is not a properly formatted Sedona Application XML file.

Figure A.8. Two sample app validation error messages


Two sample app validation error messages


To correct this problem, check your app file to make sure that it is not corrupted, and that it contains valid Sedona XML.

Another SVM is running

Before starting, the Device Simulator checks for the existence of an SVM that is already running on the desired port. If one is found, you will see the error message shown in Figure A.9. The message informs you that there is already an SVM running, and asks if you wish to stop it.

Figure A.9. Another SVM is running error message


Another SVM is running error message


To correct this problem, click Yes or No, depending on what you wish to do. If you select No, then the display returns to the Device Simulator view as if you had just selected your app file. If you select Yes, the tool attempts to invoke the “Quit” command on the app that is currently running. If this is successful, you will see the dialog shown in Figure A.10.

Figure A.10. Existing SVM killed dialog


Existing SVM killed dialog


If it is unable to stop the SVM, you can use your operating system Task Manager to determine whether you there is still an “svm.exe” process running, and if so, kill the process. Then you should be able to run the Device Simulator.