text/microsoft-resx 1.0.0.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 The server is running normally. A fatal error has occurred within the server. The server is running but has no configuration information loaded. The server has been temporarily is not getting or sending data. The server is running in test mode. The server is running properly but is having difficulty accessing data from its data sources. Unspecified error. Ran out of memory. The operation could not complete due to an abnormal server state. The operation took too long to complete (determined by server). The server is currenly processing another polled refresh for one or more of the subscriptions. No subscription handles were specified in the request. The hold time is too long (determined by server). The continuation point is not valid. The filter string is not valid. The item name is no longer available in the server address space. The item name does not conform the server’s syntax. The item path is no longer available in the server address space. The item path does not conform the server’s syntax. The item name is no longer available in the server address space. The item name does not conform the server’s syntax. The item path is no longer available in the server address space. The item path does not conform the server’s syntax. The server cannot convert the data between the requested data type and the canonical data type. The value was out of range. The value is read only and may not be written to. The value is write only and may not be read from or returned as part of a write response. The server does not support writing to the quality and/or timestamp. The property id is not valid for the item. The property id is not valid for the item. The value written was accepted but the output was clamped. The server does not support the requested rate but will use the closest available rate. Not every detected change has been returned since the server's buffer reached its limit and had to purge out the oldest data. The remote server is not currently connected