This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(102.4, 45%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ET%3C/text%3E%3C/svg%3E)
Hello, I went to do a fresh install SQL Server 2019 Enterprise (on a brand new empty Windows Server 2019 VM) and at the end it gave me the following error message:
BUTTONS:
&Retry
Cancel
This is strange being the first time I've ever encountered a SQL Server install error message near the end of installation as I've successfully installed many SQL Servers before.
I checked that help link but nothing related helpful appears.
I clicked on the Retry button a few times but immediately does not proceed and remains with same error message...sounds like something is wrong.
Is it safe to press the [Cancel] button and retry SQL Install again?
I'm just wondering since I noticed the "...Program Files\Microsoft SQL Server"...etc folders have already been created on the disks and is it safe to try install again on top of them now that it's not a fresh/clean install...or do I need to do something else (like remove these new SQL Server folders/files, uninstall Program, Services...)?
Thanks in advance.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 2%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESX%3C/text%3E%3C/svg%3E)
Hi @techresearch7777777 ,
We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.
Best regards,
Seeya
Hi @techresearch7777777 ,
In order to benefit all community members who are having this similar issue, please choose an answer to accept or vote for the answer you think is useful to you. Your contribution is highly appreciated.
Best regards,
Seeya
I would try again, just to see if it is my lucky day. But it may fail again. Since it is a new VM, I would not worry too much about making matters worse. Just recreate a VM. Or take a snaoshot before you move on.
What that error message implies; I have no idea. It could be that something is a bit too locked down in that VM image.
I tried re-running the install but was not allowing me to continue/failing due to that my previous initial attempt failed at the very end and looks like SQL Server files/registries already got written onto disks and its system.
Believe it now thinks SQL Server is already installed which it isn’t.
Sounds like it might've been underlying disk related permissions on a particular drive.
I've asked our VM team to do an entire VM restore just prior my initial SQL Server failed install and will ask them to ensure the permissions/configurations are done before I try another SQL Server install.
Thanks all for trying to help.
Hi @techresearch7777777 ,
Please refer to this MS document:
To resolve this problem, create a subfolder in the volume mount point, and assign the new subfolder to the SQL Server system folders.
Best regards,
Seeya
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Thanks for all of the replies, much appreciated.
Sorry if dumb question...but I don't quite understand "create a subfolder in the volume mount point, and assign the new subfolder to the SQL Server system folders."
What/where is the volume mount point?...is that referring to where SQL Server's system DBs (master, msdb, model) are located or something different?
When you add a disk to a system, instead of giving it a drive letter, you can mount it as, for instance, C:\SomeFolder\MyNewDiskHere.
Whether this applies in your case, I don't know. But I guess Seeya gave you this reference, since the error message matches the article in question. If you are uncertain whether mount points are in use, you may want to talk to the person who set up the VM.
By the way, I took the liberty to convert you Answer to a Comment. Answers are for answers to the original question. As the poster of the question, you would only post an Answer if you find the solution yourself.
Hi ,
A volume mount point is a folder on an NTFS volume that is used to mount the volume. For example, if you have a volume mounted at E:, you could create a subfolder within that volume called SQLServerData or something similar, and then assign that folder to the SQL Server system folders. This will allow SQL Server to access the folder and its contents.
Ok good to know differences between Answers/Comments posts.
Please excuse my limited disk experience from VM Admin team angle, trying to understand both of your replies for my situation.
Sounds like solution is more like a mapped/alias name/shortcut sub-folder point serving as letter drive ?
This server is aimed to be a Prod server and Microsoft's solution looks like to be a workaround...if yes then maybe its safer/better to ask VM team to give me new clean full empty VM server restored backup just prior my failed SQL Server install here.
But wondering if same error message will appear near the end of my 2nd SQL Server install and if maybe its OS configuration related needs to be addressed before VM team gives me fresh server?
If any other thoughts am open ears.
Thanks bunch.
Hi,
Please refer to this document:
Best regards,
Seeya