UI Translation

Power BI

  1. The RelatedEnd cannot be returned by this RelationshipManager. A RelatedEnd can only be returned by a RelationshipManager ...
  2. The RelatedEnd with role name '{0}' from relationship '{1}' has already been loaded. This can occur when using a NoTracking ...
  3. The relationship '%{strNewRelationship/}' cannot be created since relationship '%{strExistingRelationship/}' already exists ...
  4. The relationship '%{strNewRelationship/}' cannot be created since relationship '%{strExistingRelationship/}' already exists ...
  5. The relationship '{0}' does not contain the role '{1}'. Make sure that EdmRelationshipAttribute that defines this relationship ...
  6. The relationship being added conflicts with an existing relationship. Consider deleting the previous relationship and calling ...
  7. The relationship between column '%{fromTable/}'['%{fromColumn/}' and column '%{toTable/}'['%{toColumn/}' cannot have SecurityFilterBehavior ...
  8. The relationship between column '%{fromTable/}'['%{fromColumn/}' and column '%{toTable/}'['%{toColumn/}' cannot have SecurityFilterBehavior ...
  9. The relationship between the table in Excel and the table in the PowerPivot window was lost. It might have been lost either ...
  10. The relationship cannot be created because each column contains duplicate values. Select at least one column that contains ...
  11. The relationship cannot be created in the requested direction. When you click create, the direction of the relationship will ...
  12. The relationship cannot be defined because the EntitySet name '{0}.{1}' is not valid for the role '{2}' in association set ...
  13. The relationship manager supplied by the object implementing IEntityWithRelationships is not the expected relationship manager. ...
  14. The relationship manager was defined with an owner of type '{0}', which is not compatible with the type '{1}' for the source ...
  15. The relationship you're activating lets you filter {0} by {1}, but Excel {2} allows only one filtering path between tables ...
  16. The relationship you're creating lets you filter {0} by {1}, but Excel {2} allows only one filtering path between tables ...
  17. The relationship you're creating lets you filter {0} by {1}, but Excel {2} allows only one filtering path between tables ...
  18. The relationship you're creating lets you filter {0} by {1}, but {2} allows only one filtering path between tables in a Data ...
  19. The relationship you're creating lets you filter {0} by {1}, but {2} allows only one filtering path between tables in a Data ...
  20. The report '{0}' cannot be opened because no data source is associated with it. Associate a model data source with this report ...
  21. The report '{0}' cannot be opened because the data source '{1}' associated with it is not a report model. This report was ...
  22. The report '{0}' cannot be opened because you do not have permission to access the data source: '{0}'. Contact your administrator. ...
  23. The report cannot be rendered. A filter is required to prevent too much data from being returned. Add a filter to your report. ...
  24. The Report Definition Customization Extension (RDCE) name that is specified in the report does not match the RDCE name that ...
  25. The Report Definition Customization Extension (RDCE) returned a different RDL version than it was originally passed. The ...
  26. The Report Definition Customization Extension (RDCE) returned a null or invalid RDL. Make sure that the RDL contains valid ...
  27. The report query processor stopped the query to free system resources. Run the query again to see more rows in the result ...
  28. The report server at {0}' is not compatible with this version of Report Builder. Specify a URL to a SQL Server 2008 R2 report ...
  29. The report server cannot access the private key for the service account. This key is used to decrypt the symmetric key that ...
  30. The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server ...
  31. The report server cannot load the model for report '{0}' because it references no data source or references more than one ...
  32. The report server cannot open a connection to the report server database. A connection to the database is required for all ...
  33. The report server cannot process the report or shared dataset. The shared data source '{0}' for the report server or SharePoint ...
  34. The report server configuration file specifies localhost for the Web server name. The report server requires that the computer ...
  35. The report server could not transmit the file because the file {0} is not installed or you do not have the correct permissions ...
  36. The Report Server Web Service is unable to access secure information in the report server. Please verify that the WebServiceAccount ...
  37. The report snapshot '{1}' cannot be found for report '{0}'. The snapshot identifier cannot be located in the report server ...
  38. The report was saved successfully but could not be bound to the data source. Try saving the report to the same site or server ...
  39. The request to Analysis Services contains a rowset. For security reasons, rowsets are not permitted when the connection is ...
  40. The requested operation could not be completed because the object implementing IEntityWithRelationships returned a null value ...
  41. The requested operation could not be completed, because a mismatched EntityKey was returned from the EntityKey property on ...
  42. The requested protection level does not match the required data protection level of the instance for administrative operations. ...
  43. The required entry '{0}' was not found in the provided input. This entry is required by the key fields defined on type '{1}'. ...
  44. The required IACCEPTMSODBCSQLLICENSETERMS=YES command-line parameter is missing. By specifying this parameter, you acknowledge ...
  45. The required IACCEPTMSSQLCMDLNUTILSLICENSETERMS=YES command-line parameter is missing. By specifying this parameter, you ...
  46. The required IACCEPTSQLLOCALDBLICENSETERMS=YES command-line parameter is missing. By specifying this parameter, you acknowledge ...
  47. The required IACCEPTSQLNCLILICENSETERMS=YES command-line parameter is missing. By specifying this parameter, you acknowledge ...
  48. The restriction Catalog property value '%{strCatalog/}' does not match either internal database '%{strScopedInternalDb/}' ...
  49. The result of the query contains an axis with too many columns. This usually occurs because there are too many hierarchies ...
  50. The result of this query is too large to be loaded to the specified location on the worksheet. Worksheets have a limit of ...
  51. The result type '{0}' specified in the declaration of the function '{1}' does not match the result type '{2}' of the function ...
  52. The result type of the query is neither an EntityType nor a CollectionType with an entity element type. An Include path can ...
  53. The result, '%{resultid/}', cannot be found for this session. Either the result has not been created by the KeepResult header, ...
  54. The results of the current statement cannot be stored on the server because the associated session is either unspecified ...
  55. The results of the current statement cannot be stored on the server because the current session already has a stored result. ...
  56. The ResultType of the query view expression specified for the EntitySet '{0}' is not assignable to the element type of the ...
  57. The ResultType of the specified expression is not compatible with the required type. The expression ResultType is '{0}' but ...
  58. The ring index n ({0}) passed to STInteriorRingN is less than 1. The number must be greater than or equal to 1 and should ...
  59. The ROLAP database cannot create an index on the view for the '%{schema/}' schema, '%{table/}' table. Verify that the requirements ...
  60. The role assignment on the root folder cannot be deleted. At least one role assignment must be defined for the root folder ...
  61. The Role for the End with the EntitySet {0} in the AssociationSet {1} was not supplied and the End found matches one that ...
  62. The Role, '%{role/}', for the RelationshipEnd is not valid because this name is a reserved word, contains one or more invalid ...
  63. The root node name of the query trace retrieval operation has the value '%{nodename/}', which does not correspond to any ...
  64. The row filter for the table, '%{table/}', of the mining model , '%{model/}' , is invalid. The specified filter expression ...
  65. The Sage One Accounting application allows you to import and analyze your financial and sales data in Power BI. After connecting ...
  66. The schedule '{0}' already exists and cannot be created or renamed. This error occurs when the schedule name is not unique. ...
  67. The schedule '{0}' at the Share Point site '{1}' already exists and cannot be created or renamed. This error occurs when ...
  68. The schedule '{0}' cannot be found. The schedule identifier that is provided to an operation cannot be located in the catalog. ...
  69. The schedule has been altered outside of PowerPivot. Use the Manage Data Refresh page to update and re-save the schedule. ...
  70. The schedule has been altered outside of PowerPivot. Use the Manage Data Refresh page to update and re-save the schedule." ...
  71. The scheduled refresh has been suspended because the dataset is too large. Please reduce the size to 1 GB or less, and then ...
  72. The scheduled refresh has been suspended because the dataset is too large. Please reduce the size to 250 MB or less, and ...
  73. The second argument in a Top or Bottom function must be a column. The error occurred at line %d{Line/}, column %d{Column/}. ...
  74. The second parameter passed to function %{funcName/} is invalid. Please specify 0 for the Step Unit or 1 for the Step Size. ...
  75. The second table expression will be evaluated for each row in the first table. Returns the crossjoin of the first table with ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean Português
Portuguese Русский
Russian English
English (United States)