New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FB 1.5.4 command line params for SuperServerComponent installallation does not work [CORE1220] #1644
Comments
Modified by: @reevespaulassignee: Paul Reeves [ paul_reeves ] |
Commented by: @reevespaul The problem is that the /COMPONENTS string must not have spaces in it. The parser (unbelievably) chokes on them. Contrary to supposition, your example has probably never worked. It appeared to work because the installer used to default to what you wanted. Now it defaults to something else. This is due to a change in the way the components are specified. |
Commented by: Wade Auchterlonie (wadeauch) I can verify that the problem is not related to spaces in the Components declaration. The attached screen shot shows the setup being launched from the command line, specifying the components ithout spaces, and it also shows the setup stepped through to the component selection with the classic server selected for installation. |
Modified by: Wade Auchterlonie (wadeauch)Attachment: screenshot-1.jpg [ 10350 ] |
Commented by: Wade Auchterlonie (wadeauch) Further investigation has found this: Contrary to supposition, FB 1.5.3 install correctly interpreted the following parameter: /COMPONENTS="SuperServerComponent, ServerComponent, DevAdminComponent, ClientComponent" and this can be verified by playing with various combinations, and contrary to previous comments, the spaces are not a problem. With FB 1.5.4 the syntax of the command line parameters has changed. This new syntax is covered in the 1.5.4 version of the file "installation_readme.txt" however it is not indicated in this file that the syntax has changed. The new syntax requires the "ServerComponent\" prefix on the server type selection parameter. /COMPONENTS="ServerComponent, ServerComponent\SuperServerComponent, DevAdminComponent, ClientComponent" Again, spaces do not appear to be a problem, the problem is simply that there has been an unexpected change to the installer parameters between 1.5.3 and 1.5.4 This syntax change is not document in "Firebird_v1.5.4.ReleaseNotes.pdf" |
Modified by: @pcisarWorkflow: jira [ 11902 ] => Firebird [ 15485 ] |
Commented by: Yurii Kucheriavyi (yurock) Firebird-3.0.0.32483_2_Win32.exe /SILENT /NOCANCEL /NORESTART /RESTARTEXITCODE=100 /FORCE /COMPONENTS="ServerComponent\SuperServerComponent,ServerComponent,DevAdminComponent,ClientComponent" /TASKS="UseServiceTask,AutoStartTask,CopyFbClientToSysTask,CopyFbClientAsGds32Task" /SYSDBAPASSWORD="masterkey" /SUPPORTLEGACYCLIENTAUTH also do not work. Installs classic. |
Submitted by: Wade Auchterlonie (wadeauch)
Jira_subtask_outward CORE5243
Attachments:
screenshot-1.jpg
Votes: 2
With FB 1.5.3 and earlier, this command line:
Firebird-1.5.3.4870-0-Win32.exe" /SP- /SILENT /NORESTART /COMPONENTS="SuperServerComponent, ServerComponent, DevAdminComponent, ClientComponent"
would result in a super server installation being performed.
The same-ish command for FB 1.5.4:
Firebird-1.5.4.4910-0-Win32.exe" /SP- /SILENT /NORESTART /COMPONENTS="SuperServerComponent, ServerComponent, DevAdminComponent, ClientComponent"
now performs a CLASSIC server install.
This can be verified by removing the /SILENT switch and it may be observed that classic server component is selected.
Running the FB 1.5.4 installer without the components switch, i.e:
Firebird-1.5.4.4910-0-Win32.exe" /SP- /SILENT /NORESTART
results in a super server installation being performed and this may be used as a work-around.
The text was updated successfully, but these errors were encountered: