Technical Resources
Reliable, Savvy, Collaborative
Monthly Bulletin
Recommended
June 2022
April 2022
February 2022
Frequently Asked Questions
Bad Synopsis File Import
- Problem When attempting to import the MUOS synopsis file into JENM, a failure is received.
- Cause(s) Synopsis files must be in XML format, must remain unedited, and must contain necessary profile parameters to allow import.
- Solution If the synopsis file was edited to support downgrade, ensure all edits are changed back and the file is in XML format (should open in a browser). Ensure the synopsis file contains all seed parameters and ensure at least one frequency profile is contained within each individual profile.
Failed IP Assignment File Upload (JENM)
- Problem When attempting to upload an IP Assignment File for network design, receive a “Failed: File content is not properly formatted” display error.
- Cause(s) IP Assignment File formatting may have changed.
- Solution Ensure the file is formatted as received from JSMPS (e.g., banners in place, columns not
modified, etc.).
No Primary Contacts Appear to Build List (JENM)
- Problem When attempting to build a contact list, utilizing the MSISDNs contained in the imported synopsis file(s), the contacts do not appear to add to list.
- Cause(s) JENM software bug
- Solution Click on Network Configuration or Task Organization and click Modify. Press ‘Next’ through Network Configuration steps to get back to Primary Contacts. The list should populate. Delete terminal profiles uploaded in Resource Manager and upload during network design.
MUOS Profile Request Will Not Save/Submit (JSMPS)
- Problem When a MUOS Initiator attempts to submit a MUOS Profile Request, Internet Explorer presents an error message stating “Houston are you there?”
- Cause(s) Logging in with PKI causes a communication error when JSMPS database entries are requested. The profile request will not successfully save/submit.
- Solution Login with PKI, observe your username, and click “Obtain Password.” Retrieve password from SIPRNet email and re-login with username and new password. Re-submit profile request.
Corrupt Synopsis File
- Problem Following the transfer of a MUOS synopsis file from SIPRNet to NIPRNet via CENTRIXS, the synopsis file will not open or successfully import into JENM.
- Cause(s) In some scenarios, users will be required to convert the synopsis file from .xml to .txt if there are network restrictions that prohibit the use of .xml files. Copying synopsis file data from XML into notepad may cause formatting errors which result in a failed upload to JENM.
- Solution While in JSMPS>MUOS Terminal Management, select “View Synopsis” which should open the file in a new window or tab. Click File>Save As and save to the desired location. Go to the saved location and observe the default file name muos$mgmt.xml. Simply, rename it by removing the “.xml” and replace it with “.txt”. This will convert the file to a text format without corrupting the data. It is now safe to transfer using CENTRIXS.
Another solution to try is to insert an “UNCLASSIFIED” banner on the top and bottom of the document. Though not required, CENTRIXS may deem it necessary in order for the document to be passed down successfully.
Provisioning Error: K Key Missing (PRC-117)
- Problem When launching the MUOS waveform, the HMI states “Provisioning Error: K Key Missing”.
- Cause(s) Mismatch of keys to profile or multiple mission plans.
- Solution Check key info and verify AES keys have been provisioned. Ensure appropriately registered keys have been loaded to match MSISDN. Verify effectivity dates of loaded AES keys. Check to see if multiple mission plans are present and if so, deinstall the unintended mission plan. If AES UK/OK keys are loaded and no mismatch with MSISDN, this is most likely an erroneous error. To recover from this error, re-bootstrap the radio (delete Subscriber Profile and re-install new Subscriber Profile). If the error persists, reset factory defaults. Both methods will force a re-bootstrap which causes the radio to re-download the rest of the MUOS operational profile. Note: Resetting Factory Defaults will zeroize HAIPE FFVS and HAIPE PPK keys and delete the installed MUOS Mission Plan but will
GCK Unavailable (PRC-117)
- Problem When attempting to join a group, terminal HMI gives “GCK Unavailable”.
- Cause(s) Improper selection of active group keyset or improper provisioning of profile to access group with appropriate keyset. Attempting to join the group before GCK has been downloaded OTA.
- Solution Check terminal profile request and ensure appropriate group keyset is selected. Select different active keysets and return to the proper active keyset. Power cycle radio to attempt to clear error. Perform a new bootstrap of the profile and attempt to join the group again.
I/O Port Unavailable
- Problem PRC-117G, the HMI displays “SERVICE REQ FAILED I/O PORT UNAVAILABLE.”
- Cause(s) Incorrect equipment type selection in KMI for MUOS HAIPE FFVS. COMSEC Account Manager may have selected “MUOS” as equipment type.
- Solution When ordering MUOS HAIPE FFVS KEYMAT, the CAM should select PRC117 for the equipment type.
Harris Tactical Chat IP Is Not Operational
- Problem Upon opening Harris TacChat IP, a pop-up displays stating Tactical Chat IP is not operational. When clicking “My Station”, the user is only able to view the host IP address. Subnet IP and subnet mask are blank.
- Cause(s) This problem is likely due to connection settings applied to the chat application which force the application to utilize a serial-based connection for communications.
- Solution Open TacChat IP and select Options>application settings>Connections – Harris Tactical Chat IP> uncheck the box for “This device is connected to a radio by a direct serial connection.”
