Plasma
-
Posts
2 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Plasma
-
-
As the release notes state here (https://www.plasticscm.com/download/releasenotes/8.0.16.3841) to increase the default timeout to add the key "SocketConnectTimeoutMillisec" to client.conf.
I'm using Plastic SCM Cloud. I get this message when trying to look into sync view and under "Preferences" in the "Connection Profiles" page to check server the connection. I don't have this error during any push/pull. I only got this error recently and never had this problem.
In the release notes it shows how to modify the remote.conf, but not the client.conf as there is a different XML structure.
Adding <SocketConnectTimeoutMillisec>10000</SocketConnectTimeoutMillisec> to the client.conf has no effect, and copying the channel along with the children keys has no effect.
Remote.conf example:
<channels>
<channel type="Codice.Channels.PlasticTcpChannel, plastictcpchannel" name="normal" timeoutMilliseconds="10000">
<clientProviders>
<provider type="Codice.Channels.ClientSinkProvider, plastictcpchannel" />
<formatter ref="binary" />
</clientProviders>
</channel></channels>
I tried to look in Plastic SCM documentation for any sort of reference, but unfortunately could not find anything or perhaps I may have overlooked something under the documentation.
SocketConnectTimeoutMillisec Comes Up
in Configuration
Posted
I finally resolved the issue I was having.
I checked literally everything. Firewall, ports, possibly antivirus, possibly a service causing the issue (had those before). Found nothing.
After I did a fresh install of Plastic SCM on a VM, I found out that in my preferences there was no connection profile.
I can't remember adding a connection profile, as I've only created a repo, check-ins, and sync views, but probably did on a drunken night.
Upon deleting the connection profile, I have no problems connecting to my cloud repos now.
If anyone is having this particular issue and how to find the connection profile: Preferences > Connection Profiles.
I appreciate you replying to my post, Carlos, but in the end it was my connection profile which most likely wasn't added correctly.