There was a following directive in the Private Apache -- add it to your web server and it redirects documentation to docs.intersystems.com

Redirect /csp/docbook/ http://docs.intersystems.com/irisforhealth20231/csp/docbook/ 

Can you generate the QR-code in "/tmp" folder?
QR-Code on 2021.1 uses java, so you need to have java installed.
Or -- upgrade to 2023.1. QR-code module there does not need java

Even better -- use System Manager Machine field (it's also on John's screenshot) to restrict access by IP also

"Apache Worker Process Close Down: PID=11330; Configuration=0x7fe92f816000;"

It looks like the connection is closed because Apache decides to recycle the worker, therefore the connection is terminated. It's rather a question to Apache configuration, why it decided to recycle a worker process

I don't know what happens in your particular case. What you can do -- set logging level in the Web Gateway to "ev2"

"V2" incudus the following information: "Information regarding basic connection management between the Web Gateway and InterSystems IRIS (Start and Close points for each connection)"

Let the Web Gateway run for some time, then hopefully in the csp.log you'll see the details on how new connections are created and old ones are terminated

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...

Other idea -- check Apache settings. Which MPM does it use, what recycle settings for worker does it have?

Also, some notes on MPM models of Apache:
https://docs.intersystems.com/iris20232/csp/docbook/Doc.View.cls?KEY=GCG...

For already running backup or restore you can check "7) Monitor progress of backup or restore" menu in do ^BACKUP routine

This is a standard Windows error with the code 64:

C:\>net helpmsg 64

The specified network name is no longer available.

Some Caché code called some OS system function that returned this error and for some reason it was logged.

To investigate this further -- check what process logged the error message. Find in the Caché Audit a Login event with the corresponding process. Perhaps it might give you some hint

Generally, messages with severity 0 are informational, 1 -- warnings, 2 -- error, 3 -- critical

No. If you have Windows NT authentication enabled to connect to SQL Server then SQL Server ODBC driver uses OS user that executes irisdb.exe process. That's the same use as configured to run service IRIS.

If you'd like to use different user for authentication , then choose SQL Server authentication and specify that user and its password in SQL Gateway connection settings

Try to output %oblasterror:

zw %objlasterror

Based on "%Admin_Secure:USE" it seems like user who runs the CSP page lack USE privilege on %Admin_Secure resource

The best option -- create XSD from the XML or get XSD from the XML provider, import the XSD in IRIS, that will generate set of classes to import XML to

Other way -- manually create classes for each different xsi:type

Check carefully. Note -- in ^%ISCLOG (with percent) you enable the log. Then you read ^ISCLOG (without percent) in %SYS namespace.
When I repeated steps that I suggested to you, I saw the following error in ^ISCLOG

/* ERROR #5002: ObjectScript error: <PROTECT>^%CSP.Login.1 ^|^^c:\intersystems\iris2023x1\mgr\|dc.CustomLogin.1 */

Then I enabled auditing of Protect events, reproduced the eror and got more details:

Description:  Attempt to access a protected resource
Timestamp:    2023-03-19 16:01:38.000   Username:     CSPSystem
UTCTimestamp: 2023-03-19 15:01:38.000   Pid:          10896
Event Source: %System                   JobId/JobNum: 131089/17
Event Type:   %Security                 Session ID:   eK95W6SMCS
Event:        Protect                   IPAddress:    127.0.0.1
System ID:    DEP5570AKOBLOV:IRIS2023X1 Executable:   CSPa24.dll
Namespace:    %SYS                      Index:        196
Roles:
User Info:                              O/S User:     CSP Gateway
Routine:      ^%CSP.Login.1 |"^^c:\intersystems\iris2023x1\mgr\irislib\"|
Authentication: Password
Event Data:
<PROTECT>^%CSP.Login.1 *^|^^c:\intersystems\iris2023x1\mgr\|dc.CustomLogin.1

Indeed, user CSPSystem does not have READ permission on irissys database, where custom login class is located. Rather I should have created a new role that has only READ permission on %DB_IRISSYS resource, not RW.

I added role %DB_IRISSYS to user CSPSystem, closed connections from Apache to IRIS, so that the role is added on new connection, then login page began to work

Documentation has an important note about this parameter:

This parameter has been retained for compatibility, but should not be used when building new applications.

https://docs.intersystems.com/iris20223/csp/docbook/Doc.View.cls?KEY=RAC...

Yuri, enable ISCLOG, reproduce the error, disable ISCLOG and then check if it has any errors, e.g. errors.

%SYS>kill ^%ISCLOG, ^ISCLOG
%SYS>set ^%ISCLOG = 3
//reproduce the error
%SYS>set ^%ISCLOG = 0
%SYS>zw ^ISCLOG

Afaik, with custom login pages user CSPSystem needs to have READ permissions on a database where custom login page class is located

In HealthShare section you see Extended Maintenance kits
In Continuous Delivery section you'll find Health Connect 2022.3, 2022.2

404 is also returned when there are some permissions issues.
Try to give %All to the user that you calling this API with and see if it helps. If yes -- then this is permissions issue.
Or enable Audit and auditing for Protect event and see if it is logged in Audit when the problem happens

Other idea -- enable ISCLOG, reproduce the problem, disable ISCLOG and see if there are any errors there. ISCLOG is very verbose, so just do one HTTP request with ISCLOG enabled

enable:

%SYS>kill ^ISCLOG,^%ISCLOG
%SYS>set ^%ISCLOG = 3

disable:

%SYS>set ^%ISCLOG = 0

analyze:

%SYS>zw ^ISCLOG (yes, without %)

Generally, you should install external web server and use it with the application. Private Web Server (the one that runs on 57772) are for Management Portal and some basic tests only

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

Choose Logical Mode in dropdown near the Query Builder. Perhaps IRIS SQL tries to do some Logical -> Display conversion and fails.

See also

SET OPTION PKEY_IS_IDKEY = true

With this enabled your sample works as you expect

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls...

Mark, you need to close connections from Web Gateway to IRIS, so that Web Gateway reconnects and CSPSystem logins with the new role. You can do this in Web Gateway -> Status page -- close button for the second table. Or just restart the web server.

Note -- Roles field in the Audit details. Check that it has %DB_SRFT role when happens again.

In System Explorer -> Globals check "Show SQL Table Names". You'll see information on how particular global is used.