ISA Server 2006 Logging Fields and Values
This document lists the log fields that can be included in Microsoft® Internet Security and Acceleration (ISA) Server 2006 logs, and the log code values.
Firewall: Log Fields
Web Proxy: Log Fields
Web Proxy: Cache Information Log Values
Web Proxy: Error Information Log Values
Web Proxy: Object Source Log Values
Firewall: Action Log Values
Web Proxy and Firewall: Client Agent Log Values
Web Proxy and Firewall: Result Code Log Values
Administration Object Error Codes
The following table lists the fields that you can include in each of the ISA Server log files. Note that, in ISA Server log format, if a field is disabled, it will appear in the log with a hyphen (-). In World Wide Web Consortium (W3C) log file format, the field will not appear. The Bit number column refers to the position in the ISA Server file format.
Bit number | Field name (log viewer) | Field name (MSDE) | Field name (W3C) | Description |
---|---|---|---|---|
0 |
Server Name |
servername |
computer |
The name of the ISA Server computer. This is the computer name assigned in Microsoft Windows Server® 2003 or Windows® 2000 Server. |
1 |
Log Date |
logTime |
date |
The date on which the logged event occurred. In the MSDE format, both the date and the local time are included in the single logTime field, and the bits for both the date and time fields must be set. |
2 |
Log Time |
logTime |
time |
The local time when the logged event occurred. In the W3C extended file format and in ODBC-compliant Microsoft SQL Server™ databases, this time is in Coordinated Universal Time (UTC). In the MSDE format, both the date and the local time are included in the single logTime field, and the bits for both the date and time fields must be set. |
3 |
Transport |
protocol |
IP Protocol |
The transport protocol used for the connection. Common values are TCP and UDP. |
4 |
Client IP and Port |
SourceIP SourcePort |
source |
The IP address of the requesting client and the source port used. In MSDE format, there are separate SourceIP and SourcePort fields to allow individual querying. For ICMP packets, the additional field indicates the ICMP type. |
5 |
Destination IP and Port |
DestinationIP Destination Port |
destination |
The network IP address and the reserved port number on the remote computer that provides service to the current connection. The port number is used by the client application initiating the request. In MSDE format, there are separate DestinationIP and DestinationPort fields to allow individual querying. For ICMP packets, the additional field indicates the ICMP code. |
6 |
Original Client IP |
OriginalClientIP |
original client IP |
The original IP address of the requesting client. |
7 |
Source Network |
SourceNetwork |
source network |
The network from which the request originated. |
8 |
Destination Network |
DestinationNetwork |
destination network |
The network to which the request was sent. |
9 |
Action |
Action |
action |
The action performed by the Microsoft Firewall service for the current session or connection. The possible values are defined in the FpcAction enumerated type. |
10 |
Result Code |
resultcode |
status |
A Windows error code or an ISA Server error code in HRESULT format. |
11 |
Rule |
rule |
rule |
The rule that either allowed or denied access to the request, as follows: If an outgoing request was allowed, this field reflects the access rule that allowed the request. If an outgoing request was denied, this field reflects the access rule that blocked the request. If an incoming request was denied, this field reflects the Web publishing or server publishing rule that denied the request. If no rule specifically allowed the outgoing or incoming request, the request is denied. In this case, the field is empty. |
12 |
Protocol |
ApplicationProtocol |
application protocol |
The name of the application protocol used for the connection as defined in the collection of protocol definitions. |
13 |
Bidirectional |
Bidirectional |
Bidirectional |
A value from the FpcBidirection enumerated type that indicates whether the connection was bidirectional. |
14 |
Bytes Sent |
bytessent |
bytes sent |
The total number of bytes sent from the client to the destination host during the current connection. A hyphen (-), a zero (0), or a negative number in this field indicates that this information was not provided by the destination host or that no bytes were sent to the destination host. |
15 |
Bytes Sent Delta |
bytessentDelta |
bytes sent intermediate |
The number of bytes sent from the client to the destination host since the previous log entry for the current connection. A hyphen (-), a zero (0), or a negative number in this field indicates that this information was not provided by the destination host or that no bytes were sent to the destination host. |
16 |
Bytes Received |
bytesrecvd |
bytes received |
The total number of bytes sent from the remote computer and received by the client during the current connection. A hyphen (-), a zero (0), or a negative number in this field indicates that this information was not provided by the remote computer or that no bytes were received from the remote computer. |
17 |
Bytes Received Delta |
bytesrecvdDelta |
bytes received intermediate |
The number of bytes sent from the remote computer and received by the client since the previous log entry for the current connection. A hyphen (-), a zero (0), or a negative number in this field indicates that this information was not provided by the remote computer or that no bytes were received from the remote computer. |
18 |
Processing Time |
connectiontime |
connection time |
The total time, in milliseconds, that was needed by ISA Server to process the current connection. It measures the time elapsed from the time when the ISA Server computer first received the request to the time when final processing occurred on the ISA Server computer—when results were returned to the client and the connection was closed. |
19 |
Processing Time Delta |
connectiontimeDelta |
connection time intermediate |
The time, in milliseconds, that has elapsed since the previous log entry for the current connection. |
20 |
Source Proxy |
SourceProxy |
source proxy |
Reserved for future use. |
21 |
Destination Proxy |
DestinationProxy |
destination proxy |
Reserved for future use. |
22 |
Client Host Name |
SourceName |
Source Name |
Reserved for future use. |
23 |
Destination Host Name |
DestinationName |
destination name |
The domain name for the remote computer that provides service to the current connection. |
24 |
Client Username |
ClientUserName |
Username |
The account of the user making the request. A question mark (?) next to the user name indicates that the user name was sent but the user was not authenticated by ISA Server. If ISA Server access control is not being used, ISA Server uses Anonymous. |
25 |
Client Agent |
ClientAgent |
agent |
The name and version of the operating system that is running on the Firewall client that created the session, as indicated by the HTTP User-Agent header sent by the client's browser application. This field is not applicable to SecureNAT sessions. For the supported strings, see Web Proxy and Firewall: Client Agent Log Values. A User-Agent header that is not supported is regarded as an unknown operating system. |
26 |
Session ID |
sessionid |
Session ID |
An identifier that identifies a session's connections. For Firewall clients, each process that connects through the Microsoft Firewall service initiates a session. For SecureNAT clients, a single session is opened for all the connections that originate from the same IP address. |
27 |
Connection ID |
connectionid |
Connection ID |
An identifier that identifies entries belonging to the same socket. Outbound TCP usually has two entries for each connection: when the connection is established and when the connection is terminated. UDP usually has two entries for each remote address. |
28 |
Network Interface |
Interface |
Interface |
The network adapter with which the connection was established on the ISA Server computer. |
29 |
Raw IP Header |
IPHeader |
IP header |
The IP header of the current packet. Information is supplied to this field only for packets that are denied passage and are dropped by ISA Server. |
30 |
Raw Payload |
Payload |
protocol payload |
The protocol header of the current packet. Information is supplied to this field only for packets that are denied passage and are dropped by ISA Server. |
The following table lists the fields that you can include in the ISA Server Web Proxy log entries. Note that, in ISA Server log format, if a field is disabled, it will appear in the log with a hyphen (-). In World Wide Web Consortium (W3C) log file format, the field will not appear. The Bit number column refers to the position in the ISA Server file format.
Bit number | Field name (log viewer) | Field name (MSDE) | Field name (W3C) | Description |
---|---|---|---|---|
0 |
Client IP |
ClientIP |
c-ip |
The IP address of the requesting client. |
1 |
Client Username |
ClientUserName |
cs-username |
The user account making the request. A question mark (?) indicates that the user name was sent but the user was not authenticated by ISA Server. If ISA Server access control is not being used, ISA Server uses Anonymous. |
2 |
Client Agent |
ClientAgent |
c-agent |
The name and version of the client application sent in the HTTP User-Agent header. When ISA Server is actively caching, this field is set to ISA Server. |
3 |
Authenticated Client |
ClientAuthenticate |
sc-authenticated |
Indicates whether the client has been authenticated with the ISA Server computer. Possible values are Y and N. |
4 |
Log Date |
logTime |
date |
The date on which the logged event occurred. In the MSDE format, both the date and the local time are included in the single logTime field, and the bits for both the date and time fields must be set. |
5 |
Log Time |
logTime |
time |
The local time when the logged event occurred. In the W3C extended file format and in ODBC-compliant SQL Server databases, this time is in Coordinated Universal Time (UTC). In the MSDE format, both the date and the local time are included in the single logTime field, and the bits for both the date and time fields must be set. |
6 |
Service |
service |
s-svcname |
The name of the service that is logged. For example, fwsrv indicates the Microsoft Firewall service. |
7 |
Server Name |
servername |
s-computername |
The name of the ISA Server computer. |
8 |
Referring Server |
referredserver |
cs-referred |
Reserved for future use. |
9 |
Destination Host Name |
DestHost |
r-host |
The domain name for the remote computer that provides service to the current connection. A hyphen (-) in this field may indicate that an object was retrieved from the local cache and not from the destination. |
10 |
Destination IP |
DestHostIP |
r-ip |
The network IP address of the remote computer that provides service to the current connection. A hyphen (-) in this field may indicate that an object was sourced from the local cache and not from the destination. One exception is negative caching. In that case, this field contains a destination IP address for which a negative cached object was returned. |
11 |
Destination Port |
DestHostPort |
r-port |
The reserved port number on the remote computer that provides service to the current connection. This is used by the client application initiating the request. |
12 |
Processing Time |
processingtime |
time-taken |
The total time, in milliseconds, that is needed by ISA Server to process the current connection. It measures the time elapsed from the time when the server first receives the request to the time when final processing occurs on the server—when results are returned to the client and the connection is closed. For cache requests that are processed through Web Proxy Filter, the processing time measures the elapsed server time needed to fully process a client request and return an object to the client. |
13 |
Bytes Received |
bytesrecvd |
cs-bytes |
The number of bytes sent from the remote computer and received by the client during the current connection. A hyphen (-), a zero (0), or a negative number in this field indicates that this information was not provided by the remote computer or that no bytes were received from the remote computer. |
14 |
Bytes Sent |
bytessent |
sc-bytes |
The number of bytes sent from the client to the remote computer during the current connection. A hyphen (-), a zero (0), or a negative number in this field indicates that this information was not provided by the remote computer or that no bytes were sent to the remote computer. |
15 |
Protocol |
protocol |
cs-protocol |
The application protocol used for the connection. Common values are http for Hypertext Transfer Protocol, https for Secure HTTP, and ftp for FTP. |
16 |
Transport |
transport |
cs-transport |
The transport protocol used for the connection. Common values are TCP and UDP. |
17 |
HTTP Method |
operation |
s-operation |
The HTTP method used. Common values are GET, PUT, POST, and HEAD. |
18 |
URL |
uri |
cs-uri |
The URL requested. |
19 |
MIME Type |
mimetype |
cs-mime-type |
The MIME type for the current object. This field may also contain a hyphen (-) to indicate that this field is not used or that a valid MIME type was not defined or supported by the remote computer. |
20 |
Object Source |
objectsource |
s-object-source |
The type of source that was used to retrieve the current object. A table of some possible values is provided in Web Proxy: Object Source Log Values. |
21 |
Result Code |
resultcode |
sc-status |
A Windows (Win32) error code (for values less than 100), an HTTP status code (for values between 100 and 1,000), a Winsock error code (for values between 10,004 and 11,031), or an ISA Server error code. A table of some possible values is provided in Web Proxy and Firewall: Result Code Log Values. |
22 |
Cache Info |
CacheInfo |
s-cache-info |
A number reflecting the cache status of the object, which indicates the reasons why the object was or was not cached. The number logged is the sum of the values for all the conditions that are met. A table of the possible values is provided in Web Proxy: Cache Information Log Values. |
23 |
Rule |
rule |
rule |
The rule that either allowed or denied access to the request, as follows: If an outgoing request was allowed, this field indicates the access rule that allowed the request. If an outgoing request was denied by a policy rule, this field indicates the access rule that blocked the request. If an incoming request was denied by a policy rule, this field indicates the Web publishing or server publishing rule that denied the request. If ISA Server denied the connection for any reason other than a policy rule, this field contains a hyphen (-), and the Result Code field (bit 21) indicates the reason. |
24 |
Filter Information |
FilterInfo |
FilterInfo |
Information supplied by a Web filter. For example, if HTTP Filter rejected a request, this field contains the reason for the rejection. |
25 |
Source Network |
SrcNetwork |
cs-Network |
The network from which the request originated. |
26 |
Destination Network |
DstNetwork |
sc-Network |
The network to which the request was sent. |
27 |
Error info (ErrorInfo) |
ErrorInfo |
error-info |
A 32-bit bitmask that provides additional information about the request that can help identify the source of the error if an error occurred. A table of the possible bit fields is provided in Web Proxy: Error Information Log Values. |
28 |
Action |
Action |
action |
The action performed by the Microsoft Firewall Service for the current session or connection. The possible values are defined in the FpcAction enumerated type. |
29 |
GMT Log Time |
GmtLogTime |
GmtLogTime |
The date and time in Coordinated Universal Time (UTC) when the log entry was made (introduced in ISA Server Enterprise Edition). |
The Web Proxy log can include a cache info field that specifies the cache status of the object, which indicates why the object was or was not cached. The following table lists the possible cache info values.
Value | Description |
---|---|
0x00000001 |
Request should not be served from the cache. |
0x00000002 |
Request includes the IF-MODIFIED-SINCE header. |
0x00000004 |
Request includes one of these headers: CACHE-CONTROL:NO-CACHE or PRAGMA:NO-CACHE. |
0x00000008 |
Request includes the AUTHORIZATION header. |
0x00000010 |
Request includes the VIA header. |
0x00000020 |
Request includes the IF-MATCH header. |
0x00000040 |
Request includes the RANGE header. |
0x00000080 |
Request includes the CACHE-CONTROL: NO-STORE header. |
0x00000100 |
Request includes the CACHE-CONTROL: MAX-AGE, CACHE-CONTROL: MAX-STALE, or CACHE-CONTROL: MIN-FRESH header. |
0x00000200 |
Cache could not be updated. |
0x00000400 |
IF-MODIFIED-SINCE time specified in the request is newer than cached LASTMODIFIED time. |
0x00000800 |
Request includes the CACHE-CONTROL: ONLY-IF-CACHED header. |
0x00001000 |
Request includes the IF-NONE-MATCH header. |
0x00002000 |
Request includes the IF-UNMODIFIED-SINCE header. |
0x00004000 |
Request includes the IF-RANGE header. |
0x00008000 |
More than one VARY header. |
0x00010000 |
Response includes the CACHE-CONTROL: PUBLIC header. |
0x00020000 |
Response includes the CACHE-CONTROL: PRIVATE header. |
0x00040000 |
Response includes the CACHE-CONTROL: NO-CACHE or PRAGMA: NO-CACHE header. |
0x00080000 |
Response includes the CACHE-CONTROL: NO-STORE header. |
0x00100000 |
Response includes either the CACHE-CONTROL: MUST-REVALIDATE or CACHE-CONTROL: PROXY-REVALIDATE header. |
0x00200000 |
Response includes the CACHE-CONTROL: MAX-AGE or S-MAXAGE header. |
0x00400000 |
Response includes the VARY header. |
0x00800000 |
Response includes the LAST-MODIFIED header. |
0x01000000 |
Response includes the EXPIRES header. |
0x02000000 |
Response includes the SET-COOKIE header. |
0x04000000 |
Response includes the WWW-AUTHENTICATE header. |
0x08000000 |
Response includes the VIA header. |
0x10000000 |
Response includes the AGE header. |
0x20000000 |
Response includes the TRANSFER-ENCODING header. |
0x40000000 |
Response should not be cached. |
The Web Proxy log can include an error information field. The following table lists the possible values.
Value | Descriptive code | Description |
---|---|---|
0x00000001 |
ERROR_INFO_IO_RECV_FROM_CLIENT |
Error receiving packets from client. |
0x00000002 |
ERROR_INFO_IO_SEND_TO_CLIENT |
Error sending packets to client. |
0x00000004 |
ERROR_INFO_IO_SEND_TO_SERVER |
Error sending packets to server. |
0x00000008 |
ERROR_INFO_IO_RECV_FROM_SERVER |
Error receiving packets from server. |
0x00000010 |
ERROR_INFO_DEST_IS_MEMBER |
- |
0x00000020 |
ERROR_INFO_CLIENT_IS_MEMBER |
- |
0x00000040 |
ERROR_INFO_DURING_CONNECT |
Error while connecting. |
0x00000080 |
ERROR_INFO_CLIENT_KA |
Connection with client is "Keep-Alive." |
0x00000100 |
ERROR_INFO_SERVER_KA |
Connection with upstream server is "Keep-Alive." |
0x00000200 |
ERROR_INFO_REQUEST_HAS_BODY |
Client's request includes a body (of non-zero content length). |
0x00000400 |
ERROR_INFO_RESPONSE_HAS_BODY |
Server's response includes a body (of non-zero content length). |
0x00000800 |
ERROR_INFO_IP_FROM_DNS_CACHE |
Name resolution made using Domain Name System (DNS) cache. |
The Web Proxy log can include an object source field that specifies the source that was used to retrieve the current object. The following table lists the possible object source values.
Source values | Description |
---|---|
0 |
No source information is available. |
Cache |
Source is the cache. Object returned from cache. |
Inet |
Source is the Internet. Object added to cache. |
Member |
Returned from another array member. |
NotModified |
Source is the cache. Client performed an IF-MODIFIED-SINCE request and object had not been modified. |
NVCache |
Source is the cache. Object could not be verified to source. |
Upstream |
Object returned from an upstream proxy cache. |
Vcache |
Source is the cache. Object was verified to source and had not been modified. |
VFInet |
Source is the Internet. Cached object was verified to source and had been modified. |
The Firewall log can include an action field listing the action performed by the Microsoft Firewall Service for the current session or connection. The values provided in the "Action" field are short strings derived from the names of the enumeration values defined in the FpcAction COM object after deleting the prefix "fpcAction."
The following table lists the possible action values.
MSDE value | Value | String | Description |
---|---|---|---|
0 |
NotLogged |
- |
No action was logged. |
1 |
Bind |
- |
The Firewall service associated a local address with a socket. |
2 |
Listen |
- |
The Firewall service placed a socket in a state in which it listens for an incoming connection. |
3 |
GHBN |
- |
Get host by name request. The Firewall service retrieved host information corresponding to a host name. |
4 |
GHBA |
- |
Get host by address request. The Firewall service retrieved host information corresponding to a network address. |
5 |
RedirectBind |
- |
The Firewall service enabled a connection using a local address associated with a socket. |
6 |
Establish |
Initiated connection |
The Firewall service established a session. |
7 |
Terminate |
Closed connection |
The Firewall service terminated a session. |
8 |
Denied |
Denied connection |
The action requested was denied. |
9 |
Allowed |
Allowed connection |
The action requested was allowed. |
10 |
Failed |
Failed connection |
The action requested failed. |
11 |
Intermediate |
- |
The action was intermediate. |
12 |
SuccessfulConnection |
- |
The Firewall service was successful in establishing a connection to a socket. |
13 |
UnsuccessfulConnection |
- |
The Firewall service was unsuccessful in establishing a connection to a socket. |
14 |
Disconnect |
- |
The Firewall service closed a connection on a socket. |
15 |
UserClearedQuarantine |
User cleared quarantine |
The Firewall service cleared a quarantined virtual private network (VPN) client. |
16 |
QuarantineTimeout |
Quarantine timeout |
The Firewall service disqualified a quarantined VPN client after the time-out period elapsed. |
The Web Proxy and Firewall logs can include a Client Agent field that specifies the operating system initiating the request. The following table lists the possible operating system values.
User-Agent header | Client Agent value |
---|---|
Windows NT 5.2 |
Windows Server 2003 |
Windows NT 5.1 |
Windows XP |
windows nt 5 |
Windows 2000 |
windows 2000 |
Windows 2000 |
win2000 |
Windows 2000 |
winnt |
Windows NT |
windows nt |
Windows NT |
win98 |
Windows 98 |
windows 98 |
Windows 98 |
win95 |
Windows 95 |
windows 95 |
Windows 95 |
win32 |
Windows 32-bit |
win16 |
Windows 16-bit |
windows ce |
Windows CE |
windows |
Windows |
aix |
aix |
amiga |
amiga |
hp |
hp |
irix |
irix |
linux |
linux |
mac |
mac |
solaris |
solaris |
sun |
sun |
unix |
unix |
vax |
vax |
If ISA Server does not recognize the operating system, the log field value is set to Unknown.
The Web Proxy and Firewall logs can include a Result Code field that specifies the status of the request. It may be a Windows (Win32) error code (for values less than 100), an HTTP status code (for values between 100 and 1,000), a Winsock error code (for values between 10,004 and 11,031), or an ISA Server error code.
For the Web Proxy log, the HTTP Status Code column represents an HTTP error (from the Web proxy). It can get one of the following values:
- An HTTP response code, as defined in the HTTP RFC. For a list of HTTP response codes, see the Platform SDK.
- A Winsock error code. For a list of Winsock error codes, see MSDN.
- An ISA Server Web Proxy error code. These errors also include a description.
The following table summarizes some of the result code values.
Source values | Description |
---|---|
0 |
The operation completed successfully. |
200 |
OK. |
201 |
Created. |
202 |
Accepted. |
204 |
No content. |
301 |
Moved permanently. |
302 |
Moved temporarily. |
304 |
Not modified. |
400 |
Bad request. |
401 |
Unauthorized. |
403 |
Forbidden. |
404 |
Not found. |
500 |
Server error. |
501 |
Not implemented. |
502 |
Bad gateway. |
503 |
Out of resources. |
995 |
Operation aborted. |
10060 |
A connection timed out. |
10061 |
A connection was refused by the destination host. |
10065 |
No route to host. |
11001 |
Host not found. |
12217 |
The request was rejected by HTTP Filter. |
In the Firewall log, the result code field represents an error. It can be one of the following:
- A Windows-based HRESULT error code.
- An ISA Server service error code. These errors typically begin with 0xC00. Error text typically includes FWX_E_.
The following table summarizes run-time error codes, defined in Wspfwerr.h, that may be returned by the Microsoft Firewall service and may appear as result codes in ISA Server logs.
Symbolic name | Code | Message text |
---|---|---|
FWX_E_TERMINATING |
0xC0040001 |
The object is shutting down. |
FWX_E_INVALID_ARG |
0xC0040002 |
The argument is invalid. |
FWX_E_ALREADY_IN_BLOCKING_OP |
0xC0040003 |
The blocking operation is already started. |
FWX_E_NOT_IN_BLOCKING_OP |
0xC0040004 |
There is no blocking operation to be ended. |
FWX_E_FILTER_NOT_REGISTERED |
0xC0040005 |
The filter is not registered. |
FWX_E_ALREADY_EXISTS |
0x800700B7 |
The object cannot be created because an object with the same name already exists. |
FWX_E_BUFFERFULL |
0xC0040007 |
Not all the data was appended to the buffer object because the buffer was full. |
FWX_E_ALREADY_EMULATED |
0xC0040009 |
The connection is already emulated by another filter. |
FWX_E_BAD_CONTEXT |
0xC004000A |
The method was not called while handling any of the supported events. |
FWX_E_NOT_SUPPORTED |
0xC004000B |
Modifying this property is not allowed for this session. |
FWX_E_NOT_AUTHENTICATED |
0xC004000C |
The action cannot be performed because the session is not authenticated. |
FWX_E_POLICY_RULES_DENIED |
0xC004000D |
The policy rules do not allow the user request. |
FWX_E_MIME_NEEDED |
0xC004000E |
The MIME type is required. |
FWX_E_MUST_USE_DS |
0xC004000F |
- |
FWX_E_NOT_EMULATED |
0xC0040010 |
The connection is not emulated. |
FWX_E_IS_BUSY |
0xC0040011 |
- |
FWX_E_NETWORK_RULES_DENIED |
0xC0040012 |
- |
FWX_E_FRAGMENT_PACKET_DROPPED |
0xC0040013 |
- |
FWX_E_FWE_SPOOFING_PACKET_DROPPED |
0xC0040014 |
- |
FWX_E_TCPIPDROP_PACKET_DROPPED |
0xC0040015 |
- |
FWX_E_NO_BACKLOG_PACKET_DROPPED |
0xC0040016 |
- |
FWX_E_TCP_NOT_SYN_PACKET_DROPPED |
0xC0040017 |
A non-SYN packet was dropped because it was sent by a source that does not have an established connection with the ISA Server computer. |
FWX_E_BAD_LENGTH_PACKET_DROPPED |
0xC0040018 |
- |
FWX_E_PING_OF_DEATH_PACKET_DROPPED |
0xC0040019 |
- |
FWX_E_OUT_OF_BAND_PACKET_DROPPED |
0xC004001A |
- |
FWX_E_IP_HALF_SCAN_PACKET_DROPPED |
0xC004001B |
- |
FWX_E_LAND_ATTACK_DROPPED |
0xC004001C |
- |
FWX_E_UDP_BOMB_DROPPED |
0xC004001D |
- |
FWX_E_FULLDENY_DROPPED |
0xC004001E |
- |
FWX_E_IPOPTIONS_DROPPED |
0xC004001F |
- |
FWX_E_UNCOMPLETED_CONNECTION_REQUEST |
0xC0040020 |
An attempt to log on to the VPN server was rejected during the authentication phase because the authentication data was not received in a timely manner. The client session was disconnected. |
FWX_E_CONNECTION_REQUEST_REJECTED |
0xC0040021 |
An attempt to log on to the VPN server was rejected during the authentication phase. The client session was disconnected. |
FWX_E_VALIDATE_QUARANTINE_FAILED |
0xC0040022 |
The VPN quarantine settings could not be validated. The client session was disconnected. |
FWX_E_VPN_CONNECTIONS_LIMIT_EXCEEDED |
0xC0040023 |
The VPN client connection limit was exceeded. The client session was disconnected. |
FWX_E_OUT_OF_RESOURCES |
0xC0040024 |
- |
FWX_E_BROADCAST_PACKET_DROPPED |
0xC0040025 |
- |
FWX_E_UNKNOWN_ADAPTER_DROPPED |
0xC0040026 |
- |
FWX_E_ICMP_ERROR_PACKET_DROPPED |
0xC0040027 |
- |
FWX_E_INVALID_PROTOCOL_PACKET_DROPPED |
0xC0040028 |
- |
FWX_E_PORT_ZERO_PACKET_DROPPED |
0xC0040029 |
- |
FWX_E_SYN_ATTACK_START |
0xC004002A |
ISA Server detected a SYN attack. |
FWX_E_SYN_ATTACK_END |
0xC004002B |
ISA Server is no longer experiencing a SYN attack. |
FWX_E_INVALID_DHCP_OFFER |
0xC004002C |
- |
FWX_E_UNREACHABLE_ADDRESS |
0xC004002D |
- |
FWX_E_ADDRESS_NOT_ALLOWED |
0xC004002E |
- |
FWX_E_IPSEC_NO_ROUTE_DROPPED |
0xC004002F |
- |
FWX_E_OUTBOUND_PATH_THROUGH_DROPPED |
0xC0040030 |
- |
FWX_E_BAD_TCP_CHECKSUM_DROPPED |
0xC0040031 |
- |
FWX_E_VPN_USER_MAPPING_FAILED |
0xC0040032 |
An attempt to map a VPN client to a Windows user failed. The client session was disconnected. |
FWX_E_RULE_QUOTA_EXCEEDED_DROPPED |
0xC0040033 |
A connection was rejected because the maximum number of connections that can be created for a rule during one second was exceeded. |
FWX_E_SEQ_ACK_MISMATCH |
0xC0040034 |
A TCP packet was rejected because it has an invalid sequence number or an invalid acknowledgement number. |
WSA_RWS_GRACEFUL_SHUTDOWN or FWX_E_GRACEFUL_SHUTDOWN |
0x80074E20 |
A connection was gracefully closed in an orderly shutdown process with a three-way FIN-initiated handshake. |
WSA_RWS_ABORTIVE_SHUTDOWN or FWX_E_ABORTIVE_SHUTDOWN |
0x80074E21 |
A connection was abortively closed after one of the peers sent a RST segment. |
WSA_RWS_QUOTA or FWX_E_RULE_QUOTA_EXCEEDED_DROPPED |
0x80074E23 |
A connection was refused because a quota set in a rule was exceeded. |
WSA_RWS_CONNECTION_KILLED or FWX_E_CONNECTION_KILLED |
0x80074E24 |
ISA Server killed a connection. |
WSA_RWS_TIMEOUT or FWX_E_TIMEOUT |
0x80074E25 |
A connection was terminated because it was idle for more than the time-out period, or the time-out on an incomplete action expired. |
WSA_RWS_ADMIN_TERMINATE or FWX_E_ADMIN_TERMINATE |
0x80074E26 |
A connection was terminated from ISA Server Management during shutdown, or when a VPN client was disconnected. |
FWX_E_THREAD_QUOTA_EXCEEDED |
0xC0040035 |
A blocking operation could not be performed because the thread limit for this operation was reached. |
FWX_E_DNS_QUOTA_EXCEEDED |
0xC0040036 |
A DNS query could not be performed because the query limit was reached. |
FWX_E_TCP_RATE_QUOTA_EXCEEDED_DROPPED |
0xC0040037 |
A connection was rejected because the maximum connections rate for a single client host was exceeded. |
FWX_E_TCP_NO_SERVER_REPLY |
0xC0040038 |
A connection was closed because no SYN/ACK reply was received from the server. |
The following are the COM object warning (WRN) and error (ERR) codes, defined in FpcErrorCodes.h. Note that the error codes with a message identifier equal to or greater than 0xC004039D are defined only in ISA Server 2006 Enterprise Edition.
Symbolic name | Code | Message ID | Message text |
---|---|---|---|
S_FPCLOG_BAD_COLUMN_SELECTION |
FPC_WRN(0x200) |
0x80040200 |
An invalid set of log fields was selected. Any required log field that was not selected will also be logged. |
S_FPC_ALERTSRV_ALERT_NOT_FOUND |
FPC_WRN(0x201) |
0x80040201 |
The specified alert was not found. |
S_FPC_SERVICE_INACCESSIBLE |
FPC_WRN(0x202) |
0x80040202 |
The service is inaccessible. |
E_FPC_CERTIFICATE_NOT_INSTALLED |
FPC_ERR(0x300) |
0xC0040300 |
The specified certificate cannot be located. |
E_FPC_CROSS_PRIORITY_BOUNDARY |
FPC_ERR(0x301) |
0xC0040301 |
A Web filter can be moved only into the positions of filters that have the same priority. |
E_FPC_DEST_NOT_IP |
FPC_ERR(0x302) |
0xC0040302 |
This destination object is not defined using an IP address. |
E_FPC_NO_STORAGE |
FPC_ERR(0x303) |
0xC0040303 |
The object cannot be written to persistent storage before its containing object is saved. |
E_FPC_OBJECT_INVALID |
FPC_ERR(0x304) |
0xC0040304 |
The object is not valid. |
E_FPC_STRING_BAD |
FPC_ERR(0x305) |
0xC0040305 |
The string is empty or invalid. |
E_FPC_EVENT_NOT_DEFINED |
FPC_ERR(0x306) |
0xC0040306 |
The event GUID specified in the alert cannot be found in the events collection. |
E_FPC_NON_REMOVAL_EVENT |
FPC_ERR(0x307) |
0xC0040307 |
ISA Server predefined events cannot be removed. |
E_FPC_ALERT_KEY_INVALID |
FPC_ERR(0x308) |
0xC0040308 |
The additional key specified is outside of the range of possible values. |
E_FPC_CANNOT_DEL_DEFAULT_RULE |
FPC_ERR(0x309) |
0xC0040309 |
The default rule cannot be removed. |
E_FPC_CANNOT_MOVE_DEFAULT_RULE |
FPC_ERR(0x30A) |
0xC004030A |
The order of application of the default rule cannot be modified. It will always be applied last. |
E_FPC_CORRUPTED_OBJECT_DATA |
FPC_ERR(0x30B) |
0xC004030B |
The object's data is corrupted. |
E_DOMAIN_CANT_BE_IP_ADDR |
FPC_ERR(0x30C) |
0xC004030C |
An IP address cannot be used for a domain name in a domain name set. |
E_FPC_QUERY_BUFFER_FULL |
FPC_ERR(0x30D) |
0xC004030D |
There are too many records in the query result. |
E_FPC_THRESHOLD_OUT_OF_RANGE |
FPC_ERR(0x30E) |
0xC004030E |
The threshold set is not in the range of permissible values from 1 through 65535. |
E_FPC_OLD_DAILYSUMMARY_VERSION |
FPC_ERR(0x30F) |
0xC004030F |
A daily summary file is corrupted, or was generated with a previous version of the product. It cannot be used to generate the report. |
E_FPC_INVALID_SERVER_NAME |
FPC_ERR(0x310) |
0xC0040310 |
The server name has not been specified or is invalid. Enter a valid server name. |
E_FPC_STRING_CONTAINS_INVALID_CHARACTERS |
FPC_ERR(0x311) |
0xC0040311 |
The server name contains invalid characters. Enter a valid server name. |
E_FPC_EMPTY_STRING |
FPC_ERR(0x312) |
0xC0040312 |
The string is empty or invalid. |
E_FPC_VALUE_TOO_LARGE |
FPC_ERR(0x313) |
0xC0040313 |
The value is larger than the maximum allowed value. |
E_FPC_VALUE_TOO_SMALL |
FPC_ERR(0x314) |
0xC0040314 |
The value is smaller than the minimum allowed value. |
E_FPC_COMPONENT_NOT_INSTALLED |
FPC_ERR(0x315) |
0xC0040315 |
The ISA Server component is not installed. |
E_FPC_BAD_IP_FORMAT |
FPC_ERR(0x316) |
0xC0040316 |
A valid IP address must be provided. |
E_FPC_IP_FROM_MORE_THAN_TO |
FPC_ERR(0x317) |
0xC0040317 |
The value of Ip_From must be lower than the value of Ip_To. |
E_FPC_IP_PAIR_ALREADY_EXISTS |
FPC_ERR(0x318) |
0xC0040318 |
The IP address range specified already exists in the list. |
E_FPC_ALERT_MUST_HAVE_ACTIONS |
FPC_ERR(0x319) |
0xC0040319 |
The alert <AlertName> must have at least one action enabled. |
E_FPC_DEFAULT_RULE_IS_READ_ONLY |
FPC_ERR(0x31A) |
0xC004031A |
This property cannot be modified for the default rule. |
E_FPC_PROTOCOL_IS_READ_ONLY |
FPC_ERR(0x31B) |
0xC004031B |
The protocol definition cannot be removed or modified. |
E_FPC_ALERT_ALREADY_DEFINED |
FPC_ERR(0x31C) |
0xC004031C |
An alert with the event GUID, server name, and additional key specified already exists. |
E_FPC_FAILED_TO_READ_DISK_SIZE_AND_TYPE |
FPC_ERR(0x31D) |
0xC004031D |
The disk size and type properties cannot be read. |
E_FPC_EVENT_IN USE |
FPC_ERR(0x31E) |
0xC004031E |
The event definition <EventName> cannot be removed because it is used by the alert <AlertName>. |
E_FPC_PNAT_PROTOCOL_NOT_INBOUND |
FPC_ERR(0x31F) |
0xC004031F |
The protocol specified is not a server (inbound) protocol. |
E_FPC_ITEM_IN_USE |
FPC_ERR(0x320) |
0xC0040320 |
In Standard Edition: The <ObjectType1> <ObjectName1> cannot be deleted because it is used in the <ObjectType2> <ObjectName2>. In Enterprise Edition: The <ObjectType1> <ObjectName1> cannot be deleted because it is used in the <ObjectScope> <ObjectType2> <ObjectName2>. |
E_FPC_LOW_RANGE_MORE_THAN_HIGH_RANGE |
FPC_ERR(0x321) |
0xC0040321 |
The lower port must be smaller than or equal to the upper port in the <ObjectType> <RangeName>. |
E_FPC_PORT_OUT_OF_RANGE |
FPC_ERR(0x322) |
0xC0040322 |
The lower and upper ports defining a port range must be between 1 and 65535. |
E_FPC_IDENTICAL_STORAGE_NAME |
FPC_ERR(0x323) |
0xC0040323 |
An item with an identical storage name already exists in this collection. Each item added to the collection must have a unique storage name. |
E_FPC_NOT_COMMON_NETWORK_DIALUP_CONNECTION |
FPC_ERR(0x324) |
0xC0040324 |
The specified network dial-up connection cannot be found on the computer. |
E_FPC_NOT_FULL_URL |
FPC_ERR(0x325) |
0xC0040325 |
The URL must start with https://. |
E_FPC_NO_CREDENTIALS |
FPC_ERR(0x326) |
0xC0040326 |
No credentials were provided. |
E_FPC_NO_DIALUP_AVAILABLE |
FPC_ERR(0x327) |
0xC0040327 |
Automatic dialing cannot be used. There are no dial-up connection entries configured. |
E_FPC_INVALID_NETWORK_CHOSEN_FOR_AUTODIAL |
FPC_ERR(0x328) |
0xC0040328 |
Automatic dialing cannot be enabled for this type of network. |
E_FPC_NOT_SUPPORTED_IN_STANDARD_EDITION |
FPC_ERR(0x329) |
0xC0040329 |
The method or property is not available in ISA Server Standard Edition. |
E_FPC_BAD_LDT_DOMAIN_NAME_FORMAT |
FPC_ERR(0x32A) |
0xC004032A |
The string is not a valid local domain table (LDT) domain name. |
E_FPC_TCP_UDP_MISMATCH |
FPC_ERR(0x32B) |
0xC004032B |
An invalid API was used for the specified protocol. |
E_FPC_HTTP_CACHE_MIN_MUST_BE_LESS_THAN_MAX |
FPC_ERR(0x32C) |
0xC004032C |
The minimum time for content expiration in the cache rule <RuleName> must be less than or equal to the maximum time. |
E_FPC_NEED_SERVER_FOR_CREDENTIALS |
FPC_ERR(0x32D) |
0xC004032D |
Credentials cannot be added when no server is available. |
E_FPC_INVALID_PORT |
FPC_ERR(0x32E) |
0xC004032E |
A port number between 1 and 65535 must be provided. |
E_FPC_INVALID_PORT_INC_0 |
FPC_ERR(0x32F) |
0xC004032F |
A port number between 0 and 65535 must be provided. |
E_FPC_INVALID_PERIODICAL_RUN_ARGUMENTS |
FPC_ERR(0x330) |
0xC0040330 |
The repetition time is longer than the specified interval. |
E_FPC_INVALID_ICMP_CODE |
FPC_ERR(0x331) |
0xC0040331 |
An ICMP code between 0 and 255 must be provided. |
E_FPC_INVALID_ICMP_TYPE |
FPC_ERR(0x332) |
0xC0040332 |
An ICMP type between 0 and 255 must be provided. |
E_FPC_INVALID_PROTOCOL |
FPC_ERR(0x333) |
0xC0040333 |
A communication protocol number between 0 and 255 must be provided. |
E_FPC_PREDEFINED_ITEM_IS_READ_ONLY |
FPC_ERR(0x334) |
0xC0040334 |
This property cannot be modified for the predefined item. |
E_FPC_CAN_NOT_DELETE_PREDEFINED |
FPC_ERR(0x335) |
0xC0040335 |
The item cannot be deleted. It is part of the static configuration. |
E_FPC_IP_RANGE_SET_NOT_ALLOWED |
FPC_ERR(0x336) |
0xC0040336 |
This network type cannot have an IP range set. |
E_FPC_XML_PASSWORD_REQUIRED |
FPC_ERR(0x337) |
0xC0040337 |
A password containing at least eight characters must be specified in the EncryptionPassword parameter when the fpcExportImportPasswords flag is set. |
E_FPC_XML_MISMATCH_IMPORT_OBJECT |
FPC_ERR(0x338) |
0xC0040338 |
The file cannot be imported. The exported file contains an object of type <ObjectType1> which cannot be imported into an object of type <ObjectType2>. |
E_FPC_XML_SCHEMA_VALIDATION_FAILED |
FPC_ERR(0x339) |
0xC0040339 |
Schema validation failed on the exported XML document. |
E_FPC_XML_NO_SERVER_AVAILABLE_FOR_EXPORT_PASSWORD |
FPC_ERR(0x33A) |
0xC004033A |
There is no available ISA Server computer to decrypt the exported password. Verify that services are running on at least one ISA Server computer. |
E_FPC_NO_VPN_CONNECTION_FOR_THE_NETWORK |
FPC_ERR(0x344) |
0xC0040344 |
The VPN properties cannot be configured for non-VPN networks. |
E_FPC_CAN_NOT_CHANGE_CONNECTION_TYPE |
FPC_ERR(0x345) |
0xC0040345 |
The connection type cannot be set for the network specified. |
E_FPC_IP_RANGE_ENTRY_INTERSECT_WITH_LOCAL_NETWORK |
FPC_ERR(0x346) |
0xC0040346 |
The <NetworkName> network includes IP addresses in the range <LowerLimit>–<UpperLimit>. Networks cannot contain IP address ranges that overlap another network. |
E_FPC_IP_RANGE_ENTRY_INTERSECT_WITH_LIMITED_BROADCAST |
FPC_ERR(0x347) |
0xC0040347 |
The specified address range contains the limited broadcast IP address (255.255.255.255). Change the IP range so that it does not contain 255.255.255.255. |
E_FPC_IP_RANGE_ENTRY_INTERSECT_WITH_LOCAL_VPN_CONFIG |
FPC_ERR(0x348) |
0xC0040348 |
The static address pool of the VPN configuration includes IP addresses in the range %1–%2. Networks cannot contain IP address ranges that overlap the static address pool of the VPN configuration. (This error is generated only in Standard Edition.) |
E_FPC_INVALID_NETWORK_CONNECTION_TYPE |
FPC_ERR(0x349) |
0xC0040349 |
The connection type is not valid for this network type. |
E_FPC_VPN_STATIC_ADDRESS_POOL_RAN_OUT_OF_ADDRESSES |
FPC_ERR(0x34A) |
0xC004034A |
There are not enough IP addresses available for VPN connections. For each server, the number of IP addresses in the static address pool must be at least one greater than the sum of the maximum number of connections allowed in the VPN configuration and the number of VPN networks. |
E_FPC_PREDEFINED_NETWORK_IS_READ_ONLY |
FPC_ERR(0x34B) |
0xC004034B |
This property cannot be modified for a predefined network. |
E_FPC_STORAGE_VER_MISMATCH |
FPC_ERR(0x34C) |
0xC004034C |
The ISA Server storage version is incompatible. |
E_FPC_ALERTSRV_UNKNOWN_EVENT |
FPC_ERR(0x34E) |
0xC004034E |
The event signaled cannot be found. |
E_FPC_ALERTSRV_BAD_EVENT_GUID |
FPC_ERR(0x34F) |
0xC004034F |
The event GUID is not a valid GUID. |
E_FPC_ALERTSRV_DUPLICATED_ALERT |
FPC_ERR(0x350) |
0xC0040350 |
An alert with the same event condition, server name, and additional key is already defined. |
E_FPC_PROTOCOL_NOT_OUTBOUND |
FPC_ERR(0x351) |
0xC0040351 |
The specified protocol is a server (inbound) protocol. Inbound protocols can only be used in server publishing rules. |
E_FPC_VIP_IS_NOT_IN_RELATED_NETWORK |
FPC_ERR(0x352) |
0xC0040352 |
The specified virtual IP address <virtual IP address> is not contained in the <NetworkName> network, in which the Network Load Balancing cluster resides. |
E_FPC_NLB_NIC_IDENTIFIER_IS_NOT_UNIQUE |
FPC_ERR(0x353) |
0xC0040353 |
The specified network adapter (<AdapterName>) in the Network Load Balancing configuration of the <NetworkName1> network is already used for Network Load Balancing of the <NetworkName2> network on this server. |
E_FPC_NO_ACCESS_PROPERTIES_FOR_THE_RULE |
FPC_ERR(0x354) |
0xC0040354 |
Access rule properties can only be configured for access rules, and not for other rules such as Web publishing and server publishing rules. |
E_FPC_NO_SERVER_PUBLISHING_PROPERTIES_FOR_THE_RULE |
FPC_ERR(0x355) |
0xC0040355 |
Server publishing properties can be configured only for server publishing rules. |
E_FPC_NO_WEB_PUBLISHING_PROPERTIES_FOR_THE_RULE |
FPC_ERR(0x356) |
0xC0040356 |
Web publishing properties can only be configured for Web publishing rules. |
E_FPC_BAD_ITEM_NAME |
FPC_ERR(0x357) |
0xC0040357 |
The <ObjectType1> referenced by <ObjectType2> <ObjectName> does not exist. |
E_FPC_AUTHENTICATION_SCHEME_FORWARD_ONLY |
FPC_ERR(0x358) |
0xC0040358 |
The authentication method selected cannot be used to authenticate Web publishing requests. Only outgoing Web requests can be authenticated using this method. |
E_FPC_AUTHENTICATION_SCHEME_REVERSE_ONLY |
FPC_ERR(0x359) |
0xC0040359 |
The authentication method selected cannot be used to authenticate outgoing Web requests. Only Web publishing rules can use this authentication method. |
E_FPC_AUTHENTICATION_DOESNT_PROVIDE_NAMESPACE |
FPC_ERR(0x35A) |
0xC004035A |
The selected user namespace is not supported by an authentication method. |
E_FPC_AUTHENTICATION_SCHEME_EXCLUSIVE |
FPC_ERR(0x35B) |
0xC004035B |
<AuthenticationMethod> authentication cannot be used together with any other authentication method. |
E_FPC_INVALID_DATE |
FPC_ERR(0x35E) |
0xC004035E |
The date is invalid. |
E_FPC_INVALID_DAYS_OF_WEEK |
FPC_ERR(0x35F) |
0xC004035F |
At least one day of the week must be specified. |
E_FPC_INVALID_DAY_OF_MONTH |
FPC_ERR(0x360) |
0xC0040360 |
The day of the month must be a number from 1 through 31. |
E_FPC_ADD_LINK_WITHOUT_PUBLISHING |
FPC_ERR(0x361) |
0xC0040361 |
To add a link to a report, publishing must be enabled for the report. |
E_FPC_INVALID_EMAIL_CONFIGURATION |
FPC_ERR(0x362) |
0xC0040362 |
To send an e-mail, specify a valid SMTP server name, From line, and To line (or Cc line). |
E_FPC_INVALID_PUBLISHING_CONFIGURATION |
FPC_ERR(0x363) |
0xC0040363 |
When publishing a report, you must specify a valid publishing folder. |
E_FPC_INVALID_CATEGORIES |
FPC_ERR(0x364) |
0xC0040364 |
The report must include one or more valid report categories. |
E_FPC_VPN_STATIC_ADDRESS_POOL_INVALID_RANGE |
FPC_ERR(0x365) |
0xC0040365 |
IP address ranges in the static address pool must be between 1.0.0.0 and 223.255.255.255. |
E_FPC_VPN_STATIC_ADDRESS_POOL_RANGE_TOO_SMALL |
FPC_ERR(0x366) |
0xC0040366 |
The IP address range is not valid. An IP address range must contain at least two IP addresses. |
E_FPC_VPN_MAXIMUM_CONNECTION |
FPC_ERR(0x367) |
0xC0040367 |
The value specified for the maximum number of connections must be between <LowerLimit> and <UpperLimit>. |
E_FPC_VPN_INVALID_IP |
FPC_ERR(0x368) |
0xC0040368 |
An IP address must be either 0.0.0.0 or belong to the range from 1.0.0.0 to 223.255.255.255. |
E_FPC_VPN_INVALID_VALUE_IPS |
FPC_ERR(0x369) |
0xC0040369 |
The IP address of the primary server must be specified, or the option of using a DHCP server must be selected. |
E_FPC_INVALID_SAVEASHTML_CALL |
FPC_ERR(0x36A) |
0xC004036A |
Only reports that have been generated successfully can be saved in HTML format. |
E_FPC_SERVER_PUBLISHING_HAS_NO_NETWORKS |
FPC_ERR(0x36B) |
0xC004036B |
At least one network or network set must be specified for the server publishing rule <RuleName>. |
E_FPC_VPN_NETWORK_LISTENER_LIST_EMPTY |
FPC_ERR(0x36C) |
0xC004036C |
At least one network must be selected for VPN client access. |
E_FPC_VPN_PROTOCOL_NOT_CHOSEN |
FPC_ERR(0x36D) |
0xC004036D |
At least one protocol must be selected for VPN remote client access. |
E_FPC_NO_FULL_ADMINISTRATORS_LEFT |
FPC_ERR(0x36E) |
0xC004036E |
ISA Server cannot delete the specified user. An ISA Server configuration must include at least one user who is delegated the role of ISA Server Full Administrator. |
E_FPC_PROTOCOL_RAW_CAN_NOT_HAVE_AN_APPLICATION_FILTER |
FPC_ERR(0x36F) |
0xC004036F |
A protocol definition that has a raw or ICMP protocol cannot have an application filter associated with it. |
E_FPC_PROTOCOL_ONLY_ONE_RAW_CONNECTION_ALLOWED |
FPC_ERR(0x370) |
0xC0040370 |
A protocol definition can have only one raw connection. |
E_FPC_NO_LOCALHOST_IN_NETWORK_RULE |
FPC_ERR(0x371) |
0xC0040371 |
The Local Host network cannot be included in a network rule. |
E_FPC_WEB_PUB_RULE_MUST_HAVE_SPECIFIC_PUBLIC_NAMES |
FPC_ERR(0x372) |
0xC0040372 |
The Web publishing rule <RuleName> can apply only to public names that do not include an asterisk (*). When link translation is enabled, the public name cannot include wildcard characters, and must be explicit. |
E_FPC_PROTOCOL_MUST_HAVE_PRIMARY_CONNECTION |
FPC_ERR(0x373) |
0xC0040373 |
The protocol definition must include at least one primary connection. |
E_FPC_PROTOCOL_ONLY_SAME_DIRECTION_CONNECTION_ALLOWED |
FPC_ERR(0x374) |
0xC0040374 |
Primary connections for the protocol definition must be configured for either outbound or inbound traffic, but not both. |
E_FPC_REPORT_RUN_REQUIRES_SCHEDULER_RUNNING |
FPC_ERR(0x375) |
0xC0040375 |
The Microsoft ISA Server Job Scheduler service must be running to create a report. |
E_FPC_WEB_PUBLISHING_RULE_NO_LISTENER |
FPC_ERR(0x376) |
0xC0040376 |
No Web listener is specified for the Web publishing rule <RuleName>. |
E_FPC_VPN_IPSEC_PRESHARED_SECRET_NOT_SUPPORTED |
FPC_ERR(0x377) |
0xC0040377 |
The use of a preshared IPsec key is not supported on this version of Windows. |
E_FPC_RADIUS_QUARANTINE_NOT_SUPPORTED |
FPC_ERR(0x378) |
0xC0040378 |
VPN quarantine based on RADIUS policies is not supported on this version of Windows. |
E_FPC_BACKUP_ROUTE_MISSING_SERVER_NAME |
FPC_ERR(0x379) |
0xC0040379 |
A server name must be specified in the backup route in the chaining rule <RuleName>. |
E_FPC_PRIMARY_ROUTE_MISSING_SERVER_NAME |
FPC_ERR(0x37A) |
0xC004037A |
A server name must be specified in the primary route in the chaining rule <RuleName>. |
E_FPC_WEB_BROWSER_CUSTOM_SCRIPT_MISSING |
FPC_ERR(0x37B) |
0xC004037B |
The URL or file name of a custom script for configuring Firewall client Web browsers must be specified for the <NetworkName> network. |
E_FPC_DIALUP_MISSING_USER_NAME |
FPC_ERR(0x37C) |
0xC004037C |
No user name was specified for the automatic dialing configuration. |
E_FPC_VPN_IPSEC_NETWORK_NOT_SUPPORTED |
FPC_ERR(0x37D) |
0xC004037D |
Retrieval of the IPsec VPN network settings is not supported for networks that do not have an IPsec connection. |
E_FPC_VPN_L2TPPPTP_NETWORK_NOT_SUPPORTED |
FPC_ERR(0x37E) |
0xC004037E |
Retrieval of the L2TP/PPTP VPN network settings is not supported for networks that do not have a VPN connection. |
E_FPC_VPN_INVALID_PRESHARED_SECRET |
FPC_ERR(0x37F) |
0xC004037F |
A non-empty string must be specified for the preshared secret. |
E_FPC_VPN_IPSEC_NETWORK_REMOTE_SERVER_INVALID |
FPC_ERR(0x380) |
0xC0040380 |
The name specified for the remote server is not a valid IP address. |
E_FPC_VPN_IPSEC_NETWORK_LOCAL_SERVER_INVALID |
FPC_ERR(0x381) |
0xC0040381 |
The name specified for the local server is not a valid IP address. |
E_FPC_ITEM_IN_USE_NOT_IN_COLLECTION |
FPC_ERR(0x382) |
0xC0040382 |
In ISA Server Standard Edition: The <ObjectType1> <ObjectName> cannot be deleted because it is used in <ObjectType2>. In ISA Server Enterprise Edition: The <ObjectType1> <ObjectName> cannot be deleted because it is used in <Scope> <ObjectType2>. |
E_FPC_ISASCHED_DOWN |
FPC_ERR(0x383) |
0xC0040383 |
The job cannot be started because the Microsoft ISA Server Job Scheduler service is not running. Check the status of the service. |
E_FPC_VPN_S2S_AUTHENTICATION_METHOD_EMPTY |
FPC_ERR(0x384) |
0xC0040384 |
At least one authentication method must be selected for site-to-site VPN access. |
E_FPC_WEB_PUB_RULE_NO_PUBLIC_NAMES |
FPC_ERR(0x385) |
0xC0040385 |
No public domain name or site name is specified for the Web publishing rule <RuleName>. |
E_FPC_VPN_NET_INVALID_CERTIFICATE_AUTHORITY |
FPC_ERR(0x386) |
0xC0040386 |
The certification authority name must contain between <LowerLimit> and <UpperLimit> characters. |
E_FPC_VPN_NET_INVALID_PRESHARED_KEY |
FPC_ERR(0x387) |
0xC0040387 |
The preshared key must contain between <LowerLimit> and <UpperLimit> characters. |
E_FPC_SERVER_NOT_JOINED_TO_DOMAIN |
FPC_ERR(0x388) |
0xC0040388 |
The server is not joined to the domain. |
E_FPC_DENY_SRV_PUB_NOT_ALLOWED |
FPC_ERR(0x389) |
0xC0040389 |
Server publishing rules cannot be configured as "deny" rules. By design, server publishing rules allow access to specified servers for which access is denied by default. |
E_FPC_VPN_NET_CONFLICTING_AUTH_PROTOCOLS |
FPC_ERR(0x38A) |
0xC004038A |
For VPN site-to-site authentication, you can specify EAP authentication, or any combination of the alternative authentication protocols (PAP, SPAP, CHAP, MS-CHAP, MS-CHAP v2). EAP cannot be enabled together with any other authentication protocol. |
E_FPC_ISASTG_SERVICE_UNAVAILABLE |
FPC_ERR(0x38B) |
0xC004038B |
The Microsoft ISA Server Storage service is unavailable. |
E_NO_SITE_OR_DOMAIN_DEFINED |
FPC_ERR(0x38C) |
0xC004038C |
The URL specified does not contain a domain or site name. If you want to specify a folder, the folder prefix "/" must come after the domain name. |
E_PORT_NUMBER_IN_WEB_SITE_NAME |
FPC_ERR(0x38D) |
0xC004038D |
The Web server name cannot contain a port number. The port numbers to be used for redirecting requests to this Web server can be specified in the HTTPRedirectPort and SSLRedirectPort properties for the rule. |
E_DISCONNECT_CONTAINING_ARRAY |
FPC_ERR(0x38E) |
0xC004038E |
The server cannot be disconnected from the containing array. |
E_FPC_MSDE_NOT_INSTALLED |
FPC_ERR(0x38F) |
0xC004038F |
The MSDE feature is currently not installed. To install MSDE, in the Add/Remove Programs, select Microsoft ISA Server 2006 and click Change. Then, in the Microsoft ISA Server 2006 Installation Wizard, use the Modify option to add MSDE to the installation. |
E_FPC_LISTENER_WITH_SAME_IP_AND_PORT_IN_USE |
FPC_ERR(0x390) |
0xC0040390 |
A Web listener configured to listen on the same IP address and port is already being used by the rule <RuleName>. |
E_FPC_2_LISTENERS_WITH_SAME_IP_AND_PORT_IN_USE |
FPC_ERR(0x391) |
0xC0040391 |
The Web listeners used in the rule <RuleName1> and in the rule <RuleName2> specify identical IP addresses and ports. Web listener IP addresses and ports used by different rules cannot overlap. |
E_FPC_INVALID_PUBLISHING_CREDENTIALS_CONFIGURATION |
FPC_ERR(0x392) |
0xC0040392 |
The user account does not have the required permissions to publish the report. |
E_FPC_UPLOAD_NEW_CONFIGURATION |
FPC_ERR(0x393) |
0xC0040393 |
Some configuration changes were not applied. For more details, see Windows Event Viewer. |
E_FPC_INVALID_LOG_DIRECTORY_AND_TYPE |
FPC_ERR(0x394) |
0xC0040394 |
The full path option is selected for the log file path, but the log directory is specified by an empty string. |
E_FPC_PROTOCOL_NOT_SERVER_PROTOCOL |
FPC_ERR(0x395) |
0xC0040395 |
The specified protocol is not an inbound (server) protocol and cannot be used in the server publishing rule <RuleName>. |
E_FPC_SSL_MUST_HAVE_CERTIFICATE |
FPC_ERR(0x396) |
0xC0040396 |
When SSL) is enabled and an SSL port specified, you must specify a certificate for SSL authentication. |
E_FPC_CORRUPTED_ITEM_OBJECT_ATTRIBUTE |
FPC_ERR(0x397) |
0xC0040397 |
Attribute <AttributeName> of object type <ObjectType> is corrupted. You should delete the object owner <OwnerName> of type <Type>, fix the corrupted attribute, or import a valid configuration. |
E_FPC_CORRUPTED_OBJECT_ATTRIBUTE |
FPC_ERR(0x398) |
0xC0040398 |
Attribute <AttributeName> of object type <ObjectType> is corrupted. You should delete the object, fix the corrupted attribute, or import a valid configuration. |
E_FPC_XML_VERSION_MISMATCH |
FPC_ERR(0x399) |
0xC0040399 |
The XML file cannot be imported to this version of ISA Server. Install the latest version of ISA Server, including hot fixes and patches, and then try importing the XML file again. |
E_FPC_CANNOT_IMPORT_SYSTEM_POLICY_RULE |
FPC_ERR(0x39A) |
0xC004039A |
System policy rules cannot be imported individually. |
E_FPC_CANNOT_SAVE_CACHEDRIVE_WHEN_ISACTRL_SERVICE_DOWN |
FPC_ERR(0x39C) |
0xC004039C |
The ISA Server Control service is currently stopped. As a result, the changes made to the configuration cannot be saved. To save the changes, you must either start the ISA Server Control service, or disable the changed cache drive setting by resetting it back to 0. |
E_FPC_NOT_SUPPORTED_IN_ARRAY_SCOPE |
FPC_ERR(0x39D) |
0xC004039D |
In ISA Server Enterprise Edition, the property or method <Name> is not supported in array scope. |
E_FPC_NOT_SUPPORTED_IN_ENTERPRISE_SCOPE |
FPC_ERR(0x39E) |
0xC004039E |
In ISA Server Enterprise Edition, the property or method <Name> is not supported in enterprise scope. |
E_FPC_NOT_SUPPORTED_IN_SE_MODE |
FPC_ERR(0x39F) |
0xC004039F |
the property or method <Name> is not supported. |
E_FPC_NOT_SUPPORTED_IN_EE_CENTRAL_MODE |
FPC_ERR(0x3A0) |
0xC00403A0 |
In ISA Server Enterprise Edition, the property or method <Name> is not supported when a Configuration Storage server is used. |
E_FPC_NOT_SUPPORTED_IN_EE_LOCAL_MODE |
FPC_ERR(0x3A1) |
0xC00403A1 |
The property or method <Name> is not supported when the configuration is stored only on the local computer. |
E_FPC_ENTERPRISE_ITEM_CANNOT_REFERENCE_ARRAY_ITEM |
FPC_ERR(0x3A2) |
0xC00403A2 |
In ISA Server Enterprise Edition, an enterprise item cannot reference an array-level item. |
E_FPC_XML_IMPORT_ARRAY_OR_POLICY_NOT_IN_XML |
FPC_ERR(0x3A3) |
0xC00403A3 |
The exported enterprise XML file does not include data for the importing object. The file cannot be imported into this object. |
E_FPC_XML_IMPORT_FROM_NON_VALID_XML |
FPC_ERR(0x3A4) |
0xC00403A4 |
The XML file cannot be imported into this object. Verify that the exported file is valid and that it contains an appropriate object type. |
E_FPC_XML_IMPORT_CROSS_SCOPE |
FPC_ERR(0x3A5) |
0xC00403A5 |
The file cannot be imported. The file contains a <Scope1> <ObjectType1>, which cannot be imported into a <Scope2> <ObjectType2>. |
E_FPC_NOT_CONNECTED_TO_ENTERPRISE |
FPC_ERR(0x3A6) |
0xC00403A6 |
In ISA Server Enterprise Edition, the property or method <Name> is not supported when the ISA Server computer is not connected to a Configuration Storage server. |
E_FPC_CARP_IS_NOT_SUPPORTED_IN_WEB_PUBLISHING |
FPC_ERR(0x3A7) |
0xC00403A7 |
In ISA Server Enterprise Edition, CARP is not supported in a Web publishing scenario. |
E_FPC_PUBLISHING_RULES_NOT_SUPPORTED_IN_ENTERPRISE_POLICY |
FPC_ERR(0x3A9) |
0xC00403A9 |
In ISA Server Enterprise Edition, the publishing rules are not supported in an enterprise policy. |
E_FPC_ALLOW_POLICY_RULES_IN_ARRAY_POLICY_BLOCKED |
FPC_ERR(0x3AA) |
0xC00403AA |
In ISA Server Enterprise Edition, the access rules that allow traffic cannot be added to the array's Firewall policy. |
E_FPC_DENY_POLICY_RULES_IN_ARRAY_POLICY_BLOCKED |
FPC_ERR(0x3AB) |
0xC00403AB |
In ISA Server Enterprise Edition, the access rules that deny traffic cannot be added to the array's Firewall policy. |
E_FPC_PUBLISHING_POLICY_RULES_IN_ARRAY_POLICY_BLOCKED |
FPC_ERR(0x3AC) |
0xC00403AC |
In ISA Server Enterprise Edition, server publishing rules or Web publishing rules cannot be added to the array's Firewall policy. |
E_FPC_POLICY_RULES_EXISTS_IN_ARRAY_POLICY |
FPC_ERR(0x3AD) |
0xC00403AD |
In ISA Server Enterprise Edition, the array policy placeholder cannot be disabled because the array <Name> contains policy rules. |
E_FPC_DENY_POLICY_RULES_EXISTS_IN_ARRAY_POLICY |
FPC_ERR(0x3AE) |
0xC00403AE |
In ISA Server Enterprise Edition, deny rules cannot be blocked for this array because at least one access rule that denies traffic is already defined for this array. |
E_FPC_ALLOW_POLICY_RULES_EXISTS_IN_ARRAY_POLICY |
FPC_ERR(0x3AF) |
0xC00403AF |
In ISA Server Enterprise Edition, allow rules cannot be blocked for this array because at least one access rule that allows traffic is already defined for this array. |
E_FPC_PUBLISHING_POLICY_RULES_EXISTS_IN_ARRAY_POLICY |
FPC_ERR(0x3B0) |
0xC00403B0 |
In ISA Server Enterprise Edition, publishing rules cannot be blocked for this array because at least one publishing rule is already defined for this array. |
E_FPC_NOT_SUPPORTED_FOR_ARRAY_POLICY_PLACE_HOLDER |
FPC_ERR(0x3B1) |
0xC00403B1 |
In ISA Server Enterprise Edition, the property or method is not supported for an array policy placeholder rule. |
E_FPC_ENTERPRISE_NETWORK_ALREADY_INCLUDED |
FPC_ERR(0x3B4) |
0xC00403B4 |
In ISA Server Enterprise Edition, the selected enterprise network <EnterpriseNetworkName> is already included in the array network <ArrayNetworkName>. An enterprise network cannot be included in more than one array network. |
E_FPC_ENTERPRISE_NETWORK_INCLUDED_IN_TWO_NETWORKS |
FPC_ERR(0x3B5) |
0xC00403B5 |
In ISA Server Enterprise Edition, the <EnterpriseNetworkName> enterprise network is currently included in both the <ArrayNetworkName1> and <ArrayNetworkName2> array networks. An enterprise network cannot be included in more than one array network. |
E_FPC_SE_MIGRATE_ONLY_SUPPORTED_FOR_ARRAY |
FPC_ERR(0x3B6) |
0xC00403B6 |
In ISA Server Enterprise Edition, the file being imported can only be imported to an array node. |
E_FPC_SE_MIGRATE_ONLY_SUPPORTED_ONE_SERVER |
FPC_ERR(0x3B7) |
0xC00403B7 |
In ISA Server Enterprise Edition, the file being imported can only be imported into an array that has one server. |
E_FPC_SE_MIGRATE_ONLY_SUPPORTED_MERGE |
FPC_ERR(0x3B8) |
0xC00403B8 |
In ISA Server Enterprise Edition, the selected file cannot be used to restore the configuration. It can only be used for importing. |
E_FPC_NLB_NETWORK_TYPE_MUST_BE_ADAPTER |
FPC_ERR(0x3B9) |
0xC00403B9 |
In ISA Server Enterprise Edition, Network Load Balancing can be enabled on a network only if the connection to the network is configured to be through a network adapter. |
E_FPC_CANNOT_REMOVE_LAST_SERVER_FROM_ARRAY |
FPC_ERR(0x3BA) |
0xC00403BA |
In ISA Server Enterprise Edition, removing a server from an array with a single server is not allowed. Either uninstall the server or delete the entire array. |
E_FPC_ENT_NETWORK_IN_ARRAY_NETWORK_SET_NOT_ALLOWED |
FPC_ERR(0x3BB) |
0xC00403BB |
In ISA Server Enterprise Edition, array network sets cannot include enterprise networks. |
E_FPC_ENT_NETWORK_SET_IN_LISTENER_NOT_ALLOWED |
FPC_ERR(0x3BC) |
0xC00403BC |
In ISA Server Enterprise Edition, a publishing rule cannot listen on an enterprise network set. |
E_FPC_NO_NLB_CLUSTER_CONFIG_FOR_THE_NETWORK |
FPC_ERR(0x3BD) |
0xC00403BD |
In ISA Server Enterprise Edition, the Network Load Balancing cluster properties can be configured only for networks whose connection type specifies a connection through a network adapter. |
E_FPC_INVALID_NLB_CLUSTER_MASK |
FPC_ERR(0x3BE) |
0xC00403BE |
In ISA Server Enterprise Edition, the Network Load Balancing cluster IP mask must not be 255.255.255.255. |
E_FPC_PARENT_ARRAY_NOT_CONTAINING_ARRAY |
FPC_ERR(0x3BF) |
0xC00403BF |
In ISA Server Enterprise Edition, application and Web filters can only be added to and removed from an array in which this server is located. |
E_FPC_INVALID_CONFIGURATION |
FPC_ERR(0x3C0) |
0xC00403C0 |
In ISA Server Enterprise Edition, the storage configuration agent was unable to upload the configuration to the service. |
E_FPC_STORAGE_SERVER_INACCESSIBLE |
FPC_ERR(0x3C1) |
0xC00403C1 |
In ISA Server Enterprise Edition, the storage configuration agent was unable to access the Configuration Storage server. |
E_FPC_ITEM_IN_USE_NOT_IN_ARRAY_COLLECTION |
FPC_ERR(0x3C2) |
0xC00403C2 |
In ISA Server Enterprise Edition, the <ObjectType1> <ObjectName> cannot be deleted because it is used in a <ObjectType2> of the <ArrayName> array. |
E_FPC_ITEM_IN_USE_NOT_IN_POLICY_COLLECTION |
FPC_ERR(0x3C3) |
0xC00403C3 |
In ISA Server Enterprise Edition, the <ObjectType1> <ObjectName> cannot be deleted because it is used in a <ObjectType2> of the enterprise policy <PolicyName>. |
E_FPC_ITEM_IN_USE_IN_ARRAY |
FPC_ERR(0x3C4) |
0xC00403C4 |
In ISA Server Enterprise Edition, the <ObjectType1> <ObjectName1> cannot be deleted because it is used in the <ObjectType2> <ObjectName2> of the <ArrayName> array. |
E_FPC_ITEM_IN_USE_IN_POLICY |
FPC_ERR(0x3C5) |
0xC00403C5 |
In ISA Server Enterprise Edition, the <ObjectType1> <ObjectName1> cannot be deleted because it is used in the <ObjectType2> <ObjectName2> of the enterprise policy <PolicyName>. |
E_FPC_VPN_S2S_NO_ASSIGNED_SERVER |
FPC_ERR(0x3C6) |
0xC00403C6 |
In ISA Server Enterprise Edition, the ISA Server computer specified as the connection owner is not configured for VPN site-to-site network <NetworkName>. |
E_FPC_IP_RANGE_ENTRY_INTERSECT_WITH_STATIC_POOL |
FPC_ERR(0x3C7) |
0xC00403C7 |
In ISA Server Enterprise Edition, the VPN configuration static address pool for the server <ServerName> already includes IP addresses in the range <LowerLimit>–<UpperLimit>. New IP ranges cannot overlap existing ranges in the current static address pool. |
E_FPC_NO_ENTERPRISE_NETWORK_IN_PREDEFINED_ARRAY_NETWORK |
FPC_ERR(0x3C8) |
0xC00403C8 |
In ISA Server Enterprise Edition, a predefined array network cannot include an enterprise network. |
E_FPC_NO_PREDEFINED_ENTERPRISE_NETWORK_IN_ARRAY_NETWORK |
FPC_ERR(0x3C9) |
0xC00403C9 |
In ISA Server Enterprise Edition, an array network cannot include a predefined enterprise network. |
E_FPC_DEPRECATED |
FPC_ERR(0x3CA) |
0xC00403CA |
In ISA Server Enterprise Edition, the property or method <Name> is deprecated and should not be used. |
E_FPC_DHCP_NOT_SUPPORTED_ON_MULTI_SERVER_ARRAYS |
FPC_ERR(0x3CB) |
0xC00403CB |
In ISA Server Enterprise Edition, DHCP cannot be used to assign IP addresses to VPN clients or remote endpoint servers on multiple-server arrays. |
E_FPC_XML_MISMATCH_IMPORT_OBJECT_UPGRADE_ARRAY |
FPC_ERR(0x3CC) |
0xC00403CC |
In ISA Server Enterprise Edition, the file cannot be imported. It is an upgrade file of a server and therefore can only be imported into an array object. |
E_FPC_XML_MISMATCH_IMPORT_OBJECT_UPGRADE_ROOT |
FPC_ERR(0x3CD) |
0xC00403CD |
In ISA Server Enterprise Edition, the file cannot be imported. It is an upgrade file of an enterprise and therefore can only be imported into a root (enterprise) object. |
S_FPC_LOGGING_RESUMED |
FPC_WRN(0x3CE) |
0x800403CE |
In ISA Server Enterprise Edition, logging has been resumed following a previous failure. |
E_FPC_DEST_NOT_IP_MASK |
FPC_ERR(0x3CF) |
0xC00403CF |
In ISA Server Enterprise Edition, the lIP mask specified for the object is invalid. |
S_FPC_TIME_SKEW |
FPC_WRN(0x3D0) |
0x800403D0 |
In ISA Server Enterprise Edition, the time setting of at least one server in the array is not synchronized with the rest of the array. As a result, the records of some servers may be delayed. Synchronizing the time settings for array members will resolve this problem. |
E_FPC_IMPORT_ONLY_SUPPORTED_FOR_ROOT |
FPC_ERR(0x3D1) |
0xC00403D1 |
The file that you are importing is from an older build of ISA Server. Importing such files is only supported if the file was exported from the root node and can only be imported to the root node. |
E_FPC_INVALID_SPOOF_DETECTION_MODE |
FPC_ERR(0x3D2) |
0xC00403D2 |
The spoof detection mode is not valid for this network. |
E_FPC_CAN_NOT_CHANGE_SPOOF_DETECTION_MODE |
FPC_ERR(0x3D3) |
0xC00403D3 |
The spoof detection mode cannot be modified for this network. |
E_FPC_ARRAY_STORAGE_SERVER_INACCESSIBLE |
FPC_ERR(0x3D5) |
0xC00403D5 |
In ISA Server Enterprise Edition, ISA Server Management was unable to access the Configuration Storage server to which the array members are connected. |
E_FPC_REPLICATION_ERROR |
FPC_ERR(0x3D6) |
0xC00403D6 |
In ISA Server Enterprise Edition, a replication error occurred between the Configuration Storage server to which ISA Server Management is connected and the Configuration Storage server to which the array members are connected. |
E_FPC_IP_IS_NOT_SUPPORTED_AS_CONFIGURATION_STORAGE_NAME |
FPC_ERR(0x3D7) |
0xC00403D7 |
In ISA Server Enterprise Edition, using an IP address for specifying the Configuration Storage server is not supported. Use the fully qualified domain name (FQDN) instead. |
E_FPC_MACHINE_ACCOUNT_COULD_NOT_BE_RESOLVED |
FPC_ERR(0x3D8) |
0xC00403D8 |
In ISA Server Enterprise Edition, the Server service on the Configuration Storage server could not be accessed. This service is required for saving restored server data. Verify that the service is running. Alternatively, restore the configuration on the Configuration Storage server locally. |
E_FPC_INVALID_PARAMETER_FOR_SE |
FPC_ERR(0x3D9) |
0xC00403D9 |
In ISA Server Standard Edition, the value specified for the parameter <ParameterName> is not valid. |
E_FPC_WEB_PUBLISHING_RULE_NO_SERVERFARM |
FPC_ERR(0x3DA) |
0xC00403DA |
No server farm is specified for the Web publishing rule <RuleName>. |
E_FPC_SERVERFARM_NO_SERVERS |
FPC_ERR(0x3DB) |
0xC00403DB |
No published servers are specified for the server farm <ServerFarmName>. |
E_FPC_XML_ISA2000_UPGRADE_NOT_SUPPORTED |
FPC_ERR(0x3DC) |
0xC00403DC |
The configuration could not be imported. Importing an ISA Server 2000 configuration into ISA Server 2006 is not supported. |
E_FPC_FBA_NOT_SUPPORTED_IN_FORWARD_PROXY |
FPC_ERR(0x3DD) |
0xC00403DD |
The property or method is not supported for the Web listener properties of a network. |
E_FPC_ONLY_ONE_CODE_PAGE_SUPPORTED |
FPC_ERR(0x3DE) |
0xC00403DE |
An attempt was made to specify more than one code page in a Web publishing rule. |
E_FPC_CODE_PAGE_NOT_NUMERIC |
FPC_ERR(0x3DF) |
0xC00403DF |
The string supplied to specify the code page does not represent a numeric value. |
E_FPC_URL_WITHOUT_PROTOCOL |
FPC_ERR(0x3E0) |
0xC00403E0 |
An attempt was made to specify a URL without a protocol in a link translation mapping. |
E_FPC_URL_TOO_LONG |
FPC_ERR(0x3E1) |
0xC00403E1 |
An attempt was made to specify a URL that is longer than 2,057 bytes in a link translation mapping. |
E_FPC_EMPTY_PATH_MAPPINGS |
FPC_ERR(0x3E2) |
0xC00403E2 |
No path mappings are defined in the path mappings collection for the Web publishing rule. |
E_LINK_TRANSLATIONS_NOT_APPLIED_YET |
FPC_ERR(0x3E3) |
0xC00403E3 |
The configuration stored on the ISA Server computer does not yet contain the link translation configuration for the specified rule. |
E_ANY_PUBLIC_NAME_SELECTED |
FPC_ERR(0x3E4) |
0xC00403E4 |
A link translation dictionary cannot be generated for a rule that applies to any public name. |
E_FPC_CODE_PAGE_NOT_SUPPORTED |
FPC_ERR(0x3E5) |
0xC00403E5 |
Link translation does not support the specified code page. |
E_FPC_DEPRECATED_CONFIG_GROUP |
FPC_ERR(0x3E6) |
0xC00403E6 |
The configuration group of system policy rules specified is no longer supported. |
E_DOMAIN_NAME_CONTAINS_PORT_NUMBER |
FPC_ERR(0x3E7) |
0xC00403E7 |
A port number is appended to the domain name specified. |
E_FPC_ADD_VENDOR_SYSTEM_POLICY_RULE_NOT_IN_VENDOR_MODE |
FPC_ERR(0x3E8) |
0xC00403E8 |
An attempt was made to add a new vendor system policy rule when the the administration COM object hierarchy is not in vendor mode. |
E_FPC_REMOVE_VENDOR_SYSTEM_POLICY_RULE_NOT_IN_VENDOR_MODE |
FPC_ERR(0x3E9) |
0xC00403E9 |
An attempt was made to remove a vendor system policy rule when the administration COM object hierarchy is not in vendor mode. |
E_FPC_SERVICE_INACCESSIBLE |
FPC_ERR(0x3EC) |
0xC00403EC |
The Microsoft ISA Server Control service could not be accessed. |
E_FPC_INCOMPATIBLE_AUTHENTICATION_AND_DELEGATION_SCHEMES |
FPC_ERR(0x3ED) |
0xC00403ED |
The authentication settings of the Web listener used in the rule %1 are not compatible with the type of credentials delegation configured for this rule. |
E_FPC_MAIL_LOG_NOT_SUPPORTED |
FPC_ERR(0x3EE) |
0xC00403EE |
SMTP Message Screener logging is no longer supported in this version of ISA Server. |
E_FPC_URL_NOT_TRANSLATABLE_TO_ACP |
FPC_ERR(0x3EF) |
0xC00403EF |
The URL for redirecting links to unpublished sites contains one or more non-ANSI characters. |
E_FPC_HTTPS_REDIRECT_REQUIRES_SSL |
FPC_ERR(0x3F0) |
0xC00403F0 |
HTTP requests cannot be redirected as HTTPS requests if no SSL port is configured or if there is an SSL accelerator in front of the ISA Server computer. |
E_FPC_SSL_CLIENT_CERTIFICATE_RESTRICTION_ALLOWS_ANY_CERTIFICATE |
FPC_ERR(0x3F1) |
0xC00403F1 |
An SSL client certificate restriction allows any certificate. |
E_FPC_SSL_CLIENT_CERTIFICATE_RESTRICTION_ON_VALUE_OF_EHNANCED_KEY_USAGE |
FPC_ERR(0x3F2) |
0xC00403F2 |
An SSL client certificate restriction requires the Enhanced Key Usage field to have a value containing a specified string. |
E_FPC_CLIENT_CERT_TRUST_LIST_NOT_SUPPORTED_IN_FORWARD_PROXY |
FPC_ERR(0x3F3) |
0xC00403F3 |
An SSL client certificate trust list cannot be defined for the Web listener for outgoing requests from a network. |
E_FPC_CERT_RESTRICTIONS_NOT_SUPPORTED_IN_FORWARD_PROXY |
FPC_ERR(0x3F4) |
0xC00403F4 |
SSL client certificate restrictions cannot be defined for the Web listener for outgoing requests from a network. |
E_FPC_NLB_VIPS_MUST_BELONG_TO_SAME_SUBNET |
FPC_ERR(0x3F5) |
0xC00403F5 |
One or more of the additional virtual IP addresses added to the Network Load Balancing cluster do not belong to the same subnet as the first virtual IP address. |
E_FPC_VPN_REMOTE_SITE_DIPS_NOT_SUPPORTED |
FPC_ERR(0x3F6) |
0xC00403F6 |
The set of dedicated IP address ranges for remote VPN servers cannot be retrieved for networks that are not linked by VPN connections with the L2TP or PPTP protocol. |
E_FPC_INCOMPATIBLE_ARRAY_VERSION |
FPC_ERR(0x3F7) |
0xC00403F7 |
The array could not be created on this Configuration Storage server because the stored configuration only allows adding arrays from newer versions of the product. |
E_FPC_CURRENT_MGMT_NOT_ALLOWED |
FPC_ERR(0x3F8) |
0xC00403F8 |
The enterprise configuration is from a newer version of ISA Server than the installed version of ISA Server Management. You cannot manage this enterprise using this version of ISA Server Management. To manage the enterprise, you must use a newer version of ISA Server Management. |
E_FPC_NO_ADAPTERS_INFORMATION_EXIST |
FPC_ERR(0x3F9) |
0xC00403F9 |
Network adapter details for the server <ServerName> are currently unavailable. Verify that network adapters for this server are connected. |
E_FPC_PUBLIC_NAME_INVALID_FOR_SSO |
FPC_ERR(0x3FA) |
0xC00403FA |
The server public name <ServerName> used in the rule <RuleName> contains one or more illegal characters. |
E_FPC_SERVICE_NOT_SUPPORTED_BY_USER_SET |
FPC_ERR(0x3FB) |
0xC00403FB |
A required service is not supported by one or more of the authentication schemes used by the user set. |
E_FPC_PRIMARY_VIP_CHANGED |
FPC_ERR(0x3FC) |
0xC00403FC |
The primary virtual IP address for the <NetworkName> network cannot be changed because additional virtual IP addresses are configured for this network. |
E_FPC_WEB_PUB_RULE_SSL_REQUIRE_SECURE_CHANNEL_DEPRECATED_VALUES |
FPC_ERR(0x3FD) |
0xC00403FD |
The enumeration values fpcSSLRequireSecureChannel and fpcSSLRequireBoth for the SSLRequireSecureChannel property of a Web publishing rule are deprecated. |