WSAECONNRESET ERROR in VistA + Ensemble

[Suchit]

I am using Ensemble (3.1.0.2615.0) to setup VistA on a Windows 2003
Server machine. I have followed the insturctions for installation and
I have also done a lot of trouble shooting but I am unable to get past
the WSAECONNRESET ERROR when trying to connect via the RPC Broker and
CPRS 26 from the local machine.
I have tried the following:
1) Shutoff all firewalls
2) Changed the Registry keys to include the correct server and port
3) Changed Host file to include valid information
The installation instructions I have been following are at:
http://www.hardhats.org/projects/VistA_Install/Vista_Install.html

Please help me troubleshoot this.
Thank you.

Best Regards,
Suchit Ahuja

[Edward J. Koll]

First 2 thoughts that come to mind....

1. Is Taskman started?
2. Is the RPC Broker listener started on the port you are wanting to use?

[Suchit]

Yes they are both started. Using port 9210.

Cache System Status: 8:59 pm 10 Jan 2007

Process Devices KB Namespace Routine CPU,Glob Pri UIC
Location
3736 %SYS 0,0 7 0,0
CONTROL
456 %SYS 1516,57927 8 0,0
WRTDMN
2240 %SYS 0,0 7 0,0
GARCOL
3032 %SYS 42279,1815 7 0,0
JRNDMN
2300 %SYS 17,0 7 0,0
EXPDMN
2880 //./nul 131 %SYS TASKMGR 776384,149161 7 0,0
3384* |TRM|:|3384 115 VISTA %SS 1066,29 7 0,0
736 |TCP|1972 93 %SYS %cmtP 248,42 7 0,0
2896 //./nul 90 %SYS %ooCSP.Daemon.1 67151,8412 7
0,0
2928 |TCP|9210 124 VISTA XWBTCPL 8120,1033 7 0,0

3 user, 7 system, 16 mb global/8 mb routine cache

Checking Task Manager's Environment.

Checking Taskman's globals...
^%ZTSCH is defined!
^%ZTSK is defined!
^%ZTSK(-1) is defined!
^%ZIS(14.5,0) is defined!
^%ZIS(14.6,0) is defined!
^%ZIS(14.7,0) is defined!

Checking the ^%ZOSF nodes required by Taskman...
All ^%ZOSF nodes required by Taskman are defined!

Checking the links to the required volume sets...
There are no volume sets whose links are required!

Checks completed...Taskman's environment is okay!

Checking Taskman. Current $H=60640,75824 (Jan 10, 2007@21:03:44)
RUN NODE=VISTA:ENSEMBLE is the wrong type in
taskman site
parameters. (VISTA:ENSEMBLE is the wrong type in taskman site
parameters.)
Taskman is late by 5239371809 seconds. not running..
Checking the Status List:
Node weight status time $J
The Status List is empty.

Checking the Schedule List:
Taskman has 14 tasks scheduled.
All of them are overdue. First task is 18162558 seconds late.

Checking the IO Lists:
There are no tasks waiting for devices.

Checking the Job List:
There are no tasks waiting for partitions.

Checking the Task List:
There are no tasks currently running.
On node VISTA:ENSEMBLE there are no free Sub-Manager(s). Status:
Run

I am not sure why its saying "Vista:Ensemble" is the wrong
parameter.....please help / advise.
Thank you.

[Branden Tanga]

Did you create the shortcut to CPRS and make your S=VistA servers IP and P=9210?



Branden Tanga

---

> From: asu...@gmail.com
> To: Hard...@googlegroups.com
> Subject: [Hardhats] Re: WSAECONNRESET ERROR in VistA + Ensemble
> Date: Thu, 11 Jan 2007 02:05:21 +0000

[Suchit]

Yes, I did create the shortcut to CPRS and S=VistA servers IP and
P=9210.
However, in the D ^ZTMON i get

VISTA:ENSEMBLE is the wrong type in taskman site> parameters.)> Taskman
is late by 5239371809 seconds. not running..

Is this the problem?

[Nancy Anthracite]

ED GETENV^%ZOSV W Y and see what your box volume pair is (the late two things
listed ad VISTA:CACHEWEB or something like that) and then check it in the
taskman site parameters to see if it is something different. In Taskman site
parameters, when it asks you for the Box volume pair, put ? Stop Taskman be
fore you do all of this. If that is OK, Check the VOLUME file to be sure
that is right and

Is this the problem?

--
Nancy Anthracite

[Gregory Woodhouse]

On Jan 10, 2007, at 5:49 PM, Edward J. Koll wrote:

First 2 thoughts that come to mind....

1. Is Taskman started?

2. Is the RPC Broker listener started on the port you are wanting to use?

Notice that the error was connection RESET not connection REFUSED. If there were no listener, the connection would be refused. On the other hand, a reset indicates something went wrong forcing the server to abandon the connection. Check your error trap.

Gregory Woodhouse

gregory....@sbcglobal.net

"Those who are enamored of practice

without theory are like a pilot who goes

into a ship without rudder or compass."

--Leonardo da Vinci (1452-1519)

[Suchit]

How do I check the error trap? I'm fairly new to this and I am not
familiar with Winsock either.
Thank you for all your help.