Windows 10: Version 1709 (OS Build 16299.19)
WSL: Ubuntu 16.04
Following the guide here. I get an error in Step 4 when running sudo /opt/mssql/bin/mssql-conf setup
➜ x git:(master) ✗ sudo /opt/mssql/bin/mssql-conf setup
[sudo] password for devlin:
Locale en_GB not supported. Using en_US.
Choose an edition of SQL Server:
1) Evaluation (free, no production use rights, 180-day limit)
2) Developer (free, no production use rights)
3) Express (free)
4) Web (PAID)
5) Standard (PAID)
6) Enterprise (PAID)
7) Enterprise Core (PAID)
8) I bought a license through a retail sales channel and have a product key to enter.
Details about editions can be found at
https://go.microsoft.com/fwlink/?LinkId=852748
Use of PAID editions of this software requires separate licensing through a
Microsoft Volume Licensing program.
By choosing a PAID edition, you are verifying that you have the appropriate
number of licenses in place to install and run this software.
Enter your edition(1-8): 2
The license terms for this product can be found in
/usr/share/doc/mssql-server or downloaded from:
https://go.microsoft.com/fwlink/?LinkId=855862
The privacy statement can be viewed at:
https://go.microsoft.com/fwlink/?LinkId=853010
Choose the language for SQL Server:
(1) English
(2) Deutsch
(3) Español
(4) Français
(5) Italiano
(6) 日本語語
(7) 한국어어
(8) Português
(9) Русский
(10) 中文 – 简体体
(11) 中文 （繁体））
Enter Option 1-11: 1
Enter the SQL Server system administrator password:
Confirm the SQL Server system administrator password:
Configuring SQL Server...
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:
Reason: 0x00000003
Message: fd != -1
Stacktrace: 00007f15f48346e3 00007f15f41e76ba 00007f15f17e73dd
Process: 2186 - sqlservr
Thread: 2187
Instance Id: 5b1c8da3-1358-48d3-a563-25468ff2ab69
Crash Id: 577efbb6-5740-4ee5-92f6-0ddc0eea685f
Build stamp: 1fdc73777d57c7c1942f388381b8f6ac2c50f005e35b808c23f54dfecdf59384
*********** PANIC CORE DUMP GENERATION FAILED **********
Attempt to launch handle-crash.sh failed with error 0x0000000C
/opt/mssql/lib/mssql-conf/invokesqlservr.sh: line 15: 2185 Aborted (core dumped) sudo -EH -u mssql
/bin/bash -c "$CMDLINE"
Failed to connect to bus: No such file or directory
Attempting to start the Microsoft SQL Server service failed.
Any help would be appreciated.
Update 04/2021: Still not supported
From this docs:Install SQL Server and create a database on Ubuntu
At this time, the Windows Subsystem for Linux for Windows 10 is not supported as an installation target.
So your installation is not supported
Related
It's my first days in Manjaro and I am having problem with configuring SQL Server. When I enter sudo ./mssql-conf setup in lib folder of SQL Server, it says I should enter admin password. After I enter the password it says :
/opt/mssql/bin/sqlservr: /usr/lib/libldap_r-2.4.so.2: no version
information available (required by /opt/mssql/bin/sqlservr) sqlservr:
The configuration file '/var/opt/mssql/mssql.conf' failed to load
(error: Line 0: The INI file is formatted incorrectly. File must
contain at least one section.). Initial setup of Microsoft SQL Server
failed. Please consult the ERRORLOG in /var/opt/mssql/log for more
information.
I'm using the following guide to install MSSQL server on my ubuntu 16.04 machine
https://learn.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu?view=sql-server-2017
when I'm running:
sudo /opt/mssql/bin/mssql-conf setup
no matter what kind of SQL Server edition I choose, I'm getting the following error:
Confirm the SQL Server system administrator password:
Configuring SQL Server...
This program has encountered a fatal error and cannot continue running at Mon Apr 1 16:06:07 2019
The following diagnostic information is available:
Reason: 0x00000007
Message: Cannot open or read the persistent registry: \SystemRoot\security.hiv.
Process: 19600 - sqlservr
Thread: 19604 (application thread 0x4)
Instance Id: 7ebfcf27-db60-460d-afd3-6d852b70069e
Crash Id: d99ba388-d323-43f3-b758-e116f42bb2e8
Build stamp: 70437f6583b8ef39b1ef70539ef84690980315dc7a4436c9c40015f28610e4aa
Distribution: Ubuntu 16.04.6 LTS
Processors: 8
Total Memory: 16673366016 bytes
Timestamp: Mon Apr 1 16:06:07 2019
Ubuntu 16.04.6 LTS
Capturing core dump and information to /var/opt/mssql/log...
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
/usr/bin/tail: cannot open '/var/log/syslog' for reading: Permission denied
Attempting to capture a dump with paldumper
Captured a dump with paldumper
Core dump and information are being compressed in the background. When
complete, they can be found in the following location:
/var/opt/mssql/log/core.sqlservr.04_01_2019_16_06_07.19600.tbz2
Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG
in /var/opt/mssql/log for more information.
also I found this post, which look like this guy had a similar problem, but sadly no solution
does any one knows how to solve my problem?
Thank you
Edit:
after implementing the answer I got another error:
Confirm the SQL Server system administrator password:
Configuring SQL Server...
Initial setup of Microsoft SQL Server failed. Please consult the ERRORLOG in /var/opt/mssql/log for more information
To make some clean in the mess that I had in the log folder I decided to delete it completely using
sudo rm -rf /var/opt/mssql/log
and re-run the setup, Apparently that solved my last problem and finally:
Setup has completed successfully. SQL Server is now starting.
You'll find further information in
/var/opt/mssql/log
Mine said:
{
"reason": "0x00000007",
"processName": "sqlservr",
"pid": "5773",
"instanceId": "d7df749c-50e6-4f3b-b894-2aa7c743f33d",
"crashId": "281e772a-5946-4349-aa9e-671cd0a3772c",
"threadId": "5777",
"libosThreadId": "0x4",
"buildStamp": "70437f6583b8ef39b1ef70539ef84690980315dc7a4436c9c40015f28610e4aa",
"message": "Cannot open or read the persistent registry: \\SystemRoot\\lsa.hiv.",
"last_errno": "13",
"last_errno_text": "Permission denied",
"distribution": "Ubuntu 16.04.6 LTS",
"processors": "4",
"total_memory": "16732037120",
"timestamp": "Fri Apr 12 22:02:44 2019"
}
So I ran locate to see where "systemroot" is located:
locate security.hiv
/var/opt/mssql/.system/system/security.hiv
I didn't know which permissions should be applied, so I just gave read&write to "others".
then the same with
lsa.hiv
licensing.hiv
re-run
sudo /opt/mssql/bin/mssql-conf setup
and then, sql-server starts, plus the permissions for others are gone again.
By the way, you can run sql-server without service, then it works even if the service fails:
/opt/mssql/bin/sqlservr
In my case (#Mine) it was not only licensing.hiv.
My /var/opt/mssql/.system/instance_id was somehow destroyed and there were more files with owner root.
After deleting /var/opt/mssql/.system/instance_id and changing all root.root files to mssql.mssql (chown mssql.mssql /var/opt/mssql/.system/system/*), I was able to rerun "/opt/mssql/bin/mssql-conf setup"
Afterwards mssql runs fine again
I very goog hint was that "/var/opt/mssql/.system/instance_id" runs on his own.
When I installed MS SQL Server for Linux half a year ago, there was no way to choose between evaluation and developer. Now the evaluation period has expired and I can't install a developer version. I don't care about any of my databases and I have tried to remove SQL Server before installing it again. The installation is fine but when I run mssql-conf setup I get the following:
Configuring SQL Server...
Error: The evaluation period has expired.
This program has encountered a fatal error and cannot continue running.
The following diagnostic information is available:
Reason: 0x00000001
Signal: SIGSEGV - Segmentation fault (11)
Stacktrace: 0000564434051ee7 00007f9892387b20 00005644340236c2
000056443404a8db 000056443404a059
Process: 7228 - sqlservr
Thread: 7253 (application thread 0x1060)
Instance Id: 357ebf86-214d-4100-b14f-cb62b380917e
Crash Id:
Build stamp: 3db4cdd88f9bbf816f82e0ab6e17825a0a0f8b2ef98a5c67b521be0ed19c297c
/opt/mssql/lib/mssql-conf/invokesqlservr.sh: line 15: 7227 Aborted sudo -EH -u mssql /bin/bash -c "$CMDLINE"
Setup has completed successfully. SQL Server is now starting.
The last line is wrong, SQL Server does not start.
I assume that uninstallation leaves some trace of my old evaluation that is detected when I try to set up the new developer installation. Anyone knows if there is a way to get rid of whatever is blocking the new install?
TIA,
Gunnar
Shane's comment answered the question. Replacing the repository according to https://learn.microsoft.com/en-us/sql/linux/quickstart-install-connect-suse did the trick!
When trying to install postgreSQL using the graphical windows installer x64 it fails to install this as a Windows Service
>Windows Specific Configuraton
>[14:07:54] Windows Actions (services)
>Starting service "PostgreSQL 9.6 Server"
>Executing sc start "PostgreSQL 9.6 Server"
>Script exit code: 1060
>
>Script output:
> [SC] StartService: OpenService FAILED 1060:
>
>The specified service does not exist as an installed service.
>
>
>Script stderr:
> Program ended with an error exit code
>
>Error running sc start "PostgreSQL 9.6 Server": Program ended with an error >exit code
>Problem running post-install step. Installation may not complete correctly
> Error running sc start "PostgreSQL 9.6 Server": Program ended with an error >exit code
How do I correct this, and why did it happen?
You can try to install the service manually, using
pg_ctl register [-N servicename] [-U username] [-P password] [-D datadir] [-S a[uto] | d[emand] ] [-w] [-t seconds] [-s] [-o options]
According to PostgreSQL documentation on pg_ctl:
register mode allows you to register a system service on Microsoft Windows. The -S option allows selection of service start type, either "auto" (start service automatically on system startup) or "demand" (start service on demand).
If pg_ctl cannot register the service, it will most probably give a proper error message, pointing you in the proper direction (incorrect datadir, insufficient privileges for username to access and write to datadir, etc.)
The "standard" servicename used by the Graphical Installer (at least with the EnterpriseDB one) is: postgresql-x64-9.6 for PostgreSQL 64-bit version 9.6.*.
I am trying to install JDE EnterpiriseOne on a virtual machine running win7, i followed the instructions in this video :
JDE 9.1 stanalone instalation toturial
I installed "EnterpiriseOne Database Engine" of course after installing oracle client, but i cannot continue to install the "EnterpiriseOne E910 Standalone client"...
it seems to be a problem with the oracle universal Universal installer finding a running Database, i checked the listener services and found that they are running...
typed the command (lsnrctl status) in cmd, and got the following:
LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 27-JUL-2013 18:38
:12
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.119.128)(PORT=15
21)))
TNS-12535: TNS:operation timed out
TNS-12560: TNS:protocol adapter error
TNS-00505: Operation timed out
64-bit Windows Error: 60: Unknown error
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Produ
ction
Start Date 27-JUL-2013 17:14:33
Uptime 0 days 1 hr. 24 min. 1 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File c:\Oracle\E1Local\network\admin\listener.ora
Listener Log File c:\oracle\diag\tnslsnr\WIN-I3MMKFMQE20\listener\alert\
log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.119.128)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
PLZ anyone what can i do to complete the instalation???
On your tnsnames.ora and listener.ora try to change the HOST value for 127.0.0.1. Then restart the database and the listener services.
Instead of 127.0.0.1 change it to hostname. It worked fine for me after changing this to hostname.