- #The archive server connection socket could not send data archive#
- #The archive server connection socket could not send data license#
- #The archive server connection socket could not send data free#
Sometimes settings have been changed and are awaiting the services to be restarted.
#The archive server connection socket could not send data archive#
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). Depending on your setup they may be on different servers.
#The archive server connection socket could not send data license#
On the server open Services, and check that SolidNetWork License manager, SOLIDWORKS PDM Archive Server, SOLIDWORKS PDM Database Server, and SQL Server are running. Occasionally for one reason or another, the services are stopped. If it is successful you will get an all-black window. To Telnet, open the command manager and type Telnet for example - Telnet bharris-lap 3030. Check the IP address, and make sure it is correct. If it is successful you should have lost zero of the packets.
![the archive server connection socket could not send data the archive server connection socket could not send data](http://www.servolutions.com/images/exchange2007_new_send_connector_4.png)
The -l is the lowercase letter “L” this setting adjusts the packet size to 1500 bytes. To Ping, open the command prompt and type in the command ping -l 1500 where you replace with the name of your server. To use telnet, you may need to enable it. Telnet will open communications over a certain port. Ping will check if you can see the server. There are two tests you need to do, Ping and Telnet. Once you have verified you are looking to the correct locations, it is important to make sure you can communicate with those servers.įor 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. The Key ServerLoc is the name of the Archive Server.įor these keys, it is recommended to use the names of the server, but you may use the IP address if necessary. 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-LAP\SQLEXPRESS the capitalization might be different but is not important. The Key DbServer is the name of the Database Server if you have a default instance of SQL. In this case, check the following key.Ĭomputer\HKEY_CURRENT_USER\Software\SolidWorks\Applications\PDMWorks Enterprise\Vaults\ If the vault is not found there the vault view might only be available to the current user. To edit your registry, you may need Administrator privilegesĬomputer\HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\Databases\Ĭomputer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SolidWorks\Applications\PDMWorks Enterprise\Databases\ This information is kept in your Registry Keys. Sometimes this can happen if you have recently moved your server components. Occasionally PDM is looking to the wrong location for the server. For 2019 it is showing version 27, to convert that to the year you need to subtract 8 27-8=19. Upgrades and select “Edit Top 200 Rows”.īefore 2019 you will see the year, as you can see, I had 2018 installed for the first two entries.
![the archive server connection socket could not send data the archive server connection socket could not send data](https://venturebeat.com/wp-content/uploads/2018/11/IMG_20181119_132525.jpg)
Navigate to Databases - Tables, Right-click on dbo. You can right-click on the vault name and select properties, or you can open Microsoft SQL Server Management Studio. In the picture below, you can see that I have 2019 installed. Open the Administration tool and select the About SOLIDWORKS PDM Administration. Check the version on the client computer, and compare it to the one on the server, and of the vault. If there is a mismatch of versions there can be many unexpected results.
![the archive server connection socket could not send data the archive server connection socket could not send data](https://i.stack.imgur.com/Tkvan.png)
SOLIDWORKS PDM needs All of its components to be on the same major version (the same year). Open the Administration tool, right-click on the server, and select “Show the Archive Server Log”. The newest items are at the bottom of the list. Open the Administration tool and check the Log File. In that case, you may go through the solutions below. Sometimes the error message is vague, or not very helpful.
![the archive server connection socket could not send data the archive server connection socket could not send data](https://1.bp.blogspot.com/-vyManlIjGHI/Ut4LWIOu5JI/AAAAAAAAAIg/mZPsbjW0UUI/s1600/4.png)
They can give you insight into a specific issue to investigate. These logs are a great resource when troubleshooting connection issues. The first thing to do is to check the logs. I have added an Appendix of programs I reference in this document and added hyperlinks to help you find those programs.
#The archive server connection socket could not send data free#
If you are unsure, feel free to reach out to tech support. All settings are the default and should be valid for most setups, but this is not always the case. These are in the general order I check, but do not need to be checked in this order. I have collected a list of common vault connection issues. When you are not able to connect to the SOLIDWORKS PDM vault or log-in many things could have gone wrong.