7/22/2016 9:50 AM | |
Posts: 45 Rating: (1) |
I hope this is the correct one.AttachmentHMI_SQLStarter_v34.txt (949 Downloads) |
7/22/2016 10:50 AM | |
Posts: 45 Rating: (1) |
So i created a new user without space and it worked. Thanks a lot for your help. |
This contribution was helpful to1 thankful Users |
10/4/2017 7:55 PM | |
Joined: 10/27/2016 Last visit: 10/22/2024 Posts: 1 Rating: (0) |
OS: Windows Server 2012 R2 WinCC version 7.4 I'm having the same issue. I did however check both the Windows Event Logs (and found no Errors or Warnings referring to issues that resulted during the installation of SQL Server 2014 Standard 32-bit) as well as the RASETUP.LOG that is mentioned in the README file as being "the" log file created during the run of the WinCC v7.4 software. Here is the relevant section of the log (RASETUP file attached) 11:05:01: Ra->Read Dump 11:05:01: Ra-> RunningSetupIndex=23 11:05:01: Ra-> ListViewSetupIndex=SQLSTD_WINCC 11:05:01: Ra-> SetupStatus=0 11:05:01: Ra-> RunningSetupFileName=E:\INSTDATA\SQL\SQLSTARTER\media\SQLStarter.exe 11:05:01: Ra-> StepVisibleProducts=12 11:05:01: Ra-> CountVisibleProducts=22 11:05:01: Installation status loaded. Continue with setup. 11:05:01: ------------------------------------------------------- 11:05:01: 11:05:01: Ra-Auto.ini->ContinueAfterReboot=True 11:05:01: ------------------------------------------------------------------------------------ 11:05:01: Set Packversion: 11:05:01: RegKey=SOFTWARE\SIEMENS\HMI_Edition Value=07.04.20.00_01.32.00.02 11:05:01: RegKey 64Bit=SOFTWARE\SIEMENS\HMI_Edition Value=07.04.20.00_01.32.00.02 11:05:01: ------------------------------------------------------------------------------------ 11:05:01: Installation: 11:05:02: 11:05:02: ------------------------------------------------------------------------------------ 11:05:02: Start SQLSTD_WINCC: 11:05:02: Network Check: Can Access File=E:\INSTDATA\SQL\SQLSTARTER\media\SQLStarter.exe 11:05:02: CreateOPFile OpFileFullPath=C:\Temp\OPFILE.TXT 11:05:02: 11:05:02: [SETUPREQUESTS] 11:05:02: ProductCode=SQLSTD_WINCC 11:05:02: Setuplanguage=B 11:05:02: LanguagesToInstall=B 11:05:02: StartLanguage=B 11:05:02: NameOfUser= 11:05:02: NameOfCompany= 11:05:02: ID= 11:05:02: SetupMode=Batch 11:05:02: DestinationDrive=C 11:05:02: DestinationPath=\Program Files (x86)\Microsoft SQL Server 11:05:02: CommonDrive=C 11:05:02: AuthorizationDrive=A 11:05:02: LicenseSource=A 11:05:02: AuthorizationDrive=C 11:05:02: LicenseDestination=C 11:05:02: AuthorizationRequested=1 11:05:02: LicenseRequested=1 11:05:02: InstType=HMI_Edition 11:05:02: JumpOverParam=1 11:05:02: RSInstallVersion= 11:05:02: NoOSCheck=0 11:05:02: LicenseManagerHandling=0 11:05:02: SeconHandling=1 11:05:02: SeconLogFullPath= 11:05:02: 11:05:02: Secon SecurityXML count=0 11:05:02: -------------------------- 11:05:02: TimeStamp - Start Product=11:05:02 AM (hh:mm:ss) : 11:05:02: Call setup with parameter=E:\INSTDATA\SQL\SQLSTARTER\media\SQLStarter.exe /QS ControlFile=SQL2014STD_WINCC.ini /OF:"C:\Temp\OPFILE.TXT" 11:05:02: 11:05:02: Environment Path=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Common Files\Siemens\bin;C:\Program Files (x86)\Common Files\Siemens\ACE\bin;C:\Program Files (x86)\Common Files\Siemens\CommonArchiving;C:\Program Files (x86)\Common Files\Siemens\ACE;; 11:05:02: Set Environment Path=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Common Files\Siemens\bin;C:\Program Files (x86)\Common Files\Siemens\ACE\bin;C:\Program Files (x86)\Common Files\Siemens\CommonArchiving;C:\Program Files (x86)\Common Files\Siemens\ACE;; 11:05:02: 11:05:02: Call File=E:\INSTDATA\SQL\SQLSTARTER\media\SQLStarter.exe 11:05:02: Call Parameters=/QS ControlFile=SQL2014STD_WINCC.ini /OF:"C:\Temp\OPFILE.TXT" 11:05:02: Process UseShellExecute: True 11:05:02: Process WorkingDirectory: 11:05:02: Process Verb: runas 11:05:02: Process WindowsStyle: ProcessWindowStyle.Normal 11:05:02: 11:05:02: Process started: SQLSTARTER 11:05:02: Process ID: 3424 11:05:02: Session ID: 2 11:07:14: 11:07:14: Setup Return Code:77 11:07:14: -------------------------- 11:07:14: OPFILE.TXT Results: 11:07:14: [RESULTS] 11:07:14: SetupSucceeded=0 11:07:14: AuthorizationDone= 11:07:14: LicenseRequested= 11:07:14: RebootRequested=0 11:07:14: ParamAfterReboot= 11:07:14: LicenseSource= 11:07:14: LicenseDestination= 11:07:14: ErrorNumber=77 11:07:14: ErrorMessage=Info: SQL Installation was not Successful 11:07:14: SeconDone=False 11:07:14: SeconExecute=False 11:07:14: ErrorMessageCount=0 11:07:14: LicenseManager Handling is in Product -1. No licensing for this product. 11:07:14: 11:07:15: TimeStamp - End=11:07:15 AM (hh:mm:ss) 11:07:15: 11:07:15: VersionIni Path=E:\INSTDATA\SQL\SQLSTARTER\media\version.ini 11:07:15: SetupFailed=SQL Server 2014 Standard Edition (WinCC) ProductCode=SQLSTD_WINCC 11:07:15: Critical message = 0 11:10:43: CriticalComponent: The following program could not be installed: SQL Server 2014 Standard Edition (WinCC) Setup cannot complete the installation. 11:10:43: CheckProgramStartAppOnEnd strProductCode=SQLSTD_WINCC 11:10:43: 11:10:43: Secon SecurityXML count=0 11:10:43: License: the file C:\Program Files (x86)\Common Files\Siemens\SWS\almesxapix.dll not exist! 11:10:43: No setup licensing. 11:10:43: Global StartOnEnd=C:\Windows\system32\reg.exe delete "HKLM\SOFTWARE\Siemens\Shared Tools" /v "SetupRunning" /f Afterward, I did a search for "SQL Installation was not Successful error=77" however the results didn't return anything that I could link back to this particular issue. Part of it as well is the fact that because this is an embedded version of SQL Server, there doesn't appear to be much in the way of options when it relates to making changes for compatibility of SQL Server. Has anyone else run into this? As a previous post suggested that perhaps the problem relates to the fact that I'm also using Windows Server 2012 R2 (64-bit) and this version of SQL Server 2014 Standard is 32-bit. Is there a workaround using a 64-bit version of SQL Server? AttachmentRASETUP - Copy.txt (260 Downloads) |
11/20/2018 8:15 PM | |
Joined: 11/8/2018 Last visit: 10/20/2023 Posts: 2 Rating: (0) |
Hi There! Any ideas why this is happening? Thanks in advance! AttachmentSummary.txt (288 Downloads) |
Follow us on