Q186553: Terminal Server Error Messages: 1700 to 1799
Article: Q186553
Product(s): Microsoft Windows NT
Version(s): WinNT:4.0
Operating System(s):
Keyword(s):
Last Modified: 11-DEC-2001
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT Server version 4.0, Terminal Server Edition
-------------------------------------------------------------------------------
SUMMARY
=======
This article describes Terminal Server error messages 1700 to 1799.
MORE INFORMATION
================
Error 1700
----------
The string binding is invalid.
Error 1701
----------
The binding handle is not the correct type.
Error 1702
----------
The binding handle is invalid.
Error 1703
----------
The RPC protocol sequence is not supported.
Error 1704
----------
The RPC protocol sequence is invalid.
Error 1705
----------
The string universal unique identifier (UUID) is invalid.
Error 1706
----------
The endpoint format is invalid.
Error 1707
----------
The network address is invalid.
Error 1708
----------
No endpoint was found.
Error 1709
----------
The timeout value is invalid.
Error 1710
----------
The object universal unique identifier (UUID) was not found.
Error 1711
----------
The object universal unique identifier (UUID) has already been registered.
Error 1712
----------
The type universal unique identifier (UUID) has already been registered.
Error 1713
----------
The RPC server is already listening.
Error 1714
----------
No protocol sequences have been registered.
Error 1715
----------
The RPC server is not listening.
Error 1716
----------
The manager type is unknown.
Error 1717
----------
The interface is unknown.
Error 1718
----------
There are no bindings.
Error 1719
----------
There are no protocol sequences.
Error 1720
----------
The endpoint cannot be created.
Error 1721
----------
Not enough resources are available to complete this operation.
Error 1722
----------
The RPC server is unavailable.
Error 1723
----------
The RPC server is too busy to complete this operation.
Error 1724
----------
The network options are invalid.
Error 1725
----------
There is not a remote procedure call active in this thread.
Error 1726
----------
The remote procedure call failed.
Error 1727
----------
The remote procedure call failed and did not execute.
Error 1728
----------
A remote procedure call (RPC) protocol error occurred.
Error 1730
----------
The transfer syntax is not supported by the RPC server.
Error 1732
----------
The universal unique identifier (UUID) type is not supported.
Error 1733
----------
The tag is invalid.
Error 1734
----------
The array bounds are invalid.
Error 1735
----------
The binding does not contain an entry name.
Error 1736
----------
The name syntax is invalid.
Error 1737
----------
The name syntax is not supported.
Error 1739
----------
No network address is available to use to construct a universal unique
identifier (UUID).
Error 1740
----------
The endpoint is a duplicate.
Error 1741
----------
The authentication type is unknown.
Error 1742
----------
The maximum number of calls is too small.
Error 1743
----------
The string is too long.
Error 1744
----------
The RPC protocol sequence was not found.
Error 1745
----------
The procedure number is out of range.
Error 1746
----------
The binding does not contain any authentication information.
Error 1747
----------
The authentication service is unknown.
Error 1748
----------
The authentication level is unknown.
Error 1749
----------
The security context is invalid.
Error 1750
----------
The authorization service is unknown.
Error 1751
----------
The entry is invalid.
Error 1752
----------
The server endpoint cannot perform the operation.
Error 1753
----------
There are no more endpoints available from the endpoint mapper.
Error 1754
----------
No interfaces have been exported.
Error 1755
----------
The entry name is incomplete.
Error 1756
----------
The version option is invalid.
Error 1757
----------
There are no more members.
Error 1758
----------
There is nothing to unexport.
Error 1759
----------
The interface was not found.
Error 1760
----------
The entry already exists.
Error 1761
----------
The entry is not found.
Error 1762
----------
The name service is unavailable.
Error 1763
----------
The network address family is invalid.
Error 1764
----------
The requested operation is not supported.
Error 1765
----------
No security context is available to allow impersonation.
Error 1766
----------
An internal error occurred in a remote procedure call (RPC).
Error 1767
----------
The RPC server attempted an integer division by zero.
Error 1768
----------
An addressing error occurred in the RPC server.
Error 1769
----------
A floating-point operation at the RPC server caused a division by zero.
Error 1770
----------
A floating-point underflow occurred at the RPC server.
Error 1771
----------
A floating-point overflow occurred at the RPC server.
Error 1772
----------
The list of RPC servers available for the binding of auto handles has been
exhausted.
Error 1773
----------
Unable to open the character translation table file.
Error 1774
----------
The file containing the character translation table has fewer than 512 bytes.
Error 1775
----------
A null context handle was passed from the client to the host during a remote
procedure call.
Error 1777
----------
The context handle changed during a remote procedure call.
Error 1778
----------
The binding handles passed to a remote procedure call do not match.
Error 1779
----------
The stub is unable to get the remote procedure call handle.
Error 1780
----------
A null reference pointer was passed to the stub.
Error 1781
----------
The enumeration value is out of range.
Error 1782
----------
The byte count is too small.
Error 1783
----------
The stub received bad data.
Error 1784
----------
The supplied user buffer is not valid for the requested operation.
Error 1785
----------
The disk media is not recognized. It may not be formatted.
Error 1786
----------
The workstation does not have a trust secret.
Error 1787
----------
The SAM database on the Windows NT Server does not have a computer account
for this workstation trust relationship.
Error 1788
----------
The trust relationship between the primary domain and the trusted domain
failed.
Error 1789
----------
The trust relationship between this workstation and the primary domain
failed.
Error 1790
----------
The network logon failed.
Error 1791
----------
A remote procedure call is already in progress for this thread.
Error 1792
----------
An attempt was made to logon, but the network logon service was not started.
Error 1793
----------
The user's account has expired.
Error 1794
----------
The redirector is in use and cannot be unloaded.
Error 1795
----------
The specified printer driver is already installed.
Error 1796
----------
The specified port is unknown.
Error 1797
----------
The printer driver is unknown.
Error 1798
----------
The print processor is unknown.
Error 1799
----------
The specified separator file is invalid.
Additional query words:
======================================================================
Keywords :
Technology : kbWinNTsearch kbWinNT400search kbWinNTSsearch kbWinNTS400search kbNTTermServ400 kbNTTermServSearch
Version : WinNT:4.0
Issue type : kbinfo
=============================================================================
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1986-2002.