Citect V7.0 Error Codes
Citect V7.0 Error Codes
Summary
List of hardware alarms.
Error
No.
Error title
Description
256
General software error An internal CitectSCADA software error is detected. Contact Citect
Support and provide details on what causes the error.
257
258
Buffer has been overrun A buffer has been overrun. More data has been passed to a function
than it can write to its temporary buffers. Try again by calling the
function twice, with half the data in each call.
259
Array has been overrun An array passed to a function is too small for the data requested.
Define a larger array or reduce the maximum data size requested.
260
261
The specified file or device does not exist. During a function call
(that tried to open a file), the file could not be found. Call the
function again with the correct file name. This error will also occur
if you try to call TrnDelHistory() on a file that has never been added
using TrnAddHistory().
262
Check that the file does exist (use File Manager), and that you have
the correct rights to open it. (Check with your network supervisor
that you have correct rights to open the file).
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 2 of 13
263
264
The specified file cannot be written to. During a function call (that
tried to write to a file), a write error occurred. There could be a disk
full error, or a loss of the file server may have occurred, or the
operating system is out of resources.
265
An attempt was made to open a file of the wrong type, e.g. you tried
to open an ASCII file as a dBASE file.
266
267
268
The requested key was not found when a key search was performed
on a database device, i.e. the record specified on an indexed search
cannot be found. Either the record does not exist or you have
specified the wrong key.
269
271
All the available file handles have been used, i.e. too many files or
databases are open at the same time. Open fewer files at one time or
increase the number of file handles in the [CtEdit]DBFiles
parameter.
272
Out of memory
273
Divide by zero
274
Invalid argument passed An invalid argument has been passed to a Cicode function. This is a
general error message and is generated when arguments passed to a
function are out of range or are invalid. Check the value of
arguments being passed to the function. If arguments are input
directly from the operator, you should check that the correct
arguments are being passed to the function.
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 3 of 13
275
Overflow
276
No privilege for
operation
277
A user has requested data that does not belong to the current user
area.
278
A request has been made to run a report that is already running. You
can get the current state of a report with the RepGetControl()
function. You can ignore this error message (because the report is
already running).
279
280
Invalid report ID
specified
The specified report name does not exist, or the user has no privilege
to run the report, or the report is not in the current user area. Check
the name of the report and the current user's privilege and areas.
281
No server could be
found
282
Foreground Cicode
cannot block
You cannot block the foreground CitectSCADA task. You may have
called a blocking function from one of the Page animation databases.
283
284
Device is disabled
285
Foreground Cicode run The foreground Cicode task is taking too long to animate the display
is too long
page. The Cicode is too complex and is taking too long to execute.
Simplify the Cicode that is animating the page, or increase the
[Code] TimeSlice parameter. If you cannot simplify the Cicode, you
can create a separate task using TaskNew() to calculate your
complex operation, and then use the Display functions to display the
results. Cicode running from a TaskNew() call is in background
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 4 of 13
CitectSCADA has run out of Cicode tasks. Run fewer tasks (e.g.
reports, key commands, and Cicode tasks) in parallel, or increase the
number of tasks with the [Code]Threads parameter. This error can be
caused by a configuration error if you keep creating tasks but do not
"kill" them when they are no longer required.
287
Floating point exception An invalid floating-point number has been found. Check the
trap
floating-point data from the I/O Device.
288
Out of buffers
289
The specified name does not exist in this context. You are probably
using the wrong name.
290
Not finished
A request has been made for trend data that has not yet finished
trending.
291
File not CitectSCADA The specified file is not in CitectSCADA format. The file (trend,
format
graphic, or any other file) is in an invalid format. Check that the
name of the file is valid or that the file has not become corrupted.
292
Invalid function
The specified function name does not exist. You have tried to create
a task, or called a remote procedure, or set an event function that
does not exist.
293
File error
A general file error has occurred. Either a general hardware error has
occurred, or the operating system is out of resources, or the file
server is down.
294
File EOF
The end of the file was found. An attempt was made to read data off
the end of a file or database.
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 5 of 13
295
Cicode stack overflow A Cicode evaluation stack overflow has occurred. There are too
many local function variables or nested function calls. Reduce the
number of local variables or increase the [Code] Stack parameter.
The Cicode stack is used to store local function variables and
function calls. If you have many nested functions and a large number
of local function variables, the Cicode stack may overflow. When
the Cicode stack overflows, the Cicode that caused the overflow is
halted.
You can estimate the size of the stack by counting the maximum
number of local function variables in the deepest function calls. For
example, if function A has 10 variables and calls function B with 30
variables, which calls function C with 40 variables, the stack needs
to be 10 + 30 + 40 = 80 deep.
296
Queue empty
297
Semaphore owner died The owner of a Cicode semaphore was halted, killed, or returned
without releasing the semaphore. Reset the shared resource back to a
known state (because the task that died may have left it in a mess),
and then continue. For example, if you are sharing a printer, do a
form feed.
298
Semaphore timeout
The requested semaphore was still in use after the specified timeout.
Either try to get the semaphore again or abort the operation and tell
the operator of the error.
299
Cancelled
300
The trend does not exist at the specified AN and page. A trend
function may have been called when the trend is not defined for that
AN.
301
The required trend pen name does not exist in the Trends database or
is not in the current user area. Check that the pen name exists and
check the current user's privilege and area.
302
The requested trend data is not valid. Either the I/O Device data was
bad, or the CitectSCADA trend server was shut down, or the trend
data was disabled.
303
Invalid animation
number
304
File server failed, stand- CitectSCADA has detected a file server fail condition, and will
by active
switch to the standby file server. The file server is down due to
failure of the network or of the file server computer. This error is
displayed only if you have enabled redundant file servers. If a
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 6 of 13
Conflicting types of
animation
306
307
308
Data has been requested from a field that contained no data, or the
SQL server does not support this type of field data. CitectSCADA
will return an empty string. Call the SQLFieldInfo() function to list
the fields in the database.
309
You have requested trend data that was gated (set to logging
disabled) by the trigger expression (i.e. when it was acquired). The
data is returned with the gated values set to 0.
310
Incompatible server
version
311
Alarm tag synchronize When the Alarm server shuts down it writes an alarm save file. If the
error
alarm server is in tag mode (rather than record mode) this message
will display. You can set the mode with the [Alarm]SaveStyle
parameter. You can ignore this message as it is a warning only.
312
313
No MAPI
314
MAPI offline
The computer is not logged on to the MAPI mail system. Call the
MailLogon() function to log on to the MAPI mail system.
315
MAPI no mail
316
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 7 of 13
by another
dBASE file has been opened in exclusive mode by the other user.
This error can also occur if another user is updating the dBASE file,
and will most likely occur if it is an indexed database, and the file is
on a slow file server. You can adjust dBASE access with the
[General]LockRetry and [General]LockDelay parameters.
317
318
319
320
21
322
LAN Failure
323
A Super Genie variable has not been associated correctly. This error
can occur if a variable passed to the Super Genie is the wrong data
type or the variable does not exist. The error will also occur if the
Ass() function has not been called for the variable.
325
Project is not compiled Changes have been made to the project while the system was
running. Either restart the system or shutdown and re-compile.
326
327
An attempt was made to create a user of a type that has not been
defined in the users database.
328
An attempt was made to create a new user with the same name as an
existing user.
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 8 of 13
329
336
One of the arguments passed to this trend function is only valid for
event type trends.
337
The trend name inside the trend file does not exist in the trend
database. It is likely that the trend file belongs to a trend which is
deleted from the system configuration.
338
Plot Functions
Sequence Mismatch
339
342
Debug break
343
Foreground Cicode
cannot break
344
Format overflow
345
346
Dynamic Out of licence The dynamic point count has exceeded the point limit. See
points
CitectSCADA Licence Point Count.
347
Assertion failed in user An assertion has failed in your Cicode, and the task terminated.
Cicode
Assertions are made using the Assert() function. If you set the
[Code]DebugMessage parameter to 1, the assertion logged and the
operator prompted.
353
FTP Failure
354
Unrecognized object
class
355
356
Problems connecting to the FTP server for file copy. Check that the
service is running correctly by using a 3rd party tool outside
CitectSCADA.
The automation object to be used is not known or registered.
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 9 of 13
358
359
360
361
362
363
Incorrect number of
arguments
364
No 'this' argument
374
375
Password Expired
379
380
Name Exists
381
382
Page data / variable tag Page data / variable tag data mismatch with tag-based driver.
data mismatch
Cicode task has been flagged as dead. This will not be an issue if a
cicode task was killed deliberately by the cicode logic.
The code this
queue/semaphore was
waiting for exited due
to an error
A number of cicode functions can only be run in a non Web context.
This
error is flagging that such a function was tried from a Web
Unsupported cicode
function in Citect Web client.
Client
384
391
402
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 10 of 13
403
The provided cluster name was not seen as a valid cluster name.
404
A cluster name and a tag with a cluster name prefix were both
passed, but they do not match each other.
405
406
Cluster already
connected
407
Databrowse pending
408
Databrowse not
supported
409
410
411
Databrowse session
exists
412
Databrowse session
EOF
413
414
Databrowse invalid
field
Browse type unknown. Check all versions of citect32 are the same.
415
Databrowse no
command
416
Databrowse no next
cluster
417
418
No server of type on
cluster
419
Client / Server ID
mismatch
420
Internal flag that all clusters have been processed. Users use this in
cicode to determine that there are no more clusters..
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 11 of 13
process
421
422
423
Subscription value is
pending
Occurs when a tag has been subscribed to, and attempted to read the
value before the initial value has been retrieved from the server.
424
Occurs when attempt to read or subscribe to a tag that does not exist.
425
No connector
Not used.
426
427
428
429
430
431
Summary sort
parameters mismatch
432
433
Some server side changes are now allowed for cicode, without
restarting the client. This means that now it is possible to change a
tag type to one that now cannot be converted as it was before. Eg val
= TagA - TagB, If TagA has been converted from Integer to String,
then the cicode will raise a cicode type mismatch as the '-' operation
is not supported for strings
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 12 of 13
434
Invalid data conversion Attempt to convert a value to a type that cannot store the value e.g.
ULong to Long, and the value is greater than the Long type can
handle.
435
437
439
Authentication failed
440
441
Authentication session Cannot find the authentication session during the authentication
does not exist
process for
the Windows user. This indicates that there was
miscommunications in
between client and server.
Cannot perform the role-check process for the Windows user. Make
sure
the roles database in the project is not corrupted.
Role checking failed
442
No linked role
443
444
445
446
447
449
1280
1330
1331
1332
The given Windows user is not linked to any role defined in the
project.
Cannot obtain the user credential handle from Windows.
Cannot obtain the user access token. This indicates that the security
context
of the Windows user was invalid.
Cannot encrypt the user information during the Windows user
authentication
process. This indicates that the security
context of the Windows user was
invalid.
Cannot decrypt the user information during the Windows user
authentication
process. This indicates that the security
context of the Windows user was
invalid.
Cicode UsrKernelTableInfo() has asked for a table that
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009
Page 13 of 13
Related Articles
No Related Articles
Article Attachments
No Attachments
Related External Links
No Related External Links
mk:@MSITStore:D:\Control\Scada\Citect\Knowledge%20Base\CitectSCADA_KBas... 25/03/2009