How to reset/create the emergencyId /password in cache 5.0.15

[Sankar Manogaran]

Hi,

I am using Cache 5.0.15. At present, no body has admin privilege. So I need to create one. Inorder to do that, we have a option emergencyId. I read some of the documents that creating emergecyID would solve the issue. However the solution doesn't solve in cache 5.0.15. My question is does any one aware about this on cache 5.0.15?

Thanks in Advance!

Sankar

[karthi keyan]

Hello sankar,
Your cache running on Windows or Linux?
How you came to know about emergencyID, through cache 5 documentation or higher version .
It works perfect in higher versions but i need to check with version 5 . 
Use the password that you created on the fly.
Regards,
Karthik

--
--
Caché, Ensemble, DeepSee

---
You received this message because you are subscribed to the Google Groups "Caché, Ensemble, DeepSee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to intersystems-publi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[karthi keyan]

Hello Sankar,

Cache 5.0 does not have the option to access in emergencyID.

C:\CacheSys\Bin>ccontrol list [nodisplay > output.txt ]

-------------------------------------------------------------------------

usage: ccontrol start <config> 

           to start configuration <config>.

   or: ccontrol stop <config>

           to shut down configration <config>.

   or: ccontrol stopnoshut <config>

           to shut down configration <config> using INTNOSHUT^SHUTDOWN.

   or: ccontrol force <config>

           to force down configration <config>.

   or: ccontrol stopstart <config>

           to shut down and restart configration <config>.

   or: ccontrol [ run OR console OR cterminal ] <config> 

           to run Cache in programmer mode with

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

   or: ccontrol [ run OR console OR cterminal ] <config> <Mrou>

           to run Cache routine <Mrou> in application mode with

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

   or: ccontrol [ run OR console OR cterminal ] <config> <Mrou> <namespace>

           to run Cache routine <Mrou> in <namespace> in application mode with

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

   or: ccontrol probe <config>

           to probe if configuration  <config> is running.

           One byte long file (probe.dat) in config directory

           will contain '1' if running, '0' if not.

   or: ccontrol csystraystart <config>

           to start CsysTray for configration <config>.

   or: ccontrol csystraystop <config>

           to stop CsysTray for configration <config>.

   or: ccontrol clmanagerstop <config>

           to stop Clmanager running in configration <config>.

   or: ccontrol latstop

           to stop LAT.

   or: ccontrol latpause

           to pause LAT.

   or: ccontrol latresume

           to resume LAT.

   or: ccontrol latdump

           to dump LAT memory state.

   or: ccontrol lattraceon

           to begin (or resume) LAT packet trace.

   or: ccontrol lattraceoff

           to end LAT packet trace.

   or: ccontrol telnetstop <config>

           to stop TELNET.

you can try copy the CACHE.DAT from cache 5 and mount in any higher version. open the USER table and do changes and put back in Cache 5. I am not sure this will work but you can try. if this not working then contact Intersystem.

Regards,

Karthik

--

[Sankar Manogaran]

Thanks for the suggestion. Let me give a try.

You received this message because you are subscribed to a topic in the Google Groups "Caché, Ensemble, DeepSee" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/intersystems-public-cache/pOG_z6jFKjg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to intersystems-publi...@googlegroups.com.

[Michae...@kp.org]

Hey Sankar, hope you're doing well.

In the 5.0 docs at http://docs.intersystems.com/documentation/cache/cache5docs/PDFS/GCI.pdf I see this:

Section 3.3.1
csession <configname> -B
  Provides login for single-user version of Caché and, for
  multiuser versions, emergency login in case logins are
  disabled.

[Sankar Manogaran]

Hi Mike,

I am good. Hope you are doing great. Thanks for your post.

I am using windows OS, where csession doesn't recognized. 

Thanks,

Sankar

[Josep Balagué]

Hi Sankar,

For Windows: 

Start Caché As a user with administrative permissions run.

ccontrol start <instancename> /EmergencyID=<anyusername>,<anypassword>

Then login to cache using the username and password you specified above, this will log you in with single user access with %All permissions.

Navigation menu

• page
 
• discussion
 
• view source
 
• history

• log in / create account

To unsubscribe from this group and all its topics, send an email to intersystems-public-cache+unsub...@googlegroups.com.

[Sankar Manogaran]

Hi Josep,

Thanks for the suggestion. I tried execute the script ccontrol start <instancename> /EmergencyID=<anyusername>,<anypassword>

It starts the cache instance, but failed to login with EmergencyID and password

Hi Sankar,

To unsubscribe from this group and all its topics, send an email to intersystems-publi...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
Caché, Ensemble, DeepSee

---
You received this message because you are subscribed to a topic in the Google Groups "Caché, Ensemble, DeepSee" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/intersystems-public-cache/pOG_z6jFKjg/unsubscribe.

To unsubscribe from this group and all its topics, send an email to intersystems-publi...@googlegroups.com.

[Josep Balagué]

Sandar, I foud this at http://docs.intersystems.com/cache20071/csp/docbook/DocBook.UI.Page.cls?KEY=GCNV_R51

"Emergency Access

As a contingency, Caché provides a special emergency access mode that can be used under certain dire circumstances, such as severe damage to security configuration information or “unavailability” of any users with the %Admin_Manage:U or%Admin_Security:U privileges. (Although Caché attempts to prevent this situation by ensuring that there is always at least one user with the %All role, that user may not be available or may have forgotten his or her password.)

When Caché is running in emergency access mode, only a single user (the “emergency user”) is permitted. Caché is started in emergency access mode through a command-line switch, which passes a user name and password for the emergency user. This user name does not have to be previously defined within Caché. (In fact, even if the user name is defined in Caché, the emergency user is conceptually a different user.) The emergency user name and password are only valid for a single invocation of emergency mode.

The user starting Caché in emergency access mode must have operating-system level system management privileges. (On Windows systems, the user must be a member of the Administrators group. On UNIX systems, the user must be root. On OpenVMS systems, the user must have a system UIC.) Caché authenticates this user by checking his or her operating system level characteristics. When Caché is started in emergency access mode:

•  The emergency user is the only permitted user. Any attempt by another user to log in will fail.

•  The emergency user automatically has the %All role.
•  The Console and CSP services are enabled. All other services are disabled. This does not affect the enabled or disabled status of services in the configuration; only the current “in memory” information about services is affected.
•  Caché password authentication is used and unauthenticated access is forbidden for all services.
•  If possible, auditing is enabled for all events. Caché startup proceeds even if this is not possible.