Forum Replies Created
-
AuthorPosts
-
JW
ParticipantHi,
I found the difference.
Selecting “Input channels” the whole table then find and replace will not experience crash.
But selecting sub tables such as “[11]ADAM-6015 Server room” then find and replace will experience crash.
JW
Participantyes, that’s the same actions I did.
I am going to try on another computer tomorrow and see what’s the result.
JW
ParticipantHi Mikhail,
I Found a way to reproduce this consistently using the DemoProject.en-GB.
1. goto input channel table [11]
2. find and replace
Column: Name
Find: t
Replace with: s_t
uncheck match whole cell.
3. the 1st time will be performed correctly
4. do the same find and replace again, Administrator app will crash.JW
ParticipantSometimes when you change settings in role table or interface table, you will need to restart the IIS service for Windows or apache2 service for Linux to make it effective, instead of just restarting the scada server.
JW
ParticipantHi, I tried the auto login module with rapid scada 5.8.1 on both windows and linux. Neither of them work.
When try to use auto login URL, the web show only the following error message.
Application Error
An application error occurred. If it repeats often, please contact the support.
Details:
c:\SCADA\ScadaWeb\Login.aspx(19): error CS0103: The name ‘phrases’ does not exist in the current context——————————————————————————–
Web Log
——————————————————————————–
2020-11-18 10:40:27 <os-server><www-data><ACT> Initialize common web application data
2020-11-18 10:40:27 <os-server><www-data><ACT> Connect to SCADA-Server “localhost”
2020-11-18 10:40:27 <os-server><www-data><ACT> Refresh the tables of the configuration database
2020-11-18 10:40:27 <os-server><www-data><ACT> Fill input channels properties
2020-11-18 10:40:27 <os-server><www-data><ACT> Fill output channels properties
2020-11-18 10:40:27 <os-server><www-data><ACT> Fill input channel statuses properties
2020-11-18 10:40:32 <os-server><www-data><ACT> User information has been added. IP address: ::1. Session: A3B4E3B4CDA8C7978F544E55
2020-11-18 11:20:18 <os-server><www-data><ACT> Request SCADA-Server state
2020-11-18 11:20:18 <os-server><www-data><ERR> Incorrect SCADA-Server response to state request
2020-11-18 11:20:18 <os-server><www-data><ACT> Disconnect from SCADA-Server
2020-11-18 11:20:18 <os-server><www-data><ACT> Connect to SCADA-Server “localhost”
2020-11-18 11:20:18 <os-server><www-data><ACT> User information has been added. IP address: ::1. Session: 9B83F0E5C6DE2ACFC877FA8A
2020-11-18 11:20:20 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
2020-11-18 11:20:23 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
2020-11-18 11:20:27 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
2020-11-18 11:20:37 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
2020-11-18 11:20:43 <os-server><www-data><ACT> Login: guest (Guest). IP address: ::1
2020-11-18 11:20:43 <os-server><www-data><ACT> User information has been updated. IP address: ::1. Session: 9B83F0E5C6DE2ACFC877FA8A
2020-11-18 11:20:43 <os-server><www-data><ACT> Retrieve components from the installed plugins
2020-11-18 11:20:55 <os-server><www-data><ACT> Logout: guest. IP address: ::1
2020-11-18 11:21:01 <os-server><www-data><ERR> Unsuccessful login attempt: admin – Incorrect username or password. IP address: ::1
2020-11-18 11:21:07 <os-server><www-data><ACT> Login: guest (Guest). IP address: ::1
2020-11-18 11:21:07 <os-server><www-data><ACT> User information has been updated. IP address: ::1. Session: 9B83F0E5C6DE2ACFC877FA8A
2020-11-18 11:21:07 <os-server><www-data><ACT> Retrieve components from the installed plugins
2020-11-18 11:35:25 <os-server><www-data><ACT> Application shutdown
——————————————————————————–
——————————————————————————–
2020-11-18 11:36:40 <os-server><www-data><ACT> Initialize common web application data
2020-11-18 11:36:40 <os-server><www-data><ACT> Connect to SCADA-Server “localhost”
2020-11-18 11:36:40 <os-server><www-data><ACT> Refresh the tables of the configuration database
2020-11-18 11:36:40 <os-server><www-data><ACT> Fill input channels properties
2020-11-18 11:36:40 <os-server><www-data><ACT> Fill output channels properties
2020-11-18 11:36:40 <os-server><www-data><ACT> Fill input channel statuses properties
2020-11-18 11:36:46 <os-server><www-data><EXC> Application error:
System.Web.Compilation.CompilationException (0x80004005): CS0103: The name `phrases’ does not exist in the current context
at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.Web.VirtualPath virtualPath, System.CodeDom.Compiler.CompilerParameters options) [0x00312] in <716e5fc6fa1b4b5db9a4701d451ead9c>:0
at System.Web.Compilation.AssemblyBuilder.BuildAssembly (System.Web.VirtualPath virtualPath) [0x00008] in <716e5fc6fa1b4b5db9a4701d451ead9c>:0
at System.Web.Compilation.BuildManager.GenerateAssembly (System.Web.Compilation.AssemblyBuilder abuilder, System.Web.Compilation.BuildProviderGroup group, System.Web.VirtualPath vp, System.Boolean debug) [0x00202] in <716e5fc6fa1b4b5db9a4701d451ead9c>:0
at System.Web.Compilation.BuildManager.BuildInner (System.Web.VirtualPath vp, System.Boolean debug) [0x00106] in <716e5fc6fa1b4b5db9a4701d451ead9c>:0
Page: http://localhost/scada/Error.aspx
——————————————————————————–——————————————————————————–
Server Log
——————————————————————————–
2020-11-18 10:03:01 <os-server><root><ACT> ScadaServerService 5.1.4.0 is started
2020-11-18 10:03:02 <os-server><root><ACT> Check the existence of the data directories is completed successfully
2020-11-18 10:03:02 <os-server><root><ACT> Check the existence of the configuration database files is completed successfully
2020-11-18 10:03:02 <os-server><root><ACT> Input channels are read from the configuration database. Active channel count: 5
2020-11-18 10:03:02 <os-server><root><ACT> Ouput channels are read from the configuration database
2020-11-18 10:03:02 <os-server><root><ACT> Users are read from the configuration database
2020-11-18 10:03:02 <os-server><root><ACT> Formulas are read from the configuration database
2020-11-18 10:03:06 <os-server><root><ACT> The formulas source code has been compiled
2020-11-18 10:03:06 <os-server><root><ACT> Connection listener is started
2020-11-18 10:03:06 <os-server><root><ACT> Start server
2020-11-18 10:03:06 <os-server><root><ACT> Current data are loaded
2020-11-18 10:03:13 <os-server><root><ACT> Connect to client 127.0.0.1
2020-11-18 10:03:13 <os-server><root><ACT> The user ScadaComm is successfully authenticated
2020-11-18 10:40:27 <os-server><root><ACT> Connect to client 127.0.0.1
2020-11-18 10:40:27 <os-server><root><ACT> The user ScadaWeb is successfully authenticated
2020-11-18 10:41:32 <os-server><root><ACT> Disconnect client 127.0.0.1
2020-11-18 11:20:18 <os-server><root><ACT> Connect to client 127.0.0.1
2020-11-18 11:20:18 <os-server><root><ACT> The user ScadaWeb is successfully authenticated
2020-11-18 11:20:20 <os-server><root><ACT> Check username and password for admin. Result: failed
2020-11-18 11:20:23 <os-server><root><ACT> Check username and password for admin. Result: failed
2020-11-18 11:20:27 <os-server><root><ACT> Check username and password for admin. Result: failed
2020-11-18 11:20:37 <os-server><root><ACT> Check username and password for admin. Result: failed
2020-11-18 11:20:43 <os-server><root><ACT> Check username and password for guest. Result: passed
2020-11-18 11:21:01 <os-server><root><ACT> Check username and password for admin. Result: failed
2020-11-18 11:21:07 <os-server><root><ACT> Check username and password for guest. Result: passed
2020-11-18 11:22:14 <os-server><root><ACT> Disconnect client 127.0.0.1
2020-11-18 11:36:40 <os-server><root><ACT> Connect to client 127.0.0.1
2020-11-18 11:36:40 <os-server><root><ACT> The user ScadaWeb is successfully authenticated
2020-11-18 11:37:40 <os-server><root><ACT> Disconnect client 127.0.0.1
——————————————————————————–JW
Participant**note: the files in the link above are the configs that will trigger the issue, not the workaround.
JW
ParticipantThe picture you post is not visible.
Below are my experience and tips of sending command to external modbus device. Not sure is it the same issue you encountered.
When 1 trigger triggers and sends 2 commands to 1 same external device. the auto control module stops working will work at the beginning, but fail after a few events.
Then I set some delay to each command, then it seems ok as a work around.
my device comm setting, auto control setting and server log are attached in the following link.
https://drive.google.com/drive/folders/19fHCCfyO-0bWff_Tsadruy29eT05lmyJ?usp=sharingJW
Participantnever mind, just found it here…
https://github.com/RapidScada/scada/blob/master/ScadaData/ScadaData/Data/Tables/SrezAdapter.csJW
ParticipantI mean no matter what scale the user choose previously, e.g. fit to width, 50%zoom, or 100%zoom before he close the web, next time he opens scheme view again, it will be “fit to screen”. is it possible?
JW
ParticipantThe scale setting can be remember by browser, which is a nice solution.
However, sometimes I wanted to force the browser use “fit to screen” every time the user open a scheme view, is there a way to do it?
Because I usually use a very high-res map/cad drawings (e.g.6000×4000) as background image to allow user to zoom-in to see details. if it’s not “fit to screen” at the beginning, some user lost track of where they are looking at.
JW
Participanthere maybe the root cause.
the line different from 2 version in daemon files scada
5.8.1
EXE_DIR=/etc/scada/ScadaServer/
5.8.0
EXE_DIR=/opt/scada/ScadaServer/JW
ParticipantHi manjey73, thanks for your help.
it turns out it wasn’t the ScadaData.Svc.dll make it work. it was the daemons of 5.8.0 make it work.
I tried the following tests:
1. fresh install of 5.8.1, does not work;
2. fresh install of 5.8.0, work;
3. update /opt/scada to5.8.1 + keep daemons from 5.8.0, work.the file size and edit time are slightly different between 2 set of daemon files, but i can’t find the difference between the content.
5.8.0———-
-rw-rw-r– 1 jw jw 1666 2019-04-19 12:18:02.000000000 +0800 scadaagent
-rw-rw-r– 1 jw jw 1675 2018-11-22 10:02:24.000000000 +0800 scadacomm
-rw-rw-r– 1 jw jw 1735 2018-11-22 10:02:24.000000000 +0800 scadaserver
5.8.1———-
-rw-rw-r– 1 jw jw 1666 2019-04-19 12:18:00.000000000 +0800 scadaagent
-rw-rw-r– 1 jw jw 1748 2018-11-22 09:35:06.000000000 +0800 scadacomm
-rw-rw-r– 1 jw jw 1810 2018-11-22 09:35:06.000000000 +0800 scadaserverJW
ParticipantAre ScadaData.Svc.dll in ScadaServer and ScadaComm folder needed for version 5.8.1?
I copied those 2 files from 5.8.0 to 5.8.1. It seems working now.
JW
Participantin admin app, the status show Undefined instead of error.
there is no log files in /opt/scada/ScadaServer/Log, /opt/scada/ScadaServer/Log——————————————————————-
service status:jw@jw-ubuntu:~/Desktop$ sudo service scadaserver status
scadaserver.service – LSB: SCADA-Server daemon
Loaded: loaded (/etc/init.d/scadaserver; generated)
Active: failed (Result: exit-code) since Fri 2020-06-26 09:41:07 HKT; 2min 36s ago
Docs: man:systemd-sysv-generator(8)
Process: 883 ExecStart=/etc/init.d/scadaserver start (code=exited, status=203/EXEC)Jun 26 09:41:07 jw-ubuntu systemd[1]: Starting LSB: SCADA-Server daemon…
Jun 26 09:41:07 jw-ubuntu systemd[1]: scadaserver.service: Control process exited, code=exited, status=203/EXEC
Jun 26 09:41:07 jw-ubuntu systemd[1]: scadaserver.service: Failed with result ‘exit-code’.
Jun 26 09:41:07 jw-ubuntu systemd[1]: Failed to start LSB: SCADA-Server daemon.
jw@jw-ubuntu:~/Desktop$ sudo service scadacomm status
● scadacomm.service – LSB: SCADA-Communicator daemon
Loaded: loaded (/etc/init.d/scadacomm; generated)
Active: failed (Result: exit-code) since Fri 2020-06-26 09:41:07 HKT; 2min 39s ago
Docs: man:systemd-sysv-generator(8)
Process: 896 ExecStart=/etc/init.d/scadacomm start (code=exited, status=203/EXEC)Jun 26 09:41:07 jw-ubuntu systemd[1]: Starting LSB: SCADA-Communicator daemon…
Jun 26 09:41:07 jw-ubuntu systemd[1]: scadacomm.service: Control process exited, code=exited, status=203/EXEC
Jun 26 09:41:07 jw-ubuntu systemd[1]: scadacomm.service: Failed with result ‘exit-code’.
Jun 26 09:41:07 jw-ubuntu systemd[1]: Failed to start LSB: SCADA-Communicator daemon.————————————————–
journalctl log: but the scadaserver and scadacomm file are in /etc/init.d alreadyJun 26 10:04:40 jw-ubuntu systemd[1]: Starting LSB: SCADA-Server daemon…
— Subject: A start job for unit scadaserver.service has begun execution
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— A start job for unit scadaserver.service has begun execution.
—
— The job identifier is 1786.
Jun 26 10:04:40 jw-ubuntu systemd[3498]: scadaserver.service: Failed to execute command: No such file or directory
Jun 26 10:04:40 jw-ubuntu systemd[3498]: scadaserver.service: Failed at step EXEC spawning /etc/init.d/scadaserver: No such file or directory
— Subject: Process /etc/init.d/scadaserver could not be executed
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— The process /etc/init.d/scadaserver could not be executed and failed.
—
— The error number returned by this process is ERRNO.
Jun 26 10:04:40 jw-ubuntu systemd[1]: scadaserver.service: Control process exited, code=exited, status=203/EXEC
— Subject: Unit process exited
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— An ExecStart= process belonging to unit scadaserver.service has exited.
—
— The process’ exit code is ‘exited’ and its exit status is 203.
Jun 26 10:04:40 jw-ubuntu systemd[1]: scadaserver.service: Failed with result ‘exit-code’.
— Subject: Unit failed
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— The unit scadaserver.service has entered the ‘failed’ state with result ‘exit-code’.
Jun 26 10:04:40 jw-ubuntu systemd[1]: Failed to start LSB: SCADA-Server daemon.
— Subject: A start job for unit scadaserver.service has failed
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— A start job for unit scadaserver.service has finished with a failure.
—
— The job identifier is 1786 and the job result is failed.JW
Participantfor the default event 1-5, 11-15 101-114, changing color works.
but the custom event I added 1001-1010, changing color does’t work.
-
AuthorPosts