Put CCOW=DISABLED into the line with s= and p=
The demo is probably only allowed to use the new listener which makes the
connections easier through just one port and thus fewer firewall problems and
the connection is probably controlled by the listener starter which connects
when Taskman is started (I think).
CPRS normally will go for the new listener and if that fails, will switch to
the old. CPRS 23-15 was not made to use the new listener natively and the
was added when the patch for the new listener was applied to the demo, which
is why I suggested switching to the old listener settings, but your solution
is better I think. Now the next question is to find out if STOPALL^XWBTCP
works in the demo to stop the listener.
On Wednesday 27 July 2005 12:30 pm, TyrusMaynard wrote:
> Usha,
> According to your post on Jul 19 you were using CPRSv 1.0.23.15 to
> connect to your local Vista Demo.
>
> I was never able to connect with 23.15 also when I posted the following to
> the list back in January:
> "after starting RPC broker the Linux machine is just idling. *until* I
> connect with CPRS 23-15 which gives
> "Error Encountered Function was: recv
> Error was:WSAETIMEDOUT"
> which causes the server to go to 97% cpu continuously
> the D STOP^XWBTCP(9200) fails to stop the process and I have to exit GTM
> and run mupip stop process"
>
> However when I installed the modified CPRS which is provided for access to
> the online VistaDemo, it connects fine with the VistaDemo running locally.
> I don't know what version that is (or was before modification) and I don't
> know why its modifications seem to be a prerequisite for access to the
> running demo.
>
> Rusty
>
> Usha wrote:
> > Hi
> >
> > I tried to get the VA CPRS demo up and running on our linux server. The
> > only problem with it is that while connecting through CPRS, it displays
> > "WSAETIMEDOUT".
> > I have tried removing all the other NULL devices. I have tried disabling
> > the DEFAULT AUTO SIGN-ON in the KERNEL SYSTEM PARAMETERS. But the problem
> > persists...
> > Then I thought of the RPC Broker Debug log. I edited the "Enable Broker
> > Logging" to "verbose" (I was unable to run D VIEW^XWBDLOG and D
> > KILLALL^XWBDLOG as they were not available). It said "This parameter
> > controls if the RPC Broker records log data in ^TMP("XWBDBUG",$J).".
> > After running CPRS, when I try to see the global "^TMP("XWBDBUG",4277)",
> > following is displayed "%GTM-E-GVUNDEF, Global variable undefined:
> > ^TMP("XWBDBUG")".
> > Can anybody help?
> >
> > Regards
> > Usha
> >
> > ----- Original Message -----
> > From: "Mike Lieman" <[EMAIL PROTECTED]>
> > To: <hardhats-members@lists.sourceforge.net>
> > Sent: Tuesday, July 26, 2005 8:05 PM
> > Subject: Re: [Hardhats-members] == Question to Bhaskar =
> >
> > On 7/25/05, Alberto Odor <[EMAIL PROTECTED]> wrote:
> >>I have finished configuring GT.M but can't connect to CPRS, the
> >>spalshscreen disappears when I press the OK button, without any error
> >>message.
> >
> > You know what this sounds like to me?
> >
> > NULL device conflict.
> >
> > Go into VA Fileman and delete everything but the null device for gt.m
> >
> > --- Start Example ----
> >
> > GTM>D Q^DI
> >
> >
> > VA FileMan 22.0
> >
> >
> > Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
> >
> >
> >
> > INPUT TO WHAT FILE: DEVICE//
> > EDIT WHICH FIELD: ALL//
> >
> >
> > Select DEVICE NAME: null
> >
> > ---- End Example ----
> >
> > It'll give you a list, pull up the ones that aren't for unix/gt.m, and
> > give them a name of @
> > that'll delete them.
> >
> > Once they're all gone EXCEPT the
> >
> > GTM-UNIX-NULL Bit Bucket (GT.M-Unix) /dev/null
> >
> > entry, give cprs a shot again.
> >
> > Take Care,
> >
> > Mike
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=ick
> > _______________________________________________
> > Hardhats-members mailing list
> > Hardhats-members@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> > _______________________________________________
> > Hardhats-members mailing list
> > Hardhats-members@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/hardhats-members
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
--
Nancy Anthracite
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
