Authentication Option change - Terminal and Management portal no longer loading

[R Ali]

Am just setting up a test box, and it was always logging in as unknown
user, so I changed the first two checkboxes,'allow unauthenticated
access', 'allow operating system authentication', in the
authentication options under system security settings and hit save,
since then it seems I cant login/load, and terminal closes after
displaying 'access denied', now thinking I may have click the third
instead ' allow password authentication' of the second in error with
my trigger happy fingers.

Any ideas on how this can be resolved outside of termical or the
management portal?

Any advice appreciated.

[Dale du Preez]

Hi,

You should be able to stop Ensemble entirely, either from the cube (on
Windows) or via ccontrol stop <instancename> (on Unix or VMS).

You can then perform an emergency access start by following the
instructions here:

http://docs.intersystems.com/cache20101/csp/docbook/DocBook.UI.Page.cls?KEY=GCAS_secmgmt#GCAS_secmgmt_emerg_invoking

I hope that helps,
Dale

[Ali Ruhul (RQ8) Mid Essex Hospital]

Many Thanks for that Dale,

Have tried this, forgive me for my ignorance, but I believe my instance name is 'cache', none the less I tried numerous paths with prodcution name, as well as cache, including namspace all returning the same

Get an error, window as below;

"Control.exe error: pid=3624

(29) Unable to open registry key: SOFTWARE\intersystems\cache\configurations\cache\directory reason (2) the system cannot find the file specified."

Hi,

http://docs.intersystems.com/cache20101/csp/docbook/DocBook.UI.Page.cls?KEY=GCAS_secmgmt#GCAS_secmgmt_emerg_invoking

--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to Ensemble-in...@googlegroups.com
To unsubscribe from this group, send email to Ensemble-in-Healt...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/Ensemble-in-Healthcare?hl=en

Mid Essex Hospital Services NHS Trust Caring for you, Caring about you.

Information in this message may contain confidential and privileged information. If you are not the intended recipient please accept our apologies; please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it.

Content of emails received by this Trust will be subject to disclosure under the Freedom of Information Act 2000. Unless the information is legally exempt from disclosure, confidentiality of this e-mail and your reply cannot be guaranteed. Thank you for your co-operation.

[Dale du Preez]

Hi,

If you change into the installation directory, you should be able to run:
ccontrol list
or
ccontrol all
to display the currently installed instances of Ensemble and/or Cache on
your system. The "all" option is more concise, and the "list" option is
slightly more verbose. In either case, the instance name is listed along
with the directory. Using this name should correctly stop (or start)
your instance.

I hope that helps,
Dale

[Ali Ruhul (RQ8) Mid Essex Hospital]

Many thanks Dale, I did run it from the bin directory prior.

I can see the ccontrol exe in the path= C:\InterSystems\Ensemble\Bin

Clicking on this I get the below,

Based on the first, I thought instead in windows navigate to= 'C:\InterSystems\Ensemble' as this holds the cache.cpf

No joy, just get a =

'ccontrol' is not recognized as an internal or external command,
operable program or batch file.

When in bin via cmd/windows I get the lacking registry error as mentioned before.

CCONTROL.EXE USAGE:

ccontrol start <instance name> [<full path and file name of .cpf file>]

Starts Caché instance <instance name>, optionally using the specified .cpf file.

If a new .cpf file is specified, it becomes the default startup .cpf file.

Note: An optional /EmergencyId=Username,Password can be used

to start Caché in emergency mode. When the EmergencyUserId

argument is supplied, the system starts up in emergency mode in which

only the baseline databases are mounted and access to Caché is governed

by Caché login using that username and password. Emergency mode is supplied

to give access in the event that privileged users are not available or their password

is forgotten. Emergency startup is only available from an administrator account.

When Caché is started in emergency mode, the Caché control service is not used.

This means that if you log out of Windows, all the Caché processes will immediately exit.

ccontrol startnostu <instance name>

Starts instance <instance name> without running ^STU.

ccontrol stop <instance name>

Shuts down instance <instance name>.

ccontrol stopnoshut <instance name>.

Shuts down instance <instance name> using INTNOSHUT^SHUTDOWN.

ccontrol force <instance name>

Forces down instance <instance name>.

ccontrol stopstart <instance name>

Shuts down and restarts instance <instance name>.

ccontrol [ run OR console OR cterminal ] <instance name>

Runs Caché in programmer mode with

[ no-device OR console OR cterminal ] for $Principal.

ccontrol [ run OR console OR cterminal ] <instance name> <Mrou>

Runs Caché routine <Mrou> in application mode with

[ no-device OR console OR cterminal ] for $Principal.

ccontrol [ run OR console OR cterminal ] <instance name> <Mrou> <namespace>

Runs Caché routine <Mrou> in <namespace> in application mode with

[ no-device OR console OR cterminal ] for $Principal.

Note: An optional /Title="Title string" can specify the console

or terminal title bar text.

Examples:

Run ^%SS in a console in the c81u instance:

ccontrol console c81u ^^%SS

Run ^%SS in a Cache terminal in the c81u instance:

ccontrol cterminal c81u ^^%SS

Start ^%SS running in a Cache terminal in the c81u instance from a batch file (extra % required):

ccontrol cterminal c81u ^^%%SS

Run sub^test("hello") in a Cache terminal in the user namespace of cache instance c71u:

ccontrol cterminal c71u sub^^test(\"hello\") USER

Note: The namespace parameter only works if the login record for the user does not specify a namespace. If the user security record specifies a namespace, then it will override the namespace parameter.

ccontrol csystraystart <instance name>

Starts CsysTray for instance <instance name>.

ccontrol csystraystop <instance name>

Stops CsysTray for instance <instance name>.

ccontrol clmanagerstop <instance name>

Stops the clmanager process running in instance <instance name>.

ccontrol all [nodisplay > outputfile]

Lists all installed instances.

ccontrol list [nodisplay > outputfile]

Lists information about all installed instances.

ccontrol serverlist [nodisplay > outputfile]

Lists information about all defined servers.

Note: When [nodisplay > outputfile] is present, output is redirected to the file

instead of being displayed in a browser.

ccontrol latstop

Stops the Caché LAT server.

ccontrol latpause

Pauses the Caché LAT server.

ccontrol latresume

Causes a paused Caché LAT server to resume.

ccontrol latdump

Initiates a Caché LAT server memory state dump.

ccontrol lattraceon

Initiates (or resumes) a Caché LAT packet trace.

ccontrol lattraceoff

Ends a Caché LAT packet trace.

ccontrol telnetstop <instance name>

Stops the Caché TELNET daemon.

[Dale du Preez]

Hi Ali,

If this is still a problem, I think it may be well worth contacting the
WRC to get this ironed out quickly.

Does the output from running ccontrol all from a command line in
C:\InterSystems\Ensemble\Bin not list your instance names?

If the instance listed is throwing errors then I think the WRC are
definitely the right resource for this.

Dale