been trying to follow this method for a while, but i keep running into the same problem.
during step 05, it's telling me i already have a MSSQLSERVER instance installed. so when selecting "default" and clicking "next" I get an error because it already exists. so instead i create a new one with a new name in order to get through installation. I don't know how to delete the already existing MSSQLSERVER.
later down the line when i'm at step 10, I cannot connect to the .\BWDATOOLSET server and receive this message: Cannot connect to .\BWDATOOLSET. Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL Server is configured to allow remote connection. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specifies) (Microsoft SQL Server)
So, to get through connecting to your new instance... First question is, did you name the instance "BWDATOOLSET" during the installation? (Just making sure.)
Search your Start Menu for a program called "SQL Server 2022 Configuration Manager" and start it. In the tree on the left there should be a node labeled "SQL Server Services" -- click on that. On the right you should see a few entries. The row you're interested in will have the value "SQL Server" in the "Service Type" column, and the name should be "SQL Server (INSTANCE_NAME)". The value in parenthesis is the instance name you used on the "Instance Configuration" page during setup. The default instance is named "MSSQLSERVER". If you named your instance "BWDATOOLSET", then it should show up. Double check the spelling of the instance name (you don't know how many times I accidentally typed "BWDATATOOLSET"). Also make sure that row has the value "Running" in the "State" column. If that's not the case, right click on the row and click "Start."
Also in this tool you can check how the server instance is configured to accept connections. In the left side tree, expand the "SQL Server Network Configuration" node and select "Protocols for INSTANCE_NAME". The only entry you need to have enabled is "Shared Memory".
This tool also allows you to configure what protocols are used by applications that connect to SQL Server. If you expand the other nodes for client configuration you will see entries for "Client Protocols". Make sure that "Shared Memory" is enabled (and, preferably, have an "Order" value of "1".) for them.
As for removing the old default instance, you'd have to go through your installed programs and remove other instances and versions of MS SQL Server.
i dont have SQL Server 2022 Configuration Manager and have no idea how to get it (i search online and can't find any installs for a program called that). at this point i'm just trying to remove any trace of SQL from my PC so i can start over from scratch, but I can't delete the Microsoft SQL Server folder from my programs files because it says it open in another program. how do i delete this folder so i can restart?
i just wanted to say THANK YOU for this i can't believe i was finally able to get the toolset and i owe it all to you !! i had to do an extra step of installing an attribute changer to get rid of the system folder attribute of my game folder and it worked like a charm im so happy <333
I followed the tutorial, but I have a big problem, when I create morphs I can't find the file saved in the toolset and when I try to create new creatures it can't load the inventory, leaving the basic naked character as the only option, I think it's a "connection" problem, but I have no idea how to fix it, can anyone help me?
sending my thanks! this guide was so helpful and easy to follow! <3 i thought i was at a lost with not being able to get the toolset to launch and work until i was sent here! now im able to use the toolset with no issues! thank you again!!
you're a lifesaver, i got the toolset to work before after a LOT of trial and error, but i couldn't remember how i did it. this was so easy and it works way better this time! <3
Worked perfectly! Very clear and simple instructions, I didn't understand a word of it, I just had to follow to the letter. I dreaded having to install the toolset on Win10 after the guessing game of "what the heck went wrong" that characterized installing it on previous Windows versions, so having it be this painless for once was a treat! (Plus, like others have said, it's extra nice not having to keep using outdated software.) Thank you so much!
If you have Windows 11 and modern SSD (like NVMe), there could be an issue with disk "sector size" diffs.. SQL server knows how to use 512 bytes and 4Kb sizes for writing (although SQL Express 2022 should normally work by some sources, but have not tried) while most of NVMe disks have "sector size" set to 16Kb.. If so, you can try to check here for solution..
Give Feedback
28 comments
during step 05, it's telling me i already have a MSSQLSERVER instance installed. so when selecting "default" and clicking "next" I get an error because it already exists. so instead i create a new one with a new name in order to get through installation. I don't know how to delete the already existing MSSQLSERVER.
later down the line when i'm at step 10, I cannot connect to the .\BWDATOOLSET server and receive this message:
Cannot connect to .\BWDATOOLSET.
Additional information:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL Server is configured to allow remote connection. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specifies) (Microsoft SQL Server)
Search your Start Menu for a program called "SQL Server 2022 Configuration Manager" and start it. In the tree on the left there should be a node labeled "SQL Server Services" -- click on that. On the right you should see a few entries. The row you're interested in will have the value "SQL Server" in the "Service Type" column, and the name should be "SQL Server (INSTANCE_NAME)". The value in parenthesis is the instance name you used on the "Instance Configuration" page during setup. The default instance is named "MSSQLSERVER". If you named your instance "BWDATOOLSET", then it should show up. Double check the spelling of the instance name (you don't know how many times I accidentally typed "BWDATATOOLSET"). Also make sure that row has the value "Running" in the "State" column. If that's not the case, right click on the row and click "Start."
Also in this tool you can check how the server instance is configured to accept connections. In the left side tree, expand the "SQL Server Network Configuration" node and select "Protocols for INSTANCE_NAME". The only entry you need to have enabled is "Shared Memory".
This tool also allows you to configure what protocols are used by applications that connect to SQL Server. If you expand the other nodes for client configuration you will see entries for "Client Protocols". Make sure that "Shared Memory" is enabled (and, preferably, have an "Order" value of "1".) for them.
As for removing the old default instance, you'd have to go through your installed programs and remove other instances and versions of MS SQL Server.
at this point i'm just trying to remove any trace of SQL from my PC so i can start over from scratch, but I can't delete the Microsoft SQL Server folder from my programs files because it says it open in another program. how do i delete this folder so i can restart?
Uninstalled my 2008 setup and re-installed with 2022 following your guide. Time to ditch my 2008 mock up guide xD
I love step-by-step tutorials!
Awesome work! Thanks for this :D
database engine services: failed
'Error installing SQL Server Database Engine Services Instance Features
The system cannot find the path specified
Error code: 0x80004005'
any help?
SQL server knows how to use 512 bytes and 4Kb sizes for writing (although SQL Express 2022 should normally work by some sources, but have not tried) while most of NVMe disks have "sector size" set to 16Kb..
If so, you can try to check here for solution..
Cheers!