Event ID 4104 — Windows to UNIX Password Synchronization Service — Run-time Issues

Event ID 4104 — Windows to UNIX Password Synchronization Service — Run-time Issues

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Windows to UNIX Password Synchronization Service — Run-time Issues indicates the functionality of Windows to UNIX password synchronization operations.

When Password Synchronization is configured for Windows-to-UNIX synchronization, and a password is changed on a Windows-based computer running Password Synchronization, the Password Synchronization service determines whether the user’s password is to be synchronized on UNIX computers. When the Password Synchronization service is operating normally, it encrypts the password and sends it to the Password Synchronization daemon on each computer with which the Windows-based computer is configured to be synchronized. The daemon then decrypts the password and changes the password on the UNIX host.

Event Details

Product: Windows Identity Management for UNIX
ID: 4104
Source: Microsoft-Windows-IDMU-PSync
Version: 6.0
Symbolic Name: MSG_MACHINE_ACCT_IGNORED_INFO
Message: Password change request for computer account ignored. %rAccount = %1

Resolve

This is a normal condition. No further action is required.

Related Management Information

Windows to UNIX Password Synchronization Service — Run-time Issues

Identity Management for UNIX

Related:

Event ID 4104 — Terminal Services License Server Availability

Event ID 4104 — Terminal Services License Server Availability

Updated: January 5, 2012

Applies To: Windows Server 2008

The Terminal Services license server relies on the Terminal Services Licensing service to be running in order to install, issue, and track the availability of Terminal Services client access licenses (TS CALs).

Event Details

Product: Windows Operating System
ID: 4104
Source: Microsoft-Windows-TerminalServices-Licensing
Version: 6.0
Symbolic Name: TLS_E_RPC_LISTEN
Message: The remote procedure call (RPC) port is not listening.

Resolve
Start the Terminal Services Licensing service

To resolve this issue, start the Terminal Services Licensing service on the Terminal Services license server.

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

To start the Terminal Services Licensing service:

  1. On the license server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the Services pane, right-click Terminal Services Licensing, and then click Properties.
  4. On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
  5. Under Service status, click Start.
  6. Click OK to close the Terminal Services Licensing Properties dialog box.
  7. Confirm that the Status column for the Terminal Services Licensing service displays Started.

Verify

To verify that the Terminal Services license server is available, ensure that the Terminal Services Licensing service is running.

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

To verify that the Terminal Services Licensing service is started:

  1. On the license server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the Services pane, locate Terminal Services Licensing.
  4. Confirm that the Status column for the Terminal Services Licensing service displays Started.

Related Management Information

Terminal Services License Server Availability

Terminal Services

Related:

Event ID 4104 — Microsoft Distributed Transaction Coordinator Service Installation and Setup

Event ID 4104 — Microsoft Distributed Transaction Coordinator Service Installation and Setup

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

The Microsoft Distributed Transaction Coordinator service (MSDTC) is installed during the installation of the operating system. Errors that occur during installation may stop the component from working properly. Any errors that occur during an upgrade process may also stop the component from working properly.

Event Details

Product: Windows Operating System
ID: 4104
Source: Microsoft-Windows-MSDTC
Version: 6.1
Symbolic Name: IDS_DTC_INSTALLED
Message: The Microsoft Distributed Transaction Coordinator service was successfully installed.%0

Resolve

This is a normal condition. No further action is required.

Related Management Information

Microsoft Distributed Transaction Coordinator Service Installation and Setup

Application Server

Related:

There was a failure during installation of the Microsoft Exchange H.323 Conferencing Bridge. There were problems initializing performance monitoring. Error code: {error code}; Message: {message id}

Master merge has been paused on %2 due to error %3. It will be rescheduled later.

Details
Product: Windows Operating System
Event ID: 4104
Source: Ci
Version: 5.0
Component: Application Event Log
Symbolic Name: MSG_CI_MASTER_MERGE_ABORTED
Message: Master merge has been paused on %2 due to error %3. It will be rescheduled later.
   
Explanation

Indexing Service could not finish a master merge because of the error displayed. The merge will be restarted automatically. The problem is most likely due to a shortage of disk space.

   
User Action

If this is a persistent problem, free up additional disk space.

Related:

There was a failure during installation of the Microsoft Exchange Data Conferencing service. There were problems initializing performance monitoring. Error code: {error code}; Message: {message id}

The multi-part identifier “%.*ls” could not be bound.

Details
Product: SQL Server
Event ID: 4104
Source: MSSQLServer
Version: 9.0
Component: SQLEngine
Symbolic Name: ALG_MULTI_ID_BAD
Message: The multi-part identifier “%.*ls” could not be bound.
   
Explanation

The name of an entity in SQL Server is referred to as its identifier. You use identifiers whenever you reference entities, for example, by specifying column and table names in a query. A multi-part identifier contains one or more qualifiers as a prefix for the identifier. For example, a table identifier may be prefixed with qualifiers such as the database name and schema name in which the table is contained, or a column identifier may be prefixed with qualifiers such as a table name or table alias.

Error 4104 indicates that the specified multi-part identifier could not be mapped to an existing entity. This error can be returned under the following conditions:

  • The qualifier supplied as a prefix for a column name does not correspond to any table or alias name used in the query.

    For example, the following statement uses a table alias (Dept) as a column prefix, but the table alias is not referenced in the FROM clause.

    SELECT Dept.Name FROM HumanResources.Department;

    In the following statements, a multi-part column identifier TableB.KeyCol is specified in the WHERE clause as part of a JOIN condition between two tables, however, TableB is not explicitly referenced in the query.

    DELETE FROM TableA WHERE TableA.KeyCol = TableB.KeyCol;

    SELECT ‘X’ FROM TableA WHERE TableB.KeyCol = TableA.KeyCol;

  • An alias name for the table is supplied in the FROM clause, but the qualifier supplied for a column is the table name. For example, the following statement uses the table name Department as the column prefix; however, the table has an alias (Dept) referenced in the FROM clause.

    SELECT Department.Name FROM HumanResources.Department AS Dept;

    When an alias is used, the table name cannot be used elsewhere in the statement.

  • SQL Server is unable to determine if the multi-part identifier refers to a column prefixed by a table or to a property of a CLR user-defined data type (UDT) prefixed by a column. This happens because properties of UDT columns are referenced by using the period separator (.) between the column name and the property name in the same way that a column name is prefixed with a table name. The following example creates two tables, a and b. Table b contains column a, which uses a CLR UDT dbo.myudt2 as its data type. The SELECT statement contains a multi-part identifier a.c2.

    CREATE TABLE a (c2 int);
    GO

    CREATE TABLE b (a dbo.myudt2);
    GO

    SELECT a.c2 FROM a, b;

    Assuming that the UDT myudt2 does not have a property named c2, SQL Server cannot determine whether identifier a.c2 refers to column c2 in table a or to the column a, property c2 in table b.

   
User Action
  • Match the column prefixes against the table names or alias names specified in the FROM clause of the query. If an alias is defined for a table name in the FROM clause, you can only use the alias as a qualifier for columns associated with that table.

    The statements above that reference the HumanResources.Department table can be corrected as follows:

    SELECT Dept.Name FROM HumanResources.Department AS Dept;
    GO

    SELECT Department.Name FROM HumanResources.Department;
    GO

  • Ensure that all tables are specified in the query and that the JOIN conditions between tables are specified correctly. The DELETE statement above can be corrected as follows:

    DELETE FROM dbo.TableA
    WHERE TableA.KeyCol = (SELECT TableB.KeyCol
    FROM TableB
    WHERE TableA.KeyCol = TableB.KeyCol);
    GO

    The SELECT statement above for TableA can be corrected as follows:

    SELECT ‘X’ FROM TableA, TableB WHERE TableB.KeyCol = TableA.KeyCol;

    or

    SELECT ‘X’ FROM TableA INNER JOIN TableB ON TableB.KeyCol = TableA.KeyCol;

  • Use unique, clearly defined names for identifiers. Doing so makes your code easier to read and maintain, and it also minimizes the risk of ambiguous references to multiple entities.

Related: