Solidworks Simulation Database Not Found

Posted on  by 



  1. Solidworks Simulation Pdf
  2. Solidworks Simulation Results Database Not Found
  3. Using Solidworks Simulation
  4. Solidworks Model Database
  5. Solidworks Database Missing

0x80040235 = SOLIDWORKS Enterprise PDM Database Server is not installed on the database server; please contact your system administrator for assistance EEDMMAPPINGFOUND 0x8004020E = Could not remove the attribute class because it is used by a control in a file data card. SOLIDWORKS Simulation Standard is an intuitive virtual testing environment for static linear, time-based motion, and high-cycle fatigue simulation. It delivers a concurrent engineering approach, helping you know if your product will perform properly and how long it will last—during the design phase. The SOLIDWORKS Materials Web Portal is an external database of materials provided through a partnership with Matereality. The SOLIDWORKS Materials Web Portal is only accessible to SOLIDWORKS subscription services customers who have a license of SOLIDWORKS Simulation Professional, or a license of SOLIDWORKS Simulation Premium.

Moving the SOLIDWORKS PDM vault database server yourself? The first thing to do is to read through this guide thoroughly – preferably, days before the scheduled server move. This guide is not an exhaustive guide covering every possible scenario that can be performed for this task. However, this guide is based on typical server setups found while supporting our customers. Therefore, should you come up with questions after reading this guide, contact us, and let’s clear things up for you before you move any SOLIDWORKS PDM component.

This guide will cover the move of the Microsoft SQL vault database alone to a different server machine that hosts SQL Standard.

Guide use cases

  • Moving the vault database to new server hardware and decommissioning old.
  • Moving vault database to a server with newer Windows OS instead of an OS in-place upgrade.
  • Moving vault database to a server with a newer SQL version instead of an SQL in-place upgrade.
  • Moving the vault database to a new SQL server instance.

Overview

  1. Install SQL Server on a new system
  2. Create a PDM vault database backup
  3. Restore the vault database in new SQL server
  4. Take old vault database offline or delete it
  5. Update SOLIDWORKS PDM Database Server service registry keys
  6. Update SOLIDWORKS PDM Archive Server service registry keys
  7. Update SOLIDWORKS PDM Client registry keys
  8. Update passwords in
    1. SOLIDWORKS PDM Archive Server service
    2. SOLIDWORKS PDM Database Server service
    3. Lists for cards (in Administration tool)

The Works

1. Installing SQL server for SOLIDWORKS PDM vault database

We have created a guide to help step through the process of installing Microsoft SQL Standard that currently ships with the purchase of SOLIDWORKS PDM Professional 2020. This guide can be foundhere.

Also, hereis the process of installing service pack 3 for Microsoft SQL 2014.

Ensure with your IT that all the PDM clients and PDM server components can connect to it. (i.e. open firewall ports, etc.)

2. Create a PDM vault database backup

This vault database backup is to perform the vault database move. Alone, it is not enough for a disaster recovery scenario. Ensure that you have taken proper backup(s)before proceeding.

  1. Open Microsoft SQL Management Studio. Log into your SQL instance that hosts your PDM vault database.
  2. Right-click on your vault database and navigate Task > Backup…
  3. When the backup database window appears, set the following to their respective tabs:
    General
    Backup Type: Full
    Back up to: Disk
    Destination: Set where you will place the SQL Backup. Give it a unique name and provide extension of '.bak'.
    Media Options
    Overwrite Media: 'Overwrite all existing Media Set' radio button with 'Append
    to the existing backup set'
    Reliability: Check the box for 'Verify backup when finished'
  4. Proceed with taking the backup. A notification will indicate of its success.
  5. Repeat process for the ConisioMasterDb.

3. Restore the vault database in new SQL server

  1. Copy the vault database backups from step 2 to the new server. Open SQL management studio and log in to proceed with the restoration.
  2. Right-click on databases > Restore Database…
  3. When the restore database window appears, set the following to their
    respective tabs:
    General
    Device: Select the database backup to restore.
    Files
    Check the box for “relocate all files to folder” if you require the .mdf and .ldf files to be placed in a particular location. Otherwise, leave unchecked.
  4. Proceed with the restore of the backup. A notification will indicate its success.
  5. Repeat process for the ConisioMasterDb

4. Take old vault database offline or delete it

Avoid the potential of messy issues with clients connecting back to the old server. It is highly recommended to either take the old database “off-line” or delete it.

  1. To take the old database offline, right-click the old vault database and navigate: Tasks > Take Off-line. The database will then be denoted with the following if it was successfully taken off-line.
  2. In some cases, you may need to run the query below to end any running process that is preventing the database from being taken off-line. Provide the name of your database in the query 'database name' but keep the single quotes.
    USE master
    GO
    DECLARE @kill varchar(8000) = '
    SELECT @kill=@kill+'kill '+ convert(varchar(5),spid)
    FROM master..sysprocesses
    WHERE dbid=db_id('database name') --your database name goes here
    EXEC (@kill)
  3. If you would like to delete the old database instead of taking it off-line, the process is a lot easier. Simply, right-click the old vault database and select Delete.
    In the Delete Object dialog, you can close existing connections. You may not have to run the query above to kill the connections.

5. Update SOLIDWORKS PDM Database Server service registry keys

From the machine hosting the SOLIDWORKS PDM Database Server service, update the Windows registry key below. You MUST restart the SOLIDWORKS PDM Database Server service for the change to apply.
HKEY_LOCAL_MACHINESOFTWARESolidWorksApplicationsPDMWorks
EnterpriseMailServiceServer

  • Enter the name of the new SQL machine if using a default instance of SQL.
  • Enter the machine and instance name if using a named instance of SQL.
    • For example: MyServerNameInstanceName
  • Leave blank if the SOLIDWORKS PDM Database Server service has been uninstalled from the previous location and installed in the new SQL server machine.

If you are not sure how to update Windows registry keys, stop and contact us.

6. Update SOLIDWORKS PDM Archive Server service registry keys

From the machine hosting the SOLIDWORKS PDM Archive server service, update the Windows registry keys below. Repeat this step for every replicated archive server of this vault. You MUST restart the SOLIDWORKS PDM Archive server service for the change to apply.
HKEY_LOCAL_MACHINESOFTWARESolidWorksApplicationsPDMWorks
EnterpriseArchiveServerVaultsMyVaultNameServer

  • Enter the name of the new SQL machine if using a default instance of SQL.
  • Enter the machine and instance name if using a named instance of SQL.
    • For example: MyServerNameInstanceName

7. Update SOLIDWORKS PDM Client registry keys

From PDM client, update these two Windows registry keys. Repeat this step for every machine of this vault. It is recommended to at least restart the explorer.exe application from the client’s Windows Task Manager. This will ensure that the changes have been applied.

  1. HKEY_LOCAL_MACHINESOFTWARESolidWorksApplicationsPDMWorks
    EnterpriseDatabasesMyVaultNameDbServer
  2. HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeSolidWorksApplicationsPDMWorks
    EnterpriseDatabasesMyVaultNameDbServer
  3. Close any PDM Administration tools and DELETE this key:
    HKEY_CURRENT_USERSoftwareSolidWorksApplicationsPDMWorks EnterpriseConisioAdmin
    • Enter the name of the new SQL machine if using a default instance of SQL.
    • Enter the machine and instance name if using a named instance of SQL
      For example: MyServerNameInstanceName.

8. Update passwords!

This step is typically missed when there has been a different password assigned for the SQL ‘sa’ account. If there is a new password for the SQL account that PDM uses i.e. ‘sa’, ensure to update these locations.

  1. SOLIDWORKS PDM Archive Server service
    In the archive server machine, open the Archie Server Configuration tool. Update the “SQL Login” password in either the default settings or vault-specific properties:
    Repeat this step for every replicated archive server of this vault. You MUST restart the SOLIDWORKS PDM Archive server service for the change to apply.
  2. SOLIDWORKS PDM Database Server service
    In the machine that hosts the SOLIDWORKS PDM Database server service, open the Database Server Configuration tool to update the SQL password. You MUST restart the SOLIDWORKS PDM Database Server service for the change to apply.
  3. Lists for cards
    SOLIDWORKS PDM lets you query the SQL vault database to populate lists that can be used in data cards. If your vault uses Lists for cards that query the vault database, you will need to update information. This change will need to be performed in the PDM Administration tool.
    From this point, you should be able to connect to your newly moved SQL vault database. If you have any issues, send them our way.

Related Articles

When you are not able to connect to the SOLIDWORKS PDM vault or log-in many things could have gone wrong. I have collected a list of common vault connection issues. These are in the general order I check, but do not need to be checked in this order. All settings are the default and should be valid for most setups, but this is not always the case. If you are unsure, feel free to reach out to tech support.

I have added an Appendix of programs I reference in this document and added hyperlinks to help you find those programs.

Check the Logs

The first thing to do is to check the logs. These logs are a great resource when troubleshooting connection issues. They can give you insight into a specific issue to investigate. Sometimes the error message is vague, or not very helpful. In that case, you may go through the solutions below.

Where is the Client Log?

Open the Administration tool and check the Log File. The newest items are at the bottom of the list.

Where is the Archive Server Log?

Open the Administration tool, right-click on the server, and select “Show the Archive Server Log”.

Check the version

SOLIDWORKS PDM needs All of its components to be on the same major version (the same year). If there is a mismatch of versions there can be many unexpected results. Check the version on the client computer, and compare it to the one on the server, and of the vault.

What version of PDM am I using?

Open the Administration tool and select the About SOLIDWORKS PDM Administration. Check the Client version. In the picture below, you can see that I have 2019 installed.

What version is the vault/database?

You can right-click on the vault name and select properties, or you can open Microsoft SQL Server Management Studio. Navigate to Databases - [Vault Name] - Tables, Right-click on dbo. Upgrades and select “Edit Top 200 Rows”.

Before 2019 you will see the year, as you can see, I had 2018 installed for the first two entries. For 2019 it is showing version 27, to convert that to the year you need to subtract 8 27-8=19.

Check the Registry

Occasionally PDM is looking to the wrong location for the server. Sometimes this can happen if you have recently moved your server components. This information is kept in your Registry Keys. To edit your registry, you may need Administrator privileges

What keys do I need to check?

ComputerHKEY_LOCAL_MACHINESOFTWARESolidWorksApplicationsPDMWorks EnterpriseDatabases[Vault_Name]

ComputerHKEY_LOCAL_MACHINESOFTWAREWOW6432NodeSolidWorksApplicationsPDMWorks EnterpriseDatabases[Vault_Name]

If the vault is not found there the vault view might only be available to the current user. In this case, check the following key.

ComputerHKEY_CURRENT_USERSoftwareSolidWorksApplicationsPDMWorks EnterpriseVaults[Vault_Name]

The Key DbServer is the name of the Database Server if you have a default instance of SQL. If you have a named instance of SQL the value for this key needs to be the server name followed by the instance, for example, BHARRIS-LAPSQLEXPRESS the capitalization might be different but is not important.

Solidworks Simulation Pdf

The Key ServerLoc is the name of the Archive Server.

For these keys, it is recommended to use the names of the server, but you may use the IP address if necessary.

Check Communication

Once you have verified you are looking to the correct locations, it is important to make sure you can communicate with those servers.

What connections do I need to test?

For PDM to work properly you need to be able to communicate with: the Archive Server over the port 3030, the Database Server over port 1433 (1434 if you are using a named instance), and the License Manager over ports 25734, and 25735.

How can I test the connections?

There are two tests you need to do, Ping and Telnet. Ping will check if you can see the server. Telnet will open communications over a certain port. To use telnet, you may need to enable it. See Telnet in the appendix.

To Ping, open the command prompt and type in the command ping [Server Name] -l 1500 where you replace [Server Name] with the name of your server. The -l is the lowercase letter “L” this setting adjusts the packet size to 1500 bytes. For example, ping bharris-lap -l 1500.

If it is successful you should have lost zero of the packets. Check the IP address, and make sure it is correct.

To Telnet, open the command manager and type Telnet [Server Name] [Port] for example - Telnet bharris-lap 3030.

If it is successful you will get an all-black window.

Check the Services

Occasionally for one reason or another, the services are stopped. On the server open Services, and check that SolidNetWork License manager, SOLIDWORKS PDM Archive Server, SOLIDWORKS PDM Database Server, and SQL Server are running. Depending on your setup they may be on different servers. It is important that the servers defined have the appropriate services running (i.e., the archive server has the SOLIDWORKS PDM Archive Server service running).

Sometimes settings have been changed and are awaiting the services to be restarted. Feel free to restart the SOLIDWORKS PDM Archive Server, SOLIDWORKS PDM Database Server.

Check the SQL Server configuration

Sometimes the SQL is set up differently to listen on different ports. To check and adjust this, open the SQL Server Configuration Manager and navigate to SQL Server Network Configuration > Protocols for MSSQLSERVER >right-click on TCP/IP > Properties > IP Addresses tab. Here the TCP Dynamic Ports should be empty, and TCP Port should be set to 1433 (1434 if you are using a named instance). If you changed any settings Restart the SOLIDWORKS Archive Server service.

Reset the SA Password

For PDM to work properly it needs to communicate with the SQL Server part of that communication is an authentication proving PDM has permission to view and edit the SQL database. This authentication is usually the SA (System Administrator) and its password. Occasionally during the setup of PDM, this might have been typed wrong, and or the password may have become corrupted or changed. It is advisable to log into the SQL Management studio with the SA password to verify you know the correct password.

I can’t log in as SA

This could be due to either you do not know the correct password, or the account is locked due to too many failed attempts. SeeHow to Reset the SQL ‘sa’ user password.

How do I reset the SA password in PDM?

Open the Archive Server Configuration tool and first check your specific vault to see if it is using the default SQL login. To do this navigate to This Computer > Archives >right click on Vault > Properties > Login tab If the “Use Default SQL login” is not checked select “Change”. If it is checked, you are going to reset the default SQL Login. Click cancel and go to Tools > Default settings > Login tab Select “Change”. Here the SQL user Login should be “sa”.

Appendix


Programs

When writing this I’m making assumptions you know of and can find the following programs.

Solidworks Simulation Results Database Not Found


Administration tool

This is the main program for setting up SOLIDWORKS PDM. It can be found in the SOLIDWORKS PDM folder in the start menu on any computer PDM is installed.

Archive Server Configuration

Using Solidworks Simulation

This is the archive portion of PDM. It can be found in the SOLIDWORKS PDM folder in the start menu on the Archive Server.

Command Prompt

Command Prompt is a command-line interpreter application available in most Windows operating systems. It is most easily found by typing in CMD into the Start search. Or is found in the Windows System Folder of the start menu.

Microsoft SQL Server Management Studio

Microsoft SQL Server Management Studio is used for configuring, managing, and administering all components within Microsoft SQL Server. It is found in one of the Microsoft SQL Server folders in the Start menu of the server hosting SQL.

Regedit

The Windows Registry editor is also known as Regedit. Can be found in the Windows Administrative Tools folder, or by searching “Regedit”. You will need Administrative permissions to make changes here, and it is not a bad idea to ‘Export’ the registry before making any changes.

Services

Windows Services Manager can be found in the Windows Administrative Tools folder in the start menu, or by searching the start menu for services.

SQL Server Configuration Manager

SQL Server Configuration Manager is a tool to manage the services associated with SQL Server, to configure the network protocols used by SQL Server. It is found in one of the Microsoft SQL Server folders in the Start menu of the Server hosting SQL.

Telnet

Telnet is a windows tool most often used to test network communication. It is not enabled by default. To enable Telnet, navigate to Control Panel > Programs > Programs and Features on the left side there will be “Turn Windows Features on or off” check Telnet client.

How do I know if I’m using a named instance of SQL?

On the Server, open Services find SQL Server. You may have multiple services; the default will be (MSSQLSERVER), if there are any others those will be named instances. If you are using PDM Standard by default it will be an instance called (SQLEXPRESS).

To check what instance you are using for PDM, open Microsoft SQL Server Management Studio. When you are logging in there is an option for Server name: here you can choose between the different instances of SQL. When logged in to the correct instance, the vault will in the Databases.

Checklist

Solidworks Model Database

Check the Client Logs:
 Client Log
 Archive Server log

Check the Version:
 Compare the PDM Client version to the Server.
 Compare the Vault/Database version

Solidworks simulation database not found in windows 10

Check the Registry:
ComputerHKEY_LOCAL_MACHINESOFTWARESolidWorksApplicationsPDMWorks EnterpriseDatabases[Vault_Name]

If the vault is not found there the vault view might only be available to the current user.
ComputerHKEY_CURRENT_USERSoftwareSolidWorksApplicationsPDMWorks EnterpriseVaults[Vault_Name]
 DbServer (SQL Server Name or SQL Instance) IE 'BHarris-Lapsqlexpress'
 ServerLoc (Archive Server Name)
 Same in the WOW6432Node
 Delete the Key 'ComputerHKEY_CURRENT_USERSoftwareSolidWorksApplicationsPDMWorks EnterpriseConisioAdmin'

Check Communication:
 Ping the Archive Server
 Verify the IP is correct
 Telnet [Archive Server Name] 3030
 Ping the Database Server
 Verify the IP is Correct
 Telnet [Database Server Name] 1433 - 1434 If named instance of SQL
 Check for ODBC drivers: See - How to perform an ODBC test to verify SQL connectivity.pdf

Solidworks Database Missing

Check if the services are running:
It won’t hurt to restart the services.
 SOLIDWORKS PDM Archive Server
 SOLIDWORKS PDM Database Server
 SQL Server (MSSQLSERVER) - or the instance used
 SolidNetWork License Manager

Check the SQL Server Configuration manager:
Under SQL Server Network Configuration
- Protocols for MSSSQLSERVER (if using the default SQL instance) - TCP/IP - Properties
 TCP Port for all should be 1433 (1434 for named instances)
 TCP Dynamic Ports needs to be empty
 If you changed anything restart the Archive Server service

Reset the SA Password:
 Log in to the SQL Management Studio to verify the SA password
 Reset the SA password in





Coments are closed
Idm 6.23 Crack Free Download Zaltv Code 18