Overview
The Risk Modeler API identifies the cause and resolution of application errors by means of error messages. These error codes are displayed in the header of the HTTP response.
Each application error consists of an error code that identifies the error and a brief message that describes that the cause and remediation of of the issue. The error code (e.g. ACCT-001) consists of two parts: a string that identifies the error type and a number that identifies the specific error.
The Risk Modeler API returns an error whenever it returns a client error response (i.e. a response with a 400, 401, 403, 404 etc. HTTP status code). The application error is returned in the header of the response. For more information, see HTTP Status Codes.
The error message displayed in the following tables include the %d and %s variable to represent decimal and string values. Error code messages are generated dynamically and the API substitutes the values of the relevant objects in responses.
ACCT
Account errors.
| Error Code | Message |
|---|---|
ACCT-001 | We could not find account %d in this EDM. |
ACCT-002 | Sorry, you do not have access permissions for account %d. Check with your tenant administrator about getting access. |
ACCT-003 | Processing or updating account ID: %d not permitted since the account is being processed. Job ID: %d |
ACCT-004 | No geocoded locations exist in account with ID %d and number %s. Geocode this account before you run an analysis. |
ACCT-005 | Ensure at least one location is geocoded before committing account ID: %d |
ACCT-006 | No results available. Analysis job ID: %d failed for account ID: %d |
ACCT-007 | Currently processing account ID: %d. Account cannot be processed or updated while it is in the Commit queue. job ID: %d |
ACCT-008 | %s |
ACCT-404 | %s |
ACCT-405 | %s |
ACCT-500 | Sorry, we encountered an error retrieving account %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-501 | Sorry, we encountered an error checking if account %d exists. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-502 | Sorry, we encountered an error creating this account. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-503 | Database error occurred while retrieving account by link ID: %s |
ACCT-504 | Sorry, we encountered an error retrieving information about account %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-505 | Sorry, we encountered an error deleting account %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-506 | Sorry, we encountered an error saving the changes for account %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-507 | Sorry, we encountered an error retrieving geographic information for account %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-508 | Sorry, we encountered an error copying account %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-509 | Database error occurred while mapping account ID %d with user %d |
ACCT-510 | Database error occurred while saving account details for account ID: %d |
ACCT-511 | Sorry, we encountered an error searching for accounts. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-512 | Sorry, we encountered an error looking up permissions for account %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-514 | Sorry, we encountered an error retrieving geocoding information for one or more locations in account %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-515 | Sorry, we encountered an error exporting account %d to the EDM you selected. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-516 | Sorry, we encountered an error checking the geocode status of account %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-517 | Sorry, we encountered an error for account %d matching locations to policy special conditions. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-518 | Database error occurred while fetching number of exposures for exposure type: ACCOUNT. |
ACCT-519 | %s |
ACCT-520 | Error occurred with internal status code: %d while geocoding account ID: %d |
ACCT-521 | Database error occurred while archiving account report for account ID: %d |
ACCT-531 | Error occurred while retrieving reporting services for account ID: %d. No services found. |
ACCT-532 | Invalid output generated while processing account ID: %d |
ACCT-533 | Process Account failed for account ID: %d. %s |
ACCT-534 | Geocode Account failed for account ID: %d. %s |
ACCT-535 | Invalid output generated while geocoding account ID: %d |
ACCT-536 | Retrieve Reports failed for account ID: %d. %s |
ACCT-537 | Invalid output generated while retrieving reports for account ID: %d |
ACCT-538 | Sorry, we encountered an error converting currencies for account with ID: %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-539 | Failed to update Account metrics |
ACCT-540 | More than one location in account %d has latitude %f and longitude %f. Two locations in an account cannot have the same coordinates. |
ACCT-541 | No locations in account %d have latitude %f and longitude %f. Check the coordinates or geocode the account again. |
ACCT-542 | Sorry, we encountered an error performing a bulk edit on accounts for portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
ACCT-543 | account ID %d does not exist for %s number: %s |
ACCT-544 | No accounts found |
ACCT-545 | Duplicate account ID %s found in input |
ACCT-546 | Sorry, we encountered an error converting currencies for account with ID: %d due to invalid values in the specified currency scheme. Please verify your currency scheme and try again, and contact Moody's RMS Support if this still does not work. |
ACCU
| Error Code | Message |
|---|---|
ACCU-001 | Accumulation details not found |
ACCU-002 | Forbidden |
ACCU-500 | Database error occurred while retrieving accumulation details for portfolio ID: %d |
AGGPORT
| Error Code | Message |
|---|---|
AGGPORT-401 | We could not find aggregate portfolio %d in this EDM. |
AGGPORT-402 | We were unable to save the aggregate portfolio because we could not find cedant %s in this EDM. |
AGGPORT-404 | %s |
AGGPORT-405 | %s |
AGGPORT-500 | Sorry, we encountered an error saving the changes for aggregate portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-501 | Sorry, we encountered an error creating this aggregate portfolio. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-502 | Sorry, we encountered an error retrieving aggregate portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-503 | Sorry, we encountered an error searching for aggregate portfolios. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-504 | Sorry, we encountered an error deleting aggregate portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-505 | Sorry, we encountered an error copying aggregate portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-506 | Sorry, we encountered an error checking if aggregate portfolio %d exists. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-507 | Sorry, we encountered an error while submitting the convert currency job. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-508 | Sorry, we encountered an error retrieving information about aggregate portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-509 | Sorry, we encountered an error while submitting alm import job. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-510 | Sorry, we encountered an error retrieving geographic information for aggregate portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-511 | Sorry, this is an invalid resolution type: %s. |
AGGPORT-512 | Sorry, we encountered an error retrieving ALM profiles for aggregate portfolio %d. |
AGGPORT-513 | Sorry, we encountered an error converting currencies for aggregate portfolio with ID: %d. Try again, and contact Moody's RMS Support if this still does not work. |
AGGPORT-514 | Database error occurred while fetching number of exposures for exposure type: AGGREGATE PORTFOLIO. |
AGGPORT-515 | Invalid Peril code %s in request. Please use a valid peril code. |
AGGPORT-516 | Sorry, we encountered an error converting currencies for aggregate portfolio with ID: %d due to invalid values in the specified currency scheme. Please verify your currency scheme and try again, and contact Moody's RMS Support if this still does not work. |
AGGEXP
| Error Code | Message |
|---|---|
AGGEXP-401 | Sorry, we could not find aggregate exposure %d in this EDM. |
AGGEXP-500 | Sorry, we encountered an error on our end. Try saving changes for aggregate exposure %d again, and contact Moody's RMS Support if this still does not work. |
AGGEXP-501 | Sorry, we encountered an error on our end. Try creating this aggregate exposure again, and contact Moody's RMS Support if this still does not work. |
AGGEXP-502 | Sorry, we encountered an error on our end. Try retrieving aggregate exposure %d again, and contact Moody's RMS Support if this still does not work. |
AGGEXP-503 | Sorry, we encountered an error on our end. Try searching for aggregate exposures again, and contact Moody's RMS Support if this still does not work. |
AGGEXP-504 | Sorry, we encountered an error on our end. Try deleting aggregate exposure %d again, and contact Moody's RMS Support if this still does not work. |
AGGEXP-505 | Sorry, we encountered an error on our end. Try copying aggregate exposure %d again, and contact Moody's RMS Support if this still does not work. |
AGGEXP-506 | Sorry, we encountered an error on our end finding aggregate exposure %d. Try again, and contact Moody's RMS Support if this still does not work. |
AGGEXP-507 | Sorry, we encountered an import error on our end. Try again, and contact Moody's RMS Support if this still does not work. |
AGGEXP-508 | Sorry, looks like you tried to import duplicate records for aggregate portfolio %s. Please check your ALM import request and try again. |
AGGEXP-509 | Sorry, country code and resolution can not be null or empty. |
ALM
| Error Code | Message |
|---|---|
ALM-001 | Sorry, we encountered an error while running the ALM analysis job. Try again, and contact Moody's RMS Support if this still does not work. |
ALM-002 | Sorry, this profile request with peril %s isn't valid. Try again, and contact Moody's RMS Support if this still does not work. |
ALM-003 | Sorry, the analysis currency %s for this ALM analysis is invalid. Specify a valid currency and try again. |
ALM-004 | Cannot find default event rate scheme |
ALM-005 | Invalid portfolioId: %s |
ALM-006 | Invalid profile ids: %s |
ALM-007 | Invalid treaty ids |
ALM-008 | Unable to load alm profiles |
ALM-011 | Invalid value for %s |
ALM-401 | Database error occurred, ALM does not exists |
ALM-501 | Database error occurred while loading alms, reason : %s |
ANALYSIS
| Error Code | Message |
|---|---|
ANALYSIS-001 | Error occurred while generating the analysis ID sequence |
ANALYSIS-002 | Database error occurred while inserting rdm analysis record for ID : %d |
ANALYSIS-003 | Database error occurred while fetching the engine version for ID : %d |
ANALYSIS-004 | Database error occurred while inserting the record for rdm analysis perspective |
ANALYSIS-005 | Invalid analysis ID : %s |
ANALYSIS-006 | Database error occurred while fetching location AAL record for ID : %d |
ANALYSIS-007 | Load database connection properties error |
ANALYSIS-008 | The perspective code %s is invalid. Please check that your requests specify a valid perspective. |
ANALYSIS-009 | Perspective code %s is valid, but does not exist for analysis %d |
ANALYSIS-010 | Database error occurred while validating analysis and perspectives |
ANALYSIS-012 | Analysis ID %d is invalid. Check that your request specifies a valid analysis ID and that engine type is %s. |
ANALYSIS-013 | Analysis ID is invalid for Location AAL request. Check that your request specifies a valid analysis ID and that engine type is one of the supported types in %s. |
ANALYSIS-014 | Post-analysis treaty editing is not supported for this analysis. Confirm that analysis ID %d is valid, exposure level is portfolio, analysis type is EP, and the engine type is DLM, ALM or Group. See "Creating and Editing Treaties" in the Moody's RMS Support Center. |
ANALYSIS-015 | Downloading results in CSV or Parquet format is not supported for these results. Confirm that analysis ID %d is valid. You cannot download EP metrics for non-EP analyses, you cannot download stats for DLM/ALM non-EP analyses. See "Exporting to File" in the Moody's RMS Support Center. |
ANALYSIS-016 | Grouping is not supported for these analyses. Confirm that the analysis IDs are valid and that the engine type is DLM or Group. See "Grouping Results" in the Moody's RMS Support Center. |
ANALYSIS-017 | Sorry, we encountered an error while submitting a post-analysis treaty editing job for analysis ID %d. Try again, and contact Moody's RMS Support if this still does not work. |
ANALYSIS-018 | We encountered an error retrieving the analysis perspectives for analysis with error %s. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
ANALYSIS-019 | We encountered an error retrieving loss results for analysis %d. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
ANALYSIS-020 | Sorry, the metric type %s is not valid for analysis ID %d. Valid metrics are AEP, OEP, TCE-AEP, TCE-OEP. |
ANALYSIS-021 | Analysis ID is invalid for metrics request. Check that your request specifies a valid analysis ID and that engine type is one of the supported types in %s. |
ANALYSIS-022 | We encountered an error retrieving metrics. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
ANALYSIS-023 | The exposure type %d is invalid. Please check that your requests specify a valid exposure type. |
ANALYSIS-024 | Exposure type %d is invalid for this request. Only results on portfolio/aggregate-portfolio/account/policy are allowed. |
ANALYSIS-025 | Export of climate change results to RDM is not supported for HD results. |
ANALYSIS-026 | Sorry, the provided exposure type '%s' did not match the expected exposure type '%s'. |
ANALYSIS-027 | Sorry, the exposure type %s is not valid for DLM analysis. Valid exposure types are ACCOUNT and PORTFOLIO. |
ANALYSIS-028 | Sorry, the exposure type %s is not valid for model analysis. Valid exposure types are ACCOUNT, PORTFOLIO and 'AGGPORTFOLIO'. |
ANALYSIS-029 | Sorry, the exposure type is missing. Please check that your request contains exposure type. |
ANALYSIS-030 | Sorry, the provided value for exposure type is invalid. Please check that your request contains valid exposure type. |
ANALYSIS-031 | Sorry, the provided value for filter condition is invalid. Please check that your request contains a valid filter condition. |
ANALYSIS-032 | Sorry, you can't download results for an analysis |
ANALYSIS-033 | Select one of the following options to export. Select one or more DLM/Group/ALM results or select one or more HD EP results. |
ANALYSIS-034 | You cannot export the selected analysis to RDM as PLT. This export is supported only for HD EP analyses. |
ANALYSIS-035 | Sorry, we encountered an error on our end while retrieving analysis details for analysis ID %d. Contact Support at [email protected]. |
ANALYSIS-036 | Sorry, the offset parameter must be set to 0 on older analyses. |
ANALYSIS-037 | Sorry, sorting this metric type is not supported. Remove the sort parameter from your request and try again. |
ANALYSIS-038 | Sorry, this metric type requires one granularity to be selected. Make sure there is only one granularity in your request and try again. |
ANALYSIS-040 | Sorry, the metric key %s is not valid. Metric key is RETURNPERIOD or PROBABILITY or financial perspective in the format financial-perspective_LOSS, e.g., GR_LOSS (gross loss) or QS_LOSS (quota share loss). See the Risk Modeler Moody's RMS Support Center for list of financial perspectives. Enter a valid metric key and try again. |
ANALYSIS-041 | Exporting this RDM is not supported because it is an uploaded RDM that contains grouped HD results or HD ALM multi-region results. |
ANALYSIS_GROUP
| Error Code | Message |
|---|---|
ANALYSIS_GROUP-001 | Could not parse URL, reason %s |
ANALYSIS_GROUP-002 | Database error occurred while getting a analysisGroup with groupId: %d%n |
ANALYSIS_GROUP-003 | Database error occurred while getting a list of analysisGroup, reason %s |
ANALYSIS_GROUP-004 | Database error occurred while getting list of inconsistent treaties |
ANALYSIS_GROUP-005 | Invalid analysis group ID : %s |
ANALYSIS_GROUP-006 | You have entered a date using an invalid format %s. Enter dates as MM/DD/YYYY only. |
ANALYSIS_GROUP-007 | You have tried to group invalid results. You can group portfolio-level EP results, and you can group DLM groups. |
ANALYSIS_GROUP-008 | Enter a value greater than zero for the number of simulation periods for the final grouped PLT. |
ANALYSIS_GROUP-009 | You've selected too many results for grouping. Select a maximum of %d. |
ANALYSIS_GROUP-010 | Analyses details should not be empty. |
ANALYSIS_GROUP-011 | Select at least two results for grouping. |
ANALYSIS_GROUP-013 | We encountered an error during grouping. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
ANALYSIS_GROUP-014 | Simulation Set is required for grouping. If it's blank and you're grouping HD analyses, it's possible that you're grouping HD analyses run before Feb 24, 2021. Rerun the HD analyses and then group. |
ANALYSIS_GROUP-015 | Grouping is not supported for these analyses. Confirm that the analysis IDs are valid and that the engine types are not combinations of ALM and HD. See "Grouping Results" in the Moody's RMS Support Center. |
ANALYSIS_GROUP-016 | Grouping is not supported for these analyses. Confirm that the analysis IDs are valid and that the engine types are not combinations of ALM Multi Region and HD. See "Grouping Results" in the Moody's RMS Support Center. |
ANALYSIS_GROUP-017 | Sorry, Risk Modeler cannot create this group. Provide a 2-character peril code, a 2-character region code, and/or a 4-character model region code (such as NAEQ for North America earthquake) for each analysis to be included in the group. |
ANALYSIS_GROUP-018 | Analysis IDs cannot be null or empty. |
ANALYSIS_GROUP-019 | Force group type must be null or INGP. |
ANALYSIS_GROUP-020 | You cannot create a group that contains other groups if any of the member groups include HD results from an imported RDM. |
ANALYSIS_GROUP_TREATY
| Error Code | Message |
|---|---|
ANALYSIS_GROUP_TREATY-001 | We encountered an error during grouping. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
ANALYSIS_GROUP_TREATY-002 | Database error occurred while fetching the group PATE treaties for group IDs : %s. |
ANALYSIS_REGIONS
| Error Code | Message |
|---|---|
ANALYSIS_REGIONS-001 | We encountered an error while saving details for analysis regions %s. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
ANALYSIS_REGIONS-002 | We encountered an error while fetching analysis regions for analysis ID %d. |
ANALYSIS_REGIONS-003 | No rate scheme ID found for analysis ID %d. |
ANALYSIS_REGIONS-004 | We encountered an error while deleting analysis regions record for analysis ID : %d. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
| #`Analysis Regions HD | |
ANALYSIS_REGIONS_HD-001 | We encountered an error while saving details for HD analysis regions. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
ANALYSIS_REGIONS_HD-002 | We encountered an error while fetching HD analysis regions for analysis ID %d. |
ANALYTICS
| Error Code | Message |
|---|---|
ANALYTICS-000 | Sorry, looks like something might be wrong at our end. Try this again, and if it still doesn't work, contact Moody's RMS Support at support.rms.com. |
ANALYTICS-001 | No results available. account ID: %d not analyzed yet. |
ANALYTICS-500 | Database error occurred while loading event losses for Report ID: %d |
ANALYTICS-501 | Database error occurred while retrieving analysis details for Report ID: %d |
ANALYTICS-502 | Database error occurred while retrieving analysis report status for account ID: %d |
ANALYTICS-503 | Database error occurred while retrieving analysis details for data source: %s |
ANALYTICS-520 | Database error occurred while checking report count for job ID: %d |
ANALYTICS-521 | Database error occurred while getting EP metrics financial perspective analysis for analysis ID: %d |
ANALYTICS-522 | Database error occurred while getting data from Results store for analysis ID: %d |
ANALYTICS-523 | Database error occurred while getting Statistics for analysis for analysis ID: %d |
ANALYTICS-524 | Database error occurred while getting job ID for analysis for analysis ID: %d |
ANALYTICS-525 | Database error occurred while getting analysis id |
ANALYTICS-526 | Database error occurred while setting analysis status |
ANALYTICS-527 | Database error occurred while retrieving cedants list for report ID: %d |
ANALYTICS-528 | Database error occurred while retrieving treaties list for analysis ID: %d |
ANALYTICS-529 | Database error occurred while retrieving LOBs for treaty ID: %d |
ANALYTICS-530 | Database error occurred while retrieving perspectives for analysis ID: %d |
ANALYTICS-531 | Database error occurred while deleting Analysis ID: %d |
ANALYTICS-532 | Database error occurred while deleting Analyses ids: %s |
ANALYTICS-533 | Database error occurred while checking whether analysis ID: %d exists or not |
ANALYTICS-534 | We did not locate the analysis ID: %d. Either it doesn't exist or you don't have access to it. |
ANALYTICS-536 | Analysis ID: %d not found in Result Service. Please check that your requests specify a valid analysis ID. |
ANALYTICS-537 | Sorry, we can't calculate losses for the input you provided. |
ANALYTICS-538 | Peril code %s is not supported for the Analysis Summary report. Select a supported peril. |
ANALYTICS-539 | Database error occurred while retrieving analysis details list |
ANALYTICS-540 | Database error occurred while retrieving analysis details for Exposure type: %s with ID: %d |
ANALYTICS-541 | Sorry, we encountered an error trying to connect to our databases. Try again, and contact Moody's RMS Support if this still does not work. |
ANALYTICS-542 | Sorry, analysis ID %d is invalid for the Analysis Summary report. You can run the Analysis Summary report on portfolio-level DLM analyses only. |
ANALYTICS-543 | Database error occurred while getting analysis group info data for analysis IDs - %s. |
ANALYTICS-544 | Database error occurred while retrieving analysis details : %s. |
ANALYTICS-545 | Sorry, we encountered an error while fetching losses. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ANALYTICS-546 | We encountered an error retrieving treaty information. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
ANALYTICS-547 | Sorry, looks like this analysis did not generate losses for selected perspective. |
ANALYTICS-548 | Analysis ids: %s are invalid. Please check that your requests specify a valid analysis ID. |
ANALYTICS-549 | Sorry, analysis ID %d is invalid for the Analysis Summary report. You cannot run the report on DLM results that have been simulated to a PLT. |
ANALYTICS-550 | Sorry, date in analysis search query %s is invalid. Please try again with valid date. |
ANALYTICS-551 | Database error occurred while retrieving analysis engine details for analysis ID: %d. |
ANALYTICS-552 | Sorry, analysis ID %d is invalid for the Analysis Summary report. You cannot run the report on %s engine sub type. |
ANALYTICS-553 | Sorry, the provided ep type %s is invalid |
ANALYTICS-554 | Sorry, pagination operation not supported except policy |
ANALYTICS-555 | Sorry, filter operation for %s, %s not supported except policy |
ANALYTICS-556 | Sorry, %s param is only supported for exposure type policy |
ANALYTICS-557 | Sorry, only %s exposure type is supported when exposure ID is provided |
ANALYTICS-558 | Sorry, only perspective type %s is allowed for exposure type %s |
ANALYTICS-559 | Sorry, filter operation for %s is not supported for policy |
ANALYTICS-560 | Sorry, perspective code not supported for HD analysis. |
ANALYTICS-561 | Sorry, %s not supported when exposure type policy with ID specified or non-policy exposure types |
ANALYTICS-562 | Sorry, multiple perspective codes are only supported when Exposure Resource Type is POLICY and Exposure Resource ID is not provided |
AUTHORIZATION
| Error Code | Message |
|---|---|
AUTHORIZATION-401 | You tried to make this API call with an expired API token. Ask your platform administrator for a new API token and try again. |
AUTHORIZATION-501 | Error getting user information |
AUTHORIZATION-502 | Error creating user token |
BRANCH
| Error Code | Message |
|---|---|
BRANCH-401 | Database error occurred, branch does not exist |
BRANCH-402 | Database error occurred while loading branches, reason : %s |
BRANCH-404 | %s |
BRANCH-406 | %s |
BRANCH-409 | %s |
BRANCH-502 | Database error occurred while creating branch, reason : %s |
BRANCH-503 | Database error occurred while updating branch with ID: %d, reason : %s |
BRANCH-504 | Database error occurred while deleting branch with ID: %d, reason : %s |
BRANCH-505 | Database error occurred duplicate branch, branch already exists |
BRANCH-506 | Validation error, branch ID cannot be null or empty. |
BRANCH-508 | Validation error, branch, the name field has exceeded allowed length. |
BRANCH-509 | Database error occurred while checking if branch exists : reason %s |
BRANCH-510 | Database error occurred while checking if branch has reference in accgrp table : reason %s |
CE
Configuration errors.
| Error Code | Message |
|---|---|
CE-001 | Failed to build tenant key for: %s. Most likely tenant ID was missing from thread context or environment variable. |
CE-002 | Failed to find a value for required key: %s |
CE-003 | Failed to build a key for configuration level: %s, and key: %s. |
CE-004 | Sorry, we encountered an error while loading the configurations. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work |
CE-005 | Failed to build a cache for SQL configuration provider. |
CE-006 | Failed to build a cache for tenant configuration provider. |
CEDANT
| Error Code | Message |
|---|---|
CEDANT-401 | Database error occurred, cedant with ID: %s does not exists |
CEDANT-404 | %s |
CEDANT-406 | %s |
CEDANT-409 | %s |
CEDANT-501 | Database error occurred while loading cedants, reason : %s |
CEDANT-502 | Database error occurred while creating cedant, reason : %s |
CEDANT-503 | Database error occurred while updating cedant with ID: %s, reason : %s |
CEDANT-504 | %s |
CEDANT-505 | Error occurred while creating or updating cedant with name %s, ID %s. Cedant already exists with the same name or ID. |
CEDANT-506 | Validation error, cedant ID cannot be null or empty. |
CEDANT-507 | Validation error, cedant ID length has to be between 1 and 20. |
CEDANT-508 | Validation error, cedant, some of the String field has exceeded allowed length. |
CEDANT-509 | Database error occurred while checking if cedant ID: %d exists |
CEDANT-510 | Database error occurred while checking if cedant with ID: %d and Name: %s exists |
CLIENT
| Error Code | Message |
|---|---|
CLIENT-001 | Invalid identifier, %s : %s |
CLIENT-002 | Sorry, we could not get the requested data. The input '%s' (line %d, character %d) is not valid. See the Moody's RMS Support Center for help with query syntax. |
CLIENT-003 | Sorry, looks like there is a syntax error (line %d, character %d). See the "Bulk Edits-Advanced" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-005 | Sorry, we don't recognize the field '%s' |
CLIENT-006 | Unknown parser error: %s. (line %d, character %d) |
CLIENT-007 | Incompatible data type for %s, expected %s but got %s |
CLIENT-008 | Sorry, looks like '%s' (line %d, character %d) is an invalid command. Valid commands include EDIT, SET, and WHERE. See the "Bulk Edits-Advanced" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-009 | Sorry, this is an invalid argument for the EDIT command : '%s' . This should be policy or location (line %d, character %d). See the "Bulk Edits-Advanced" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-010 | Sorry, this is an invalid symbol : '%s' (line %d, character %d). |
CLIENT-011 | Sorry, looks like '%s' (line %d, character %d) is an invalid command. Valid options include WHERE or comma ','. See the "Bulk Edits-Advanced" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-012 | Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the SET command. See the "Bulk Edits-Advanced" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-013 | Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Bulk Edits-Advanced" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-014 | Sorry, you entered an invalid value for parameter '%s' |
CLIENT-015 | Sorry, this currency conversion request isn't valid. Try again, and contact Moody's RMS Support if this still does not work. |
CLIENT-016 | Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Account Search" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-017 | Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Portfolio Search" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-018 | Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "policy Search" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-019 | Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Step policy Search" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-020 | Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Aggregate Portfolio Search" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-021 | Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "treaty Search" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-022 | Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. |
CLIENT-023 | Sorry, looks like your query contains mismatched data type values. |
CLIENT-024 | Sorry, we could not get the requested data. The input '%s' (line %d, character %d) is not valid. See the "Bulk Edits-Advanced" topic in the Moody's RMS Support Center for help with query syntax. |
CLIENT-025 | Sorry, looks like there is no viable alternative at input '%s' (line %d, character %d). See the Moody's RMS Support Center for help with query syntax. |
CLIENT-026 | Sorry, looks like there is %s (line %d, character %d). See the Moody's RMS Support Center for help with query syntax. |
CLIENT-027 | Sorry, invalid filter. See the Moody's RMS Support Center for help with query syntax. |
CLIENT-028 | Sorry, sorting allowed on only one field. See the Moody's RMS Support Center for help with query syntax. |
CLIENT-029 | Sorry, invalid operator %s. See the Moody's RMS Support Center for help with query syntax. |
CLIENT-400 | Unable to read JSON |
CLIENT-402 | Sorry, we don't recognize the field %s. Check the field in the API reference on the Developer Portal. |
CLIENT-403 | Sorry, this is an invalid format for %s. Check the format in the API reference on the Developer Portal. |
CLIMATE-CHANGE
| Error Code | Message |
|---|---|
| CLIMATE-CHANGE-001 | To run an analysis, select at least 1 RCP scenario with 1 time horizon, or select the 2°C warming scenario. RCP scenarios are 2.6, 4.5, 6.0, 8.5. Time horizons are between the years of 2020 and 2100 in 5-year increments. |
| CLIMATE-CHANGE-002 | To run a climate change analysis on the selected results, %s input is required. |
| CLIMATE-CHANGE-003 | Sorry, you can run climate change analyses on individual, portfolio-EP analyses only. You cannot run a climate change analysis on DLM results that have been simulated to a PLT. |
| CLIMATE-CHANGE-004 | Climate change analyses are supported only for results from these models: %s. |
| CLIMATE-CHANGE-005 | Time horizon %d is invalid. Valid time horizons are between 2020 and 2100 in 5-year increments. |
| CLIMATE-CHANGE-006 | RCP scenario %f is invalid. Valid RCP scenarios are 2.6, 4.5, 6.0, 8.5. |
| CLIMATE-CHANGE-007 | Sorry, we encountered an error on our end while running the climate change analysis for analysis ID %d. Contact Support at [email protected]. |
| CLIMATE-CHANGE-008 | You cannot run a climate change analysis on HD results generated prior to Feb 24, 2021. Rerun the HD analysis, and then run the climate change analysis on the new results. |
| CLIMATE-CHANGE-009 | You have submitted an invalid climate conditioned view for %s analysis. To learn more about valid views for different peril models, see "Climate Change Model Analyses" in the Moody's RMS Support Center. |
| CLIMATE-CHANGE-010 | You have submitted an invalid reference rate scheme ID for %s analysis. To learn more about valid scheme IDs for different peril models, see "Climate Change Model Analyses" in the Moody's RMS Support Center. |
| CLIMATE-CHANGE-011 | Invalid argument for %s |
| CLIMATE-CHANGE-012 | Unable to retrieve metadata for %s |
| CLIMATE-CHANGE-013 | You cannot select the 2 degree C warming scenario for results from these models: %s. |
| CLIMATE-CHANGE-014 | Sorry, you can not perform climate change on %s engine sub type. |
| CLIMATE-CHANGE-015 | You cannot run a Climate Change Model analysis on HD results from an imported RDM. |
CONVERT-EVENT
| Error Code | Message |
|---|---|
CONVERT-EVENT-001 | Invalid argument for %s |
CONVERT-EVENT-002 | Unable to retrieve metadata for %s |
CONVERT-EVENT-003 | Sorry, you can convert event rates or apply loss adjustments on %s engine type(s) only. Enter a non-HD or non-simulated DLM analysis ID. |
CONVERT-EVENT-004 | Unsupported analysis type. Convert analysis event rate and loss is only supported on %s analysis type(s) |
CONVERT-EVENT-005 | Sorry, we encountered an error while submitting the convert analysis event rate and loss job. Try again, and contact Moody's RMS Support if this still does not work. |
CONVERT-EVENT-006 | Analysis ID %d already ran on event rate ID %d. |
CONVERT-EVENT-007 | Error when getting event loss adjustments: Unable to read the file header. |
CONVERT-EVENT-008 | Sorry, you must provide at least one event rate scheme ID or one event loss adjustment scheme ID to run convert event rate and loss. |
CONVERT-EVENT-009 | Unsupported exposure type. Convert event rate and loss is not supported for account analyses. |
CONVERT-EVENT-010 | Sorry, convert event rate and loss is not supported PLT groups. |
CONVERT-EVENT-011 | Sorry, the event rate scheme ID %d does not match the analysis peril region(s). |
CONVERT-EVENT-012 | Sorry, the loss adjustment scheme ID %d does not match the analysis peril region(s). |
CONVERT-EVENT-013 | Sorry, we encountered an error while reading the event loss adjustments. Try again, and contact Moody's RMS Support if this still does not work. |
CONVERT-EVENT-014 | Error while reading the event loss adjustments, non numeric values found. |
CONVERT-EVENT-015 | No event rate schemes found for analysis ID %d. |
CONVERT-EVENT-017 | Sorry, you can not perform convert event on %s engine sub type. |
CONVERT-RESULT-CURRENCY
| Error Code | Message |
|---|---|
| CONVERT-RESULT-CURRENCY-001 | Sorry, we encountered an error on our end while converting currency for analysis ID %d. Contact Support at [email protected]. |
| CONVERT-RESULT-CURRENCY-002 | Invalid argument for %s |
| CONVERT-RESULT-CURRENCY-003 | Unable to retrieve metadata for %s |
| CONVERT-RESULT-CURRENCY-004 | Sorry, some of the currency information is invalid. Check the currency scheme, currency code, vintage, and as-of date and try again. |
| CONVERT-RESULT-CURRENCY-005 | Sorry, the target currency is the same as the original currency. Check the target currency and try again. |
| CONVERT-RESULT-CURRENCY-006 | Sorry, the analysis ID for the currency conversion is not valid. Check the analysis ID and try again. |
| CONVERT-RESULT-CURRENCY-007 | You cannot convert the currency for this group because the group and/or the group’s underlying analyses need to be recalculated. Recalculate the group and/or the underlying analyses, and then try again to convert the currency. |
| CONVERT-RESULT-CURRENCY-008 | The currency scheme you selected does not contain the source currency %s. Please select the correct currency scheme to continue. |
| CONVERT-RESULT-CURRENCY-009 | The currency scheme you selected contains currency exchange rates that are not positive. Please select currency scheme with only positive exchange rates. |
CURRENCY
| Error Code | Message |
|---|---|
CURRENCY-400 | Validation error, Invalid domain name |
CURRENCY-401 | Validation error, Invalid tablespace |
CURRENCY-402 | Validation error, Invalid entity name |
CURRENCY-403 | Validation error, Invalid records |
CURRENCY-404 | Validation error, Invalid column name |
CURRENCY-405 | Validation error, Mandatory column missing |
CURRENCY-501 | Database error occurred while creating records in table |
CURRENCY-502 | An error occurred while validating currency |
CURRENCY-503 | Invalid exposure type passed for currency conversion |
CV
| Error Code | Message |
|---|---|
CV-001 | Invalid operator: '%s' |
CV-002 | Search feature not supported for field: '%s' |
DATABASE_MAINTENANCE
| Error Code | Message |
|---|---|
DATABASE_MAINTENANCE-001 | Database error occurred while updating database statistics. |
DATABASE_MAINTENANCE-002 | Database error occurred while updating EDM data version. |
DATABASE_STORE
| Error Code | Message |
|---|---|
DATABASE_STORE-400 | Invalid server ID provided: %d |
DATABASE_STORE-401 | Invalid SQL server version provided. |
DATABASE_STORE-404 | Data Bridge data source %s not found |
DATABASE_STORE-500 | An error occurred retrieving database store record |
DATABASE_STORE-501 | An error occurred inserting database store record |
DATABASE_STORE-502 | An error occurred updating database store record |
DATABASE_STORE-503 | An error occurred deleting database store records |
DATABASE_STORE-504 | Database Store task exceeded maximum wait time. |
DATA-BRIDGE
| Error Code | Message |
|---|---|
DATA-BRIDGE-501 | Sorry, we encountered an error submitting this Data Bridge job. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-502 | Sorry, we encountered an error loading this database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-503 | Sorry, we encountered an error deregistering this database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-401 | Invalid notification key %s |
DATA-BRIDGE-402 | %s not supported on Data Bridge databases |
DATA-BRIDGE-403 | The database %s that you tried to de-register does not exist. |
DATA-BRIDGE-404 | The database you tried to de-register has not been registered on the Data Bridge. |
DATA-BRIDGE-405 | Target Data Bridge database %s does not exist |
DATA-BRIDGE-550 | Sorry, we encountered an error creating this Data Bridge database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-551 | Sorry, we encountered an error deleting this Data Bridge database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-552 | Sorry, we encountered an error creating this Data Bridge sign-in. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-553 | Sorry, we encountered an error setting permissions on this Data Bridge database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-554 | Sorry, we encountered an error importing this Data Bridge database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-555 | Sorry, we encountered an error exporting this Data Bridge database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-556 | Sorry, we encountered an error trying to get details for data bridge database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-557 | Sorry, we failed to process this request. %s. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
DATA-BRIDGE-558 | Failed to get job: %s status |
DATA-BRIDGE-559 | Databridge task %s not found |
DATA-BRIDGE-560 | Failed to register databridge EDM: %s |
DATA-BRIDGE-561 | The server type for server ID %d is not supported for Data Bridge. Please provide a valid Data Bridge server ID. |
DATA-BRIDGE-562 | Sort by databaseId and serverId is currently not supported for Data Bridge. |
DATA-BRIDGE-563 | Exposure already exists for exposureSet %s. Cannot register multiple exposures under the same exposureSet. |
DATA-BRIDGE-564 | Error occurred while registering exposure under exposureSet with ID %d |
DATA-BRIDGE-565 | Data Bridge Database with serverId: %d and databaseId: %d not found. Check the database details and try again. |
DATA-BRIDGE-566 | The query provided is not supported for Data Bridge databaseType. Please provide a valid query. |
DATA-BRIDGE-567 | The query provided contains unsupported operators for Data Bridge. Please provide a valid query. |
DBATTRIBUTE
| Error Code | Message |
|---|---|
DBATTRIBUTE-001 | Error occurred while fetching the db attribute : %s |
DBM
Database metrics
| Error Code | Message |
|---|---|
DBM-502 | Database error occurred while updating metrics for database with ID: %d |
DBM-503 | Database error occurred while calculating metrics for database |
DBM-504 | Database error occurred while updating metrics for database |
DBM-505 | Database error occurred while calculating the size of EDMs |
DBM-506 | Database error occurred while checking if the metrics exist |
DBM-507 | Database error occurred while getting metrics for database with ID: %d |
DBM-508 | Database error occurred while deleting metrics for database |
ENT
Entitlements errors.
| Error Code | Message |
|---|---|
| ENT-001 | Sorry, this could be an error on our end. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
| ENT-002 | Sorry, this could be an error on our end. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
| ENT-003 | You cannot run this analysis because you do not have a current model license. Check with your Risk Intelligence administrator to find out which models are licensed by your organization. |
| ENT-004 | You cannot run an analysis on the following model(s) because you do not license them: Engine: %s, Peril: %s, Region: %s, Sub-region(s): %s. Check with your Risk Intelligence administrator to find out which models are licensed by your organization. |
| ENT-005 | You cannot run an analysis on the following model(s) because you do not license them: Engine: %s, Insurance Type: Workers Comp, Peril: %s, Region: %s, Sub-region(s): %s. Check with your Risk Intelligence administrator to find out which models are licensed by your organization. |
| ENT-006 | You cannot run an analysis on the following model(s) because you do not license them: Engine: %s, Peril: %s, Vulnerability Curves: Vulnerability Set 101, Region: %s, Sub-region(s): %s. Check with your Risk Intelligence administrator to find out which models are licensed by your organization. |
| ENT-007 | You cannot run an %s analysis on one or more of the countries you have selected because you do not license them. Check with your Risk Intelligence administrator to find out which ALM models you license. |
| ENT-008 | You cannot run a Climate Change Model analysis on the following model region(s) because you do not license them: Engine: %s, Peril: %s, Region: %s, Sub-region(s): %s. Check with your Risk Intelligence administrator to find out which models are licensed by your organization. |
| ENT-009 | Sorry, this could be an error on our end. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
| ENT-010 | You cannot run an analysis on the following model(s) because you do not license them: Engine: %s, Peril: %s, Region: %s, Sub-region(s): %s, Vulnerability Curves: %s. Check with your Risk Intelligence administrator to find out which models are licensed by your organization. |
EXTRACT-ELT
| Error Code | Message |
|---|---|
| EXTRACT-ELT-001 | Invalid argument for %s |
DATE
| Error Code | Message |
|---|---|
DATE-001 | Invalid date. The valid range of dates is from 01/01/1753 to 12/31/9999 |
DATE-002 | %s |
DLM_SERVICE
| Error Code | Message |
|---|---|
DLM_SERVICE-001 | Sorry, we encountered an error while running the DLM analysis job. Try again, and contact Moody's RMS Support if this still does not work. |
DLM_SERVICE-002 | Sorry, we encountered an error while loading the model profile ID %d for this DLM analysis. Try again, and contact Moody's RMS Support if this still does not work. |
DLM_SERVICE-003 | Sorry, we encountered an error while loading the analysis currency %s for this DLM analysis. Try again, and contact Moody's RMS Support if this still does not work. |
DLM_SERVICE-004 | Sorry, the model version %s for this DLM analysis is invalid. Specify a valid version and try again. |
DLM_SERVICE-005 | Sorry, the currency vintage %s with the as-of date %s is invalid. Specify a valid vintage and try again. |
DLM_SERVICE-006 | Sorry, the output profile is invalid or missing. Specify a valid output profile and try again. |
DLM_SERVICE-007 | Model Region with code %s and isHd %s is not found |
DLM_SERVICE-008 | Invalid model profile - footprintId missing or invalid |
DLM_SERVICE-009 | Footprint Event %s is not found |
DLM_SERVICE-010 | Sorry, the output profile ID %d for this analysis is invalid. Specify a valid output profile and try again. |
DLM_SERVICE-011 | We encountered an error retrieving the output profile with ID %d. Try again. If this still doesn't work, contact Moody's RMS Support. |
DLM_SERVICE-012 | Sorry, climate change analysis cannot be run at %s level. Use a portfolio level exposure and try again. |
DLM_SERVICE-013 | Sorry, climate change analysis is not supported for %s analysis type. Use EP or Simulated type and try again. |
DLM_SERVICE-014 | Sorry, climate change analysis is not supported for dlm engine version %s. Select dlm version 22 or higher and try again. |
DLM_SERVICE-015 | Sorry, climate change analysis is not supported for peril %s. Use windstorm peril and try again. |
DLM_SERVICE-016 | Sorry, climate change analysis is not supported for region %s. Select region %s and try again. |
DLM_SERVICE-017 | Sorry, we encountered an error while loading the currency vintage %s with the as-of date %s is invalid. Try again. If this still doesn't work, contact Moody's RMS Support. |
DLM_SERVICE-018 | Sorry, the event rate scheme ID %d for this DLM analysis is invalid. Specify a valid event rate scheme ID and try again. |
DLM_SERVICE-019 | Sorry, DLM or HD analysis is not supported for analysis type %s and exposure type %s in %s. Use EP type and try again. |
DLM_SERVICE-020 | This footprint is no longer valid. An updated version of this footprint may be able to be run by creating a new model profile for this analysis. |
DLM_SERVICE-021 | Sorry, you have provided invalid settings with model type %s. |
DOM
| Error Code | Message |
|---|---|
DOM-001 | Domain data not found for domain %s, tablespace %s, entity %s |
DOM-003 | Invalid format for entity path %s |
DOM-004 | Scalar domain data for domain %s, tablespace %s, entity %s found %d values |
DOM-005 | Invalid input data for the parameter : %s |
DOM-006 | Sorry, we're having some trouble on our end. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-007 | Sorry, we encountered parsing error. Try different input for parameter: %s |
DOM-008 | Sorry, we encountered an error while retrieving peril and loss type for coverage %s. See the "Fields for Advanced Bulk Edits" topic in the Moody's RMS Support Center for help with query syntax. |
DOM-500 | Sorry, we encountered an error while retrieving domain names. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-501 | Sorry, we encountered an error while retrieving tablespace names for domain %s. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-502 | Sorry, we encountered an error while retrieving entity names for domain %s and tablespace %s. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-503 | Sorry, we encountered an error while retrieving entity attributes for domain %s, tablespace %s, and entity %s. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-504 | Sorry, we encountered an error while retrieving entity values for domain %s, tablespace %s, and entity %s. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-505 | Sorry, we encountered an error while retrieving secondary modifiers for domain %s, tablespace %s, and entity %s. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-506 | Sorry, we encountered an error while retrieving construction details for country %s, construction class scheme %s, and construction class %s. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-507 | Sorry, we encountered an error while retrieving occupancy details for country %s, occupancy type scheme %s, and occupancy type %s. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-509 | Sorry, we encountered an error while retrieving hazards for domain %s, tablespace %s, and entity %s. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-510 | Sorry, we encountered an error while retrieving country resolution values for country code: '%s', resolution type: '%s'. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-511 | Sorry, we encountered an error while retrieving country line of business types for country code: '%s'. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-512 | Sorry, we encountered an error while retrieving resolution column mappings. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-513 | Sorry, there is a mismatch between country code: '%s' and resolution: '%s'. |
DOM-514 | Sorry, we're having some trouble on our end. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-515 | Sorry, we encountered an error while retrieving climate-conditioned-views for regionperil %s and enginetype %s. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-516 | Sorry, we encountered an error while retrieving reference-rate-scheme for rate-scheme-id %d. Try again, and contact Moody's RMS Support if this still does not work. |
DOM-517 | Sorry, we encountered an error while retrieving analysis regions for peril %s. Try again, and contact Moody's RMS Support at [email protected]if this still does not work. |
DOM-518 | Sorry, we can't find results for the entries you provided: domain: '%s', tablespace: '%s', entity: '%s'. |
DS
| Error Code | Message |
|---|---|
DS-001 | We did not locate the database %s. Check the database name. |
DS-002 | Sorry, looks like you do not have access permission for the %s database. |
DS-003 | The database cannot be empty. Enter a valid database name. |
DS-004 | job paused. The database server has reached the maximum number of stored databases. Delete one or more EDMs from this server to resume the job. |
DS-401 | Invalid instance namespace: %s |
DS-402 | Invalid instance status: %s |
DS-403 | Specified server %s is not registered. |
DS-404 | Unable to process MDF import into RDS database instances. |
DS-405 | The selected server does not support MDF imports. |
DS-406 | The selected server does not support BAK imports. |
DS-408 | You cannot load (register) a database that's not a Data Bridge EDM. |
DS-409 | You cannot export to an existing RDM database. This is only supported for Data Bridge. |
DS-410 | Data Bridge Database %s not found. Check the database name and try again. |
DS-411 | Database error due to missing table. |
DS-412 | The detachOnly option can be "true" only if the format is MDF, the operation is DOWNLOAD_EDM, and the SQL Server version is 2019. |
DS-413 | Exporting a database in MDF format requires the option detachOnly to be true when the database size is greater than 100 GB. |
DS-500 | Sorry, we encountered an error trying to retrieve the database. Try again. |
DS-501 | Sorry, we encountered an error while checking the access permissions for this database. Try again. |
DS-502 | Database error occurred while validating data source %s |
DS-503 | Database error occurred while retrieving data source: %s for account ID: %d |
DS-504 | Error occurred starting the database connection pool for data source: %s |
DS-505 | Error occurred stopping the database connection pool for data source: %s |
DS-506 | Database error occurred while creating data source: %s |
DS-507 | A database with the name %s already exists. Enter a different name. |
DS-508 | Database error occurred while updating data source: '%s' |
DS-509 | Database error occurred while deleting data source: '%s' |
DS-510 | Database error occurred while creating backup for data source: '%s' |
DS-511 | Sorry, you tried something invalid. Enter a valid datastore operation. |
DS-512 | You have reached the maximum number (%s) of EDMs allowed for your organization. Delete an EDM before you create or upload a new one. |
DS-513 | Sorry, we encountered an error creating this database. Try again, and contact Moody's RMS Support if this still does not work. |
DS-514 | Sorry, this could be an error on our end. Try again, and contact Moody's RMS Support if this still does not work. |
DS-515 | Sorry, we encountered an error triggering this job. Something might be missing from the job input. Try again, and contact Moody's RMS Support if this still does not work. |
DS-516 | The database %s is being upgraded. Wait a few minutes and try again. |
DS-517 | Sorry, we encountered an error trying to retrieve database information for tenant %s. Try again. |
DS-519 | Sorry, we encountered an error reading database information. Try again, and contact Moody's RMS Support if this still does not work. |
DS-520 | Sorry, we encountered an error reading database system information. Try again, and contact Moody's RMS Support if this still does not work. |
DS-521 | job paused. This job type is already running on the maximum number of databases. This job will automatically resume once the other jobs in the queue are complete. |
DS-522 | Sorry, we can't find database %s. Either it doesn't exist or you don't have access to it. |
DS-523 | Could not parse URL, reason %s |
DS-524 | Sorry, the only allowed version for upgrade is 22 |
DS-525 | Invalid sql version provided |
DS-526 | We did not locate the database for exposureId: %d. Either it doesn't exist or you don't have access to it. |
DS-527 | The exposureId %s provided is invalid. Please enter a valid exposureId. |
DS-528 | Error occurred while creating exposure under exposureSet with ID %d |
DS-529 | Sorry, file format %s is not supported for download EDM. Supported file formats are BAK and MDF |
EDM
| Error Code | Message |
|---|---|
EDM-501 | Database error occurred while loading EDMs |
EDM-502 | Database error occurred while creating EDM with name: %s |
EDM-505 | Database error occurred while creating EDM with name %s already exists |
EDM-506 | Database error occurred while creating a backup for EDM |
EDM-507 | Database error occurred while creating a backup for EDM not found |
EDM-509 | Database error occurred while querying for list of EDMs |
EDM-510 | Sorry, you do not have access permissions to any groups of tenant %s. Check with your Administrator about getting access. |
EDM_SYNC
| Error Code | Message |
|---|---|
EDM_SYNC-001 | Failed to sync with Analytics Gateway |
EDM_SYNC-002 | Failed to sync with Analytics Gateway, Response: %s |
EDM_SYNC-003 | Received an invalid message from Analytics Gateway, response status, msg: %d %s |
ENGINE
| Error Code | Message |
|---|---|
ENGINE-001 | We encountered an error trying to run the job. Try again. If this still does not work, contact Moody's RMS Support. |
ENGINE-002 | We encountered an error trying to run the job. job inputs aren't valid |
ENGINE-003 | only CopyAccount, DeleteAccount or ConvertCurrency operation is supported |
ENGINE-004 | Record not found in import store database. |
ENGINE-005 | Database with data source name : '%s', already exists |
ENGINE-006 | Sorry, we failed to process this request since the database limit has been exceeded. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-007 | Data source %s not found |
ENGINE-008 | Database error occurred while creating backup for data source: '%s' |
ENGINE-009 | Database error occurred while deleting data source: '%s' |
ENGINE-010 | Database error occurred while creating data source: %s |
ENGINE-011 | Database error occurred while retrieving data source: %s |
ENGINE-012 | RDM database creation failed |
ENGINE-013 | Validations failed |
ENGINE-014 | We encountered an error trying to run the job. Try again. If this still does not work, contact Moody's RMS Support. |
ENGINE-015 | Unsupported Exposure Type: %s |
ENGINE-016 | %s backup status cannot be retrieved |
ENGINE-017 | %s back up cannot be created and failed with exception : %s |
ENGINE-018 | LI job got canceled |
ENGINE-019 | MRI job failed with validation errors. Please see jobs' details for validation log file. |
ENGINE-020 | No job ID found for analysis ID : %s |
ENGINE-021 | No results are available for analysis %s included the download. Remove this analysis from the download and try again. |
ENGINE-022 | DB name : %s, %s failed! |
ENGINE-023 | rdsHost cannot be null or empty |
ENGINE-024 | rdsPort cannot be null or empty |
ENGINE-025 | rdsUser cannot be null or empty |
ENGINE-026 | rdsPwd cannot be null or empty |
ENGINE-027 | s3AccessKey cannot be null or empty |
ENGINE-028 | s3Secret cannot be null or empty |
ENGINE-029 | dbRdmKey cannot be null or empty |
ENGINE-030 | s3bucket cannot be null or empty |
ENGINE-031 | s3DownLoadBucket cannot be null or empty |
ENGINE-032 | tenantId cannot be null or empty |
ENGINE-033 | analysisId cannot be null or empty |
ENGINE-034 | userId cannot be null or empty |
ENGINE-035 | workflowId cannot be null or empty |
ENGINE-036 | workflowServiceUrl cannot be null or empty |
ENGINE-037 | expirationHours cannot be null or empty |
ENGINE-038 | edmBucketName cannot be null or empty |
ENGINE-039 | BCP Batch size cannot be null or empty and must be numeric |
ENGINE-040 | BCP timeout cannot be null or empty and must be numeric |
ENGINE-041 | Detail losses export value cannot be null or empty and must be boolean |
ENGINE-042 | Sorry, the following event rate scheme(s) are invalid: %s See Event Rates in the Risk Modeler Model Composer for a list of valid IDs. |
ENGINE-043 | The request %s |
ENGINE-044 | Error when getting event rates: Datastore call failed |
ENGINE-045 | Error when getting event rates |
ENGINE-046 | Error when getting event rates: Unable to read the rate headers. |
ENGINE-047 | LI-BULK: Geocoding job %s failed |
ENGINE-048 | server returned statusCode: %s |
ENGINE-049 | only CopyPortfolio, DeletePortfolio or ConvertCurrency operation is supported |
ENGINE-050 | Sorry, looks like something might be wrong at our end. Try this again, and if it still doesn't work, contact Moody's RMS Support at support.rms.com. |
ENGINE-051 | Template file does not exist |
ENGINE-052 | dlmjobId cannot be null or empty |
ENGINE-053 | authToken cannot be null or empty |
ENGINE-054 | serviceName cannot be null or empty |
ENGINE-055 | Exposure isn't valid. %s |
ENGINE-056 | SQL exception. |
ENGINE-057 | HPC exception. %s |
ENGINE-058 | only ConvertCurrency operation is supported |
ENGINE-059 | Sorry, we were unable to upgrade this EDM. It could be an error on our end or a network connectivity issue. Try again, and if this still doesn't work, contact Moody's RMS Support at [email protected]. |
ENGINE-060 | Exception occurred while copy account operation |
ENGINE-061 | Exception occurred while delete account operation |
ENGINE-062 | Exception occurred while convert currency operation |
ENGINE-063 | Database error occurred while calculating Portfolio and its accounts metrics |
ENGINE-064 | Database error occurred while calculating metrics for all Portfolios and Accounts in EDM |
ENGINE-065 | Detail stats export value cannot be null or empty and must be boolean |
ENGINE-066 | Error occurred while copying portfolio |
ENGINE-067 | Error occurred while deleting portfolio |
ENGINE-068 | Failed to get analytics details |
ENGINE-069 | Error when dropping database |
ENGINE-070 | Failed to Update DB Attribute table |
ENGINE-071 | Failed to make DB INFO entries for EDM |
ENGINE-072 | Failed to acquire position in task queue |
ENGINE-073 | Failed to create empty EDM: %s |
ENGINE-074 | Failed load parquet files from S3 |
ENGINE-075 | Failed recreate RDM indices |
ENGINE-076 | Failed to update RDM seed IDs |
ENGINE-077 | Failed to create RDM backup |
ENGINE-078 | Failed to generate download link for RDM |
ENGINE-079 | Layer info parse failed |
ENGINE-081 | Failed to drop indicies during download RDM |
ENGINE-082 | Failed to delete webDb entries |
ENGINE-084 | Failed to create webDb entries |
ENGINE-085 | Failed to create DbInfo entries |
ENGINE-086 | Failed to create db metrics entries |
ENGINE-087 | Failed to create groupDb detail entries |
ENGINE-088 | Failed to detach DataSource |
ENGINE-089 | Failed to get ImportSource |
ENGINE-090 | Failed to get taskID for restore process |
ENGINE-091 | Failed to upload EDM |
ENGINE-092 | Failed to update import source |
ENGINE-093 | Failed to delete groupDbDetail table |
ENGINE-094 | Failed to delete the dbInfo table |
ENGINE-095 | Failed to copy EDM |
ENGINE-096 | Failed to get EDM name from database |
ENGINE-097 | IO exception while attempting to get geohaz inputs |
ENGINE-098 | No job ID found for analysis ID %s |
ENGINE-099 | Load database connection properties error |
ENGINE-100 | Failed to retrieve analysis name |
ENGINE-101 | Failed while rebaselining the database |
ENGINE-102 | Failed to create DB type %s |
ENGINE-103 | Failed to initialize datasource |
ENGINE-104 | Invalid engine input |
ENGINE-105 | failed to read exposure from job input |
ENGINE-106 | Too many treaty priority numbers: %s > Max %s |
ENGINE-107 | Unable to save financial perspective |
ENGINE-108 | Unable to save treaties |
ENGINE-109 | Unable to load treaties |
ENGINE-110 | Unable to get analysis status |
ENGINE-111 | Unable to get analysisId for jobId: %s |
ENGINE-112 | Unable to get analysis for ID: %s |
ENGINE-113 | Unable to get jobId for analysis ID: %s |
ENGINE-114 | Unable to copy analysis record for analysis ID: %s |
ENGINE-115 | Unable to get event loss |
ENGINE-116 | Unable to get treaty info |
ENGINE-117 | Unable to load event losses for perspective: %s |
ENGINE-118 | Unable to load losses for perspective: %s |
ENGINE-119 | EP Type needed |
ENGINE-120 | treaty information not set: %s |
ENGINE-121 | Analysis isn't of type EP. No EP calculation performed. |
ENGINE-126 | No event losses found |
ENGINE-127 | Incomplete input! The statistics calculator was NOT set with an %s curve, needed to calculate the statistics. Perspective: %s |
ENGINE-130 | Unable to load financial perspective |
ENGINE-131 | EP losses calculation Failed |
ENGINE-132 | Unable to generate EP curves for treaty: %s |
ENGINE-133 | Unable to create group |
ENGINE-134 | Unable to add analysis events |
ENGINE-135 | Invalid analysis to add |
ENGINE-136 | Failed to delete results |
ENGINE-137 | Unable to write analysis event |
ENGINE-138 | Failed to delete group results |
ENGINE-139 | Failed to regroup treaties |
ENGINE-140 | Group already contains analysis %s |
ENGINE-141 | Group contains a circular hierarchy due to group ID %s |
ENGINE-142 | Duplicate analysis ID found: %s |
ENGINE-143 | Regional grouping engine failed |
ENGINE-144 | Failed to get event ID count |
ENGINE-145 | Failed to convert currency |
ENGINE-146 | Failed to get scheme count |
ENGINE-147 | Analysis or currency not found |
ENGINE-148 | Analysis region count not found |
ENGINE-149 | Failed to get Analysis count |
ENGINE-150 | Missing mapping for perspcode: %s |
ENGINE-151 | Missing mapping for analysis ID: %s |
ENGINE-152 | Unable to find %s in ExposureIDOrderTable |
ENGINE-153 | Unable to get group exposure list |
ENGINE-154 | Failed to group regional losses |
ENGINE-155 | AnalysisId %s is not in any group list |
ENGINE-156 | Failed to get group loss for perspective |
ENGINE-157 | treaty %s not found in rdm pate edit list. |
ENGINE-158 | treaty loss calculation failed |
ENGINE-159 | Failed to get treaty: %s |
ENGINE-160 | Unsupported analysis mode: %s. Valid modes are Expected and Distributed |
ENGINE-161 | DLM parent analysis ID was not set |
ENGINE-162 | S3 bucket for jobId:%s did not become consistent after %s ms |
ENGINE-163 | ALM analysis missing exposures |
ENGINE-164 | ALM analysis missing profiles |
ENGINE-165 | Sorry, it looks like something might be wrong at our end. The job failed to submit to HPC. Contact Support at [email protected] for help resolving this issue. |
ENGINE-166 | Failed to transform job to HPC |
ENGINE-167 | Failed S3 write |
ENGINE-168 | Unable to create database. DB Name conflict |
ENGINE-169 | Failed to create download link |
ENGINE-170 | Failed to create retention entry |
ENGINE-171 | Failed to create HPC job |
ENGINE-172 | Failed to create HPC task: %s |
ENGINE-173 | Failed to set up HPC ENV |
ENGINE-174 | S3 file read failed |
ENGINE-175 | Unable to get Rlaas Input |
ENGINE-176 | EDM creation failed |
ENGINE-177 | Invalid analysis ID filter |
ENGINE-178 | Database quota exceeded. Unable to create new databases while at or above quota. |
ENGINE-179 | Sorry, it looks like something went wrong on our end. Try your analysis again. If this still doesn't work, contact Moody's RMS Support. |
ENGINE-180 | Error occurred during transforming the registration output |
ENGINE-181 | Exception occurred while bulk edit operation |
ENGINE-182 | Exception occurred while fetching metadata from results service |
ENGINE-183 | Exception occurred while querying results service |
ENGINE-184 | Exception occurred while fetching HD EP via results service : %s |
ENGINE-185 | Exception occurred while fetching HD Statistics via results service : %s |
ENGINE-186 | RL Geohaz job %s failed |
ENGINE-187 | Exception occurred while fetching HD non-EP results via results service : %s |
ENGINE-188 | Exception occurred while fetching HD PLT results via results service : %s |
ENGINE-189 | Invalid database store type |
ENGINE-191 | %s doesn't match %s. Failed to process the file. |
ENGINE-192 | Failed to check if the uploaded DB corresponds with the DB Upload type operation. Please ensure the rmsver table exists. |
ENGINE-193 | Exception occurred while downloading csv via results-service |
ENGINE-194 | job cancelled |
ENGINE-195 | job failed. %s |
ENGINE-197 | job failed. Infrastructure issue |
ENGINE-198 | Failed to process GEOHAZ for given Exposure Criteria. %s |
ENGINE-199 | Failed to update the copy_edm_destination table for ID. %s |
ENGINE-200 | Recreate indexes value cannot be null or empty and must be boolean |
ENGINE-201 | Failed to refresh analysis results status: %d. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-202 | Failed to refresh results for analysis. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-203 | Sorry, we encountered an error downloading this database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-204 | Sorry, we encountered an error with this hazard retrieval. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-205 | Failed register result table, errorCode: %s error: %s |
ENGINE-206 | job failed. Invalid engine input. Reason: %s |
ENGINE-207 | Failed to restore databases to Data Bridge server |
ENGINE-208 | Invalid DB key |
ENGINE-209 | Failed to track the status of rds task |
ENGINE-210 | DB name : %s, %s failed! Sorry, it looks like you tried to upload a database created with a SQL Server version we do not support. See "EDM and RDM Upload" in the Moody's RMS Support Center for a list of supported SQL Server versions. |
ENGINE-211 | Sorry, we encountered an error while downloading this database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-212 | Sorry, we encountered an error migrating the data bridge EDM. Try again, and contact Moody's RMS Support if this still doesn't work. |
ENGINE-213 | Sorry, we encountered an unknown error trying to de-register this database. Try again, and contact Moody's RMS Support if this still doesn't work. |
ENGINE-214 | Sorry, we encountered an error deleting this aggregate portfolio. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-215 | Sorry, looks like this is an invalid operation for an aggregate portfolio. |
ENGINE-216 | Sorry, we encountered an error importing this aggregate portfolio. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-217 | Sorry, we encountered an error copying this aggregate portfolio. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-218 | Looks like you didn't provide any files for import. |
ENGINE-219 | Looks like there's something wrong with the input file format. Check that you're using a TXT or CSV file. |
ENGINE-220 | Sorry, we encountered an error exporting this data. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-221 | Sorry, we encountered an error exporting this data. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-222 | Target RDM database %s does not exist |
ENGINE-224 | Sorry, we encountered an error while processing the input data for loss registration. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-225 | Sorry, we encountered an error while running this HD analysis. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-226 | Sorry, looks like there's not enough space. Delete some databases from your local storage or Data Bridge server and try again |
ENGINE-227 | Sorry, the %s %s failed to upload. The BAK file might not be a valid SQL backup file or might be corrupted. Recreate the BAK file with a supported SQL version and try the upload again. See "EDM and RDM Upload" in the Moody's RMS Support Center for a list of supported SQL Server versions. |
ENGINE-228 | Failed to restore the %s %s from backup file. |
ENGINE-229 | Sorry, the %1$s failed to upload because the %1$s version %2$d is not supported. Upgrade or downgrade the %1$s to a supported version and try the upload again. See "EDM and RDM Upload" in the Moody's RMS Support Center for a list of supported %1$s versions. |
ENGINE-230 | Sorry, the EDM failed to upload because the EDM version is missing. See "EDM and RDM Upload" in the Moody's RMS Support Center for a list of supported EDM versions. |
ENGINE-231 | Failed to read the valid EDM versions. |
ENGINE-232 | Sorry, we encountered an error while geocoding. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-233 | Sorry, we encountered an error while running this Climate Change analysis. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-234 | No climate change scenario was found for this combination of inputs. Check your inputs and try again, or contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-235 | Sorry, we can't perform this operation because the database is read-only. We recommend changing source database to read-write then creating a backup and repeating the upload. |
ENGINE-236 | Unrecognized engine version: %s |
ENGINE-237 | Failed table: %s error code: %s error message: %s |
ENGINE-238 | workflowId should not be null |
ENGINE-239 | Loss Transformations workflow failed with status %s. Workflow URL: %s |
ENGINE-240 | Sorry, we encountered an error while running this HD Grouping analysis. To resolve this issue, Contact Support at [email protected]. |
ENGINE-241 | Currency scheme must contain USD currency code. |
ENGINE-242 | Sorry, the database backup failed. The database doesn't exist. |
ENGINE-243 | Failed to restore the %s %s from backup file, as either the backup file is corrupt or the source database of the backup file is corrupt. Please check the source database and backup file and re-upload. |
ENGINE-244 | Failed to truncate RDM table %s for write retry. |
ENGINE-245 | Failed to delete duplicate RDM rate scheme entries before copying data. |
ENGINE-246 | Sorry, we encountered an error on our end while converting currency. Contact Support at [email protected]. |
ENGINE-247 | Failed to send notification. |
ENGINE-248 | Sorry, we encountered an error while running this Simulate Losses analysis. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-249 | Sorry, we encountered an error on our end while checking duplicate records. Contact Support at [email protected]. |
ENGINE-250 | Failed to upload rdm due to duplicate records found in %s. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-251 | Sorry, we failed to %s EDM with data source name : '%s' since it doesn't exist |
ENGINE-252 | Sorry, we encountered an error while running this HD ALM analysis. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-253 | Sorry, we encountered an error while running this HD PATE analysis. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-254 | treaty ID %d is not valid for post-analysis treaty editing. You can add, edit or delete only group level treaties for an HD analysis. |
ENGINE-255 | userName cannot be null or empty |
ENGINE-256 | You have entered an event rate scheme ID that does not have a corresponding simulation set. See the Simulation Set table in Risk Modeler Reference Data for a list of valid simulation sets. |
ENGINE-257 | You have entered an invalid event rate scheme ID for the peril model region. See Event Rates in the Risk Modeler Model Composer for a list of valid IDs. |
ENGINE-258 | %s |
ENGINE-259 | Sorry, marginal impact analysis cannot run on exposures with step policies. |
ENGINE-260 | Exposure set %s already in use with another exposure or result data. Please check and try again. |
ENGINE-261 | Result registration failed. |
ENGINE-262 | Sorry, we encountered an error while loading the treaty metadata for HD analysis. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-263 | Sorry, we encountered an error while retrieving the PLT metadata for HD analysis from the database. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-264 | This job could not be completed because data source %s does not exist or this user does not have access to it. |
ENGINE-265 | Sorry, we encountered an error while writing the %s for HD analysis %s to S3. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
ENGINE-266 | Sorry, we failed to upload your EDM. There was an error while upgrading the database. |
ENGINE-267 | You provided an invalid model version %s. For a list of valid model versions, see the Peril Model List in the Risk Modeler Moody's RMS Support Center or on the Moody's RMS Support Center. |
ENGINE-268 | Failed to restore the %s %s from backup file, as %s |
ENGINE-269 | PATE input list is either missing or empty |
ENGINE-270 | Error occurred while parsing PATE input list json |
ENGINE
DLM errors.
| Error Code | Message |
|---|---|
| ENGINE-400 | Exposure failed to process. No valid locations for the peril region. |
| ENGINE-401 | Exposure failed to process. No valid location coverages for peril region. |
| ENGINE-402 | Exposure failed to process. Too many lines of business, limit is 255. |
| ENGINE-403 | Exposure failed to process. Exposure requires missing currency: %s. |
| ENGINE-404 | Exposure failed to process. Exposure item not found. |
| ENGINE-405 | Exposure failed to process. Try again, and contact Moody's RMS Support if this still does not work. |
| ENGINE-406 | No results' metadata found for analysis ID %s |
| ENGINE-407 | Batch data validation failed |
| ENGINE-408 | Unable to load currencies. |
| ENGINE-409 | We have exhausted all unique IDs for an EDM table. Please use another EDM to import data. |
EVENTINFO
| Error Code | Message |
|---|---|
| EVENTINFO-401 | Database error occurred, rate scheme does not exists |
| EVENTINFO-502 | Database error occurred while saving rate scheme for database with ID: %d |
EXPORT
| Error Code | Message |
|---|---|
EXPORT-001 | There was an unexpected issue that occurred while moving the EDMs. |
EXPORT-002 | To export locations, policies, treaties, peril details, and/or reinsurance, you must also export accounts. |
EXPORT-003 | To export reinsurance and/or peril details, you must also export locations. |
EXPORT-004 | To export data to an EDM, you must specify the source EDM. |
EXPORT-005 | To export data to an EDM, you must specify the destination EDM. |
EXPORT-006 | The source EDM does not exist. Please choose a valid source EDM and try again. |
EXPORT-007 | The destination EDM does not exist. Please choose a valid destination EDM and try again. |
EXPORT-008 | To export data to an EDM, you must provide at least one exposure ID to export. |
EXPORT-009 | Error occurred while downloading the results for ID %d |
EXPORT-010 | The export format is missing. Specify the export format as CSV or PARQUET. |
EXPORT-011 | The loss metrics, financial perspectives, output levels, and/or hazard/damage/uncertainty output are missing from this export. Include one or more of these selections and try again. |
EXPORT-012 | The export format is invalid. Specify the export format as CSV or PARQUET. |
EXPORT-013 | This export type is not supported because you are either exporting between Risk Modeler database and Data Bridge database, or between two different Data Bridge servers. You can either export from any Risk Modeler database to another Risk Modeler database, or export between same Data Bridge servers. |
EXPORT-014 | Sorry, download to CSV or Parquet are not supported. |
EXPORT-015 | Sorry, you cannot download intermediate output data to CSV or Parquet files. This output is only supported for HD non-EP analyses. |
EXPORT-016 | Sorry, you have exceeded the supported number of multiple analyses for export location results: %s. Please provide a valid input and try again. |
EXPORT-017 | Sorry, the financial perspective(s) you requested are not supported. See 'Financial Perspectives' in the Moody's RMS Support Center for perspectives that are supported for different analysis types. |
EXPORT-018 | Sorry, the field(s) you requested are not supported for location results export. See 'Location Results Export' in the Moody's RMS Support Center for the supported fields. |
EXPORT-019 | Sorry, you must provide at least one financial perspective and one export field to export location results. |
EXPORT-020 | Sorry, you can export location results only for account-level analyses. |
EXPORT-021 | Sorry, you must provide at least one financial perspective to export location results from an uploaded RDM that is not associated with an uploaded EDM. |
EXPORT-022 | Sorry, you must provide at least one export field to export location results for a non-EP analysis. |
EXPORT-023 | Sorry, you cannot export location results for non-EP analyses from an uploaded RDM that is not associated with an uploaded EDM. |
EXPORT-024 | Sorry, you cannot export location results for accounts that have more than 250,000 locations. Check the number of locations on the Accounts tab. |
EXPORT-025 | Sorry, you cannot export location results analyses from multiple EDMs. Enter analysis IDs from the same EDM to export. |
EXPORT-026 | Sorry, you cannot export location results analyses from multiple accounts. Enter analysis IDs from the same EDM and account to export. |
EXPORT-027 | Sorry, you cannot export location results for more than one analyses from uploaded RDMs that are not associated with an EDM. Enter one analysis ID from an uploaded RDMs that is not associated with an EDM or enter one or more analyses associated with an EDM. |
EXPORT-028 | Export of a weighted PLT is available only for a single EP analysis for HD or HD-ALM earthquake models. To export the weighted PLT, you must also export loss table output with at least one financial perspective and at least one output level. |
EXPORT-029 | The export input is invalid for received export type: %s. Please provide a valid input and try again. |
EXPORT-030 | The export input is invalid for received export ID: %s. Please provide a valid input and try again. |
EXPORT-031 | No data found for analysisId %s. Please make sure the input contains all valid analysisIds and try again. |
EXPORT-032 | Sorry, you must provide locationId as an export field to export location results for multiple analyses. |
EXPORT-033 | The export format is invalid. Specify the export format as CSV or JSON. |
EXPORT-034 | Sorry, you cannot export on %s engine sub type. |
EXPORT-035 | Sorry, you cannot perform export to file on %s engine sub type. |
EXPORT-036 | Sorry, you can not provide export type %s for received type %s. Check the export type and try again. |
EXPORT-037 | Sorry, Preserve IDs validation failed: You must export to a new EDM when you select the option to preserve IDs. |
EXP
Exposure errors.
| Error Code | Message |
|---|---|
EXP-500 | Database error occurred while updating time stamps for Exposure Type: %s, Exposure ID: %d |
EXP-501 | Exposure with database name : %s not found |
EXP-001 | Could not parse URL, reason %s |
EXP-502 | Database error occurred while determining exposure name |
EXP-503 | Database error occurred while calculating number of locations |
EXP-504 | Database error occurred while saving exposure owner |
EXP-505 | Database error occurred while determining exposure number |
EXP-506 | Database error occurred while checking whether exposure has owner |
EXP-507 | Database error occurred while saving exposure audit history |
EXP-508 | Database error occurred while updating exposure metrics |
EXP-509 | Error occurred while fetching the HD results for analysis ID %d |
EXP-510 | Active Database backup operation is in-progress for DB %s |
EXP-511 | Database error occurred while getting geocode summary |
EXP-512 | Database error occurred while getting hazard summary |
EXP-513 | Database error occurred while exporting portfolio |
EXP-514 | Database error occurred while exporting account |
EXP-515 | Database error occurred while updating exposure revision table |
EXP-516 | Database error occurred while calculating exposure workers compensation |
EXP-517 | Database error occurred while calculating number of policies |
EXP-518 | Database error occurred while updating metrics |
EXP-519 | Peril code %s is not supported for the Exposure Summary report. Select a supported peril. |
EXP-520 | Hazard name %s is not supported for the Exposure Summary report. Select a supported hazard. |
EXP-521 | Error occurred while %s batch data |
EXP-522 | treaty number %s already exists in EDM |
EXP-524 | Primary Location details not found. |
EXP-525 | Database error occurred while exporting aggregate portfolio |
EXP-526 | Validation Error encountered for %s |
EXP-527 | %s |
EXPOSURE-SET
| Error Code | Message |
|---|---|
EXPOSURE-SET-001 | Provide either the exposureSetId or the groupIds but not both. |
EXPOSURE-SET-002 | The exposureSetId %s is invalid. Use the RM GET /v1/exposuresets API to get a list of valid exposureSetId's. |
EXPOSURE-SET-003 | The groupIds %s are invalid. Use the SML GET /v1/Profile/groups API to get a list of valid groupId's. |
EXPOSURE-SET-004 | The operation %s is not valid for property %s. |
EXPOSURE-SET-005 | The request includes %s Use the SML GET /v1/Profile/groups API to get a list of valid groupId's. |
EXPOSURE-SET-006 | Sorry, you do not have access to exposureSetId %s. Check the ID and try again. |
EXPOSURE-SET-007 | Sorry, you can not perform this operation because you are not a member of the group. |
EXPOSURE-SET-008 | Sorry, we encountered an error on our end while querying exposure sets. Try again, and contact Moody's RMS Support if this still does not work. |
EXPOSURE-SET-009 | Sorry, we can't find %s %s. Either it doesn't exist or you don't have access to it. |
EXPOSURE-SET-010 | Sorry, you can not provide %s in case of no share. |
EXPOSURE-SET-011 | Provide either the exposureSetId or the dataSourceName but not both. |
EXPOSURE-SET-012 | Sorry, you can not provide same group value in add and remove operations. |
EXPOSURE-SET-013 | Exposure already exists for exposureSet %s. Cannot create multiple exposures under the same exposureSet. |
FAC
| Error Code | Message |
|---|---|
FAC-404 | %s |
FAC-406 | %s |
FAC-409 | %s |
FAC-500 | Database error occurred while retrieving fac layers |
FAC-501 | Database error occurred while creating facultative with name: %s |
FAC-502 | Database error occurred while checking for existing facultative |
FAC-503 | Database error occurred, facultative already exists |
FAC-504 | Database error occurred, facultative with ID: %s not exists |
FAC-505 | Database error occurred, while retrieving facultatives |
FAC-506 | Database error occurred while updating facultative |
FAC-507 | Database error occurred while loading facultative with ID: %s |
FAC-508 | A facultative cession with name: %s already exists. Use a different name. |
FAC-509 | Validation error, facultative ID cannot be null or empty. |
FAC-510 | Validation error, facultative, some of the String field has exceeded allowed length. |
FAC-511 | Database error occurred, facultative has relation to policy or location and cannot be %s |
FAC-512 | Database error occurred while checking if facultative has relation with policy or location |
FAC-513 | Database error occurred while deleting facultative with ID: %s |
FILE
| Error Code | Message |
|---|---|
FILE-001 | Bucket %d does not exist |
FILE-002 | Unable to access bucket %d |
FILE-003 | File %s does not exist |
FILE-004 | Unable to access file %d |
FILE-005 | Not authorized to grant temporary credentials |
FILE-006 | S3 Object %s does not exist |
FILE-007 | Sorry, we're having trouble reading the import file. Check the file format and delimiter and try again. |
FILE-009 | Sorry, looks there might be a problem on our end. Try saving again, and contact Moody's RMS Support if this still does not work. |
FILE-010 | The selected resolution requires a secondary resolution as well. This secondary resolution is missing from the import file. |
FILE-011 | The selected resolution requires a secondary resolution as well. This secondary resolution is incorrect for the resolution in the import file. |
FILE-014 | Sorry, we're having some trouble on our end. Try again, and contact Moody's RMS Support if this still does not work. |
FILE-015 | Sorry, we're having trouble with the column mapping in the import file and cannot complete the import. |
FILE-016 | Sorry, we're having trouble with provided resolution. Please check the resolution, try again and contact Moody's RMS Support if this still does not work. |
FILE-017 | Sorry, we're having trouble with retrieving the following missing files: %s |
FILE-018 | Sorry, we're having trouble with uploading empty files: %s. Please check. |
FILE-500 | Error occurred creating a new bucket |
FILE-505 | Error occurred staging bucket %d |
FILE-506 | Error occurred checking if bucket %d exists |
FILE-507 | Error occurred checking bucket %d permissions |
FILE-508 | Sorry, there's something wrong with the import file. Check that file type is valid. |
FILE-509 | Sorry, there's something wrong with the import file. Check that delimiter is valid. |
FILE-510 | Error occurred creating a new file |
FILE-511 | Error occurred retrieving file %d |
FILE-512 | Error occurred searching for files |
FILE-513 | Sorry, there's something wrong with the mapping. Check that country code and resolution are supported. |
FILE-514 | Sorry, missing or unsupported file extension for this input type. |
FILE-515 | Error occurred checking if file %d exists |
FILE-516 | Sorry it seems that the file that you have provided is not a valid ALM file. |
FILE-520 | Error occurred inserting import file record |
FILE-521 | Error occurred reading import file records |
GE
Global edit error messages.
| Error Code | Message |
|---|---|
GE-001 | Invalid exposure type. Valid exposure types are ACCOUNT and PORTFOLIO. Exposure type given: %s |
GE-002 | Account bulk edit cannot be preformed on account exposure |
GE-003 | Validation failed: %s |
GE-004 | Some data types in the WHERE clause do not match the data types of the respective fields |
GE-005 | Some data types in the SET clause do not match the data types of the respective fields |
GE-006 | Sorry, the provided date is invalid. %s |
GE-007 | List of updates provided in input is invalid for Basic Bulk Edit. |
GE-008 | Edit Query provided in input cannot be null or empty for Advanced Bulk Edit. |
GE-501 | An unexpected error occurred while preforming bulk edit on account %d |
GEO_SERVICE
| Error Code | Message |
|---|---|
GEO_SERVICE-001 | You have provided an invalid geoHaz engine type: %s. Engine type must be RL or HD. |
GEO_SERVICE-002 | You have provided an invalid data type for field: %s. Value must be true or false. |
GEO_SERVICE-003 | Your input is missing the required layerOptions. |
GEO_SERVICE-004 | Your input is missing property: %s for layerOptions. |
GEO_SERVICE-005 | You have provided an invalid value for layerOptions property: %s. Enter 0 for engineType RL or 1 for engineType HD. |
GEO_SERVICE-006 | You have provided an invalid geoHaz name: %s or version: %s for the engineType: %s. Only specific names and versions are valid. |
GEO_SERVICE-007 | You have provided an invalid geoHaz type: %s. GeoHaz type must be geocode or hazard. |
GEO_SERVICE-008 | You have provided an invalid engine type: %s. Geocode with LiaaS engine type is supported only for location level. |
GROUPING
| Error Code | Message |
|---|---|
GROUPING-001 | Sorry, we encountered an error running your grouping job. Contact Support at [email protected] to resolve this issue. |
GROUPING-002 | Invalid argument for %s |
GROUPING-003 | Group must contain at least one analysis |
GROUPING-004 | Invalid region code: %s |
GROUPING-006 | Invalid rate scheme data |
GROUPING-008 | %s is mapped to multiple rate scheme IDs %s |
GROUPING-009 | Unable to load analysis %s |
GROUPING-010 | Unable to load analysis group with ID: %s |
GROUPING-011 | Analysis %s is not a group |
GROUPING-012 | We can not process this job because the analysis %s is already an independent group |
GROUPING-013 | We can not process this job because the analysis %s is an HD group |
GROUPING-014 | We can not process this job because the analysis %s is a Marginal Impact Analysis |
HPC
| Error Code | Message |
|---|---|
HPC-001 | Unknown task type |
HPC-501 | Failed to create HPC job. Error: %s |
HPC-502 | Failed to create HPC task. Error: %s |
HPC-503 | Failed to submit HPC job. Error: %s |
HPC-504 | Failed to submit HPC job |
HPC-505 | Failed to get HPC job details. Response code: %d. Error: %s |
HPC-506 | Failed to get HPC job details |
HPC-507 | Failed to cancel HPC job. Response code: %d. Error: %s |
HPC-508 | Failed to cancel HPC job |
HPC-509 | Failed to set environment variables for HPC job |
HPC-510 | Failed to get HPC job task details |
HPC-511 | Failed to get HPC job task details. Response code: %d. Error: %s |
HPC-512 | Failed to check HPC job status. Failed after multiple retries |
IAM
| Error Code | Message |
|---|---|
IAM-001 | Credentials are required to access this resource |
IAM-002 | No databases found for user |
IAM-003 | User %d was not found |
IAM-004 | User group %d was not found |
IAM-005 | User reporting currency was not found for user %d |
IAM-500 | Internal error occurred retrieving user profile |
IAM-501 | Internal error occurred retrieving a user's databases |
IAM-502 | Error getting user information |
IAM-503 | Error occurred creating a new user token |
IAM-504 | Error occurred updating a user token |
IAM-505 | Error occurred deleting a user token |
IAM-506 | Error occurred validating a user token |
IAM-507 | Internal error occurred retrieving a user group information |
IAM-508 | Database error occurred while adding security log |
IAM-509 | Error occurred while encrypting string |
IAM-510 | The new password and confirmation password do not match |
IAM-511 | Error occurred updating a user password |
IAM-512 | Password cannot be null or empty |
IAM-513 | Password cannot be longer than 18 characters |
IAM-514 | Invalid user ID |
IAM-515 | Error occurred while retrieving list of tenant IDs |
IAM-516 | Error occurred while retrieving list of EDMs assigned to tenant |
IAM-517 | Database error occurred while saving Group DB Detail for DbId: %d |
IAM-518 | Database error occurred while retrieving Tenant EDM metrics |
IMP
| Error Code | Message |
|---|---|
IMP-001 | The account, location, and/or reinsurance file for this import is empty. Provide a valid file and try the import again. |
IMP-002 | Sorry, we're having trouble reading the import file %s. Check the file and try again. |
IMP-003 | Sorry, we're having trouble with this import file. It looks like the header row and the first row of the file have a different number of columns. |
IMP-004 | Duplicate portfolio ids. PortfolioIds must be unique. |
IMP-005 | Error occurred extracting data from file %d. Error: %s |
IMP-006 | You have provided an invalid value for the HTTP header "Accept-Language". Check the value and the spelling (it's case-sensitive). Valid values are en-US, de-DE, en-GB, fr-FR, en, de and fr. |
IMP-500 | Sorry, we encountered an error while performing this import. Try again, and contact Moody's RMS Support if this still does not work. |
IMP-501 | Error occurred validating import data |
IMP-502 | Error occurred extracting data from file %d |
IMP-503 | Error occurred creating the mapping file |
IMP-504 | Error occurred creating the account file |
IMP-505 | Sorry, it looks like there's a problem with the location file. Verify the account number and the selected delimiter, and try again. |
IMPORT_STORE
| Error Code | Message |
|---|---|
IMPORT_STORE-401 | Database error occurred, IMPORT_STORE does not exists |
IMPORT_STORE-501 | Database error occurred while loading IMPORT_STOREs, reason : %s |
IMPORT_STORE-502 | Database error occurred while creating IMPORT_STORE, reason : %s |
IMPORT_STORE-503 | Database error occurred while updating IMPORT_STORE, reason : %s |
IMPORT_STORE-504 | Database error occurred while deleting IMPORT_STORE, reason : %s |
IMPORT_STORE-505 | Database error occurred duplicate IMPORT_STORE, IMPORT_STORE already exists |
IMPORT_STORE-506 | Validation error, IMPORT_STORE ID cannot be null. |
IMPORT_STORE-507 | Validation error, IMPORT_STORE ID length has to be between 1 and 20. |
IMPORT_STORE-508 | Validation error, IMPORT_STORE, some of the String field has exceeded allowed length. |
IMPORT_STORE-509 | Could not parse URL, reason %s |
IMPORT_STORE-510 | Unknown DbType, only EDM, RDM, EXPOSURE_BATCH_EDIT or BATCH DbType is supported |
IMPORT_STORE-511 | Validation error, file names must be named in a GUID format. With an appropriate %s extension. |
IMPORT_STORE-512 | Validation error, file names must share the same name with different extensions. |
INFRA
| Error Code | Message |
|---|---|
INFRA-001 | Submit job failed. Please resubmit job. |
JOB
| Error Code | Message |
|---|---|
JOB-001 | job %s was not found |
JOB-002 | Unable to access job %d |
JOB-003 | Failed to cancel the job ID %d. Error: %s |
JOB-500 | Database error occurred while retrieving execution status for job ID: %d |
JOB-501 | Database error occurred while searching for jobs |
JOB-502 | Database error occurred while getting job ID %d |
JOB-503 | Database error occurred while checking if user is authorized to cancel job %d |
JOB-504 | Database error occurred while canceling job %d |
JOB-505 | Database error occurred while archiving job details for job ID: %d |
JOB-506 | Database error occurred while retrieving job report message for jobId: %d, Service ID: %d |
JOB-507 | Database error occurred while retrieving job identifier for account ID: %d |
JOB-508 | Database error occurred while retrieving job details for account ID: %d |
JOB-509 | Database error occurred while retrieving services for account ID: %d |
JOB-510 | Database error occurred while retrieving job report for job ID: %d, Service ID: %d |
JOB-511 | Database error occurred while retrieving user details for job Type: %s, job ID: %d |
JOB-512 | Database error occurred while retrieving job status for job ID: %d |
JOB-513 | Error occurred. Invalid job status found for job ID: %d |
JOB-514 | Database error occurred while retrieving job ID from commit queue for account ID: %d |
JOB-515 | Database error occurred while retrieving job status from commit queue for job ID: %d |
JOB-516 | Database error occurred while searching for job monitoring records |
JOB-517 | Database error occurred deleting job monitoring record ID: %d |
JOB-518 | Sorry, user %s is not allowed to update the %s job priority due to no access to %s resource group |
JOB
| Error Code | Message |
|---|---|
JOB-601 | Sorry, both status and priority provided in same request. Please check and try again |
JOB-602 | Sorry, update operation not allowed for job ID %s with status %s |
JOB-603 | Invalid resource uri %s is provided |
JOB-604 | Invalid resource type %s is provided |
JOB-605 | Invalid job type %s is provided |
JOB-606 | Sorry, there is no job ID %s for this user %s |
JOB-607 | Invalid jobId %s is provided |
JOB-608 | Sorry, provide either status or priority in request. |
JOB-609 | Sorry, cancellation is not supported for %s job. |
JOB-610 | Sorry, priority update is not supported for %s job. |
LOC_RES
| Error Code | Message |
|---|---|
LOC_RES-001 | No data found for export fields and perspectives |
LOC_RES-002 | No loss nor exposure found for analysis/account |
LOC_RES-003 | No location results schema found for analysis ID %s |
KS
Keystore errors.
| Error Code | Message |
|---|---|
KS-001 | The tenant ID in a key and URL must match |
KS-003 | Operation not supported; The value should be CREATE, READ, UPDATE or DELETE only |
KS-004 | Key exists |
KS-005 | Key does not exist |
KS-006 | Value cannot be empty |
KS-007 | Key not found in baseline properties: %s |
KS-008 | Sorry, this could be an error on our end. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
KS-009 | Sorry, this could be an error on our end. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
LINE_OF_BUSINESS
| Error Code | Message |
|---|---|
LINE_OF_BUSINESS-401 | Database error occurred, line of business does not exists |
LINE_OF_BUSINESS-404 | %s |
LINE_OF_BUSINESS-406 | %s |
LINE_OF_BUSINESS-409 | %s |
LINE_OF_BUSINESS-501 | Database error occurred while loading line of business, reason : %s |
LINE_OF_BUSINESS-502 | Database error occurred while creating line of business, reason : %s |
LINE_OF_BUSINESS-503 | Database error occurred while updating line of business with ID: %s, reason : %s |
LINE_OF_BUSINESS-504 | Database error occurred while deleting line of business with ID: %s, reason : %s |
LINE_OF_BUSINESS-505 | Sorry, this LOB name already exists. Try using a different name. |
LINE_OF_BUSINESS-506 | Validation error, line of business, the name field has exceeded allowed length. |
LINE_OF_BUSINESS-507 | Database error occurred while validating LOB details. |
LINE_OF_BUSINESS-508 | Line of business validation failed. |
LOCATION
| Error Code | Message |
|---|---|
LOC-001 | Location %d was not found |
LOC-002 | Account %d, for location %d, was not found |
LOC-003 | Do not have sufficient permission to location %d |
LOC-004 | The floors occupied exceed the number of stories. Change one of these values. |
LOC-005 | Facultative cession layer information is mandatory when reinsurance cession is Facultative |
LOC-006 | treaty information is mandatory when reinsurance cession is treaty |
LOC-007 | Do not have sufficient permission on given locations |
LOC-008 | You must enter a value for at least one building or contents coverage for the combined coverage limits and deductibles to apply |
LOC-009 | Location Business Interruption Detail ID: %d was not found for Location ID: %d |
LOC-010 | Location building attribute ID: %d was not found for Location ID: %d |
LOC-011 | Insufficient information to geocode the location. Please provide additional address information. The minimum required fields are: City & State, ZIP Code, OR Latitude & Longitude |
LOC-012 | The primary building of a multi-building site cannot be deleted. To delete this building, configure it as a secondary building. |
LOC-013 | Multiple locations with the same site name can only have 1 Primary Building selected. Only one location can be the Primary Building if multiple locations have the same site name. |
LOC-014 | The primary building of a multi-building site cannot be modified. To modify this building, configure it as a secondary building. Modifications cannot be made to Location ID: %d |
LOC-015 | %s cannot be assigned to secondary buildings on a multi-building campus. |
LOC-016 | Ensure location is geocoded before running hazard lookup |
LOC-017 | Start date should be less than or equal to Completion date |
LOC-018 | %s |
LOC-019 | Database error occurred while retrieving Location ID: %d |
LOC-020 | Site Limit should be between 0 to 1e+14 |
LOC-021 | Site Deductible should be between 0 to 1e+14 |
LOC-022 | Location coverage label may not be empty and label ID should not be 0 |
LOC-023 | Invalid input. There are no locations associated with the given exposure |
LOC-024 | Inception date should be less than or equal to Expiration date |
LOC-025 | Location Earthquake Detail ID: %d was not found for Location ID: %d |
LOC-026 | Location Windstorm Detail ID: %d was not found for Location ID: %d |
LOC-027 | Location Flood Detail ID: %d was not found for Location ID: %d |
LOC-028 | Location Fire Detail ID: %d was not found for Location ID: %d |
LOC-029 | Location Terrorism Detail ID: %d was not found for Location ID: %d |
LOC-030 | Location Tornado Detail ID: %d was not found for Location ID: %d |
LOC-031 | Location coverage ID: %d was not found for Location ID: %d |
LOC-032 | Location reinsurance Cession ID: %d was not found for Location ID: %d |
LOC-033 | Location Workers Compensation ID: %d was not found for Location ID: %d |
LOC-034 | Location condition ID: %d was not found for Location ID: %d |
LOC-035 | Invalid input. At least one location condition should be specified. |
LOC-036 | Location Currency code should not be null or empty. |
LOC-404 | %s |
LOC-500 | Database error occurred while searching locations |
LOC-501 | Database error occurred while retrieving Location ID: %d |
LOC-502 | Database error occurred while loading location currency information for Location ID: %d |
LOC-503 | Database error occurred while loading parent account information for Location ID: %d |
LOC-504 | Database error occurred while creating location |
LOC-505 | Database error occurred while deleting Location ID: %d |
LOC-506 | Database error occurred while updating Location ID: %d |
LOC-508 | Database error occurred while performing bulk edit of locations under account ID: %d |
LOC-512 | Database error occurred while checking if Location reinsurance Cession ID: %d exists for Location ID: %d |
LOC-514 | Database error occurred while retrieving Location reinsurance Cession ID: %d for Location ID: %d |
LOC-515 | Database error occurred while creating location reinsurance cession for Location ID: %d |
LOC-516 | Database error occurred while updating Location reinsurance ID: %d for Location ID: %d |
LOC-517 | Database error occurred while deleting Location reinsurance ID: %d for Location ID: %d |
LOC-518 | Database error occurred while checking if Location Earthquake details ID: %d exists |
LOC-519 | Database error occurred while retrieving location earthquake details for Location ID: %d |
LOC-520 | Database error occurred while retrieving Location Earthquake details ID: %d |
LOC-521 | Database error occurred while creating location earthquake details for Location ID: %d |
LOC-522 | Database error occurred while updating Earthquake details ID: %d for Location ID: %d |
LOC-523 | Database error occurred while deleting Earthquake details ID: %d for Location ID: %d |
LOC-524 | Database error occurred while checking if Location Flood details ID: %d exists |
LOC-525 | Database error occurred while retrieving location flood details for Location ID: %d |
LOC-526 | Database error occurred while retrieving Location Flood details ID: %d |
LOC-527 | Database error occurred while creating location flood details for Location ID: %d |
LOC-528 | Database error occurred while updating Flood details ID: %d for Location ID: %d |
LOC-529 | Database error occurred while deleting Flood details ID: %d for Location ID: %d |
LOC-530 | Database error occurred while checking if Location Fire details ID: %d exists |
LOC-531 | Database error occurred while retrieving location fire details for Location ID: %d |
LOC-532 | Database error occurred while retrieving Location Fire details ID: %d |
LOC-533 | Database error occurred while creating location fire details for Location ID: %d |
LOC-534 | Database error occurred while updating Fire details ID: %d for Location ID: %d |
LOC-535 | Database error occurred while deleting Fire details ID: %d for Location ID: %d |
LOC-536 | Database error occurred while checking if Location Windstorm details ID: %d exists |
LOC-537 | Database error occurred while retrieving location windstorm details for Location ID: %d |
LOC-538 | Database error occurred while retrieving Location Windstorm details ID: %d |
LOC-539 | Database error occurred while creating location windstorm details for Location ID: %d |
LOC-540 | Database error occurred while updating Windstorm details ID: %d for Location ID: %d |
LOC-541 | Database error occurred while deleting Windstorm details ID: %d for Location ID: %d |
LOC-542 | Database error occurred while checking if Location Tornado details ID: %d exists |
LOC-543 | Database error occurred while retrieving location tornado details for Location ID: %d |
LOC-544 | Database error occurred while retrieving Location Tornado details ID: %d |
LOC-545 | Database error occurred while creating location tornado details for Location ID: %d |
LOC-546 | Database error occurred while updating Tornado details ID: %d for Location ID: %d |
LOC-547 | Database error occurred while deleting Tornado details ID: %d for Location ID: %d |
LOC-548 | Database error occurred while checking if Location Terrorism details ID: %d exists |
LOC-549 | Database error occurred while retrieving location terrorism details for Location ID: %d |
LOC-550 | Database error occurred while retrieving Location Terrorism details ID: %d |
LOC-551 | Database error occurred while creating location terrorism details for Location ID: %d |
LOC-552 | Database error occurred while updating Terrorism details ID: %d for Location ID: %d |
LOC-553 | Database error occurred while deleting Terrorism details ID: %d for Location ID: %d |
LOC-554 | Database error occurred while checking if Location Worker Compensation details ID: %d exists |
LOC-556 | Database error occurred while retrieving Location Worker Compensation details ID: %d |
LOC-557 | Database error occurred while creating location worker compensation details for Location ID: %d |
LOC-558 | Database error occurred while updating Worker Compensation details ID: %d for Location ID: %d |
LOC-559 | Database error occurred while deleting Worker Compensation details ID: %d for Location ID: %d |
LOC-560 | Database error occurred while checking if Location Business Interruption details ID: %d exists |
LOC-562 | Database error occurred while retrieving Location Business Interruption details ID: %d |
LOC-563 | Database error occurred while creating location business interruption details for Location ID: %d |
LOC-564 | Database error occurred while updating Business Interruption details ID: %d for Location ID: %d |
LOC-565 | Database error occurred while deleting Business Interruption details ID: %d for Location ID: %d |
LOC-566 | Database error occurred while checking if Location coverage details ID: %d exists |
LOC-567 | Database error occurred while checking coverage dependency for Location ID: %d |
LOC-568 | Database error occurred while retrieving Location coverage details ID: %d |
LOC-569 | Database error occurred while creating location coverage details for Location ID: %d |
LOC-570 | Database error occurred while updating coverage details ID: %d for Location ID: %d |
LOC-571 | Database error occurred while deleting coverage details ID: %d for Location ID: %d |
LOC-573 | Database error occurred while calculating number of employees for Location ID: %d |
LOC-574 | Database error occurred while checking if building attribute details ID: %d exists |
LOC-575 | Database error occurred while creating building attribute details for Location ID: %d |
LOC-576 | Database error occurred while updating building attribute details ID: %d for Location ID: %d |
LOC-577 | Database error occurred while deleting building attribute details ID: %d |
LOC-578 | Database error occurred while checking if Location condition details ID: %d exists for Location ID: %d |
LOC-580 | Database error occurred while retrieving Location condition details ID: %d |
LOC-581 | Database error occurred while creating location condition details for Location ID: %d |
LOC-582 | Database error occurred while updating condition details ID: %d for Location ID: %d |
LOC-583 | Database error occurred while deleting condition details ID: %d for Location ID: %d |
LOC-584 | Database error occurred while retrieving policy conditions list by Location ID: %d |
LOC-585 | Database error occurred while querying location information for Location ID: %d |
LOC-586 | Error occurred while geocoding Location ID: %d |
LOC-587 | Error occurred while geocoding Street Address: %s |
LOC-588 | Error occurred while running hazard on Location ID: %d |
LOC-589 | Error occurred while running hazard on Street Address: %s |
LOC-590 | Database error occurred while checking if Construction Class valid for Building Class Scheme: %s, Building Class: %s |
LOC-591 | Database error occurred while checking if Occupancy Type valid for Occupancy Type Scheme: %s, Occupancy Type: %s |
LOC-592 | Database error occurred while checking if MSB Construction Class valid for Building Class Scheme: %s, Building Class: %s |
LOC-593 | Database error occurred while retrieving Construction Code for Building Class Scheme: %s, Building Class: %s |
LOC-594 | Database error occurred while retrieving MSB Construction Code for ATC Constriction Code: %s |
LOC-595 | Database error occurred while retrieving Occupancy Code for Occupancy Type Scheme: %s, Occupancy Type |
LOC-596 | Database error occurred while retrieving Location IDs for the AccountId: %d |
LOC-601 | Database error occurred while checking if location is primary building for Multi-Building campus for Location ID: %d |
LOC-602 | Database error occurred while getting count of secondary buildings for Multi-Building campus for Location ID: %d |
LOC-603 | Database error occurred while checking if location is secondary building for Multi-Building campus for Location ID: %d |
LOC-604 | Database error occurred while checking if site name is unique |
LOC-605 | Database error occurred while retrieving site names for account ID: %d |
LOC-606 | Database error occurred while back filling policy conditions for Location ID: %d and condition ID: %d |
LOC-607 | MSB security token authorization failure |
LOC-608 | Error occurred while updating the enhanced building attributes for ESDB |
LOC-609 | Multiple Combined coverage entries on a location are not allowed for a single peril |
LOC-610 | Database error occurred while updating condition details for Location ID: %d |
LOC-611 | %s %d not found for location condition |
LOC-613 | Location ID %d for property does not exist |
LOC-614 | Duplicate Location ID %s found in input |
LOC-615 | Invalid Occupancy type scheme provided for Worker Compensation details |
LOC-616 | Location ID: %d and building attribute ID: %d provided should be equal |
LOC-617 | Address ID: %d provided for property is invalid for operationType: %s |
LOC-618 | Duplicate Location ID: %d and condition ID: %d found in input |
LOC-619 | Invalid location %s yearBuilt: %s. Value provided must be between %d and %d |
LOC-620 | Invalid location. Property and Address field cannot be null |
LOC-621 | Invalid location. Location Number cannot be null or empty. |
LOC-622 | %s cannot be greater than zero during location creation |
LOC-623 | %s details already exist for location ID: %d |
MAP
| Error Code | Message |
|---|---|
MAP-001 | Credentials are required to access this resource |
MAP-002 | There aren't any locations or address details for latitude and longitude are missing! |
MAP-PERSPECTIVE
| Error Code | Message |
|---|---|
MAP-PERSPECTIVE-001 | The source perspective code %s is invalid. Please check that your request specifies a valid perspective. |
MAP-PERSPECTIVE-002 | The target perspective code %s is invalid. Please check that your request specifies a valid perspective. |
MAP-PERSPECTIVE-003 | Sorry, we encountered an error on our end while mapping perspective for analysis ID %d. Contact Support at [email protected]. |
MAP-PERSPECTIVE-004 | Sorry, the target and source perspectives cannot be the same. Enter a target perspective different than the source perspective. |
MAP-PERSPECTIVE-005 | Sorry, perspective mapping is not supported for this analysis. Please enter a non HD or non-simulated DLM analysis ID. |
MAP-PERSPECTIVE-006 | Sorry, you can map perspective only for portfolio or aggregate portfolio analyses. |
MAP-PERSPECTIVE-007 | Sorry, you can not perform map perspective on %s engine sub type. |
MARGINAL-IMPACT
| Error Code | Message |
|---|---|
MARGINAL-IMPACT-001 | Invalid argument for %s |
MARGINAL-IMPACT-002 | Sorry, we encountered an error while submitting the Marginal Impact job. Try again, and contact Moody's RMS Support if this still does not work. |
MARGINAL-IMPACT-003 | Sorry, you can perform marginal impact on %s engine type(s) only. |
MARGINAL-IMPACT-004 | Sorry, you can perform marginal impact on %s output type(s) only. |
MARGINAL-IMPACT-005 | The analysis is using unsupported exposure types. The reference analysis can be a portfolio or group. The marginal impact analysis can be an account. |
MARGINAL-IMPACT-006 | We were unable to find the exposure used while generating the input analysis. %s. |
MARGINAL-IMPACT-007 | Sorry, you can not perform marginal impact on %s engine sub type. |
METADATA
RDM metadata errors.
|Error Code |Message|
|:---|:---|
|METADATA-001|Error occurred while inserting a record in rdm metadata for analysis ID : %d|
|METADATA-002|Sorry, this could be an error on our end. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work.|
|METADATA-003|Database error occurred while deleting records for the analysis ID : %d|
|METADATA-004|Database error occurred while populating rdm analysis regions hd table for tenant ID: %s|
|METADATA-005|Database error occurred while reading total count of rdm analysis regions records for tenant ID: %s|
|METADATA-006|Database error occurred while reading analysis IDs for data clean up for tenant ID: %s|
MGMT
| Error Code | Message |
|---|---|
MGMT-001 | Request is missing property: %s |
MGMT-002 | Unable to acquire service name |
MGMT-003 | Error reading properties file |
MGMT-004 | Conflicting operation in-progress |
MGMT-005 | Invalid DB Key |
MGMT-006 | Can not delete currently active DB server |
MGMT-007 | S3 error while copying results schema to tenant loss bucket |
MGMT-008 | Tenant not found |
MGMT-010 | Failed to retrieve tenant entitlements |
MGMT-011 | Database error reading tenant package with packageId: %s |
MGMT-012 | Error reading tenant entitlement for tenant: %s |
MGMT-013 | Failed to retrieve EDMs |
MGMT-014 | Failed to lock EDM |
MGMT-015 | Failed to unlock EDM |
MGMT-016 | Failed to retrieve tenant db migration sub task |
MGMT-017 | Failed to retrieve tenant db migration edm status |
MGMT-018 | Failed to update tenant db migration sub task |
MGMT-019 | Failed to insert tenant db migration sub task |
MGMT-020 | Failed to update tenant db migration edm status |
MGMT-021 | Failed to insert tenant db migration edm status |
MGMT-022 | Failed to update database connection string |
MGMT-023 | Failed to get engine input |
MGMT-024 | Failed to do backup operation on database: %s |
MGMT-025 | Failed to do restore operation on database: %s |
MGMT-026 | Failed to retrieve Data Bridge notification status |
MGMT-027 | Failed to update Data Bridge notification sub task |
MGMT-028 | Failed to insert Data Bridge notification sub task |
MGMT-029 | Failed to get Data Bridge notification sub task |
MGMT-030 | Tenant is missing the required package entitlement for: %s |
MGMT-031 | The provided task ID does not belong to this tenant |
MGMT-032 | The previous call to delete this tenant did not complete successfully. Please re-run the tenant delete before attempting to re-onboard. |
MGMT-033 | There was an error while creating event info database %s |
MGMT-034 | There was an error while restoring geohazard database %s to server %s |
MGMT-035 | There was an error while creating the geohazard database restore task for ID %s |
MGMT-036 | Failed to add common bucket IAM role to server %d for tenant %s |
MGMT-037 | Failed to upgrade RDS server %s for tenant %s |
MGMT-038 | Failed to get validation result for DB type: %s, tenantId: %s |
MGMT-039 | Validations failed on Tenant DB: %s, tenantId: %s |
MGMT-040 | Can not upgrade tenant app : %s for tenantId: %s. Please check if the tenant app onboarded successfully. |
MP
|MP-001|Sorry, we could not submit this analysis. To resolve this issue, contact Moody's RMS Support at [email protected].|
|MP-002|Sorry, we encountered an error processing the input you provided for running this analysis. Validate the input and try again. Contact Support at [email protected] if this still doesn't work.|
|MP-003|Sorry, this could be an error on our end. Try again, and contact Moody's RMS Support at [email protected] if this still does not work.|
PARQUET2RDM
| Error Code | Message |
|---|---|
PARQUET2RDM-001 | Could not parse URL, reason %s |
PARQUET2RDM-002 | Sorry, we cannot process this job because a job on analysis ID %s is already running. Wait for the job to finish before you run this new job |
PARQUET2RDM-003 | Unable to acquire lock |
PARQUET2RDM-004 | Sorry, something is wrong with this data submitted for RDM download. Check the properties and format of the results data and try again. If this still does not work, contact Moody's RMS Support |
PARQUET2RDM-006 | Sorry, download of these results will not work right now. It could be that post-analysis treaty editing is being performed on these results. Wait and try again. |
PARQUET2RDM-007 | Sorry, we encountered an error while creating the export RDM job. Try again. If this still doesn't work, contact Moody's RMS Support. |
PATE
| Error Code | Message |
|---|---|
PATE-001 | PATE ID in URL and body must match |
PATE-002 | Database error occurred while creating pate with treaty number: %s |
PATE-003 | Database error occurred while updating pate with pateId: %d |
PATE-004 | Database error occurred while deleting pate with pateId: %d |
PATE-005 | Database error occurred while getting a list of pate treaties |
PATE-006 | Database error occurred while deleting a list of pate treaties |
PATE-007 | treaty number %s already exists. Check if new added treaties having a valid (unique) treaty number and an occurrence limit greater than zero. |
PATE-008 | Database error occurred while retrieving a list of pate lobs with treatyId: %d |
PATE-009 | Analysis ID %d is not valid for post-analysis treaty editing. Check that the exposure type is portfolio or aggportfolio and the analysis type is EP. |
PATE-010 | Cannot delete treaty with type: %s |
PATE-011 | Invalid Operation type for treaty ID: %d |
PATE-013 | Database error occurred while deleting pate treaties in a batch for analysis ID: %d |
PATE-014 | We cannot process this job because a job on this result is already running. |
PATE-015 | Database error occurred while acquiring lock |
PATE-016 | Database error occurred while updating lock metadata |
PATE-017 | Attempt to acquire lock failed. Lock has been acquired by a different process. |
PATE-018 | We cannot process this job because you have not made any changes. |
PATE-019 | Database error occurred while checking PATE records for analysis ID: %d |
PATE-020 | TenantId was not available from thread context for operations on pate treaties |
PATE-021 | A group of PATE treaties cannot be deleted because one of the treaties is marked not for deletion |
PATE-022 | Database error occurred while retrieving treaty type |
PATE-023 | Sorry, you've provided an invalid operationType for one of the input properties. INSERT is valid operationType for insert property. DELETE is valid operationType for delete property. UPDATE is valid operationType for update property. |
PATE-024 | Sorry, looks like the treatyID is missing or invalid. For delete and update properties, treatyID must be greater than zero. |
PATE-025 | Sorry, looks like the input for running PATE on an analysis is missing or invalid. Please provide a valid input for the request. |
PATE-026 | Sorry, looks like the input for running PATE on an analysis is invalid. For insert property, the treatyID must be zero. |
PATE-027 | Use only positive numbers for the hours clause. Negative numbers are not supported. |
PATE-028 | Do not include radius clauses for treaties added post analysis. They are not supported. |
PATE-029 | treaty type cannot be blank. Enter one of the following treaty types: Catastrophe, Corporate, Stop Loss |
PATE-030 | Sorry, you can not perform PATE on %s engine sub type. |
PATE-031 | Database error occurred while getting patetreatyid for treatyid: %d. |
PATE-032 | Performing post-analysis treaty editing on these results is not supported because they are from an uploaded RDM with HD results from earthquake or terrorism HD analyses. |
PATE-033 | List of treaties attached post-analysis is invalid. One of the treaties either doesn't exist or is not associated with the analysis. Check the treaty IDs and try again. |
PATE-034 | Analysis or group IDs provided in input are not valid for post-analysis treaty editing. Please check the analysis or group IDs and try again. |
PLATFORM
| Error Code | Message |
|---|---|
PLATFORM-001 | Sorry, something might be wrong at our end. We failed to load the currency scheme. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-002 | Sorry, something might be wrong at our end. We failed to load the event rate scheme. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-003 | Sorry, something might be wrong at our end. We failed to load the event rates. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-004 | Sorry, something might be wrong at our end. We failed to load the model profile. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-005 | Sorry, something might be wrong at our end. We failed to load the output profile. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-006 | Sorry, something might be wrong at our end. We failed to load the ALM profiles. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-007 | Sorry, something might be wrong at our end. We failed to load the default ALM profiles. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-008 | Sorry, something might be wrong at our end. We failed to load the footprint event. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-009 | Sorry, something might be wrong at our end. We failed to load the currency vintage. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-010 | Sorry, something might be wrong at our end. We failed to load the default event rate schemes. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-011 | Sorry, something might be wrong at our end. We failed to load the cost severity scheme. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-012 | Sorry, something might be wrong at our end. We failed to load the cost severity averages. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-013 | Sorry, something might be wrong at our end. We failed to load the cost severity CVs. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-014 | Sorry, something might be wrong at our end. We failed to load the model region hierarchy. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-015 | Sorry, the currency scheme is invalid. Specify a valid currency and try again. |
PLATFORM-016 | Sorry, the model profile is invalid. Specify a valid model profile and try again. |
PLATFORM-017 | Sorry, the output profile is invalid. Specify a valid output profile and try again. |
PLATFORM-018 | Sorry, the footprint event is invalid. Specify a valid footprint event and try again. |
PLATFORM-019 | Sorry, the currency vintage is invalid. Specify a valid currency and try again. |
PLATFORM-020 | Sorry, something might be wrong at our end. We failed to find the simulation set. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-021 | Sorry, something might be wrong at our end. We failed to load the simulation set. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-022 | Sorry, something might be wrong at our end. We failed to load the event loss adjustment scheme. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-023 | Sorry, something might be wrong at our end. We failed to load the PET Metadata. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PLATFORM-024 | Sorry, something might be wrong at our end. We failed to load the Currency Metadata. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
PORT
PORT errors are returned for resources in the Portfolios collection.
| Error Code | Message |
|---|---|
PORT-001 | We could not find portfolio %d in this EDM. |
PORT-004 | No geocoded locations exist in portfolio with ID %d and number %s. Geocode this portfolio before you run an analysis. |
PORT-401 | Select at least one account to add to or remove from the portfolio. |
PORT-402 | Sorry, we cannot process the input. Please do not include null values in accountsToAdd and accountsToRemove collections. |
PORT-404 | %s |
PORT-405 | %s |
PORT-500 | Sorry, we encountered an error retrieving portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-501 | Sorry, we encountered an error checking if portfolio %d exists. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-502 | Sorry, we encountered an error creating this portfolio. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-504 | Sorry, we encountered an error retrieving information about portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-505 | Sorry, we encountered an error deleting portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-506 | Sorry, we encountered an error saving the changes for portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-508 | Sorry, we encountered an error copying portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-511 | Sorry, we encountered an error searching for portfolios. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-512 | Database error occurred while fetching number of exposures for exposure type: PORTFOLIO. |
PORT-514 | Sorry, we encountered an error retrieving geocoding information for one or more locations in portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-515 | Sorry, we encountered an error retrieving total number of accounts in portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-534 | Geocode Portfolio failed for portfolio ID: %d. |
PORT-539 | Database error occurred while managing accounts to portfolio ID: %d |
PORT-540 | You cannot add and remove the same account for portfolio: %d. |
PORT-541 | Sorry, we encountered an error searching accounts for portfolio %d. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-542 | Sorry, we encountered an error converting currencies for portfolio with ID: %d. Try again, and contact Moody's RMS Support if this still does not work. |
PORT-543 | More than one location in portfolio %d has latitude %f and longitude %f. Two locations in a portfolio cannot have the same coordinates. |
PORT-544 | No locations in portfolio %d have latitude %f and longitude %f. Check the coordinates or regeocode the portfolio. |
PORT-548 | You cannot analyze a portfolio with more than 1M accounts if the output profile specifies loss table output at the contract granularity. |
PORT-549 | Duplicate portfolio ID %s found in input. |
PORT-550 | Validation failed. Accounts count to add/remove to/from portfolio exceeds the limit %d. |
PORT-551 | Sorry, we encountered an error converting currencies for portfolio with ID: %d due to invalid values in the specified currency scheme. Please verify your currency scheme and try again, and contact Moody's RMS Support if this still does not work. |
POL
policy error messages.
|Error Code |Message|
|:---|:---|
|POL-000|Sorry, looks like something might be wrong at our end. Try this again, and if it still doesn't work, contact Moody's RMS Support at [email protected].
|POL-001|policy %d was not found
|POL-002|User does not have sufficient permissions on policy ID: %d
|POL-003|policy Effective date must be less than policy Expiration Date.
|POL-004|Facultative cession layer information is mandatory when reinsurance cession is Facultative
|POL-005|treaty information is mandatory when reinsurance cession is treaty
|POL-006|policy coverage ID: %d for policy %d was not found
|POL-007|policy reinsurance Cession ID: %d for policy %d was not found
|POL-008|policy condition ID: %d for policy %d was not found
|POL-009|policy Criteria ID: %d for policy condition ID: %d was not found
|POL-010|Condition ID: %d was not found
|POL-011|Parent account ID: %d was not found for policy ID: %d
|POL-012|%s
|POL-013|policy %s is required
|POL-014|%s may not be null
|POL-404|%s
|POL-500|Database error occurred while retrieving policy ID: %d
|POL-501|Database error occurred while checking if policy ID: %d exists
|POL-502|Database error occurred while creating policy, reason: %s
|POL-503|Database error occurred while retrieving policy by link ID: %s
|POL-504|Database error occurred while retrieving policy metrics for policy ID: %d
|POL-505|Database error occurred while deleting policy ID: %d
|POL-506|Database error occurred while updating policy, reason: %s
|POL-507|Database error occurred while retrieving countries covered by policy ID: %d
|POL-508|Database error occurred while copying policy ID: %d
|POL-509|Database error occurred while mapping policy ID %d with user %d
|POL-510|Database error occurred while saving policy details for policy ID: %d
|POL-511|Database error occurred while searching policies
|POL-512|Database error occurred while checking policy permissions for policy ID: %d
|POL-514|Database error occurred while retrieving location coordinates covered by policy ID: %d
|POL-515|Database error occurred while loading parent account information for policy ID: %d
|POL-516|Database error occurred while loading policy currency information for policy ID: %d
|POL-517|Database error occurred while performing bulk edit of policies under account ID: %d
|POL-518|Database error occurred while checking if policy coverage ID: %d exists for policy ID: %d
|POL-519|Database error occurred while retrieving policy coverages for policy ID: %d
|POL-520|Database error occurred while retrieving policy coverage ID: %d
|POL-521|Database error occurred while creating policy coverage for policy ID: %d
|POL-522|Database error occurred while updating policy coverage ID: %d for policy ID: %d
|POL-523|Database error occurred while deleting policy coverage ID: %d
|POL-524|Database error occurred while checking if policy reinsurance Cession ID: %d exists for policy ID: %d
|POL-525|Database error occurred while retrieving policy reinsurance cessions for policy ID: %d
|POL-526|Database error occurred while retrieving policy reinsurance Cession ID: %d for policy ID: %d
|POL-527|Database error occurred while creating policy reinsurance cession for policy ID: %d
|POL-528|Database error occurred while updating policy reinsurance ID: %d for policy ID: %d
|POL-529|Database error occurred while deleting policy reinsurance ID: %d for policy ID: %d
|POL-530|Database error occurred while checking if policy condition ID: %d exists for policy ID: %d
|POL-531|Database error occurred while checking if policy condition ID: %d exists
|POL-532|Database error occurred while retrieving policy conditions for policy ID: %d
|POL-533|Database error occurred while retrieving policy condition ID: %d
|POL-534|Database error occurred while creating policy condition for policy ID: %d
|POL-535|Database error occurred while updating policy condition ID: %d for policy ID: %d
|POL-536|Database error occurred while deleting policy condition ID: %d
|POL-537|Database error occurred while checking if policy condition Criteria ID: %d exists for condition ID: %d
|POL-538|Database error occurred while retrieving policy condition criterias for condition ID: %d
|POL-539|Database error occurred while retrieving policy condition Criteria ID: %d for condition ID: %d
|POL-540|Database error occurred while retrieving condition criteria list by condition ID: %d
|POL-541|Database error occurred while creating policy condition criteria for condition ID: %d
|POL-542|Database error occurred while updating policy condition Criteria ID: %d for condition ID: %d
|POL-543|Database error occurred while deleting policy condition Criteria ID: %d for condition ID: %d
|POL-544|Database error occurred while getting policy condition count for policy ID: %d for condition type: %d
|POL-545|Error occurred. Only one policy Restriction allowed per policy for policy ID: %d
|POL-546|Database error occurred while checking condition name: %s is unique for policy ID: %d
|POL-547|The condition names must be unique within each policy
|POL-548|Condition can't have parent condition which is child of another condition
|POL-549|Database error occurred while getting list of policy conditions for account ID: %d
|POL-550|Database error occurred while back filling policy conditions for condition ID: %d
|POL-551|%s
|POL-553|Invalid input. Line of business does not exist
|POL-554|Database error occurred while retrieving policy conditions list
|POL-555|Database error occurred while retrieving policy conditions metrics for condition ID: %d
|POL-556|policy coverage label may not be empty and label ID should be valid
|POL-557|policy condition name may not be null or empty
|POL-558|Illegal policy condition type id
|POL-559|Condition cannot have an empty parent condition
|POL-560|Duplicate policy ID %s found in input
|POL-561|policy condition name exceeds the allowed length
PRODUCER
| Error Code | Message |
|---|---|
PRODUCER-401 | Database error occurred, producer does not exists |
PRODUCER-404 | %s |
PRODUCER-406 | %s |
PRODUCER-409 | %s |
PRODUCER-501 | Database error occurred while loading producers, reason : %s |
PRODUCER-502 | Database error occurred while creating producer, reason : %s |
PRODUCER-503 | Database error occurred while updating producer with ID: %s, reason : %s |
PRODUCER-504 | Database error occurred while deleting producer with ID: %s, reason : %s |
PRODUCER-505 | Database error occurred duplicate producer, producer already exists |
PRODUCER-506 | Validation error, producer ID cannot be null or empty. |
PRODUCER-508 | Validation error, producer, some of the String field has exceeded allowed length. |
PRO
Profiles errors.
| Error Code | Message |
|---|---|
PRO-001 | Invalid value: %s, passed for category parameter |
PRO-500 | Database Error occurred while retrieving model profiles |
PRO-501 | Error occurred while retrieving service information for driver: %s |
REINS_CESSION
| Error Code | Message |
|---|---|
REINS_CESSION-001 | Layer Number should be between 1 and 99 |
REINS_CESSION-002 | Priority should be between 1 and 127 |
REINS_CESSION-003 | treaty ID must be greater than zero when reinsurance cession type provided is %s |
REINS_CESSION-004 | FacReinsurer ID must not be null or blank when reinsurance cession type provided is %s |
RENAME
| Error Code | Message |
|---|---|
RENAME-001 | Attempt to acquire lock failed. Lock has been acquired by a different process. |
RENAME-002 | We cannot process this job because a job on this result is already running. |
RENAME-003 | Sorry, we encountered an error while running rename-analysis. Try again, and contact Moody's RMS Support at [email protected] if this still does not work. |
RENAME-004 | Invalid argument for %s |
RENAME-005 | Sorry, the new analysis name format is invalid |
RERUN-EP
| Error Code | Message |
|---|---|
RERUN-EP-001 | Invalid argument for %s |
RERUN-EP-002 | Unable to retrieve metadata for %s |
RERUN-EP-003 | Sorry, you can recalculate EP metrics on %s engine type(s) only. Enter a non-HD or non-simulated DLM analysis ID |
RERUN-EP-004 | Unsupported analysis type. Rerun Ep is only supported on %s analysis type(s) |
RERUN-EP-005 | Sorry, we encountered an error while submitting the rerun Ep job. Try again, and contact Moody's RMS Support if this still does not work. |
RERUN-EP-006 | Sorry, you can not perform Rerun Ep on %s engine sub type. |
RERUN-EP-007 | Unsupported exposure type. Rerun Ep is not supported for account analyses. |
REPORT
| Error Code | Message |
|---|---|
REPORT-001 | Sorry, we encountered an error searching for reports. Try again, and contact Moody's RMS Support if this still does not work. |
REPORT-002 | Sorry, we encountered an error creating this report. Try again, and contact Moody's RMS Support if this still does not work. |
REPORT-003 | Sorry, the exposure type %s is not valid for search reports. Valid exposure types are ACCOUNT and PORTFOLIO. |
REPORT-004 | Sorry, we encountered an error while processing the data submitted for the reports. Try again, and contact Moody's RMS Support if this still does not work. |
REPORT-005 | Sorry, we can't find Report ID: %s for EDM: %s. Either it doesn't exist or you don't have access to it. |
REPORT-006 | Sorry, we encountered an error while updating the report information. Try again, and contact Moody's RMS Support if this still does not work. |
RETENTION
| Error Code | Message |
|---|---|
RETENTION-501 | Database error occurred while creating data retention |
RETENTION-502 | Database error occurred while retrieving expired data retentions |
RETENTION-503 | Database error occurred while archiving data retention |
RG
Resource group errors.
|RG-001|Sorry, this could be an error on our end. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work.|
|RG-002|You cannot run the API call because you cannot access the Risk Modeler default resource group. Check with your Intelligent Risk Platform administrator to find out if there is a default resource group for Risk Modeler and ensure you have access to it.|
|RG-003|The resource group ID %s is invalid. Please check and try again, and contact Moody's RMS Support at [email protected] if this still doesn't work.|
|RG-004|The resource group ID not provided in request header. Please check and try again.|
|RG-005|The provided resource group ID %s cannot be used with this API. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work.|
|RG-006|Sorry, you cannot perform this operation because you don't have to access to job resource group.|
S2S
| Error Code | Message |
|---|---|
S2S-001 | Missing S2S token |
SERVER_INFO
| Error Code | Message |
|---|---|
SERVER_INFO-500 | Failed to find the requested server info |
SERVER_INFO-501 | Failed to insert new server info record |
SERVER_INFO-502 | Failed to update server info record |
SERVER_INFO-503 | Failed to find server info records for tenant |
SERVER_INFO-504 | Failed to find server info records for tenant namespace %s |
SERVER_INFO-505 | Failed to delete server info record |
SERVER_INFO-506 | The server name %s that you provided doesn't match an existing server name. Check the server name for misspellings and try again. |
SERVER_INFO-507 | Invalid Operator or expression in condition %s. Please check the query and try again. |
SERVER_INFO-508 | The server ID %d that you provided doesn't match an existing server ID. Check the server ID and try again. |
SETUP
| Error Code | Message |
|---|---|
| SETUP-500 | Failed to read from setup jobs table. |
| SETUP-501 | Failed to insert data into setup jobs table. |
SIMULATE-LOSSES
| Error Code | Message |
|---|---|
SIMULATE-LOSSES-001 | We encountered an error retrieving the simulation set with ID %d. Try again. If this still doesn't work, contact Moody's RMS Support. |
SIMULATE-LOSSES-002 | Sorry, we encountered an error while simulating ELT to PLT for this analysis. Try again, and contact Moody's RMS Support if this still does not work. |
SIMULATE-LOSSES-003 | You cannot simulate these ELT-based results to a PLT because the analysis type is invalid. The results must be for individual (not group), DLM, portfolio-level, EP analyses. |
SIMULATE-LOSSES-004 | You cannot simulate these results from ELT- to PLT-based results because these results have already been simulated to a PLT. |
SIMULATE-LOSSES-005 | Enter a valid value greater than zero for the event rate scheme ID for the selected DLM analysis. |
SIMULATE-LOSSES-006 | Enter a valid value greater than zero for the simulation set ID for the selected DLM analysis. |
SIMULATE-LOSSES-007 | Enter a valid value greater than zero for the simulation periods for the selected DLM analysis. |
SIMULATE-LOSSES-008 | You have entered an invalid simulation set ID for the peril model region. See the Simulation Set table in Risk Modeler Reference Data for a list of valid IDs. |
SMTP
| Error Code | Message |
|---|---|
SMTP-500 | SMTP host was not found |
SMTP-501 | SMTP port was not found |
SMTP-502 | Invalid SMTP credentials |
STEPPOL
| Error Code | Message |
|---|---|
STEPPOL-000 | Sorry, looks like something might be wrong at our end. Try this again, and if it still doesn't work, contact Moody's RMS Support at support.rms.com. |
STEPPOL-001 | Step policy Effective date must be less than Step policy Expiration Date. |
STEPPOL-002 | Step policy %d was not found |
STEPPOL-003 | Parent account ID: %d was not found for Step policy ID: %d |
STEPPOL-004 | User does not have sufficient permissions on Step policy ID: %d |
STEPPOL-404 | %s |
STEPPOL-406 | %s |
STEPPOL-409 | %s |
STEPPOL-500 | Database error occurred while updating Step policy ID: %d |
STEPPOL-501 | Database error occurred while creating Step policy |
STEPPOL-502 | Database error occurred while retrieving Step policy ID: %d |
STEPPOL-503 | Database error occurred while loading parent account information for Step policy ID: %d |
STEPPOL-504 | Database error occurred while deleting Step policy ID: %d |
STEPPOL-505 | Database error occurred while searching policies |
STEPPOL-506 | Database error occurred while copying Step policy ID: %d |
STEPPOL-507 | Step order ID %d received for creation already exists |
STEPPOL-508 | Maximum step order ID %s exceeded |
STEPPOL-509 | Duplicate Step policy ID %s found in input |
STEP-TOOL
| Error Code | Message |
|---|---|
STEP-TOOL-001 | Invalid argument for %s |
STEP-TOOL-002 | Must include at least one analysis |
STEP-TOOL-003 | Sorry, we encountered an error while submitting the Step-Tool job. Try again, and contact Moody's RMS Support if this still does not work. |
STEP-TOOL-004 | Unsupported analyses %s. Only DLM Portfolio EP and ALM analyses are supported. |
TENANT
| Error Code | Message |
|---|---|
TENANT-001 | Could not parse URL, reason %s |
TENANT-002 | Tenant file was not found |
TENANT-003 | Tenant file cannot be read |
TENANT-004 | Tenant ID in the request does not match with the token details |
TENANT-005 | Database error occurred while retrieving RDM names |
TENANT-006 | The key %s does not have correct db properties format |
TENANT-007 | The key %s already exists in the database |
TENANT-008 | The property(s) are missing the primary key |
TENANT-009 | The EDM db already exists |
TENANT-011 | Invalid EDM database type |
TENANT-012 | Database error occurred while adding edm db properties |
TENANT-013 | The tenant edm keys do not match |
TENANT-014 | The sql server db should have this format %s |
TENANT-015 | Database error occurred while retrieving tenant database information for tenant ID %s |
TENANT-016 | Database credentials cannot be null or empty |
TENANT-017 | Given destination database credentials are invalid. Could not connect to the database. |
TENANT-018 | Given source database credentials do not match with system's database credentials |
TENANT-019 | Source and destination database servers cannot be same |
TENANT-020 | This feature is not enabled for your organization: %s. Contact your RMS Account Manager about enabling this. |
TENANT-021 | This feature is not supported for tenants with UDS support enabled. |
TENANT-022 | RDS server %s already exists |
TENANT-023 | DB server migration allowed only between RDS server |
TREATY
| Error Code | Message |
|---|---|
TREATY-001 | treaty with ID: %d was not found |
TREATY-002 | treaty with ID: %d and Line of business with ID:%d was not found |
TREATY-401 | treaty Effective date cannot be null or empty |
TREATY-402 | treaty Expire date cannot be null or empty |
TREATY-403 | Invalid treaty effective date format. Expected: yyyy-MM-ddTHH:mm:ssZ |
TREATY-404 | Invalid treaty expire date format. Expected: yyyy-MM-ddTHH:mm:ssZ |
TREATY-405 | treaty expiry date cannot be before effective date |
TREATY-406 | An hours clause is required before you add a radius clause |
TREATY-407 | %s |
TREATY-408 | %s |
TREATY-409 | %s |
TREATY-410 | Some of the selected treaties are not applicable to the given exposure. Please select applicable treaties and try again. |
TREATY-411 | Aggregate Limit and Aggregate Deductible are not applicable for non-portfolio treaties. |
TREATY-412 | %s |
TREATY-500 | Database error occurred while checking loading treaties for Exposure type:%s and treaty type:%s |
TREATY-501 | Database error occurred while loading treaty with treatyId: %d |
TREATY-502 | Database error occurred while checking loading policy level treaties for account ID:%d and policy ID:%d |
TREATY-503 | Database error occurred while checking loading location level treaties for account ID:%d |
TREATY-504 | Database error occurred while creating new treaty with name: %s |
TREATY-505 | Database error occurred while updating treaty with treatyId: %d |
TREATY-506 | Database error occurred while deleting treaty with treatyId: %d |
TREATY-507 | Database error occurred while searching treaties with optional filters |
TREATY-508 | Database error occurred while saving treaty lob with treaty ID: %d |
TREATY-509 | Database error occurred while deleting treaty lob with treaty ID: %d |
TREATY-510 | Database error occurred while get treaty lob with treaty ID: %d |
TREATY-511 | Database error occurred while checking if treaty ID: %d exists |
TREATY-512 | Database error occurred while checking if treaty ID: %d and Line of business with ID: %d exists |
TREATY-513 | treaty with ID: %d and Line of business with ID: %d already exists |
TREATY-514 | Database error occurred duplicate treaty; treaty already exists |
TREATY-515 | Database error occurred while creating treaty with number: %s, reason : cedant with ID: %s was not found |
TREATY-516 | Database error occurred while creating treaty with Number: %s, reason : Producer with ID: %s was not found |
TREATY-517 | Sorry, we encountered an error converting currencies for treaty with ID: %d. Try again, and contact Moody's RMS Support if this still does not work. |
TREATY-518 | Invalid treaty Number |
TREATY-519 | Covered percentage must be between 0 and 100 |
TREATY-520 | Placed percentage must be between 0 and 100 |
TREATY-521 | Share percentage must be between 0 and 100 |
TREATY-522 | Retention percentage must be between 0 and 100 |
TREATY-523 | Reinstatement Charge Percentage must be between 0 and 1000 |
TREATY-524 | Per risk limit must be a positive number |
TREATY-525 | Occurrence limit must be a positive number |
TREATY-526 | Attachment point must be a positive number |
TREATY-527 | Premium must be a positive number |
TREATY-528 | Number of reinstatements must be between 0 and 99 |
TREATY-529 | Invalid treaty Type |
TREATY-530 | Inuring priority must be between 1 and 127 |
TREATY-531 | Invalid attachment basis |
TREATY-532 | Invalid exposure level |
TREATY-533 | Invalid exposure level for Quota Share treaty type |
TREATY-534 | Invalid exposure level for Working Excess treaty type |
TREATY-535 | Invalid Exposure Level for Surplus Share treaty type |
TREATY-536 | Invalid treaty Name |
TREATY-537 | Database error occurred while getting all treaty lobs |
TREATY-538 | Occurrence Limit must be greater than zero |
TREATY-539 | %s |
TREATY-540 | Error occurred while inserting a rdm treaty mapping data for ID %d |
TREATY-541 | Error occurred while fetching the edm treaty ID mapping data for ID %d |
TREATY-542 | Database error occurred while loading next treaty ID |
TREATY-543 | Database error occurred while checking if treaty Number: %s exists |
TREATY-544 | Database error occurred while checking if treaty with ID: %d and Number: %s exists |
TREATY-545 | Error occurred because the cat treaty: %d does not exist |
TREATY-546 | Aggregate Deductible must be greater than or equal to zero |
TREATY-547 | Aggregate Limit must be greater than or equal to zero |
TREATY-548 | Sorry, we encountered an error copying treaty with treatyId: %d. Try again, and contact Moody's RMS Support if this still does not work. |
TREATY-549 | Sorry, we encountered an error getting list of loss occurrences for treatyId: %d. Try again, and contact Moody's RMS Support if this still does not work. |
TREATY-550 | Sorry, we encountered an error getting loss occurrence with ID: %d for treaty with treatyId: %d. Try again, and contact Moody's RMS Support if this still does not work. |
TREATY-551 | Sorry, we encountered an error inserting loss occurrence for treatyId: %d. Try again, and contact Moody's RMS Support if this still does not work. |
TREATY-552 | Sorry, we encountered an error updating loss occurrence with ID: %d for treaty with treatyId: %d. Try again, and contact Moody's RMS Support if this still does not work. |
TREATY-553 | Sorry, we encountered an error deleting loss occurrence with ID: %d. Try again, and contact Moody's RMS Support if this still does not work. |
TREATY-554 | Sorry, we encountered an error getting treaties for analysis. Try again, and contact Moody's RMS Support if this still does not work. |
TREATY-555 | Inuring Priority must be 1 or 2 |
TREATY-556 | Sorry, we encountered an error getting treaties for aggregate portfolio ID: %d. Try again, and contact Moody's RMS Support if this still does not work. |
TREATY-557 | Database error occurred while checking if treaties are present for analysis ID(s): %s |
TREATY-558 | Sorry, we encountered a database error while inserting the LOB(s) of treaties for treaty ID: %d |
TREATY-559 | Sorry, we encountered a database error while fetching the LOB(s) for treaty ID: %d |
TREATY-560 | Database error occurred while fetching number of exposures for exposure type: TREATY. |
TREATY-561 | treaty currency code cannot be null or empty. |
TREATY-562 | Duplicate treaty number found in input. |
TREATY-563 | Duplicate treaty ID %s found in input. |
TREATY-564 | treaty Number %s already exists for treaty ID %s. |
TREATY-565 | Database error occurred while converting currency of treaty with ID: %d due to invalid values in the specified currency scheme. Please verify your currency scheme and try again, and contact Moody's RMS Support if this still does not work. |
UNDERWRITER
| Error Code | Message |
|---|---|
UNDERWRITER-401 | Database error occurred, underwriter does not exist |
UNDERWRITER-402 | Database error occurred while loading underwriters, reason : %s |
UNDERWRITER-404 | %s |
UNDERWRITER-406 | %s |
UNDERWRITER-409 | %s |
UNDERWRITER-502 | Database error occurred while creating underwriter, reason : %s |
UNDERWRITER-503 | Database error occurred while updating underwriter with ID: %d, reason : %s |
UNDERWRITER-504 | Database error occurred while deleting underwriter with ID: %d, reason : %s |
UNDERWRITER-505 | Database error occurred duplicate underwriter, underwriter already exists |
UNDERWRITER-508 | Validation error, underwriter, the name field has exceeded allowed length. |
UNDERWRITER-509 | Database error occurred while checking if underwriter exists : reason %s |
UNIFIED-DATA-STORE
Data Bridge error messages.
| Error Code | Message |
|---|---|
UNIFIED-DATA-STORE-001 | Database error occurred: %s |
UNIFIED-DATA-STORE-002 | Failed to create database. %s. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
UNIFIED-DATA-STORE-003 | Failed to restore database. %s. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
UNIFIED-DATA-STORE-004 | Failed to delete database. %s. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
UNIFIED-DATA-STORE-005 | Failed to attach database. %s. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
UNIFIED-DATA-STORE-006 | Failed to backup database. %s. Try again, and contact Moody's RMS Support at [email protected] if this still doesn't work. |
UPLOAD
| Error Code | Message |
|---|---|
UPLOAD-001 | Could not parse URL, reason %s |
UPLOAD-002 | ImportSource could not be found upload ID: %s |
UPLOAD-003 | Data source name already exists |
UPLOAD-004 | MDF File upload operation not permitted on RDS DB Store |
UPLOAD-005 | Upload ID %s is not valid. It should be in UUID format. |
UPLOAD-006 | Server name can't be empty for import rdm from DB server |
UPLOAD-007 | Invalid server name %s for import rdm from DB server. |
UTIL
| Error Code | Message |
|---|---|
UTIL-501 | An error occurred while writing the object as json |
UTIL-502 | An error occurred converting the object |
VER
| Error Code | Message |
|---|---|
VER-001 | Database error occurred while retrieving version, reason : %s |
WORKERSCOMP
| Error Code | Message |
|---|---|
WORKERSCOMP-401 | Database error occurred, injury cost scheme does not exists |
WORKERSCOMP-502 | Database error occurred while saving injury cost scheme for database with ID: %d |
WORKFLOW
| Error Code | Message |
|---|---|
WORKFLOW-400 | The quota for the user-defined workflow should not exceed the tenant's Quota entitlements |
WORKFLOW-401 | The workflow DAG should define at least one operation |
WORKFLOW-402 | The workflow DAG should have no-cycles |
WORKFLOW-403 | Each label in the workflow should be unique identifying single operation |
WORKFLOW-404 | Invalid batch API input |
WORKFLOW-405 | Failed to trigger batch API job |
WORKFLOW-406 | This workflow uses an invalid dependency labels %s. Check that all the 'dependsOn' statements refer to valid labels |
WORKFLOW-407 | This workflow uses an invalid operation. Check that all operations has an input field |
WORKFLOW-408 | This workflow uses an invalid operation %s. Valid operations are geohaz, process, group or a valid Risk Modeler API URL |
WORKFLOW-409 | Operation %s contains invalid ID: %s. ID must be greater than or equal to 1. |
WORKFLOW-501 | Workflow service returned an error while submitting workflow ID: %s, reason : %s |
WORKFLOW-502 | Workflow service returned an error while submitting workflow: %s |
WORKFLOW-503 | Failed to get status for workflow ID: %s |
WORKFLOW-504 | Failed to get detail for workflow ID: %s |
WORKFLOW-505 | Failed to save result for workflow ID: %s |
WORKFLOW-506 | Failed to cancel workflow ID: %s |
WORKFLOW-507 | Failed to get list of workflows |
WORKFLOW-508 | Invalid date format: %s |
WORKFLOW-509 | Invalid status parameter: %s |
WORKFLOW-510 | Invalid workflow type parameter: %s |
WORKFLOW-511 | Invalid workflow ID: %s |
WORKFLOW-512 | Invalid sort attributes: %s |
WORKFLOW-513 | Invalid date, from date cannot be greater than to date |
WORKFLOW-514 | Failed to get the list of users: %s |
WORKFLOW-515 | Status for workflow ID %s is %s. You cannot cancel a job with this status. |
WORKFLOW-516 | Failed to get tenant queues |
WORKFLOW-517 | Failed to create tenant queue |
WORKFLOW-518 | Sorry, we encountered an error trying to get the workflow. Try again, and contact Moody's RMS Support if this still does not work. |
WORKFLOW-519 | Sorry, we encountered an error trying to get the job. Try again, and contact Moody's RMS Support if this still does not work. |
WORKFLOW-520 | No workflow exists for client ID: %s |
WORKFLOW-521 | Sorry, we cannot process the input. The type parameter is required if any of the operations use the enum values of process, geohaz or group. |
WORKFLOW-522 | Failed to upload %s body to S3. |
WORKFLOW-523 | Failed to get job input from S3: %s |
WORKFLOW-524 | Failed to create clean up task: %s |