I am getting a crash immediately at startup with an exe4j executable on Windows Server 2012 R2.
Turned on redirect of stderr and stdout to try to get any message at all, but failed.
Tried 'run as administrator', failed.
Rebuilt the executable, failed.
At this point I cannot think of anything new to try. Can someone offer a suggestion?
Below are the problem details from the windows dialog. Any idea what could be causing this?
Problem signature:
Problem Event Name: BEX64
Application Name: DCoreX64.exe
Application Version: 9.1.0.0
Application Timestamp: 54d098c4
Fault Module Name: DCoreX64.exe
Fault Module Version: 9.1.0.0
Fault Module Timestamp: 54d098c4
Exception Offset: 00000000000049d0
Exception Code: c0000409
Exception Data: 0000000000000000
OS Version: 6.3.9600.2.0.0.400.8
Locale ID: 1033
Additional Information 1: 1678
Additional Information 2: 16789cf0f420663251ee660bfee7765e
Additional Information 3: 415a
Additional Information 4: 415aeefa71c8c47ed34c12722ba51457
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=280262
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
My issue turned out to be that the classpath was too long. Exe4j put out a new release to address it.
Related
I have been trying to upgrade SQL server 2017 to run Python 3.7. We have installed CU28 and the product version is 14.0.3430.2 which includes the C:\Program Files\Microsoft SQL Server\MSSQL14.INSTANCENAME\PYTHON_SERVICES.3.7.
I have made sure all permissions are granted to the INSTANCENAME directory and pythonlauncher.config working directory is pointing to C:\Program Files\Microsoft SQL Server\MSSQL14.INSTANCENAME\MSSQL\ExtensibilityData and launchpad service account has permissions to this directory.
I have done all this as an upgrade twice and got various errors, and a clean install. The error I am getting is
Msg 39004, Level 16, State 20, Line 0
A 'Python' script error occurred during execution of 'sp_execute_external_script' with HRESULT 0x80004004.
Msg 39019, Level 16, State 2, Line 0
An external script error occurred:
Invalid BXL stream
error while running BxlServer: caught exception: Error communicating between BxlServer and client: 0x000000e8
HRESULT 0x000000e8 looks like INVALID_CANCEL_OF_FILE_OPEN
HRESULT 0x80004004 looks like E_ABORT
So no real clues what is wrong here. pythonlauncher.log does show the error;
[Error] Process::TryTerminate failed with error code: 5
Session 0E93E9D1-07A7-448A-8B1A-FCA5263A5F53 TryTerminate(1067) failed with 5
Error code 5 is ERROR_ACCESS_DENIED
Also got this warning
[Warning] StaleDirectoryCleaner() failed to delete C:\Program Files\Microsoft SQL Server\MSSQL14.INSTANCENAME\MSSQL\ExtensibilityData\FAMSQL17UAT01\8B97815A-E9EA-4FA0-98F3-0440D4180522 after 5 retries
So all up this looks there are still permission issues. Extremely frustrating as there is next to no help on this. Any help would be greatly appreciated.
UPDATE:
After another clean install - first checked Python 3.5.2 worked and it did. Upgraded to 3.7, and again got the same issue. A bit more digging around I find this...
The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/SERVERNAME.domain_name.com:INSTANCENAME ]
Login failed for user 'DOMAIN\SERVERNAME$'. Reason: Could not find a login matching the name provided.
We have a service account that is not part of the domain which is NT Service\MSSQL$INSTANCENAME. Why on this implementation expecting a windows authenticated user the same name as the server??? How can I go about remedy this?
I think what has happened is that MS have left debug code in their production release.
FURTHER UPDATE:
In the event log we are seeing
Faulting application:Python.exe: 3.7.1150.1013 Faulting module name:
pylink.pyd Faulting module path:c:\Program Files\Microsoft SQL
Server\MSSQL14.INSTANCENAME\PYTHON_SERVICES.3.7\lib\site-packages\revoscalepy\rxLibs\pylink.pyd
Microsoft have confirmed that this is a bug. Their work around is below.
It's CU27 and CU28 that 3.7 is broken in - so you could use CU26 and still use Python 3.7. That version started at CU22... so CU22-26 work fine.
Or - it's only the pylink.pyd that is broken - you can simply grab the pylink.pyd from a CU22-26 installation for Python 3.7, and swap it into your CU27/CU28 files. This workaround will work now, and will also not cause any issues going forward once the fix does come. That is, on your next update, it shouldn't interfere and it should all go smoothly.
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!
Lately I’ve been getting an intermittent error when running Internet Explorer Automation using Selenium WebDriver on a virtual machine. The tests are being running on Virtual Machine through Microsoft Test Manger. I’m having a hard time figuring out what is going on.
The following is logged for the test that was trying run when this problem occured:
exception: OpenQA.Selenium.WebDriverException: The HTTP request to the remote WebDriver server for URL http://localhost:56645/session/2762cafb-d3c9-4d9a-a0a5-05463e69b7b7/moveto timed out after 60 seconds. ---> System.Net.WebException: The operation has timed out
When a test fails I write the Exception message and stack trace to a file. But in this case there really is no stack. Was expecting something deeper.
System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetResponse()
at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)
Here is detail from eventviewer when the failure occured:
Log Name: Application
Source: Application Error
Date: 8/28/2015 9:02:09 AM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxxxxxxxxxx
Description:
Faulting application name: IEDriverServer.exe, version: 2.44.0.0, time stamp: 0x5449666f
Faulting module name: IED4C2A.tmp, version: 0.0.0.0, time stamp: 0x5449666b
Exception code: 0xc0000005
Fault offset: 0x000a41e6
Faulting process id: 0xf2c
Faulting application start time: 0x01d0e191ad6d3d19
Faulting application path: C:\AutomationDrivers\IEDriverServer.exe
Faulting module path: C:\Users\SACCTO~Z\AppData\Local\Temp\IED4C2A.tmp
Report Id: fd4f5070-4d84-11e5-891b-00155d6e673e
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-08-28T13:02:09.000000000Z" />
<EventRecordID>14302</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxxxxxxxxxxxxxxxx</Computer>
<Security />
</System>
<EventData>
<Data>IEDriverServer.exe</Data>
<Data>2.44.0.0</Data>
<Data>5449666f</Data>
<Data>IED4C2A.tmp</Data>
<Data>0.0.0.0</Data>
<Data>5449666b</Data>
<Data>c0000005</Data>
<Data>000a41e6</Data>
<Data>f2c</Data>
<Data>01d0e191ad6d3d19</Data>
<Data>C:\AutomationDrivers\IEDriverServer.exe</Data>
<Data>C:\Users\TASKBO~1\AppData\Local\Temp\IED4C2A.tmp</Data>
<Data>fd4f5070-4d84-11e5-891b-00155d6e673e</Data>
</EventData>
</Event>
I can run the same test locally using the test runner built into Visual studio without any problems. The VM has about 1.5 Gig of memory and never uses up more than half of it while the tests are running. CPU stays fairly low.
Am running out of idea on things to look at. Any thought/ideas appreciated. Thank you.
I have written two articles on how to create good crash dumps when the Windows Error Reporting dialog is shown.
The first article describes how to attach a debugger, basically:
wait for the WER dialog to be shown
attach a debugger (like windbg)
press the "Debug" button
confirm the warning that a debugger is already attached
click "No" when asked to use the selected debugger
now do whatever you like in your debugger, e.g. create a dump with .dump /ma seleniumcrash.dmp
If you're not so familiar using a debugger, try the second article, which activates LocalDumps just in time, which is:
wait for the WER dialog to be shown
create WER LocalDumps Registry entries for the application that crashed. Make sure you set DumpType to 2 and the folder is writable (check NTFS permissions).
Close the WER dialog
Once you have the good crash dumps, you can get much more information out of them, such as the call stack and .NET callstack.
The event viewer exception code is 0xc0000005, which is an access violation aka. NullReferenceException in .NET.
I'm trying to install SQL Server 2008 R2 express on my fresh win 7 ultimate x64 install. Every time the installation starts, it crashes with the following message:
Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: setup100.exe
Application Version: 10.50.1600.1
Application Timestamp: 4bb6742c
Fault Module Name: mscorwks.dll
Fault Module Version: 2.0.50727.4952
Fault Module Timestamp: 4bebe78c
Exception Code: c0000005
Exception Offset: 00000000001e41a0
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Did anyone had similar problem? how did you solve?
So here are some ideas to try if they help. First, I assume that you're installing the 64bit version of SQL Express? Also, the faulting module is a .NET component, so maybe try repairing .NET 2.0? Finally, I'm not sure this would work, but as a last-ditch effort, you could reboot to safe mode and try the installation from there. I know these are just shots-in-the-dark, but if 300 billion web pages don't have the answer, then maybe some random tests might get lucky.
In my experience SQL express installs tend to crash (well over the past 5 years anyway) when you install direct from the web. I would allways recommend downloading the complete install package, then runing it from a local folder. Everytime the direct web install has crashed for me (probably around a dozen time now accross various versions), downloading the full install and then running it locally has lead to a clean install.