generated: '2026-07-25' method: searched source: https://developer.rms.com/platform/docs/custom-error-codes docs: https://developer.rms.com/platform/docs/custom-error-codes format: vendor-error-code note: Moody's RMS Platform APIs do not use RFC 9457 problem+json. Application errors are returned as a JSON object with code, message and logId. The code is a domain prefix plus a number (for example ACCT-001). Message strings use %d and %s placeholders that the API substitutes at runtime. Captured verbatim from the published Custom Error Codes reference. envelope: media_type: application/json fields: - field: code type: string description: 'Internal error code: a domain prefix that identifies the error type (e.g. INT) plus a number identifying the specific error (e.g. 999).' - field: message type: string description: Error message describing the cause of the error, sometimes including details or resolution steps. - field: logId type: string description: ID of the error in the response log. example: code: INT-999 message: The resource ID is not specified. logId: e5c4187b4deee9c09 http_status_codes: docs: https://developer.rms.com/platform/docs/http-status-codes note: Platform APIs use standard HTTP response status codes as defined in RFC 9110. counts: domains: 106 codes: 2125 domains: - domain: ACCT count: 48 codes: - code: ACCT-001 message: We could not find account %d in this EDM. - code: ACCT-002 message: Sorry, you do not have access permissions for account %d. Check with your Administrator about getting access. - code: ACCT-003 message: 'Processing or updating Account Id: %d not permitted since the account is being processed. Job id: %d' - code: ACCT-004 message: No geocoded locations exist in account with id %d and number %s. Geocode this account before you run an analysis. - code: ACCT-005 message: 'Ensure at least one location is geocoded before committing Account Id: %d' - code: ACCT-006 message: 'No results available. Analysis Job Id: %d failed for Account Id: %d' - code: ACCT-007 message: 'Currently processing Account ID: %d. Account cannot be processed or updated while it is in the Commit queue. Job ID: %d' - code: ACCT-008 message: '%s' - code: ACCT-404 message: '%s' - code: ACCT-405 message: '%s' - code: ACCT-406 message: 'Invalid Account input: The field %s value is not in the correct UUID format.' - code: ACCT-500 message: Sorry, we encountered an error retrieving account %d. Try again, and contact Support if this still does not work. - code: ACCT-501 message: Sorry, we encountered an error checking if account %d exists. Try again, and contact Support if this still does not work. - code: ACCT-502 message: Sorry, we encountered an error creating this account. Try again, and contact Support if this still does not work. - code: ACCT-503 message: 'Database error occurred while retrieving account by Link Id: %s' - code: ACCT-504 message: Sorry, we encountered an error retrieving information about account %d. Try again, and contact Support if this still does not work. - code: ACCT-505 message: Sorry, we encountered an error deleting account %d. Try again, and contact Support if this still does not work. - code: ACCT-506 message: Sorry, we encountered an error saving the changes for account %d. Try again, and contact Support if this still does not work. - code: ACCT-507 message: Sorry, we encountered an error retrieving geographic information for account %d. Try again, and contact Support if this still does not work. - code: ACCT-508 message: Sorry, we encountered an error copying account %d. Try again, and contact Support if this still does not work. - code: ACCT-509 message: Database error occurred while mapping account id &d with user %d - code: ACCT-510 message: 'Database error occurred while saving account details for Account Id: %d' - code: ACCT-511 message: Sorry, we encountered an error searching for accounts. Try again, and contact Support if this still does not work. - code: ACCT-512 message: Sorry, we encountered an error looking up permissions for account %d. Try again, and contact Support if this still does not work. - code: ACCT-514 message: Sorry, we encountered an error retrieving geocoding information for one or more locations in account %d. Try again, and contact Support if this still does not work. - code: ACCT-515 message: Sorry, we encountered an error exporting account %d to the EDM you selected. Try again, and contact Support if this still does not work. - code: ACCT-516 message: Sorry, we encountered an error checking the geocode status of account %d. Try again, and contact Support if this still does not work. - code: ACCT-517 message: Sorry, we encountered an error for account %d matching locations to policy special conditions. Try again, and contact Support if this still does not work. - code: ACCT-518 message: 'Database error occurred while fetching number of exposures for exposure type: ACCOUNT.' - code: ACCT-519 message: '%s' - code: ACCT-520 message: 'Error occurred with internal status code: %d while geocoding Account Id: %d' - code: ACCT-531 message: 'Error occurred while retrieving reporting services for Account Id: %d. No services found.' - code: ACCT-532 message: 'Invalid output generated while processing Account Id: %d' - code: ACCT-533 message: 'Process Account failed for Account Id: %d. %s' - code: ACCT-534 message: 'Geocode Account failed for Account Id: %d. %s' - code: ACCT-535 message: 'Invalid output generated while geocoding Account Id: %d' - code: ACCT-536 message: 'Retrieve Reports failed for Account Id: %d. %s' - code: ACCT-537 message: 'Invalid output generated while retrieving reports for Account Id: %d' - code: ACCT-538 message: 'Sorry, we encountered an error converting currencies for account with Id: %d. Try again, and contact Support if this still does not work.' - code: ACCT-539 message: Failed to update Account metrics - code: ACCT-540 message: More than one location in account %d has latitude %f and longitude %f. Two locations in an account cannot have the same coordinates. - code: ACCT-541 message: No locations in account %d have latitude %f and longitude %f. Check the coordinates or geocode the account again. - code: ACCT-542 message: Sorry, we encountered an error performing a bulk edit on accounts for portfolio %d. Try again, and contact Support if this still does not work. - code: ACCT-543 message: 'Account id %d does not exist for %s number: %s' - code: ACCT-544 message: No accounts found - code: ACCT-545 message: Duplicate Account id %s found in input - code: ACCT-546 message: '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 Support if this still does not work.' - code: ACCT-547 message: Invalid Stamp date or Create date specified for %s operation on account %s - domain: ACCU count: 5 codes: - code: ACCU-001 message: Accumulation details not found - code: ACCU-002 message: Forbidden - code: ACCU-003 message: Sorry, we encountered an error while running delete analysis. Try again, and contact Support at `RMSSupport@moodys.com` if this still does not work. - code: ACCU-004 message: You are not authorized to perform this operation on the accumulation analysis. This may be due to an expired token, invalid credentials, or insufficient permissions. Verify your authorization and try again, or contact your administrator. - code: ACCU-500 message: 'Database error occurred while retrieving accumulation details for Portfolio Id: %d' - domain: ACMI count: 19 codes: - code: ACMI-001 message: The reference (portfolio) analysis RI ID could not be resolved in UDS. | `NOT_FOUND` - code: ACMI-002 message: The marginal (account) analysis RI ID could not be resolved in UDS. | `NOT_FOUND` - code: ACMI-003 message: Caller does not have access to the requested resource group. | `FORBIDDEN` - code: ACMI-004 message: Request is missing or carries an invalid auth token. | `UNAUTHORIZED` - code: ACMI-400 message: Reference analysis was not run with the Accumulation engine. | `BAD_REQUEST` - code: ACMI-401 message: Reference analysis exposure type is not supported for accumulation marginal impact. | `BAD_REQUEST` - code: ACMI-402 message: Marginal analysis was not run with the Accumulation engine. | `BAD_REQUEST` - code: ACMI-403 message: Marginal analysis exposure type is not supported for accumulation marginal impact. | `BAD_REQUEST` - code: ACMI-404 message: The supplied currency object could not be validated against DataStore. | `BAD_REQUEST` - code: ACMI-405 message: Reference analysis is not a single-event accumulation analysis type. | `BAD_REQUEST` - code: ACMI-406 message: Marginal analysis is not a single-event accumulation analysis type. | `BAD_REQUEST` - code: ACMI-407 message: Reference and marginal analyses were run with different model profiles. | `BAD_REQUEST` - code: ACMI-408 message: One or more tag IDs are not accessible to the current user. | `BAD_REQUEST` - code: ACMI-409 message: The reference analysis ID and marginal analysis ID must not be the same. | `BAD_REQUEST` - code: ACMI-500 message: Unexpected error while submitting the job to Analytics Engines. | `INTERNAL_SERVER_ERROR` - code: ACMI-501 message: Analytics Engines returned 404 (wrong path, not deployed, or route not registered). | `BAD_GATEWAY` - code: ACMI-502 message: Analytics Engines returned 400 (rejected payload or business validation). | `BAD_REQUEST` - code: ACMI-503 message: Analytics Engines returned 403. | `FORBIDDEN` - code: ACMI-504 message: '| `INTERNAL_SERVER_ERROR`' - domain: AGGEXP count: 11 codes: - code: AGGEXP-401 message: Sorry, we could not find aggregate exposure %d in this EDM. - code: AGGEXP-500 message: Sorry, we encountered an error on our end. Try saving changes for aggregate exposure %d again, and contact Support if this still does not work. - code: AGGEXP-501 message: Sorry, we encountered an error on our end. Try creating this aggregate exposure again, and contact Support if this still does not work. - code: AGGEXP-502 message: Sorry, we encountered an error on our end. Try retrieving aggregate exposure %d again, and contact Support if this still does not work. - code: AGGEXP-503 message: Sorry, we encountered an error on our end. Try searching for aggregate exposures again, and contact Support if this still does not work. - code: AGGEXP-504 message: Sorry, we encountered an error on our end. Try deleting aggregate exposure %d again, and contact Support if this still does not work. - code: AGGEXP-505 message: Sorry, we encountered an error on our end. Try copying aggregate exposure %d again, and contact Support if this still does not work. - code: AGGEXP-506 message: Sorry, we encountered an error on our end finding aggregate exposure %d. Try again, and contact Support if this still does not work. - code: AGGEXP-507 message: Sorry, we encountered an import error on our end. Try again, and contact Support if this still does not work. - code: AGGEXP-508 message: Sorry, looks like you tried to import duplicate records for aggregate portfolio %s. Please check your ALM import request and try again. - code: AGGEXP-509 message: Sorry, country code and resolution can not be null or empty. - domain: AGGPORT count: 22 codes: - code: AGGPORT-401 message: We could not find aggregate portfolio %d in this EDM. - code: AGGPORT-402 message: We were unable to save the aggregate portfolio because we could not find cedant %s in this EDM. - code: AGGPORT-404 message: '%s' - code: AGGPORT-405 message: '%s' - code: AGGPORT-406 message: Peril code must not be null. - code: AGGPORT-500 message: Sorry, we encountered an error saving the changes for aggregate portfolio %d. Try again, and contact Support if this still does not work. - code: AGGPORT-501 message: Sorry, we encountered an error creating this aggregate portfolio. Try again, and contact Support if this still does not work. - code: AGGPORT-502 message: Sorry, we encountered an error retrieving aggregate portfolio %d. Try again, and contact Support if this still does not work. - code: AGGPORT-503 message: Sorry, we encountered an error searching for aggregate portfolios. Try again, and contact Support if this still does not work. - code: AGGPORT-504 message: Sorry, we encountered an error deleting aggregate portfolio %d. Try again, and contact Support if this still does not work. - code: AGGPORT-505 message: Sorry, we encountered an error copying aggregate portfolio %d. Try again, and contact Support if this still does not work. - code: AGGPORT-506 message: Sorry, we encountered an error checking if aggregate portfolio %d exists. Try again, and contact Support if this still does not work. - code: AGGPORT-507 message: Sorry, we encountered an error while submitting the convert currency job. Try again, and contact Support if this still does not work. - code: AGGPORT-508 message: Sorry, we encountered an error retrieving information about aggregate portfolio %d. Try again, and contact Support if this still does not work. - code: AGGPORT-509 message: Sorry, we encountered an error while submitting alm import job. Try again, and contact Support if this still does not work. - code: AGGPORT-510 message: Sorry, we encountered an error retrieving geographic information for aggregate portfolio %d. Try again, and contact Support if this still does not work. - code: AGGPORT-511 message: 'Sorry, this is an invalid resolution type: %s.' - code: AGGPORT-512 message: Sorry, we encountered an error retrieving ALM profiles for aggregate portfolio %d. - code: AGGPORT-513 message: 'Sorry, we encountered an error converting currencies for aggregate portfolio with Id: %d. Try again, and contact Support if this still does not work.' - code: AGGPORT-514 message: 'Database error occurred while fetching number of exposures for exposure type: AGGREGATE PORTFOLIO.' - code: AGGPORT-515 message: Invalid Peril code %s in request. Please use a valid peril code. - code: AGGPORT-516 message: '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 Support if this still does not work.' - domain: ALM count: 12 codes: - code: ALM-001 message: Sorry, we encountered an error while running the ALM analysis job. Try again, and contact Support if this still does not work. - code: ALM-002 message: Sorry, this profile request with peril %s isn't valid. Try again, and contact Support if this still does not work. - code: ALM-003 message: Sorry, the analysis currency %s for this ALM analysis is invalid. Specify a valid currency and try again. - code: ALM-004 message: Cannot find default event rate scheme - code: ALM-005 message: 'Invalid portfolioId: %s' - code: ALM-006 message: 'Invalid profile ids: %s' - code: ALM-007 message: Invalid treaty ids - code: ALM-008 message: Unable to load alm profiles - code: ALM-009 message: Invalid column mapping for lob %s, the position couldn't be %s - code: ALM-011 message: Invalid value for %s - code: ALM-401 message: Database error occurred, ALM does not exists - code: ALM-501 message: 'Database error occurred while loading alms, reason : %s' - domain: ANALYSIS count: 52 codes: - code: ANALYSIS-001 message: Error occurred while generating the analysis id sequence - code: ANALYSIS-002 message: 'Database error occurred while inserting rdm analysis record for id : %d' - code: ANALYSIS-003 message: 'Database error occurred while fetching the engine version for id : %d' - code: ANALYSIS-004 message: Database error occurred while inserting the record for rdm analysis perspective - code: ANALYSIS-005 message: 'Invalid analysis id : %s' - code: ANALYSIS-006 message: 'Database error occurred while fetching location AAL record for id : %d' - code: ANALYSIS-007 message: Load database connection properties error - code: ANALYSIS-008 message: The perspective code %s is invalid. Please check that your requests specify a valid perspective. - code: ANALYSIS-009 message: Perspective code %s is valid, but does not exist for analysis %d - code: ANALYSIS-010 message: Database error occurred while validating analysis and perspectives - code: ANALYSIS-012 message: Analysis ID %d is invalid. Check that your request specifies a valid analysis ID and that engine type is %s. - code: ANALYSIS-013 message: 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. - code: ANALYSIS-014 message: 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 Help Center. - code: ANALYSIS-015 message: 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 Help Center. - code: ANALYSIS-016 message: 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 Help Center. - code: ANALYSIS-017 message: Sorry, we encountered an error while submitting a post-analysis treaty editing job for analysis ID %d. Try again, and contact Support if this still does not work. - code: ANALYSIS-018 message: We encountered an error retrieving the analysis perspectives for analysis with error %s. Try again, and if this still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ANALYSIS-019 message: We encountered an error retrieving loss results for analysis %d. Try again, and if this still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ANALYSIS-020 message: Sorry, the metric type %s is not valid for analysis id %d. Valid metrics are AEP, OEP, TCE-AEP, TCE-OEP. - code: ANALYSIS-021 message: 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. - code: ANALYSIS-022 message: We encountered an error retrieving metrics. Try again, and if this still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ANALYSIS-023 message: The exposure type %d is invalid. Please check that your requests specify a valid exposure type. - code: ANALYSIS-024 message: Exposure type %d is invalid for this request. Only results on portfolio/aggregate-portfolio/account/policy are allowed. - code: ANALYSIS-025 message: Export of climate change results to RDM is not supported for HD results. - code: ANALYSIS-026 message: Sorry, the provided exposure type '%s' did not match the expected exposure type '%s'. - code: ANALYSIS-027 message: Sorry, the exposure type %s is not valid for DLM analysis. Valid exposure types are 'ACCOUNT' and 'PORTFOLIO'. - code: ANALYSIS-028 message: Sorry, the exposure type %s is not valid for model analysis. Valid exposure types are 'ACCOUNT', 'PORTFOLIO' and 'AGGPORTFOLIO'. - code: ANALYSIS-029 message: Sorry, the exposure type is missing. Please check that your request contains exposure type. - code: ANALYSIS-030 message: Sorry, the provided value for exposure type is invalid. Please check that your request contains valid exposure type. - code: ANALYSIS-031 message: Sorry, the provided value for filter condition is invalid. Please check that your request contains a valid filter condition. - code: ANALYSIS-032 message: Sorry, you can't download results for an analysis` | %d, that has been deleted. - code: ANALYSIS-033 message: Select one of the following options to export. Select one or more DLM/Group/ALM results or select one or more HD EP results. - code: ANALYSIS-034 message: You cannot export the selected analysis to RDM as PLT. This export is supported only for HD EP analyses. - code: ANALYSIS-035 message: Sorry, we encountered an error on our end while retrieving analysis details for analysis id %d. Contact Support at`RMSSupport@moodys.com`. - code: ANALYSIS-036 message: Sorry, the offset parameter must be set to 0 on older analyses. - code: ANALYSIS-037 message: Sorry, sorting this metric type is not supported. Remove the sort parameter from your request and try again. - code: ANALYSIS-038 message: Sorry, this metric type requires one granularity to be selected. Make sure there is only one granularity in your request and try again. - code: ANALYSIS-040 message: 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 Help Center for list of financial perspectives. Enter a valid metric key and try again. - code: ANALYSIS-041 message: Sorry, it looks like imported group or multi-region ALM results that you are exporting are missing required number of simulation periods. Remove the imported group/multi-region analysis from this export to proceed. - code: ANALYSIS-042 message: Post-analysis actions on an Account grouped analysis %d are not supported. - code: ANALYSIS-043 message: Sorry, the granularity type '%s' is not valid for the metric type '%s'.Check the possible granularity types in the API reference on the Developer Portal. - code: ANALYSIS-044 message: Sorry, this operation is not supported for the requested analysis. - code: ANALYSIS-045 message: Sorry, we encountered problem accessing exposureIQ API. Please contact ExposureIQ support. - code: ANALYSIS-046 message: We encountered an error retrieving metrics - %s. Please check that your request contains the right data. - code: ANALYSIS-047 message: The granularity is not supported for the metrics you requested. See the "Output Profiles" topic in the Help Center for supported granularities. - code: ANALYSIS-048 message: Sorry, the exposure type %s is not valid for this request. Use only %s level results for this to work. - code: ANALYSIS-049 message: Sorry, GET key-event-stats only support to be sorted by eventId currently. - code: ANALYSIS-050 message: Sorry, Exposure details not found in variation. - code: ANALYSIS-051 message: Export of grouped results having underlying climate change results to RDM is not supported for HD results. - code: ANALYSIS-052 message: Convert to ELT of grouped results having underlying climate change results is not supported for HD results. - code: ANALYSIS-053 message: Sorry, the provided value for exposureId is invalid. Please check that your request contains valid exposure id for the given analysis id %d. - code: ANALYSIS-054 message: Invalid location IDs. Provide up to %s comma-separated numeric location IDs. - domain: ANALYSIS_GROUP count: 33 codes: - code: ANALYSIS_GROUP-001 message: Could not parse URL, reason %s - code: ANALYSIS_GROUP-002 message: 'Database error occurred while getting a analysisGroup with groupId: %d%n' - code: ANALYSIS_GROUP-003 message: Database error occurred while getting a list of analysisGroup, reason %s - code: ANALYSIS_GROUP-004 message: Database error occurred while getting list of inconsistent treaties - code: ANALYSIS_GROUP-005 message: 'Invalid analysis group id : %s' - code: ANALYSIS_GROUP-006 message: You have entered a date using an invalid format %s. Enter dates as MM/DD/YYYY only. - code: ANALYSIS_GROUP-007 message: You have tried to group invalid results. You can group portfolio-level EP results, and you can group DLM groups. - code: ANALYSIS_GROUP-008 message: Enter a value greater than zero for the number of simulation periods for the final grouped PLT. - code: ANALYSIS_GROUP-009 message: You've selected too many results for grouping. Select a maximum of %d. - code: ANALYSIS_GROUP-010 message: Analyses details should not be empty. - code: ANALYSIS_GROUP-011 message: Select at least two results for grouping. - code: ANALYSIS_GROUP-013 message: We encountered an error during grouping. Try again, and if this still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ANALYSIS_GROUP-014 message: 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. - code: ANALYSIS_GROUP-015 message: 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 Help Center. - code: ANALYSIS_GROUP-016 message: 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 Help Center. - code: ANALYSIS_GROUP-017 message: 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. - code: ANALYSIS_GROUP-018 message: Analysis ids cannot be null or empty. - code: ANALYSIS_GROUP-019 message: Force group type must be null or INGP. - code: ANALYSIS_GROUP-020 message: Sorry, it looks like an imported group that you are adding to a group is missing required number of simulation periods. Remove the imported group from this group to proceed. - code: ANALYSIS_GROUP-021 message: Sorry, it looks like an imported HD that you are adding to a group is missing required weighted PLT. Remove the imported HD from this group to proceed. - code: ANALYSIS_GROUP-022 message: Sorry, you cannot group account analysis type with other exposure type analyses. - code: ANALYSIS_GROUP-023 message: Sorry, you cannot group HD account analysis with DLM/Group account analyses. - code: ANALYSIS_GROUP-024 message: Sorry, you cannot group Non-EP account analyses. - code: ANALYSIS_GROUP-025 message: Sorry, you cannot group account analyses with different exposure ids. - code: ANALYSIS_GROUP-026 message: Sorry, one or more account analyses are not associated with an EDM. - code: ANALYSIS_GROUP-027 message: Sorry, you cannot group account analyses belonging to different EDMs. - code: ANALYSIS_GROUP-028 message: Engine version is required for RL Group (DLM) grouping. Provide engineVersion for each region-peril in regionPerilSimulationSet. - code: ANALYSIS_GROUP-029 message: You cannot group PLTs for the same region/peril generated with different simulation sets because correlations between events may be missed. Rerun the analyses using the same simulation sets or remove analyses from the group to proceed. - code: ANALYSIS_GROUP-030 message: Underlying analyses for the same peril/region/model version have conflicting event rates. Select a consistent event rate for the group. - code: ANALYSIS_GROUP-031 message: You can only create groups with Portfolio EP HD results that were run without the "Apply Contract Dates" option. - code: ANALYSIS_GROUP-032 message: Grouping model results from different model versions is not recommended. The model version represents a major model update with new eventids and/or new event frequency. Continuing the grouping process will cause incorrect group results because events will not be correlated. We recommend resolving this conflict in the group selection before submitting. - code: ANALYSIS_GROUP-033 message: The selected simulation periods for the underlying ELTs are less than the target group simulation periods. With this selection, the simulated PLTs will be duplicated and shuffled to match the target group length, without using all available periods in the period event quantile table (PEQT). This approach loses the value of the additional periods and risks missing event correlations if grouping with another PLT that shares eventids. We recommend selecting simulation periods equal to the target group simulation periods if available. - code: ANALYSIS_GROUP-034 message: The North Atlantic Hurricane simulation set should match the US Flood HD simulation set to create a group. We recommend updating the hurricane simulation set to match the U.S. flood simulation set. This will result in hurricane losses that are different from the original analysis, but will preserve event correlation with U.S. Flood HD so the group result is correct.If you don't want the group to convert the hurricane analyses, we recommend selecting a US Flood HD model results with a simulation set that matches the hurricane simulation set. - domain: ANALYSIS_GROUP_TREATY count: 2 codes: - code: ANALYSIS_GROUP_TREATY-001 message: We encountered an error during grouping. Try again, and if this still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ANALYSIS_GROUP_TREATY-002 message: 'Database error occurred while fetching the group PATE treaties for group ids : %s.' - domain: ANALYSIS_REGIONS count: 7 codes: - code: ANALYSIS_REGIONS-001 message: We encountered an error while saving details for analysis regions %s. Try again, and if this still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ANALYSIS_REGIONS-002 message: We encountered an error while fetching analysis regions for analysis id %d. - code: ANALYSIS_REGIONS-003 message: No rate scheme id found for analysis id %d. - code: ANALYSIS_REGIONS-004 message: 'We encountered an error while deleting analysis regions record for analysis id : %d. Try again, and if this still doesn''t work, contact Support at `RMSSupport@moodys.com`.' - code: ANALYSIS_REGIONS-005 message: Analysis ID %d is missing analysis regions likely because the region information is missing from the analysis in an uploaded RDM. This action can't be performed without valid analysis regions. - code: ANALYSIS_REGIONS_HD-001 message: We encountered an error while saving details for HD analysis regions. Try again, and if this still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ANALYSIS_REGIONS_HD-002 message: We encountered an error while fetching HD analysis regions for analysis id %d. - domain: ANALYTICS count: 55 codes: - code: ANALYTICS-000 message: Sorry, looks like something might be wrong at our end. Try this again, and if it still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ANALYTICS-001 message: 'No results available. Account Id: %d not analyzed yet.' - code: ANALYTICS-500 message: 'Database error occurred while loading event losses for Report Id: %d' - code: ANALYTICS-501 message: 'Database error occurred while retrieving analysis details for Report Id: %d' - code: ANALYTICS-502 message: 'Database error occurred while retrieving analysis report status for Account Id: %d' - code: ANALYTICS-503 message: 'Database error occurred while retrieving analysis details for data source: %s' - code: ANALYTICS-520 message: 'Database error occurred while checking report count for Job Id: %d' - code: ANALYTICS-521 message: 'Database error occurred while getting EP metrics financial perspective analysis for analysis Id: %d' - code: ANALYTICS-522 message: 'Database error occurred while getting data from results store for analysis id: %d' - code: ANALYTICS-523 message: 'Database error occurred while getting statistics for analysis id: %d' - code: ANALYTICS-524 message: 'Database error occurred while getting job id for analysis id: %d' - code: ANALYTICS-525 message: Database error occurred while getting analysis id - code: ANALYTICS-526 message: Database error occurred while setting analysis status - code: ANALYTICS-527 message: 'Database error occurred while retrieving Cedants list for Report Id: %d' - code: ANALYTICS-528 message: 'Database error occurred while retrieving Treaties list for Analysis id: %d' - code: ANALYTICS-529 message: 'Database error occurred while retrieving LOBs for Treaty id: %d' - code: ANALYTICS-530 message: 'Database error occurred while retrieving perspectives for Analysis id: %d' - code: ANALYTICS-531 message: 'Database error occurred while deleting Analysis id: %d' - code: ANALYTICS-532 message: 'Database error occurred while deleting Analyses ids: %s' - code: ANALYTICS-533 message: 'Database error occurred while checking whether analysis id: %d exists or not' - code: ANALYTICS-534 message: 'We did not locate the analysis id: %d. Either it doesn''t exist or you don''t have access to it.' - code: ANALYTICS-536 message: 'Analysis id: %d not found in Result Service. Please check that your requests specify a valid Analysis ID.' - code: ANALYTICS-537 message: Sorry, we can't calculate losses for the input you provided. - code: ANALYTICS-538 message: Peril code %s is not supported for analysis summary report. Select a supported peril - code: ANALYTICS-539 message: Database error occurred while retrieving analysis details list - code: ANALYTICS-540 message: 'Database error occurred while retrieving analysis details for Exposure type: %s with Id: %d' - code: ANALYTICS-541 message: Sorry, we encountered an error trying to connect to our databases. Try again, and contact Support if this still does not work. - code: ANALYTICS-542 message: Sorry, %s analysis id %d is invalid for analysis summary report. You can run it for portfolio-level analysis - code: ANALYTICS-543 message: Database error occurred while getting analysis group info data for analysis ids - %s. - code: ANALYTICS-544 message: 'Database error occurred while retrieving analysis details : %s.' - code: ANALYTICS-545 message: Sorry, we encountered an error while fetching losses. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ANALYTICS-546 message: We encountered an error retrieving treaty information. Try again, and if this still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ANALYTICS-547 message: Sorry, looks like this analysis did not generate losses for selected perspective. - code: ANALYTICS-548 message: 'There are invalid analysis ids in: %s. Please check that your requests specify valid analysis ids' - code: ANALYTICS-549 message: Sorry, analysis id %d is invalid for the analysis summary report. You cannot run it on DLM results that have been simulated to a PLT - code: ANALYTICS-550 message: Sorry, date in analysis search query %s is invalid. Please try again with valid date - code: ANALYTICS-551 message: 'Database error occurred while retrieving analysis engine details for Analysis Id: %d' - code: ANALYTICS-552 message: Sorry, analysis id %d is invalid for analysis summary report. You cannot run it on %s engine subtype - code: ANALYTICS-553 message: Sorry, the provided ep type %s is invalid - code: ANALYTICS-554 message: Sorry, pagination operation not supported except policy - code: ANALYTICS-555 message: Sorry, filter operation for %s, %s not supported except policy - code: ANALYTICS-556 message: Sorry, %s param is only supported for exposure type policy - code: ANALYTICS-557 message: Sorry, only %s exposure type is supported when exposure id is provided - code: ANALYTICS-558 message: Sorry, only perspective type %s is allowed for exposure type %s - code: ANALYTICS-559 message: Sorry, filter operation for %s is not supported for policy - code: ANALYTICS-560 message: Sorry, perspective code not supported for HD analysis. - code: ANALYTICS-561 message: Sorry, %s not supported when exposure type policy with id specified or non-policy exposure types - code: ANALYTICS-562 message: Sorry, multiple perspective codes are only supported when Exposure Resource Type is POLICY and Exposure Resource Id is not provided - code: ANALYTICS-563 message: Sorry, %s analysis id %d is not supported for analysis summary report with peril code %s - code: ANALYTICS-564 message: 'Sorry, %s Analysis id: %d having peril: %s is not supported for analysis summary report with input peril: %s. Supported peril: %s.' - code: ANALYTICS-565 message: Additional download options are not configured correctly. %s. - code: ANALYTICS-566 message: Invalid UUID passed in query filter for search analyses - code: ANALYTICS-567 message: Invalid input provided in query filter for search analyses - code: ANALYTICS-568 message: Financial perspective codes cannot be null or empty. To find a list of valid perspectives, search for the "Financial Perspectives" topic in the help center of your IRP application. - code: ANALYTICS-569 message: This request applies only to ELT-based results. ELTs are produced by DLM/ALM analyses and by DLM/ALM groups. - domain: ARCH count: 24 codes: - code: ARCH-400 message: Archive with id %d was not found. - code: ARCH-401 message: exposureSetId cannot be provided for a databridge server with registerFlag disabled. - code: ARCH-402 message: ExposureSetName or groups cannot be passed when passing exposureSetId. - code: ARCH-404 message: The provided database is not EDM and can be restored only on DataBridge. - code: ARCH-406 message: The provided owner does not exist. - code: ARCH-407 message: 'Invalid restore request for server type: Platform and either DB type non-EDM or skip-register true' - code: ARCH-408 message: 'Cannot register for database type: non-EDM and store type: Databridge' - code: ARCH-409 message: Archives that expired cannot be restored. - code: ARCH-410 message: In order to register, the database owner should have access to the Exposure set %s. - code: ARCH-411 message: The database name is empty. Please provide a valid database name. - code: ARCH-412 message: Sorry, the expirationDate should not be before the current date. - code: ARCH-413 message: 'No action taken: The database for provided exposure does not exist, has no physical files, or is already being deleted.' - code: ARCH-414 message: The storageType is required field and must be set to permanent for an update of temporary archive. - code: ARCH-415 message: The storageType cannot be updated for an archive that is permanent. - code: ARCH-416 message: 'No action taken: There are no updates to be made on the archive with the provided input.' - code: ARCH-417 message: '%s must be greater than 0' - code: ARCH-418 message: Restore of type %s is currently not supported - code: ARCH-419 message: The request body must not be null - code: ARCH-420 message: An archive operation for this database is currently being processed. Please check its status before trying again. - code: ARCH-421 message: Sorry, this archive (ID %s) is still being created and cannot be restored yet. Wait for the archive to finish and try again, or contact Support at RMSSupport@moodys.com for assistance. - code: ARCH-500 message: Sorry, we encountered an error triggering this job. Try again, and contact Support if this still does not work. - code: ARCH-501 message: Sorry, we encountered an error getting the list of archives. Try again, and contact Support if this still does not work. - code: ARCH-502 message: Sorry, we encountered an error getting the archive with id %d. Try again, and contact Support if this still does not work. - code: ARCH-503 message: Sorry, we encountered an error updating this archive. Try again, and contact Support if this still does not work. - domain: AUTHORIZATION count: 4 codes: - code: AUTHORIZATION-401 message: You tried to make this API call with an expired API token. Ask your platform administrator for a new API token and try again. - code: AUTHORIZATION-501 message: Error getting user information - code: AUTHORIZATION-502 message: Error creating user token - code: AUTHORIZATION-503 message: Error getting tenant groups - domain: BRANCH count: 13 codes: - code: BRANCH-401 message: Database error occurred, branch does not exist - code: BRANCH-402 message: 'Database error occurred while loading branches, reason : %s' - code: BRANCH-404 message: '%s' - code: BRANCH-406 message: '%s' - code: BRANCH-409 message: '%s' - code: BRANCH-502 message: 'Database error occurred while creating branch, reason : %s' - code: BRANCH-503 message: 'Database error occurred while updating branch with Id: %d, reason : %s' - code: BRANCH-504 message: 'Database error occurred while deleting branch with Id: %d, reason : %s' - code: BRANCH-505 message: Database error occurred duplicate branch, branch already exists - code: BRANCH-506 message: Validation error, branch id cannot be null or empty. - code: BRANCH-508 message: Validation error, branch, the name field has exceeded allowed length. - code: BRANCH-509 message: 'Database error occurred while checking if branch exists : reason %s' - code: BRANCH-510 message: 'Database error occurred while checking if branch has reference in accgrp table : reason %s' - domain: CE count: 6 codes: - code: CE-001 message: 'Failed to build tenant key for: %s. Most likely tenant id was missing from thread context or environment variable.' - code: CE-002 message: 'Failed to find a value for required key: %s' - code: CE-003 message: 'Failed to build a key for configuration level: %s, and key: %s.' - code: CE-004 message: Sorry, we encountered an error while loading the configurations. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work - code: CE-005 message: Failed to build a cache for sql configuration provider. - code: CE-006 message: Failed to build a cache for tenant configuration provider. - domain: CEDANT count: 14 codes: - code: CEDANT-401 message: 'Database error occurred, cedant with Id: %s does not exist' - code: CEDANT-404 message: '%s' - code: CEDANT-406 message: '%s' - code: CEDANT-409 message: '%s' - code: CEDANT-501 message: 'Database error occurred while loading cedants, reason : %s' - code: CEDANT-502 message: 'Database error occurred while creating cedant, reason : %s' - code: CEDANT-503 message: 'Database error occurred while updating cedant with Id: %s, reason : %s' - code: CEDANT-504 message: '%s' - code: CEDANT-505 message: Error occurred while creating or updating Cedant with name %s, id %s. Cedant already exists with the same name or id. - code: CEDANT-506 message: Validation error, cedant id cannot be null or empty. - code: CEDANT-507 message: Validation error, cedant id length has to be between 1 and 20. - code: CEDANT-508 message: Validation error, cedant, some of the String field has exceeded allowed length. - code: CEDANT-509 message: 'Database error occurred while checking if cedant Id: %d exists' - code: CEDANT-510 message: 'Database error occurred while checking if cedant with Id: %d and Name: %s exists' - domain: CLIENT count: 38 codes: - code: CLIENT-001 message: 'Invalid identifier, %s : %s' - code: CLIENT-002 message: Sorry, we could not get the requested data. The input '%s' (line %d, character %d) is not valid. See the Help Center for help with query syntax. - code: CLIENT-003 message: Sorry, looks like there is a syntax error (line %d, character %d). See the "Bulk Edits-Advanced" topic in the Help Center for help with query syntax. - code: CLIENT-005 message: Sorry, we don't recognize the field '%s' - code: CLIENT-006 message: 'Unknown parser error: %s. (line %d, character %d)' - code: CLIENT-007 message: Incompatible data type for %s, expected %s but got %s - code: CLIENT-008 message: 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 Help Center for help with query syntax. - code: CLIENT-009 message: '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 Help Center for help with query syntax.' - code: CLIENT-010 message: 'Sorry, this is an invalid symbol : ''%s'' (line %d, character %d).' - code: CLIENT-011 message: 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 Help Center for help with query syntax. - code: CLIENT-012 message: Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the SET command. See the "Bulk Edits-Advanced" topic in the Help Center for help with query syntax. - code: CLIENT-013 message: Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Bulk Edits-Advanced" topic in the Help Center for help with query syntax. - code: CLIENT-014 message: Sorry, you entered an invalid value for parameter '%s' - code: CLIENT-015 message: Sorry, this currency conversion request isn't valid. Try again, and contact Support if this still does not work. - code: CLIENT-016 message: Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Account Search" topic in the Help Center for help with query syntax. - code: CLIENT-017 message: Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Portfolio Search" topic in the Help Center for help with query syntax. - code: CLIENT-018 message: Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Policy Search" topic in the Help Center for help with query syntax. - code: CLIENT-019 message: Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Step Policy Search" topic in the Help Center for help with query syntax. - code: CLIENT-020 message: Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Aggregate Portfolio Search" topic in the Help Center for help with query syntax. - code: CLIENT-021 message: Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. See the "Treaty Search" topic in the Help Center for help with query syntax. - code: CLIENT-022 message: Sorry, looks like '%s' (line %d, character %d) is an unsupported field in the WHERE command. - code: CLIENT-023 message: Sorry, looks like your query contains mismatched data type values. - code: CLIENT-024 message: 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 Help Center for help with query syntax. - code: CLIENT-025 message: Sorry, looks like there is no viable alternative at input '%s' (line %d, character %d). See the Help Center for help with query syntax. - code: CLIENT-026 message: Sorry, looks like there is %s (line %d, character %d). See the Help Center for help with query syntax. - code: CLIENT-027 message: Sorry, invalid filter. See the Help Center for help with query syntax. - code: CLIENT-028 message: Sorry, sorting allowed on only one field. See the Help Center for help with query syntax. - code: CLIENT-029 message: Sorry, invalid operator %s. See the Help Center for help with query syntax. - code: CLIENT-030 message: Sorry, IN condition is only supported for %s field. See the Help Center for help with query syntax. - code: CLIENT-031 message: Sorry, LIKE operator is only supported for %s field. See the Help Center for help with query syntax. - code: CLIENT-032 message: Sorry, this is an invalid financial perspective. See https://developer.rms.com/platform/docs/financial-perspectives for a list of valid perspective codes. - code: CLIENT-033 message: Sorry, equals operator is only supported for %s field. See the Help Center for help with query syntax. - code: CLIENT-034 message: 'Validation failed: %s' - code: CLIENT-035 message: Sorry, we could not process your filter query as it is too large or complex. Please shorten or simplify your filter criteria and try again. - code: CLIENT-400 message: Unable to read JSON - code: CLIENT-401 message: Invalid data submitted. NOTE, CLIENT-401 message is not actually used - here mainly for unit test - code: CLIENT-402 message: Sorry, we don't recognize the field %s. Check the field in the API reference on the Developer Portal. - code: CLIENT-403 message: Sorry, this is an invalid format for %s. Check the format in the API reference on the Developer Portal. - domain: CLIMATE-CHANGE count: 20 codes: - code: CLIMATE-CHANGE-001 message: To run an analysis, select at least 1 scenario with 1 time horizon, or select the 2°C warming scenario. RCP scenarios are 2.6, 4.5, 6.0, 8.5. SSP scenarios are 1-2.6, 2-4.5, 3-7.0, 5-8.5. Time horizons are between the years of 2020 and 2100 in 5-year increments. - code: CLIMATE-CHANGE-002 message: To run a climate change analysis on the selected results, %s input is required. - code: CLIMATE-CHANGE-003 message: Sorry, you can run climate change analyses on individual, portfolio-level and account-level EP analyses only. You cannot run a climate change analysis on DLM results that have been simulated to a PLT. - code: CLIMATE-CHANGE-004 message: 'Climate change analyses are supported only for results from these models: %s.' - code: CLIMATE-CHANGE-005 message: Time horizon %d is invalid. Valid time horizons are between 2020 and 2100 in 5-year increments. - code: CLIMATE-CHANGE-006 message: RCP scenario %f is invalid. Valid RCP scenarios are 2.6, 4.5, 6.0, 8.5. - code: CLIMATE-CHANGE-007 message: Sorry, we encountered an error on our end while running the climate change analysis for analysis id %d. Contact Support at`RMSSupport@moodys.com`. - code: CLIMATE-CHANGE-008 message: 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. - code: CLIMATE-CHANGE-009 message: 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 Help Center. - code: CLIMATE-CHANGE-010 message: 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 Help Center. - code: CLIMATE-CHANGE-011 message: Invalid argument for %s - code: CLIMATE-CHANGE-012 message: Unable to retrieve metadata for %s - code: CLIMATE-CHANGE-013 message: 'You cannot select the 2 degree C warming scenario for results from these models: %s.' - code: CLIMATE-CHANGE-014 message: Sorry, you can not perform climate change on %s engine sub type. - code: CLIMATE-CHANGE-015 message: You cannot run a Climate Change Model analysis on HD results from an imported RDM. - code: CLIMATE-CHANGE-016 message: Sorry, you can not perform climate change on %s engine type. - code: CLIMATE-CHANGE-017 message: 'You cannot run a Climate Change Model analysis on the following model versions/regions because those models do not exist: NAWF HDv2.0 (Canada) or NAWF HDv1.0 (Canada).' - code: CLIMATE-CHANGE-018 message: Type %s is invalid. Valid types are rcp, ssp. - code: CLIMATE-CHANGE-019 message: SSP scenario %s is invalid. Valid SSP scenarios are 1-2.6, 2-4.5, 3-7.0, 5-8.5. - code: CLIMATE-CHANGE-020 message: Type %s is not supported for the given model versions/regions. - domain: COMMIT-ACC count: 16 codes: - code: COMMIT-ACC-001 message: Account with ID %s not found - code: COMMIT-ACC-002 message: Failed to submit account commit workflow - code: COMMIT-ACC-003 message: Commit setting with ID %s not found - code: COMMIT-ACC-004 message: 'Invalid commit setting: %s' - code: COMMIT-ACC-005 message: 'Pre-bind conditions validation failed: %s' - code: COMMIT-ACC-006 message: Error encountered while performing post bind updates - code: COMMIT-ACC-007 message: Error encountered while assigning account to portfolios - code: COMMIT-ACC-008 message: Error encountered while transitioning account state to active - code: COMMIT-ACC-009 message: Error encountered while deleting account as part of workflow failure cleanup - code: COMMIT-ACC-010 message: Error encountered while performing pre-bind validations - code: COMMIT-ACC-011 message: Error fetching database connection for database %s - code: COMMIT-ACC-012 message: Error occurred while copying account from source exposure to target exposure - code: COMMIT-ACC-013 message: Error getting exposure information for exposure ID %s - code: COMMIT-ACC-014 message: Equivalent updates for successful validations do not exist in settings - code: COMMIT-ACC-015 message: Commit Account is not supported across different instances. Source and destination exposures need to be in the same server instance - code: COMMIT-ACC-016 message: Error duplicating account for commit to same exposure - domain: COMMIT-SET count: 19 codes: - code: COMMIT-SET-001 message: Commit rule with id %s not found - code: COMMIT-SET-002 message: Cannot delete the default commit rule. Please set another rule as default first. - code: COMMIT-SET-003 message: Cannot set isDefault to false. To unset a default rule, set another rule as default. - code: COMMIT-SET-004 message: Invalid copy settings. %s - code: COMMIT-SET-005 message: Invalid update settings. %s - code: COMMIT-SET-006 message: When commitType is provided, updateSettings must also be provided in the request. - code: COMMIT-SET-007 message: 'Invalid exposure ID: %s' - code: COMMIT-SET-008 message: 'Invalid portfolio ID(s): %s for the given exposure ID: %s' - code: COMMIT-SET-009 message: 'Invalid commit type: %s. Valid values are: basic, advanced' - code: COMMIT-SET-010 message: 'When commitType is ''advanced'', all updateSettings must have a non-empty ''advancedStatement'' field. Invalid at index: %s' - code: COMMIT-SET-011 message: When updateSettings is provided in a PATCH request, commitType must also be provided. - code: COMMIT-SET-012 message: Error encountered while creating account commit setting - code: COMMIT-SET-013 message: Error encountered while fetching account commit setting(s) - code: COMMIT-SET-014 message: Error encountered while updating account commit setting - code: COMMIT-SET-015 message: Error encountered while deleting account commit setting - code: COMMIT-SET-016 message: Error encountered while setting account commit setting to default - code: COMMIT-SET-017 message: 'Duplicate resourceType found in updateSettings. Each resourceType (ACCOUNT, POLICY) can appear at most once across all updateSettings entries. Duplicate resourceType: %s' - code: COMMIT-SET-018 message: No default commit setting exists for your tenant. Please request admin to add settings - code: COMMIT-SET-019 message: Lob is not a supported field for commit conditions in update settings - domain: CONVERT-EVENT count: 17 codes: - code: CONVERT-EVENT-001 message: Invalid argument for %s - code: CONVERT-EVENT-002 message: Unable to retrieve metadata for %s - code: CONVERT-EVENT-003 message: Sorry, you can convert event rates or apply loss adjustments on %s engine type(s) only. Enter a non-HD or non-simulated DLM or non-CEP analysis ID. - code: CONVERT-EVENT-004 message: Unsupported analysis type. Convert analysis event rate and loss is only supported on %s analysis type(s) - code: CONVERT-EVENT-005 message: Sorry, we encountered an error while submitting the convert analysis event rate and loss job. Try again, and contact Support if this still does not work. - code: CONVERT-EVENT-006 message: Analysis id %d already ran on event rate id %d. - code: CONVERT-EVENT-007 message: 'Error when getting event loss adjustments: Unable to read the file header.' - code: CONVERT-EVENT-008 message: 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. - code: CONVERT-EVENT-009 message: Unsupported exposure type. Convert event rate and loss is not supported for account analyses. - code: CONVERT-EVENT-010 message: Sorry, convert event rate and loss is not supported PLT groups. - code: CONVERT-EVENT-011 message: Sorry, the event rate scheme id %d does not match the analysis peril region(s). - code: CONVERT-EVENT-012 message: Sorry, the loss adjustment scheme id %d does not match the analysis peril region(s). - code: CONVERT-EVENT-013 message: Sorry, we encountered an error while reading the event loss adjustments. Try again, and contact Support if this still does not work. - code: CONVERT-EVENT-014 message: Error while reading the event loss adjustments, non numeric values found. - code: CONVERT-EVENT-015 message: No event rate schemes found for analysis id %d. - code: CONVERT-EVENT-016 message: 'Missing event rate schemes with ids: %s' - code: CONVERT-EVENT-017 message: Sorry, you can not perform convert event on %s engine sub type. - domain: CONVERT-RESULT-CURRENCY count: 10 codes: - code: CONVERT-RESULT-CURRENCY-001 message: Sorry, we encountered an error on our end while converting currency for analysis id %d. Contact Support at`RMSSupport@moodys.com`. - code: CONVERT-RESULT-CURRENCY-002 message: Invalid argument for %s - code: CONVERT-RESULT-CURRENCY-003 message: Unable to retrieve metadata for %s - code: CONVERT-RESULT-CURRENCY-004 message: Sorry, some of the currency information is invalid. Check the currency scheme, currency code, vintage, and as-of date and try again. - code: CONVERT-RESULT-CURRENCY-005 message: Sorry, the target currency is the same as the original currency. Check the target currency and try again. - code: CONVERT-RESULT-CURRENCY-006 message: Sorry, the analysis ID for the currency conversion is not valid. Check the analysis ID and try again. - code: CONVERT-RESULT-CURRENCY-007 message: 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. - code: CONVERT-RESULT-CURRENCY-008 message: The currency scheme you selected does not contain the source currency %s. Please select the correct currency scheme to continue. - code: CONVERT-RESULT-CURRENCY-009 message: The currency scheme you selected contains currency exchange rates that are not positive. Please select currency scheme with only positive exchange rates. - code: CONVERT-RESULT-CURRENCY-010 message: Sorry, you can not perform convert currency on %s engine type. - domain: CURRENCY count: 10 codes: - code: CURRENCY-400 message: Validation error, Invalid domain name - code: CURRENCY-401 message: Validation error, Invalid tablespace - code: CURRENCY-402 message: Validation error, Invalid entity name - code: CURRENCY-403 message: Validation error, Invalid records - code: CURRENCY-404 message: Validation error, Invalid column name - code: CURRENCY-405 message: Validation error, Mandatory column missing - code: CURRENCY-501 message: 'Database error occurred while creating records in table ` | %s, reason : %s' - code: CURRENCY-502 message: An error occurred while validating currency - code: CURRENCY-503 message: Invalid exposure type passed for currency conversion - code: CURRENCY-504 message: Invalid currency. Please enter a valid currency and try again. - domain: CV count: 2 codes: - code: CV-001 message: 'Invalid operator: ''%s''' - code: CV-002 message: 'Search feature not supported for field: ''%s''' - domain: CYBER count: 35 codes: - code: CYBER-001 message: 'Cyber Policy with Id: %d was not found' - code: CYBER-002 message: Cyber Policy accGrpId must be greater than 0 - code: CYBER-003 message: Cyber Policy expiry date cannot be before inception date - code: CYBER-004 message: Cyber Policy inception date cannot be null or empty - code: CYBER-005 message: Cyber Policy expire date cannot be null or empty - code: CYBER-006 message: 'Invalid cyber policy inception date format. Expected: yyyy-MM-ddTHH:mm:ssZ' - code: CYBER-007 message: 'Invalid cyber policy expire date format. Expected: yyyy-MM-ddTHH:mm:ssZ' - code: CYBER-008 message: Cyber Policy share must be between 0 and 100 - code: CYBER-009 message: Cyber Policy amount field %s must not be negative - code: CYBER-010 message: Cyber Policy currency field %s must not be empty when amount is set - code: CYBER-011 message: Cyber Policy accGrpId %d does not exist in the database - code: CYBER-012 message: 'Duplicate Cyber Policy Id: %d found in batch input' - code: CYBER-101 message: 'Cyber Policy Coverage with Id: %d was not found' - code: CYBER-102 message: Cyber Policy Coverage policyId must be greater than 0 - code: CYBER-103 message: Cyber Policy Coverage amount field %s must not be negative - code: CYBER-104 message: Cyber Policy Coverage currency field %s must not be empty when amount is set - code: CYBER-105 message: 'Duplicate Cyber Policy Coverage Id: %d found in batch input' - code: CYBER-106 message: 'Cyber Policy Coverage references non-existent PolicyCoverageCondition Id: %d' - code: CYBER-201 message: 'Company with Id: %d was not found' - code: CYBER-202 message: Company policyId must be greater than 0 - code: CYBER-203 message: 'Duplicate Company Id: %d found in batch input' - code: CYBER-204 message: 'Invalid Company reportingCloseDate format. Expected: yyyy-MM-dd' - code: CYBER-301 message: 'TechnoInfo with CompanyInfoId: %d was not found' - code: CYBER-302 message: 'TechnoInfo parent Company with CompanyInfoId: %d was not found' - code: CYBER-303 message: 'Duplicate TechnoInfo CompanyInfoId: %d found in batch input' - code: CYBER-401 message: 'ScoreInfo with AccGrpId: %d was not found' - code: CYBER-402 message: ScoreInfo accGrpId must be greater than 0 - code: CYBER-403 message: 'Duplicate ScoreInfo AccGrpId: %d found in batch input' - code: CYBER-501 message: 'Cyber Policy Coverage Condition with Id: %d was not found' - code: CYBER-502 message: 'Duplicate Cyber Policy Coverage Condition Id: %d found in batch input' - code: CYBER-601 message: 'Cyber Policy Coverage Condition Criteria with Id: %d was not found' - code: CYBER-602 message: Cyber Policy Coverage Condition Criteria polCvgCondId must be greater than 0 - code: CYBER-603 message: 'Duplicate Cyber Policy Coverage Condition Criteria Id: %d found in batch input' - code: CYBER-700 message: Cyber batch edit is not enabled. Remove cyberPolicies, cyberPolicyCoverageConditions, and companies from the request. - code: CYBER-701 message: The target EDM does not contain the required cyber/company schemas. Remove cyberPolicies, cyberPolicyCoverageConditions, and companies from the request, or use an EDM with the cyber schema. - domain: DATABASE_MAINTENANCE count: 3 codes: - code: DATABASE_MAINTENANCE-001 message: Database error occurred while updating database statistics. - code: DATABASE_MAINTENANCE-002 message: Database error occurred while updating EDM data version. - code: DATABASE_MAINTENANCE-003 message: Database error occurred while updating EDM exposure tags. - domain: DATABASE_STORE count: 8 codes: - code: DATABASE_STORE-400 message: 'Sorry, we can''t find server id or name: %s. Either it doesn''t exist or you don''t have access to it.' - code: DATABASE_STORE-401 message: Invalid SQL server version provided. - code: DATABASE_STORE-404 message: Data Bridge data source %s not found - code: DATABASE_STORE-500 message: An error occurred retrieving database store record - code: DATABASE_STORE-501 message: An error occurred inserting database store record - code: DATABASE_STORE-502 message: An error occurred updating database store record - code: DATABASE_STORE-503 message: An error occurred deleting database store records - code: DATABASE_STORE-504 message: Database Store task exceeded maximum wait time. - domain: DATA-BRIDGE count: 30 codes: - code: DATA-BRIDGE-501 message: Sorry, we encountered an error submitting this Data Bridge job. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-502 message: Sorry, we encountered an error loading this database. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-503 message: Sorry, we encountered an error deregistering this database. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-401 message: Invalid notification key %s - code: DATA-BRIDGE-402 message: '%s not supported on Data Bridge databases' - code: DATA-BRIDGE-403 message: The database %s that you tried to de-register does not exist. - code: DATA-BRIDGE-404 message: The database you tried to de-register has not been registered on the Data Bridge. - code: DATA-BRIDGE-405 message: Target Data Bridge database %s does not exist - code: DATA-BRIDGE-406 message: The database may not exist or you might not have access. Please contact your administrator. - code: DATA-BRIDGE-550 message: Sorry, we encountered an error creating this Data Bridge database. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-551 message: Sorry, we encountered an error deleting this Data Bridge database. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-552 message: Sorry, we encountered an error creating this Data Bridge sign-in. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-553 message: Sorry, we encountered an error setting permissions on this Data Bridge database. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-554 message: Sorry, we encountered an error importing this Data Bridge database. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-555 message: Sorry, we encountered an error exporting this Data Bridge database. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-556 message: Sorry, we encountered an error trying to get details for data bridge database. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-557 message: Sorry, we failed to process this request. %s. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: DATA-BRIDGE-558 message: 'Failed to get job: %s status' - code: DATA-BRIDGE-559 message: Databridge task %s not found - code: DATA-BRIDGE-560 message: 'Failed to register databridge EDM: %s' - code: DATA-BRIDGE-561 message: The server type for server id %d is not supported for Data Bridge. Please provide a valid Data Bridge server id. - code: DATA-BRIDGE-562 message: Sort by databaseId and serverId is currently not supported for Data Bridge. - code: DATA-BRIDGE-563 message: Exposure already exists for exposureSet %s. Cannot register multiple exposures under the same exposureSet. - code: DATA-BRIDGE-564 message: Error occurred while registering exposure under exposureSet with id %d - code: DATA-BRIDGE-565 message: 'Data Bridge Database with serverId: %d and databaseId: %d not found. Check the database details and try again.' - code: DATA-BRIDGE-566 message: The query provided is not supported for Data Bridge databaseType. Please provide a valid query. - code: DATA-BRIDGE-567 message: The query provided contains unsupported operators for Data Bridge. Please provide a valid query. - code: DATA-BRIDGE-568 message: User is not the owner of the database and is not authorized for owner override - code: DATA-BRIDGE-569 message: current version of the API cannot support this action. Please use the latest of the API endpoint - code: DATA-BRIDGE-570 message: EDM %s is already registered. To register this database, you must rename it. - domain: DATA-TAG count: 9 codes: - code: DATA-TAG-001 message: Sorry, we do not support sort on %s for Search. Please provide a valid sort query param and try again. - code: DATA-TAG-002 message: 'The number of values passed in search query: %s for tagIds field cannot exceed %d.' - code: DATA-TAG-003 message: 'An internal parser error occurred, error while extracting tag ids list from table for column: %s.' - code: DATA-TAG-004 message: Tags provided in input must not be null and should contain valid, positive integer type values in a list. Please provide a valid list of tags and try again. - code: DATA-TAG-005 message: Tag Ids provided in input %s are invalid. Please make sure that the tags exist and try again. - code: DATA-TAG-006 message: Sorry, we failed to load the Data Tag details from Data Store. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: DATA-TAG-008 message: List of tags cannot be null when updating tags. - code: DATA-TAG-009 message: The search query %s provided contains an unsupported operator %s for tagIds. Please provide a valid search query and try again. - code: DATA-TAG-010 message: You are not authorized to perform this Data Tag operation. This may be due to an expired token, invalid credentials, or insufficient permissions. Verify your authorization and try again, or contact your administrator. - domain: DATE count: 2 codes: - code: DATE-001 message: Invalid date. The valid range of dates is from 01/01/1753 to 12/31/9999 - code: DATE-002 message: '%s' - domain: DBATTRIBUTE count: 1 codes: - code: DBATTRIBUTE-001 message: 'Error occurred while fetching the db attribute : %s' - domain: DBM count: 7 codes: - code: DBM-502 message: 'Database error occurred while updating metrics for database with Id: %d' - code: DBM-503 message: Database error occurred while calculating metrics for database - code: DBM-504 message: Database error occurred while updating metrics for database - code: DBM-505 message: Database error occurred while calculating the size of EDMs - code: DBM-506 message: Database error occurred while checking if the metrics exist - code: DBM-507 message: 'Database error occurred while getting metrics for database with ID: %d' - code: DBM-508 message: Database error occurred while deleting metrics for database - domain: DLM_SERVICE service count: 23 codes: - code: DLM_SERVICE-001 message: Sorry, we encountered an error while running the DLM analysis job. Try again, and contact Support if this still does not work. - code: DLM_SERVICE-002 message: Sorry, we encountered an error while loading the model profile ID %d for this DLM analysis. Try again, and contact Support if this still does not work. - code: DLM_SERVICE-003 message: Sorry, we encountered an error while loading the analysis currency %s for this DLM analysis. Try again, and contact Support if this still does not work. - code: DLM_SERVICE-004 message: Sorry, the model version %s for this DLM analysis is invalid. Specify a valid version and try again. - code: DLM_SERVICE-005 message: Sorry, the currency vintage %s with the as-of date %s is invalid. Specify a valid vintage and try again. - code: DLM_SERVICE-006 message: Sorry, the output profile is invalid or missing. Specify a valid output profile and try again. - code: DLM_SERVICE-007 message: Model Region with code %s and isHd %s is not found - code: DLM_SERVICE-008 message: Invalid model profile - footprintId missing or invalid - code: DLM_SERVICE-009 message: Footprint Event %s is not found - code: DLM_SERVICE-010 message: Sorry, the output profile ID %d for this analysis is invalid. Specify a valid output profile and try again. - code: DLM_SERVICE-011 message: We encountered an error retrieving the output profile with id %d. Try again. If this still doesn't work, contact Support. - code: DLM_SERVICE-012 message: Sorry, climate change analysis cannot be run at %s level. Use a portfolio level exposure and try again. - code: DLM_SERVICE-013 message: Sorry, climate change analysis is not supported for %s analysis type. Use EP or Simulated type and try again. - code: DLM_SERVICE-014 message: Sorry, climate change analysis is not supported for dlm engine version %s. Select dlm version 22 or higher and try again. - code: DLM_SERVICE-015 message: Sorry, climate change analysis is not supported for peril %s. Use windstorm peril and try again. - code: DLM_SERVICE-016 message: Sorry, climate change analysis is not supported for region %s. Select region %s and try again. - code: DLM_SERVICE-017 message: 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 Support. - code: DLM_SERVICE-018 message: Sorry, the event rate scheme Id %d for this DLM analysis is invalid. Specify a valid event rate scheme Id and try again. - code: DLM_SERVICE-019 message: Sorry, DLM or HD analysis is not supported for analysis type %s and exposure type %s in %s. Use EP type and try again. - code: DLM_SERVICE-020 message: 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. - code: DLM_SERVICE-021 message: Sorry, you have provided invalid settings with model type %s. - code: DLM_SERVICE-022 message: Sorry, DLM Ensemble CEP analysis only supports exposure type %s. - code: DLM_SERVICE-023 message: Sorry, the model profile is invalid. Specify a valid model profile and try again. - domain: DOI_SERVICE count: 5 codes: - code: DOI_SERVICE-001 message: Sorry, we encountered an error while running the CA DOI job. Try again, and contact Support if this still does not work. - code: DOI_SERVICE-002 message: Sorry, we encountered an error while generating the CA DOI report. Try again, and contact Support if this still does not work. - code: DOI_SERVICE-003 message: Sorry, we encountered an error while downloading the RDM for CA DOI analysis. Try again, and contact Support if this still does not work. - code: DOI_SERVICE-004 message: All the scale factors cannot be 0. - code: DOI_SERVICE-005 message: Peril code %s is not supported for the Exposure DOI report. Select a supported peril. - domain: DOM count: 26 codes: - code: DOM-001 message: Domain data not found for domain %s, tablespace %s, entity %s - code: DOM-003 message: Invalid format for entity path %s - code: DOM-004 message: Scalar domain data for domain %s, tablespace %s, entity %s found %d values - code: DOM-005 message: 'Invalid input data for the parameter : %s' - code: DOM-006 message: Sorry, the combination of country %s and resolution %s is not supported. To learn more, see [](https://help.rms.com/help/RiskModeler/prod/Content/RM_HowTo/ALMResForImportAndAgg.htm) in Support Center. - code: DOM-007 message: 'Sorry, we encountered parsing error. Try different input for parameter: %s' - code: DOM-008 message: Sorry, we encountered an error while retrieving peril and loss type for coverage %s. See the "Fields for Advanced Bulk Edits" topic in the Help Center for help with query syntax. - code: DOM-009 message: 'Invalid value provided : %s for enum type field : %s' - code: DOM-500 message: Sorry, we encountered an error while retrieving domain names. Try again, and contact Support if this still does not work. - code: DOM-501 message: Sorry, we encountered an error while retrieving tablespace names for domain %s. Try again, and contact Support if this still does not work. - code: DOM-502 message: Sorry, we encountered an error while retrieving entity names for domain %s and tablespace %s. Try again, and contact Support if this still does not work. - code: DOM-503 message: Sorry, we encountered an error while retrieving entity attributes for domain %s, tablespace %s, and entity %s. Try again, and contact Support if this still does not work. - code: DOM-504 message: Sorry, we encountered an error while retrieving entity values for domain %s, tablespace %s, and entity %s. Try again, and contact Support if this still does not work. - code: DOM-505 message: Sorry, we encountered an error while retrieving secondary modifiers for domain %s, tablespace %s, and entity %s. Try again, and contact Support if this still does not work. - code: DOM-506 message: Sorry, we encountered an error while retrieving construction details for country %s, construction class scheme %s, and construction class %s. Try again, and contact Support if this still does not work. - code: DOM-507 message: Sorry, we encountered an error while retrieving occupancy details for country %s, occupancy type scheme %s, and occupancy type %s. Try again, and contact Support if this still does not work. - code: DOM-509 message: Sorry, we encountered an error while retrieving hazards for domain %s, tablespace %s, and entity %s. Try again, and contact Support if this still does not work. - code: DOM-510 message: 'Sorry, we encountered an error while retrieving country resolution values for country code: ''%s'', resolution type: ''%s''. Try again, and contact Support if this still does not work.' - code: DOM-511 message: 'Sorry, we encountered an error while retrieving country line of business types for country code: ''%s''. Try again, and contact Support if this still does not work.' - code: DOM-512 message: Sorry, we encountered an error while retrieving resolution column mappings. Try again, and contact Support if this still does not work. - code: DOM-513 message: 'Sorry, there is a mismatch between country code: ''%s'' and resolution: ''%s''.' - code: DOM-514 message: Sorry, we're having some trouble on our end. Try again, and contact Support if this still does not work. - code: DOM-515 message: Sorry, we encountered an error while retrieving climate-conditioned-views for regionperil %s and enginetype %s. Try again, and contact Support if this still does not work. - code: DOM-516 message: Sorry, we encountered an error while retrieving reference-rate-scheme for rate-scheme-id %d. Try again, and contact Support if this still does not work. - code: DOM-517 message: Sorry, we encountered an error while retrieving analysis regions for peril %s. Try again, and contact Support at `RMSSupport@moodys.com`.comif this still does not work. - code: DOM-518 message: 'Sorry, we can''t find results for the entries you provided: domain: ''%s'', tablespace: ''%s'', entity: ''%s''.' - domain: DS count: 56 codes: - code: DS-001 message: We did not locate the database %s. Check the database name. - code: DS-002 message: Sorry, looks like you do not have access permission for the %s database. - code: DS-003 message: The database cannot be empty. Enter a valid database name. - code: DS-004 message: 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. - code: DS-401 message: 'Invalid instance namespace: %s' - code: DS-402 message: 'Invalid instance status: %s' - code: DS-403 message: Specified server %s is not registered. - code: DS-404 message: Unable to process MDF import into RDS database instances. - code: DS-405 message: The selected server does not support MDF imports. - code: DS-406 message: The selected server does not support BAK imports. - code: DS-408 message: You cannot load (register) a database that's not a Data Bridge EDM. - code: DS-409 message: You cannot export to an existing RDM database. This is only supported for Data Bridge. - code: DS-410 message: Data Bridge Database %s not found. Check the database name and try again. - code: DS-411 message: Database error due to missing table. - code: DS-412 message: The detachOnly option can be "true" only if the format is MDF, the operation is DOWNLOAD_EDM, and the SQL Server version is 2019. - code: DS-413 message: Exporting a database in MDF format requires the option detachOnly to be true when the database size is greater than 100 GB. - code: DS-500 message: Sorry, we encountered an error trying to retrieve the database. Try again. - code: DS-501 message: Sorry, we encountered an error while checking the access permissions for this database. Try again. - code: DS-502 message: Database error occurred while validating data source %s - code: DS-503 message: 'Database error occurred while retrieving data source: %s for Account Id: %d' - code: DS-504 message: 'Error occurred starting the database connection pool for data source: %s' - code: DS-505 message: 'Error occurred stopping the database connection pool for data source: %s' - code: DS-506 message: 'Database error occurred while creating data source: %s' - code: DS-507 message: A database with the name %s already exists. Enter a different name. - code: DS-508 message: 'Database error occurred while updating data source: ''%s''' - code: DS-509 message: 'Database error occurred while deleting data source: ''%s''' - code: DS-510 message: 'Database error occurred while creating backup for data source: ''%s''' - code: DS-511 message: Sorry, you tried something invalid. Enter a valid datastore operation. - code: DS-512 message: You have reached the maximum number (%s) of EDMs allowed for your organization. Delete an EDM before you create or upload a new one. - code: DS-513 message: Sorry, we encountered an error creating this database. Try again, and contact Support if this still does not work. - code: DS-514 message: Sorry, this could be an error on our end. Try again, and contact Support if this still does not work. - code: DS-515 message: Sorry, we encountered an error triggering this job. Something might be missing from the job input. Try again, and contact Support if this still does not work. - code: DS-516 message: The database %s is being upgraded. Wait a few minutes and try again. - code: DS-517 message: Sorry, we encountered an error trying to retrieve database information for tenant %s. Try again. - code: DS-519 message: Sorry, we encountered an error reading database information. Try again, and contact Support if this still does not work. - code: DS-520 message: Sorry, we encountered an error reading database system information. Try again, and contact Support if this still does not work. - code: DS-521 message: 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. - code: DS-522 message: Sorry, we can't find database %s. Either it doesn't exist or you don't have access to it. - code: DS-523 message: Could not parse URL, reason %s - code: DS-524 message: Sorry, the only allowed version for upgrade is 22 - code: DS-525 message: Invalid sql version provided - code: DS-526 message: 'We did not locate the database for exposureId: %d. Either it doesn''t exist or you don''t have access to it.' - code: DS-527 message: The exposureId %s provided is invalid. Please enter a valid exposureId. - code: DS-528 message: Error occurred while creating exposure under exposureSet with id %d - code: DS-529 message: Sorry, file format %s is not supported for download EDM. Supported file formats are BAK and MDF - code: DS-530 message: The data source %s exists and is currently marked for deletion. Any actions on this data source during the deletion are not supported. If you want to reuse this database name for a new database, wait until the deletion is complete. - code: DS-531 message: The exposureId %d exists and is currently marked for deletion. Any actions on this exposure during the deletion are not supported. - code: DS-532 message: The transaction log is full due to an active open transaction in the database and due to this the log cannot be truncated. Wait for some time and retry again. If this still does not work, please contact the support at RMSsupport@moodys.com - code: DS-533 message: 'We did not locate the exposure variation with id: %d. Either it doesn''t exist or you don''t have access to it.' - code: DS-534 message: Database %s is currently in a not ready state. Actions on this exposure are temporarily unavailable. Please try again later. - code: DS-535 message: schemaVersion is only applicable for DOWNLOAD_EDM operation. Please remove schemaVersion from the request and try again. - code: DS-536 message: Failed to validate database existence for %s. An unexpected error occurred during validation. - code: DS-537 message: Failed to search for database '%s' on DataBridge server. An unexpected error occurred during search. - code: DS-538 message: EDM %s already exists. To create/import/upload this database, you must rename it. - code: DS-539 message: EDM %s is already registered. To register this database, you must rename it. - code: DS-540 message: Export of SQL Server %s file is now deprecated on Intelligent Risk Platform. Please use a supported version (i.e. SQL 2019). - domain: EDM count: 8 codes: - code: EDM-501 message: Database error occurred while loading EDMs - code: EDM-502 message: 'Database error occurred while creating EDM with name: %s' - code: EDM-505 message: Database error occurred while creating EDM with name %s already exists - code: EDM-506 message: Database error occurred while creating a backup for EDM - code: EDM-507 message: Database error occurred while creating a backup for EDM not found - code: EDM-509 message: Database error occurred while querying for list of EDMs - code: EDM-510 message: Sorry, you do not have access permissions to any groups of tenant %s. Check with your Administrator about getting access. - code: EDM-511 message: Error occurred while deleting EDM metadata - domain: EDM_SYNC count: 3 codes: - code: EDM_SYNC-001 message: Failed to sync with Analytics Gateway - code: EDM_SYNC-002 message: 'Failed to sync with Analytics Gateway, Response: %s' - code: EDM_SYNC-003 message: 'Received an invalid message from Analytics Gateway, response status, msg: %d %s' - domain: ENGINE count: 288 codes: - code: ENGINE-001 message: We encountered an error trying to run the job. Try again. If this still does not work, contact Support. - code: ENGINE-002 message: We encountered an error trying to run the job. Job inputs aren't valid - code: ENGINE-003 message: only CopyAccount, DeleteAccount or ConvertCurrency operation is supported - code: ENGINE-004 message: Record not found in import store database. - code: ENGINE-005 message: 'Database with data source name : ''%s'', already exists' - code: ENGINE-006 message: Sorry, we failed to process this request since the database limit has been exceeded. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-007 message: Data source %s not found - code: ENGINE-008 message: 'Database error occurred while creating backup for data source: %s' - code: ENGINE-009 message: 'Database error occurred while deleting data source: ''%s''' - code: ENGINE-010 message: 'Database error occurred while creating data source: %s' - code: ENGINE-011 message: 'Database error occurred while retrieving data source: %s' - code: ENGINE-012 message: RDM database creation failed - code: ENGINE-013 message: Validations failed - code: ENGINE-014 message: We encountered an error trying to run the job. Try again. If this still does not work, contact Support. - code: ENGINE-015 message: 'Unsupported Exposure Type: %s' - code: ENGINE-016 message: '%s backup status cannot be retrieved' - code: ENGINE-017 message: '%s back up cannot be created and failed with exception : %s' - code: ENGINE-018 message: LI Job got canceled - code: ENGINE-019 message: MRI Job failed with validation errors. Please see jobs' details for validation log file. - code: ENGINE-020 message: 'No job id found for analysis id : %s' - code: ENGINE-021 message: No results are available for analysis %s included the download. Remove this analysis from the download and try again. - code: ENGINE-022 message: 'DB name : %s, %s failed!' - code: ENGINE-023 message: rdsHost cannot be null or empty - code: ENGINE-024 message: rdsPort cannot be null or empty - code: ENGINE-025 message: rdsUser cannot be null or empty - code: ENGINE-026 message: rdsPwd cannot be null or empty - code: ENGINE-027 message: s3AccessKey cannot be null or empty - code: ENGINE-028 message: s3Secret cannot be null or empty - code: ENGINE-029 message: dbRdmKey cannot be null or empty - code: ENGINE-030 message: s3bucket cannot be null or empty - code: ENGINE-031 message: s3DownLoadBucket cannot be null or empty - code: ENGINE-032 message: tenantId cannot be null or empty - code: ENGINE-033 message: analysisId cannot be null or empty - code: ENGINE-034 message: userId cannot be null or empty - code: ENGINE-035 message: workflowId cannot be null or empty - code: ENGINE-036 message: workflowServiceUrl cannot be null or empty - code: ENGINE-037 message: expirationHours cannot be null or empty - code: ENGINE-038 message: edmBucketName cannot be null or empty - code: ENGINE-039 message: BCP Batch size cannot be null or empty and must be numeric - code: ENGINE-040 message: BCP timeout cannot be null or empty and must be numeric - code: ENGINE-041 message: Detail losses export value cannot be null or empty and must be boolean - code: ENGINE-042 message: '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.' - code: ENGINE-043 message: The request %s - code: ENGINE-044 message: 'Error when getting event rates: Datastore call failed' - code: ENGINE-045 message: Error when getting event rates - code: ENGINE-046 message: 'Error when getting event rates: Unable to read the rate headers.' - code: ENGINE-047 message: 'LI-BULK: Geocoding job %s failed' - code: ENGINE-048 message: 'server returned statusCode: %s' - code: ENGINE-049 message: only CopyPortfolio, DeletePortfolio or ConvertCurrency operation is supported - code: ENGINE-050 message: Sorry, looks like something might be wrong at our end. Try this again, and if it still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: ENGINE-051 message: Template file does not exist - code: ENGINE-052 message: dlmJobId cannot be null or empty - code: ENGINE-053 message: authToken cannot be null or empty - code: ENGINE-054 message: serviceName cannot be null or empty - code: ENGINE-055 message: Exposure isn't valid. %s - code: ENGINE-056 message: SQL exception. - code: ENGINE-057 message: HPC exception. %s - code: ENGINE-058 message: only ConvertCurrency operation is supported - code: ENGINE-059 message: 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 Support at `RMSSupport@moodys.com`. - code: ENGINE-060 message: Exception occurred while copy account operation - code: ENGINE-061 message: Exception occurred while delete account operation - code: ENGINE-062 message: Exception occurred while convert currency operation - code: ENGINE-063 message: Database error occurred while calculating Portfolio and its accounts metrics - code: ENGINE-064 message: Database error occurred while calculating metrics for all Portfolios and Accounts in EDM - code: ENGINE-065 message: Detail stats export value cannot be null or empty and must be boolean - code: ENGINE-066 message: Error occurred while copying portfolio - code: ENGINE-067 message: Error occurred while deleting portfolio - code: ENGINE-068 message: Failed to get analytics details - code: ENGINE-069 message: Error when dropping database - code: ENGINE-070 message: Failed to Update DB Attribute table - code: ENGINE-071 message: Failed to make DB INFO entries for EDM - code: ENGINE-072 message: Failed to acquire position in task queue - code: ENGINE-073 message: 'Failed to create empty EDM: %s' - code: ENGINE-074 message: Failed load parquet files from S3 - code: ENGINE-075 message: Failed recreate RDM indices - code: ENGINE-076 message: Failed to update RDM seed IDs - code: ENGINE-077 message: Failed to create RDM backup - code: ENGINE-078 message: Failed to generate download link for RDM - code: ENGINE-079 message: Layer info parse failed - code: ENGINE-081 message: Failed to drop indicies during download RDM - code: ENGINE-082 message: Failed to delete webDb entries - code: ENGINE-084 message: Failed to create webDb entries - code: ENGINE-085 message: Failed to create DbInfo entries - code: ENGINE-086 message: Failed to create db metrics entries - code: ENGINE-087 message: Failed to create groupDb detail entries - code: ENGINE-088 message: Failed to detach DataSource - code: ENGINE-089 message: Failed to fetch the input due to invalid uploadId. Please check the uploadId and try again. - code: ENGINE-090 message: Failed to get taskID for restore process - code: ENGINE-091 message: Failed to upload EDM - code: ENGINE-092 message: Failed to update import source - code: ENGINE-093 message: Failed to delete groupDbDetail table - code: ENGINE-094 message: Failed to delete the dbInfo table - code: ENGINE-095 message: Failed to copy EDM - code: ENGINE-096 message: Failed to get EDM name from database - code: ENGINE-097 message: IO exception while attempting to get geohaz inputs - code: ENGINE-098 message: No job id found for analysis id %s - code: ENGINE-099 message: Load database connection properties error - code: ENGINE-100 message: Failed to retrieve analysis name - code: ENGINE-101 message: Failed while rebaselining the database - code: ENGINE-102 message: Failed to create DB type %s - code: ENGINE-103 message: Failed to initialize datasource - code: ENGINE-104 message: Invalid engine input - code: ENGINE-105 message: failed to read exposure from job input - code: ENGINE-106 message: 'Too many treaty priority numbers: %s > Max %s' - code: ENGINE-107 message: Unable to save financial perspective - code: ENGINE-108 message: Unable to save treaties - code: ENGINE-109 message: Unable to load treaties - code: ENGINE-110 message: Unable to get analysis status - code: ENGINE-111 message: 'Unable to get analysisId for jobId: %s' - code: ENGINE-112 message: 'Unable to get analysis for id: %s' - code: ENGINE-113 message: 'Unable to get jobId for analysis ID: %s' - code: ENGINE-114 message: 'Unable to copy analysis record for analysis Id: %s' - code: ENGINE-115 message: Unable to get event loss - code: ENGINE-116 message: Unable to get treaty info - code: ENGINE-117 message: 'Unable to load event losses for perspective: %s' - code: ENGINE-118 message: 'Unable to load losses for perspective: %s' - code: ENGINE-119 message: EP Type needed - code: ENGINE-120 message: 'Treaty information not set: %s' - code: ENGINE-121 message: Analysis isn't of type EP. No EP calculation performed. - code: ENGINE-126 message: No event losses found - code: ENGINE-127 message: 'Incomplete input! The statistics calculator was NOT set with an %s curve, needed to calculate the statistics. Perspective: %s' - code: ENGINE-130 message: Unable to load financial perspective - code: ENGINE-131 message: EP losses calculation Failed - code: ENGINE-132 message: 'Unable to generate EP curves for treaty: %s' - code: ENGINE-133 message: Unable to create group - code: ENGINE-134 message: Unable to add analysis events - code: ENGINE-135 message: Invalid analysis to add - code: ENGINE-136 message: Failed to delete results - code: ENGINE-137 message: Unable to write analysis event - code: ENGINE-138 message: Failed to delete group results - code: ENGINE-139 message: Failed to regroup treaties - code: ENGINE-140 message: Group already contains analysis %s - code: ENGINE-141 message: Group contains a circular hierarchy due to group id %s - code: ENGINE-142 message: 'Duplicate analysis id found: %s' - code: ENGINE-143 message: Regional grouping engine failed - code: ENGINE-144 message: Failed to get event id count - code: ENGINE-145 message: Failed to convert currency - code: ENGINE-146 message: Failed to get scheme count - code: ENGINE-147 message: Analysis or currency not found - code: ENGINE-148 message: Analysis region count not found - code: ENGINE-149 message: Failed to get Analysis count - code: ENGINE-150 message: 'Missing mapping for perspcode: %s' - code: ENGINE-151 message: 'Missing mapping for analysis ID: %s' - code: ENGINE-152 message: Unable to find %s in ExposureIDOrderTable - code: ENGINE-153 message: Unable to get group exposure list - code: ENGINE-154 message: Failed to group regional losses - code: ENGINE-155 message: AnalysisId %s is not in any group list - code: ENGINE-156 message: Failed to get group loss for perspective - code: ENGINE-157 message: Treaty %s not found in rdm pate edit list. - code: ENGINE-158 message: Treaty loss calculation failed - code: ENGINE-159 message: 'Failed to get treaty: %s' - code: ENGINE-160 message: 'Unsupported analysis mode: %s. Valid modes are Expected and Distributed' - code: ENGINE-161 message: DLM parent analysis id was not set - code: ENGINE-162 message: S3 bucket for jobId:%s did not become consistent after %s ms - code: ENGINE-163 message: ALM analysis missing exposures - code: ENGINE-164 message: ALM analysis missing profiles - code: ENGINE-165 message: Sorry, it looks like something might be wrong at our end. The job failed to submit to HPC. Contact Support at `RMSSupport@moodys.com` for help resolving this issue. - code: ENGINE-166 message: Failed to transform job to HPC - code: ENGINE-167 message: Failed S3 write - code: ENGINE-168 message: Unable to create database. DB Name conflict - code: ENGINE-169 message: Failed to create download link - code: ENGINE-170 message: Failed to create retention entry - code: ENGINE-171 message: Failed to create HPC job - code: ENGINE-172 message: 'Failed to create HPC task: %s' - code: ENGINE-173 message: Failed to set up HPC ENV - code: ENGINE-174 message: S3 file read failed - code: ENGINE-175 message: Unable to get Rlaas Input - code: ENGINE-176 message: EDM creation failed - code: ENGINE-177 message: Invalid analysis id filter - code: ENGINE-178 message: Database quota exceeded. Unable to create new databases while at or above quota. - code: ENGINE-179 message: Sorry, it looks like something went wrong on our end. Try your analysis again. If this still doesn't work, contact Support. - code: ENGINE-180 message: Error occurred during transforming the registration output - code: ENGINE-181 message: Exception occurred while bulk edit operation - code: ENGINE-182 message: Exception occurred while fetching metadata from results service - code: ENGINE-183 message: Exception occurred while querying results service - code: ENGINE-184 message: 'Exception occurred while fetching HD EP via results service : %s' - code: ENGINE-185 message: 'Exception occurred while fetching HD Statistics via results service : %s' - code: ENGINE-186 message: RL Geohaz job %s failed - code: ENGINE-187 message: 'Exception occurred while fetching HD non-EP results via results service : %s' - code: ENGINE-188 message: 'Exception occurred while fetching HD PLT results via results service : %s' - code: ENGINE-189 message: Invalid database store type - code: ENGINE-191 message: '%s doesn''t match %s. Failed to process the file.' - code: ENGINE-192 message: Failed to check if the uploaded DB corresponds with the DB Upload type operation. Please ensure the rmsver table exists. - code: ENGINE-193 message: Exception occurred while downloading csv via results-service - code: ENGINE-194 message: Job cancelled - code: ENGINE-195 message: Job failed. %s - code: ENGINE-197 message: Job failed. Infrastructure issue - code: ENGINE-198 message: Failed to process GEOHAZ for given Exposure Criteria. %s - code: ENGINE-199 message: Failed to update the copy\*edm_destination table for id. %s - code: ENGINE-200 message: Recreate indexes value cannot be null or empty and must be boolean - code: ENGINE-201 message: 'Failed to refresh analysis results status: %d. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn''t work.' - code: ENGINE-202 message: Failed to refresh results for analysis. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-203 message: Sorry, we encountered an error downloading this database. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-204 message: Sorry, we encountered an error with this hazard retrieval. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-205 message: 'Failed register result table, errorCode: %s error: %s' - code: ENGINE-206 message: 'Job failed. Invalid engine input. Reason: %s' - code: ENGINE-207 message: Failed to restore databases to Data Bridge server - code: ENGINE-208 message: Invalid DB key - code: ENGINE-209 message: Failed to track the status of rds task - code: ENGINE-210 message: '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 Help Center for a list of supported SQL Server versions.' - code: ENGINE-211 message: Sorry, we encountered an error while downloading this database. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-212 message: Sorry, we encountered an error migrating the data bridge EDM. Try again, and contact Support if this still doesn't work. - code: ENGINE-213 message: Sorry, we encountered an unknown error trying to de-register this database. Try again, and contact Support if this still doesn't work. - code: ENGINE-214 message: Sorry, we encountered an error deleting this aggregate portfolio. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-215 message: Sorry, looks like this is an invalid operation for an aggregate portfolio. - code: ENGINE-216 message: Sorry, we encountered an error importing this aggregate portfolio. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-217 message: Sorry, we encountered an error copying this aggregate portfolio. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-218 message: Sorry, we can't complete this import because you didn't provide any files for import. - code: ENGINE-219 message: Looks like there's something wrong with the input file format. Check that you're using a TXT or CSV file. - code: ENGINE-220 message: Sorry, we encountered an error exporting this data. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-221 message: Sorry, we encountered an error exporting this data. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-222 message: Target RDM database %s does not exist - code: ENGINE-224 message: Sorry, we encountered an error while processing the input data for loss registration. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-225 message: Sorry, we encountered an error while running this HD analysis. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-226 message: Sorry, looks like there's not enough space. Delete some databases from your local storage or Data Bridge server and try again - code: ENGINE-227 message: 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 Help Center for a list of supported SQL Server versions. - code: ENGINE-228 message: Failed to restore the %s %s from backup file. - code: ENGINE-229 message: 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 Help Center for a list of supported %1$s versions. - code: ENGINE-230 message: Sorry, the EDM failed to upload because the EDM version is missing. See "EDM and RDM Upload" in the Help Center for a list of supported EDM versions. - code: ENGINE-231 message: Failed to read the valid EDM versions. - code: ENGINE-232 message: Sorry, we encountered an error while geocoding. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-233 message: Sorry, we encountered an error while running this Climate Change analysis. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-234 message: No climate change scenario was found for this combination of inputs. Check your inputs and try again, or contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-235 message: 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. - code: ENGINE-236 message: 'Unrecognized engine version: %s' - code: ENGINE-237 message: 'Failed table: %s error code: %s error message: %s' - code: ENGINE-238 message: workflowId should not be null - code: ENGINE-239 message: 'Loss Transformations workflow failed with status %s. Workflow URL: %s' - code: ENGINE-240 message: Sorry, we encountered an error while running this HD Grouping analysis. To resolve this issue, Contact Support at `RMSSupport@moodys.com`. - code: ENGINE-241 message: Currency scheme must contain USD currency code. - code: ENGINE-242 message: Sorry, the database backup failed. The database doesn't exist. - code: ENGINE-243 message: 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. - code: ENGINE-244 message: Failed to truncate RDM table %s for write retry. - code: ENGINE-245 message: Failed to delete duplicate RDM rate scheme entries before copying data. - code: ENGINE-246 message: Sorry, we encountered an error on our end while converting currency. Contact Support at `RMSSupport@moodys.com`. - code: ENGINE-247 message: Failed to send notification. - code: ENGINE-248 message: Sorry, we encountered an error while running this Simulate Losses analysis. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-249 message: Sorry, we encountered an error on our end while checking duplicate records. Contact Support at `RMSSupport@moodys.com`. - code: ENGINE-250 message: Failed to upload rdm due to duplicate records found in %s. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-251 message: 'Sorry, we failed to %s EDM with data source name : ''%s'' since it doesn''t exist' - code: ENGINE-252 message: Sorry, we encountered an error while running this HD ALM analysis. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-253 message: Sorry, we encountered an error while running this HD PATE analysis. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-254 message: 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. - code: ENGINE-255 message: userName cannot be null or empty - code: ENGINE-256 message: 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. - code: ENGINE-257 message: 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. - code: ENGINE-258 message: '%s' - code: ENGINE-259 message: Sorry, marginal impact analysis cannot run on exposures with step policies. - code: ENGINE-260 message: Exposure set %s already in use with another exposure or result data. Please check and try again. - code: ENGINE-261 message: Result registration failed. - code: ENGINE-262 message: Sorry, we encountered an error while loading the treaty metadata for HD analysis. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-263 message: Sorry, we encountered an error while retrieving the PLT metadata for HD analysis from the database. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-264 message: This job could not be completed because data source %s does not exist or this user does not have access to it. - code: ENGINE-265 message: Sorry, we encountered an error while writing the %s for HD analysis %s to S3. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-266 message: Sorry, we failed to upload your EDM. There was an error while upgrading the database. - code: ENGINE-267 message: You provided an invalid model version %s. For a list of valid model versions, see the Peril Model List in the Risk Modeler Help Center or on the Moody's RMS Support Center. - code: ENGINE-268 message: Failed to restore the %s %s from backup file, as %s - code: ENGINE-269 message: PATE input list is either missing or empty - code: ENGINE-270 message: Error occurred while parsing PATE input list json - code: ENGINE-271 message: Analysis information map is not available - code: ENGINE-272 message: Analysis group information is not available - code: ENGINE-273 message: The database is corrupted with some data consistency issues. Please run DBCC CHECKDB on the database to repair before creating the backup. - code: ENGINE-274 message: Invalid backup/MDF file provided. The backup set formed could be incorrect or the backup file is corrupted. - code: ENGINE-275 message: Failed to detect SQL version of the provided file. Please import the SQL 2019 bak file or mdf file type. - code: ENGINE-276 message: An internal error has occurred during the backup/restore operation. - code: ENGINE-277 message: The provided backup file is empty - code: ENGINE-278 message: 'The given database is too large to be exported as an mdf. More details: %s' - code: ENGINE-279 message: Failed to create exposure bundle from database %s. - code: ENGINE-280 message: Failed to mark EDM for deletion - code: ENGINE-281 message: Sorry, we encountered an error on our end while mapping financial perspectives. Contact Support at `RMSSupport@moodys.com`. - code: ENGINE-282 message: 'Failed to get the analysis details for analysis id: %s' - code: ENGINE-283 message: Sorry, we encountered an error on our end while running the hd marginal impact job. Contact Support at `RMSSupport@moodys.com`. - code: ENGINE-284 message: Sorry, we encountered an error while running the job due to invalid group id. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-285 message: 'Export job failed due to primary key violation in table: %s. Please check the database for duplicate records and try again.' - code: ENGINE-286 message: 'Table capacity reached for table: %s. Please consider splitting analyses to chunks and export to separate databases.' - code: ENGINE-287 message: Data source %s can only contain characters only 0-9, A-Z, a-z, underscore(\*), and hyphen(-). Can't start or end with hyphen, and can't include multiple consecutive hyphens (--). Spaces are not allowed. - code: ENGINE-288 message: Sorry, HD grouping is not allowed because one or more climate change analyses use a non-CCM PET. Contact Support at `RMSSupport@moodys.com` if you need assistance. - code: ENGINE-289 message: EDM %s is already registered. To register this database, you must rename it. - code: ENGINE-290 message: Sorry, we encountered an error during copy operation. A %s record already exists for Location ID %s. Try again, and contact Support at RMSSupport@moodys.com if this still doesn't work. - code: ENGINE-291 message: Sorry, we encountered an error while submitting ELT to PLT Job as there are no losses generated for analysis, and contact Support at RMSSupport@moodys.com if this still doesn't work. - code: ENGINE-426 message: '' - code: ENGINE-427 message: 'The RDM database might have an invalid schema. Error: %s.' - code: ENGINE-428 message: Sorry, we are unable to import this database because it contains encrypted objects. Please remove the encryption from the database and try again, or contact Support at RMSSupport@moodys.com for assistance. - code: ENGINE-429 message: Database connection error occurred during %s operation. Please verify that the EDM exists and try again, or contact Support at RMSSupport@moodys.com if you need assistance. - code: ENGINE-430 message: 'Invalid analysis group type; expected ANLS, CDGP, INGP, or MCGP (received: %s).' - code: ENGINE-431 message: Sorry, the EDM failed to upload because the EDM version %s is not supported. Upgrade or downgrade the EDM to a supported version and try the upload again. See "EDM and RDM Upload" in the Help Center for a list of supported EDM versions. - code: ENGINE-432 message: Sorry, the exposure set (ID %s) was not found or your user doesn't have access to it. Verify the exposure set and try again, or contact Support at RMSSupport@moodys.com for assistance. - code: ENGINE-433 message: The %s operation failed because the database server has insufficient memory resources. Please wait a few minutes and try again. If the problem persists, contact Support at RMSSupport@moodys.com for assistance. - domain: ENGINE (DLM) count: 26 codes: - code: ENGINE-400 message: Exposure failed to process. No valid locations for the peril region. - code: ENGINE-401 message: Exposure failed to process. No valid location coverages for peril region. - code: ENGINE-402 message: Exposure failed to process. Too many lines of business, limit is 255. - code: ENGINE-403 message: 'Exposure failed to process. Exposure requires missing currency: %s.' - code: ENGINE-404 message: Exposure failed to process. Exposure item not found. - code: ENGINE-405 message: Exposure failed to process. Try again, and contact Support if this still does not work. - code: ENGINE-406 message: No results' metadata found for analysis id %s - code: ENGINE-407 message: Batch data validation failed - code: ENGINE-408 message: Unable to load currencies. - code: ENGINE-409 message: We have exhausted all unique ids for an EDM table. Please use another EDM to import data. - code: ENGINE-410 message: Sorry, we encountered an error. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-411 message: Sorry, we encountered an error while running underlying ensemble-loader analysis. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: ENGINE-412 message: Fire following is not supported for the selected region and engine version. - code: ENGINE-413 message: Database upgrade failed. %s - code: ENGINE-414 message: Unable to find the metadata for the following analyses in the report %s - code: ENGINE-415 message: Sorry, we can't generate the CA DOI report because your portfolio doesn't include California locations covered by earthquake policies. - code: ENGINE-416 message: 'Sorry, we can not find variationId for the given analysisId: %s' - code: ENGINE-417 message: 'Sorry, we can''t import this RDM because the following groups contain cycles: %s.' - code: ENGINE-418 message: 'The EDM database might have an invalid schema. Error: %s.' - code: ENGINE-419 message: The DLM exposure data might have some invalid entries. Please check the data and try again. - code: ENGINE-420 message: The DLM job timed out while processing a large dataset. Please try reducing the exposure size and try again. - code: ENGINE-421 message: The DLM job failed to parse the profile settings. Please check the profile settings and try again. - code: ENGINE-422 message: The DLM job failed because at least one location contains invalid coordinates. Latitude values must range from -90 to 90, and longitude values must range from -180 to 180. - code: ENGINE-423 message: Failed to downgrade database schema to target version. %s - code: ENGINE-424 message: HD job failed because the specified exposure was not found. Please verify the exposure ID and try again. - code: ENGINE-425 message: Sorry, we are unable to export this database because it contains encrypted objects. Please remove the encryption from the database and try again, or contact Support at `RMSSupport@moodys.com` for assistance. - domain: ENRICHMENT_SERVICE count: 7 codes: - code: ENRICH_EXPOSURE-001 message: When createBackup is true, backupDetails is required. - code: ENRICH_EXPOSURE-002 message: When createBackup is true, backupDetails.exposureName and backupDetails.exposureNumber are required. - code: ENRICH_EXPOSURE-003 message: When createBackup is true, backupDetails.exposureResourceName and backupDetails.exposureResourceNumber are required. - code: ENRICH_EXPOSURE-004 message: '%s' - code: ENRICH_EXPOSURE-005 message: '%s' - code: ENRICH_EXPOSURE-006 message: Both fields retrieveData and transferData are false. At least one of them should be true. - code: ENRICH_EXPOSURE-007 message: The field createBackup cannot be true when transferData is false. - domain: ENT count: 14 codes: - code: ENT-001 message: Sorry, this could be an error on our end. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: ENT-002 message: Sorry, this could be an error on our end. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: ENT-003 message: You cannot run this analysis because you do not have a current model license. Check with your Intelligent Risk Platform administrator to find out which models are licensed by your organization. - code: ENT-004 message: '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 Intelligent Risk Platform administrator to find out which models are licensed by your organization.' - code: ENT-005 message: '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 Intelligent Risk Platform administrator to find out which models are licensed by your organization.' - code: ENT-006 message: '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 Intelligent Risk Platform administrator to find out which models are licensed by your organization.' - code: ENT-007 message: 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 Intelligent Risk Platform administrator to find out which ALM models you license. - code: ENT-008 message: '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 Intelligent Risk Platform administrator to find out which models are licensed by your organization.' - code: ENT-009 message: Sorry, this could be an error on our end. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: ENT-010 message: '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 Intelligent Risk Platform administrator to find out which models are licensed by your organization.' - code: ENT-011 message: 'You cannot run hazard analysis with the following layer(s) because you do not license them: %s. Check with your Intelligent Risk Platform administrator to find out which hazard layers are licensed by your organization.' - code: ENT-012 message: You cannot run exposure enrichment because you do not license it. Check with your Intelligent Risk Platform administrator to find out what is licensed by your organization. - code: ENT-013 message: '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, Analysis type: %s. Check with your Intelligent Risk Platform administrator to find out which models are licensed by your organization.' - code: ENT-014 message: 'You cannot run an analysis with the following settings because you do not license them: Peril: %s, Region: %s, Custom Hazard: %s. Check with your Intelligent Risk Platform administrator to find out which models are licensed by your organization.' - domain: EVENTINFO count: 2 codes: - code: EVENTINFO-401 message: Database error occurred, rate scheme does not exists - code: EVENTINFO-502 message: 'Database error occurred while saving rate scheme for database with Id: %d' - domain: EXTRACT-ELT count: 1 codes: - code: EXTRACT-ELT-001 message: Invalid argument for %s - domain: EXP count: 41 codes: - code: EXP-500 message: 'Database error occurred while updating time stamps for Exposure Type: %s, Exposure Id: %d' - code: EXP-501 message: 'Exposure with database name : %s not found' - code: EXP-001 message: Could not parse URL, reason %s - code: EXP-502 message: Database error occurred while determining exposure name - code: EXP-503 message: Database error occurred while calculating number of locations - code: EXP-504 message: Database error occurred while saving exposure owner - code: EXP-505 message: Database error occurred while determining exposure number - code: EXP-506 message: Database error occurred while checking whether exposure has owner - code: EXP-507 message: Database error occurred while saving exposure audit history - code: EXP-508 message: Database error occurred while updating exposure metrics - code: EXP-509 message: Error occurred while fetching the HD results for analysis id %d - code: EXP-510 message: Active Database backup operation is in-progress for DB %s - code: EXP-511 message: Database error occurred while getting geocode summary - code: EXP-512 message: Database error occurred while getting hazard summary - code: EXP-513 message: Database error occurred while exporting portfolio - code: EXP-514 message: Database error occurred while exporting account - code: EXP-515 message: Database error occurred while updating exposure revision table - code: EXP-516 message: Database error occurred while calculating exposure workers compensation - code: EXP-517 message: Database error occurred while calculating number of policies - code: EXP-518 message: Database error occurred while updating metrics - code: EXP-519 message: Peril code %s is not supported for the Exposure Summary report. Select a supported peril. - code: EXP-520 message: Hazard name %s is not supported for the Exposure Summary report. Select a supported hazard. - code: EXP-521 message: Error occurred while %s batch data - code: EXP-522 message: Treaty number %s already exists in EDM - code: EXP-524 message: 'Primary Location details not found for accountId: %s, siteName: %s' - code: EXP-525 message: Database error occurred while exporting aggregate portfolio - code: EXP-526 message: Validation Error encountered for %s - code: EXP-527 message: '%s' - code: EXP-528 message: Sorry, input should be contained with one or more exposure input(s). - code: EXP-529 message: Failed to copy exposure %d. - code: EXP-530 message: Job input for id %s could not be found on S3. Please verify the id and try again. - code: EXP-531 message: 'Job event ids input are not correct: %s.' - code: EXP-532 message: 'Sorry, the following export fields provided for location results are invalid: %s. Please check that your requests specify valid export fields.' - code: EXP-533 message: 'Job input for folderId: %s fileName: %s could not be found on S3. Please verify the folderId and the fileName and try again.' - code: EXP-534 message: Sorry, we encountered an error retrieving information about %s with id %d. Try again, and contact Support if this still does not work. - code: EXP-535 message: Exposure Summary reports only support up to %d locations - code: EXP-536 message: 'Error occurred while %s batch data: %s' - code: EXP-537 message: Failed to submit move database job. Please try again or contact your administrator. - code: EXP-538 message: 'Database error occurred during export process: Schema definition of the source EDM is not valid for the table mentioned in the following message. %s' - code: EXP-539 message: Location and policy conditions batch edit is not enabled. Remove policyConditions and locationConditions from the request. - code: EXP-540 message: For %s conditions batch input field %s is missing or contains a wrong value. - domain: EXPORT count: 48 codes: - code: EXPORT-001 message: There was an unexpected issue that occurred while moving the EDMs. - code: EXPORT-002 message: To export locations, policies, treaties, peril details, and/or reinsurance, you must also export accounts. - code: EXPORT-003 message: To export reinsurance and/or peril details, you must also export locations. - code: EXPORT-004 message: To export data to an EDM, you must specify the source EDM. - code: EXPORT-005 message: To export data to an EDM, you must specify the destination EDM. - code: EXPORT-006 message: The source EDM does not exist. Please choose a valid source EDM and try again. - code: EXPORT-007 message: The destination EDM does not exist. Please choose a valid destination EDM and try again. - code: EXPORT-008 message: To export data to an EDM, you must provide at least one exposure ID to export. - code: EXPORT-009 message: Error occurred while downloading the results for id %d - code: EXPORT-010 message: The export format is missing. Specify the export format as CSV or PARQUET. - code: EXPORT-011 message: 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. - code: EXPORT-012 message: The export format is invalid. Specify the export format as CSV or PARQUET. - code: EXPORT-013 message: 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. - code: EXPORT-014 message: Sorry, download to CSV or Parquet are not supported. - code: EXPORT-015 message: Sorry, you cannot download intermediate output data to CSV or Parquet files. This output is only supported for HD non-EP analyses. - code: EXPORT-016 message: 'Sorry, you have exceeded the supported number of multiple analyses for export location results: %s. Please provide a valid input and try again.' - code: EXPORT-017 message: Sorry, the financial perspective(s) %s you requested are not supported. See 'Financial Perspectives' in the Help Center for perspectives that are supported for different analysis types. - code: EXPORT-018 message: Sorry, the field(s) %s you requested are not supported for location results export. See 'Location Results Export' in the Help Center for the supported fields. - code: EXPORT-019 message: Sorry, you must provide at least one financial perspective or one export field to export location results. - code: EXPORT-020 message: Sorry, you can export location results only for account-level analyses. - code: EXPORT-021 message: 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. - code: EXPORT-022 message: Sorry, you must provide at least one export field to export location results for a non-EP analysis. - code: EXPORT-023 message: Sorry, you cannot export location results for non-EP analyses from an uploaded RDM that is not associated with an uploaded EDM. - code: EXPORT-024 message: Sorry, you cannot export location results for accounts that have more than %,d locations. Check the number of locations on the Accounts tab. - code: EXPORT-025 message: Sorry, you cannot export location results analyses from multiple EDMs. Enter analysis ids from the same EDM to export. - code: EXPORT-026 message: Sorry, you cannot export location results analyses from multiple accounts. Enter analysis ids from the same EDM and account to export. - code: EXPORT-027 message: 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. - code: EXPORT-028 message: Exporting equally weighted PLT is available only for a single EP analysis for HD or HD-ALM. This feature is only applicable to analyses run with weighted PET. To export the equally weighted PLT, you must also export loss table output with at least one financial perspective and at least one output level. - code: EXPORT-029 message: 'The export input is invalid for received export type: %s. Please provide a valid input and try again.' - code: EXPORT-030 message: 'The export input is invalid for received export id: %s. Please provide a valid input and try again.' - code: EXPORT-031 message: No data found for analysisId %s. Please make sure the input contains all valid analysisIds and try again. - code: EXPORT-032 message: Sorry, you must provide locationId as an export field to export location results for multiple analyses. - code: EXPORT-033 message: The export format is invalid. Specify the export format as CSV or JSON. - code: EXPORT-034 message: Sorry, you cannot export on %s engine sub type. - code: EXPORT-035 message: Sorry, you cannot perform export to file on %s engine sub type. - code: EXPORT-036 message: Sorry, you can not provide export type %s for received type %s. Check the export type and try again. - code: EXPORT-037 message: 'Sorry, Preserve IDs validation failed: You must export to a new EDM when you select the option to preserve IDs.' - code: EXPORT-038 message: Invalid SQL server version provided - code: EXPORT-040 message: You cannot specify a group for sharing a Data Bridge RDM if you export to an existing RDM or non dataBridge RDM. Export the results to a new RDM if you want to share the RDM with specific groups. - code: EXPORT-041 message: When share is true, you must provide the group id to share the RDM with. - code: EXPORT-042 message: You cannot specify groups when share is false. - code: EXPORT-043 message: Shuffled PLT Export is available only for a single EP analysis for HD or HD-ALM. Weighted PLTs are not supported. Also, to export the Shuffled PLT, you must select loss table output with at least one financial perspective and at least one output level. - code: EXPORT-044 message: Sorry, the field(s) you requested in lossDetails.outputLevels are not supported for export to RDM. - code: EXPORT-045 message: The export format is invalid. The lossDetails in the input is provided. Specify the export format as CSV, PARQUET, RDM, or RDM_DATABRIDGE. - code: EXPORT-046 message: 'Invalid schema version format: %s. Expected format is: V followed by valid schema version digits.' - code: EXPORT-047 message: Target version %s must be lower than source version %s for downgrade export. Same version export (e.g., V25 to V25) is only supported when the source version is V25 (latest). - code: EXPORT-048 message: The requested feature is not available for your tenant. Please contact support to enable this feature. - code: EXPORT-049 message: At least one of %s must be non-empty. - domain: EXPOSURE-SET count: 23 codes: - code: EXPOSURE-SET-001 message: Provide either the exposureSetId or the groupIds but not both. - code: EXPOSURE-SET-002 message: The exposureSetId %s is invalid. Use the RM GET /v1/exposuresets API to get a list of valid exposureSetId's. - code: EXPOSURE-SET-003 message: The groupIds %s are invalid. Use the SML GET /v1/Profile/groups API to get a list of valid groupId's. - code: EXPOSURE-SET-004 message: The operation %s is not valid for given property. - code: EXPOSURE-SET-005 message: The request includes %s Use the SML GET /v1/Profile/groups API to get a list of valid groupId's. - code: EXPOSURE-SET-006 message: Sorry, you do not have access to exposureSetId %s. Check the Id and try again. - code: EXPOSURE-SET-007 message: Sorry, you can not perform this operation because you are not a member of the group. - code: EXPOSURE-SET-008 message: Sorry, we encountered an error on our end while querying exposure sets. Try again, and contact Support if this still does not work. - code: EXPOSURE-SET-009 message: Sorry, we can't find %s %s. Either it doesn't exist or you don't have access to it. - code: EXPOSURE-SET-010 message: Sorry, you can not provide %s in case of no share. - code: EXPOSURE-SET-011 message: Provide either the exposureSetId or the dataSourceName but not both. - code: EXPOSURE-SET-012 message: Sorry, you can not provide same group value in add and remove operations. - code: EXPOSURE-SET-013 message: Exposure already exists for exposureSet %s. Cannot create multiple exposures under the same exposureSet. - code: EXPOSURE-SET-014 message: User is not the owner of the exposureSet %s - code: EXPOSURE-SET-015 message: Exposure already exists for exposureSetId %d. Please provide a valid exposureSetId. - code: EXPOSURE-SET-017 message: Group %s not found for this tenant - code: EXPOSURE-SET-018 message: Error encountered while creating exposure set - code: EXPOSURE-SET-019 message: Error encountered while updating exposure set with id %s - code: EXPOSURE-SET-020 message: No groups returned for the tenant - code: EXPOSURE-SET-021 message: '%s' - code: EXPOSURE-SET-022 message: The exposure set name is empty. Please provide a valid input. - code: EXPOSURE-SET-023 message: Error encountered while Deleting exposure set with id %s - code: EXPOSURE-SET-024 message: Error encountered while Archiving exposure set with id %s - domain: FAC count: 17 codes: - code: FAC-404 message: '%s' - code: FAC-406 message: '%s' - code: FAC-409 message: '%s' - code: FAC-500 message: Database error occurred while retrieving fac layers - code: FAC-501 message: 'Database error occurred while creating facultative with name: %s' - code: FAC-502 message: Database error occurred while checking for existing facultative - code: FAC-503 message: Database error occurred, facultative already exists - code: FAC-504 message: 'Database error occurred, facultative with id: %s not exists' - code: FAC-505 message: Database error occurred, while retrieving facultatives - code: FAC-506 message: Database error occurred while updating facultative - code: FAC-507 message: 'Database error occurred while loading facultative with id: %s' - code: FAC-508 message: 'A facultative cession with name: %s already exists. Use a different name.' - code: FAC-509 message: Validation error, facultative id cannot be null or empty. - code: FAC-510 message: Validation error, facultative, some of the String field has exceeded allowed length. - code: FAC-511 message: Database error occurred, facultative has relation to policy or location and cannot be %s - code: FAC-512 message: Database error occurred while checking if facultative has relation with policy or location - code: FAC-513 message: 'Database error occurred while deleting facultative with id: %s' - domain: FILE count: 32 codes: - code: FILE-001 message: Bucket %d does not exist - code: FILE-002 message: Unable to access bucket %d - code: FILE-003 message: File %s does not exist - code: FILE-004 message: Unable to access file %d - code: FILE-005 message: Not authorized to grant temporary credentials - code: FILE-006 message: S3 Object %s does not exist - code: FILE-007 message: Sorry, we're having trouble reading the import file. Check the file format and delimiter and try again. - code: FILE-009 message: Sorry, looks there might be a problem on our end. Try saving again, and contact Support if this still does not work. - code: FILE-010 message: The selected resolution requires a secondary resolution as well. This secondary resolution is missing from the import file. - code: FILE-011 message: The selected resolution requires a secondary resolution as well. This secondary resolution is incorrect for the resolution in the import file. - code: FILE-014 message: Sorry, we're having some trouble on our end. Try again, and contact Support if this still does not work. - code: FILE-015 message: Sorry, we're having trouble with the column mapping in the import file and cannot complete the import. - code: FILE-016 message: Sorry, we're having trouble with provided resolution. Please check the resolution, try again and contact Support if this still does not work. - code: FILE-017 message: 'Sorry, we''re having trouble with retrieving the following missing files: %s. Try to import again. If this still doesn''t work, email Support at `RMSSupport@Moodys.com`.' - code: FILE-018 message: 'Sorry, we''re having trouble with uploading empty files: %s. Please check.' - code: FILE-019 message: Sorry, we can't start this import because you didn't provide any files for import. - code: FILE-020 message: Sorry, we can't start this import because you haven't provided any CSV or TXT import files. For help about ALM import files, paste this URL in your browser to access the Risk Modeler help center https://help.rms.com/help/RiskModeler/dev/Content/RM_HowTo/ALMAggPortCreate.htm (sign in to Risk Modeler for the link to work). - code: FILE-500 message: Error occurred creating a new bucket - code: FILE-505 message: Error occurred staging bucket %d - code: FILE-506 message: Error occurred checking if bucket %d exists - code: FILE-507 message: Error occurred checking bucket %d permissions - code: FILE-508 message: Sorry, there's something wrong with the import file. Check that file type is valid. - code: FILE-509 message: Sorry, there's something wrong with the import file. Check that delimiter is valid. - code: FILE-510 message: Error occurred creating a new file - code: FILE-511 message: Error occurred retrieving file %d - code: FILE-512 message: Error occurred searching for files - code: FILE-513 message: Sorry, there's something wrong with the mapping. Check that country code and resolution are supported. - code: FILE-514 message: Sorry, missing or unsupported file extension for this input type. - code: FILE-515 message: Error occurred checking if file %d exists - code: FILE-516 message: Sorry it seems that the file that you have provided is not a valid ALM file. - code: FILE-520 message: Error occurred inserting import file record - code: FILE-521 message: Error occurred reading import file records - domain: GE count: 9 codes: - code: GE-001 message: 'Invalid exposure type. Valid exposure types are ACCOUNT and PORTFOLIO. Exposure type given: %s' - code: GE-002 message: Account bulk edit cannot be preformed on account exposure - code: GE-003 message: 'Validation failed: %s' - code: GE-004 message: Some data types in the WHERE clause do not match the data types of the respective fields - code: GE-005 message: Some data types in the SET clause do not match the data types of the respective fields - code: GE-006 message: Sorry, the provided date is invalid. %s - code: GE-007 message: List of updates provided in input is invalid for Basic Bulk Edit. - code: GE-008 message: Edit Query provided in input cannot be null or empty for Advanced Bulk Edit. - code: GE-501 message: An unexpected error occurred while preforming bulk edit on account %d - domain: GEO_SERVICE count: 9 codes: - code: GEO_SERVICE-001 message: 'You have provided an invalid geoHaz engine type: %s. Engine type must be RL or HD.' - code: GEO_SERVICE-002 message: 'You have provided an invalid data type for field: %s. Value must be true or false.' - code: GEO_SERVICE-003 message: Your input is missing the required layerOptions. - code: GEO_SERVICE-004 message: 'Your input is missing property: %s for layerOptions.' - code: GEO_SERVICE-005 message: 'You have provided an invalid value for layerOptions property: %s. Enter 0 for engineType RL or 1 for engineType HD.' - code: GEO_SERVICE-006 message: 'You have provided an invalid geoHaz name: %s or version: %s for the engineType: %s. Only specific names and versions are valid.' - code: GEO_SERVICE-007 message: 'You have provided an invalid geoHaz type: %s. GeoHaz type must be geocode or hazard.' - code: GEO_SERVICE-008 message: 'You have provided an invalid engine type: %s. Geocode with LiaaS engine type is supported only for location level.' - code: GEO_SERVICE-009 message: There is no input provided in the liProfile. The list is null or empty. - domain: GROUPING count: 15 codes: - code: GROUPING-001 message: Sorry, we encountered an error running your grouping job. Contact Support at`RMSSupport@moodys.com`to resolve this issue. - code: GROUPING-002 message: Invalid argument for %s - code: GROUPING-003 message: Group must contain at least one analysis - code: GROUPING-004 message: 'Invalid region code: %s' - code: GROUPING-006 message: Invalid rate scheme data - code: GROUPING-008 message: '%s is mapped to multiple rate scheme ids %s' - code: GROUPING-009 message: Unable to load analysis %s - code: GROUPING-010 message: 'Unable to load analysis group with id: %s' - code: GROUPING-011 message: Analysis %s is not a group - code: GROUPING-012 message: We can not process this job because the analysis %s is already an independent group - code: GROUPING-013 message: We can not process this job because the analysis %s is an HD group - code: GROUPING-014 message: We can not process this job because the analysis %s is a Marginal Impact Analysis - code: GROUPING-015 message: We can not process this job because the analysis %s is a CEP or CEP Group engine type. - code: GROUPING-016 message: We can not process this job because the underlying analyses have different exposure types. - code: GROUPING-017 message: We can not process this job because the underlying analyses are not associated with an EDM. - domain: HPC count: 13 codes: - code: HPC-001 message: Unknown task type - code: HPC-501 message: 'Failed to create HPC job. Error: %s' - code: HPC-502 message: 'Failed to create HPC task. Error: %s' - code: HPC-503 message: 'Failed to submit HPC job. Error: %s' - code: HPC-504 message: Failed to submit HPC job - code: HPC-505 message: 'Failed to get HPC job details. Response code: %d. Error: %s' - code: HPC-506 message: Failed to get HPC job details - code: HPC-507 message: 'Failed to cancel HPC job. Response code: %d. Error: %s' - code: HPC-508 message: Failed to cancel HPC job - code: HPC-509 message: Failed to set environment variables for HPC job - code: HPC-510 message: Failed to get HPC job task details - code: HPC-511 message: 'Failed to get HPC job task details. Response code: %d. Error: %s' - code: HPC-512 message: Failed to check HPC job status. Failed after multiple retries - domain: IAM count: 24 codes: - code: IAM-001 message: Credentials are required to access this resource - code: IAM-002 message: No databases found for user - code: IAM-003 message: User %d was not found - code: IAM-004 message: User group %d was not found - code: IAM-005 message: User reporting currency was not found for user %d - code: IAM-500 message: Internal error occurred retrieving user profile - code: IAM-501 message: Internal error occurred retrieving a user's databases - code: IAM-502 message: Error getting user information - code: IAM-503 message: Error occurred creating a new user token - code: IAM-504 message: Error occurred updating a user token - code: IAM-505 message: Error occurred deleting a user token - code: IAM-506 message: Error occurred validating a user token - code: IAM-507 message: Internal error occurred retrieving a user group information - code: IAM-508 message: Database error occurred while adding security log - code: IAM-509 message: Error occurred while encrypting string - code: IAM-510 message: The new password and confirmation password do not match - code: IAM-511 message: Error occurred updating a user password - code: IAM-512 message: Password cannot be null or empty - code: IAM-513 message: Password cannot be longer than 18 characters - code: IAM-514 message: Invalid user ID - code: IAM-515 message: Error occurred while retrieving list of tenant Ids - code: IAM-516 message: Error occurred while retrieving list of EDMs assigned to tenant - code: IAM-517 message: 'Database error occurred while saving Group DB Detail for DbId: %d' - code: IAM-518 message: Database error occurred while retrieving Tenant EDM metrics - domain: IMPORT_STORE count: 13 codes: - code: IMPORT_STORE-401 message: Database error occurred, IMPORT_STORE does not exists - code: IMPORT_STORE-501 message: 'Database error occurred while loading IMPORT_STOREs, reason : %s' - code: IMPORT_STORE-502 message: 'Database error occurred while creating IMPORT_STORE, reason : %s' - code: IMPORT_STORE-503 message: 'Database error occurred while updating IMPORT_STORE, reason : %s' - code: IMPORT_STORE-504 message: 'Database error occurred while deleting IMPORT_STORE, reason : %s' - code: IMPORT_STORE-505 message: Database error occurred duplicate IMPORT_STORE, IMPORT_STORE already exists - code: IMPORT_STORE-506 message: Validation error, IMPORT_STORE id cannot be null. - code: IMPORT_STORE-507 message: Validation error, IMPORT_STORE id length has to be between 1 and 20. - code: IMPORT_STORE-508 message: Validation error, IMPORT_STORE, some of the String field has exceeded allowed length. - code: IMPORT_STORE-509 message: Could not parse URL, reason %s - code: IMPORT_STORE-510 message: Unknown DbType, only EDM, RDM, EXPOSURE_BATCH_EDIT or BATCH DbType is supported - code: IMPORT_STORE-511 message: Validation error, file names must be named in a GUID format. With an appropriate %s extension. - code: IMPORT_STORE-512 message: Validation error, file names must share the same name with different extensions. - domain: IMP count: 13 codes: - code: IMP-001 message: The account, location, and/or reinsurance file for this import is empty. Provide a valid file and try the import again. - code: IMP-002 message: Sorry, we're having trouble reading the import file %s. Check the file and try again. - code: IMP-003 message: 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. - code: IMP-004 message: Duplicate portfolio ids. PortfolioIds must be unique. - code: IMP-005 message: 'Error occurred extracting data from file %d. Error: %s' - code: IMP-006 message: 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. - code: IMP-007 message: PortfolioIds cannot be null or empty. - code: IMP-500 message: Sorry, we encountered an error while performing this import. Try again, and contact Support if this still does not work. - code: IMP-501 message: Error occurred validating import data - code: IMP-502 message: Error occurred extracting data from file %d - code: IMP-503 message: Error occurred creating the mapping file - code: IMP-504 message: Error occurred creating the account file - code: IMP-505 message: Sorry, it looks like there's a problem with the location file. Verify the account number and the selected delimiter, and try again. - domain: INFR count: 1 codes: - code: INFRA-001 message: Submit job failed. Please resubmit job. - domain: INT count: 7 codes: - code: INT-500 message: '%s' - code: INT-501 message: An internal parser error occurred, found an unknown value type - code: INT-502 message: An internal parser error occurred, error loading domain data for domain %s, tablespace %s, entity %s - code: INT-999 message: An unexpected error occurred - code: INT-409 message: The `X-RMS-REQUESTID` :%s provided is currently being used in another request. This occurs if you are making duplicate requests simultaneously. Please retry after 10 seconds - code: INT-400 message: '%s' - code: INT-404 message: '%s' - domain: JOB count: 22 codes: - code: JOB-001 message: Job %s was not found - code: JOB-002 message: Unable to access job %d - code: JOB-003 message: 'Failed to cancel the Job Id %d. Error: %s' - code: JOB-500 message: 'Database error occurred while retrieving execution status for Job Id: %d' - code: JOB-501 message: Database error occurred while searching for jobs - code: JOB-502 message: Database error occurred while getting job Id %d - code: JOB-503 message: Database error occurred while checking if user is authorized to cancel job %d - code: JOB-504 message: Database error occurred while canceling job %d - code: JOB-505 message: 'Database error occurred while archiving job details for job id: %d' - code: JOB-506 message: 'Database error occurred while retrieving job report message for JobId: %d, Service Id: %d' - code: JOB-507 message: 'Database error occurred while retrieving job identifier for account id: %d' - code: JOB-508 message: 'Database error occurred while retrieving job details for account id: %d' - code: JOB-509 message: 'Database error occurred while retrieving services for account id: %d' - code: JOB-510 message: 'Database error occurred while retrieving job report for Job Id: %d, Service Id: %d' - code: JOB-511 message: 'Database error occurred while retrieving user details for Job Type: %s, Job Id: %d' - code: JOB-512 message: 'Database error occurred while retrieving job status for Job Id: %d' - code: JOB-513 message: 'Error occurred. Invalid job status found for Job Id: %d' - code: JOB-514 message: 'Database error occurred while retrieving job id from commit queue for account Id: %d' - code: JOB-515 message: 'Database error occurred while retrieving job status from commit queue for Job Id: %d' - code: JOB-516 message: Database error occurred while searching for job monitoring records - code: JOB-517 message: 'Database error occurred deleting job monitoring record Id: %d' - code: JOB-518 message: Sorry, user %s is not allowed to update the %s job priority due to no access to %s resource group - domain: JOB (Platform Error) count: 15 codes: - code: JOB-601 message: Sorry, both status and priority provided in same request. Please check and try again - code: JOB-602 message: Sorry, update operation not allowed for job id %s with status %s - code: JOB-603 message: Invalid resource uri %s is provided - code: JOB-604 message: Invalid resource type %s is provided - code: JOB-605 message: Invalid job type %s is provided - code: JOB-606 message: Sorry, there is no job id %s for this user %s - code: JOB-607 message: Invalid jobId %s is provided - code: JOB-608 message: Sorry, provide either status or priority in request. - code: JOB-609 message: Sorry, cancellation is not supported for %s job. - code: JOB-610 message: Sorry, priority update is not supported for %s job. - code: JOB-611 message: Sorry, startedAt date is not in a valid range for %s job. - code: JOB-612 message: Invalid entitlement '%s' is provided. Supported entitlements are %s - code: JOB-613 message: Sorry, user %s is not allowed to update/cancel %s job due to no access to %s resource group. - code: JOB-614 message: Sorry, user %s is not allowed to access these %s resource group ids. - code: JOB-615 message: Invalid taskId %s is provided - domain: JOBSERVICE count: 16 codes: - code: PROFILE-001 message: Profile not found - code: PROFILE-002 message: Profile type not implemented - code: PROFILE-003 message: Illegal Argument - code: PROFILE-004 message: Unsupported Operation - code: PROFILE-501 message: Failed to get profile type - code: EXPOSURE-001 message: Exposure not found - code: TREATIES-501 message: Failed to save treaties - code: HISTOGRAM-501 message: Failed to get core configuration from Histogram DB - code: CONFIG-501 message: Failed to create job configuration - code: DBMANAGER-001 message: 'Query error. Reason: %s' - code: STOREMANAGER-001 message: 'Record not found for type: %s and Identifier: %s' - code: EDM-508 message: Failed to find the EDM - code: SUBMITJOB-500 message: 'Submit job failed. Error: %s' - code: GETJOB-500 message: 'Get job failed. Error: %s' - code: CANCELJOB-500 message: 'Cancel job failed. Error: %s' - code: GETTASKS-500 message: 'Get tasks failed. Error: %s' - domain: KS count: 8 codes: - code: KS-001 message: The tenant id in a key and URL must match - code: KS-003 message: Operation not supported; The value should be CREATE, READ, UPDATE or DELETE only - code: KS-004 message: Key exists - code: KS-005 message: Key does not exist - code: KS-006 message: Value cannot be empty - code: KS-007 message: 'Key not found in baseline properties: %s' - code: KS-008 message: Sorry, this could be an error on our end. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - code: KS-009 message: Sorry, this could be an error on our end. Try again, and contact Support at `RMSSupport@moodys.com` if this still doesn't work. - domain: LINE_OF_BUSINESS count: 14 codes: - code: LINE_OF_BUSINESS-401 message: Database error occurred, line of business does not exists - code: LINE_OF_BUSINESS-404 message: '%s' - code: LINE_OF_BUSINESS-406 message: '%s' - code: LINE_OF_BUSINESS-409 message: '%s' - code: LINE_OF_BUSINESS-501 message: 'Database error occurred while loading line of business, reason : %s' - code: LINE_OF_BUSINESS-502 message: 'Database error occurred while creating line of business, reason : %s' - code: LINE_OF_BUSINESS-503 message: 'Database error occurred while updating line of business with Id: %s, reason : %s' - code: LINE_OF_BUSINESS-504 message: 'Database error occurred while deleting line of business with Id: %s, reason : %s' - code: LINE_OF_BUSINESS-505 message: Sorry, this LOB name already exists. Try using a different name. - code: LINE_OF_BUSINESS-506 message: Validation error, line of business, the name field has exceeded allowed length. - code: LINE_OF_BUSINESS-507 message: Database error occurred while validating LOB details. - code: LINE_OF_BUSINESS-508 message: Line of business validation failed. - code: LINE_OF_BUSINESS-509 message: Line of business validation failed while validating LOB details. You have duplicate LOB names for treaties - code: LINE_OF_BUSINESS-510 message: Line of business validation failed while inserting new LOB details. LOB name already exists. - domain: LOC count: 166 codes: - code: LOC-001 message: Location %d was not found - code: LOC-002 message: Account %d, for location %d, was not found - code: LOC-003 message: Do not have sufficient permission to location %d - code: LOC-004 message: The floors occupied exceed the number of stories. Change one of these values. - code: LOC-005 message: Facultative cession layer information is mandatory when reinsurance cession is Facultative - code: LOC-006 message: Treaty information is mandatory when reinsurance cession is Treaty - code: LOC-007 message: Do not have sufficient permission on given locations - code: LOC-008 message: You must enter a value for at least one building or contents coverage for the combined coverage limits and deductibles to apply - code: LOC-009 message: 'Location Business Interruption Detail Id: %d was not found for Location Id: %d' - code: LOC-010 message: 'Location Building Attribute Id: %d was not found for Location Id: %d' - code: LOC-011 message: 'Insufficient information to geocode the location. Please provide additional address information. The minimum required fields are: City & State, ZIP Code, OR Latitude & Longitude' - code: LOC-012 message: The primary building of a multi-building site cannot be deleted. To delete this building, configure it as a secondary building. - code: LOC-013 message: 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. - code: LOC-014 message: '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' - code: LOC-015 message: '%s cannot be assigned to secondary buildings on a multi-building campus.' - code: LOC-016 message: Ensure location is geocoded before running hazard lookup - code: LOC-017 message: Start date should be less than or equal to Completion date - code: LOC-018 message: '%s' - code: LOC-019 message: 'Database error occurred while retrieving Location Id: %d' - code: LOC-020 message: Site Limit should be between 0 to 1e+14 - code: LOC-021 message: Site Deductible should be between 0 to 1e+14 - code: LOC-022 message: Location Coverage label may not be empty and label id should not be 0 - code: LOC-023 message: Invalid input. There are no locations associated with the given exposure - code: LOC-024 message: Inception date should be less than or equal to Expiration date - code: LOC-025 message: 'Location Earthquake Detail Id: %d was not found for Location Id: %d' - code: LOC-026 message: 'Location Windstorm Detail Id: %d was not found for Location Id: %d' - code: LOC-027 message: 'Location Flood Detail Id: %d was not found for Location Id: %d' - code: LOC-028 message: 'Location Fire Detail Id: %d was not found for Location Id: %d' - code: LOC-029 message: 'Location Terrorism Detail Id: %d was not found for Location Id: %d' - code: LOC-030 message: 'Location Tornado Detail Id: %d was not found for Location Id: %d' - code: LOC-031 message: 'Location Coverage Id: %d was not found for Location Id: %d' - code: LOC-032 message: 'Location Reinsurance Cession Id: %d was not found for Location Id: %d' - code: LOC-033 message: 'Location Workers Compensation Id: %d was not found for Location Id: %d' - code: LOC-034 message: 'Location Condition Id: %d was not found for Location Id: %d' - code: LOC-035 message: Invalid input. At least one location condition should be specified. - code: LOC-036 message: Location Currency code should not be null or empty. - code: LOC-037 message: 'Error while validating field %s. Value ''%s'' is in invalid date format. Expected: yyyy-MM-dd''T''HH:mm:ss.SSS''Z''' - code: LOC-038 message: Error while validating field %s. Value '%s' is not a supported date. - code: LOC-404 message: '%s' - code: LOC-500 message: Database error occurred while searching locations - code: LOC-501 message: 'Database error occurred while retrieving Location Id: %d' - code: LOC-502 message: 'Database error occurred while loading location currency information for Location Id: %d' - code: LOC-503 message: 'Database error occurred while loading parent account information for Location Id: %d' - code: LOC-504 message: Database error occurred while creating location - code: LOC-505 message: 'Database error occurred while deleting Location Id: %d' - code: LOC-506 message: 'Database error occurred while updating Location Id: %d' - code: LOC-508 message: 'Database error occurred while performing bulk edit of locations under Account Id: %d' - code: LOC-512 message: 'Database error occurred while checking if Location Reinsurance Cession Id: %d exists for Location Id: %d' - code: LOC-514 message: 'Database error occurred while retrieving Location Reinsurance Cession Id: %d for Location Id: %d' - code: LOC-515 message: 'Database error occurred while creating location reinsurance cession for Location Id: %d' - code: LOC-516 message: 'Database error occurred while updating Location Reinsurance Id: %d for Location Id: %d' - code: LOC-517 message: 'Database error occurred while deleting Location Reinsurance Id: %d for Location Id: %d' - code: LOC-518 message: 'Database error occurred while checking if Location Earthquake details Id: %d exists' - code: LOC-519 message: 'Database error occurred while retrieving location earthquake details for Location Id: %d' - code: LOC-520 message: 'Database error occurred while retrieving Location Earthquake details Id: %d' - code: LOC-521 message: 'Database error occurred while creating location earthquake details for Location Id: %d' - code: LOC-522 message: 'Database error occurred while updating Earthquake details Id: %d for Location Id: %d' - code: LOC-523 message: 'Database error occurred while deleting Earthquake details Id: %d for Location Id: %d' - code: LOC-524 message: 'Database error occurred while checking if Location Flood details Id: %d exists' - code: LOC-525 message: 'Database error occurred while retrieving location flood details for Location Id: %d' - code: LOC-526 message: 'Database error occurred while retrieving Location Flood details Id: %d' - code: LOC-527 message: 'Database error occurred while creating location flood details for Location Id: %d' - code: LOC-528 message: 'Database error occurred while updating Flood details Id: %d for Location Id: %d' - code: LOC-529 message: 'Database error occurred while deleting Flood details Id: %d for Location Id: %d' - code: LOC-530 message: 'Database error occurred while checking if Location Fire details Id: %d exists' - code: LOC-531 message: 'Database error occurred while retrieving location fire details for Location Id: %d' - code: LOC-532 message: 'Database error occurred while retrieving Location Fire details Id: %d' - code: LOC-533 message: 'Database error occurred while creating location fire details for Location Id: %d' - code: LOC-534 message: 'Database error occurred while updating Fire details Id: %d for Location Id: %d' - code: LOC-535 message: 'Database error occurred while deleting Fire details Id: %d for Location Id: %d' - code: LOC-536 message: 'Database error occurred while checking if Location Windstorm details Id: %d exists' - code: LOC-537 message: 'Database error occurred while retrieving location windstorm details for Location Id: %d' - code: LOC-538 message: 'Database error occurred while retrieving Location Windstorm details Id: %d' - code: LOC-539 message: 'Database error occurred while creating location windstorm details for Location Id: %d' - code: LOC-540 message: 'Database error occurred while updating Windstorm details Id: %d for Location Id: %d' - code: LOC-541 message: 'Database error occurred while deleting Windstorm details Id: %d for Location Id: %d' - code: LOC-542 message: 'Database error occurred while checking if Location Tornado details Id: %d exists' - code: LOC-543 message: 'Database error occurred while retrieving location tornado details for Location Id: %d' - code: LOC-544 message: 'Database error occurred while retrieving Location Tornado details Id: %d' - code: LOC-545 message: 'Database error occurred while creating location tornado details for Location Id: %d' - code: LOC-546 message: 'Database error occurred while updating Tornado details Id: %d for Location Id: %d' - code: LOC-547 message: 'Database error occurred while deleting Tornado details Id: %d for Location Id: %d' - code: LOC-548 message: 'Database error occurred while checking if Location Terrorism details Id: %d exists' - code: LOC-549 message: 'Database error occurred while retrieving location terrorism details for Location Id: %d' - code: LOC-550 message: 'Database error occurred while retrieving Location Terrorism details Id: %d' - code: LOC-551 message: 'Database error occurred while creating location terrorism details for Location Id: %d' - code: LOC-552 message: 'Database error occurred while updating Terrorism details Id: %d for Location Id: %d' - code: LOC-553 message: 'Database error occurred while deleting Terrorism details Id: %d for Location Id: %d' - code: LOC-554 message: 'Database error occurred while checking if Location Worker Compensation details Id: %d exists' - code: LOC-556 message: 'Database error occurred while retrieving Location Worker Compensation details Id: %d' - code: LOC-557 message: 'Database error occurred while creating location worker compensation details for Location Id: %d' - code: LOC-558 message: 'Database error occurred while updating Worker Compensation details Id: %d for Location Id: %d' - code: LOC-559 message: 'Database error occurred while deleting Worker Compensation details Id: %d for Location Id: %d' - code: LOC-560 message: 'Database error occurred while checking if Location Business Interruption details Id: %d exists' - code: LOC-562 message: 'Database error occurred while retrieving Location Business Interruption details Id: %d' - code: LOC-563 message: 'Database error occurred while creating location business interruption details for Location Id: %d' - code: LOC-564 message: 'Database error occurred while updating Business Interruption details Id: %d for Location Id: %d' - code: LOC-565 message: 'Database error occurred while deleting Business Interruption details Id: %d for Location Id: %d' - code: LOC-566 message: 'Database error occurred while checking if Location Coverage details Id: %d exists' - code: LOC-567 message: 'Database error occurred while checking coverage dependency for Location Id: %d' - code: LOC-568 message: 'Database error occurred while retrieving Location Coverage details Id: %d' - code: LOC-569 message: 'Database error occurred while creating location coverage details for Location Id: %d' - code: LOC-570 message: 'Database error occurred while updating Coverage details Id: %d for Location Id: %d' - code: LOC-571 message: 'Database error occurred while deleting Coverage details Id: %d for Location Id: %d' - code: LOC-573 message: 'Database error occurred while calculating number of employees for Location Id: %d' - code: LOC-574 message: 'Database error occurred while checking if Building Attribute details Id: %d exists' - code: LOC-575 message: 'Database error occurred while creating building attribute details for Location Id: %d' - code: LOC-576 message: 'Database error occurred while updating Building Attribute details Id: %d for Location Id: %d' - code: LOC-577 message: 'Database error occurred while deleting Building Attribute details Id: %d' - code: LOC-578 message: 'Database error occurred while checking if Location Condition details Id: %d exists for Location Id: %d' - code: LOC-580 message: 'Database error occurred while retrieving Location Condition details Id: %d' - code: LOC-581 message: 'Database error occurred while creating location condition details for Location Id: %d' - code: LOC-582 message: 'Database error occurred while updating Condition details Id: %d for Location Id: %d' - code: LOC-583 message: 'Database error occurred while deleting Condition details Id: %d for Location Id: %d' - code: LOC-584 message: 'Database error occurred while retrieving policy conditions list by Location Id: %d' - code: LOC-585 message: 'Database error occurred while querying location information for Location Id: %d' - code: LOC-586 message: 'Error occurred while geocoding Location Id: %d' - code: LOC-587 message: 'Error occurred while geocoding Street Address: %s' - code: LOC-588 message: 'Error occurred while running hazard on Location Id: %d' - code: LOC-589 message: 'Error occurred while running hazard on Street Address: %s' - code: LOC-590 message: 'Database error occurred while checking if Construction Class valid for Building Class Scheme: %s, Building Class: %s' - code: LOC-591 message: 'Database error occurred while checking if Occupancy Type valid for Occupancy Type Scheme: %s, Occupancy Type: %s' - code: LOC-592 message: 'Database error occurred while checking if MSB Construction Class valid for Building Class Scheme: %s, Building Class: %s' - code: LOC-593 message: 'Database error occurred while retrieving Construction Code for Building Class Scheme: %s, Building Class: %s' - code: LOC-594 message: 'Database error occurred while retrieving MSB Construction Code for ATC Constriction Code: %s' - code: LOC-595 message: 'Database error occurred while retrieving Occupancy Code for Occupancy Type Scheme: %s, Occupancy Type' - code: LOC-596 message: 'Database error occurred while retrieving Location IDs for the AccountId: %d' - code: LOC-601 message: 'Database error occurred while checking if location is primary building for Multi-Building campus for Location Id: %d' - code: LOC-602 message: 'Database error occurred while getting count of secondary buildings for Multi-Building campus for Location Id: %d' - code: LOC-603 message: 'Database error occurred while checking if location is secondary building for Multi-Building campus for Location Id: %d' - code: LOC-604 message: Database error occurred while checking if site name is unique - code: LOC-605 message: 'Database error occurred while retrieving site names for Account Id: %d' - code: LOC-606 message: 'Database error occurred while back filling policy conditions for Location Id: %d and Condition Id: %d' - code: LOC-607 message: MSB security token authorization failure - code: LOC-608 message: Error occurred while updating the enhanced building attributes for ESDB - code: LOC-609 message: Multiple Combined Coverage entries on a location are not allowed for a single peril - code: LOC-610 message: 'Database error occurred while updating condition details for Location Id: %d' - code: LOC-611 message: '%s %d not found for location condition' - code: LOC-613 message: Location id %d for property does not exist - code: LOC-614 message: Duplicate Location id %s found in input - code: LOC-615 message: Invalid Occupancy type scheme provided for Worker Compensation details - code: LOC-616 message: 'Location Id: %d and Building Attribute Id: %d provided should be equal' - code: LOC-617 message: 'Address Id: %d provided for property is invalid for operationType: %s' - code: LOC-618 message: 'Duplicate Location Id: %d and Condition Id: %d found in input' - code: LOC-619 message: 'Invalid Location %s %s: %s. Value provided must not be null or empty and must be between %d and %d' - code: LOC-620 message: Invalid Location. Property and Address field cannot be null - code: LOC-621 message: Invalid Location. Location Number cannot be null or empty. - code: LOC-622 message: '%s cannot be greater than zero during location creation' - code: LOC-623 message: '%s details already exist for location Id: %d' - code: LOC-624 message: Exposure Enrichment for this location is not available - code: LOC-625 message: Database error occurred while searching enriched details for Location Id %d. - code: LOC-626 message: 'Job not submitted: Exposure enrichment requires RMS geocoding output in the range 1 < geoResolutionCode and geoResolutionCode < 5 for matching. Please run the geocoding process.' - code: LOC-627 message: 'Job not submitted: Exposure enrichment only available for U.S. locations.' - code: LOC-628 message: Job not submitted because the exposure does not contain enriched locations. Run exposure enrichment on the exposure. - code: LOC-629 message: Invalid location condition with %s %d.Condition does not belong to the location %d. - code: LOC-630 message: 'Database error occurred while deleting Condition details Id: %d' - code: LOC-631 message: 'Error occurred while validating Windstorm details: %s' - code: LOC-632 message: 'Error occurred while validating BI details: %s' - code: LOC-633 message: 'Error occurred while validating Terrorism details: %s' - code: LOC-634 message: 'Error occurred while validating Tornado details: %s' - code: LOC-635 message: 'Error occurred while validating Fire details: %s' - code: LOC-636 message: 'Error occurred while validating Flood details: %s' - code: LOC-637 message: 'Error occurred while validating Earthquake details: %s' - code: LOC-638 message: 'Error occurred while validating %s details: %s' - code: LOC-639 message: 'Error occurred while validating Location Coverage: %s' - code: LOC-640 message: 'Error occurred while validating Location Address: %s' - domain: LOC_RES count: 3 codes: - code: LOC_RES-001 message: No data found for export fields and perspectives - code: LOC_RES-002 message: No loss nor exposure found for analysis/account - code: LOC_RES-003 message: No location results schema found for analysis id %s - domain: MAP count: 2 codes: - code: MAP-001 message: Credentials are required to access this resource - code: MAP-002 message: '%s doesn''t include locations with lat/long information. To resolve this, run geocoding on it.' - domain: MAP-PERSPECTIVE count: 7 codes: - code: MAP-PERSPECTIVE-001 message: The source perspective code %s is invalid. Please check that your request specifies a valid perspective. - code: MAP-PERSPECTIVE-002 message: The target perspective code %s is invalid. Please check that your request specifies a valid perspective. - code: MAP-PERSPECTIVE-003 message: Sorry, we encountered an error on our end while mapping perspective for analysis id %d. Contact Support at`RMSSupport@moodys.com`. - code: MAP-PERSPECTIVE-004 message: Sorry, the target and source perspectives cannot be the same. Enter a target perspective different than the source perspective. - code: MAP-PERSPECTIVE-005 message: Sorry, perspective mapping is not supported for this analysis. Please enter a HD or non-simulated DLM or non-CEP analysis ID. - code: MAP-PERSPECTIVE-006 message: Sorry, you can map perspective only for portfolio or aggregate portfolio analyses. - code: MAP-PERSPECTIVE-007 message: Sorry, you can not perform map perspective on %s engine sub type. - domain: MARGINAL-IMPACT count: 12 codes: - code: MARGINAL-IMPACT-001 message: Invalid argument for %s - code: MARGINAL-IMPACT-002 message: Sorry, we encountered an error while submitting the Marginal Impact job. Try again, and contact Support if this still does not work. - code: MARGINAL-IMPACT-003 message: Sorry, you can perform marginal impact on %s engine type(s) only. - code: MARGINAL-IMPACT-004 message: Sorry, you can perform marginal impact on %s output type(s) only. - code: MARGINAL-IMPACT-005 message: The analysis is using unsupported exposure types. The reference analysis can be a portfolio or group. The marginal impact analysis can be an account. - code: MARGINAL-IMPACT-006 message: We were unable to find the exposure used while generating the input analysis. %s. - code: MARGINAL-IMPACT-007 message: Sorry, you can not perform marginal impact on %s engine sub type. - code: MARGINAL-IMPACT-008 message: Sorry, the reference analysis's engine type can only be DLM or GROUP with DLM-only underlying analyses. - code: MARGINAL-IMPACT-009 message: You cannot run a marginal impact analysis on this group. Only groups of HD + HD, HD + DLM, or DLM + DLM results are supported. - code: MARGINAL-IMPACT-010 message: You cannot run a marginal impact analysis on this imported HD group because it has no underlying analyses. - code: MARGINAL-IMPACT-011 message: 'You cannot run a marginal analysis on this analysis: %s because it''s not an account-level analysis. Only account-level analyses are supported.' - code: MARGINAL-IMPACT-012 message: We were unable to find the analysis with provided riIds. %s. - domain: MDB count: 4 codes: - code: MDB-001 message: Move operation is not allowed. Source and destination server must be different. - code: MDB-002 message: Database cannot be moved because it is not in Ready state. - code: MDB-003 message: A database with the same name already exists on the destination server. - code: MDB-004 message: Destination server does not have sufficient storage capacity for the database. - domain: METADATA count: 6 codes: - code: METADATA-001 message: 'Error occurred while inserting a record in rdm metadata for analysis id : %d' - code: METADATA-002 message: Sorry, this could be an error on our end. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: METADATA-003 message: 'Database error occurred while deleting records for the analysis id : %d' - code: METADATA-004 message: 'Database error occurred while populating rdm analysis regions hd table for tenant id: %s' - code: METADATA-005 message: 'Database error occurred while reading total count of rdm analysis regions records for tenant id: %s' - code: METADATA-006 message: 'Database error occurred while reading analysis ids for data clean up for tenant id: %s' - domain: MGMT count: 39 codes: - code: MGMT-001 message: 'Request is missing property: %s' - code: MGMT-002 message: Unable to acquire service name - code: MGMT-003 message: Error reading properties file - code: MGMT-004 message: Conflicting operation in-progress - code: MGMT-005 message: Invalid DB Key - code: MGMT-006 message: Can not delete currently active DB server - code: MGMT-007 message: S3 error while copying results schema to tenant loss bucket - code: MGMT-008 message: Tenant not found - code: MGMT-010 message: Failed to retrieve tenant entitlements - code: MGMT-012 message: 'Error reading tenant entitlement for tenant: %s' - code: MGMT-013 message: Failed to retrieve EDMs - code: MGMT-014 message: Failed to lock EDM - code: MGMT-015 message: Failed to unlock EDM - code: MGMT-016 message: Failed to retrieve tenant db migration sub task - code: MGMT-017 message: Failed to retrieve tenant db migration edm status - code: MGMT-018 message: Failed to update tenant db migration sub task - code: MGMT-019 message: Failed to insert tenant db migration sub task - code: MGMT-020 message: Failed to update tenant db migration edm status - code: MGMT-021 message: Failed to insert tenant db migration edm status - code: MGMT-022 message: Failed to update database connection string - code: MGMT-023 message: Failed to get engine input - code: MGMT-024 message: 'Failed to do backup operation on database: %s' - code: MGMT-025 message: 'Failed to do restore operation on database: %s' - code: MGMT-026 message: Failed to retrieve Data Bridge notification status - code: MGMT-027 message: Failed to update Data Bridge notification sub task - code: MGMT-028 message: Failed to insert Data Bridge notification sub task - code: MGMT-029 message: Failed to get Data Bridge notification sub task - code: MGMT-030 message: 'Tenant is missing the required package entitlement for: %s' - code: MGMT-031 message: The provided task id does not belong to this tenant - code: MGMT-032 message: The previous call to delete this tenant did not complete successfully. Please re-run the tenant delete before attempting to re-onboard. - code: MGMT-033 message: There was an error while creating event info database %s - code: MGMT-034 message: There was an error while restoring geohazard database %s to server %s - code: MGMT-035 message: There was an error while creating the geohazard database restore task for id %s - code: MGMT-036 message: Failed to add common bucket IAM role to server %d for tenant %s - code: MGMT-037 message: Failed to upgrade RDS server %s for tenant %s - code: MGMT-038 message: 'Failed to get validation result for DB type: %s, tenantId: %s' - code: MGMT-039 message: 'Validations failed on Tenant DB: %s, tenantId: %s' - code: MGMT-040 message: 'Can not upgrade tenant app : %s for tenantId: %s. Please check if the tenant app onboarded successfully.' - code: MGMT-041 message: Your tenant is missing the required entitlement for %s. Check with your Intelligent Risk Platform administrator to find out which application entitlements are licensed by your organization. - domain: MP count: 3 codes: - code: MP-001 message: Sorry, we could not submit this analysis. To resolve this issue, contact Support at`RMSSupport@moodys.com`. - code: MP-002 message: Sorry, we encountered an error processing the input you provided for running this analysis. Validate the input and try again. Contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: MP-003 message: Sorry, this could be an error on our end. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - domain: PARQUET2RDM count: 8 codes: - code: PARQUET2RDM-001 message: Could not parse URL, reason %s - code: PARQUET2RDM-002 message: 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 - code: PARQUET2RDM-003 message: Database error occurred while acquiring locks on resources - code: PARQUET2RDM-004 message: 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 Support - code: PARQUET2RDM-006 message: 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. - code: PARQUET2RDM-007 message: Sorry, we encountered an error while creating the export RDM job. Try again. If this still doesn't work, contact Support. - code: PARQUET2RDM-008 message: Sorry, cannot retrieve analysis details for analysis ids provided. - code: PARQUET2RDM-009 message: Analysis ids cannot be zero or negative. - domain: PATE count: 38 codes: - code: PATE-001 message: PATE id in URL and body must match - code: PATE-002 message: 'Database error occurred while creating pate with treaty number: %s' - code: PATE-003 message: 'Database error occurred while updating pate with pateId: %d' - code: PATE-004 message: 'Database error occurred while deleting pate with pateId: %d' - code: PATE-005 message: Database error occurred while getting a list of pate treaties - code: PATE-006 message: Database error occurred while deleting a list of pate treaties - code: PATE-007 message: Treaty number %s already exists. Check if new added treaties having a valid (unique) treaty number and an occurrence limit greater than zero. - code: PATE-008 message: 'Database error occurred while retrieving a list of pate lobs with treatyId: %d' - code: PATE-009 message: 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. - code: PATE-010 message: 'Cannot delete Treaty with type: %s' - code: PATE-011 message: 'Invalid Operation type for Treaty id: %d' - code: PATE-013 message: 'Database error occurred while deleting pate treaties in a batch for analysis id: %d' - code: PATE-014 message: We cannot process this job because a job on this result is already running. - code: PATE-015 message: Database error occurred while acquiring lock - code: PATE-016 message: Database error occurred while updating lock metadata - code: PATE-017 message: Attempt to acquire lock failed. Lock has been acquired by a different process. - code: PATE-018 message: We cannot process this job because you have not made any changes. - code: PATE-019 message: 'Database error occurred while checking PATE records for analysis id: %d' - code: PATE-020 message: TenantId was not available from thread context for operations on pate treaties - code: PATE-021 message: A group of PATE treaties cannot be deleted because one of the treaties is marked not for deletion - code: PATE-022 message: Database error occurred while retrieving treaty type - code: PATE-023 message: 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. - code: PATE-024 message: Sorry, looks like the treatyID is missing or invalid. For delete and update properties, treatyID must be greater than zero. - code: PATE-025 message: Sorry, looks like the input for running PATE on an analysis is missing or invalid. Please provide a valid input for the request. - code: PATE-026 message: Sorry, looks like the input for running PATE on an analysis is invalid. For insert property, the treatyID must be zero. - code: PATE-027 message: Use only positive numbers for the hours clause. Negative numbers are not supported. - code: PATE-028 message: Do not include radius clauses for treaties added post analysis. They are not supported. - code: PATE-029 message: 'Treaty type cannot be blank. Enter one of the following treaty types: Catastrophe, Corporate, Stop Loss' - code: PATE-030 message: Sorry, you can not perform PATE on %s engine sub type. - code: PATE-031 message: 'Database error occurred while getting patetreatyid for treatyid: %d.' - code: PATE-032 message: 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. - code: PATE-033 message: 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. - code: PATE-034 message: 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. - code: PATE-035 message: Sorry, you can not perform PATE on %s engine type. - code: PATE-036 message: Sorry, treatyid must be 0 for operation type INSERT. - code: PATE-037 message: Sorry, treatyid must be greater than 0 for operation type UPDATE or DELETE - code: PATE-038 message: Sorry, you can't perform post-analysis treaty editing on these imported HD results. To fix this issue, the original analysis must be re-exported in the current version of the IRP. Then re-import and perform PATE on the newly imported results. - code: PATE-039 message: Sorry, you can't perform post-analysis treaty editing on PLT Group having Climate Change analysis. - domain: PC count: 19 codes: - code: PC-001 message: 'Predefined condition with id: %d was not found.' - code: PC-002 message: 'Criteria with id: %d for predefined condition with id: %d was not found.' - code: PC-003 message: 'The name: %s is already in use. The predefined condition names must be unique.' - code: PC-004 message: predefinedConditionName size must be between 1 and %d. - code: PC-005 message: No updates will be performed, please provide at least one field to update. - code: PC-006 message: Invalid input for condition type. See the Help Center for help with query syntax - code: PC-500 message: 'Database error occurred while checking if predefined condition with id: %d exists. Try again, and contact Support if this still does not work.' - code: PC-501 message: 'Database error occurred while retrieving predefined condition with id: %d. Try again, and contact Support if this still does not work.' - code: PC-502 message: Database error occurred while retrieving predefined conditions. Try again, and contact Support if this still does not work. - code: PC-503 message: Database error occurred while creating predefined condition. Try again, and contact Support if this still does not work. - code: PC-504 message: 'Database error occurred while updating predefined condition with id: %d. Try again, and contact Support if this still does not work.' - code: PC-505 message: 'Database error occurred while deleting predefined condition with id: %d. Try again, and contact Support if this still does not work.' - code: PC-506 message: 'Database error occurred while checking if provided predefined condition name: %s is unique. Try again, and contact Support if this still does not work.' - code: PC-507 message: 'Database error occurred while checking if predefined condition criteria with id: %d exists. Try again, and contact Support if this still does not work.' - code: PC-508 message: 'Database error occurred while retrieving predefined condition criteria with id: %d for predefined condition with id: %d. Try again, and contact Support if this still does not work.' - code: PC-509 message: 'Database error occurred while retrieving predefined condition criteria list for predefined condition with id: %d. Try again, and contact Support if this still does not work.' - code: PC-510 message: 'Database error occurred while creating predefined condition criteria for predefined condition with id: %d. Try again, and contact Support if this still does not work.' - code: PC-511 message: 'Database error occurred while updating predefined condition criteria with id: %d for predefined condition with id: %d. Try again, and contact Support if this still does not work.' - code: PC-512 message: 'Database error occurred while deleting predefined condition criteria with id: %d for predefined condition with id: %d. Try again, and contact Support if this still does not work.' - domain: PLATFORM count: 41 codes: - code: PLATFORM-001 message: Sorry, something might be wrong at our end. We failed to load the currency scheme. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-002 message: Sorry, something might be wrong at our end. We failed to load the event rate scheme. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-003 message: Sorry, something might be wrong at our end. We failed to load the event rates. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-004 message: Sorry, something might be wrong at our end. We failed to load the model profile. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-005 message: Sorry, something might be wrong at our end. We failed to load the output profile. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-006 message: Sorry, something might be wrong at our end. We failed to load the ALM profiles. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-007 message: Sorry, something might be wrong at our end. We failed to load the default ALM profiles. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-008 message: Sorry, something might be wrong at our end. We failed to load the footprint event. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-009 message: Sorry, something might be wrong at our end. We failed to load the currency vintage. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-010 message: Sorry, something might be wrong at our end. We failed to load the default event rate schemes. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-011 message: Sorry, something might be wrong at our end. We failed to load the cost severity scheme. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-012 message: Sorry, something might be wrong at our end. We failed to load the cost severity averages. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-013 message: Sorry, something might be wrong at our end. We failed to load the cost severity CVs. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-014 message: Sorry, something might be wrong at our end. We failed to load the model region hierarchy. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-015 message: Sorry, the currency scheme is invalid. Specify a valid currency and try again. - code: PLATFORM-016 message: Sorry, the model profile is invalid. Specify a valid model profile and try again. - code: PLATFORM-017 message: Sorry, the output profile is invalid. Specify a valid output profile and try again. - code: PLATFORM-018 message: Sorry, the footprint event is invalid. Specify a valid footprint event and try again. - code: PLATFORM-019 message: Sorry, the currency vintage is invalid. Specify a valid currency and try again. - code: PLATFORM-020 message: Sorry, something might be wrong at our end. We failed to find the simulation set. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-021 message: Sorry, something might be wrong at our end. We failed to load the simulation set. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-022 message: Sorry, something might be wrong at our end. We failed to load the event loss adjustment scheme. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-023 message: Sorry, something might be wrong at our end. We failed to load the PET Metadata. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-024 message: Sorry, something might be wrong at our end. We failed to load the Currency Metadata. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-025 message: Sorry, something might be wrong at our end. We failed to load the STEP Tool Event Metadata. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-026 message: Sorry, something might be wrong at our end. We failed to create the STEP Tool Event Metadata. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-027 message: Please provide either destinationExposureId or newExposureName with exposureSetId but not both. - code: PLATFORM-028 message: Please provide destinationExposureId or newExposureName with exposureSetId. - code: PLATFORM-029 message: Sorry, we encountered an error fetching the exposure resource ids. Try again, and contact Support if this still does not work. - code: PLATFORM-030 message: settings.exposureSetId cannot be null or 0. - code: PLATFORM-031 message: settings.exposureSetId must be greater than or equal to 1. - code: PLATFORM-032 message: settings.newExposureName cannot be null or blank. - code: PLATFORM-033 message: settings.newExposureName %s - code: PLATFORM-034 message: Sorry, we encountered an error fetching geographic resolution data. Try again, and contact Support if this still does not work. - code: PLATFORM-035 message: Sorry, we encountered an error fetching climate change scenario metadata. Try again, and contact Support if this still does not work. - code: PLATFORM-036 message: Sorry, the model profile is invalid. %s. Specify a valid model profile and try again. - code: PLATFORM-037 message: No Climate change PET Metadata found for the given Scenario, Time Horizon, Climate Conditioned View and Reference Rate Scheme. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: PLATFORM-038 message: Sorry, the groupSet metadata is not found for this groupSetId %s. Please check the groupSetId and try again. - code: PLATFORM-039 message: Select at least one groupingSetId to run grouping. - code: PLATFORM-040 message: 'The Group Validation Service task with id: %s was not found. Try again, and contact Support if this still does not work.' - code: PLATFORM-041 message: 'Invalid copy request: linkExistingAccounts=true requires settings.filters.exposureResourceType to be PORTFOLIOS.' - domain: POL count: 86 codes: - code: POL-000 message: Sorry, looks like something might be wrong at our end. Try this again, and if it still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: POL-001 message: Policy %d was not found - code: POL-002 message: 'User does not have sufficient permissions on Policy Id: %d' - code: POL-003 message: Policy Effective date must be less than Policy Expiration Date. - code: POL-004 message: Facultative cession layer information is mandatory when reinsurance cession is Facultative - code: POL-005 message: Treaty information is mandatory when reinsurance cession is Treaty - code: POL-006 message: 'Policy Coverage Id: %d for Policy %d was not found' - code: POL-007 message: 'Policy Reinsurance Cession Id: %d for Policy %d was not found' - code: POL-008 message: 'Policy Condition Id: %d for Policy %d was not found' - code: POL-009 message: 'Policy Criteria Id: %d for Policy Condition Id: %d was not found' - code: POL-010 message: 'Condition Id: %d was not found' - code: POL-011 message: 'Parent Account Id: %d was not found for Policy Id: %d' - code: POL-012 message: '%s' - code: POL-013 message: Policy %s is required - code: POL-014 message: '%s may not be null' - code: POL-015 message: Policy currency code should not be null or empty. - code: POL-404 message: '%s' - code: POL-500 message: 'Database error occurred while retrieving Policy Id: %d' - code: POL-501 message: 'Database error occurred while checking if Policy Id: %d exists' - code: POL-502 message: 'Database error occurred while creating policy, reason: %s' - code: POL-503 message: 'Database error occurred while retrieving policy by Link Id: %s' - code: POL-504 message: 'Database error occurred while retrieving policy metrics for Policy Id: %d' - code: POL-505 message: 'Database error occurred while deleting Policy Id: %d' - code: POL-506 message: 'Database error occurred while updating policy, reason: %s' - code: POL-507 message: 'Database error occurred while retrieving countries covered by Policy Id: %d' - code: POL-508 message: 'Database error occurred while copying Policy Id: %d' - code: POL-509 message: Database error occurred while mapping policy id %d with user %d - code: POL-510 message: 'Database error occurred while saving policy details for Policy Id: %d' - code: POL-511 message: Database error occurred while searching policies - code: POL-512 message: 'Database error occurred while checking policy permissions for Policy Id: %d' - code: POL-514 message: 'Database error occurred while retrieving location coordinates covered by Policy Id: %d' - code: POL-515 message: 'Database error occurred while loading parent account information for Policy Id: %d' - code: POL-516 message: 'Database error occurred while loading policy currency information for Policy Id: %d' - code: POL-517 message: 'Database error occurred while performing bulk edit of policies under Account Id: %d' - code: POL-518 message: 'Database error occurred while checking if Policy Coverage Id: %d exists for Policy Id: %d' - code: POL-519 message: 'Database error occurred while retrieving policy coverages for Policy Id: %d' - code: POL-520 message: 'Database error occurred while retrieving Policy Coverage Id: %d' - code: POL-521 message: 'Database error occurred while creating policy coverage for Policy Id: %d' - code: POL-522 message: 'Database error occurred while updating Policy Coverage Id: %d for Policy Id: %d' - code: POL-523 message: 'Database error occurred while deleting Policy Coverage Id: %d' - code: POL-524 message: 'Database error occurred while checking if Policy Reinsurance Cession Id: %d exists for Policy Id: %d' - code: POL-525 message: 'Database error occurred while retrieving policy reinsurance cessions for Policy Id: %d' - code: POL-526 message: 'Database error occurred while retrieving Policy Reinsurance Cession Id: %d for Policy Id: %d' - code: POL-527 message: 'Database error occurred while creating policy reinsurance cession for Policy Id: %d' - code: POL-528 message: 'Database error occurred while updating Policy Reinsurance Id: %d for Policy Id: %d' - code: POL-529 message: 'Database error occurred while deleting Policy Reinsurance Id: %d for Policy Id: %d' - code: POL-530 message: 'Database error occurred while checking if Policy Condition Id: %d exists for Policy Id: %d' - code: POL-531 message: 'Database error occurred while checking if Policy Condition Id: %d exists' - code: POL-532 message: 'Database error occurred while retrieving policy conditions for Policy Id: %d' - code: POL-533 message: 'Database error occurred while retrieving Policy Condition Id: %d' - code: POL-534 message: 'Database error occurred while creating policy condition for Policy Id: %d' - code: POL-535 message: 'Database error occurred while updating Policy Condition Id: %d for Policy Id: %d' - code: POL-536 message: 'Database error occurred while deleting Policy Condition Id: %d' - code: POL-537 message: 'Database error occurred while checking if Policy Condition Criteria Id: %d exists for Condition Id: %d' - code: POL-538 message: 'Database error occurred while retrieving policy condition criterias for Condition Id: %d' - code: POL-539 message: 'Database error occurred while retrieving Policy Condition Criteria Id: %d for Condition Id: %d' - code: POL-540 message: 'Database error occurred while retrieving condition criteria list by Condition Id: %d' - code: POL-541 message: 'Database error occurred while creating policy condition criteria for Condition Id: %d' - code: POL-542 message: 'Database error occurred while updating Policy Condition Criteria Id: %d for Condition Id: %d' - code: POL-543 message: 'Database error occurred while deleting Policy Condition Criteria Id: %d for Condition Id: %d' - code: POL-544 message: 'Database error occurred while getting Policy Condition count for Policy Id: %d for Condition type: %d' - code: POL-545 message: 'Error occurred. Only one Policy Restriction allowed per policy for Policy Id: %d' - code: POL-546 message: 'Database error occurred while checking condition name: %s is unique for Policy Id: %d' - code: POL-547 message: The condition names must be unique within each policy - code: POL-548 message: Condition can't have parent condition which is child of another condition - code: POL-549 message: 'Database error occurred while getting list of Policy Conditions for Account Id: %d' - code: POL-550 message: 'Database error occurred while back filling Policy Conditions for Condition Id: %d' - code: POL-551 message: '%s' - code: POL-554 message: Database error occurred while retrieving Policy Conditions list - code: POL-555 message: 'Database error occurred while retrieving Policy Conditions metrics for Condition Id: %d' - code: POL-556 message: Policy Coverage label may not be empty and label id should be valid - code: POL-557 message: Policy Condition name may not be null or empty - code: POL-558 message: Illegal Policy Condition type id - code: POL-559 message: Condition cannot have an empty parent condition - code: POL-560 message: Duplicate Policy id %s found in input - code: POL-561 message: Policy Condition name exceeds the allowed length - code: POL-562 message: Policy Coverage %s must not be null or empty. - code: POL-563 message: 'Policy condition criteria logic: ''%s'' provided is invalid for Condition Id: %d. It is not allowed for first criteria and must be one of %s for subsequent criteria.' - code: POL-564 message: 'Policy condition criteria provided cannot be parsed due to invalid input for Condition Id: %d. Please check the values provided and try again.' - code: POL-566 message: Duplicate policy condition name %s provided in input. The condition names must be unique within each policy. - code: POL-567 message: Sorry, we cannot process the criteria input values you provided for policy condition %s because they are either too complex or reference a large number of tables. Simplify the input and try again. Contact Support if you need help rewriting the input. - code: POL-568 message: 'Policy condition criteria provided cannot be parsed due to invalid input for Condition Id: %d. The value exceeds the allowed length. Please check the values provided and try again.' - code: POL-569 message: 'Policy condition criteria provided cannot be parsed due to invalid input for Condition Id: %d. The field %s cannot be found. Please check the values provided and try again.' - code: POL-570 message: 'Policy condition criteria provided cannot be parsed due to invalid input for Condition Id: %d. The operator contains the wrong value %s. Please check the values provided and try again.' - code: POL-571 message: '%s %d not found for policy condition %s' - code: POL-572 message: Database error occurred while searching policy conditions - domain: PORT count: 28 codes: - code: PORT-001 message: We could not find portfolio %d in this EDM. - code: PORT-004 message: No geocoded locations exist in portfolio with id %d and number %s. Geocode this portfolio before you run an analysis. - code: PORT-401 message: Select at least one account to add to or remove from the portfolio. - code: PORT-402 message: Sorry, we cannot process the input. Please do not include null values in accountsToAdd and accountsToRemove collections. - code: PORT-404 message: '%s' - code: PORT-405 message: '%s' - code: PORT-500 message: Sorry, we encountered an error retrieving portfolio %d. Try again, and contact Support if this still does not work. - code: PORT-501 message: Sorry, we encountered an error checking if portfolio %d exists. Try again, and contact Support if this still does not work. - code: PORT-502 message: Sorry, we encountered an error creating this portfolio. Try again, and contact Support if this still does not work. - code: PORT-504 message: Sorry, we encountered an error retrieving information about portfolio %d. Try again, and contact Support if this still does not work. - code: PORT-505 message: Sorry, we encountered an error deleting portfolio %d. Try again, and contact Support if this still does not work. - code: PORT-506 message: Sorry, we encountered an error saving the changes for portfolio %d. Try again, and contact Support if this still does not work. - code: PORT-508 message: Sorry, we encountered an error copying portfolio %d. Try again, and contact Support if this still does not work. - code: PORT-511 message: Sorry, we encountered an error searching for portfolios. Try again, and contact Support if this still does not work. - code: PORT-512 message: 'Database error occurred while fetching number of exposures for exposure type: PORTFOLIO.' - code: PORT-514 message: Sorry, we encountered an error retrieving geocoding information for one or more locations in portfolio %d. Try again, and contact Support if this still does not work. - code: PORT-515 message: Sorry, we encountered an error retrieving total number of accounts in portfolio %d. Try again, and contact Support if this still does not work. - code: PORT-534 message: 'Geocode Portfolio failed for Portfolio Id: %d.' - code: PORT-539 message: 'Database error occurred while managing accounts to Portfolio Id: %d' - code: PORT-540 message: 'You cannot add and remove the same account for portfolio: %d.' - code: PORT-541 message: Sorry, we encountered an error searching accounts for portfolio %d. Try again, and contact Support if this still does not work. - code: PORT-542 message: 'Sorry, we encountered an error converting currencies for portfolio with Id: %d. Try again, and contact Support if this still does not work.' - code: PORT-543 message: More than one location in portfolio %d has latitude %f and longitude %f. Two locations in a portfolio cannot have the same coordinates. - code: PORT-544 message: No locations in portfolio %d have latitude %f and longitude %f. Check the coordinates or regeocode the portfolio. - code: PORT-548 message: You cannot analyze a portfolio with more than %d accounts if the output profile specifies loss table output at the contract granularity. - code: PORT-549 message: Duplicate Portfolio id %s found in input. - code: PORT-550 message: Validation failed. Accounts count to add/remove to/from portfolio exceeds the limit %d. - code: PORT-551 message: '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 Support if this still does not work.' - domain: PRO count: 3 codes: - code: PRO-001 message: 'Invalid value: %s, passed for category parameter' - code: PRO-500 message: Database Error occurred while retrieving model profiles - code: PRO-501 message: 'Error occurred while retrieving service information for driver: %s' - domain: PRODUCER count: 11 codes: - code: PRODUCER-401 message: Database error occurred, producer does not exists - code: PRODUCER-404 message: '%s' - code: PRODUCER-406 message: '%s' - code: PRODUCER-409 message: '%s' - code: PRODUCER-501 message: 'Database error occurred while loading producers, reason : %s' - code: PRODUCER-502 message: 'Database error occurred while creating producer, reason : %s' - code: PRODUCER-503 message: 'Database error occurred while updating producer with Id: %s, reason : %s' - code: PRODUCER-504 message: 'Database error occurred while deleting producer with Id: %s, reason : %s' - code: PRODUCER-505 message: Database error occurred duplicate producer, producer already exists - code: PRODUCER-506 message: Validation error, producer id cannot be null or empty. - code: PRODUCER-508 message: Validation error, producer, some of the String field has exceeded allowed length. - domain: REINS_CESSION count: 4 codes: - code: REINS_CESSION-001 message: Layer Number should be between 1 and 99 - code: REINS_CESSION-002 message: Priority should be between 1 and 127 - code: REINS_CESSION-003 message: Treaty id must be greater than zero when reinsurance cession type provided is %s - code: REINS_CESSION-004 message: FacReinsurer id must not be null or blank when reinsurance cession type provided is %s - domain: RENAME count: 6 codes: - code: RENAME-001 message: Attempt to acquire lock failed. Lock has been acquired by a different process. - code: RENAME-002 message: We cannot process this job because a job on this result is already running. - code: RENAME-003 message: Sorry, we encountered an error while running rename-analysis. Try again, and contact Support at`RMSSupport@moodys.com`if this still does not work. - code: RENAME-004 message: Invalid argument for %s - code: RENAME-005 message: Sorry, the new analysis name format is invalid - code: RENAME-006 message: You are not authorized to perform this rename operation on the accumulation analysis. This may be due to an expired token, invalid credentials, or insufficient permissions. Verify your authorization and try again, or contact your administrator. - domain: REPORT count: 27 codes: - code: REPORT-001 message: Sorry, we encountered an error searching for reports. Try again, and contact Support if this still does not work. - code: REPORT-002 message: Sorry, we encountered an error creating this report. Try again, and contact Support if this still does not work. - code: REPORT-003 message: Sorry, the exposure type %s is not valid for search reports. Valid exposure types are 'ACCOUNT' and 'PORTFOLIO'. - code: REPORT-004 message: Sorry, we encountered an error while processing the data submitted for the reports. Try again, and contact Support if this still does not work. - code: REPORT-005 message: 'Sorry, we can''t find Report id: %s for EDM: %s. Either it doesn''t exist or you don''t have access to it.' - code: REPORT-006 message: Sorry, we encountered an error while updating the report information. Try again, and contact Support if this still does not work. - code: REPORT-007 message: 'Sorry, we can''t find Report id: %s. Either it doesn''t exist or you don''t have access to it.' - code: REPORT-008 message: 'We did not locate the database for report Id: %d. Either it doesn''t exist or you don''t have access to it.' - code: REPORT-009 message: 'Sorry, we encountered an error while parsing the report details for report url: %s.' - code: REPORT-010 message: Duplicate metric found in the input %s. - code: REPORT-011 message: Invalid resource type provided. - code: REPORT-012 message: 'Invalid resource uri provided: %s.' - code: REPORT-013 message: Invalid report type provided. - code: REPORT-014 message: Invalid data type %s provided. - code: REPORT-015 message: 'This application is not supported: %s.' - code: REPORT-016 message: Sorry, we encountered an error while processing this portfolio accumulation report. Try again, and contact Support if this still does not work. - code: REPORT-017 message: The request input is invalid. Please provide a valid input and try again. - code: REPORT-018 message: Sorry, we encountered an error while getting the analysis details. Try again, and contact Support if this still does not work. - code: REPORT-019 message: Sorry, we can't find analysis. Either it doesn't exist or you don't have access to it. - code: REPORT-020 message: Sorry, we encountered an error while processing the data submitted for the business hierarchy report. Try again, and contact Support if this still does not work. - code: REPORT-021 message: Sorry, we encountered an error while generating the report. Try again, and contact Support if this still does not work. - code: REPORT-022 message: Sorry, we encountered an error while deleting the report. Try again, and contact Support if this still does not work. - code: REPORT-023 message: Sorry, we encountered an error while submitting the report download. Try again, and contact Support if this still does not work. - code: REPORT-024 message: Invalid resource type provided. Expected %s, but found %s. - code: REPORT-025 message: 'Invalid resource type. Valid resource types are accountVariation and portfolioVariation. Resource type given: %s' - code: REPORT-026 message: Events data type cannot be combined with Geographies or Policies in multi-event accumulation analysis. - code: REPORT-027 message: Events data type is not supported for single-event accumulation analysis. - domain: REPORT-DOWNLOAD count: 1 codes: - code: REPORT-DOWNLOAD-001 message: Failure occurred while exporting %s dashboard data - domain: RERUN-EP count: 7 codes: - code: RERUN-EP-001 message: Invalid argument for %s - code: RERUN-EP-002 message: Unable to retrieve metadata for %s - code: RERUN-EP-003 message: Sorry, you can recalculate EP metrics on %s engine type(s) only. Enter a non-HD or non-simulated DLM or non-CEP analysis ID - code: RERUN-EP-004 message: Unsupported analysis type. Rerun Ep is only supported on %s analysis type(s) - code: RERUN-EP-005 message: Sorry, we encountered an error while submitting the rerun Ep job. Try again, and contact Support if this still does not work. - code: RERUN-EP-006 message: Sorry, you can not perform Rerun Ep on %s engine sub type. - code: RERUN-EP-007 message: Unsupported exposure type. Rerun Ep is not supported for account analyses. - domain: RETENTION count: 3 codes: - code: RETENTION-501 message: '"Database error occurred while creating data retention"' - code: RETENTION-502 message: '"Database error occurred while retrieving expired data retentions"' - code: RETENTION-503 message: '"Database error occurred while archiving data retention"' - domain: RG count: 7 codes: - code: RG-001 message: Sorry, this could be an error on our end. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: RG-002 message: 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. - code: RG-003 message: The resource group id %s is invalid. Please check and try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: RG-004 message: The resource group id not provided in request header. Please check and try again. - code: RG-005 message: The provided resource group id %s cannot be used with this API. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: RG-006 message: Sorry, you cannot perform this operation because you don't have access to job resource group. - code: RG-007 message: The provided resource group does not have assigned resources to be used for this request. - domain: S2S count: 1 codes: - code: S2S-001 message: Missing S2S token - domain: SEED count: 1 codes: - code: SEED-501 message: Database error occurred while loading seeds. - domain: SERVER_INFO count: 9 codes: - code: SERVER_INFO-500 message: Failed to find the requested server info - code: SERVER_INFO-501 message: Failed to insert new server info record - code: SERVER_INFO-502 message: Failed to update server info record - code: SERVER_INFO-503 message: Failed to find server info records for tenant - code: SERVER_INFO-504 message: Failed to find server info records for tenant namespace %s - code: SERVER_INFO-505 message: Failed to delete server info record - code: SERVER_INFO-506 message: The server name %s that you provided doesn't match an existing server name. Check the server name for misspellings and try again. - code: SERVER_INFO-507 message: Invalid Operator or expression in condition %s. Please check the query and try again. - code: SERVER_INFO-508 message: The server id %d that you provided doesn't match an existing server id. Check the server id and try again. - domain: SETUP count: 2 codes: - code: SETUP-500 message: Failed to read from setup jobs table. - code: SETUP-501 message: Failed to insert data into setup jobs table. - domain: SIMULATE-LOSSES count: 12 codes: - code: SIMULATE-LOSSES-001 message: We encountered an error retrieving the simulation set with id %d. Try again. If this still doesn't work, contact Support. - code: SIMULATE-LOSSES-002 message: Sorry, we encountered an error while simulating ELT to PLT for this analysis. Try again, and contact Support if this still does not work. - code: SIMULATE-LOSSES-003 message: 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. - code: SIMULATE-LOSSES-004 message: You cannot simulate these results from ELT- to PLT-based results because these results have already been simulated to a PLT. - code: SIMULATE-LOSSES-005 message: Enter a valid value greater than zero for the event rate scheme id field. - code: SIMULATE-LOSSES-006 message: Enter a valid value greater than zero for the simulation set id field. - code: SIMULATE-LOSSES-007 message: Enter a valid value greater than zero for the simulation periods field. - code: SIMULATE-LOSSES-008 message: 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. - code: SIMULATE-LOSSES-009 message: Unsupported regionPerilSettings field present in the request. - code: SIMULATE-LOSSES-010 message: Unsupported request, if regionPerilSettings is populated then other fields must not be passed in the request. - code: SIMULATE-LOSSES-011 message: Enter a valid value for modelRegionCode. - code: SIMULATE-LOSSES-012 message: Provided regionPerilSettings is not matching the ELT analysis. - domain: SMART count: 5 codes: - code: SMART-001 message: Sorry, we encountered an error while executing the Smart Selection Service. Try again, and contact Support if this still does not work. - code: SMART-002 message: Sorry, we encountered an error while retrieving the Smart Selection Service status. Try again, and contact Support if this still does not work. - code: SMART-003 message: Sorry, we encountered an error while executing the Smart Selection Service. Try again, and contact Support if this still does not work. - code: SMART-004 message: 'The Smart Selection Service task with id: %s was not found. Try again, and contact Support if this still does not work.' - code: SMART-005 message: The number of model profiles to be used for auto-select exceeds the %d limit. Please delete model profiles from your tenant before attempting the call again. - domain: SMTP count: 3 codes: - code: SMTP-500 message: SMTP host was not found - code: SMTP-501 message: SMTP port was not found - code: SMTP-502 message: Invalid SMTP credentials - domain: SNAP count: 11 codes: - code: SNAP-001 message: Sorry, we encountered an error getting the list of snapshot databases. Try again, and contact Support if this still does not work. - code: SNAP-002 message: Snapshot with id %d and database id %d not found. - code: SNAP-003 message: Snapshot with id %d and database id(s) %s not found. - code: SNAP-004 message: Snapshot with id %d and database id %s contains invalid server type. - code: SNAP-005 message: Failed to submit copy to archive job. Try again, and contact Support if this still does not work. - code: SNAP-006 message: Snapshot with id %d and database id(s) %s got expired. - code: SNAP-007 message: Snapshot with id %d not found. - code: SNAP-008 message: Sorry, databaseSnapshotIds should not be provided when copyAllDatabaseSnapshots is true. Please provide either list with databaseSnapshotIds or set copyAllDatabaseSnapshots as true. - code: SNAP-009 message: Please provide either list with databaseSnapshotIds or set copyAllDatabaseSnapshots as true. - code: SNAP-010 message: Sorry, the expiration date should not be before the current date. - code: SNAP-011 message: Sorry, there are no databases associated with the given snapshotId %d. - domain: STEPPOL count: 19 codes: - code: STEPPOL-000 message: Sorry, looks like something might be wrong at our end. Try this again, and if it still doesn't work, contact Support at `RMSSupport@moodys.com`. - code: STEPPOL-001 message: Step Policy Effective date must be less than Step Policy Expiration Date. - code: STEPPOL-002 message: Step Policy %d was not found - code: STEPPOL-003 message: 'Parent Account Id: %d was not found for Step Policy Id: %d' - code: STEPPOL-004 message: 'User does not have sufficient permissions on Step Policy Id: %d' - code: STEPPOL-404 message: '%s' - code: STEPPOL-406 message: '%s' - code: STEPPOL-409 message: '%s' - code: STEPPOL-500 message: 'Database error occurred while updating Step Policy Id: %d' - code: STEPPOL-501 message: Database error occurred while creating Step Policy - code: STEPPOL-502 message: 'Database error occurred while retrieving Step Policy Id: %d' - code: STEPPOL-503 message: 'Database error occurred while loading parent account information for Step Policy Id: %d' - code: STEPPOL-504 message: 'Database error occurred while deleting Step Policy Id: %d' - code: STEPPOL-505 message: Database error occurred while searching policies - code: STEPPOL-506 message: 'Database error occurred while copying Step Policy Id: %d' - code: STEPPOL-507 message: Step order id %d received for creation already exists - code: STEPPOL-508 message: Maximum step order id %s exceeded - code: STEPPOL-509 message: Duplicate Step policy id %s found in input - code: STEPPOL-510 message: 'Error occurred while validating StepPolicy: %s' - domain: STEP-TOOL count: 7 codes: - code: STEP-TOOL-001 message: Invalid argument for %s - code: STEP-TOOL-002 message: Must include at least one analysis. - code: STEP-TOOL-003 message: Sorry, we encountered an error while submitting the Step-Tool job. Try again, and contact Support if this still does not work. - code: STEP-TOOL-004 message: Unsupported analyses %s. Only DLM Portfolio EP, DLM Portfolio EP Groups, and ALM are supported - code: STEP-TOOL-005 message: An error occurred while loading STEP Tool events. - code: STEP-TOOL-006 message: Must have more than 1 analysis to group result. - code: STEP-TOOL-007 message: Invalid eventid weights input. - domain: TENANT count: 22 codes: - code: TENANT-001 message: Could not parse URL, reason %s - code: TENANT-002 message: Tenant file was not found - code: TENANT-003 message: Tenant file cannot be read - code: TENANT-004 message: Tenant id in the request does not match with the token details - code: TENANT-005 message: Database error occurred while retrieving RDM names - code: TENANT-006 message: The key %s does not have correct db properties format - code: TENANT-007 message: The key %s already exists in the database - code: TENANT-008 message: The property(s) are missing the primary key - code: TENANT-009 message: The EDM db already exists - code: TENANT-011 message: Invalid EDM database type - code: TENANT-012 message: Database error occurred while adding edm db properties - code: TENANT-013 message: The tenant edm keys do not match - code: TENANT-014 message: The sql server db should have this format %s - code: TENANT-015 message: Database error occurred while retrieving tenant database information for tenant id %s - code: TENANT-016 message: Database credentials cannot be null or empty - code: TENANT-017 message: Given destination database credentials are invalid. Could not connect to the database. - code: TENANT-018 message: Given source database credentials do not match with system's database credentials - code: TENANT-019 message: Source and destination database servers cannot be same - code: TENANT-020 message: 'This feature is not enabled for your organization: %s. Contact your RMS Account Manager about enabling this.' - code: TENANT-021 message: This feature is not supported for tenants with UDS support enabled. - code: TENANT-022 message: RDS server %s already exists - code: TENANT-023 message: DB server migration allowed only between RDS server - domain: TREATY count: 80 codes: - code: TREATY-001 message: 'Treaty with Id: %d was not found' - code: TREATY-002 message: 'Treaty with Id: %d and Line of business with Id:%d was not found' - code: TREATY-401 message: Treaty Effective date cannot be null or empty - code: TREATY-402 message: Treaty Expire date cannot be null or empty - code: TREATY-403 message: 'Invalid treaty effective date format. Expected: yyyy-MM-ddTHH:mm:ssZ' - code: TREATY-404 message: 'Invalid treaty expire date format. Expected: yyyy-MM-ddTHH:mm:ssZ' - code: TREATY-405 message: Treaty expiry date cannot be before effective date - code: TREATY-406 message: An hours clause is required before you add a radius clause - code: TREATY-407 message: '%s' - code: TREATY-408 message: '%s' - code: TREATY-409 message: '%s' - code: TREATY-410 message: Some of the selected treaties are not applicable to the given exposure. Please select applicable treaties and try again. - code: TREATY-411 message: Aggregate Limit and Aggregate Deductible are not applicable for non-portfolio treaties. - code: TREATY-412 message: '%s' - code: TREATY-500 message: Database error occurred while checking loading treaties for Exposure type:%s and Treaty type:%s - code: TREATY-501 message: 'Database error occurred while loading treaty with treatyId: %d' - code: TREATY-502 message: Database error occurred while checking loading policy level treaties for Account Id:%d and Policy Id:%d - code: TREATY-503 message: Database error occurred while checking loading location level treaties for Account Id:%d - code: TREATY-504 message: 'Database error occurred while creating new treaty with name: %s' - code: TREATY-505 message: 'Database error occurred while updating treaty with treatyId: %d' - code: TREATY-506 message: 'Database error occurred while deleting treaty with treatyId: %d' - code: TREATY-507 message: Database error occurred while searching treaties with optional filters - code: TREATY-508 message: 'Database error occurred while saving treaty lob with Treaty Id: %d' - code: TREATY-509 message: 'Database error occurred while deleting treaty lob with Treaty Id: %d' - code: TREATY-510 message: 'Database error occurred while get treaty lob with Treaty Id: %d' - code: TREATY-511 message: 'Database error occurred while checking if Treaty Id: %d exists' - code: TREATY-512 message: 'Database error occurred while checking if Treaty Id: %d and Line of business with Id: %d exists' - code: TREATY-513 message: 'Treaty with Id: %d and Line of business with Id:%d already exists' - code: TREATY-514 message: Database error occurred duplicate Treaty, Treaty already exists - code: TREATY-515 message: 'Database error occurred while creating Treaty with Number: %s, reason : Cedant with Id: %s was not found' - code: TREATY-516 message: 'Database error occurred while creating Treaty with Number: %s, reason : Producer with Id: %s was not found' - code: TREATY-517 message: 'Sorry, we encountered an error converting currencies for treaty with Id: %d. Try again, and contact Support if this still does not work.' - code: TREATY-518 message: Invalid Treaty Number - code: TREATY-519 message: Covered Percentage must be between 0 and 100 - code: TREATY-520 message: Placed Percentage must be between 0 and 100 - code: TREATY-521 message: Share Percentage must be between 0 and 100 - code: TREATY-522 message: Retention Percentage must be between 0 and 100 - code: TREATY-523 message: Reinstatement Charge Percentage must be between 0 and 1000 - code: TREATY-524 message: Per Risk Limit must be a positive number - code: TREATY-525 message: Occurrence Limit must be a positive number - code: TREATY-526 message: Attachment Point must be a positive number - code: TREATY-527 message: Premium must be a positive number - code: TREATY-528 message: Number of Reinstatements must be between 0 and 99 - code: TREATY-529 message: Invalid Treaty Type - code: TREATY-530 message: Inuring Priority must be between 1 and 127 - code: TREATY-531 message: Invalid Attachment Basis - code: TREATY-532 message: Invalid Exposure Level - code: TREATY-533 message: Invalid Exposure Level for Quota Share treaty type - code: TREATY-534 message: Invalid Exposure Level for Working Excess treaty type - code: TREATY-535 message: Invalid Exposure Level for Surplus Share treaty type - code: TREATY-536 message: Invalid Treaty Name - code: TREATY-537 message: Database error occurred while getting all treaty lobs - code: TREATY-538 message: Occurrence Limit must be greater than zero - code: TREATY-539 message: '%s' - code: TREATY-540 message: Error occurred while inserting a rdm treaty mapping data for id %d - code: TREATY-541 message: Error occurred while fetching the edm treaty id mapping data for id %d - code: TREATY-542 message: Database error occurred while loading next Treaty Id - code: TREATY-543 message: 'Database error occurred while checking if Treaty Number: %s exists' - code: TREATY-544 message: 'Database error occurred while checking if Treaty with Id: %d and Number: %s exists' - code: TREATY-545 message: 'Error occurred because the cat treaty: %d does not exist' - code: TREATY-546 message: Aggregate Deductible must be greater than or equal to zero - code: TREATY-547 message: Aggregate Limit must be greater than or equal to zero - code: TREATY-548 message: 'Sorry, we encountered an error copying treaty with treatyId: %d. Try again, and contact Support if this still does not work.' - code: TREATY-549 message: 'Sorry, we encountered an error getting list of loss occurrences for treatyId: %d. Try again, and contact Support if this still does not work.' - code: TREATY-550 message: 'Sorry, we encountered an error getting loss occurrence with Id: %d for treaty with treatyId: %d. Try again, and contact Support if this still does not work.' - code: TREATY-551 message: 'Sorry, we encountered an error inserting loss occurrence for treatyId: %d. Try again, and contact Support if this still does not work.' - code: TREATY-552 message: 'Sorry, we encountered an error updating loss occurrence with Id: %d for treaty with treatyId: %d. Try again, and contact Support if this still does not work.' - code: TREATY-553 message: 'Sorry, we encountered an error deleting loss occurrence with Id: %d. Try again, and contact Support if this still does not work.' - code: TREATY-554 message: Sorry, we encountered an error getting treaties for analysis. Try again, and contact Support if this still does not work. - code: TREATY-555 message: Inuring Priority must be 1 or 2 - code: TREATY-556 message: 'Sorry, we encountered an error getting treaties for aggregate portfolio id: %d. Try again, and contact Support if this still does not work.' - code: TREATY-557 message: 'Database error occurred while checking if treaties are present for analysis Id(s): %s' - code: TREATY-558 message: 'Sorry, we encountered a database error while inserting the LOB(s) of treaties for treaty Id: %d' - code: TREATY-559 message: 'Sorry, we encountered a database error while fetching the LOB(s) for treaty Id: %d' - code: TREATY-560 message: 'Database error occurred while fetching number of exposures for exposure type: TREATY.' - code: TREATY-561 message: Treaty currency code cannot be null or empty. - code: TREATY-562 message: Duplicate treaty number found in input. - code: TREATY-563 message: Duplicate Treaty id %s found in input. - code: TREATY-564 message: Treaty Number %s already exists for treaty id %s. - code: TREATY-565 message: '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 Support if this still does not work.' - domain: UNDERWRITER count: 11 codes: - code: UNDERWRITER-401 message: Database error occurred, underwriter does not exist - code: UNDERWRITER-402 message: 'Database error occurred while loading underwriters, reason : %s' - code: UNDERWRITER-404 message: '%s' - code: UNDERWRITER-406 message: '%s' - code: UNDERWRITER-409 message: '%s' - code: UNDERWRITER-502 message: 'Database error occurred while creating underwriter, reason : %s' - code: UNDERWRITER-503 message: 'Database error occurred while updating underwriter with Id: %d, reason : %s' - code: UNDERWRITER-504 message: 'Database error occurred while deleting underwriter with Id: %d, reason : %s' - code: UNDERWRITER-505 message: Database error occurred duplicate underwriter, underwriter already exists - code: UNDERWRITER-508 message: Validation error, underwriter, the name field has exceeded allowed length. - code: UNDERWRITER-509 message: 'Database error occurred while checking if underwriter exists : reason %s' - domain: UNIFIED-DATA-STORE count: 9 codes: - code: UNIFIED-DATA-STORE-001 message: 'Database error occurred: %s' - code: UNIFIED-DATA-STORE-002 message: Failed to create database. %s. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: UNIFIED-DATA-STORE-003 message: Failed to restore database. %s - code: UNIFIED-DATA-STORE-004 message: Failed to delete database. %s. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: UNIFIED-DATA-STORE-005 message: Failed to attach database. %s - code: UNIFIED-DATA-STORE-006 message: Failed to backup database. %s. Try again, and contact Support at`RMSSupport@moodys.com`if this still doesn't work. - code: UNIFIED-DATA-STORE-007 message: Failed to restore archive. %s. Try again, and contact Support at support@rms.com if this still doesn't work. - code: UNIFIED-DATA-STORE-008 message: Failed to delete archive. %s. Try again, and contact Support at support@rms.com if this still doesn't work. - code: UNIFIED-DATA-STORE-009 message: Failed to update archive. %s. Try again, and contact Support at support@rms.com if this still doesn't work. - domain: UPLOAD count: 7 codes: - code: UPLOAD-001 message: Could not parse URL, reason %s - code: UPLOAD-002 message: 'ImportSource could not be found upload Id: %s' - code: UPLOAD-003 message: Data source name already exists - code: UPLOAD-004 message: MDF File upload operation not permitted on RDS DB Store - code: UPLOAD-005 message: Upload id %s is not valid. It should be in UUID format. - code: UPLOAD-006 message: Server name can't be empty for import rdm from DB server - code: UPLOAD-007 message: Invalid server name %s for import rdm from DB server. - domain: UTIL count: 2 codes: - code: UTIL-501 message: An error occurred while writing the object as json - code: UTIL-502 message: An error occurred converting the object - domain: VER count: 1 codes: - code: VER-001 message: 'Database error occurred while retrieving version, reason : %s' - domain: WORKFLOW count: 37 codes: - code: WORKFLOW-400 message: The workflow you are trying to submit cannot be executed because it requires more concurrency quota than your entitlement has. Please try reducing the number of jobs in the workflow and submit it again. - code: WORKFLOW-401 message: The workflow DAG should define at least one operation - code: WORKFLOW-402 message: The workflow DAG should have no-cycles - code: WORKFLOW-403 message: Each label in the workflow should be unique identifying single operation - code: WORKFLOW-404 message: Invalid batch API input - code: WORKFLOW-405 message: Failed to trigger batch API job - code: WORKFLOW-406 message: This workflow uses an invalid dependency labels %s. Check that all the 'dependsOn' statements refer to valid labels - code: WORKFLOW-407 message: This workflow uses an invalid operation. Check that all operations has an %s field - code: WORKFLOW-408 message: This workflow uses an invalid operation %s. Valid operations are geohaz, process, group or a valid Risk Modeler API URL - code: WORKFLOW-409 message: 'Operation %s contains invalid id: %s. Id must be greater than or equal to 1.' - code: WORKFLOW-410 message: 'Operation with label: %s contains invalid reference workflow labels' - code: WORKFLOW-501 message: 'Workflow service returned an error while submitting Workflow Id: %s, reason : %s' - code: WORKFLOW-502 message: 'Workflow service returned an error while submitting workflow: %s' - code: WORKFLOW-503 message: 'Failed to get status for Workflow Id: %s' - code: WORKFLOW-504 message: 'Failed to get detail for Workflow Id: %s' - code: WORKFLOW-505 message: 'Failed to save result for Workflow Id: %s' - code: WORKFLOW-506 message: 'Failed to cancel Workflow Id: %s' - code: WORKFLOW-507 message: Failed to get list of workflows - code: WORKFLOW-508 message: 'Invalid date format: %s' - code: WORKFLOW-509 message: 'Invalid status parameter: %s' - code: WORKFLOW-510 message: 'Invalid workflow type parameter: %s' - code: WORKFLOW-511 message: 'Invalid workflow id: %s' - code: WORKFLOW-512 message: 'Invalid sort attributes: %s' - code: WORKFLOW-513 message: Invalid date, from date cannot be greater than to date - code: WORKFLOW-514 message: 'Failed to get the list of users: %s' - code: WORKFLOW-515 message: Status for workflow id %s is %s. You cannot cancel a job with this status. - code: WORKFLOW-516 message: Failed to get tenant queues - code: WORKFLOW-517 message: Failed to create tenant queue - code: WORKFLOW-518 message: Sorry, we encountered an error trying to get the workflow. Try again, and contact Support if this still does not work. - code: WORKFLOW-519 message: Sorry, we encountered an error trying to get the job. Try again, and contact Support if this still does not work. - code: WORKFLOW-520 message: 'No workflow exists for client id: %s' - code: WORKFLOW-521 message: 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". - code: WORKFLOW-522 message: Failed to upload %s body to S3. - code: WORKFLOW-523 message: 'Failed to get job input from S3: %s' - code: WORKFLOW-524 message: 'Failed to create clean up task: %s' - code: WORKFLOW-525 message: 'Invalid entitlement parameter: %s' - code: WORKFLOW-526 message: Error occurred while generating secure download link. Try again, and contact Support if this still does not work. - domain: WORKERSCOMP count: 2 codes: - code: WORKERSCOMP-401 message: Database error occurred, injury cost scheme does not exists - code: WORKERSCOMP-502 message: 'Database error occurred while saving injury cost scheme for database with Id: %d'