I just ran across this in the release notes.Benjamin Lombard wrote:
No I didn't. I didn't notice that information. Do you know how I might be able to fix that problem without having to re-install everything ?
"pdmwDataPortWorker::InitInstance() - CFileException() : An Existing connection was forcibly closed by the remote host. (10054)"
This line is present for every file and reference that PDMW could not open.
The vault is on the same machine that the server and client are on.
This error is actually quite common. A google search on "An existing connection was forcibly closed by the remote host. 10054" brings up 18,000 hits or so.
One of the more meaningful results was, "A 10054 means that the host you are trying to talk to exists, but that the port does not exist or is blocked (i.e. firewalled)." The OP responded, "The issue turns out to be "User Error". My FABRIC_ADMIN_ADDRESS was not set correctly. Once I fixed that all was well." Not just sure what that means yet.
Another site had:
"WSAECONNRESET
10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer
application on the remote host is suddenly stopped, the host is rebooted, the host or remote network
interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the
SO_LINGER option on the remote socket).
This error may also result if a connection was broken due to
keep-alive activity detecting a failure while one or more operations are in progress. Operations that
were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET."
From the MicroSoft WINSOCK2 Documentation:WSAECONNRESET (10054) Connection reset by peer.
A existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close" (see setsockopt(SO_LINGER)) on the remote socket.
I'm not sure... we're running 2008 of PDMWE and SolidWorks right now... but in the documentation I read about upgrading, it said that you have to upgrade PDMWE BEFORE upgrading SolidWorks... so that might cause that error if you didn't go in that order.