Authentication problems in new TRYCACHE installation

Question

Question

Jon Midgley · Feb 10, 2018

New Windows 10 Cache [ TRYCACHE] successfully installed - but unable to log onto the Management Portal . What "User Name" and "Password" are being asked for? No opportunity to specify the sources. Thanks.

Discussion (5)0

Log in or sign up to continue

Robert Cemper · Feb 10, 2018

User =_SYSTEM PW=sys or SYS it varies

3 0

score 0 · Answer 1 · 2018-02-10T16:40:46-05:00

Unfortunately, "User =_SYSTEM PW=sys or SYS it varies" didn't work - is that for Operating-system-based? I think my authentication type is Cache login. Thank you in any case.

score 2 · Answer 2 · 2018-02-10T16:50:00-05:00

I assume this is the Trial version !

if you log in the management portal you should have a management account _SYSTEM
and it has a 3 letter password SYS or sys

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=RSQL_defaultusernamepassword#RSQL_C127680

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCAS_users#GCAS_users_predefined

score 0 · Answer 3 · 2018-02-10T18:56:01-05:00

If none of those above solutions work, it might be possible to use emergency login into the system. Then setup your own username and password in the management portal once in.

1. Stop cache instance.

2. Open windows cmd as "Run as administrator".

3. Browse to the bin directory inside the directory where you installed cache.

4. use the command

ccontrol start <instance> /EmergencyId=<username>,<password>

Where instance is the name of your Caché instance, and type any username and password.

E.g:

ccontrol start MyCache /EmergencyId=Eugenia,52601

Try to login using that and then setup a username and password and then restart Caché to login via the newly setup username and password. You can read more under "Emergency Access" here:

http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=...

score 1 · Answer 4 · 2018-02-11T15:56:35-05:00

Cache is now reinstalled and operational. The reported problem was caused by missing the opportunity to specify the passwords during the first installation. Thank you to all who offered help.