SQL Server 2017 crashes when backing up because filepath is wrong
I was trying to restore my database and SQL Server kept crashing. I would get a message in SSMS that said there was a network transport error (the connection dropped bc the crash). I checked the logs and found nothing more than SQL Server closed unexpectedly. I would then have to go and restart the service.
I narrowed the issue down to the script that the GUI was trying to run. The problem is when it goes to take a tail log backup, the path to the backup files is wrong. It should be D:mapbenefits...
BACKUP LOG [mapbenefits]
TO DISK = N'D:mapbenefits_LogBackup_2019-02-21_13-58-24.bak'
WITH NOFORMAT, NOINIT, NAME = N'mapbenefits_LogBackup_2019-02-21_13-58-24',
NOSKIP, NOREWIND, NOUNLOAD, NORECOVERY , STATS = 5
I have two questions.
How do I fix this path? I tried going into the server settings and the backup path is
D:with no slash. If I add the slash the gui removes it. This is SSMS v17.9.1. I can pickD:mapbenefitsand that works but I wantD:DATABASE...Is this a bug? Should SQL server crash just because a path is incorrectly typed? Once I fixed the file path it has no trouble. I can reproduce anytime just by mucking up the filepath.
If I run a query to check version I get CU13, but if I go into settings I see version 14.0.1000.169.
Looks like this is a bug and is reproducible so I posted it to here: https://feedback.azure.com/forums/908035-sql-server/suggestions/36920542-incorrect-filepath-with-backup-log-command-causes
sql-server backup sql-server-2017
asked 8 hours ago
RickRick
905
add a comment |
I was trying to restore my database and SQL Server kept crashing. I would get a message in SSMS that said there was a network transport error (the connection dropped bc the crash). I checked the logs and found nothing more than SQL Server closed unexpectedly. I would then have to go and restart the service.
I narrowed the issue down to the script that the GUI was trying to run. The problem is when it goes to take a tail log backup, the path to the backup files is wrong. It should be D:mapbenefits...
BACKUP LOG [mapbenefits]
TO DISK = N'D:mapbenefits_LogBackup_2019-02-21_13-58-24.bak'
WITH NOFORMAT, NOINIT, NAME = N'mapbenefits_LogBackup_2019-02-21_13-58-24',
NOSKIP, NOREWIND, NOUNLOAD, NORECOVERY , STATS = 5
I have two questions.
How do I fix this path? I tried going into the server settings and the backup path is
D:with no slash. If I add the slash the gui removes it. This is SSMS v17.9.1. I can pickD:mapbenefitsand that works but I wantD:DATABASE...Is this a bug? Should SQL server crash just because a path is incorrectly typed? Once I fixed the file path it has no trouble. I can reproduce anytime just by mucking up the filepath.
If I run a query to check version I get CU13, but if I go into settings I see version 14.0.1000.169.
Looks like this is a bug and is reproducible so I posted it to here: https://feedback.azure.com/forums/908035-sql-server/suggestions/36920542-incorrect-filepath-with-backup-log-command-causes
sql-server backup sql-server-2017
asked 8 hours ago
RickRick
905
2
Rick, if you have a support agreement with Microsoft would you be able to open a ticket? That would be helpful. In addition, I've circulated this post internally.
– DBArgenis
2 hours ago
add a comment |
I was trying to restore my database and SQL Server kept crashing. I would get a message in SSMS that said there was a network transport error (the connection dropped bc the crash). I checked the logs and found nothing more than SQL Server closed unexpectedly. I would then have to go and restart the service.
I narrowed the issue down to the script that the GUI was trying to run. The problem is when it goes to take a tail log backup, the path to the backup files is wrong. It should be D:mapbenefits...
BACKUP LOG [mapbenefits]
TO DISK = N'D:mapbenefits_LogBackup_2019-02-21_13-58-24.bak'
WITH NOFORMAT, NOINIT, NAME = N'mapbenefits_LogBackup_2019-02-21_13-58-24',
NOSKIP, NOREWIND, NOUNLOAD, NORECOVERY , STATS = 5
I have two questions.
How do I fix this path? I tried going into the server settings and the backup path is
D:with no slash. If I add the slash the gui removes it. This is SSMS v17.9.1. I can pickD:mapbenefitsand that works but I wantD:DATABASE...Is this a bug? Should SQL server crash just because a path is incorrectly typed? Once I fixed the file path it has no trouble. I can reproduce anytime just by mucking up the filepath.
If I run a query to check version I get CU13, but if I go into settings I see version 14.0.1000.169.
Looks like this is a bug and is reproducible so I posted it to here: https://feedback.azure.com/forums/908035-sql-server/suggestions/36920542-incorrect-filepath-with-backup-log-command-causes
sql-server backup sql-server-2017
asked 8 hours ago
RickRick
905
I was trying to restore my database and SQL Server kept crashing. I would get a message in SSMS that said there was a network transport error (the connection dropped bc the crash). I checked the logs and found nothing more than SQL Server closed unexpectedly. I would then have to go and restart the service.
I narrowed the issue down to the script that the GUI was trying to run. The problem is when it goes to take a tail log backup, the path to the backup files is wrong. It should be D:mapbenefits...
BACKUP LOG [mapbenefits]
TO DISK = N'D:mapbenefits_LogBackup_2019-02-21_13-58-24.bak'
WITH NOFORMAT, NOINIT, NAME = N'mapbenefits_LogBackup_2019-02-21_13-58-24',
NOSKIP, NOREWIND, NOUNLOAD, NORECOVERY , STATS = 5
I have two questions.
How do I fix this path? I tried going into the server settings and the backup path is
D:with no slash. If I add the slash the gui removes it. This is SSMS v17.9.1. I can pickD:mapbenefitsand that works but I wantD:DATABASE...Is this a bug? Should SQL server crash just because a path is incorrectly typed? Once I fixed the file path it has no trouble. I can reproduce anytime just by mucking up the filepath.
If I run a query to check version I get CU13, but if I go into settings I see version 14.0.1000.169.
Looks like this is a bug and is reproducible so I posted it to here: https://feedback.azure.com/forums/908035-sql-server/suggestions/36920542-incorrect-filepath-with-backup-log-command-causes
sql-server backup sql-server-2017
sql-server backup sql-server-2017
asked 8 hours ago
RickRick
905
asked 8 hours ago
RickRick
905
edited 7 hours ago
Rick
asked 8 hours ago
RickRick
905
asked 8 hours ago
RickRick
905
asked 8 hours ago
RickRick
905
905
2
Rick, if you have a support agreement with Microsoft would you be able to open a ticket? That would be helpful. In addition, I've circulated this post internally.
– DBArgenis
2 hours ago
add a comment |
2
Rick, if you have a support agreement with Microsoft would you be able to open a ticket? That would be helpful. In addition, I've circulated this post internally.
– DBArgenis
2 hours ago
2
2
Rick, if you have a support agreement with Microsoft would you be able to open a ticket? That would be helpful. In addition, I've circulated this post internally.
– DBArgenis
2 hours ago
Rick, if you have a support agreement with Microsoft would you be able to open a ticket? That would be helpful. In addition, I've circulated this post internally.
– DBArgenis
2 hours ago
add a comment |
1 Answer
1
active
oldest
votes
On 2016, if I put an invalid path like that, I get this message:
Cannot open backup device 'D:mapbenefits_LogBackup_2019-02-21_13-58-24.bak'. Operating system error 3(The system cannot find the path specified.)
On 2017 CU 13 (14.0.3048.4), it results in the service crashing. You've already mentioned that in the latest hotfix (14.0.3049.1), the service doesn't crash, but the session is killed. I'd be concerned about what this does to your backup history.
If I put a "valid" path that doesn't exist, I get the correct behavior ("cannot find the path specified") in 2017.
This looks like a bug to me - in both CU 13 and the hotfix build. Passing incorrect parameters to the BACKUP command shouldn't crash the service or kill your session. You can report it on the feedback site.
answered 7 hours ago
jadarnel27jadarnel27
5,46811937
Thanks, I reported it. Were you able to reproduce in 2017 or are you just summarizing?
– Rick
7 hours ago
2
@Rick Yes, I repro'd on 2017 CU 13. Interesting bug you found!
– jadarnel27
7 hours ago
Just glad I found it on this new server I'm building before production moves over! :-)
– Rick
7 hours ago
@Rick Haha yes, that is good news =)
– jadarnel27
45 mins ago
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%2f230419%2fsql-server-2017-crashes-when-backing-up-because-filepath-is-wrong%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
On 2016, if I put an invalid path like that, I get this message:
Cannot open backup device 'D:mapbenefits_LogBackup_2019-02-21_13-58-24.bak'. Operating system error 3(The system cannot find the path specified.)
On 2017 CU 13 (14.0.3048.4), it results in the service crashing. You've already mentioned that in the latest hotfix (14.0.3049.1), the service doesn't crash, but the session is killed. I'd be concerned about what this does to your backup history.
If I put a "valid" path that doesn't exist, I get the correct behavior ("cannot find the path specified") in 2017.
This looks like a bug to me - in both CU 13 and the hotfix build. Passing incorrect parameters to the BACKUP command shouldn't crash the service or kill your session. You can report it on the feedback site.
answered 7 hours ago
jadarnel27jadarnel27
5,46811937
Thanks, I reported it. Were you able to reproduce in 2017 or are you just summarizing?
– Rick
7 hours ago
2
@Rick Yes, I repro'd on 2017 CU 13. Interesting bug you found!
– jadarnel27
7 hours ago
Just glad I found it on this new server I'm building before production moves over! :-)
– Rick
7 hours ago
@Rick Haha yes, that is good news =)
– jadarnel27
45 mins ago
add a comment |
On 2016, if I put an invalid path like that, I get this message:
Cannot open backup device 'D:mapbenefits_LogBackup_2019-02-21_13-58-24.bak'. Operating system error 3(The system cannot find the path specified.)
On 2017 CU 13 (14.0.3048.4), it results in the service crashing. You've already mentioned that in the latest hotfix (14.0.3049.1), the service doesn't crash, but the session is killed. I'd be concerned about what this does to your backup history.
If I put a "valid" path that doesn't exist, I get the correct behavior ("cannot find the path specified") in 2017.
This looks like a bug to me - in both CU 13 and the hotfix build. Passing incorrect parameters to the BACKUP command shouldn't crash the service or kill your session. You can report it on the feedback site.
answered 7 hours ago
jadarnel27jadarnel27
5,46811937
Thanks, I reported it. Were you able to reproduce in 2017 or are you just summarizing?
– Rick
7 hours ago
2
@Rick Yes, I repro'd on 2017 CU 13. Interesting bug you found!
– jadarnel27
7 hours ago
Just glad I found it on this new server I'm building before production moves over! :-)
– Rick
7 hours ago
@Rick Haha yes, that is good news =)
– jadarnel27
45 mins ago
add a comment |
On 2016, if I put an invalid path like that, I get this message:
Cannot open backup device 'D:mapbenefits_LogBackup_2019-02-21_13-58-24.bak'. Operating system error 3(The system cannot find the path specified.)
On 2017 CU 13 (14.0.3048.4), it results in the service crashing. You've already mentioned that in the latest hotfix (14.0.3049.1), the service doesn't crash, but the session is killed. I'd be concerned about what this does to your backup history.
If I put a "valid" path that doesn't exist, I get the correct behavior ("cannot find the path specified") in 2017.
This looks like a bug to me - in both CU 13 and the hotfix build. Passing incorrect parameters to the BACKUP command shouldn't crash the service or kill your session. You can report it on the feedback site.
answered 7 hours ago
jadarnel27jadarnel27
5,46811937
On 2016, if I put an invalid path like that, I get this message:
Cannot open backup device 'D:mapbenefits_LogBackup_2019-02-21_13-58-24.bak'. Operating system error 3(The system cannot find the path specified.)
On 2017 CU 13 (14.0.3048.4), it results in the service crashing. You've already mentioned that in the latest hotfix (14.0.3049.1), the service doesn't crash, but the session is killed. I'd be concerned about what this does to your backup history.
If I put a "valid" path that doesn't exist, I get the correct behavior ("cannot find the path specified") in 2017.
This looks like a bug to me - in both CU 13 and the hotfix build. Passing incorrect parameters to the BACKUP command shouldn't crash the service or kill your session. You can report it on the feedback site.
answered 7 hours ago
jadarnel27jadarnel27
5,46811937
answered 7 hours ago
jadarnel27jadarnel27
5,46811937
answered 7 hours ago
jadarnel27jadarnel27
5,46811937
answered 7 hours ago
jadarnel27jadarnel27
5,46811937
5,46811937
Thanks, I reported it. Were you able to reproduce in 2017 or are you just summarizing?
– Rick
7 hours ago
2
@Rick Yes, I repro'd on 2017 CU 13. Interesting bug you found!
– jadarnel27
7 hours ago
Just glad I found it on this new server I'm building before production moves over! :-)
– Rick
7 hours ago
@Rick Haha yes, that is good news =)
– jadarnel27
45 mins ago
add a comment |
Thanks, I reported it. Were you able to reproduce in 2017 or are you just summarizing?
– Rick
7 hours ago
2
@Rick Yes, I repro'd on 2017 CU 13. Interesting bug you found!
– jadarnel27
7 hours ago
Just glad I found it on this new server I'm building before production moves over! :-)
– Rick
7 hours ago
@Rick Haha yes, that is good news =)
– jadarnel27
45 mins ago
Thanks, I reported it. Were you able to reproduce in 2017 or are you just summarizing?
– Rick
7 hours ago
Thanks, I reported it. Were you able to reproduce in 2017 or are you just summarizing?
– Rick
7 hours ago
2
2
@Rick Yes, I repro'd on 2017 CU 13. Interesting bug you found!
– jadarnel27
7 hours ago
@Rick Yes, I repro'd on 2017 CU 13. Interesting bug you found!
– jadarnel27
7 hours ago
Just glad I found it on this new server I'm building before production moves over! :-)
– Rick
7 hours ago
Just glad I found it on this new server I'm building before production moves over! :-)
– Rick
7 hours ago
@Rick Haha yes, that is good news =)
– jadarnel27
45 mins ago
@Rick Haha yes, that is good news =)
– jadarnel27
45 mins ago
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%2f230419%2fsql-server-2017-crashes-when-backing-up-because-filepath-is-wrong%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
2
Rick, if you have a support agreement with Microsoft would you be able to open a ticket? That would be helpful. In addition, I've circulated this post internally.
– DBArgenis
2 hours ago