Page tree
Skip to end of metadata
Go to start of metadata

Question:

What does this error message mean?

Context:

All versions of PVSS.

Version:

1.26

Background

WinCC-OA/PVSS sometimes gives cryptic errors! Here is an explanation of the ones we've come across. If you have a message to add, please feel free to contact us by following the Feedback link below.

IMPORTANT: ETM have recently started their own list of cryptic messages. If you cannot find your message in this Cern list, look at the messages page on the ETM Portal.

Our message explanations are in alphabetical order. Don't forget you can search for a string within the page when using most web-browsers.

Please note that the "NV" manager messages can also be produced by the "UI" manager (as of PVSS 3.6).

Message Text

Explanation

ABORT

Remarks: Seen in the PVSS Console Log file.

Cause: When two managers' -num}}s are the same. For example, the second Ctrl manager to start with {{-num 1 will "ABORT".

Remedy: Use a unique -num on each of your managers.

Cannot open >< for cerr/cout! (Message 1)
myPanel.pnl_ cannot be deleted (Message 2)

Remarks: These messages have only been seen occurring together and then only on Windows.
Message (1) was seen when first starting PVSS (i.e. the Project Administrator window). PVSS continued to run but we could not save any edits to any panel as Message (2) popped up!

Explanation 1: There was an incompatibility between PVSS and the setting of the Windows environment variable TEMP on the machine. Normally TEMP points to just one single directory. If you point TEMP to a path of directories, PVSS cannot cope. (The problem was reported to ETM in Nov. 2005.)

Cannot open >C:\ETM\PVSS2\3.1\log\PVSS00NV0.log< for cerr/cout!

This message can appear when starting the Project Administrator (PA). It means that your username does not have sufficient privilege to run this particular project, possibly because this project was created by someone else. For a full discussion of this message see the FAQ Which Windows privileges do I need to run PVSS-II V3.* ?

Can't copy something from IDP to archive description structure

Remarks: Produced by the valarch task at startup. Click for a Full explanation

On Linux: Can't fetchpvsspath , exiting

On Windows with WinCC-OA >= 3.12: Cannot fetch installation path from "C:\ProgramData\Siemens\WinCC_OA\pvssInst.conf"! Either the file doesn't exist or isn't readable or there is some error in file content or it is locked? ("C:/ProgramData/Siemens/WinCC_OA/pvssInst.conf.lck") Exiting...

${PVSS_II_ROOT}/ pvssInst.conf.lck gets left around in the "registry directory" after a crash. startPA then fails to startup and gives this message. Fix it by deleting the ".lck" file. (By default, PVSS_II_ROOT is assumed to be /etc/opt/pvss on Linux and C:\ProgramData\Siemens\WinCC_OA on Windows)
Alternative explanation: You do not have appropriate disk write access permission. See your system manager.

Alternative explanation 2: WinCC OA 3.15 - Installation, Distribution

Checking environment ...

From PVSStoolSyncTypes. See the note in the FAQ.

CreateDbResources::makeConfigFileWithoutLang rename failederrno: 2 (1), <dateTime> exit(1) called!

This message can appear when trying to create a new project in a path which contains space characters - as in "Documents and Settings". The workaround is to create your project in a path with no embedded space characters.

Das PVSS-II-Projekt name Liuft bereits!

Means "PVSS project name is already running."Error appears in German by default. The new instance cannot even get started well enough to identify your preferred language!

Driver number 1 is not running!

Seen when PARA starts up. Reason: The Simulation Driver with number 1 is not running. This driver is created automatically in every project. If you have deleted it, put it back!

ERROR: To archive you have to create shared directory

Click for a full explanation

Error creating Project! For further information see the log file: WINCCOA_PATH/log/PVSS_II.log

Have a look in the logfilein the "system tree" i.e. where WinCC-OA itself was installed (for example C:\Siemens\Automation\WinCC_OA\3.11\log\PVSS_II.log) for additional diagnostics. Then come back here and look in the list below for those new messages!

NB There is, of course, nologfilein your project folder that you can inspect - as your project failed to create!

If there is no file WINCCOA_PATH/log/PVSS_II.log in the system tree either, then this certainly means that your username is running without the necessary privileges. Please review the WinCC-OA installation instructions (ie get Local Admin privs).

WCCOAui (0), 2014.11.26 10:51:21.974, SYS, SEVERE, 7/pa, paCreateProjExtend, Error when creating the project 'C:/Projects/sillyProject'
WCCOAui (0), 2014.11.26 10:51:21.912, CTRL, WARNING, 73/pv2admin, Project creation failed for project sillyProject with error -1, no error

You are trying to create a project on a machine where another project is already running. Stop the running project; Delete the files ofyournew (incompletely created) project and try again.

Error creating project. Would you like to open <projectname>\log\createDb.log?

Your username does not have sufficient privilege to create a new project. For a full discussion of this message see the FAQ Which Windows privileges do I need to run PVSS-II V3.* ?

Error starting project monitor. See PVSS_PATH\log\PVSS_II.log

You have no privilege to write into the project folder. For a full discussion of this message see the FAQ Which Windows privileges do I need to run PVSS-II V3.* ?

Error writing to the temporary location

Popup window message. Typically observed during installation of PVSS. Occurs when you do not have administrator privileges on your computer. (You need local admin privilege!)

Failed to update the system registry. Please try using Regedit.

This popup can appear when starting a project from the PVSS console. You may safely ignore it and proceed as if nothing had happened! Yes, really! For a full discussion of this message see the FAQ Which Windows privileges do I need to run PVSS-II V3.* ?

Lost connection to Event Manager. Please save all data and restart this manager. Be aware that some actions might not work properly or even fail completely without communication to the Event Manager! <Quit now> <Try to continue>

Message from a dangling UI. In nearly 100% of all casesyou really will want to press "Quit Now!" Believeme. See also How do I avoid crash notification dialogs?

Missing or erroneous progs or config file! See PVSS_PATH\log\PVSS00pmon_<hostname>.log

This message can appear when you choose a project in the Project Administrator (PA). It can mean that your username does not have sufficient privilege to run this particular project, possibly because this project was created by someone else. For a full discussion of this message see the FAQ Which Windows privileges do I need to run PVSS-II V3.* ?

No changes can be made to this configuration: _alert_hdl

Click for a full explanation

PVSS00xxx (0), <TIMESTAMP>, SYS, FATAL, 158, Could not create the server socket on port = nnnn: Permission denied
PVSS00xxx (0), <TIMESTAMP>, SYS, INFO, 2, Manager Stop

See the FAQ Windows Port Allocation issue for a full explanation.

PVSS00<manager> (<num>), <TIMESTAMP-X>, <TYPE>, <PRIO>, <error-num>, info-text

and

PVSS00<manager> (<num>), <TIMESTAMP>, SYS, INFO, 119, Last error
repeated XXXX times.

In order to avoid filling the logfilewith endlessrepeated messages, PVSS will suppress adjacent repeats. Outputwill resume when a different message is written to the logfile. The message pair shown on the left is recorded in the logfile when output resumes.
Note that the timestamp <TIMESTAMP-X> refers to the time of the most recent occurrence of the repeated message (i.e. it does not refer to the time of the first suppressed message!)

PVSS00data0:PVSS00data(0), <TIMESTAMP>:error allocating 550134892 bytes of memory! exiting ...

The PVSS Data Manager (DM) has crashed because your database is corrupt. This can happen after a power cut.
1) Consider buying a UPS before it happens again!
2) See the FAQ "My PVSS database is corrupt!" We have certainly seen this message when the latest ("last") values database was corrupt.
You may well have to restore your PVSS system from your backup .

PVSS00data (0), 2005.04.12 18:05:45.297, IMPL, SEVERE, 54, Unexpected state, DataManDpIntern, refreshSaveDirList,Fehler beim lesen der Verzeichnissen!
and
PVSS00data (0), 2005.04.12 18:05:45.297, IMPL, SEVERE, 54, Unexpected state, DataManDpIntern, refreshAlertSaveDirList, Fehler beim lesen der Verzeichnissen!

After a project restore, these messages will appear if these directories do not exist:

<proj_path>/db/pvss/save

and

<proj_path>/db/pvss/alsave

You should simply create them by hand. The error will then go away.

PVSS00data (0), <TIMESTAMP>, IMPL, WARNING, 54, Unexpected state,
AlertAdministration, insertAlert, no gone alert between two came ones
< DP-Name>:_alert_hdl (<DP-ID>)

Click for a full explanation

PVSS00data (0), <TIMESTAMP>, IMPL, WARNING, 54,
Unexpected state, HistArchive, archive is offline: 2, cannot write
original value:

dist_1:myValue.C2.AVG_WT0:_original.._value (Type: 70 Sys: 1 Dp: 362 El:
6 Conf: 1 Det: 0 Attr: 0x20065)

Your Value Archive manager is not running. (The example on the left is complaining because manager number 2 is stopped.)

PVSS00data (0), <TIMESTAMP>, IMPL, WARNING, 54, Unexpected state,
PersAlertValue, loadSumAlert, nonexistent identifier in the ID-list (<unknown DP-Identifier>) referenced from sumalert
< DP-Element-Name>:_alert_hdl (<DP-Identifier>)

This message means that the dp-list in a sum-alert-handling that is configured at the dp-element <DP-Element-Name> refers to another dp-element <unknown
DP-Identifier> that no longer exists.
You should correct the sum-alert-config definition for dp-element <DP-Element-Name>.

PVSS00data (0), 2011.12.13 16:48:58.851, IMPL, SEVERE, 54, Unexpected state, AlertHistory, switchFiles,letzterDateiwechselnichtbeendet

The message is saying that you cannot switch to a new alert archive file because the previous file switch operation has not yet completed. There is a known problem (at least in PVSS3.8.2) whereby the fileswitchoperation never completes. Contact us for advice.

PVSS00data (1), 2003.06.20 11:03:44.597,PARAM,INFO , 1, "Manager Start", HistOrgMain connection from archive received - initializing archive number is: 0

ACE_ASSERT: file d:\workspace\exe\datanew\valuearchive\archivset.cpp, line5821 assertion failed for 'wrData.valChanged'.

{{6/20/2003, 11:03:46 AM: Manager terminated unexpectedly C:\ETM\PVSS2\2.12\bin\PVSS00valarch.exe -num 0 -log +file -config
C:\ETM\PVSS2\TEST\config\config -PROJ TEST}}

{{PVSS00data (1), 2003.06.20 11:03:46.262,SYS ,SEVERE , 63, "Connection
error", Manager: 3(DATA) 2 0
socket error(10054)}}

PVSS00data (1), 2003.06.20 11:03:46.500,PARAM,INFO , 2, "Manager Stop", HistOrgMain archive is now offline archive number is:0

Context: When a value archive manager is starting
Cause: The manager's Value Archive current file is corrupted.
Effect: The affected value archive manager will shutdown immediately.
[Click for a full explanation]

PVSS00data (0), 2008.12.02 22:01:22.969, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-4 (PROGRAMMER/USER error: -4
can not open dictionary
C errno = 5: Input/output error
FILE: inittab.c(87)), errno:5 (Input/output error) FATAL ERROR - Trying to exit

PVSS00data (0), 2008.12.02 22:01:22.969, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-906 (SYSTEM/OS error: -906
unable to open TAF or DBL or LOG file
C errno = 13: Permission denied
FILE: taffcns.c(356)), errno:13 (Permission denied)

PVSS00data (0), 2008.12.02 22:01:22.969, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-906 (SYSTEM/OS error: -906
unable to open TAF or DBL or LOG file
C errno = 13: Permission denied
FILE: dblfcns.c(314)), errno:13 (Permission denied)

PVSS00data (0), 2008.12.02 22:01:22.969, SYS, SEVERE, 69, Database error, TypeAndIdDb, open

(The above repeated 5 more times, then: )

PVSS00data (0), 2008.12.02 22:01:26.103, IMPL, SEVERE, 54, Unexpected state, DataManDpIntern, init, Datenbank konnte nicht geoeffnet werden!

PVSS00data (0), 2008.12.02 22:01:26.103, SYS, INFO, 0, , Loading DpIdentification

PVSS00data (0), 2008.12.02 22:01:26.120, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-1 (PROGRAMMER/USER error: -1
database not opened
C errno = 13: Permission denied
FILE: trxfcns.c(33)), errno:13 (Permission denied)

PVSS00data (0), 2008.12.02 22:01:26.120, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-27 (PROGRAMMER/USER error: -27
transaction not active
C errno = 13: Permission denied
FILE: trxfcns.c(264)), errno:13 (Permission denied)

PVSS00data (0), 2008.12.02 22:01:26.120, SYS, SEVERE, 66, Error when connecting, DataManager, initialize

PVSS00pmon (1), 2008.12.02 22:01:26.188, SYS, INFO, 11/pmon, Detected stopped manager PVSS00data(0) - restarting it #1

At project startup(project won't start!)
Is caused when the PVSS Project directory is not the last <proj_path> entry in the config file.
Correct your config file manually. Kill any stray PVSS processes and restart the project.
(NB See similar messages in the next table entry, below, also!)

PVSS00pmon (1), <TIMESTAMP>, SYS, INFO, 20/pmon, Got START_ALL command from 127.0.0.1, starting the project

PVSS00pmon (1), <TIMESTAMP>, SYS, INFO, 1, Manager Start, C:\ETM\PVSS2\3.8\bin\PVSS00data.exe -PROJ 381SupportProject -pmonIndex 1

PVSS00data (0), <TIMESTAMP>, SYS, INFO, 1, Manager Start, PROJ, 381SupportProject, V 3.8 - 3.8 SP1 linked at Apr 2 2009 04:48:28

PVSS00data (0), <TIMESTAMP>, SYS, INFO, 0, , (Re)Opening databases in single user mode without transaction logging.
PVSS00data (0), <TIMESTAMP>, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-4 (PROGRAMMER/USER error: -4
can not open dictionary
C errno = 13: Permission denied
FILE: inittab.c(87)), errno:13 (Permission denied) FATAL ERROR - Trying to exit

PVSS00data (0), <TIMESTAMP>, SYS, SEVERE, 69, Database error, ValHistDb, open, 0000000000\ValHist

PVSS00data (0), <TIMESTAMP>, IMPL, SEVERE, 54, Unexpected state, DataManDpIntern, init, Datenbank konnte nicht geoeffnet werden!

PVSS00data (0), <TIMESTAMP>, SYS, INFO, 0, , Loading DpIdentification

PVSS00data (0), <TIMESTAMP>, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-1 (PROGRAMMER/USER error: -1
database not opened
C errno = 0: No error
FILE: trxfcns.c(33))

PVSS00data (0), <TIMESTAMP>, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-27 (PROGRAMMER/USER error: -27
transaction not active
C errno = 13: Permission denied
FILE: trxfcns.c(264)), errno:13 (Permission denied)

PVSS00data (0), <TIMESTAMP>, SYS, SEVERE, 66, Error when connecting, DataManager, initialize

PVSS00data (0), <TIMESTAMP>, SYS, INFO, 2, Manager Stop

At project startup- project won't start.

You are logged in as somebody else - not the person who created and still owns this project. You do not have proper permissions on the files to start this project successfully.

Logout and login again as the correct user!

PVSS00data (0), <TIMESTAMP>, SYS, SEVERE, 69, Database error, StAHVariableUtils, loadVariable *** Code : 6

PVSS00data (0), <TIMESTAMP>, SYS, SEVERE, 69, Database error, StAlertRec, getAlertClass, Variablenicht ladbar

These log-messagesdescribe that an alert-classwas deleted but that some alert-handling-configs still refer to this alert class.

You should perform the following steps:
– make an ASCII-out of the _alert_hdl-config
– create a list of those dp-elements which are used as alert-classes
– check ifan _alert_class-config is added at all of thesedp-elements

PVSS00data (0), <TIMESTAMP>, SYS, SEVERE, 69, Database error, StAHVariableUtils, deleteVariable6

PVSS00data (0), <TIMESTAMP>, SYS, SEVERE, 69, Database error, AlertCacheItem, remove, Code :0
BIS3C02.bf:_alert_hdl.._value (Type: 0 Sys: 0 Dp: 217465 El: 40 : _alert_hdl.._value)

These messages can appear when the database for the "living"-alerts gets corrupted. The log-messagedescribes that an alert cannot be removed. Possibly you are seeing this log-messagebecause an alert is in state"gone and acknowledged" and hence is no longer shown in the "living"-alerts.

You could try to solve this problem with an initialization of alliving-database:
– ASCII-export of the alerts (config _alert_hdl)
– stop the project
– make a copy of the database, if value-archives are used these files do not need to be copied
– open a DOS-box/command-shell
– switch to the directory <project>/db/pvss/alliving
– start the command initdb -y AlertHist
– start PVSS00data and PVSS00event
– ASCII-import the alerts
– stop the project
– start the project

PVSS00data(0), 2010.12.08 17:09:01.421, SYS, SEVERE, 69, Database error, DataManTask, dbError, RAIMA Database Error *** Code:-909 (SYSTEM/OS error: -909 file record limit exceeded


See full description here

PVSS00databg (1), <TIMESTAMP>, IMPL, WARNING, 51, Parameter incorrect, DataBgDpIntern, openDatabases, Datenbank konnte nicht geoffnet werden, retry: 5

PVSS00databg (1), <TIMESTAMP>, SYS, SEVERE, 69, Database error, DbDirDb, open

PVSS00databg (1), <TIMESTAMP>, PARAM,FATAL, 54, Unexpected state, DataBgDpIntern, init, Datenbankkonntenichtgeoeffnetwerden,bitte lm_ippruefen!

The PVSS lock manager is not running properly. Stop the project and all PVSS tasks completely. Kill any stray PVSS lock manager ("lockmgr") task. Restart the project.

If this fails, try restarting the lock manager manually from your normal prompt (i.e. NOT from a root prompt!) with:

<pvss_path>/bin/lm_ip -a lockmgr -f 1600

for example, with:

/home/PvssSystems/3.0.1SP1/pvss2_v3.0/bin/lm_ip -a lockmgr -f 1600

PVSS00databg (1), <TIMESTAMP>, IMPL, SEVERE, 54,
Unexpected state, DataManDpIntern, refreshSaveDirList, Fehler beim lesen der Verzeichnissen!
PVSS00databg (1), <TIMESTAMP>, IMPL, SEVERE, 54,
Unexpected state, DataManDpIntern, refreshAlertSaveDirList, Fehler beim lesen der Verzeichnissen!

Can also be aassociated with the appearance of:

PVSS00databg (1), <TIMESTAMP>, SYS, SEVERE, 69,

Database error, DataBgActionManager, status record first/next-24

PVSS00databg (1), <TIMESTAMP>, SYS, SEVERE, 69,
Database error, RAIMA Database Error *** Code:-24 (PROGRAMMER/USER
error: -24
attempt to access unlocked set/record
C errno = 32: Broken pipe), errno:32 (Broken pipe)
PVSS00databg (1), <TIMESTAMP>, SYS, SEVERE, 69,
Database error, DataBgActionManager, status record first/next-24
PVSS00databg (1), <TIMESTAMP>, SYS, WARNING, 69,
Database error, PVSSStoreObj, ReadLock, retrying ReadLock ...

These lines appear in the log file every minute or so if the folders <PROJ_PATH>/db/pvss/save and <PROJ_PATH>/db/pvss/alsave do not exist.

Solution: Create these directories.

PVSS00dist (93), 2006.02.16 12:34:35.378, SYS, SEVERE, 65, Wrong destination address, (SYS: 1 Dist -num 1 CONN: 1), REDUNDANCY_SYS_MSG

PVSS00dist (93), 2006.02.16 12:34:35.378, REDU, INFO, 0, , Closing connection topassiv peer (SYS: 91 Dist -num 91 CONN: 1)

These messages appear in a distributed system scenario, in the log of a client system that is trying (and failing) to make a solid contact with another (server) system. These messages are followed by a "Connection lost" message. The message pair is often repeated as the connect operation is retried.

*Explanation: *The client is specifying a target PVSS system number on the server machine. Although a PVSS system is running on the server, it does not have that corresponding system number. In the example shown, the client (system number 93) was trying to contact system number 91. This was incorrect as the system number of the system that was actually running on the remote server machine was number 1.

Action: Correct the entry in the client system's config file where it says distPeer = "sysName" sysNumber. Then you should see a much nicer message such as: PVSS00dist (93), 2006.02.16 12:38:25.237, SYS, INFO, 4, Connected to, (SYS: 1 Dist -num 1 CONN: 1) @ pcitco91.cern.ch

PVSS00dist(n) ,SYS,SEVERE,159,Could not create the alive-server socket on port = 4500: Permission denied

This is not a username/permission problem. Rather, someone else is using that port. (In WXPSP2 it's the lsass task.)

PVSS00event (0), <TIMESTAMP>, IMPL, WARNING, 54, Unexpected state, DP: (Type: 221 Sys: 7 Dp: 945182 El: 2 : _original.._stime), MAN: (SYS: 7 Event -num 0 CONN: 1), EvDpManager::getDpValueAttribut: no element

User accidentally deleted some PVSS internal datapoints and thoroughly confused the Event Manager!

WCCILevent (0), 2015.06.17 15:12:02.369, IMPL, SEVERE, 54, Unexpected state, ElementTable, getElementFullName, Element/Parent element not found - Type 130, Element 47, Parent element 0
WCCILevent (0), 2015.06.17 15:12:02.368,PARAM,WARNING, 8, Element does not exist, DP: (Type: 130 Sys: 47 Dp: 308 El:47 : _original.._value), MAN: (SYS: 47 Data -num 99 CONN: 1)

You are trying to accessa aDP or DPE that no longer exists. Which one?Unfortunatelyit is not possible to retrieve the name of the DP/DPE - as it has been deleted! You may retrieve the Datapoint Type (DPT) name (which might give you a clue) by exporting everything with the Ascii Manager and looking in the .dpl file. Clearly, even that won't work if you have deleted the DPT as well !!

 

PVSS00event (1), <TIMESTAMP>,PARAM,WARNING, 54, "Unexpected state", dcs1:PLC1_AI_Val_Pression_Rich.value:_alert_hdl.3._alert_color Type: 0 Sys: 1 Dp: 8853 El: 2 Conf: 23
Det: 3 Attr: 524914 AlertTime: 2002.02.16;09:59:19,284 Count: 0 has more than 500 matching alerts

See the FAQ Too many pending alerts.

WCCILevent (0), 2015.02.20 15:24:26.023, SYS, SEVERE, 39, Connection lost, Send buffer limit exceeded, closing connection to (SYS: 32 Ui-num 1 CONN: 1) @ pcen33889.cern.ch, [PeerItcIOHandler::sendCall]

A similar message can be generated by any manager trying to send a message to another manager. This example was generated by the Event Manager trying to send to the UI. The UI was not absorbing messages quickly enough and the allocated EM output queue filled up.

This message, its causesand your possible actions, are described at length in the ETM FAQ :https://portal.etm.at/index.php?option=com_quickfaq&view=items&cid=26:logs&id=356:wincc-oa-managers-syssevere-send-buffer-limit-exceeded-closing-connection-to-connection&Itemid=54

You should also consider:

  • If your CTRL manager is the message source, are you inadvertently in a tight loop and using dpSet() rather than dpSetWait() to send messages?

Recall that the System Management Panel > Diagnostics tab > System Overview panel helps you tovisualiseoverall flows of message traffic in WinCC-OA.

 

PVSS00event (0), <TIMESTAMP>, IMPL, SEVERE, 54, Unexpected state, ElementTable, getElementFullName, Element/Vaterelement nicht gefunden - Type 144, Element 40, Vaterelement 0

A DPE that used to exist cannot be found any more.

PVSS00event (0), <TIMESTAMP>, PARAM,WARNING, 22, Internal consistency check for config failed, <DP-Element-Name>:_alert_hdl, MAN: (SYS: 1 Event -num 0 CONN: 1), SumAlert config does not have an id list nor an id
pattern to select DP elements

This message says that the sum-alert-config for <DP-Element-Name> is not configured correctly as there is neither a dp-list nor a dp-pattern defined.
Please correct the configuration by defining a validdp-list or adp-pattern (NB other than "*" ). Alternatively, if the config is no longer needed you can simply delete it.

PVSS00event (0), <TIMESTAMP>, PARAM,SEVERE, 92, DP functions: infinite loop found, DP: <DP-Name>:_dp_fct, EvDpManager::, handleDpFuncHL #1, check dp function

This log-message appears in 2 situations.

1) An infinite loop really is configured. E.g.

A dp-function on dpe A is set to react on a change in dpe B

AND

A dp-function on dpe B is set to react to a change in dpe A.

2) Yourdp-function was called more than 25 times with the same time-stamp on theinput-variables. You should check the configuration of thedp-elements which are used asinput-variables. (You should also check the configuration of where their values are coming from, eg your OPC group settings.)

PVSS00NV(n) , IMPL, SEVERE, 54, Unexpected State

[Click for more]

PVSS00NV (0), SYS, WARNING, 133, Could not load shared library

[Click for more ]

PVSS00opc (7), <TIMESTAMP>, SYS, SEVERE, 54, Unexpected state, OPCServer, initialize, Could not get CLSID for OPC20CanOpen+

Your OPC client cannot connect to the OPC Server.

WCCOAopc (7), 2014.07.09 15:14:06.024, IMPL, WARNING, 54, Unexpected state,
OPCServer, CheckSrvInterfaces, Server does not support
IOPCBrowseAddressSpace -> no browse info (Interfaccia non registrata.
(0x80040154))

The above message appears with:

WCCOAopc (7), 2014.07.09 15:14:06.024, IMPL, SEVERE, 54,
Unexpected state, OPCServer, CheckSrvInterfaces, Server does not
support IOPCServer -> server cannot be used (Interfaccia non
registrata. (0x80040154))

This is not a problem with WinCC-OA itself, but with your WinCC-OA OPC UA client trying to use the ELMB OPC Server from Atlas. The problem appears when certain libraries are not found in your installation.

Please (re-)install them as follows:

If your NICE PC is being managed with CMF:

    • From Named System Set (NSS) called IT Controls
    • Install the package: OPC Foundation x64 redistributable

If your NICE PC is not under CMF, you can access the two relevant files directly from DFS:

  1. G:\Applications\OPCCommon\MS VCPP redistributables\x64\vcredist2008_x64.exe
  2. G:\Applications\OPCCommon\OPC Foundation redistributables\OPC Core Components Redistributable (x64) 105.1\OPC Core Components Redistributable (x64).msi

Important: Please install (run) vcredist2008_x64.exe first and only then install the OPC Core Components Redistributable (x64).msi.

PVSS00opc (6), <TIMESTAMP>, IMPL, WARNING, 54, Unexpected state, OPCGroup:CAENOPCGroupIn, additem, AddItems returned Incorrect function.
(0x1) for RPCHV02CMS.Board02.Chan084.Rel

[Click for more ]

PVSS00opc (2), 2005.07.01 10:22:41.494, IMPL, WARNING, 54, Unexpected state, OPCGroup, groupGA, Could not start Refresh on MatrikonLocalGroup:Unspecified error
(0x80004005) There is no active item in the group.

Accompanied with:

PVSS00event (0), 2005.07.01 09:09:24.994,PARAM,WARNING, 7, Datapoint does not exist,DP: :_original, MAN: (SYS: 1 Driver -num 2 CONN: 1)

Means that your config file refers to an OPC server but that you have not yet defined that OPC server in the PVSS panel.

PVSS00opc ,WARNING, 54, Unexpected state,OPCGroup:MyOPCGroupName,start, No internal DP forgroup.Groupcannot be used!

Often encountered after incorrectly installing PVSS 3.1 patch P256. Check again in the file ReadmeP256.txt that comes with the patch.

PVSS00pmon (1), <Timestamp>, SYS, SEVERE, 38/pmon, The Port 4999 could not be opened.

See Why isn't my console behaving correctly?

{{PVSS00ui (1), <Timestamp>, CTRL, WARNING, 5/ctrl, Location of the following log entry:
Module: Vision_125
Panel: C:\PvssProjects\381FwSupportProject\panels\newTrendParentPanel.pnl []
Object: 38 named: "initScript" of type: PRIMITIVE_TEXT
In reference: fwTrending\fwTrendingTrend.pnl Group: 10 named: "trend"
used in: objects\fwTrending\fwTrendingFaceplate.pnl Group: 0
named: "hardwareChannelPlotConfiguration"
Script: Initialize
Library: C:\PvssProjects\fwComponents_20090826\scripts\libs\fwGeneral/fwException.ctl
Line: 106

PVSS00ui (1), <Timestamp>, IMPL, WARNING, 0, , The parameter sNameOfChannelToBeTrended was not specified, ,}}

This message is benign (smile) and can be safely ignored. See Location of the following log entry / fwException.ctl

PVSS00ui (11), <TIMESTAMP>, PARAM,FATAL, 54, Unexpected state, initUimDpIdentifiers, _Ui_11.LayerOn.PanelName, no such name

may also be seen with:

PVSS00ui (11), <TIMESTAMP>, PARAM,WARNING, 7, Datapoint does not exist, CtrlDbg::init, _CtrlDebug_UI_11.Command

You are trying to simultaneously run more UI managers than the system is configured for. Increase the number allowed by following the instructions described in this FAQ.

PVSS00valarch(13), 2012.04.10 11:57:00.092:error allocating memory! exiting ...
PVSS00valarch: NoPosix.cxx:253: static void NoPosix::newHandler(): Assertion `false' failed.

Can also provoke a Data Manager crash. Try adding the following entry into your config file:

[valarch]
maxNumberOfReadThreads=1

See a full description in Jira case ENS-5235 .

PVSS00valarch(11), 2012.04.10 12:00:57.516, IMPL, SEVERE, 54, Unexpected state, Didn't get any appropriate mapping, stopping read, [ArchivSet.cpp:5323]

Have you exceeded the Linux per-user limit on open files? See Which Operating System Settings may affect me?

PVSS00valarch(n) ,IMPL, WARNING, 54, Unexpected state, Archive, doFileRestore, Not all files in action.files are present (ErrNum=28), Couldn't find any from sets identified in list

PVSS00valarch(n) , IMPL, SEVERE, 54, Unexpected state, Archive, doFileRestore, The action can not be started (ErrNum=31), Error encountered during processing of doFileRestore

This message should not appear under normal circumstances. It implies that you have been fiddling around with the files in the Archive directories using Windows Explorer, i.e. without going through the PVSS panels. The message probably means that you have forgotten to copy youronline-backup(or at leastthe AR_X-files (where X is thearchive-number) from the VA-directories of an old system to the new system. (CT349326)

PVSS00valarch(n) , Severe, Unexpected state

[Click for more ]

setCerrLog():cannot open STDERR on C:\ETM\PVSS2.12.1\log\PVSSConsole.log,err=5!

Remarks: This message / these messages are sometimes seen soon after installing PVSS on Windows.

Cause: Lack of privilege.

Remedy: Ensure you have appropriate rights on your machine. You need extensive rights to install PVSS properly. If you installed PVSS without these rights initially then you will need to re-install PVSS all over again, sorry!

If PVSS was installed OK but you need to simply run, you may need different rights.

See Which Windows privileges do I need to run PVSS2 V3.*?

unspecified user id
C errno = 13: Permission denied
FILE: initenv.c(120)), errno:13 (Permission denied)

PVSS00data (0), 2007.09.17 14:03:11.068, SYS, SEVERE, 69,
Database error, TypeAndIdDb, open

PVSS00data (0), 2007.09.17 14:03:11.088, IMPL, WARNING, 51,
Parameter incorrect, DataManDpIntern, reopenDataBase, Datenbank konnte
nicht geoffnet werden, retry: 1

PVSS00data (0), 2007.09.17 14:03:11.098, SYS, SEVERE, 69,
Database error, DataManTask, dbError, RAIMA Database Error *** Code:-1
(PROGRAMMER/USER error: -1 database not opened
[Raima Object Manager Error: -42]
Programmer / User error: -42
bad DBUSERID (too long or contains non-alphanumeric)

If you see a slew of messages like these, does your Windows/Linux login username contain an embedded space or other inappropriate character? See Which Windows/Linux login name restrictions exist for PVSS users?

Wait condition in nested function call

[Click for a full explanation ]

WCCOAui (0), 2012.10.09 17:30:52.495, CTRL, WARNING, 76, Invalid argument in function,
Module: Vision_11
Panel: C:\Siemens\Automation\WinCC_OA\3.11\panels\projAdmin\project_admin_register.pnl 
Object: 6 named: "cmdPath" of type: PUSH_BUTTON
Script: Clicked
Line: 13, strpos, #2
WCCOAui (0), 2012.10.09 17:30:56.206, CTRL, WARNING, 45/pv2admin, Registry error, paRegProj,

This happens under Windows 7 and later.

It means that you were running the Project Administrator with normal privilege when you tried to create your project (rather than with admin privilege.)

NB Even if you are an admin user on your machine, ie your username has general permission to invoke admin rights, you still need to explicitly invoke those rights.

To always run the Project Administrator with admin rights, Right click the PA icon > Properties > Advanced > Run as administrator

 

 

 

WCCOAui (0), ...15:02:43.072, SYS, INFO, 1, Manager Start, PROJ, OWS_3.11-NORDB-ISO, V 3.11 - 3.11 SP1 platform Windows AMD64 linked at May 27 2015 15:48:25
WCCOAui (0), ... 15:02:43.108, PARAM,FATAL, 142, PmonTable: The loaded project (OWS_3.11-RDB-ISO) is not the just started one (OWS_3.11-NORDB-ISO)
WCCOAui (0), ... 15:02:45.124, SYS, INFO, 2, Manager Stop

Affects Users logging into Production systems at Cern via an Operator Workstation (OWS) application on Windows. (OWS supports a scattered UI viewer into the production system.)
If your local OWS UI fails to start and you see this message as a popup, you need to update the version of OWS on your local machine. (Get the latest version of OWS from NICE CMF.)

If you are merely seeing this message in the logfile, you can safely ignore it. Someone, somewhere, though, will be seeing the popup described above! Who? It's impossible to say. It might be on any of the terminal servers (unlikely) or on some user's own desktop development machine (quite likely) or even on a VM that someone happens to be using...

When that someone moans that he can't start the UI, you can now help him :-)

In the meantime, you may sleep peacefully. The production system will continue to run correctly.

Explanation: The problem manifests when more than one OWS scattered viewer is run on a single machine, each connecting to a different project. WinCC-OA by default mis-diagnoses this as a problem. The corrective technical details are discussed here.

WCCOAascii (1), 2012.10.18 07:34:14.391, SYS, INFO, 2, Manager Stop
doAsciiIn returned error code: -50
A full list of Ascii Manager return codes is given in the Online Help > Reference Tables > Manager Options > WCCOAascii

Error -50 means: DpIdentifier <DpId> for attribute <name> does not exist.
You are trying to import a config of a DPE that does not exist.
You should make sure that the .dpl file that you are currently trying to import also contains an appropriate DP definition. (Go back and export it again.)

WCCOAascii_log:WCCOAascii (1), 2013.05.29 16:23:28.516, SYS, INFO, 2, Manager Stop
WCCOAascii_log:doAsciiIn returned warning code: 56
A full list of Ascii Manager return codes is given in the Online Help > Reference Tables > Manager Options > WCCOAascii

Error 56 means that your logfilehas at leastone line such as the following in it :
WCCOAascii_info:Datapoint/DpId (23): Datapoint (dist_1978:S7_State) with ID 363 already exists, new ID will be generated

Explanation: You are trying to import a DPE with an internal ID that has already been used in the current project. It's just a warning. WinCC-OA uses a new ID.

WCCOAascii_info:DpType (206): Element with ID 276 other than FwCaenCrateSY1527.Information.Debug.MemoryStatus.Free differs in type, given ID will be ignored


This message is saying that you are trying to import a DPT definition but that the Event Manager already has inside it an existing DPT definition using the same DPE ID you mention in your new definition. Your new DPT definition will be skipped entirely.

 
 
 
 

  • No labels