Getting the following error message when checking in a file:
The archive server connection socket could not receive data
Has anyone seen this before?
It might be that the archive server is full.
Still have plenty of disk space on archive server...
That is a very generic error. Could be many things.
Is the archive server the same service pack as all the clients?
Yes, service pack on archive server is the same as all clients.
You might need to turn off IPV6 for the network card (server should be enough). See also S-066826.
Hi Richard, I can't find S-066826 in the knowledge base? could you kindly post its contents?
I don't think I can post the entire solution. In short,
1 it could be due to replication, you should check the registry on the servers together with your VAR.
2 It could be IPV6 is enabled for the network card on your server, simply disable it as it is often not used in a local network.
3 It could be antivirus or another security application that is blocking the communication. Disable all and test.
We've been receiving this same message since November, randomly throughout the day. We did what Richard Bremmer suggested (IPV6), and this did not fix our problem. Did any one else find a resolve?
Are there any other protocols/network adapters installed?
try to ping and see if you have in ipv4 adress.
Oh this is a network issue. Our network hiccups and our IT guy shrugs.
Firstly - be sure, that you have a free space on the archive server disk(s) and the system has the rights to write/read from this disks.
We also get this error and figure out what the issue is.
If it takes more than a 1 millisecond (if I recall) to connect to the server it fails.
S. Casale - it's not true!!!
May you mistake it with issue (reported in SPR) with connecting to SNL server (not PDM server) when it takes more than 100 ms than it fails? But it's just fixed!
My number may be wrong.
Andy Ahne and Jack Hodge - let's look for S-071582, there is PDF attached which explains common reasons of this warning. S-071582 should be visible for all of you.
Check the size of your TempDB in SQL Server. I recently had a client with this and it was the transaction log file was full because the tempdb was full. IT reallocated space on their VM and it stopped the error.
Hope this helps,
Believe in The Q!
As many pointed out, this is a pretty generic error message and encompasses a broad range of causes.
If you open the admin tool on the local client, there is a log file that may give more detailed information.
Is this happening for just you or all users? Is this happening all the time or does it appear intermittently? Does it appear to be happening to a certain set of files (type/location/ etc...?)
Understanding the scope of this will go a long way in helping us help you.
Retrieving data ...