When loading a display I get the Prognosis Client GUI error:
Unknown Record name xxxxx.
PARAMS: The invalid Record name.
CAUSE: The record is not valid
ACTION: Specify a valid record and/or RECORD DEFINITION NOT AVAILABLE
Causes: There are two common causes for this error:
1. Prognosis Version and Patch levels differ between servers and therefore have differing record definitions. The Solution is to bring all servers to similar version and patch levels.
2. old License file on the server or not licensed for that record. The Solution is to ensure you have the latest supplied license applied to the node and if so to check with your IR Account Manager or Support as to whether you have the product licensed.
Recently my institution have migrated the Prognosis service to new set of servers, and have also requested to have our license/license files updated. However, after being informed that license was renewed/files updated properly, I'm still encountering running Prognosis display over the most basic RECORDS, such as Prognosis for Payments/MTS, to poll the queue details:
RECORD DEFINITION NOT AVAILABLE Unknown Rec AciMtsQueue.
This message may be generated by either of the following cases:
1. The Record requested is not licensed on any Node on your
Prognosis system. In this case, you have started a Document
created from a previous network configuration that now no
longer supports the Record you wish to collect.
2. The Record Id is invalid, this may be due to a currupt document
that has been started.
3. The Record Id is invalid, it may have been incorrectly specified
if created using IRCMD.
4. The Record Id is invalid, the Document was created on an old
version of Prognosis that specified a Record that has now
Just as a preference, we migrated exactly the same setup (AIX OS level, Prognosis version, MTS version, etc.) The only difference is that, it was on one set of servers and now it's on another set of servers in different physical location. So, #2 and #4 are unlikely. #3 is also unlikely, again based solely on the fact everything in previous server grouping works (in fact continue to work as we speak) and it is the basic built-in RECORD. Which leaves me to assume the likely option of #1.
I have reached out to double-check that license file for the AIX/MTS servers are updated correctly, but I also want to know where can I go locally (i.e., not in a PDF documentation) to see where all, or parts, of Record IDs are defined and made available for usage?
Please check if the updatd license file has the MTS product code for the AIX server. If the server is under new host name and the product code is not present, the record will not be recognised so the unknown record error will pop up.
You can log a support case, our suport team can help identify the cause.
Thank you @David_Sun for the response.
That was our first troubleshooting step as well; there were three of us, each in charge a piece in our environment: The Windows server side, AIX/(MTS) application server side, and user GUI side. we have examined our piece and license file matched with our environment.
I do have a question, perhaps you can answer: If we install our application server side (AIX/MTS server) first with non-functioning license file, i.e., license file that doesn't have its host name in list, and we later replace the license file when we got our updated contract and new license file, would that by chance still hold onto the old non-functioning licensing? Do we need to reinstall the app-side component now the proper license is in? we have path level all the way up to z1150p02. Do we need to roll back and "re-patching" our server?
Hi @Kuanyu_C ,
Thank you for quick reply.
So the MTS code is in the license file.
If the intallation completed successfully then you do not need to re-install it after you get the new updated license file, just replace the old license file and restart Prognosis.
For patching, please install the latest v11.5 patch 8 on top of the current installation.
If the problem persists please log a support casse with the infrax from both AIX and Windows server, and the error screenshot so we can check in details.