This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Starting with the 2-25 build, all attempts to run commands on CVS generic filesystems end with following error: cvs [status aborted]: cannot create socket: Unknown socket error: 10106
Hmm, that does not help much to locate the problem. Can you execute successfully the commands from the command line in the first place? If yes, please try to copy the command's execution string from the Runtime tab to the console (on Windows you need to remove the backslashes due to the strange Windows behavior ;-)
command works from command-line. also works with yesterday's build in same userdir. when i copy failed UPDATE command execution string into command line: cmd /X /C "cd /D \"e:\trunk\nball\xml\core\javahelp\org\netbeans\modules\xml\core\docs\.\"&& \"cvs\" -d \":pserver:johnjullion@appsrv.czech:/cvs\" update -P -d -R \"xml-toc.xml\" " remove all backslashes, i get: The system cannot find the path specified.
Couldn't it be related to recent removal of appsrv tunneling to cvs.netbeans.org ? Just guessing ... :-)
But it works from the command line using appsrv. AFAIK appsrv hasn't been shut down yet.
> remove all backslashes, i get: > The system cannot find the path specified. Well, I meant not really *ALL* backslashes, but those that are before quotes ("). Please try this: cmd /X /C "cd /D e:\trunk\nball\xml\core\javahelp\org\netbeans\modules\xml\core\docs&& cvs -d :pserver:johnjullion@appsrv.czech:/cvs update -P -d -R xml-toc.xml"
*** Issue 31488 has been marked as a duplicate of this issue. ***
I can't reproduce it. John ?
*** Issue 31495 has been marked as a duplicate of this issue. ***
just tried it from home, using cvs.netbeans.org, fresh userdir, no firewall. still doesn't work, same error. used the command syntax that martin gave me on the command line and all cvs commands work fine. patrick is having the same problems if you want to go check it out on his machine.
Well, the isuue is serious and reproducable. The vcsgeneric module is one of they key modules. The module is unusable. I suggest P1.
This bugs seem to affect only Windows platform. But it's really critical. All cvs commands ends with: The instruction at "0x006e0065" referenced memory at "0x006e0065". The memory could not be "read".
The external commands are probably totally confused by corrupted set of environemnt variables. Please execute by internal execution the attached test program. Here's a sample of it's output: NAME = 'HOMEPATH', VALUE = '\' 'AME = 'LOGONSERVER', VALUE = '\\SUPERSAMBA 'AME = 'PROCESSOR_ARCHITECTURE', VALUE = 'x86 'AME = 'SystemRoot', VALUE = 'C:\WINNT It seems, that the values are corrupted.
Created attachment 9197 [details] The test program to test system variables.
This is likely a regression of issue #30621.
This bug is probably related to bug #31433 which was just fixed a few minutes ago. Martin can you please verify
31433 fixing seems to resolve the issue for me. Thanks!
verified