Thread: New SC 6.1 Install connection error

Greetings all,
I have been out of ServiceCenter since 4.09. I recently installed SC 6.1 on my local laptop. When I try to connect, I receive the following error message:

Error connecting to server, server not up or wrong connection parameters:
http://localhost:12670/sc61server/ui
Cause: javax.xml.SOAPException: Message send failed - connection reset by server

The server is running. What did I miss?

Thanks,

Mike

Neither the client nor the web will access. I thought so too about a standard install. Still get

Error connecting to server, server not up or wrong connection parameters:
http://localhost:12670/sc61server/ui
Cause: javax.xml.SOAPException: Message send failed - connection reset by server

2884 04/21/2006 16:25:09 connection accepted on socket 392
3248 04/21/2006 16:25:09 xprt_close: closesocket( 228 ),, socket operation on non-socket, errno(10038)
3248 04/21/2006 16:25:09 Process 3248 started on socket 392.
3248 04/21/2006 16:25:09 recvTCP(): socket error, errno=10038
3248 04/21/2006 16:25:09 recvTCP(): Error receiving data over TCP connection, socket operation on non-socket, errno(10038)
3248 04/21/2006 16:25:09 TCP connection failed - new user process or thread will terminate
3248 04/21/2006 16:25:09 expressterm returned 1
3248 04/21/2006 16:25:09 Process termination in progress
3248 04/21/2006 16:25:09 xprt_close: closesocket( 392 ),, socket operation on non-socket, errno(10038)
2884 04/21/2006 16:25:09 connection accepted on socket 384
4052 04/21/2006 16:25:09 xprt_close: closesocket( 228 ),, socket operation on non-socket, errno(10038)
4052 04/21/2006 16:25:09 Process 4052 started on socket 384.
4052 04/21/2006 16:25:09 recvTCP(): socket error, errno=10038
4052 04/21/2006 16:25:09 recvTCP(): Error receiving data over TCP connection, socket operation on non-socket, errno(10038)
4052 04/21/2006 16:25:09 TCP connection failed - new user process or thread will terminate
4052 04/21/2006 16:25:09 expressterm returned 1
4052 04/21/2006 16:25:09 Process termination in progress
4052 04/21/2006 16:25:09 xprt_close: closesocket( 384 ),, socket operation on non-socket, errno(10038)

I tried checking/unchecking the advanced options but with the same result.

When you install the SC client...did you reboot your desktop before trying to connect to the server? I believe the client hasn't finish its install until you reboot. I would uninstall the sc client, reboot your desktop, install the client again, reboot your desktop...then try connecting to the server.

I've seen this error on occasion.

1. Check your sc.ini file to make sure you're pointing to an existing database folder with appropriate scdb loaded
2. What OS are you using and do you have other servers that might conflict with SC? ie. do you have VMWare or Citrix installed on your laptop as well?

I just performed a fresh 6.1 install on my new laptop, and ran into the same problem. On my old laptop the same software installed and ran without a hitch.

I'm still trying to locate the cause of the problem, but so far I can tell you this:

- The problem is definitively with the server, not with the client. If you try connecting with the server using telnet localhost 12670, you get the same error messages in sc.log.

- This happens with a completely fresh install, identical to the install I performed on my other laptop without seeing the problem.

- It happens with both SC 6.1.1 and SC 6.1.2 server.

- Error code 10038 is an odd one, it means that the code is attempting to perform a socket operation (for instance setting socket options) on a file handle that is not connected to a socket.

- As far as I can tell, this is what is happening: The scenter listener listens on port 12670, detects an incoming connection and creates a new process to handle the new session. The new process is handed a file handle that is supposed to be the network socket. It tries to perform a socket operation on the file handle, and fails. It logs the error to sc.log, and exits. The short lifetime of the process makes it hard to trace it and see what it really is doing.

If anybody has any further knowledge of what might be going on, I'd love to hear it. If not, I'll post back here if I am able to find a workaround.

Hi - just had the same problem and this fix worked great.

Thanx for the great post fid509...!!

Cheers