Cicode Programming Reference > Cicode Errors > Cicode and General Errors

Cicode and General Errors

The table below describes the general errors in Cicode.

Error No.

Error title

Description

0 No Error No error
32 The unit the tag is on has not been connected to yet When the error for a tag has specific values the tag test can show "#WAIT" for this error. This occurs for scheduled or Dial-up devices.
53 The tag is not known by the server being talked to at this time. The reason for a tag being unknown by the I/O or alarm system may not be that it does not exist, just that the server it is on is yet to come up and tell us about it. However, more often that not, it is because it does not exist.

55

Tag value is limited

Tag value is limited to be within range.

256

General software error

An internal Citect SCADA software error is detected. Contact Technical Support for this product and provide details on what causes the error.

257

Value is out of range

A numeric value is out of range. An out-of-range value has been passed to a function, or an array index is off the end of an array, or a value that is outside of the specified engineering scale has been assigned to a I/O Device variable. You can disable range checking on PLC variables with the CodeSetMode() function.

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

Path does not exist

The specified path to a device or file does not exist. During a function call (that tried to open a file), a non-existent path was specified. Call the function again with the correct path.

261

File does not exist

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 be detected if you try to call TrnDelHistory() on a file that has not been added using TrnAddHistory().

262

Cannot open file

The specified file cannot be opened. During a function call (that tried to open a file), the file could not be opened. There may be a mode error (for example, from trying to open a read-only file in write mode), or the file may be open by others, or the operating system resources may be too low to open the file.

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).

263

Cannot read file

The specified file cannot be read. Either an error has been detected during a read operation, or the end of file was unexpectedly found, or a disconnection from of the file server occurred, or the operating system is out of resources.

264

Cannot write to file

The specified file cannot be written to. During a function call (that tried to write to a file), a write error has been detected. There could be a disk full error, or a disconnection from of the file server may have occurred, or the operating system is out of resources.

265

Invalid file type

An attempt was made to open a file of the wrong type, for example, you tried to open an ASCII file as a dBASE file.

266

Field not found in file

The specified field does not exist in the device or database. A function that is trying to access an individual field in a database cannot find that field. Check that you have specified the correct field name and database name.

267

File mode is invalid

An operation has been attempted on a file or device that is of the wrong mode, for example, you tried to perform a seek on a printer device.

268

Key not found in file

The requested key was not found when a key search was performed on a database device, that is the record specified on an indexed search cannot be found. Either the record does not exist or you have specified the wrong key.

269

Bad handle specified

A bad handle has been passed to a function. You have called a function that requires a device handle, font handle, window handle, etc., but you passed a number that does not associate with a read device, font, or window (for example, you called WinGoto(100) when no window with the handle "100" exists). Check where the handle or number was retrieved from, and verify that it is the same handle. This error may also be detected if you have closed or destroyed the resource and you then try to access it.

271

No more free handles left

All the available file handles have been used, that is 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

Citect SCADA is out of memory. Increase the amount of memory in the computer or use smaller databases.

273

Divide by zero

An attempt has been made to divide a number 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.

275

Overflow

A calculation has resulted in a numeric value overflow. Check for operations that will generate large numbers.

276

No privilege for operation

A user has requested an operation for which he or she has no privilege.

277

Not in correct area

A user has requested data that does not belong to the current user area.

278

Report already busy

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

Report is late for execution

The report cannot run at the rate requested in the configuration. An attempt could have been made to run a report too frequently, and the required data cannot be read from the I/O Device(s) in time for the next report.

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

The specified Citect SCADA server cannot be found. Either the server is not running or there is some disturbance in the network. Check that the network is set up correctly, and you are using the same Server Name on both the client and server.

282

Foreground Cicode cannot block

You cannot block the foreground Citect SCADA task. You may have called a blocking function from one of the Page animation databases.

283

Trend has missed samples

The trend cannot run at the rate requested in the configuration. An attempt could have been made to trend the data too frequently, and the required data cannot be read from the I/O Device(s) in time for the next trend. Either increase the performance of the communication link to the PLCs or slow the rate of trend data acquisition.

284

Device is disabled

An attempt was made to access a device that is disabled. You can disable any devices (printers and other logging devices) with the DevDisable() function. When Citect SCADA (or your Cicode function) tries to access a disabled device, this message returns and all output is lost.

285

Foreground Cicode run is too long

The foreground Cicode task is taking too long to animate the display 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 mode and can run as long as required.

286

Out of Cicode threads

Citect SCADA has run out of Cicode tasks. Run fewer tasks (for example, 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 that do not finish.

287

Floating point exception trap

An invalid floating-point number has been found. Check the floating-point data from the I/O Device.

288

Out of buffers

Citect SCADA is out of dynamic buffers. You have called a function that requests buffer space but no buffers are available. Check which function is causing the error and increase the associated buffers, or slow the rate of transfer to that function. If the error occurs on a server or LAN device, increase the number of buffers with the [Lan]ReadPool parameter.

This error can also be detected if something is stopping the release of the buffers, for example, if network communication has stopped or a PLC has just come off-line. The error 'Out of buffers' can also be generated in the following ways:

Calling QueWrite() when the queue functions have run out of buffers. You can increase the number of queue buffers with the [Code] Queue parameter.

Calling WinFree() to free the last Cicode window. If WinFree() did free the last window, Citect SCADA would have no windows left.

To verify which function is causing the hardware error, display the {ERRPAGE} and {ERRDESC} fields on the hardware alarm.

289

Name does not exist

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 Citect SCADA format

The specified file is not in Citect SCADA format. The file (trend, 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 been detected. 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.

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

An attempt has been made to read an element from an empty queue.

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 detected error.

299

Cancelled

The specified form or command was cancelled. This error is returned when a user presses the Cancel button on a form. The normal procedure is to abort the operation.

300

Trend not found

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

Trend pen not found

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

Trend data not valid

The requested trend data is not valid. Either the I/O Device data was bad, or the Citect SCADA trend server was shut down, or the trend data was disabled.

303

Invalid animation number

The AN specified in the function is not defined. You called one of the DspXXX animation functions, but you specified an animation number that was out of range or that had been deleted.

304

File server inoperative, stand-by active

Citect SCADA has detected that a file server has become inoperative, and will switch to the standby file server. The file server's inoperative condition is due to errors of the network or of the file server computer. This error is displayed only if you have enabled redundant file servers. If a redundant file server is not enabled, Citect SCADA and Windows become inoperative when the file server becomes inoperative. You should report this error to the operators to fix the file server.

305

Conflicting types of animation

The same AN is being used for two different types of animation. This error is detected if you try to display two (or more) incompatible types of animation on the same AN (for example, you try to display a symbol at a AN where a bar graph is already displayed). Check the configuration. If you need to display a new animation, you need to first delete the old animation with the DspDel() function.

306

SQL field value truncated

A maximum of 1000bytes (1Kb) can be returned from a single field call. If the field data is larger than this limit, it is truncated. You have tried to access a database where one of the fields is greater than 1000 bytes in size. Change the database field size to less than 1000 bytes so it can be accessed. In fact, you should change the field size to less than 256 bytes, the maximum allowable length of a Cicode string.

307

SQL database error

A general SQL error. Call the SQLErrMsg() function for details of the detected error.

308

SQL null field data returned

Data has been requested from a field that contained no data, or the SQL server does not support this type of field data. Citect SCADA will return an empty string. Call the SQLFieldInfo() function to list the fields in the database.

309

Trend data is gated

You have requested trend data that was gated (set to logging disabled) by the trigger expression (that is when it was acquired). The data is returned with the gated values set to 0.

310

Incompatible server version

Two servers are running incompatible versions of the Citect SCADA software. Install the latest version on each server. Contact Schneider Electric Technical Support to arrange for an upgrade.

311

Alarm tag synchronize error

When the Alarm server shuts down it writes an alarm save file. If the 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 an alert only.

312

MAPI generic error

A generic MAPI error has been detected. Call the MailError() function to retrieve the MAPI error.

313

No MAPI

The MAPI mail system is not installed, or incorrectly installed on the computer.

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

No mail was available. This message is returned from the MailRead() function if no mail is available.

316

dBASE record locked by another

The dBASE file is being accessed by another user. Check if the dBASE file has been opened in exclusive mode by the other user. This error can also be detected if another user is updating the dBASE file, and will usually 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

Not in this version

The operation is not supported in this version of Citect SCADAor view-only client. You need to upgrade to a higher version of Citect SCADA or install a control client.

318

Invalid page function

You have called the PageGoto(), PageNext(), PagePrev(), PageDisplay(), or PageLast() as an exit command in the Pages database.

319

Low physical memory

Citect SCADA is low on physical memory. Increase available physical memory (not virtual memory). Reduce the size of SMARTDRV cache, close any other windows programs that are running, or add more RAM to your computer. You can set the minimum size of memory required by Citect SCADA with the [Memory]MinPhyK parameter. This parameter sets a value for the minimum physical memory before Citect SCADA will generate this error message.

This error may also be detected if your swap file is large (that is greater than 20 Mb). Reduce the size of your swap file. The swap file is configured with the Windows Control Panel (386 Enhanced icon).

320

Cannot free window

The WinFree() function has been called but Citect SCADA has no windows left. (Be aware that the last window and any child windows owned by the last window cannot be removed.)

321

Font cannot be found

The specified font cannot be found. Check the font name.

322

Cannot connect to LAN

Citect SCADA has detected an error on the network.

323

Super Genie not Associated

A Super Genie variable has not been associated correctly. This error can be detected if a variable passed to the Super Genie is the wrong data type or the variable does not exist. The error will also be detected 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

Could not run the Citect SCADA compiler

The Citect SCADA compiler could not be found. Either the computer has run out of memory, or the compiler has been removed from its directory.

327

User type not found

An attempt was made to create a user of a type that has not been defined in the users database.

328

User already exists

An attempt was made to create a new user with the same name as an existing user.

329

Cannot have mixed trends

An attempt was made to display both a periodic trend and an event trend in the same trend window. Check the project configuration (Trend Tags and Page Trends databases) for mixed trends displayed in a trend window.

336

Event type trend is expected

One of the arguments passed to this trend function is only valid for event type trends.

337

Trend in file does not exist

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

Plot functions are to be written in sequence since they depend on the data set up by other plot functions. Please refer to the description section for each Plot Function for the order of plot functions.

339

Plot Marker is not Defined

An undefined plot marker symbol has been used. Use the PlotSetMarker function before the PlotLine, PlotXYLine or PlotMarker functions.

340

Invalid subgroup size

The subgroup size specified for this SPC trend is not valid.

341

Trend Cursor Disabled

The trend cursor is currently disabled.

342

Debug break

The DebugBreak() Cicode function has been called. This indicates an invalid condition detected in user written Cicode. Enable the Cicode debugger to find the cause of the problem.

343

Foreground Cicode cannot break

A breakpoint has been hit in foreground Cicode. Foreground Cicode cannot be blocked. You can disable this error message in Debug Options, accessed through the Debug menu in the Cicode Editor.

344

Format overflow

This error occurs when the string being used to return an error message is not long enough for the information to go into it.

345

Data not ready

This error is returned when the requested data is not ready to be returned. Try again later.

346

Dynamic Out of licence points

The dynamic point count has exceeded the point limit. See Citect SCADA Licence Point Count.

347

Assertion did not succeed in user Cicode

An assertion in your Cicode has been proven FALSE, and the task terminated. Assertions are made using the Assert() function. If you set the [Code]DebugMessage parameter to 1, the assertion is logged and the operator prompted.

348

Property does not exist

The tag property does not exist.

350

RDB file not found

A RDB file is not found. Try a full compile and re-start.

353

Cannot connect to FTP

Problems connecting to the FTP server for file copy. Check that the service is running correctly by using a 3rd party tool outside Citect SCADA.

354

Unrecognized object class

The automation object to be used is not known or registered.

355

Object has no interface

The automation objects interface no longer exists. This is either a logic or code error.

356

Object automation exception

Generic automation exception code for logging issues.

357

Too many arguments

Formatting issues likely due to too many arguments (automation)

358

Too few arguments

Less arguments available than expected (automation)

359

Named object already exists

An object tried to be created when it was already existed and it was not expected to exist. Check your cicode (automation)

360

Unrecognized named object

The name of an object did not match the internal records. Check your cicode (automation).

361

Page CTG/RDB record mismatch

An animation object id was not found in the records. Try a full compile and re-start.

362

Object event queue flooded

Citect SCADA has run out of Cicode tasks while processing ActiveX events. Create fewer concurrent ActiveX events, or increase the number of tasks with the [Code]Threads parameter.

363

Incorrect number of arguments

Internal error in cicode handling of objects. Try a full recompile and restart.

364

No 'this' argument

Internal error in cicode handling of objects. Try a full recompile and restart.

367

File cannot be printed

Unable to print the specified file on the specified port.

368

Animation number invalid

Unable to display the animation at the given AN.

369

Wrong type for text display

Unable to display the given animation as text.

370

No FileFind instances to close

There are no FileFind instances to close.

371

No dialback response returned

The retry count for the dialback response has been exceeded.

372

Unrecognised ActiveX object

The ActiveX graphics data was unable to be loaded as it is an unrecognised object.

374

Date Time Conflict

A Date and/or time conflict has been detected. If you are attempting a TrnAddHistory(), verify that the file you are adding does not have a conflicting time or date with existing trend files.

375

Password Expired

The password has expired. Change password or adjust the [General]PasswordExpiry settings.

376

Error Writing to Files of Trend

An error has occurred while attempting to write to a trend file.

377

Error Reading Files of Trend

An error has occurred while attempting to read from a trend file.

379

Cannot modify field

The Users.DBF cannot be modified by direct user manipulation.

380

Name Exists

The user name specified already exists in the Users.DBF.

381

File Format Error

The file is not in the desired format. It may be corrupted.

382

Page data / variable tag data mismatch

Page data / variable tag data mismatch with tag-based driver.

384

The code this queue/semaphore was waiting for exited due to an error

Cicode task has been flagged as locked or inactive. This will not apply if a Cicode task was killed deliberately by the Cicode logic.

385

Cannot download websignature.xml

Unable to download the webclient signature file.

388

OID check disabled

Attempting to open a DBF file without checking to see if it has changed.

391

Unsupported Cicode function in Citect Web Client

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 client.

392

Timeout from Rnd Alarm Server

The timeout for receiving alarm data from the redundant alarm server has been exceeded.

393

RDB and associated page mismatch

The RDB page version does not match the one expected after compilation.

394

Remote license lost

The remote licence can not be found.

400

Project or file is Read-Only

The operation could not be completed because the project or file is read only.

401

Redundant server not found

The redundant server is current not available or was not found.

402

Cluster not specified

Cicode call is ambiguous because no cluster was specified.

403

Cluster not found

The provided cluster name was not seen as a valid cluster name.

404

Cluster name and tag mismatch

A cluster name and a tag with a cluster name prefix were both passed, but they do not match each other.

405

Cluster not connected

The operation cannot continue as the cluster is not connected.

406

Cluster already connected

The operation cannot continue as the cluster is already connected.

407

Databrowse pending

Databrowse session currently being connected and is not yet available for further commands.

408

Databrowse not supported

This normally means that data has been requested from the wrong client / server type, that is a client request on a server or vice versa.

409

Databrowse type not found

Browse type unknown. Check that the versions of citect32 are the same.

410

Databrowse session not found

iSession handle is invalid.

411

Databrowse session exists

Cannot open a session as it already exists.

412

Databrowse session EOF

Cannot browse beyond end of file. No more records left in the browse.

413

Databrowse field not found

The specified field is not present in the file.

414

Databrowse invalid field

The specified field is not valid for this browse function.

415

Databrowse no command

Browse command unknown. Check that the versions of citect32 are the same.

416

Databrowse no next cluster

Internal flag that all clusters have been processed. Users use this in cicode to determine that there are no more clusters.

417

Cluster required for operation

The operation cannot continue as the cluster is required for operation of a server.

418

No server of type on cluster

There is no server of the required type configured on the server.

419

Client / Server ID mismatch

An ID given to a Cicode function is not of the correct type.

420

Not available outside process

This functionality is not available outside a process boundary for example, AlarmFirstCatRec is only able to be called from inside the Alarm Server process.

421

Invalid tran handle detected

Citect's internal communications subsystem detected an error while trying to send a message.

422

Dial call did not succeed

An attempt to make a call to a remote I/O device did not succeed. You can find more information on the cause of this problem (if it is reproducible) by setting [Dial]Debug=1 and [Dial]DebugLevel=3 and looking in the syslog.dat.

423

Waiting for initial data

Occurs when attempted to read the value before the initial value has been retrieved from the device.

424

Tag not found

Occurs when attempt to read or subscribe to a tag that does not exist.

425

No connector

Not used.

426

Write to named pipe did not succeed

An attempt to send a message via a name pipe has did not succeed.

427

Redirect from non-Cicode task

A function cannot be redirected to another component as a proxy RPC unless it is in the context of a Cicode call.

428

Data browse record is invalid

The specified record is not valid for this browse function.

429

Can't plot symbol to printer

The Cicode PlotMarker() function can only plot a symbol to the display. This error occurs when the PlotMarker() Cicode function is used with a user-defined marker and a printer was specified as the output when PlotOpen() was called.

430

Alarm sort parameters mismatch

The [Alarm]SortMode parameter value on client is different as compared to the value on the alarm server. This value should be same in order to display alarms in correct order on the client.

431

Summary sort parameters mismatch

Values for [Alarm]SummarySort and [Alarm]SummarySortMode parameters on client are different as compared to the values on the alarm server. These values should be same in order to display alarm summary in correct order on the client.

432

Property not ready

A specific tag property has been read in synchronous mode, before the value has been retrieved from the server. (similar to subscription value is pending)

433

Cicode type mismatch

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

434

Invalid data conversion

Attempt to convert a value to a type that cannot store the value for example, ULong to Long, and the value is greater than the Long type can handle.

436

User password invalid

The password is incorrect. Check that the user name and password are typed in correctly.

437

Unable to load security provider

Cannot load or initialize the Windows security provider. This indicates that the installation of operating system may be corrupted or the Windows security provider was not included.

439

Authentication did not succeed

Cannot authenticate the given Windows user name and password. Check that the user name and password are typed in correctly

440

Authentication session does not exist

Cannot find the authentication session during the authentication process for the Windows user. This indicates that there was miscommunications in between client and server.

441

Role checking did not succeed

Cannot perform the role-check process for the Windows user. Check that the roles database in the project is not corrupted.

442

No linked role

The given Windows user is not linked to any role defined in the project.

443

Acquire user credentials did not succeed

Cannot obtain the user credential handle from Windows.

444

Acquire user access token did not succeed

Cannot obtain the user access token. This indicates that the security context of the Windows user was invalid.

445

Encrypt data did not succeed

Cannot encrypt the user information during the Windows user authentication process. This indicates that the security context of the Windows user was invalid.

446

Decrypt data did not succeed

Cannot decrypt the user information during the Windows user authentication process. This indicates that the security context of the Windows user was invalid.

447

The name of the table can not be found in the kernel.

Cicode UsrKernelTableInfo() has asked for a table that does not exist.

449

Invalid logout

The logout was called when there is no one logged in or the logged on user is system default user.

450

Invalid tag data

Invalid tag data has been detected.

453

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.

457

Old and new SQL functions mixed

An attempt has been made to terminate a SQL session by calling SQLDisconnect when it was opened by SQLCreate and SQLOpen, or by calling SQLClose and SQLDispose when it was opened by SQLConnect.

512

Time out error

Did not execute requested action on time.

513

Access denied error

Access denied to perform requested action.

514

Write unsuccessful

Can not write to view-only client. User needs to login with valid user credentials to get write access and to control alarms.

517

Can't swap pages from foreground

Cannot swap the page on foreground cicode.

518

Too Many arguments for function

Too many arguments have been passed to a Cicode function. Check the number of arguments being passed to the function. If arguments are input directly from the operator, you should check that the correct number of arguments are being passed to the function.

519

Remote cicode call Interrupted

Cicode call that triggers an RPC remote call is interrupted before the expected result is returned.

520

Alarm category out of range

A category number is out of its valid range (from 0 to 16375 inclusively).

521

Data browse record is deleted

A record is deleted during reload of ART server.

522

Trend archive property mismatch

A trend records archive properties are changed during start-up or reload.

523

Alarm priority out of range

A category priority is out of its valid range (from 0 to 255 inclusively).

524

ComBreak is obsolete parameter

[Page]ComBreak and [Page]ComBreakText are obsolete parameters.

525

Tag in Last Usable Value

Tag quality is uncertain and its value is the last usable value.

526

Tran authentication unsuccessful

Login did not authenticate correctly.

527

High watermark reached on Tran

High watermark is reached on transaction, network is overloaded.

528

Reduced size of resized page

The specified resized page has been reduced in size to fit the constrains of the maximum height and width of 4096.

529

Too few arguments

Too few arguments have been passed to a Cicode function. Check the number of arguments being passed to the function. If arguments are input directly from the operator, you should check that the correct number of arguments are being passed to the function.

530

Null pointer as an argument

A string with invalid pointer has been passed to SCADA execution system.

532

Tag resolve timeout Server responses to tag exists requests have timed out.
533 Server reload before initialize The attempt to initiate a server side online change did not succeed because the server has not been fully initialized.
534 Server reload not prepared The attempt to reload the main alarm server when the non-main alarm server is not reloaded first.
535 Alarm command partial success An alarm command has succeeded on at least one cluster but has been unsuccessful on at least one other cluster in a multi cluster environment.
536 No record found for the operation Indicates that for the given scope there is no record found for the requested operation.
537 Operation unsuccessful Indicates that the requested operation was unsuccessful.
540 Database not connected The connection to database, such as the alarm runtime database has not been established. This could be the hosting server such as the alarm server is not available, or the logon to the database was unsuccessful.
543 XML Exception Load or parse error in the xml.
544 Invalid Xpath expression Invalid Xpath expression.
545 Invalid XML operation Invalid operation on an XML document
546 Exceeded XML Boundary Exceeded the boundary, unable to add more to xmlDocument or xmlNode.
547 Exceeded Boundary Cannot create a new connection or transaction, boundary exceeded.
548 Invalid Proxy dll Specified dll is not a valid proxy dll.
549 Missing Proxy Method Specified method cannot be found in proxy dll.
550 Invalid Proxy Method Specified method cannot be invoked from proxy dll.
551 Ambiguous Proxy Method More than one method in proxy dll matches the binding criteria.
552 Invalid OP Proxy Method The method in proxy dll has one or more unspecified parameters.
553 Proxy Load Error Cannot load proxy dll.For example, proxy dll may have a dependency that cannot be found.
554 Transaction Process Error Other errors occurred when processing a transaction. The transaction cannot be processed.
555 Invalid URI Web service address provided is not valid/well formed URI.
556 Transaction not ready Not all parameters are loaded before processing the transaction.
557 Tag Name Exceed Length Tag name exceeds the 254 character length limit.
559 CiVBA is not supported when an alarm server is in Ext Mem mode A call to CiVBA code is not supported when an alarm server is operating in Extended Memory mode.
560 ActiveX is not supported for x64 when an alarm server is in Ext Mem mode A call to an ActiveX function is not supported when an alarm server is operating in Extended Memory mode.
561 AlarmSum index not current. The index passed to AlarmSum* functions must be current. I.E. either:
- the index returned by most recent call to AlarmSumFirst/Last/Find/Next/Prev, OR
- the index returned by the most recent call to AlarmSumAppend/Split
562 AlarmSum not initialized The alarm sum session needs to be initialized, by calling AlarmSumFirst/Last/Find, before AlarmSumNext/Prev is able to be called.
563 AlarmSum busy AlarmSum* functions should not be called from multiple concurrent cicode tasks. If busy this error will occur.
564 AlarmSum record deleted The alarm summary record represented by the index is deleted.
565 AlarmSum invalid field name The alarm summary cicode function does not accept the specified field name.

Windows Socket Error Codes

The following Citect SCADA error codes are mapped to standard Windows socket errors. Generally these errors are beyond Citect SCADA's control, that is, there is a external reason why Citect SCADA cannot use the TCP/IP connection (assuming there are no Citect configuration issues).

Error No.

Error title

Description

1330

WSAENETDOWN

(10050) Network is down.

1331

Socket unreachable

(10051) Network is unreachable.

1332

Network reset

(10052) Network dropped connection on reset.

1333

Connection aborted

(10053) Software caused connection abort.

1334

Connection reset

(10054) Connection reset by peer.

1335

No buffers available

(10055) No buffer space available.

1340

Socket timeout

(10060) Connection timed out.

1341

Connection refused

(10061) Connection refused.

1343

Name too long

(10063) Item Name too long.

1344

Host down

(10064) Host is down.

1345

Host unreachable

(10065) No route to host.

Published November 2016