- #THE ARCHIVE SERVER CONNECTION SOCKET COULD NOT SEND DATA FULL#
- #THE ARCHIVE SERVER CONNECTION SOCKET COULD NOT SEND DATA WINDOWS#
If the Telnet test returns unsuccessful while the ping tests are successful, this means that the ports are blocked. 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. To use Telnet to test a port, open Command Prompt again, this time you want to type – telnet.
#THE ARCHIVE SERVER CONNECTION SOCKET COULD NOT SEND DATA WINDOWS#
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. 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. More details about ports are in the next step. 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. If not, you will need some support from your IT to fix the network connection issue. Check the network connection and make sure that both machines are on the same Domain Network. If this is the case, then Client machine is not communicating to the Server Machine. 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. 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. Ping test successful for either of the two but unsuccessful for another
![the archive server connection socket could not send data the archive server connection socket could not send data](https://www.web3us.com/sites/default/files/inline-images/Download%20connector%20J.png)
Once open, you’ll need to type “ping SERVERNAME” and press enter, where you put in your Server Name or Server IP Address. To access ping test, click Windows Start and type “Command Prompt”, you should right click and open as Administrator. The ping test is a simple DOS command that tests network connectivity, it does not test ports. First ping the server machine by server-name and then use the Server IP address to test. Perform a “Ping” test to the server machine from your client machine. Check if the client machine can communicate with SQL Server Machine You may need Windows Admin log in for your VAR to be able to access and check registries. 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. Consult your IT Team to check if the information about the server is correct. Open PDM Administration tool, right click on the vault and click properties. 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. Check if the SQL Server Name and Database shown in the log description are correct. Below are some basic troubleshooting steps that can be performed on PDM client-side to establish connection with SQL Server. There are several reasons why this error message can occur.
![the archive server connection socket could not send data the archive server connection socket could not send data](https://static.filehorse.com/screenshots/file-transfer-and-networking/serial-to-ethernet-connector-screenshot-02.png)
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. 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. 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.Īs PDM is a client server setup, the error could be from your client or from the server.
![the archive server connection socket could not send data the archive server connection socket could not send data](https://images.saymedia-content.com/.image/c_limit%2Ccs_srgb%2Cq_auto:good%2Cw_700/MTc1MDE0MzQyNDQ1MTE1MTEy/how-to-configure-exchange-after-installation.png)
#THE ARCHIVE SERVER CONNECTION SOCKET COULD NOT SEND DATA FULL#
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. 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. These messages only tell us what the error is, not what caused it. Have you experienced this before? Here are our top 8 troubleshooting steps to resolve these issues.įirstly, about the error – we need to get as much information about the cause of the error. The most common and generic error when working with PDM is “Cannot access the item in the database” or “Could not find the Server”. Don’t worry, most issues are usually IT related, which can easily be resolved by following these troubleshooting steps.
![the archive server connection socket could not send data the archive server connection socket could not send data](http://people.ece.cornell.edu/land/courses/ece4760/FinalProjects/s2010/jkd27_dm472/MyPage/images/photos/wifi_setup.jpg)
However, when it doesn’t work it can become very frustrating. Using SolidWorks PDM is a great tool to control your revisions and versions, manage your files, etc.