 |
SoftTree Technologies
Technical Support Forums
|
|
| Author |
Message |
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
 |
 |
All the config options you enter on the logon screen. There is nothing else.
Have you tried connecting to the scheduler using telnet with port 1096 as suggested in the previous responses?
Telnet utility of course is not going to connect but it will let you know if it can reach the scheduler using TCP/IP protocol.
|
|
| Thu May 31, 2007 11:51 pm |
  |
 |
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
Ok, I've tried telnet both locally from the server and from my workstation to port 1096. In both cases I get a blank telnet screen when it 'connects', with just a cursor showing, no context information and anything I type does not show up.
|
|
| Mon Jun 04, 2007 5:17 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
| |
|
That's fine. The purpose of trying Telnet was to ensure you can "ping" to the server on port 1096. For your Telnet connections do you see anything turning up in the master.log file on the server?
|
|
| Mon Jun 04, 2007 5:28 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
Here it is, there is no time and date so not sure which entries are relevant
SMI10 Listener (05101FD0): Start Listening: computerName(), serviceName(1096), driverName(WinSock). ... (00000000)
SMI Property: __DriverName='WinSock'
SMI Property: __ApplicationName='1096'
SMI Property: __Options='MaxListeningThreads=9'
SMI Property: MaxListeningThreads='9'
SMI AddRef SMI_TRACE(05101A70) refCount(2)
WSD11 AddRef: RefCount for listener object = 1
WSD11 AddRef: RefCount for listener object = 2
WSD11 AddRef: RefCount for listener object = 3
WSD11 AddRef: RefCount for listener object = 5
WSD11 AddRef: RefCount for listener object = 4
SMI10 Listener (05101FD0): Start Listening: computerName(), serviceName(1096), driverName(WinSock). SUCCEEDED (00000000)
WSD11 AddRef: RefCount for listener object = 6
WSD11 AddRef: RefCount for listener object = 7
WSD11 AddRef: RefCount for listener object = 8
WSD11 AddRef: RefCount for listener object = 9
WSD11 AddRef: RefCount for listener object = 10
DPB30 Listener (009FE848): Start Listening : application(1096), location(), driver(WinSock). FAILED (80004005)
DPB55 Memory Session : (00000000) count(3786), total(618496), alloc(402351), free(198750)
DPB56 Memory Proc Common : count(1286), total(151552), alloc(71281), free(74688)
SMI AddRef SMI_LISTENER(05101FD0) refCount(2)
SMI AddRef SMI_TRACE(05101A70) refCount(3)
WSD04 AddRef: RefCount for connection object = 1
SMI AddRef SMI_TRACE(05101A70) refCount(4)
SMI AddRef SMI_TRACE(05101A70) refCount(5)
SMI AddRef SMI_LISTENER(05101FD0) refCount(3)
SMI Release SMI_LISTENER(05101FD0) refCount(2)
SMI AddRef SMI_CONNECTION(05101DC8) refCount(3)
SMI Release SMI_CONNECTION(05101DC8) refCount(2)
SMI12 Listener (05101FD0): Open Connection: (05101DC8). numConnections(1), SUCCEEDED (00000000)
WSD04 AddRef: RefCount for connection object = 2
SMI AddRef SMI_LISTENER(05101FD0) refCount(3)
SMI AddRef SMI_TRACE(05101A70) refCount(6)
WSD04 AddRef: RefCount for connection object = 1
SMI AddRef SMI_TRACE(05101A70) refCount(7)
SMI AddRef SMI_TRACE(05101A70) refCount(8)
SMI AddRef SMI_LISTENER(05101FD0) refCount(4)
SMI Release SMI_LISTENER(05101FD0) refCount(3)
SMI AddRef SMI_CONNECTION(051061B8) refCount(3)
SMI Release SMI_CONNECTION(051061B8) refCount(2)
SMI12 Listener (05101FD0): Open Connection: (051061B8). numConnections(2), SUCCEEDED (00000000)
WSD04 AddRef: RefCount for connection object = 2
SMI02 Connection(05101DC8): ERROR OCCURRED: Distributed Communications Error: Recv call failed with the error , (3DE) (8004200D)
SMI02 Connection(05101DC8): ERROR OCCURRED: Distributed Communications Error: Winsock driver internal error, (298) (8004200D)
WSD04 Release: RefCount for connection object = 2
SMI02 Connection(051061B8): ERROR OCCURRED: Distributed Communications Error: Recv call failed with the error EOF, (3A0) (8004200D)
DPB42 SessionId (051062B0): Being Disconnected :
SMI08 Connection(051061B8): Disconnect: ... (00000000)
WSD04 Release: RefCount for connection object = 2
SMI08 Connection(051061B8): Disconnect: SUCCEEDED (00000000)
WSD04 Release: RefCount for connection object = 1
SMI Release SMI_CONNECTION(051061B8) refCount(1)
SMI Release SMI_TRACE(05101A70) refCount(7)
|
|
| Mon Jun 04, 2007 5:32 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
| |
|
Do you see anything like this when you attempt to connect from the web console? If yes, can you post the trace for a web console connection?
|
|
| Mon Jun 04, 2007 7:30 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
Here's an interesting behaviour;
24x7 is running as a process currently as I am finding it much easier to develop in that mode (although when I installed the web console and first found the invalid server reply problem it was in service mode)
When i press login on the web console page, it actually seems to kill the scheduler. The GUI minimises to tray, and then disappears entirely and task manager does not show 24x7.exe as running. I can start it up again fine.
it happens when I try the web console locally or from my workstation.
|
|
| Mon Jun 04, 2007 7:41 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
| |
|
Please post your master.log file after this happens again.
|
|
| Mon Jun 04, 2007 7:54 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
Just happened and here it is
SMI10 Listener (05101FD0): Start Listening: computerName(), serviceName(1096), driverName(WinSock). ... (00000000)
SMI Property: __DriverName='WinSock'
SMI Property: __ApplicationName='1096'
SMI Property: __Options='MaxListeningThreads=9'
SMI Property: MaxListeningThreads='9'
SMI AddRef SMI_TRACE(05101A70) refCount(2)
WSD11 AddRef: RefCount for listener object = 1
WSD11 AddRef: RefCount for listener object = 2
WSD11 AddRef: RefCount for listener object = 3
WSD11 AddRef: RefCount for listener object = 4
WSD11 AddRef: RefCount for listener object = 5
WSD11 AddRef: RefCount for listener object = 6
WSD11 AddRef: RefCount for listener object = 7
WSD11 AddRef: RefCount for listener object = 8
WSD11 AddRef: RefCount for listener object = 9
WSD11 AddRef: RefCount for listener object = 10
SMI10 Listener (05101FD0): Start Listening: computerName(), serviceName(1096), driverName(WinSock). SUCCEEDED (00000000)
DPB30 Listener (009FE848): Start Listening : application(1096), location(), driver(WinSock). FAILED (80004005)
DPB55 Memory Session : (00000000) count(3786), total(618496), alloc(402351), free(198750)
DPB56 Memory Proc Common : count(1286), total(151552), alloc(71281), free(74688)
SMI AddRef SMI_LISTENER(05101FD0) refCount(2)
SMI AddRef SMI_TRACE(05101A70) refCount(3)
WSD04 AddRef: RefCount for connection object = 1
SMI AddRef SMI_TRACE(05101A70) refCount(4)
SMI AddRef SMI_TRACE(05101A70) refCount(5)
SMI AddRef SMI_LISTENER(05101FD0) refCount(3)
SMI Release SMI_LISTENER(05101FD0) refCount(2)
SMI AddRef SMI_CONNECTION(05101DC8) refCount(3)
SMI Release SMI_CONNECTION(05101DC8) refCount(2)
SMI12 Listener (05101FD0): Open Connection: (05101DC8). numConnections(1), SUCCEEDED (00000000)
WSD04 AddRef: RefCount for connection object = 2
WSD07 ReadHeader: Proto = 24576, Len = 157
SMI01 Connection(05101DC8): Create Message: (05101A10), initial size 157 bytes
DPB AddRef DPB_SESSION_SERVICE(051090C8) refCount(2)
DPB40 SessionId (00000000): Handle Request: CREATE_SESSION(1), streamVer(0). SUCCEEDED (00000000)
DPB20 Connection(05101DC8): ClientConnect : IUSR_KBDVFDSINT01(KBDVFDSINT01) userId(ldowse01), connectString(), sessionId(FFFFFFFF). ... (00000000)
SMI AddRef SMI_LISTENER(05101FD0) refCount(3)
SMI16 Listener (05101FD0): Create Session: (05109120). SUCCEEDED (00000000)
DPB41 : Use Session : sessionId(84971808). SUCCEEDED (00000000)
SMI Release SMI_LISTENER(05101FD0) refCount(2)
SMI AddRef SMI_CONNECTION(05101DC8) refCount(3)
DPB AddRef DPB_Connection(051086E0) refCount(1)
DPB AddRef DPB_SESSION_SERVICE(051090C8) refCount(3)
DPB20 Connection(05101DC8): ClientConnect : IUSR_KBDVFDSINT01(KBDVFDSINT01) userId(ldowse01), connectString(), sessionId(05109120). SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(051090C8) refCount(2)
SMI06 Connection(05101DC8): Process request Message: (05101A10) serviceId(0), sequenceNumber(0). SUCCEEDED (00000000)
SMI01 Connection(05101DC8): Create Message: (05109330), initial size 0 bytes
SMI03 Connection(05101DC8): Send Reply Message: (05109330) sequenceNumber(837) Asynchronous. ... (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 97
WSD08 Send: result = 0
SMI01 Connection(05101DC8): Create Message: (05109370), initial size 97 bytes
SMI03 Connection(05101DC8): Send Reply Message: (05109330) sequenceNumber(837) Asynchronous. SUCCEEDED (00000000)
DPB AddRef DPB_SESSION_SERVICE(051090C8) refCount(3)
SMI08 Connection(05101DC8): Disconnect: ... (00000000)
DPB40 SessionId (05109120): Handle Request: CREATE_INSTANCE(3), streamVer(0). SUCCEEDED (00000000)
WSD09 SendDisconnect: result = 0
WSD04 Release: RefCount for connection object = 2
SMI08 Connection(05101DC8): Disconnect: SUCCEEDED (00000000)
DPB AddRef DPB_SESSION_SERVICE(051090C8) refCount(4)
DPB Release DPB_SESSION_SERVICE(051090C8) refCount(3)
DPB Release DPB_SESSION_SERVICE(051090C8) refCount(2)
SMI Release SMI_CONNECTION(05101DC8) refCount(2)
SMI06 Connection(05101DC8): Process request Message: (05109370) serviceId(0), sequenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 112
SMI01 Connection(05101DC8): Create Message: (05101A10), initial size 112 bytes
DPB56 Memory Proc Common : count(1388), total(167936), alloc(86773), free(75192)
SMI06 Connection(05101DC8): Process request Message: (05101A10) serviceId(0), sequenceNumber(0). SUCCEEDED (00000000)
DPB Release DPB_SESSION_SERVICE(051090C8) refCount(1)
DPB Release DPB_SESSION_SERVICE(051090C8) refCount(0)
DPB Release DPB_Connection(051086E0) refCount(0)
SMI Release SMI_CONNECTION(05101DC8) refCount(1)
SMI Release SMI_TRACE(05101A70) refCount(4)
WSD07 ReadHeader: Proto = 24576, Len = 112
SMI01 Connection(05101DC8): Create Message: (05101F20), initial size 112 bytes
SMI06 Connection(05101DC8): Process request Message: (05101F20) serviceId(0), sequenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 87
SMI01 Connection(05101DC8): Create Message: (05101F20), initial size 87 bytes
SMI06 Connection(05101DC8): Process request Message: (05101F20) serviceId(0), sequenceNumber(0). SUCCEEDED (00000000)
WSD07 ReadHeader: Proto = 24576, Len = 83
SMI01 Connection(05101DC8): Create Message: (05109370), initial size 83 bytes
SMI06 Connection(05101DC8): Process request Message: (05109370) serviceId(0), sequenceNumber(0). SUCCEEDED (00000000)
SMI02 Connection(05101DC8): ERROR OCCURRED: Distributed Communications Error: (8004200D)
SMI08 Connection(05101DC8): Disconnect: ... (00000000)
SMI08 Connection(05101DC8): Disconnect: SUCCEEDED (00000000)
WSD04 Release: RefCount for connection object = 1
SMI Release SMI_CONNECTION(05101DC8) refCount(0)
SMI Release SMI_TRACE(05101A70) refCount(3)
SMI Release SMI_LISTENER(05101FD0) refCount(1)
SMI Release SMI_TRACE(05101A70) refCount(2)
SMI AddRef SMI_LISTENER(05101FD0) refCount(2)
SMI AddRef SMI_TRACE(05101A70) refCount(3)
WSD04 AddRef: RefCount for connection object = 1
SMI AddRef SMI_TRACE(05101A70) refCount(4)
SMI AddRef SMI_TRACE(05101A70) refCount(5)
SMI AddRef SMI_LISTENER(05101FD0) refCount(3)
SMI Release SMI_LISTENER(05101FD0) refCount(2)
SMI AddRef SMI_CONNECTION(05101DC8) refCount(3)
SMI Release SMI_CONNECTION(05101DC8) refCount(2)
SMI12 Listener (05101FD0): Open Connection: (05101DC8). numConnections(2), SUCCEEDED (00000000)
WSD04 AddRef: RefCount for connection object = 2
WSD07 ReadHeader: Proto = 24576, Len = 164
SMI01 Connection(05101DC8): Create Message: (05101F20), initial size 164 bytes
DPB AddRef DPB_SESSION_SERVICE(051090C8) refCount(2)
DPB40 SessionId (00000000): Handle Request: CREATE_SESSION(1), streamVer(0). SUCCEEDED (00000000)
DPB20 Connection(05101DC8): ClientConnect : IUSR_KBDVFDSINT01(KBDVFDSINT01) userId(kbdevl\ldowse05), connectString(), sessionId(FFFFFFFF). ... (00000000)
SMI AddRef SMI_LISTENER(05101FD0) refCount(3)
SMI16 Listener (05101FD0): Create Session: (05109120). SUCCEEDED (00000000)
DPB41 : Use Session : sessionId(84971808). SUCCEEDED (00000000)
SMI Release SMI_LISTENER(05101FD0) refCount(2)
SMI AddRef SMI_CONNECTION(05101DC8) refCount(3)
DPB AddRef DPB_Connection(05109270) refCount(1)
DPB AddRef DPB_SESSION_SERVICE(051090C8) refCount(3)
DPB20 Connection(05101DC8): ClientConnect : IUSR_KBDVFDSINT01(KBDVFDSINT01) userId(kbdevl\ldowse05), connectString(), sessionId(05109120). SUCCEEDED (00000000)
SMI01 Connection(05101DC8): Create Message: (05101A10), initial size 0 bytes
DPB Release DPB_SESSION_SERVICE(051090C8) refCount(2)
SMI03 Connection(05101DC8): Send Reply Message: (05101A10) sequenceNumber(4692) Asynchronous. ... (00000000)
SMI06 Connection(05101DC8): Process request Message: (05101F20) serviceId(0), sequenceNumber(0). SUCCEEDED (00000000)
WSD08 Send: result = 0
WSD07 ReadHeader: Proto = 24576, Len = 97
SMI03 Connection(05101DC8): Send Reply Message: (05101A10) sequenceNumber(4692) Asynchronous. SUCCEEDED (00000000)
SMI01 Connection(05101DC8): Create Message: (05109330), initial size 97 bytes
SMI08 Connection(05101DC8): Disconnect: ... (00000000)
WSD09 SendDisconnect: result = 0
WSD04 Release: RefCount for connection object = 2
SMI08 Connection(05101DC8): Disconnect: SUCCEEDED (00000000)
DPB AddRef DPB_SESSION_SERVICE(051090C8) refCount(3)
DPB Release DPB_SESSION_SERVICE(051090C8) refCount(2)
DPB40 SessionId (05109120): Handle Request: CREATE_INSTANCE(3), streamVer(0). SUCCEEDED (00000000)
SMI Release SMI_CONNECTION(05101DC8) refCount(2)
DPB AddRef DPB_SESSION_SERVICE(051090C8) refCount(3)
DPB56 Memory Proc Common : count(1390), total(167936), alloc(86835), free(75123)
DPB Release DPB_SESSION_SERVICE(051090C8) refCount(2)
|
|
| Mon Jun 04, 2007 8:27 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
| |
|
Something seems to be missing in the communication stream, but I don't yet understand what. I'm going to compare your output against mine using a similar configuration
|
|
| Mon Jun 04, 2007 8:48 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
This is an interesting line
DPB30 Listener (009FE848): Start Listening : application(1096), location(), driver(WinSock). FAILED (80004005)
|
|
| Mon Jun 04, 2007 9:09 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
| |
|
I believe this line is ok. Not sure why it says FAILED in that line but I've seen this many times without impact on any processing. I'm more concerned about ERROR # 8004200D and some out of sequences messages between the console and the scheduler. Are you sure there are no related errors reported in the schedule.log file?
|
|
| Mon Jun 04, 2007 9:14 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
There are some not authorised messages I have noticed for the first time in there, is there any additional configuration required within the scheduler for user accounts beyond setting them up in job database users and permissions?
Below is the stuff in question for the schedule.log, you're seeing the results of the scheduler dropping and me starting it up again.
5/06/2007 11:32:09 0 0 0 24x7 Scheduler 24x7 Scheduler starting...
5/06/2007 11:32:30 1 0 0 24x7 Scheduler Client ldowse01 not authorized. Connection denied.
5/06/2007 11:34:15 0 0 0 24x7 Scheduler 24x7 Scheduler starting...
5/06/2007 11:35:03 1 0 0 24x7 Scheduler Client ldowse01 not authorized. Connection denied.
5/06/2007 11:36:46 0 0 0 24x7 Scheduler 24x7 Scheduler starting...
5/06/2007 11:38:02 1 0 0 24x7 Scheduler Client ldowse01 not authorized. Connection denied.
5/06/2007 12:14:53 0 0 0 24x7 Scheduler 24x7 Scheduler starting...
5/06/2007 12:16:29 1 0 0 24x7 Scheduler Client ldowse01 not authorized. Connection denied.
5/06/2007 12:24:29 1 0 0 24x7 Scheduler Client kbdevl\ldowse05 not authorized. Connection denied.
5/06/2007 13:06:45 0 0 0 24x7 Scheduler 24x7 Scheduler starting...
|
|
| Mon Jun 04, 2007 10:49 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
| |
|
This means that you have security enabled in the scheduler yet user "ldowse01" is not entered into the scheduler settings or not part of a group that is allowed to connect to it. Either add this user or disable the security.
|
|
| Mon Jun 04, 2007 11:07 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
ldowse01 is a member of "Administrators" within 24x7. So is kbdevl\ldowse05.
|
|
| Mon Jun 04, 2007 11:08 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
I've just added another user to 24x7, tested and same behaviour. Do the accounts need to be local os accounts or mentioned in IIS or something like that?
|
|
| Mon Jun 04, 2007 11:11 pm |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
