Microsoft sql server ошибка при установке solidworks

Common SOLIDWORKS Electrical Installation Errors

Installations are often blocked by firewall ports, incorrect server name, or a default SQL instance that has already been created. So if you’re dealing with SOLIDWORKS Electrical installation errors or connecting to the SQL Express, check that these common errors are not causing problems.

Firewall Ports

A firewall is an essential barrier to block unwanted communication to your company’s network. It can also cause problems during program installations if the correct firewall ports are not open.

Firewall ports 1433 and 26666 must be open for SOLIDWORKS Electrical to communicate with the SQL and collaborative server. To check if the ports are open, run a telnet test.

1. Go to windows features and turn on the Telnet client.
2. Open a command prompt.
3. In the command prompt type. “ telnet

”

A Default Instance has already been created.

If installing a new SOLIDWORKS Electrical database, occasionally a database of the same name is already installed, or if a previous installation fails, the default SQL database has already been created.

There are two possible solutions.

1. Change the name on the default instance from “yourservernameTEW_SQLEXPRESS” to “yourservernameNewNameHere”
2. Try the “Use an Existing SQL Server Database” option and check “Connect using SQL Server Authentication” and use the default username (SA) and password (same as the ‘tew’ user).

Using “localhost” instead of the computer name

When installing SOLIDWORKS Electrical, it is important to use your computer name instead of the default “localhost”. Change from “localhost”, to your computer name in the Collaborative Server and SQL Server names.

If you have any further questions about SOLIDWORKS Electrical, please contact us .

Editor’s Note: This article was originally published in December 2019 and has been updated for accuracy and comprehensiveness.

Источник

Solidworks microsoft sql server failed to install

Solidworks microsoft sql server failed to install

microsoft sql server failed to install. instance name ‘tew_sqlexpress’ is already in use. to continue, specify a unique instance name. You can also click here. Best Laptops for Solidworks

SOLIDWORKS Electrical is unable to connect to the SQL Server… Error… Possible reasons for this failure: -Incorrect username or pasword -Incorrect server name -Server is unavailable Please check the SQL server settings under the SOLIDWORKS Electrical options.

You can check the SQL server Express log files (located at %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOG). If you are receiving an error about the instance name not being unique, you can manually clean off the orphaned instance name by doing the following:

Please open Add/remove programs and uninstall all the SQL server components.

Delete all the files in software installed location path (For ex: C:Program FilesMicrosoft SQL Server – delete this folder).

Then Open “regedit” (Registry Editor) and delete the below mentioned entries.

1. Click on the Start menu, choose Run and type regedit
2. Go to HKEY_LOCAL_MACHINESoftwareMicrosoftMicrosoft SQL Server
3. Remove SQLEXPRESS from the REG_MULTI_SZ value named InstalledInstances
4. Delete the subhive named MSSQL.1
5. Delete the subhive named SQLEXPRESS
6. Go to HKEY_LOCAL_MACHINESoftwareMicrosoftMicrosoft SQL ServerInstance NamesSQL
7. Delete the value named SQLEXPRESS
8. Delete the folder %ProgramFiles%Microsoft SQL ServerMSSQL.1

if you want clean installation you can delete entirely: HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server

Once completed please restart the machine and start the installation. it will be successfully install without any issues.

Note – the above steps apply to the instance name that is created when SQL Express is installed as a part of Visual Studio 2005. The actual instance name on your system may vary if you have had any other beta version of SQL 2005 (such as the developer edition). Please make sure to adjust the steps accordingly based on what instance name information is in your registry and file system.

Configuring Microsoft SQL Server

You must insure that an instance of the SQL Server database is available for any type of SOLIDWORKS Electrical installation. You can use an existing SQL Server database if it is already installed on the system, or install a new instance as part of the SOLIDWORKS Electrical installation.

When you install a new instance of SQL Server, SOLIDWORKS installation provides a free version of Microsoft SQL Server Express. This version is limited to 1 CPU, 1 GB of memory, and 10 GB of data. The memory and CPU limitations are sufficient to support 5 concurrent users.

If you install SQL Server Express Edition, ensure that the server software and hardware meet the requirements listed http://solidworks.com/System_Requirements.

However, if there are more 6 or more concurrent users on the same server, you should purchase and install a full version of SQL Server, and use the workflow described for installing SOLIDWORKS Electrical with an existing instance of SQL Server.

For information about the SQL Server Express Edition, consult the Microsoft SQL Server documentation.

New Instances of SQL Server

If you install a new instance of SQL Server, you need full administrative rights to the server, and also to any client systems. You must also ensure that clients have read/write privileges for the database, so they can create and modify projects, libraries, symbols and other project data.

When you install a new instance of SQL Server, select a name other than the default.

Existing Instances of SQL Server

You need a user account that has full administrative rights to the SQL Server database to install new SOLIDWORKS Electrical databases or to connect to a SOLIDWORKS Electrical installation on an existing instance of SQL Server.

For SOLIDWORKS Electrical to function properly, you must enable SQL Server for mixed mode authentication. Mixed mode authentication allows the use of either Windows or SQL Server credentials.

To connect to an existing SQL Server database, you can use Windows or SQL Server authentication. Enter a user name and password for a Windows or SQL Server login that has full SQL Server administrative rights.

You cannot use the ‘tew’ user to connect to SQL Server for installation. Contact your SQL Server administrator or system administrator for help to obtain a login with the proper credentials for SQL Server.

Post Installation of SQL Server

After SOLIDWORKS Electrical is installed, the SQL Server instance creates the following databases in SOLIDWORKS Electrical:

• TEW_APP_DATA
• TEW_APP_MACRO
• TEW_APP_PROJECT
• TEW_CATALOG
• TEW_CLASSIFICATION
• TEW_SQLEXPRESS

Источник

SOLIDWORKS Electrical Cannot Connect to Database?!

Article by Justin Flett updated July 2, 2015

Article

One of the most commonly seen errors when trying to launch SOLIDWORKS Electrical is the “cannot connect to database” error. If you have ever run into the error message below, this article will give a how-to guide for quickly and easily resolving the issue.

Cannot connect to database error

This error message may occur for a few reasons, however it most often occurs if the SolidWorks Electrical SQL Server is not running. This issue is very similar to the Collaborative Server error that we have discussed previously, and as expected it can be resolved in a very similar manner.

Step 1: Check that the SQL Service is Running

The first step to check this issue is to check if the SQL Server service is running. This can be found in the Windows Services panel by searching “Services” in the Windows Start->Search for programs and files search bar.

Within the services panel we can scroll to the SQL Server (TEW_SQLEXPRESS) service and notice that under “Status” the service is not started. From here we simply right-click on the service and select Start, and ensure the status has changed to “Started”. Note that the default SolidWorks Electrical SQL instance is named “TEW_SQLEXPRESS” however your particular SQL instance may be named differently as defined during the initial install.

SQL Server (TEW_SQLEXPRESS)

Step 2: Check that the SQL Application Settings are Correct

If you’ve gone through these steps and have confirmed that the SQL service is running however are still receiving the same error message, it could be an issue with your application settings. In this case the next step would be to open SOLIDWORKS Electrical Application Settings (Tools > Application settings) and double check the information in the Databases tab.

Application Setting – Databases

Here we can check the server name, user name, and user password of our SQL instance and make sure we are both pointing to the correct server location and giving the correct authentication information. This SQL authentication information was setup during the initial installation process.

Finally, close and reopen SOLIDWORKS Electrical the error should be gone and we can continue our electrical design work!

Источник

Top 8 Troubleshooting Steps for PDM Connectivity Issues

Using SolidWorks PDM is a great tool to control your revisions and versions, manage your files, etc. However, when it doesn’t work it can become very frustrating. Don’t worry, most issues are usually IT related, which can easily be resolved by following these troubleshooting steps. The most common and generic error when working with PDM is “Cannot access the item in the database” or “Could not find the Server”. Have you experienced this before? Here are our top 8 troubleshooting steps to resolve these issues.

Firstly, about the error – we need to get as much information about the cause of the error. These messages only tell us what the error is, not what caused it. To determine the cause of the error, you’ll need to open up you PDM Administration Tool, the under Local Settings double click on Log File. This will give you a chronological list of errors and warnings, once you find the log at the time you got the error, double click on the entry to get full details.
The description of the PDM Client Log will show you a similar message to “SQL Server does not exist or access denied.” This is the cause of the error and we need to address this.

As PDM is a client server setup, the error could be from your client or from the server. The first question you should ask yourself – is this happening to everyone or just me? If it’s just you, then it’s a client-side issue, if it’s happening to everyone then it’s a server-side issue. We cover both sides in this blog.
Please note, it is assumed you are at least a little experienced with IT troubleshooting processes and have some administration permissions, otherwise, as always, we highly recommend you contact your reseller for support.

Troubleshooting For PDM Client

There are several reasons why this error message can occur. Below are some basic troubleshooting steps that can be performed on PDM client-side to establish connection with SQL Server.

1. Check if the SQL Server Name and Database shown in the log description are correct.

The Server Name and SQL Database information can be found in the error log shown in the image above as well as from the PDM Administration tool. Open PDM Administration tool, right click on the vault and click properties. Consult your IT Team to check if the information about the server is correct.

If the server details shown here are correct, then contact your reseller so they can have a look if the registries of the Vault are correct. You may need Windows Admin log in for your VAR to be able to access and check registries.

2. Check if the client machine can communicate with SQL Server Machine

Perform a “Ping” test to the server machine from your client machine. First ping the server machine by server-name and then use the Server IP address to test. The ping test is a simple DOS command that tests network connectivity, it does not test ports. To access ping test, click Windows Start and type “Command Prompt”, you should right click and open as Administrator. Once open, you’ll need to type “ping SERVERNAME” and press enter, where you put in your Server Name or Server IP Address. Here are a few scenarios:

A. Ping test successful for either of the two but unsuccessful for another

If you can successfully ping the server using server name but no luck with IP address or vice versa, then this shows that this is a DNS Host Name issue.

To resolve this, use Host file to map the IP Address and the Server Machine name and this will fix the DNS issue and the SQL Server should now be recognised.

B. Ping test unsuccessful for both.

If this is the case, then Client machine is not communicating to the Server Machine. Check the network connection and make sure that both machines are on the same Domain Network. If not, you will need some support from your IT to fix the network connection issue.

C. Ping test successful for both

If the ping test returns successful for both, then it is important to test if the ports the client machine communicates to the SQL Server are open. More details about ports are in the next step.

3. Check if the ports used for SQL are open

If SQL is installed and configured to use default ports, then we need to make sure that Ports – TCP 1433 and UDP 1434 are open. To test this, perform a “Telnet” Test.

Remember to turn on the “telnet” client on the client machine for telnet test to work, in Control Panel -> Programs and Features -> Turn Windows features on or off.

To use Telnet to test a port, open Command Prompt again, this time you want to type – telnet

. If you get a blank screen with a blinking cursor then it worked, if you receive an error message then the port is not open.

A. Telnet test Unsuccessful

If the Telnet test returns unsuccessful while the ping tests are successful, this means that the ports are blocked. The ports need to be opened. Contact your IT to make sure they have opened the ports that are being used for SQL.

B. Telnet Test Successful

If Telnet test returns successful, then the ports are open, and the communication should work fine.

If you still receive an error message while accessing the vault, then it is worth ensuring your client machine is using a static TCP port to communicate to the SQL Server – see next step.

4. Force Client Machine to use Static TCP Port for SQL Database communication

To enable a client to use a static port to communicate to SQL Database, an ODBC Test needs to be performed. The easiest way to find the tool is to click Windows Start and type ODBC, you’ll get the 32 and 64 bit version, use the 64 Bit version. When configuring an ODBC Test, it is advisable to use SQL “sa” (System Administration user) log in so please make sure that you have the password easily accessible. If not, please ask your IT/Admin to help you.

While configuring the test, make sure to click Client Configuration. In the dialogue box, alias name and server name will be automatically populated. There is no need to change them. Just uncheck “Dynamically Determine Port” and use the port number that is being used by SQL Server. If it’s a default, then it will be 1433.

Once you get a successful result from this test then you should not have any issues communicating to the SQL Server. Remember to restart your PDM Client.

ODBC Test establishes an ODBC connection alias which will then be used by the client when communicating with the SQL server instance. In most of the cases where the SQL has a named instance (i.e. when the name of the SQL instance hosting the vault database is different than the default name) ODBC Test is required.
When all the above steps are performed and there is still an error message when communicating with SQL Server, then this requires a troubleshooting at the server level.

Troubleshooting on Server Machine

On the server, following are the few basic things that can be checked:

1.Make sure SQL Server Services are running

The list of these services can be checked from the task manager

2.Firewall Settings

As the firewall should be on for protection, please check that all the ports were added to the firewall exception list. Make sure the firewall exceptions are added for both incoming and outgoing. If PDM is configured using default ports, then following is the list of ports that need to be opened:
i. SNL (SolidNetwork License Manager) Ports for PDM Licensing to work properly
a. TCP 25734 & 25735
ii. Archive Server Ports
a. TCP – 3030
b. UDP – 3030
iii. Database Server (SQL Server) Ports
a. TCP – 1433
b. UDP – 1434

3.Force SQL to use Static TCP Port

Open SQL Server Configuration Manager. If you don’t have this tool installed, then press “Windows Key + r” and run “compmgmt.msc” to access the SQL Server Configurations.
Use the following steps to make sure SQL Services are communicating through port 1433 for all IP Addresses.

4.Make sure SQL System Admin (sa) Log in Credentials are correct

There could be couple of scenarios:
A. PDM is configured to use correct “sa” credentials
B. Not sure if PDM Vault is configured with correct “sa” log in credentials or if “sa” login credentials have been changed recently

CASE A: If PDM is configured using correct “sa” credentials, then make sure that vault is using the “default” SQL Login. This setting can be done within the Archive Server Configuration tool. Access the properties – Right Click Vault -> Properties -> Navigate to Login tab. Check the box for “Use default SQL Login”

CASE B: If unsure that PDM was setup using correct “sa” credentials or if “sa” credentials have been changed then you can update PDM to use the correct SQL Password. Follow the steps mentioned above to navigate to the Login tab of the Vault Properties dialogue box and simply uncheck the dialogue box to enter the correct password.

This will not test the password; it will just use this password whenever it needs to. So, if it is wrong you will get the error, however, once you fix up the correct password PDM will begin to work as normal.

Hopefully, you’ve successfully troubleshooted your PDM connectivity issues and are back on track using PDM to help with your SolidWorks designs. It’s always extra satisfying to resolve your own issues.

However, if you have tried all of these troubleshooting steps and solutions and you’re still having these issues, that’s what your reseller support is for. We have some highly experienced PDM application engineers on hand ready to get you back up and running asap.

Arpit Saxena, Applications Engineer Team Leader at CADspace, a SOLIDWORKS Value Added Reseller in Australia.

Источник

Приветствую, господа.

Не забавы ради, а чисто от безысходности своего недоразумения, так сказать.

Ранее пользовался на своем ноуте SW 2015, после перешёл на 2019 версию и она периодически «отваливалась», но работала.

Где-то с год не пользовался SW на своём ноуте, а тут возникла необходимость и началось…

Решил, т.к. были проблемы, переустановить Вин7 заново и, так сказать, начать с чистого листа. Устанавливал сразу SW 2019 sp5.

Начались капризы с SW Electrical: не мог он принять SQL Server. Бодался и бодался, нашел видео, где на стадии установки «дописывались символы» в имена хоста и папки установки. Установка пошла, но, опять на стадии  SQL и Electrical все обвалилось.

Предактивации веду все по инструкциям.

Ладно, крутил вертел. Начала удалял остатки и пути через Revo Uninstaller и CCleaner.  Потом чистил вручную реестр по поиску имен «Solid» (но удалял не все) и «SolidWorks» (тут затирал абсолютно всё).

Не помогло.

Психанул — переустановил Вин7 опять.

Скачал с официального сайта и отдельно, сразу, накатил MS SQL Server 2014. Начал установку SW 2019 sp5 -ниче не вышло. Опять Электрикал и СКЮЭЛ не дружат.

Скачал SW 2020 sp3 — те же яйцы. Скачал SW 2015 sp5 — те же яйцы. Скачал SW 2016 sp3 — те же яйцы.

Благо трафик бесплатный…

Помогите, пожалуйста, что не так? У меня уже глаз дёргается. 

Начал уже думать на компас переходить и его изучение начинать. Но по совокупности плюсов и хотелок, все же, хочется на SW остаться.

Единственно, что только не пробовал, сегодня в сети нашел, не сносил Visual Studio C++ и иже с ними. Но, когда раньше ставил SW 2015 никаких танцев с бубнами не было. И на прошлой работе, тоже сам ставил на ноут солид — тоже без таких танцев с бубном было.

Что разное было, так это точно Вин 7. Сейчас у меня Ультиматум версия стоит Sp1. Тот экземпляр, что раньше стоял и на котором все работало я, успешно, потерял.

Installations are often blocked by firewall ports, incorrect server name, or a default SQL instance that has already been created. So if you’re dealing with SOLIDWORKS Electrical installation errors or connecting to the SQL Express, check that these common errors are not causing problems. 

Firewall Ports

A firewall is an essential barrier to block unwanted communication to your company’s network. It can also cause problems during program installations if the correct firewall ports are not open.

Firewall ports 1433 and 26666 must be open for SOLIDWORKS Electrical to communicate with the SQL and collaborative server. To check if the ports are open, run a telnet test.

Telnet Test:

1. Go to windows features and turn on the Telnet client.
2. Open a command prompt.
3. In the command prompt type. “ telnet <yourservername> <port number>”
4. If a blank screen opens, the port is open. Otherwise, the port is not open and the test will fail.

A Default Instance has already been created.

If installing a new SOLIDWORKS Electrical database, occasionally a database of the same name is already installed, or if a previous installation fails, the default SQL database has already been created. 

There are two possible solutions.

1. Change the name on the default instance from “yourservernameTEW_SQLEXPRESS” to “yourservernameNewNameHere”
2. Try the “Use an Existing SQL Server Database” option and check “Connect using SQL Server Authentication” and use the default username (SA) and password (same as the ‘tew’ user).

Using “localhost” instead of the computer name

When installing SOLIDWORKS Electrical, it is important to use your computer name instead of the default “localhost”. Change from “localhost”, to your computer name in the Collaborative Server and SQL Server names.

If you have any further questions about SOLIDWORKS Electrical, please contact us. 

Editor’s Note: This article was originally published in December 2019 and has been updated for accuracy and comprehensiveness. 

Learn More About SOLIDWORKS Electrical 

SOLIDWORKS Electrical: Establishing ODBC Database Connection with Microsoft SQL

SOLIDWORKS Electrical Intallation

SOLIDWORKS Electrical — Server Install 

Wrapping Attribute Text in SOLIDWORKS Electrical 

SOLIDWORKS Electrical Automation — Propagation

Solidworks microsoft sql server failed to install

microsoft sql server failed to install. instance name ‘tew_sqlexpress’ is already in use. to continue, specify a unique instance name. You can also click here. Best Laptops for Solidworks

SOLIDWORKS Electrical is unable to connect to the SQL Server… Error… Possible reasons for this failure: -Incorrect username or pasword -Incorrect server name -Server is unavailable Please check the SQL server settings under the SOLIDWORKS Electrical options.

You can check the SQL server Express log files (located at %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOG).  If you are receiving an error about the instance name not being unique, you can manually clean off the orphaned instance name by doing the following:

Please open Add/remove programs and uninstall all the SQL server components.

Delete all the files in software installed location path (For ex: C:Program FilesMicrosoft SQL Server – delete this folder).

Then Open “regedit” (Registry Editor) and delete the below mentioned entries.

1. Click on the Start menu, choose Run and type regedit
2. Go to HKEY_LOCAL_MACHINESoftwareMicrosoftMicrosoft SQL Server
3. Remove SQLEXPRESS from the REG_MULTI_SZ value named InstalledInstances
4. Delete the subhive named MSSQL.1
5. Delete the subhive named SQLEXPRESS
6. Go to HKEY_LOCAL_MACHINESoftwareMicrosoftMicrosoft SQL ServerInstance NamesSQL
7. Delete the value named SQLEXPRESS
8. Delete the folder %ProgramFiles%Microsoft SQL ServerMSSQL.1

if you want clean installation you can delete entirely: HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL Server

Once completed please restart the machine and start the installation. it will be successfully install without any issues.

Note – the above steps apply to the instance name that is created when SQL Express is installed as a part of Visual Studio 2005.  The actual instance name on your system may vary if you have had any other beta version of SQL 2005 (such as the developer edition).  Please make sure to adjust the steps accordingly based on what instance name information is in your registry and file system.

Configuring Microsoft SQL Server

You must insure that an instance of the SQL Server database is available for any type of SOLIDWORKS Electrical installation. You can use an existing SQL Server database if it is already installed on the system, or install a new instance as part of the SOLIDWORKS Electrical installation.

When you install a new instance of SQL Server, SOLIDWORKS installation provides a free version of Microsoft SQL Server Express. This version is limited to 1 CPU, 1 GB of memory, and 10 GB of data. The memory and CPU limitations are sufficient to support 5 concurrent users.

If you install SQL Server Express Edition, ensure that the server software and hardware meet the requirements listed http://solidworks.com/System_Requirements.

However, if there are more 6 or more concurrent users on the same server, you should purchase and install a full version of SQL Server, and use the workflow described for installing SOLIDWORKS Electrical with an existing instance of SQL Server.

For information about the SQL Server Express Edition, consult the Microsoft SQL Server documentation.

New Instances of SQL Server

If you install a new instance of SQL Server, you need full administrative rights to the server, and also to any client systems. You must also ensure that clients have read/write privileges for the database, so they can create and modify projects, libraries, symbols and other project data.

When you install a new instance of SQL Server, select a name other than the default.

Existing Instances of SQL Server

You need a user account that has full administrative rights to the SQL Server database to install new SOLIDWORKS Electrical databases or to connect to a SOLIDWORKS Electrical installation on an existing instance of SQL Server.

For SOLIDWORKS Electrical to function properly, you must enable SQL Server for mixed mode authentication. Mixed mode authentication allows the use of either Windows or SQL Server credentials.

To connect to an existing SQL Server database, you can use Windows or SQL Server authentication. Enter a user name and password for a Windows or SQL Server login that has full SQL Server administrative rights.

You cannot use the ‘tew’ user to connect to SQL Server for installation. Contact your SQL Server administrator or system administrator for help to obtain a login with the proper credentials for SQL Server.

Post Installation of SQL Server

After SOLIDWORKS Electrical is installed, the SQL Server instance creates the following databases in SOLIDWORKS Electrical:

• TEW_APP_DATA
• TEW_APP_MACRO
• TEW_APP_PROJECT
• TEW_CATALOG
• TEW_CLASSIFICATION
• TEW_SQLEXPRESS