wyattetal Posted January 26, 2016 Report Share Posted January 26, 2016 Frequently (but not always) when I compile in VS2015 (and sometimes just when VS2015 gets focus), I get a dialog that reports: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. Server <our server>:8088. An existing connection was forcibly closed by the remote host. Some details: * The source control plug-in (Tools->Options->Source Control) is set to Plastic SCM. * My plastic configuration does not use port 8088. It uses 8087. It is unclear why the dialog is citing port 8088. * I am running two instances of VS2015, each looking at a solution in a different repo & workspace from the other. * In one of the workspaces/solutions, some (but not all) vcxproj's have the SCC section set to plastic plug-in. * Uninstalling the plastic plug-in eliminates the dialogs. * Uninstalling the plastic SCM plug-in from VS2015 causes VS2015 to modify the SCC sections of the above noted projects to remove the plug-in info. (So as a team we apparently need to all use the plug-in or none of us use it). In general, it is not clear to me if the Plastic SCM plug-in is intended to be: * A VS2015 choice; in which case why note and enforce via the vcxproj file? * A project choice; in which case I do not understand how to specify for all rather than some of a vcxproj's in a repo. Link to comment Share on other sites More sharing options...
manu Posted January 26, 2016 Report Share Posted January 26, 2016 Hi there, are you using the SCC plugin or the Plastic SCM VS Package? The 8088 port is used by default for the SSL connections but if your client is not configured to communicate with the server using it I don't understand why are you getting that message. Link to comment Share on other sites More sharing options...
wyattetal Posted January 27, 2016 Author Report Share Posted January 27, 2016 Plastic SCM Source Control Package Link to comment Share on other sites More sharing options...
manu Posted January 29, 2016 Report Share Posted January 29, 2016 Well, that Plastic SCC plugin is a little bit old and it's missing all the great features the new VS Plastic SCM package has. Is it possible for you to switch to the new VS Package? Link to comment Share on other sites More sharing options...
wyattetal Posted January 29, 2016 Author Report Share Posted January 29, 2016 How do I get the new package to which you refer in post #4? When I run the 5.4.16.721 installer I am offered the following * "Visual Studio integration package (2010 of higher)", which affords me "Plastic SCM Source Control Package" in VS (referred to in Post #3) * "SCC plug-in", which affords me "Plastic SCC Plug-in" in VS (is this the one you recommend using in Post #4? If so, I must say that the installer leads me to believe that this is the older of the two.) Link to comment Share on other sites More sharing options...
manu Posted February 1, 2016 Report Share Posted February 1, 2016 Sorry, my fault. I read it wrong... You are already using the VS Package. Let me try to find more information. Link to comment Share on other sites More sharing options...
wyattetal Posted February 8, 2016 Author Report Share Posted February 8, 2016 I have found that removing the following line <LastUsedRepServer>OUR_SERVER:8088</LastUsedRepServer> from C:\Users\<ME>\AppData\Local\plastic4\guiclient.conf seems to have eliminated the problem. Is that a helpful clue? Link to comment Share on other sites More sharing options...
manu Posted February 8, 2016 Report Share Posted February 8, 2016 Well, yes. At least we can understand from where the "OUR_SERVER:8088" value is taken. Did you perform any operation using the SSL port lately? Link to comment Share on other sites More sharing options...
wyattetal Posted February 8, 2016 Author Report Share Posted February 8, 2016 No. I am configured to use 8087, Link to comment Share on other sites More sharing options...
manu Posted February 10, 2016 Report Share Posted February 10, 2016 Ok, remove that part from the guiclient.conf file and monitor it for some time in order to check if the issue is completely gone. Link to comment Share on other sites More sharing options...
wyattetal Posted February 11, 2016 Author Report Share Posted February 11, 2016 Less frequent warnings, but still occur. Link to comment Share on other sites More sharing options...
manu Posted February 11, 2016 Report Share Posted February 11, 2016 And is the "<LastUsedRepServer>" field having the wrong server specification? Link to comment Share on other sites More sharing options...
wyattetal Posted February 12, 2016 Author Report Share Posted February 12, 2016 I have removed the "<LastUsedRepServer>" field. It has not returned. In order to rule out some sort of interaction between the Plastic Client and the plug-in, I have also tried the case where I reboot, do not launch the stand alone plastic client, and only use the VS plug-in. Warnings still appear, still citing the 8088 port. Link to comment Share on other sites More sharing options...
manu Posted February 15, 2016 Report Share Posted February 15, 2016 Thanks you for the info. Let me try to study it and I'll return back to you once I have more info. Link to comment Share on other sites More sharing options...
manu Posted February 15, 2016 Report Share Posted February 15, 2016 Hi again, can you tell me all the ".conf" files you have at: C:\Users\<Your_user>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\ The plugin gets installed by VSIX under "qc5142wc.02w"-like directories. I'm wondering the configuration files you have there. Link to comment Share on other sites More sharing options...
wyattetal Posted February 15, 2016 Author Report Share Posted February 15, 2016 C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\remoting.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\extensions\config_samples\bugzilla.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\extensions\config_samples\fogbugz.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\extensions\config_samples\jira.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\extensions\config_samples\mantis.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\extensions\config_samples\ontime.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\extensions\config_samples\polarion.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\extensions\config_samples\rally.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\extensions\config_samples\trac.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\extensions\config_samples\versionone.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\theme\windows\default\theme.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\theme\windows\default\colors\colors.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\theme\windows\i3\theme.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\theme\windows\i3\colors\colors.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\theme\windows\montana\theme.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\theme\windows\montana\colors\colors.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\theme\windows\montana-dark\theme.conf C:\Users\<User>\AppData\Local\Microsoft\VisualStudio\14.0\Extensions\nwmw0re3.djd\theme\windows\montana-dark\colors\colors.conf Link to comment Share on other sites More sharing options...
wyattetal Posted February 18, 2016 Author Report Share Posted February 18, 2016 Update: Since our server was upgraded to Plastic SCM 5.4.16.726, the problem has not re-occurred. Link to comment Share on other sites More sharing options...
manu Posted February 19, 2016 Report Share Posted February 19, 2016 Mmmmmm keep an eye on it since, i'm afraid, we didn't fix a thing regarding this. Link to comment Share on other sites More sharing options...
wyattetal Posted February 19, 2016 Author Report Share Posted February 19, 2016 Could it be related to mono3 -> mono4 change? Link to comment Share on other sites More sharing options...
manu Posted February 19, 2016 Report Share Posted February 19, 2016 Nop, I don't see how. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.