Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

PC7v9.0: DATA-SERVER01,SCRIPT,Endact. Timeout,MSG_STATE_COME

Created by: arunvt1992 at: 10/14/2024 11:34 AM (6 Replies)

Rating (0)

Thanks 0

7 Entries

10/14/2024 11:34 AM	Rate (0)
arunvt1992 Bronze Member Joined: 10/5/2016 Last visit: 8/10/2025 Posts: 109 Rating: (2)	We are using PC7v9.0 and after a complete download to the server , runtime was activated. After Activation we received a dialog box ,telling to check the PDLRTSEH log file in the Wincc diagnose location. Upon looking the logic file we found DATA-SERVER01,SCRIPT,Endact. Timeout,MSG_STATE_COME . Can anyone advise what is this regarding to and what should be done to resolve it. yangfl Is there anyone who have seen this problem? This Project is consist of three Servers & one Client and Two AS, One TMC controller. The original Project is done by Siemens I&S, We upgrade the Project,But the Project have a ATD_MP software,we only use the old version ATD_MP software which mainly use as the procedure of CFC,faceplate. Now the upgraded Project encontered two problem, one is the above listed, that is the running picture is not move and not dynamically refreshed, and when this problem occurs, the diagnosis information of the the Diagnos Folder alway wrote the information " 255,02.08.2007,00:00:44:484,1007008,4,,SERVER11,SCRIPT,EndAct Timeout 255,02.08.2007,00:01:44:484,1007008,4,,SERVER11,SCRIPT,EndAct Timeout 255,02.08.2007,22:38:43:687,1007008,4,,SERVER11,SCRIPT,EndAct Timeout 255,02.08.2007,22:39:43:703,1007008,4,,SERVER11,SCRIPT,EndAct Timeout 255,02.08.2007,22:40:43:703,1007008,4,,SERVER11,SCRIPT,EndAct Timeout" And we don't know how to do. Could help me,Thanks a ------------------------------------------------------------------------------------------ Split from PCS7 SERVER11,SCRIPT,EndAct Timeout.
	Last edited by: Moderator_Lan at: 10/14/2024 11:44:14 New subject after splitting
Suggestion To thank Quote Answer

10/15/2024 7:22 AM	Rate (0)
Molthoff Experienced Member Joined: 3/13/2015 Last visit: 9/1/2025 Posts: 166 Rating: (41)	Hi, I'm not familiar with the software inplace, so no direct solution. What I do know from experiance is that the Script engine is single threaded. So if a script is holding up, and in the end giving a time out this will freeze all script related tasks of the client/server. This will also lead to bad/none reaction to the mouse actions in graphic runtime. This can happen eq when the database that is a resource for the script is extensive or a bad while loop is in place. All other functionality of the OS server/Client will function like tagmanagement, Alarm- and taglogging. So my suggetion is first to eliminated all cyclic scripting (by eq. remove starting triggers/place a "return void/true/false (depending on the script)" at the start of the script) to see if the problem reocurs to pinpoint the script with the execution problem. If the problem is not within the cyclic scripting then take a look at the picture objects that may trigger a failing script. Success with the search, and ofcourse create a Service Request when its seem to be a (supported) product issue. Best regards, Cedric
	Last edited by: Molthoff at: 10/15/2024 07:22:43 Last edited by: Molthoff at: 10/15/2024 07:23:53 Dit it work? Let your fellow forum users know what your solution was!
Suggestion To thank Quote Answer

10/21/2024 4:08 AM	Rate (0)
arunvt1992 Bronze Member Joined: 10/5/2016 Last visit: 8/10/2025 Posts: 109 Rating: (2)	Thank you for the reply. There are no scripts in this Server project. All are done without using scripting. Kindly find attached error . Attachment Error.jpeg (207 Downloads)
	Last edited by: arunvt1992 at: 10/21/2024 04:24:35
Suggestion To thank Quote Answer

10/22/2024 12:19 PM	Rate (0)
arunvt1992 Bronze Member Joined: 10/5/2016 Last visit: 8/10/2025 Posts: 109 Rating: (2)	arunvt1992 Thank you for the reply. There are no scripts in this Server project. All are done without using scripting. Kindly find attached error . Please find attached error which we are getting when we click on Alarm journal button.. Can anyone advise what should we do to resolve this. Attachment PDLRTSEH error.jpeg (203 Downloads)

Suggestion To thank Quote Answer

10/22/2024 9:42 PM	Rate (0)
Molthoff Experienced Member Joined: 3/13/2015 Last visit: 9/1/2025 Posts: 166 Rating: (41)	Hi, When using the standard PCS 7 configuration scripts are always used. When the system is not configured correctly, eq to much archive segments or to must unarchived batches, etc. I understand you configured no additional scripts. Please create a service request if the system is default. Please let us know if a solution is found. Best regards, Cedric
	Dit it work? Let your fellow forum users know what your solution was!
Suggestion To thank Quote Answer

10/23/2024 5:15 AM	Rate (0)
arunvt1992 Bronze Member Joined: 10/5/2016 Last visit: 8/10/2025 Posts: 109 Rating: (2)	As this is PCS7v9.0 when i created a service request , they told i need to purchase a legacy contract to support which i do not have .

Suggestion To thank Quote Answer

10/24/2024 7:35 AM	Rate (0)
arunvt1992 Bronze Member Joined: 10/5/2016 Last visit: 8/10/2025 Posts: 109 Rating: (2)	Below is the data from the log file and also i have copied all the data from the log file in the attachment. // WinCC reported exception with code: E06D7363 // Date: 23.10.2024 - Time: 12:10:06 // Caused at logical address 74D08668 01:000B7668 //==================================================================== // FAULTING MODULE: C:\Windows\SYSTEM32\KERNELBASE.dll //==================================================================== // Registers: // ---------- // EAX:117BFD20 // EBX:0C029870 // ECX:00000003 // EDX:00000000 // ESI:7299C7EC // EDI:72A38518 // CS:EIP:0023:74D08668 // SS:ESP:002B:117BFD20 EBP:117BFD7C // DS:002B ES:002B FS:0053 GS:002B // Flags:00000212 // // Raw stack dump: // ----------- 117BFD20 E06D7363 00000001 00000000 74D08668 00000003 19930520 117BFDC4 7299C888 117BFD40 FFFFFFFF 00000024 117BFD54 72A38518 7299C7EC 0C029870 117BFD74 7299AAA1 117BFD60 117BFD6C 72990949 72A354C0 117BFDAC 7299260C A65714B2 7299A9E5 117BFDB4 117BFD80 729A872D E06D7363 00000001 00000003 117BFDA8 E06D7363 00000001 00000000 117BFDA0 00000000 00000003 19930520 117BFDC4 7299C888 117BFDD4 729BF30F 117BFDC4 117BFDC0 7299C888 7299C7EC 7299B754 77049800 7299B754 117BFE0C 00692164 062D195C 117BFDE0 062D1950 00000000 00000E7F 027F9870 041E10E0 00000000 00000002 0000000C 117BFE00 00000003 00000000 062D1950 117BFE44 62DCC831 77169020 041E10E0 117BFE3C 117BFE20 117BFE34 00000000 10387120 00000010 729DC59C 00000000 00000000 00000000 117BFE40 80004005 117BFF3C 62DCA117 77169020 041E10E0 00000000 0BCFBA18 117BFE9C 117BFE60 117BFEA0 82488D78 10387120 10387120 00000025 00000001 13EBD598 13002E00 117BFE80 1056C840 10387120 10387120 10387120 10387120 00000000 00000002 041E10E0 117BFEA0 00000000 00000002 10387120 0BCFBA08 00000000 00000001 106985B8 00000000 117BFEC0 00000000 00000010 00000000 00000F08 00000CF8 00000001 00000000 00000000 117BFEE0 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 117BFF00 00000000 00000000 00000000 00000000 00000000 00000000 106A1448 117B0001 117BFF20 80004005 101D0670 00000000 00000000 117BFF64 62DD049D FFFFFFFF 117BFF74 117BFF40 729DC556 101D0670 B867EB9D 729DC59C 729DC59C 0C029870 E06D7363 117BFF48 117BFF60 117BEFF4 117BFFCC 72A0B65A DB81D169 00000000 117BFF80 729DC600 729DC59C 117BFF80 117BFF94 76EA3744 0C029870 76EA3720 3EB43E51 117BFFDC 7703AA64 0C029870 117BFFA0 DAC5E463 00000000 00000000 0C029870 E06D7363 74D1C5E0 00000000 117BEFF4 117BFFC0 DAC5E463 117BFFA0 117BEFF4 117BFFE4 770519D0 BCB307D7 00000000 117BFFEC 117BFFE0 7703AA2F FFFFFFFF 7705E498 00000000 00000000 729DC59C 0C029870 00000000 // ----------- // // Call stack: // ----------- // Address \| Frame \| // ---------+----------+---------------------------------------------- // 74D08668 \| 117BFD7C \| RaiseException+48 // 729A872D \| 117BFDB4 \| CxxThrowException+45 // 729BF30F \| 117BFDD4 \| fcloseall+6835 // 00692164 \| 117BFE0C \| CcSplayCompressWithHeader+64 // 62DCC831 \| 117BFE44 \| 0001:0001B831 C:\Program Files (x86)\Common Files\Siemens\ACE\Bin\SCSCALCX.dll // 62DCA117 \| 117BFF3C \| 0001:00019117 C:\Program Files (x86)\Common Files\Siemens\ACE\Bin\SCSCALCX.dll // 729DC556 \| 117BFF74 \| endthreadex+3A // 729DC600 \| 117BFF80 \| endthreadex+E4 // 76EA3744 \| 117BFF94 \| BaseThreadInitThunk+24 // 7703AA64 \| 117BFFDC \| RtlSetCurrentTransaction+D4 // 7703AA2F \| 117BFFEC \| RtlSetCurrentTransaction+9F //==================================================================== Attachment WinCC reported exception with code.docx (203 Downloads)

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on