Error starting SQL Server 2017 service. Error Code 3417 The 2019 Stack Overflow Developer...
Why not take a picture of a closer black hole?
What information about me do stores get via my credit card?
What other Star Trek series did the main TNG cast show up in?
Why doesn't shell automatically fix "useless use of cat"?
How did passengers keep warm on sail ships?
What's the point in a preamp?
Example of compact Riemannian manifold with only one geodesic.
Keeping a retro style to sci-fi spaceships?
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
Didn't get enough time to take a Coding Test - what to do now?
Could an empire control the whole planet with today's comunication methods?
What do I do when my TA workload is more than expected?
Why doesn't a hydraulic lever violate conservation of energy?
Student Loan from years ago pops up and is taking my salary
should truth entail possible truth
My body leaves; my core can stay
60's-70's movie: home appliances revolting against the owners
Would an alien lifeform be able to achieve space travel if lacking in vision?
Loose spokes after only a few rides
How did the audience guess the pentatonic scale in Bobby McFerrin's presentation?
Presidential Pardon
Is this wall load bearing? Blueprints and photos attached
Are there continuous functions who are the same in an interval but differ in at least one other point?
Windows 10: How to Lock (not sleep) laptop on lid close?
Error starting SQL Server 2017 service. Error Code 3417
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)error code 3417 - after installing CU for SQL SERVER 2016 SP1Upgrade to SQL Server 2017 FailsCluster node upgrade of SQL Server 2008 R2 to SP3 fails when moving resourceSQL Server 2008 service keeps crashingService Broker cryptographic errorSQL Server not starting after SQL Server 2016 SP1 CU6Upgraded to SQL Server 2017 and now see WSFC lease timeoutsSQL Server 2017 Management Data Warehouse: collection_set_1 not working due to database triggerFailure during install of SQL Server 2016 sp2Cannot Start SQL Server 2017?error code 3417 - after installing CU for SQL SERVER 2016 SP1Upgrade to SQL Server 2017 Fails
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have SQL Server 2017 installed on my computer. This is what SELECT @@VERSION returns:
Microsoft SQL Server 2017 (RTM-GDR) (KB4293803) - 14.0.2002.14 (X64) Jul 21 2018 07:47:45 Copyright (C) 2017 Microsoft Corporation Enterprise Edition (64-bit) on Windows 10 Enterprise 10.0 (Build 17134: )`
It was working fine until yesterday. Suddenly SQL SERVER Service did not run. When I wanted to run the service manually it showed 3417 error. When I checked event log I saw this error:
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.`
After some googling I found out I can run it with /T902 switch and try to fix the problem. But no solution worked for me. So I installed another instance of the same SQL SERVER 2017 and restored databases. Now the new installed instance has the same problem.
What could be the problem?
UPDATE
Here is the full error log of SQL Server.
2018-09-17 13:06:47.29 spid6s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Creating SSIS folders...
2018-09-17 13:06:47.30 spid6s Dropping procedure [dbo].[sp_syscollector_get_instmdw]
2018-09-17 13:06:47.30 spid6s Creating procedure [dbo].[sp_syscollector_get_instmdw]...
2018-09-17 13:06:47.30 spid6s Dropping procedure [dbo].[sp_syscollector_upload_instmdw]
2018-09-17 13:06:47.30 spid6s Creating procedure [dbo].[sp_syscollector_upload_instmdw]...
2018-09-17 13:06:47.30 spid6s Uploading data collector package from disk: c:Program FilesMicrosoft SQL ServerMSSQL14.SQL2017MSSQLInstallSqlTraceCollect.dtsx
2018-09-17 13:06:47.30 spid6s Uploading data collector package from disk: c:Program FilesMicrosoft SQL ServerMSSQL14.SQL2017MSSQLInstallSqlTraceCollect.dtsx
2018-09-17 13:06:47.30 spid6s Error: 2775, Severity: 17, State: 12.
2018-09-17 13:06:47.30 spid6s The code page 65001 is not supported by the server.
2018-09-17 13:06:47.30 spid6s Error: 912, Severity: 21, State: 2.
2018-09-17 13:06:47.30 spid6s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2018-09-17 13:06:47.30 spid6s Error: 3417, Severity: 21, State: 3.
2018-09-17 13:06:47.30 spid6s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2018-09-17 13:06:47.30 spid6s SQL Server shutdown has been initiated
2018-09-17 13:06:47.30 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
UPDATE
This line has something to tell. The code page 65001 is not supported by the server. My recently windows updated to Version 1803 (OS Build 17134.285). After this update some applications texts has changed to unknown characters. Can this be the cause of the problem?
SOLUTION
Uncheck Beta: Use Unicode UTF-8 for worldwide language support in Control Panel -> Region -> Administrative -> Change System Locale and restart the computer.
This solved my problem. As @Shanky stated in his answer this seems to be a bug.
sql-server windows sql-server-2017 character-set encoding
edited Feb 18 at 9:53
jdoeadeer
31
asked Sep 17 '18 at 6:57
BeginnerBeginner
1335
add a comment |
I have SQL Server 2017 installed on my computer. This is what SELECT @@VERSION returns:
Microsoft SQL Server 2017 (RTM-GDR) (KB4293803) - 14.0.2002.14 (X64) Jul 21 2018 07:47:45 Copyright (C) 2017 Microsoft Corporation Enterprise Edition (64-bit) on Windows 10 Enterprise 10.0 (Build 17134: )`
It was working fine until yesterday. Suddenly SQL SERVER Service did not run. When I wanted to run the service manually it showed 3417 error. When I checked event log I saw this error:
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.`
After some googling I found out I can run it with /T902 switch and try to fix the problem. But no solution worked for me. So I installed another instance of the same SQL SERVER 2017 and restored databases. Now the new installed instance has the same problem.
What could be the problem?
UPDATE
Here is the full error log of SQL Server.
2018-09-17 13:06:47.29 spid6s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Creating SSIS folders...
2018-09-17 13:06:47.30 spid6s Dropping procedure [dbo].[sp_syscollector_get_instmdw]
2018-09-17 13:06:47.30 spid6s Creating procedure [dbo].[sp_syscollector_get_instmdw]...
2018-09-17 13:06:47.30 spid6s Dropping procedure [dbo].[sp_syscollector_upload_instmdw]
2018-09-17 13:06:47.30 spid6s Creating procedure [dbo].[sp_syscollector_upload_instmdw]...
2018-09-17 13:06:47.30 spid6s Uploading data collector package from disk: c:Program FilesMicrosoft SQL ServerMSSQL14.SQL2017MSSQLInstallSqlTraceCollect.dtsx
2018-09-17 13:06:47.30 spid6s Uploading data collector package from disk: c:Program FilesMicrosoft SQL ServerMSSQL14.SQL2017MSSQLInstallSqlTraceCollect.dtsx
2018-09-17 13:06:47.30 spid6s Error: 2775, Severity: 17, State: 12.
2018-09-17 13:06:47.30 spid6s The code page 65001 is not supported by the server.
2018-09-17 13:06:47.30 spid6s Error: 912, Severity: 21, State: 2.
2018-09-17 13:06:47.30 spid6s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2018-09-17 13:06:47.30 spid6s Error: 3417, Severity: 21, State: 3.
2018-09-17 13:06:47.30 spid6s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2018-09-17 13:06:47.30 spid6s SQL Server shutdown has been initiated
2018-09-17 13:06:47.30 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
UPDATE
This line has something to tell. The code page 65001 is not supported by the server. My recently windows updated to Version 1803 (OS Build 17134.285). After this update some applications texts has changed to unknown characters. Can this be the cause of the problem?
SOLUTION
Uncheck Beta: Use Unicode UTF-8 for worldwide language support in Control Panel -> Region -> Administrative -> Change System Locale and restart the computer.
This solved my problem. As @Shanky stated in his answer this seems to be a bug.
sql-server windows sql-server-2017 character-set encoding
edited Feb 18 at 9:53
jdoeadeer
31
asked Sep 17 '18 at 6:57
BeginnerBeginner
1335
add a comment |
I have SQL Server 2017 installed on my computer. This is what SELECT @@VERSION returns:
Microsoft SQL Server 2017 (RTM-GDR) (KB4293803) - 14.0.2002.14 (X64) Jul 21 2018 07:47:45 Copyright (C) 2017 Microsoft Corporation Enterprise Edition (64-bit) on Windows 10 Enterprise 10.0 (Build 17134: )`
It was working fine until yesterday. Suddenly SQL SERVER Service did not run. When I wanted to run the service manually it showed 3417 error. When I checked event log I saw this error:
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.`
After some googling I found out I can run it with /T902 switch and try to fix the problem. But no solution worked for me. So I installed another instance of the same SQL SERVER 2017 and restored databases. Now the new installed instance has the same problem.
What could be the problem?
UPDATE
Here is the full error log of SQL Server.
2018-09-17 13:06:47.29 spid6s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Creating SSIS folders...
2018-09-17 13:06:47.30 spid6s Dropping procedure [dbo].[sp_syscollector_get_instmdw]
2018-09-17 13:06:47.30 spid6s Creating procedure [dbo].[sp_syscollector_get_instmdw]...
2018-09-17 13:06:47.30 spid6s Dropping procedure [dbo].[sp_syscollector_upload_instmdw]
2018-09-17 13:06:47.30 spid6s Creating procedure [dbo].[sp_syscollector_upload_instmdw]...
2018-09-17 13:06:47.30 spid6s Uploading data collector package from disk: c:Program FilesMicrosoft SQL ServerMSSQL14.SQL2017MSSQLInstallSqlTraceCollect.dtsx
2018-09-17 13:06:47.30 spid6s Uploading data collector package from disk: c:Program FilesMicrosoft SQL ServerMSSQL14.SQL2017MSSQLInstallSqlTraceCollect.dtsx
2018-09-17 13:06:47.30 spid6s Error: 2775, Severity: 17, State: 12.
2018-09-17 13:06:47.30 spid6s The code page 65001 is not supported by the server.
2018-09-17 13:06:47.30 spid6s Error: 912, Severity: 21, State: 2.
2018-09-17 13:06:47.30 spid6s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2018-09-17 13:06:47.30 spid6s Error: 3417, Severity: 21, State: 3.
2018-09-17 13:06:47.30 spid6s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2018-09-17 13:06:47.30 spid6s SQL Server shutdown has been initiated
2018-09-17 13:06:47.30 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
UPDATE
This line has something to tell. The code page 65001 is not supported by the server. My recently windows updated to Version 1803 (OS Build 17134.285). After this update some applications texts has changed to unknown characters. Can this be the cause of the problem?
SOLUTION
Uncheck Beta: Use Unicode UTF-8 for worldwide language support in Control Panel -> Region -> Administrative -> Change System Locale and restart the computer.
This solved my problem. As @Shanky stated in his answer this seems to be a bug.
sql-server windows sql-server-2017 character-set encoding
edited Feb 18 at 9:53
jdoeadeer
31
asked Sep 17 '18 at 6:57
BeginnerBeginner
1335
I have SQL Server 2017 installed on my computer. This is what SELECT @@VERSION returns:
Microsoft SQL Server 2017 (RTM-GDR) (KB4293803) - 14.0.2002.14 (X64) Jul 21 2018 07:47:45 Copyright (C) 2017 Microsoft Corporation Enterprise Edition (64-bit) on Windows 10 Enterprise 10.0 (Build 17134: )`
It was working fine until yesterday. Suddenly SQL SERVER Service did not run. When I wanted to run the service manually it showed 3417 error. When I checked event log I saw this error:
Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.`
After some googling I found out I can run it with /T902 switch and try to fix the problem. But no solution worked for me. So I installed another instance of the same SQL SERVER 2017 and restored databases. Now the new installed instance has the same problem.
What could be the problem?
UPDATE
Here is the full error log of SQL Server.
2018-09-17 13:06:47.29 spid6s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Configuration option 'Agent XPs' changed from 1 to 1. Run the RECONFIGURE statement to install.
2018-09-17 13:06:47.29 spid6s Creating SSIS folders...
2018-09-17 13:06:47.30 spid6s Dropping procedure [dbo].[sp_syscollector_get_instmdw]
2018-09-17 13:06:47.30 spid6s Creating procedure [dbo].[sp_syscollector_get_instmdw]...
2018-09-17 13:06:47.30 spid6s Dropping procedure [dbo].[sp_syscollector_upload_instmdw]
2018-09-17 13:06:47.30 spid6s Creating procedure [dbo].[sp_syscollector_upload_instmdw]...
2018-09-17 13:06:47.30 spid6s Uploading data collector package from disk: c:Program FilesMicrosoft SQL ServerMSSQL14.SQL2017MSSQLInstallSqlTraceCollect.dtsx
2018-09-17 13:06:47.30 spid6s Uploading data collector package from disk: c:Program FilesMicrosoft SQL ServerMSSQL14.SQL2017MSSQLInstallSqlTraceCollect.dtsx
2018-09-17 13:06:47.30 spid6s Error: 2775, Severity: 17, State: 12.
2018-09-17 13:06:47.30 spid6s The code page 65001 is not supported by the server.
2018-09-17 13:06:47.30 spid6s Error: 912, Severity: 21, State: 2.
2018-09-17 13:06:47.30 spid6s Script level upgrade for database 'master' failed because upgrade step 'msdb110_upgrade.sql' encountered error 200, state 7, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.
2018-09-17 13:06:47.30 spid6s Error: 3417, Severity: 21, State: 3.
2018-09-17 13:06:47.30 spid6s Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.
2018-09-17 13:06:47.30 spid6s SQL Server shutdown has been initiated
2018-09-17 13:06:47.30 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
UPDATE
This line has something to tell. The code page 65001 is not supported by the server. My recently windows updated to Version 1803 (OS Build 17134.285). After this update some applications texts has changed to unknown characters. Can this be the cause of the problem?
SOLUTION
Uncheck Beta: Use Unicode UTF-8 for worldwide language support in Control Panel -> Region -> Administrative -> Change System Locale and restart the computer.
This solved my problem. As @Shanky stated in his answer this seems to be a bug.
sql-server windows sql-server-2017 character-set encoding
sql-server windows sql-server-2017 character-set encoding
edited Feb 18 at 9:53
jdoeadeer
31
asked Sep 17 '18 at 6:57
BeginnerBeginner
1335
edited Feb 18 at 9:53
jdoeadeer
31
asked Sep 17 '18 at 6:57
BeginnerBeginner
1335
edited Feb 18 at 9:53
jdoeadeer
31
edited Feb 18 at 9:53
jdoeadeer
31
edited Feb 18 at 9:53
jdoeadeer
31
31
asked Sep 17 '18 at 6:57
BeginnerBeginner
1335
asked Sep 17 '18 at 6:57
BeginnerBeginner
1335
asked Sep 17 '18 at 6:57
BeginnerBeginner
1335
1335
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
I would start by saying that you are running SQL Server 2017 on Windows 10 (client OS) which is not supported see Hardware and Software requirements for SQL Server 2017. You are wasting the capability of enterprise edition and lot of money by running it on client OS.
Plus I believe such issues are mostly bugs so I would suggest you to apply latest SQL Server 2017 CU 10. Let me know if that fixes you issue. If you want to try out workaround for this issues please refer to This Blog.
As confirmed by OP the issues did not solved even after applying SQL Server 2017 CU10.
EDIT: The problem starts with below statement
2018-09-17 13:06:47.30 spid6s The code page 65001 is not supported by the server.
The code page 65001 means UTF 8 encoding which is not supported by SQL Server and this I believe is causing the issue. This is definitely a BUG I am perplexed why this is still not fixed in CU10. The upgrade process is trying to bulk load data having UTF 8 encoding and since SQL Server does not supports it, it is failing.
You have windows 10 go to control pane, now select region and language applet, it might be just region for you on Windows 10. Go to administrative tab and in the lower part of tab you have to click on change system Locale and then go ahead and activate/select the Beta: UTF8 Support and start the windows machine. Below is what options look from my windows 7 machine. The option might be almost same for Windows 10.
As conformed by OP the whole issues started after applying certain OS patch. The issue was resolved after unchecking the "Beta:UTF8 support". The issue seems to be 2 things.
OP already has Beta:UTF8 Support checked and was running fine until he applied OS patch which changed "something".
The issue resolved after unchecking Beta:UTF8 Support from control panel with OS patch already there.
The SQL Server was running fine with Beta:UTF8 Support but when OS patch was applied "something" broke in such a way that SQL Server master database was not able to come online which message that code page 65001 is not supported. Disabling Beta:UTF8 from control panel resolved the issue. Although I believe this is more of a workaround and MS need to come out with proper KB article for this.
PS: I also found Connect Bug already raised for this issue. When I say not supported(for installing Enterprise edition on client OS) that does not means you cannot run this infrastructure it only means you are on your own if you hit some "bug" or something fails unexpectedly. If you raise case with MS about any such issue I am sure they would point this out.
answered Sep 17 '18 at 7:26
ShankyShanky
14.5k32144
Finally I installed the update. Before installing the update I started the SQL Server Service with /T902 switch. But unfortunately it did not solve the problem. Still getting the same error.
– Beginner
Sep 17 '18 at 8:41
Ok, so this means SQL Server is not coming online right ?. Can you refer to "The Blog" link in the answer and see if that helps you. Please also add the complete SQL Server errorlog in the question.
– Shanky
Sep 17 '18 at 9:01
I guess then it is better to remove the OS update you installed, seems like it is breaking things for you.
– Shanky
Sep 17 '18 at 14:24
1
I Unchecked Beta: UTF8 Support in Regoin and restarted the computer. Now both SQL Server instances are running.
– Beginner
Sep 18 '18 at 5:12
1
@Beginner and Shanky: I checked that file (C:Program FilesMicrosoft SQL ServerMSSQL14.MSSQLSERVERMSSQLInstallSqlTraceCollect.dtsx) in Notepad++ and it shows an encoding of "UCS-2 LE BOM", which is really UTF-16 LE, which in Microsoft-land is called "Unicode". Not sure if the bug is in Windows or SQL Server, but given that the file has a Byte Order Mark (BOM), it shouldn't have attempted to read it as UTF-8 regardless of the system's default encoding. That is, after all, the entire purpose of having the BOM ;-) The file even starts with:<?xml version="1.0" encoding="utf-16"?>.
– Solomon Rutzky
Oct 2 '18 at 16:46
|
show 1 more comment
Tuve el mismo problema por varios dias y probe soluciones diferentes con varios tutoriales y foros y era tan simple como la compatibilidad, gracias por el aporte. El problema se resolvió después de desmarcar la opción "Beta: UTF8 support"
answered 7 mins ago
fredy de la torrefredy de la torre
1
New contributor
fredy de la torre is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f217759%2ferror-starting-sql-server-2017-service-error-code-3417%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I would start by saying that you are running SQL Server 2017 on Windows 10 (client OS) which is not supported see Hardware and Software requirements for SQL Server 2017. You are wasting the capability of enterprise edition and lot of money by running it on client OS.
Plus I believe such issues are mostly bugs so I would suggest you to apply latest SQL Server 2017 CU 10. Let me know if that fixes you issue. If you want to try out workaround for this issues please refer to This Blog.
As confirmed by OP the issues did not solved even after applying SQL Server 2017 CU10.
EDIT: The problem starts with below statement
2018-09-17 13:06:47.30 spid6s The code page 65001 is not supported by the server.
The code page 65001 means UTF 8 encoding which is not supported by SQL Server and this I believe is causing the issue. This is definitely a BUG I am perplexed why this is still not fixed in CU10. The upgrade process is trying to bulk load data having UTF 8 encoding and since SQL Server does not supports it, it is failing.
You have windows 10 go to control pane, now select region and language applet, it might be just region for you on Windows 10. Go to administrative tab and in the lower part of tab you have to click on change system Locale and then go ahead and activate/select the Beta: UTF8 Support and start the windows machine. Below is what options look from my windows 7 machine. The option might be almost same for Windows 10.
As conformed by OP the whole issues started after applying certain OS patch. The issue was resolved after unchecking the "Beta:UTF8 support". The issue seems to be 2 things.
OP already has Beta:UTF8 Support checked and was running fine until he applied OS patch which changed "something".
The issue resolved after unchecking Beta:UTF8 Support from control panel with OS patch already there.
The SQL Server was running fine with Beta:UTF8 Support but when OS patch was applied "something" broke in such a way that SQL Server master database was not able to come online which message that code page 65001 is not supported. Disabling Beta:UTF8 from control panel resolved the issue. Although I believe this is more of a workaround and MS need to come out with proper KB article for this.
PS: I also found Connect Bug already raised for this issue. When I say not supported(for installing Enterprise edition on client OS) that does not means you cannot run this infrastructure it only means you are on your own if you hit some "bug" or something fails unexpectedly. If you raise case with MS about any such issue I am sure they would point this out.
answered Sep 17 '18 at 7:26
ShankyShanky
14.5k32144
Finally I installed the update. Before installing the update I started the SQL Server Service with /T902 switch. But unfortunately it did not solve the problem. Still getting the same error.
– Beginner
Sep 17 '18 at 8:41
Ok, so this means SQL Server is not coming online right ?. Can you refer to "The Blog" link in the answer and see if that helps you. Please also add the complete SQL Server errorlog in the question.
– Shanky
Sep 17 '18 at 9:01
I guess then it is better to remove the OS update you installed, seems like it is breaking things for you.
– Shanky
Sep 17 '18 at 14:24
1
I Unchecked Beta: UTF8 Support in Regoin and restarted the computer. Now both SQL Server instances are running.
– Beginner
Sep 18 '18 at 5:12
1
@Beginner and Shanky: I checked that file (C:Program FilesMicrosoft SQL ServerMSSQL14.MSSQLSERVERMSSQLInstallSqlTraceCollect.dtsx) in Notepad++ and it shows an encoding of "UCS-2 LE BOM", which is really UTF-16 LE, which in Microsoft-land is called "Unicode". Not sure if the bug is in Windows or SQL Server, but given that the file has a Byte Order Mark (BOM), it shouldn't have attempted to read it as UTF-8 regardless of the system's default encoding. That is, after all, the entire purpose of having the BOM ;-) The file even starts with:<?xml version="1.0" encoding="utf-16"?>.
– Solomon Rutzky
Oct 2 '18 at 16:46
|
show 1 more comment
I would start by saying that you are running SQL Server 2017 on Windows 10 (client OS) which is not supported see Hardware and Software requirements for SQL Server 2017. You are wasting the capability of enterprise edition and lot of money by running it on client OS.
Plus I believe such issues are mostly bugs so I would suggest you to apply latest SQL Server 2017 CU 10. Let me know if that fixes you issue. If you want to try out workaround for this issues please refer to This Blog.
As confirmed by OP the issues did not solved even after applying SQL Server 2017 CU10.
EDIT: The problem starts with below statement
2018-09-17 13:06:47.30 spid6s The code page 65001 is not supported by the server.
The code page 65001 means UTF 8 encoding which is not supported by SQL Server and this I believe is causing the issue. This is definitely a BUG I am perplexed why this is still not fixed in CU10. The upgrade process is trying to bulk load data having UTF 8 encoding and since SQL Server does not supports it, it is failing.
You have windows 10 go to control pane, now select region and language applet, it might be just region for you on Windows 10. Go to administrative tab and in the lower part of tab you have to click on change system Locale and then go ahead and activate/select the Beta: UTF8 Support and start the windows machine. Below is what options look from my windows 7 machine. The option might be almost same for Windows 10.
As conformed by OP the whole issues started after applying certain OS patch. The issue was resolved after unchecking the "Beta:UTF8 support". The issue seems to be 2 things.
OP already has Beta:UTF8 Support checked and was running fine until he applied OS patch which changed "something".
The issue resolved after unchecking Beta:UTF8 Support from control panel with OS patch already there.
The SQL Server was running fine with Beta:UTF8 Support but when OS patch was applied "something" broke in such a way that SQL Server master database was not able to come online which message that code page 65001 is not supported. Disabling Beta:UTF8 from control panel resolved the issue. Although I believe this is more of a workaround and MS need to come out with proper KB article for this.
PS: I also found Connect Bug already raised for this issue. When I say not supported(for installing Enterprise edition on client OS) that does not means you cannot run this infrastructure it only means you are on your own if you hit some "bug" or something fails unexpectedly. If you raise case with MS about any such issue I am sure they would point this out.
answered Sep 17 '18 at 7:26
ShankyShanky
14.5k32144
Finally I installed the update. Before installing the update I started the SQL Server Service with /T902 switch. But unfortunately it did not solve the problem. Still getting the same error.
– Beginner
Sep 17 '18 at 8:41
Ok, so this means SQL Server is not coming online right ?. Can you refer to "The Blog" link in the answer and see if that helps you. Please also add the complete SQL Server errorlog in the question.
– Shanky
Sep 17 '18 at 9:01
I guess then it is better to remove the OS update you installed, seems like it is breaking things for you.
– Shanky
Sep 17 '18 at 14:24
1
I Unchecked Beta: UTF8 Support in Regoin and restarted the computer. Now both SQL Server instances are running.
– Beginner
Sep 18 '18 at 5:12
1
@Beginner and Shanky: I checked that file (C:Program FilesMicrosoft SQL ServerMSSQL14.MSSQLSERVERMSSQLInstallSqlTraceCollect.dtsx) in Notepad++ and it shows an encoding of "UCS-2 LE BOM", which is really UTF-16 LE, which in Microsoft-land is called "Unicode". Not sure if the bug is in Windows or SQL Server, but given that the file has a Byte Order Mark (BOM), it shouldn't have attempted to read it as UTF-8 regardless of the system's default encoding. That is, after all, the entire purpose of having the BOM ;-) The file even starts with:<?xml version="1.0" encoding="utf-16"?>.
– Solomon Rutzky
Oct 2 '18 at 16:46
|
show 1 more comment
I would start by saying that you are running SQL Server 2017 on Windows 10 (client OS) which is not supported see Hardware and Software requirements for SQL Server 2017. You are wasting the capability of enterprise edition and lot of money by running it on client OS.
Plus I believe such issues are mostly bugs so I would suggest you to apply latest SQL Server 2017 CU 10. Let me know if that fixes you issue. If you want to try out workaround for this issues please refer to This Blog.
As confirmed by OP the issues did not solved even after applying SQL Server 2017 CU10.
EDIT: The problem starts with below statement
2018-09-17 13:06:47.30 spid6s The code page 65001 is not supported by the server.
The code page 65001 means UTF 8 encoding which is not supported by SQL Server and this I believe is causing the issue. This is definitely a BUG I am perplexed why this is still not fixed in CU10. The upgrade process is trying to bulk load data having UTF 8 encoding and since SQL Server does not supports it, it is failing.
You have windows 10 go to control pane, now select region and language applet, it might be just region for you on Windows 10. Go to administrative tab and in the lower part of tab you have to click on change system Locale and then go ahead and activate/select the Beta: UTF8 Support and start the windows machine. Below is what options look from my windows 7 machine. The option might be almost same for Windows 10.
As conformed by OP the whole issues started after applying certain OS patch. The issue was resolved after unchecking the "Beta:UTF8 support". The issue seems to be 2 things.
OP already has Beta:UTF8 Support checked and was running fine until he applied OS patch which changed "something".
The issue resolved after unchecking Beta:UTF8 Support from control panel with OS patch already there.
The SQL Server was running fine with Beta:UTF8 Support but when OS patch was applied "something" broke in such a way that SQL Server master database was not able to come online which message that code page 65001 is not supported. Disabling Beta:UTF8 from control panel resolved the issue. Although I believe this is more of a workaround and MS need to come out with proper KB article for this.
PS: I also found Connect Bug already raised for this issue. When I say not supported(for installing Enterprise edition on client OS) that does not means you cannot run this infrastructure it only means you are on your own if you hit some "bug" or something fails unexpectedly. If you raise case with MS about any such issue I am sure they would point this out.
answered Sep 17 '18 at 7:26
ShankyShanky
14.5k32144
I would start by saying that you are running SQL Server 2017 on Windows 10 (client OS) which is not supported see Hardware and Software requirements for SQL Server 2017. You are wasting the capability of enterprise edition and lot of money by running it on client OS.
Plus I believe such issues are mostly bugs so I would suggest you to apply latest SQL Server 2017 CU 10. Let me know if that fixes you issue. If you want to try out workaround for this issues please refer to This Blog.
As confirmed by OP the issues did not solved even after applying SQL Server 2017 CU10.
EDIT: The problem starts with below statement
2018-09-17 13:06:47.30 spid6s The code page 65001 is not supported by the server.
The code page 65001 means UTF 8 encoding which is not supported by SQL Server and this I believe is causing the issue. This is definitely a BUG I am perplexed why this is still not fixed in CU10. The upgrade process is trying to bulk load data having UTF 8 encoding and since SQL Server does not supports it, it is failing.
You have windows 10 go to control pane, now select region and language applet, it might be just region for you on Windows 10. Go to administrative tab and in the lower part of tab you have to click on change system Locale and then go ahead and activate/select the Beta: UTF8 Support and start the windows machine. Below is what options look from my windows 7 machine. The option might be almost same for Windows 10.
As conformed by OP the whole issues started after applying certain OS patch. The issue was resolved after unchecking the "Beta:UTF8 support". The issue seems to be 2 things.
OP already has Beta:UTF8 Support checked and was running fine until he applied OS patch which changed "something".
The issue resolved after unchecking Beta:UTF8 Support from control panel with OS patch already there.
The SQL Server was running fine with Beta:UTF8 Support but when OS patch was applied "something" broke in such a way that SQL Server master database was not able to come online which message that code page 65001 is not supported. Disabling Beta:UTF8 from control panel resolved the issue. Although I believe this is more of a workaround and MS need to come out with proper KB article for this.
PS: I also found Connect Bug already raised for this issue. When I say not supported(for installing Enterprise edition on client OS) that does not means you cannot run this infrastructure it only means you are on your own if you hit some "bug" or something fails unexpectedly. If you raise case with MS about any such issue I am sure they would point this out.
answered Sep 17 '18 at 7:26
ShankyShanky
14.5k32144
edited Sep 18 '18 at 6:35
answered Sep 17 '18 at 7:26
ShankyShanky
14.5k32144
answered Sep 17 '18 at 7:26
ShankyShanky
14.5k32144
answered Sep 17 '18 at 7:26
ShankyShanky
14.5k32144
14.5k32144
Finally I installed the update. Before installing the update I started the SQL Server Service with /T902 switch. But unfortunately it did not solve the problem. Still getting the same error.
– Beginner
Sep 17 '18 at 8:41
Ok, so this means SQL Server is not coming online right ?. Can you refer to "The Blog" link in the answer and see if that helps you. Please also add the complete SQL Server errorlog in the question.
– Shanky
Sep 17 '18 at 9:01
I guess then it is better to remove the OS update you installed, seems like it is breaking things for you.
– Shanky
Sep 17 '18 at 14:24
1
I Unchecked Beta: UTF8 Support in Regoin and restarted the computer. Now both SQL Server instances are running.
– Beginner
Sep 18 '18 at 5:12
1
@Beginner and Shanky: I checked that file (C:Program FilesMicrosoft SQL ServerMSSQL14.MSSQLSERVERMSSQLInstallSqlTraceCollect.dtsx) in Notepad++ and it shows an encoding of "UCS-2 LE BOM", which is really UTF-16 LE, which in Microsoft-land is called "Unicode". Not sure if the bug is in Windows or SQL Server, but given that the file has a Byte Order Mark (BOM), it shouldn't have attempted to read it as UTF-8 regardless of the system's default encoding. That is, after all, the entire purpose of having the BOM ;-) The file even starts with:<?xml version="1.0" encoding="utf-16"?>.
– Solomon Rutzky
Oct 2 '18 at 16:46
|
show 1 more comment
Finally I installed the update. Before installing the update I started the SQL Server Service with /T902 switch. But unfortunately it did not solve the problem. Still getting the same error.
– Beginner
Sep 17 '18 at 8:41
Ok, so this means SQL Server is not coming online right ?. Can you refer to "The Blog" link in the answer and see if that helps you. Please also add the complete SQL Server errorlog in the question.
– Shanky
Sep 17 '18 at 9:01
I guess then it is better to remove the OS update you installed, seems like it is breaking things for you.
– Shanky
Sep 17 '18 at 14:24
1
I Unchecked Beta: UTF8 Support in Regoin and restarted the computer. Now both SQL Server instances are running.
– Beginner
Sep 18 '18 at 5:12
1
@Beginner and Shanky: I checked that file (C:Program FilesMicrosoft SQL ServerMSSQL14.MSSQLSERVERMSSQLInstallSqlTraceCollect.dtsx) in Notepad++ and it shows an encoding of "UCS-2 LE BOM", which is really UTF-16 LE, which in Microsoft-land is called "Unicode". Not sure if the bug is in Windows or SQL Server, but given that the file has a Byte Order Mark (BOM), it shouldn't have attempted to read it as UTF-8 regardless of the system's default encoding. That is, after all, the entire purpose of having the BOM ;-) The file even starts with:<?xml version="1.0" encoding="utf-16"?>.
– Solomon Rutzky
Oct 2 '18 at 16:46
Finally I installed the update. Before installing the update I started the SQL Server Service with /T902 switch. But unfortunately it did not solve the problem. Still getting the same error.
– Beginner
Sep 17 '18 at 8:41
Finally I installed the update. Before installing the update I started the SQL Server Service with /T902 switch. But unfortunately it did not solve the problem. Still getting the same error.
– Beginner
Sep 17 '18 at 8:41
Ok, so this means SQL Server is not coming online right ?. Can you refer to "The Blog" link in the answer and see if that helps you. Please also add the complete SQL Server errorlog in the question.
– Shanky
Sep 17 '18 at 9:01
Ok, so this means SQL Server is not coming online right ?. Can you refer to "The Blog" link in the answer and see if that helps you. Please also add the complete SQL Server errorlog in the question.
– Shanky
Sep 17 '18 at 9:01
I guess then it is better to remove the OS update you installed, seems like it is breaking things for you.
– Shanky
Sep 17 '18 at 14:24
I guess then it is better to remove the OS update you installed, seems like it is breaking things for you.
– Shanky
Sep 17 '18 at 14:24
1
1
I Unchecked Beta: UTF8 Support in Regoin and restarted the computer. Now both SQL Server instances are running.
– Beginner
Sep 18 '18 at 5:12
I Unchecked Beta: UTF8 Support in Regoin and restarted the computer. Now both SQL Server instances are running.
– Beginner
Sep 18 '18 at 5:12
1
1
@Beginner and Shanky: I checked that file (
C:Program FilesMicrosoft SQL ServerMSSQL14.MSSQLSERVERMSSQLInstallSqlTraceCollect.dtsx) in Notepad++ and it shows an encoding of "UCS-2 LE BOM", which is really UTF-16 LE, which in Microsoft-land is called "Unicode". Not sure if the bug is in Windows or SQL Server, but given that the file has a Byte Order Mark (BOM), it shouldn't have attempted to read it as UTF-8 regardless of the system's default encoding. That is, after all, the entire purpose of having the BOM ;-) The file even starts with: <?xml version="1.0" encoding="utf-16"?>.– Solomon Rutzky
Oct 2 '18 at 16:46
@Beginner and Shanky: I checked that file (
C:Program FilesMicrosoft SQL ServerMSSQL14.MSSQLSERVERMSSQLInstallSqlTraceCollect.dtsx) in Notepad++ and it shows an encoding of "UCS-2 LE BOM", which is really UTF-16 LE, which in Microsoft-land is called "Unicode". Not sure if the bug is in Windows or SQL Server, but given that the file has a Byte Order Mark (BOM), it shouldn't have attempted to read it as UTF-8 regardless of the system's default encoding. That is, after all, the entire purpose of having the BOM ;-) The file even starts with: <?xml version="1.0" encoding="utf-16"?>.– Solomon Rutzky
Oct 2 '18 at 16:46
|
show 1 more comment
Tuve el mismo problema por varios dias y probe soluciones diferentes con varios tutoriales y foros y era tan simple como la compatibilidad, gracias por el aporte. El problema se resolvió después de desmarcar la opción "Beta: UTF8 support"
answered 7 mins ago
fredy de la torrefredy de la torre
1
New contributor
fredy de la torre is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Tuve el mismo problema por varios dias y probe soluciones diferentes con varios tutoriales y foros y era tan simple como la compatibilidad, gracias por el aporte. El problema se resolvió después de desmarcar la opción "Beta: UTF8 support"
answered 7 mins ago
fredy de la torrefredy de la torre
1
New contributor
fredy de la torre is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Tuve el mismo problema por varios dias y probe soluciones diferentes con varios tutoriales y foros y era tan simple como la compatibilidad, gracias por el aporte. El problema se resolvió después de desmarcar la opción "Beta: UTF8 support"
answered 7 mins ago
fredy de la torrefredy de la torre
1
New contributor
fredy de la torre is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Tuve el mismo problema por varios dias y probe soluciones diferentes con varios tutoriales y foros y era tan simple como la compatibilidad, gracias por el aporte. El problema se resolvió después de desmarcar la opción "Beta: UTF8 support"
answered 7 mins ago
fredy de la torrefredy de la torre
1
New contributor
fredy de la torre is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 7 mins ago
fredy de la torrefredy de la torre
1
New contributor
fredy de la torre is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 7 mins ago
fredy de la torrefredy de la torre
1
answered 7 mins ago
fredy de la torrefredy de la torre
1
1
New contributor
fredy de la torre is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
fredy de la torre is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
fredy de la torre is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f217759%2ferror-starting-sql-server-2017-service-error-code-3417%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
