UI Translation

BizTalk Server 2010

  1. The project '%1' is on an untrusted web server. Opening this project may cause code to be executed with full trust. Do you ...
  2. The project '%1' is under source control. An error occurred registering this project with source control. It is recommended ...
  3. The project '%1' is under source control. This version of Visual Studio .NET does not support source controlled projects. ...
  4. The project '%1' was created with a newer version of Visual Studio, which is incompatible with your version. You can only ...
  5. The project '%1' was created with a newer version of Visual Studio. If you open it with this version of Visual Studio, some ...
  6. The project '%1' will be upgraded to run against version %2 of the .NET Framework the next time it is built. You can use ...
  7. The project already has a Web reference to the URL '%1'. Do you want to update this reference with the latest information ...
  8. The project location "{0}" is not empty. You need to do one of the following: 1. Choose a different location for the new ...
  9. The project location is not fully trusted by the .NET runtime. This is usually because it is either a network share or mapped ...
  10. The project location is not fully trusted by the .NET runtime. This is usually because it is either a network share or mapped ...
  11. The properties BatchName, DestinationPartyName, SenderPartyName and AgreementName present in the activation message does ...
  12. The properties BatchSize and BatchTimeout can be used to specify how BizTalk RFID Mobile forwards events to BizTalk RFID ...
  13. The properties of the device could not be retrieved. To view the last known properties of the device, or to modify the connection ...
  14. The properties that describe these protocol settings. The protocol settings name is unique within the business profile to ...
  15. The property could not be applied because it specifies both input port profile and output port profile for the same source. ...
  16. The property profile for devices {0} could not be applied. This can happen if the devices were offline. For details, see ...
  17. The property set for the "%1" document either is missing or does not contain a valid value for the "%2" property. Please ...
  18. The property sheet field "From" or "Send notification to" is not configured for the BizTalk.SendSMTP transport component. ...
  19. The property values in the selected versions are identical. However, the two versions might differ in the device connectivity ...
  20. The property will contain a value that is a reference number for the code list. Refer to help on code lists to know more ...
  21. The provider for the device %1 has encountered a fault that could result in unpredictable behavior of this device. If this ...
  22. The Provider Manager startup has failed to start up completely within the specified time. Try restarting the Microsoft BizTalk ...
  23. The provider metadata retrieved from assembly {0} was unexpectedly null. For further assistance, contact your provider vendor. ...
  24. The provider {0} has either not been started or has encountered an error. Restart the provider in the service. If that does ...
  25. The public address of this location. This address is used to describe a specific server and database to an external partner. ...
  26. The published message could not be routed because no subscribers were found. This error occurs if the subscribing orchestration ...
  27. The query cannot be opened. Check the file name and try again. Contact your System Administrator if the problem persists. ...
  28. The query cannot be opened. The file does not exists or you do not have the required permissions to access it. Correct the ...
  29. The Query Service Timeout value is invalid or out of range. It must be a strictly positive integer and cannot exceed 1 hour. ...
  30. The real time aggregation is disabled. Please install and configure Sql Server Analysis Services 2008 Enterprise Edition, ...
  31. The Receive Adapter "%1" threw an exception while receiving the handler configuration from the Messaging Engine. Exception ...
  32. The receive adapter on this receive location is not supported on 64-bit host instances. Please make sure that the receive ...
  33. The receive handler configuration for the Windows SharePoint Services adapter is invalid. The following error has been raised: ...
  34. The receive location encountered an error receiving messages. As per configuration to stop on failure, this receive location ...
  35. The receive pipeline: "%1" for receive location: "%2" is trying to explicitly suspend a message that has a non-seekable stream. ...
  36. The receive pipeline:"%1" is trying to suspend a message received on Receive Location:"%2". The Adapter/Receive Location ...
  37. The registry key '{0}' value is incorrect. Refer to the documentation to specify an appropriate value for '{0}'. If this ...
  38. The reported device identifier {0} and the reported connection information {1} in the physical device information affect ...
  39. The reported device identifier {0} and the reported name {1} in the physical device information affect more than one device. ...
  40. The reported device name {0} and the reported connection information {1} in the physical device information affect more than ...
  41. The reported name {0} for the physical device and the corresponding name {1} for the device maintained by BizTalk RFID do ...
  42. The reported physical device name %1 and the corresponding logical device name %2 do not match. Rename the device using BizTalk ...
  43. The requested operation cannot be completed because of a previous WMI failure. The WMI object path is empty in this case. ...
  44. The requested operation is not allowed when the BizTalk orchestration is in the bound state. The only allowed operation is ...
  45. The requested operation is not allowed when the BizTalk orchestration is in the started state. The only allowed operation ...
  46. The requested operation is not allowed when the BizTalk orchestration is in the stopped state. The allowed operations are ...
  47. The resource could not be found in the application "{0}". Please verify that you provided the correct application name. If ...
  48. The revocation status is unknown for the certificate used to encrypt the message. This might be because the Certificate authority ...
  49. The revocation status is unknown for the certificate used to sign the message. This might be because the certificate authority ...
  50. The RFID Print Label Wizard cannot be started because the selected printer does not have any print templates. Add one or ...
  51. The RFID process engine %1 encountered an error of type %2. The service will attempt to restart this process engine automatically, ...
  52. The RFID SDK feature contains product samples, a sample device simulator and a sample device provider along with source code. ...
  53. The Rfid Services feature contains components for Rfid Service Engine, Business Rule Engine, Rfid Store and Rule Engine Database, ...
  54. The RFID Tools and Client Connector feature contains components for the Client Console administration tool, Rfid Connector ...
  55. The RTA timeslice value cannot be greater than the RTA window value. For best results the RTA window should be a multiple ...
  56. The Rules Engine database currently configured on this machine (server = '{0}', database = '{1}') does not match the database ...
  57. The Rules Engine is configured but the database (server = '{0}', database = '{1}') can not be found. Please unconfigure the ...
  58. The rules policy "{0}" with version {1} is not published. Only published policies can be associated with an application. ...
  59. The runtime configuration of Microsoft BizTalk RFID service is not in a valid format. Reason: {0}. Verify that the data in ...
  60. The runtime configuration of the Microsoft BizTalk RFID service does not conform to the schema due to {0}. Verify that the ...
  61. The Schema Annotations: Default Child Delimiter, Default Repeating Delimiter, Default Wrap Character, and Default Escape ...
  62. The schema does not have the structure of a property schema. A property schema can only have element field(s) directly under ...
  63. The schema node with xsd path {0} could not be found in the replaced schema. Links from/to this node will not be created ...
  64. The Schema node's Default Repeating Delimiter and Default Repeating Delimiter Type properties must be set if a record's repeating ...
  65. The schema of the returned table differs in the following way: {0}. Delete the SQL Server Sink database, and then create ...
  66. The schema to be imported has a blank target namespace. Only schemas that have a target namespace can be imported, and that ...
  67. The schema version of the registered Management database on server "%1" / database name "%2" is incompatible with the expected ...
  68. The schema you are trying to open is an XDR schema (BizTalk 2000 or BizTalk 2002 format). Do you want to convert this schema ...
  69. The schema_type attribute has the value "xml". Only non-XML document specifications are allowed for this format. Verify the ...
  70. The script type is not set for the functoid. If this is scripting functoid then check that a script type is set. For all ...
  71. The search condition(s) contain a Numeric Range Dimension with an empty value. When used as search conditions for alerts, ...
  72. The search condition(s) contain a Progress Dimension with an incorrect value. Progress Dimension values must be either all ...
  73. The selected assembly has more than one provider. Choose the provider that you want to register from the list of available ...
  74. The selected database is not compatible with minimum requirements for a {0} database. Please confirm that compatibility level ...
  75. The selected entity is already signed. Signing again will invalidate the existing signature. Are you sure you want to sign ...
Deutsch (Deutschland)
German (Germany) Español (España)
Spanish (Spain) Français (France)
French (France) italiano
Italian 日本語
Japanese 한국어
Korean English
English (United States)