If you're going to run on Cache/Windows, you do not need the globals and routines zip files.

The port that CIS is looking for is the port of the RPC broker, not the port that Cache listens on for Studio connections.  You need to start the RPC broker, and to do that, you first need to start TaskMan.  Open up the Cache Terminal and run the following:

D START^ZTMB
D ^ZTMON

Press ENTER until it says Taskman is current... , then type ^ and press ENTER to exit.  Next, run:

D RESTART^XWBTCP

Once this command finishes, the RPC broker should be running on port 9201 (the default port configured in the release).  Enter the host and port 9201 in the CIS login dialog and try connecting again.

If you want to change the port, you will need to edit the RPC BROKER SITE PARAMETERS file within OpenVista.

You are probably just in the wrong namespace.  In cache, namespaces are analogous to separate databases within a single database server.  If you know the name of your namespace, you can simply change to it before you execute your statements.  For example, if your desired namespace is "CACHE", you can change to it as follows:

USER> ZNSPACE "CACHE"

CACHE> D START^ZTMB

... the ZNSPACE command can be abbreviated to ZN.

If you aren't sure what your namespace is then you can run the ^%CD routine and inputing ? at the namespace prompt and it will show you a list of namespaces:

USER> D ^%CD

Namespace: ?

    '?' for help.
    '@' (at-sign) to edit the default, the last namespace
        name attempted.  Edit the line just as if it were
        a line of code.
    <RETURN> will leave you in the current namespace.
Here are the defined namespaces:
     %SYS
     CACHE
     DEMO
     DOCBOOK
     SAMPLES
     USER

... you can enter the name of the desired namespace at the Namespace: prompt and it will change to the requested namespace for you.

good luck.

Andy

I don't think I've seen that particular error before - what version of Cache are you using?

What did you do to fix TaskMan (for the benefit of others who may find this thread in the future)?

For the broker problem, have a look at this document and see if it fixes your problem: CPRS can connect, but CIS says "Unable to connect to VistA server"

Yes, the global and routine mappings are required.

I think running STRT^XWBTCP(9201) starts the "old-style" broker.  Try RESTART^XWBTCP instead.

At this point, once you started the old style RPC Broker, its hard for me to tell if the old one is still running or not but it looks like the old style might be.  The first step would be to stop the broker that is running on port 9201.  I'm no expert in this, but I would suppose that if you started the old style with STRT^XWBTCP, then try STOP^XWBTCP and check the port to make sure that no process at all is running on the port.  If this is a development environment, then stoppping and starting cache itself is a brute-force way to do the same thing -- but only if you can do that without disrupting other users, of course.  Once you are sure that nothing is running on port 9201, then, as Jon indicated, start RPCBroker as:

D RESTART^XWBTCP

... and run taskman as:

D ^ZTMB

Good luck and let us know if it works or not.

Andy

Perhaps your vista instance is configured to run the new style rpc broker on a different port other than 9201?  Sometimes it will be configured for 9021 or 9260, etc.  After starting the new style broker, can you check all your TCP ports for some type of XWBTCP process that is listening and then use that port when you connect from CIS?  I'm hoping that you'll find it running on a different port in the 9xxx range.  Also, when you start CIS, make sure that you are using -proxy-mode builtin as a command line argument.

Andy