Forum Home › Forums › Installation Issues › SCADA-related services cannot be automatic started
- This topic has 9 replies, 2 voices, and was last updated 3 months, 3 weeks ago by
Mikhail.
-
AuthorPosts
-
February 8, 2023 at 7:21 am #12083
grhsc
ParticipantHi, dear developer, I deployed SCADA on win10 desktop and it works fine. But when I migrate rapid scada project to win server 2022, its services cannot be started automatically (although I see their status is automatic)
https://drive.google.com/file/d/1iuhBlPVnGOqbPKiGcKUHFidcdnstAJlY/view?usp=sharing
This is the information in the event log, could you provide a suggestion please?
https://drive.google.com/file/d/1Eh3ksOv-yu2VSwdYxg6C-gn4JBXFDz6I/view?usp=sharing
February 8, 2023 at 9:47 am #12084Mikhail
ModeratorHi,
Can the Webstation and Administrator applications start successfully?
February 8, 2023 at 11:06 am #12090grhsc
ParticipantI’m not quite sure what these 2 applications refer to
Webstation – does it mean the web UI of rapid scada v6? it won’t work, it shows an error on the login page: the application not ready, try again later
administrator – does it mean the ScadaAdmin editor? I don’t know because the server doesn’t have this dev tools installed
Please let me know if my understanding is incorrect
By the way, the version I’m talking about is V6.01,thank you!-
This reply was modified 4 months ago by
grhsc.
February 8, 2023 at 11:28 am #12092Mikhail
ModeratorYou understanding is correct.
Please run from a command line:
dotnet --info
What does this command return?February 8, 2023 at 12:28 pm #12093grhsc
Participanthello, this is the information returned
C:\Users\rapid_scada>dotnet –info
global.json file:
Not foundHost:
Version: 6.0.12
Architecture: x64
Commit: 02e45a41b7.NET SDKs installed:
No SDKs were found..NET runtimes installed:
Microsoft.AspNetCore.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]Download .NET:
https://aka.ms/dotnet-downloadLearn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-infoFebruary 8, 2023 at 12:54 pm #12094Mikhail
ModeratorLooks correct.
What if you open command line as administrator, find and run ScadaServerWkr.exe?February 8, 2023 at 1:53 pm #12095grhsc
Participanthere they are, by the way, I see from the forum timestamp that your local time is too late, It’s not urgent, you can help me when you are free, take care!
C:\Program Files\SCADA\ScadaServer>ScadaServerWkr.exe
info: Scada.Server.Wkr.Worker[0]
Server is started successfully
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: C:\Program Files\SCADA\ScadaServer
info: Microsoft.Hosting.Lifetime[0]
Application is shutting down…
info: Scada.Server.Wkr.Worker[0]
Server is stoppedC:\Program Files\SCADA\ScadaServer>
-
This reply was modified 4 months ago by
grhsc.
February 9, 2023 at 8:40 am #12098Mikhail
ModeratorThank you for your care.
According to the messages, Server started successfully when executed manually.
Could you try executing svc_stop.bat and svc_start.bat from command line as administrator.
What is written in SCADA\ScadaSever\Log\ScadaServer.log ?February 10, 2023 at 2:22 pm #12105grhsc
ParticipantThank you so much for your continued attention. Attach the log information after its execution
I have tried other ways. If I change the service startup type from automatic to automatic (delayed) startup, the 3 services of rapidSCADA can start normally.
I don’t know why there is no need to set the delay in win 10 desktop version but it needs to be set in win server 2022.
do you have encountered such a case before?
If I find out why in the future, I’ll come back and note it here too.-------------------------------------------------------------------------------- 2023-02-10 22:16:09 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Server 6.0.0.1 started 2023-02-10 22:16:09 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Storage FileStorage 6.0.0.0 loaded from file C:\Program Files\SCADA\ScadaServer\FileStorage.dll 2023-02-10 22:16:09 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Start logic processing 2023-02-10 22:16:10 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] The configuration database has been read successfully 2023-02-10 22:16:10 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][INF] Number of active channels for archiving: 3174 2023-02-10 22:16:10 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][INF] Number of active channels for sending commands: 0 2023-02-10 22:16:10 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Compile the source code of scripts and formulas 2023-02-10 22:16:11 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Added the following dependencies: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.12\netstandard.dll C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.12\System.Console.dll C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.12\System.Linq.dll C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.12\System.Private.CoreLib.dll C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.12\System.Runtime.dll C:\Program Files\SCADA\ScadaServer\ScadaCommon.dll C:\Program Files\SCADA\ScadaServer\ScadaServerEngine.dll 2023-02-10 22:16:13 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] The source code of scripts and formulas has been compiled successfully 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Module ModArcBasic 6.0.0.0 loaded from file C:\Program Files\SCADA\ScadaServer\Mod\ModArcBasic.Logic.dll 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Module ModArcPostgreSql 6.0.0.0 loaded from file C:\Program Files\SCADA\ScadaServer\Mod\ModArcPostgreSql.Logic.dll 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Archive Cur initialized successfully 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Archive Min initialized successfully 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Archive Hour initialized successfully 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Archive Events initialized successfully 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Start listener on port 10000 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][INF] Archive in DAT format: C:\Program Files\SCADA\Archive 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][INF] Archive copy in DAT format: C:\Program Files\SCADA\ArchiveCopy 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Delete outdated data from the Min archive older than 10/02/2022 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Delete outdated data from the Hour archive older than 10/02/2022 2023-02-10 22:16:14 [TEST-RENHUA-RAP][TEST-RENHUA-RAP$][ACT] Delete outdated data from the Events archive older than 10/02/2022
-
This reply was modified 3 months, 3 weeks ago by
Mikhail.
February 13, 2023 at 9:42 am #12111Mikhail
ModeratorIf I change the service startup type from automatic to automatic (delayed) startup, the 3 services of rapidSCADA can start normally.
I don’t know why there is no need to set the delay in win 10 desktop version but it needs to be set in win server 2022.
do you have encountered such a case before?This is a weird thing. Thank you for finding a workaround.
We haven’t met this before. However, as for me, I haven’t tried Windows Server 2022 yet.
In case I got new related info, I will text here. -
This reply was modified 4 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.