Skip to Content

Register Login

Default Header

(header konnte nicht geladen werden)

Navigation

TIA V18 - An error occurred during setup

Created by: AutoGen_6295578 at: 12/1/2023 12:34 PM (2 Replies)

Rating (0)

Thanks 1

3 Entries

12/1/2023 12:34 PM	Rate (0)
AutoGen_6295578 Joined: 4/16/2021 Last visit: 7/14/2025 Posts: 1 Rating: (0)	Hello, We have a problem installing TIA v18. Right after it starts, it ends during the adjustment of the system. We tried it: - on Windows 10 Pro and Windows 11. - in different languages (english and german) - different settings (minimum and standard) everytime we found the following entry in the log twice: ERROR AdsWorkerForeignExe::GetInstallResult(): - -2147023636: assuming unknown error, because return value is not in OK-list which is only defined. Please check the corresponding log file for more detailed information. Do you have any ideas? Attachment SIA_STEP7_S7FPLUS_WINCC_ADV_V18@23-12-01_13-00-27_01.txt (343 Downloads)
	Last edited by: The Helping Hand at: 12/01/2023 12:53:12 Text formatting optimized
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users AutoGen_4257883

12/1/2023 3:02 PM	Rate (0)
ElonksuM Experienced Member Joined: 5/6/2022 Last visit: 11/27/2025 Posts: 589 Rating: (123)	Hi AutoGen_6295578, Where did you get the installer from? Did you download it from SIOS or did it come on the CD? If it is from SIOS, I would recommend downloading it again in case there had been a problem downloading it since it is very strange.
	If this Information really helps, you could use the Rate function Thank you.
Suggestion To thank Quote Answer

12/2/2023 1:34 AM	Rate (0)
Bevan Weiss Regular Member Joined: 7/26/2011 Last visit: 7/22/2025 Posts: 64 Rating: (6)	AutoGen_6295578 ... everytime we found the following entry in the log twice: ERROR AdsWorkerForeignExe::GetInstallResult(): - -2147023636: assuming unknown error, because return value is not in OK-list which is only defined. Please check the corresponding log file for more detailed information. Unfortunately this is only the first step of the errors. It's the highest level. You need to go further down the rabbit hole. If you open the log file, and search for "\|ERROR" (as recommended at the top of the file) you'd see there were 3 errors, and they all appeared to be related to Asp_DotNet_Core. 13:06:08\|... \|AdsWorkerForeignExe::Progress() \|(01) Executing: S:\InstData\Prerequisites\Asp_DotNet_Core\Media\aspnetcore-runtime-6.0.8-win-x64.exe /install /quiet /norestart /log "C:\ProgramData\Siemens\Automation\Logfiles\Setup\install_Asp_DotNet_Core_log.txt"; WaitForApp: 13:06:09\|. \|AdsWorkerForeignExe::Completed() \|(01) END executing AdsWorker 'Asp_DotNet_Core' for 'AddLocal' 13:06:09\|ERROR \|AdsWorkerForeignExe::GetInstallResult() \|(01) -2147023636: assuming unknown error, because return value is not in OK-list which is only defined. Please check the corresponding log file for more detailed information You can see the log file that you need to look in referenced there: C:\ProgramData\Siemens\Automation\Logfiles\Setup\install_Asp_DotNet_Core_log.txt I've found that often there's two problems: 1. The installer is written badly, and doesn't handle if DotNet Core is already installed. The solution is to uninstall your current version of DotNetCore v6 and let the installer try to install it. 2. The installer is written badly, and doesn't handle some concern that DotNetCore had during its installer routine. In this case you want to make sure that you've installed the exact version of DotNetCore successfully yourself. So you'd try to install DotNetCore x64 6.0.8. I'd suggest doing them in the order I've detailed. First uninstall if already installed, and if that doesn't work, then install exactly x64 6.0.8 yourself. You should consult the installation logs again between each step if it didn't produce success. And Good Luck. I've just had an issue trying to Uninstall v18 Professional where an early step in the uninstaller deleted the ..Compatibility...XML file, and then a subsequent step absolutely required that file to exist. I had to copy the file back mid installer execution at the right time to get it to work.

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on