Event ID 105 — Windows NT Token-Based Application – Miscellaneous

Event ID 105 — Windows NT Token-Based Application – Miscellaneous

Updated: February 27, 2008

Applies To: Windows Server 2008

Monitor miscellaneous authentication requests that are made to the Windows token-based agent.

Event Details

Product: Windows Operating System
ID: 105
Source: Microsoft-Windows-ADFS
Version: 6.0
Symbolic Name: WSEXT_INITIAL_REDIR_FAILURE
Message: The AD FS Web Agent for Windows NT token-based applications encountered a serious error. The Web agent was not able to redirect the unauthenticated client to the Federation Service. User Action If this error persists, enable the AD FS troubleshooting log.

Resolve
Enable the AD FS troubleshooting log

If this error persists, enable the Active Directory Federation Services (AD FS) troubleshooting log.

To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.

To enable the AD FS troubleshooting log:

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

  1. Click Start, click Run, type regedit, and then click OK.
  2. Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ifssvc\ Parameters
  3. Right-click Parameters, click New, and then click DWORD Value.
  4. In the New Value name box, type ADFSEvent, and then press ENTER.
  5. Double-click the new entry, and then, in Value data, provide a value for one of the following levels (or add values to configure multiple levels) and then click OK:
    • Warning: 0x01
    • Information: 0x02
    • Success: 0x04
    • Failure: 0x08

For more information, see Configure event logging for a Windows NT token-based application (http://go.microsoft.com/fwlink/?LinkId=94741).

Verify

Verify that you can access the Active Directory Federation Services (AD FS)-enabled application from a client browser and that the resource can be accessed with the appropriate authorization.

If you cannot access the application successfully, verify that the Windows token-based agent is configured with correct URL values and that all configuration parameters contain valid values.

To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.

To verify that the Windows token-based agent is configured with correct values:

  1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the console tree, click YourComputerName(local computer).
  3. In the console tree, double-click Sites, and then click YourWebSiteName.
  4. In the center pane, double-click Authentication, highlight AD FS Windows Token-Based Agent, and then in the Actions pane click Edit.
  5. In the AD FS Windows Token-Based Agent dialog box, confirm that the Enable AD FS Web Agent check box is selected.
  6. Make sure that the following values are valid, and then click OK.
    • Cookie path
    • Cookie domain
    • Return URL

Related Management Information

Windows NT Token-Based Application – Miscellaneous

Active Directory Federation Services

Related:

Event ID 105 — Remote Desktop IP Virtualization IP Address Assignment

Event ID 105 — Remote Desktop IP Virtualization IP Address Assignment

Published: January 8, 2010

Applies To: Windows Server 2008 R2

Remote Desktop IP Virtualization allows you to assign a unique IP address to a user session or on a per program basis. You must have a DHCP scope configured with enough IP addresses for all sessions or programs on an RD Session Host server.

Event Details

Product: Windows Operating System
ID: 105
Source: Microsoft-Windows-TerminalServices-TSAppSrv-TSVIP
Version: 6.1
Symbolic Name: EVENT_ERROR_LEASESESSIONVIP
Message: Remote Desktop IP Virtualization could not acquire an IP address for session ID %1. Error code: %2

Resolve
Check connectivity to the DHCP server and ensure enough IP addresses are available

To resolve this issue, identify and fix any issues with your DHCP server by doing the following:

  • Determine if there is a network connectivity problem by using the ping command.
  • Ensure that enough IP addresses are available within the DHCP scope.
  • Perform additional troubleshooting steps, if necessary, to help identify the cause of the problem.

To perform these tasks, refer to the following sections.

Note:  The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.

To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

Determine if there is a network connectivity problem

To determine if there is a network connectivity problem between the RD Session Host server and the DHCP server:

  1. On the RD Session Host server, click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the DHCP server (for example, server1.contoso.com), and then press ENTER.

    If the ping was successful, you will receive a reply similar to the following:

    Reply from IP_address: bytes=32 time=3ms TTL=59

    Reply from IP_address: bytes=32 time=20ms TTL=59

    Reply from IP_address: bytes=32 time=3ms TTL=59

    Reply from IP_address: bytes=32 time=6ms TTL=59

  3. At the command prompt, type ping IP_address, where IP_address is the IP address of the DHCP server, and then press ENTER.

If you can successfully ping the DHCP server by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.

If you cannot successfully ping the DHCP server by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.

Ensure that enough IP addresses are available within the DHCP scope

To ensure that enough IP addresses are available within the DHCP scope:

  1. On the DHCP server, click Start, point to Administrative Tools, and then click DHCP.
  2. Expand the DHCP server, expand IPv4, and then click Address Leases.
  3. Ensure that the amount of DHCP leases does not exceed the amount of IP addresses available within the DHCP scope.

Perform additional troubleshooting steps

The following are some additional troubleshooting steps that you can perform to help identify the root cause of the problem:

  • Ensure that the DHCP server and the RD Session Host server are located on the same subnet.

Verify

To verify that an IP address has been assigned to a session or a specified program, you must use Event Viewer and confirm that Event 103 in the Microsoft-Windows-TerminalServices-TSAppSrv-TSVIP event source was written to the System event log.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To confirm that Event 103 was written to the System event log:

  1. On the RD Session Host server, open Event Viewer. To open Event Viewer, click Start, point to Administrative Tools, and then click Event Viewer.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  3. In the left pane, expand Windows Logs, and then click System.
  4. Look for an event with a Source of Microsoft-Windows-TerminalServices-TSAppSrv-TSVIP and an Event ID of 103. This event indicates that an IP address was assigned to either a session or program.

Related Management Information

Remote Desktop IP Virtualization IP Address Assignment

Remote Desktop Services

Related:

Machine Check Event reported is a fatal error reported to CPU %1.

Details
Product: Windows Operating System
Event ID: 105
Source: WMIxWDM
Version: 5.2
Symbolic Name: MCA_ERROR_UNKNOWN
Message: Machine Check Event reported is a fatal error reported to CPU %1.
   
Explanation

A hardware error caused the hardware to fail. The type of error cannot be determined because the error record returned by the firmware is not in the required format. For detailed information about the hardware that caused the problem, refer to the event log.

   
User Action

Contact your hardware support provider.

Related:

Unclosed quotation mark before the character string ‘%.*ls’.

Details
Product: SQL Server
Event ID: 105
Source: MSSQLServer
Version: 8.0
Component: SQL Engine
Message: Unclosed quotation mark before the character string ‘%.*ls’.
   
Explanation
This error occurs when a Transact-SQL statement contains mismatched single or double quotes. The SET QUOTED_IDENTIFIER setting will determine which combinations of single and double quotations marks are valid. For more information about SET QUOTED_IDENTIFIER, see “SET QUOTED_IDENTIFIER” in Books Online.

Each single or double quotation mark used to mark the beginning of a literal string must have a corresponding quotation mark of the same type to mark the end of the literal string. A single quotation mark cannot be paired with a double quotation mark to delimit a single literal string.

Quotation marks that are part of the literal string are handled differently. If a single quotation mark (‘) is part of the literal string, it can be represented by two single quotation marks (”). If a literal string is delimited by double quotation marks and SET QUOTED_IDENTIFIER is OFF, the string can contain embedded single quotation marks, such as apostrophes. If a literal string is delimited by single quotation marks and SET QUOTED_IDENTIFIER is either ON or OFF, the string can contain embedded double quotation marks.

If you do not place the correct type and number of quotation marks in each place in your code, SQL Server will return the above error, possibly along with an “Incorrect syntax near %” error.

For more information about managing quotation marks in code, see these Microsoft Knowledge Base articles:
311023 and 311021.

For examples of quotation mark usage, see “SET QUOTED_IDENTIFIER” in Books Online.

   
User Action
  • Check whether QUOTED_IDENTIFIER is true for your current session with this Transact-SQL command:
    SELECT SESSIONPROPERTY(‘QUOTED_IDENTIFIER’)
    Depending on your needs, you may need to change the setting with SET QUOTED_IDENTIFIER ON/OFF.
  • Verify that each quotation mark intended to delimit a string has a matching quotation mark of the same type.
  • Verify that each quotation mark that is part of the literal string is represented by two of the same type of quotation mark.

Related:

The server was unable to register the administration tool discovery information. The administration tool may not be able to see this server. The data is the error code.For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.

Details
Product: Exchange
Event ID: 105
Source: POP3SVC
Version: 6.5.0000.0
Message: The server was unable to register the administration tool discovery information. The administration tool may not be able to see this server. The data is the error code.For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp.
   
Explanation
This error usually indicates a communication problem between Exchange and Active Directory. This can happen even if Exchange is installed on a Domain Controller.

  • NetBIOS may have been turned off on the Network Card. This may be the case

    on dual-homed machines.

  • The Network cable may have been removed from the Network Card. This will

    also cause other errors in DNS, etc..

  • The Exchange server may not be able to communicate with Active Directory for

    some reason.

   
User Action
  • Enable NetBIOS on the Network Card.
  • Check the IP Configuration on the Exchange server to ensure that the

    correct DNS Server has been listed.

  • Ensure that Exchange is connected to the network and can communicate with Active Directory properly.

Related:

An MTA database server error was encountered. [{value}{value}{value}{value}] (14)

Details
Product: Exchange
Event ID: 105
Source: MSExchangeMTA
Version: 6.0
Component: Message Transfer Agent
Symbolic Name: MTA00105
Message: An MTA database server error was encountered. [{value}{value}{value}{value}] (14)
   
Explanation
The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full.
   
User Action
If the Exchange server disk is full, delete any unneeded files. If you suspect a disk error, run Chkdsk. Verify that the \Exchsrvr\Mtadata directory exists. Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt. If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Contact Microsoft Product Support Services for assistance.

Related:

Stopped clustered mailbox server %1 with reason: %2.

Details
Product: Exchange
Event ID: 105
Source: MSExchangeRepl
Version: 8.0
Symbolic Name: StopCMSSuccess
Message: Stopped clustered mailbox server %1 with reason: %2.
   
Explanation

This Information event indicates that clustered mailbox server %1 is offline because of %2. This information event may be triggered by multiple causes. Similarly, the method by which you resolve this condition varies greatly depending on what triggered this event in your particular Exchange environment.

   
User Action

To resolve this error, do one or more of the following:

  • Review the System and Application event logs for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this event.

  • If you cannot resolve this problem or if you experience other problems or mail flow interruptions in your Exchange environment, contact Microsoft Product Support Services. For information about contacting support, visit the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related: