<< Click to Display Table of Contents >> Navigation:  Editing a SpecView Project > SpecView Error Codes > Error Message Numbers

 

All messages in SpecView have a number which starts with either an 'E' (for Error message) or an 'M' (for informational Message) or 'W' (for Warning message).

This number uniquely identifies the message, which is particularly useful when SpecView has been translated into another language, as it allows us to understand which message is being displayed.

 

For example:

 

 

Some messages require further explanation, see below:

 

 

 

M12337 WARNING! Editing this project without a dongle connected will mean that it will not subsequently run with a Runtime-Only dongle, or some other systems.

When SpecView is run with a Runtime-Only license it will only allow projects to be used that were last saved with a full (not Runtime-Only) license.

This is to prevent projects from being edited by removing the license (dongle). If in any doubt or to update the license to a full license please contact your SpecView Representative.

 

 

W12380 This project uses some features that are not supported by this build of SpecView.

The message then lists the feature(s), followed by:

"The project will run, but these new features will not operate correctly, or may cause unexpected results.

Please update your version of SpecView."

 

SpecView projects are typically backwards compatible, which means that a project developed using the latest build (or release) would work with previous builds.

(That is within a given major version, which means that Version 3 projects are not backwards compatible with Version 2).

 

Therefore to allow new features to be added to SpecView this message has been added.

The first new features relevant to this were the addition of flashing and hiding to Color Dynamics.

The information about new features is stored in the [NEW] section of the SETTINGS.INI file.

 

E12086 This GDW was not defined in this project. To prevent misleading values appearing, all dynamic items have been removed.

 

This is typically caused by users copying files from one project folder to another. It is important to remember that all the files in a project folder are interconnected and so cannot be copied from one project folder to another.

However, if this error occurs and it is believed that files have not been intentionally copied then please make an Archive of the project. It is important to check the ‘SpecView backups’ box, and uncheck the 'Include Log files' box.  Then email the Archive to SpecView's Technical Support.

 

E12272 Devices found on the Remote tab that are not present on this PC. To remove them click OK, to keep them click Cancel.

 

This means that this SpecView Project was originally from a different PC, which was running as a SpecView Local.

 

For example, if there were two PCs with IP addresses 1.1.1.1 and 2.2.2.2 and a Project is setup on the PC 1.1.1.1 as a SpecView Local, it would be 'listening' on IP address 1.1.1.1

 

If this Project was then moved/copied/archived onto PC 2.2.2.2 then (so long as this PC only has the one network card) SpecView would just use the IP address of the network card, so it would ‘listen’ on 2.2.2.2.

 

But going into File->Preferences would cause SpecView to notice that this Project was originally setup to listen on 1.1.1.1, so it would display this message.

 

Clicking OK would remove the reference to 1.1.1.1, whereas Cancel would keep the reference, this is so that if this Project was then subsequently put back on PC 1.1.1.1 it would work without the need for further change.

 

E12310 WARNING: The Delete key has been disabled for deleting this type of ActiveX control.

 

Instead please use the Delete menu item on the Edit menu.

The reason for this is because it is unclear whether it should delete something within the control, or delete the control itself.

 

This warning message will be displayed when the delete key is used to delete an ActiveX control which has a data entry field within it. This is because the meaning of delete key becomes ambiguous in this context. So to delete the contol use the Delete menu item on the Edit menu.

 

E12313 ERROR: ActiveX controls cannot be registered or unregistered because you are not running as an Administrator

E12314 ERROR: ActiveX environment is not setup

E12315 ERROR: ActiveX controls cannot be registered because you are not running as an Administrator

The 3 errors above are detailed here.

 

E17022 Could not write namePacket to log file (9)     (or a similarly worded message)

All the time that SpecView is in Runtime mode it is writing to the log data files. These files are stored in the Project's sub-folder, which is within the folder where SpecView was installed (this is usually C:\SV3\ unless this was specifically changed during the installation).

 

This error will occur if SpecView is unable to write the log data files. There are a number of possible reasons for this:

 

- The computer may have run out of disk space to store the log data files. Please check the amount of free disk space available to the folder where SpecView is installed.

 

- The project subfolder has been copied onto this computer from a CD. When files are put onto a CD they are automatically made Read-Only, and they have to be manually made writeable again for the log data files to be written to. Instead use SpecView's Archive feature to archive & restore projects.

 

- The user has logged into the computer but doesn't have sufficient privileges to access and write files to the project's subfolder.

 

- The folder where the log files are put has been specifically changed to a different folder, which is now either non-existent or inaccessible to this user.

It is possible to specify a different folder to write the log files to by setting 'Path=C:\MyPath\' in the [Logging] section of SETTINGS.INI. However, it is VERY IMPORTANT that specified folder is on this computer, not on a network drive, in case of network failure.

 

E17813 Invalid Entry 2024/MM/DD HH:MM:SS

 

There is a date problem with SpecView Log Reports and Historical Replay in 2024 which gives the error,

for example: E17813 Invalid Entry 2024/01/02 08:25:00

 

For additional details, please read through the following page, E17813 Invalid Entry.