Veeam error 1064 an exception occurred in the service when handling the control request

For some reason and to come to speed with all the Veeam components, I decided to revive my Veeam Lab and during the process, I encountered the following error “Error 1064 — An exception occurred in the service when handling the control request : No connection can be made because the active machine rejected it “. Before I proceed to fix this issue, I would love to discuss the capabilities of Veeam for anyone that may stumble on this article. 

Veeam Backup & Replication is comprehensive data protection and disaster recovery solution that provides a centralized console for administering backup, restore, replication operations in all supported platforms (virtual, physical, cloud). Regardless of what your needs are ranging from flexible hybrid cloud capabilities from AWS, Azure, and Google Cloud, or the most robust ransomware protection and recovery options. Veeam brings hardened immutable storage options, dependable cloud-native backup options, Continuous Data Protection, and much more all under one platform, with a single portable license for all workloads

Below are the images of the errors I get when i tried launching the Veeam Backup & Replication console.

The reason for this error was because my “SQL Server Evaluation period got expired”. This means, it exceeded the 180 days permitted. Also, I took a look at the log and found out that the Backup and Replication Server could not connect to the SQL Server as shown below.

[21.02.2022 21:59:45] <04> Info         [db] Connecting to SQL Server (CurrentUser=[TECHDIRECTARCHIChristian], ServerInstance=[MBAMSERV1MBAM], Options=[Direct])
[21.02.2022 21:59:45] <04> Info         [db] Removing 'Initial Catalog' property from connection string
[21.02.2022 22:01:45] <04> Info         [DB|ERROR] Failed to connect to server . (Microsoft.SqlServer.Management.Common.ConnectionFailureException)
[21.02.2022 22:01:45] <04> Info         [DB|ERROR]    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
[21.02.2022 22:01:45] <04> Info         [DB|ERROR]    at Veeam.Backup.DBCreator.DatabaseConnector.Connect(DatabaseConnectorOptions options)
[21.02.2022 22:01:45] <04> Info         [DB|ERROR] A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (System.Data.SqlClient.SqlException)

As you can see below, the error message from the Event Viewer with event ID 17051. Here is the link to my blogpost on how I resolved this issue.

To resolve this issues, I had to upgrade the SQL Server instance. here is a link to the complete blogpost.

• Launch the Open the SQL Server Installation Center and click on the Maintenance link. You can also launch this by launching setup.exe on MS SQL server installation media as well

Upon clicking on the Installation Center, the following window will open up. Then click on the Maintenance Tab, and then on Edition Upgrade

This will open up the “upgrade the Edition for SQL Server” window as shown below,  

On the Product Key page, select ”Enter the product key,” and type the product key and click Next.

Accept the license terms and click Next.

Select the instance you want to upgrade. You can see the instance name and select that instance. In this case, MBAM instance, which pointed out with evaluation. Select the instance and click Next.

On the ”Ready to upgrade edition” page, please click upgrade.

The upgrade process will take a few minutes to complete. Once the upgrade is completed, you will get a complete status, “succeeded”

Next, let’s ensure we are able to start our services again. As you can see, the services are running again.

Note: If you stop at here without granting the Veeam Backup Service the right privilege, you will also not be able to start the services, and launch the VBR console. To fix this, you will need to grant the Veeam Backup Service local administrative rights. Here is a link on this blogpost.

Upon granting this Log On rights, I was able to start the Veeam Backup and Replication Console. 

Veeam Backup and Replication is comprehensive data protection and disaster recovery solution which is capable of creating image-level backups of virtual, physical servers, cloud machines, and restoration as well. You may encounter the following errors when installing the Veeam backup and replication tool “VEEAM service is unable to start, error 1064: An exception occurred in the service when handling the control request”. Therefore, I will be showing you the steps on how to resolve this issue very quickly. Here is a detailed link to this post.

If you are here reading this troubleshooting guide "new Veeam Backup server but then Veeam won’t start", this means you must have recently installed Veeam Backup and Replication Server or must have recently upgraded it. As you can see from the images below, these are some errors I encountered while installing Veeam Backup and Replication in my test environment before deployment.

The «Failed to start service / connect to Veeam» and «connection refused». is not a connection or firewall issue. If you encounter similar issue, please endeavour to review the log file. Below are the 

Because of this error, you will also notice that most of the Veeam services are not running. Also, the SQL Server Express was stopped at this moment. Therefore, the error “Remoting Channel Sink UriNotPublished. RequestUri is ‘/VeeamService’ simply means the Veeam Service has not started yet“. To fix these issues, ensure the following registry keys have your server name and the SQL instance and Veeam database name are correct in the windows registry. If everything is fine here just as it is in my case, please proceed to the steps below. Below are the registry keys that need to be verified.

HKEY_LOCAL_MACHINESOFTWAREVeeamVeeam Backup and ReplicationSqlInstanceName
HKEY_LOCAL_MACHINESOFTWAREVeeamVeeam Backup and ReplicationSqlServerName
HKLMSOFTWAREVeeamVeeam Backup CatalogCatalogSharedFolderPath

Also, try to ensure the Veeam Backup and Replication services and the database services are running. If you get an error as shown below while trying to start any of the services, please proceed to the recommended solution below.

Recommended solution: From my log reviews and programs installed on my Server, It seems Veeam Backup and Replication was not correctly installed as I never got any installation success message. Also, these updates were missing and therefore, Veeam installation failed.
–I will have to repair the installation. To do this, run the Veeam setup.exe file again as shown below.

This will open the Veeam Backup and Replication window. Click on install Veeam Backup and replication.
— You will now be prompted with the maintenance mode window. Select Repair and click on Next to continue.

Specify your service account. Veeam recommends using the local system account but you can create your own service again due to security reasons.

The repair process will start as shown below. In between you will be asked to apply updates, please apply these updates and continue.

As we can see, the installation has succeeded.

As you can see below, all services have been started successfully. See this article on how to install and configure Veeam Backup and Replication 11 Community Edition.

Henceforth, Veeam backup and Replication should work as expected. Start the Veeam Backup and Replication Console: From the Start menu, select Apps > Veeam > Veeam Backup & Replication Console. Alternatively, to access the Backup and Replication console, open Veeam using the Veeam Backup and Replication Console shortcut created on your desktop and click on connect as shown below.

If you wish to uninstall Veeam Backup and Replication from your server, please follow the steps discussed in this link. I hope you found this blog post helpful.

ИТ База знаний

Курс по Asterisk

Полезно

— Узнать IP — адрес компьютера в интернете

— Онлайн генератор устойчивых паролей

— Онлайн калькулятор подсетей

— Калькулятор инсталляции IP — АТС Asterisk

— Руководство администратора FreePBX на русском языке

— Руководство администратора Cisco UCM/CME на русском языке

— Руководство администратора по Linux/Unix

Навигация

Серверные решения

Телефония

FreePBX и Asterisk

Настройка программных телефонов

Корпоративные сети

Протоколы и стандарты

SQL error 1064 – что делать?

Вам когда-нибудь приходилось видеть ошибку 1064 при работе с MySQL? Причем она указывает на некие синтаксические ошибки в SQL запросе, и эти ошибки могут быть совсем неочевидны – подробнее расскажем ниже.

Python — программист с нуля

Стань разработчиком на одном из самых популярных языков программирования

Использование зарезервированных слов

У каждой версии MySQL есть свой список зарезервированных слов – эти слова используются для особых задач или особых функций внутри движка MySQL. При попытке использовать какие-то из них, вы получите ту самую ошибку 1064. К примеру, ниже пример SQL запроса, который использует зарезервированное слово в качестве имени таблицы.

Как этого избежать? Просто! Только потому что слово alter зарезервировано, это не значит, что его нельзя использовать – нужно просто по-особенному приготовить! Чтобы движок MySQL не воспринимал это слово как команду, мы будем просто использовать кавычки и оно взлетит:

Недостающая информация в таблице

Иногда какой-то части информации в таблице нет и это может вызвать эту ошибку, если запрос обращался к этим данным. К примеру, если в таблице был список сотрудников, и каждому был присвоен ID, было бы логично предположить, что запрос будет вызывать запись сотрудника вместе с номером ID, например:

Если пресловутый $id никогда не был правильно указан, запрос будет выглядеть для MySQL сервера следующим образом:

Т.к запрос по сути пустой, движок MySQL будет выдавать ту самую ошибку 1064. Исправляется это следующим образом – вам нужно каким-то образом вызвать конкретную запись и добавить недостающую информацию, причем сделать это не так просто: если пытаться вызвать запись по уникальному номеру, скорее всего вы увидите точно такую ошибку. Можно с помощью phpMyAdmin вручную выбрать необходимую строку и добавить нужную информацию.

Опечатки в командах

Одной из самых частых причин ошибки 1064 являются опечатки. И иногда можно десять раз посмотреть на команду и не увидеть опечатки – как пример ниже с командой UPDATE:

Соответственно, проверяйте команды свежим взглядом и старайтесь не пропускать такого. Правильный вариант будет выглядеть так:

Устаревшие команды

Некоторые команды устарели, и в новых версиях MySQL начинают выдавать хорошо знакомую нам ошибку. К примеру, команда ‘TYPE’ была признана устаревшей в MySQL 4.1 и была полностью удалена в MySQL 5.1, где при попытке использовать ее вы можете видеть ту самую ошибку. Вместо нее необходимо использовать команду ‘ENGINE’.

Ниже неверный вариант:

А вот правильный, модный и современный вариант (как оно должно быть, чтобы не было ошибки):

Заключение

Как можно видеть, для одной несчастной ошибки, указывающей на синтаксис, может быть целый ряд разных причин. Так что когда вы видите подобную ошибку – вспомните эту статью и проверьте все возможные варианты ?

Бесплатный вводный урок на онлайн курс по Linux

Мы собрали концентрат самых востребованных знаний, которые позволят начать карьеру администраторов Linux, расширить текущие знания и сделать уверенный шаг в DevOps

Полезно?

Почему?

😪 Мы тщательно прорабатываем каждый фидбек и отвечаем по итогам анализа. Напишите, пожалуйста, как мы сможем улучшить эту статью.

😍 Полезные IT – статьи от экспертов раз в неделю у вас в почте. Укажите свою дату рождения и мы не забудем поздравить вас.

Источник

Official Support Articles

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

• Qlik Community
• :
• Support
• :
• Support
• :
• Knowledge
• :
• Support Articles
• :
• Error 1064 Unable to start Qlik logging service af.

• Subscribe to RSS Feed
• Mark as New
• Mark as Read
• Bookmark
• Subscribe
• Printer Friendly Page
• Report Inappropriate Content

Error 1064 Unable to start Qlik logging service after hostname was changed

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

After having successfully changed your Qlik Sense server hostname in an environment where centralized logging is enabled, when attempting to start Qlik logging service you receive

«Error 1064: An exception occurred in the service when handling the control request»

After having enabled centralized logging logs with this article How to enable logging for the Qlik Sense Centralized Logging service, the log returns the following error:

In the Qlik.Sense.Logging.log file, any of the following is registered:

[Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] — DevartLogDatabase::Connect failed!
Exception:
No connection could be made because the target machine actively refused it 172.16.16.101:4432
.
[ERROR] — Failed to retrieve settings from database. Error: [«DevartLogDatabase::Connect failed!nException:ntNo connection could be made because the target machine actively refused it 172.16.16.101:4432n»]

.
[Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] — Failed to initialize database. [«DevartLogDatabase::Connect failed!nException:ntNo connection could be made because the target machine actively refused it 172.16.16.101:4432n»]

May also see the following:

Qlik.Logging.Service [ERROR] — DevartLogDatabase::Connect failed!
Exception:
No such host is known

Environment:

• Qlik Sense Enterprise on Windows, February 2019 and later

Cause:

1. The Qlik Sense Server postgreSQL is not listening on the correct IP address

2. The connection string to the QLogs database has not been updated with the new server hostname

Resolution:

For Cause 1 above:

Modify the listen_addresses setting in the postgres.conf file to listen on the address mapped to the new hostname.

Note: Make sure to make a backup copy of postgres.conf before modifying it to contain either a wildcard (e.g «*», as shown on image below) or the new hostname (e.g: the server’s FQDN).

The file is found under the following path on the Central node:

This change requires the restart of the Qlik Sense Repository Database service, or PostgresSQL service if installed on separate server.

For Cause 2 above:

I. Update the hostname in the QlikCentralizedLogging.config file via command line.

See more information on updating the hostname using the CLI under Qlik Logging Service

1. Open CMD.exe as Administrator
2. Go to Logging folder: cd C:Program FilesQlikSenseLogging
3. Execute the following:
   1. Qlik.Logging.Service.exe validate
   2. Verify CentralizedLoggingEnabled: True or False
   3. If an error (example below) is returned instead, also see resolution for cause 1 above.

Failed to validate logging database. Database does not exist or is an invalid version

1. Change the hostname:
   1. Execute the following command:
   2. Qlik.Logging.Service.exe update —hostname
2. Verify the hostname is showing in the connection string as shown on the image below, and per II.1 below.
3. Make sure CentralizedLoggingEnabled is true, and start the Qlik Logging Service in services.msc.

II. Change the hostname: Connection String Editor

Change the hostname with the Qlik Sense «connection string editor»

1. Check the Connection string set in: C:ProgramDataQlikSenseLogQlikCentralizedLogging.config

To do this, use QlikSenseUtil.exe

1. Go to %Program Files%QlikSenseRepositoryUtilQlikSenseUtil.
2. Open QlikSenseUtil.exe as Admin (right-lick > run as administrator).
3. In QlikSenseUtil.exe > connect to the database with your superuser password then select «Connection String Editor».
4. In the file path to config file, place C:ProgramDataQlikSenseLogQlikCentralizedLogging.config
5. Compare the host set in the connection string with the current FQDN of the server
6. If the hostname is different, first backup file C:ProgramDataQlikSenseLogQlikCentralizedLogging.config before making any change

2. Try to modify the hostname in your connection string, and hit the save button.

Make sure your file has been changed by clicking the «read» button afterwords.

3. In case your Connection string cannot be changed please try III.

III. Change the hostname: Config file changes

Change the hostname by editing QlikCentralizedLogging.config

Note that this solution is a workaround in case point II. did not work,
By applying this change the centralize logging connection string will be set in clear text and will be no longer encrypted. Make sure to let the customer aware about this .

1. Backup file C:ProgramDataQlikSenseLogQlikCentralizedLogging.config before making any change
2. Edit QlikCentralizedLogging.config as follows
3. Copy the current connection string in a text editor, by using the QlikSenseUtil.exe .
   Please refer to II.1) to do this
   1. open file C:ProgramDataQlikSenseLogQlikCentralizedLogging.config
   2. Find and remove » » all the way to » «
   3. Replace with with the connection string you saved in a., corrected with the new server FQDN
4. If it still does not work, and your Database is stored on the same server, replace to host=localhost

Источник

KDS doesn’t start or KDS root key isn’t created in Windows Server 2012 R2

This article describes some issues that occur when you use the group Managed Service Accounts (gMSAs) feature on Windows Server 2012 R2-based domain controllers. You can fix these issues by using the update in this article. Before you install this update, see the Prerequisites section.

Symptoms

If the domain controller account isn’t located in the root of the Domain Controllers organizational unit (OU), you may encounter one of the following issues and receive the corresponding error messages:

Microsoft Key Distribution Service (KDS) start failure:

System error 1064 has occurred. An Exception occurred in the service when handling the control request.

KDS root key generation failure:

The process cannot access the file because it is being used by another process. ( Exception from HRESULT: 0x80070020 )

Cause

This issue occurs because KDS assumes that the domain controllers are in the Domain Controllers OU instead of a child OU of the Domain Controllers.

Resolution

The update changes the KDS service Domain Controller search behavior to look in the subtree below the «Domain Controllers» OU.

How to get this update

Important If you install a language pack after you install this update, you must reinstall this update. Therefore, we recommend that you install any language packs that you need before you install this update. For more information, see Add language packs to Windows.

Method 1: Windows Update

This update is provided as a Recommended update on Windows Update. For more information on how to run Windows Update, see How to get an update through Windows Update.

Method 2: Microsoft Download Center

The update is available for download from the Microsoft Download Center:

For more information about how to download Microsoft support files, select the following article number to view the article in the Microsoft Knowledge Base:

119591 How to get Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Update detail information

Prerequisites

Registry information

To apply this update, you don’t have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this update.

Update replacement information

This update doesn’t replace a previously released update.

More information

If you move DCs out of the Domain Controllers OU, the default setup of Group Policy is not applying to the Domain Controllers anymore, as most of the important settings are applied through the «Domain Controllers» OU. See the following TechNet article that warns about this problem:

Important: Do not move any domain controller accounts out of the default Domain Controllers OU, even if some administrators log on to them to run administrative tasks. Moving these accounts will disrupt the consistent application of domain controller policies to all domains and isn’t supported.

Many facilities that search for Domain Controller computer accounts search the subtree of the «Domain Controllers» OU. So placing the computer accounts in subtree may work with a lot of the software solutions out there.

However, there may be some services and applications, including analysis tools, that only search the Domain Controllers OU for DCs (by examining the GUID_DOMAIN_CONTROLLERS_CONTAINER_W value and setting a search base of «one-level»). DCs in child OUs won’t be found in this case.

It is up to the owner of the solution whether they see this as a valid issue to create an update to allow accounts to be located in child OUs of «Domain Controllers».

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

References

See reference for well-known AD objects:

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.

The files that apply to a specific product, milestone (RTM, SP n), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

Источник

After having successfully changed your Qlik Sense server hostname in an environment where centralized logging is enabled, when attempting to start Qlik logging service you receive

«Error 1064: An exception occurred in the service when handling the control request»

After having enabled centralized logging logs with this article How to enable logging for the Qlik Sense Centralized Logging service, the log returns the following error:

In the Qlik.Sense.Logging.log file, any of the following is registered:

…

[Qlik.Logging.Service.exe] Qlik.Logging.Service [ERROR] — DevartLogDatabase::Connect failed!
Exception:
No connection could be made because the target machine actively refused it 172.16.16.101:4432
…
[ERROR] — Failed to retrieve settings from database. Error: [«DevartLogDatabase::Connect failed!nException:ntNo connection could be made because the target machine actively refused it 172.16.16.101:4432n»]

Environment:

• Qlik Sense Enterprise on Windows, February 2019 and later

Cause:

1. The Qlik Sense Server postgreSQL is not listening on the correct IP address

2. The connection string to the QLogs database has not been updated with the new server hostname

Resolution:

For  Cause 1 above:

Modify the listen_addresses setting in the postgres.conf file to listen on the address mapped to the new hostname.

Note: Make sure to make a backup copy of postgres.conf before modifying it to contain either a wildcard (e.g «*», as shown on image below) or the new hostname (e.g: the server’s FQDN).

The file is found under the following path on the Central node:

 C:ProgramDataQlikSenseRepositoryPostgreSQL9.6 

This change requires the restart of the Qlik Sense Repository Database service, or PostgresSQL service if installed on separate server.

 For more information see PostgreSQL: postgresql.conf and pg_hba.conf explained 

For  Cause 2 above:

I. Update the hostname in the QlikCentralizedLogging.config file via command line.

1. Open CMD.exe as Administrator
2. Go to Logging folder: cd C:Program FilesQlikSenseLogging
3. Execute the following:
   1. Qlik.Logging.Service.exe validate
   2. Verify CentralizedLoggingEnabled: True or False
   3. If an error (example below) is returned instead, also see resolution for cause 1 above.

Failed to validate logging database. Database does not exist or is an invalid version

1. Change the hostname:
   1. Execute the following command:
   2. Qlik.Logging.Service.exe update —hostname <newhostname>
      

      example: Qlik.Logging.Service.exe update --hostname QlikServer55.domain.local​

2. Verify the hostname is showing in the connection string as shown on the image below, and per II.1 below.
3. Make sure CentralizedLoggingEnabled is true, and start the Qlik Logging Service in services.msc.

II. Change the hostname: Connection String Editor

1. Check the Connection string set in: C:ProgramDataQlikSenseLogQlikCentralizedLogging.config 

To do this, use QlikSenseUtil.exe

1. Go to %Program Files%QlikSenseRepositoryUtilQlikSenseUtil.
2. Open QlikSenseUtil.exe as Admin (right-lick > run as administrator).
3. In QlikSenseUtil.exe > connect to the database with your superuser password then select «Connection String Editor».
4. In the file  path to config file, place C:ProgramDataQlikSenseLogQlikCentralizedLogging.config
5. Compare the host set in the connection string with the current FQDN of the server
6. If the hostname is different, first backup file C:ProgramDataQlikSenseLogQlikCentralizedLogging.config  before making any change

2. Try to modify the hostname in your connection string, and hit the save button.

Make sure your file has been changed by clicking the «read» button afterwords.

3. In case your Connection string cannot be changed please try III. 

III. Change the hostname: Config file changes

1. Backup file C:ProgramDataQlikSenseLogQlikCentralizedLogging.config  before making any change
2. Edit QlikCentralizedLogging.config as follows
3. Copy the current connection string in a text editor, by using the QlikSenseUtil.exe .
   Please refer to II.1) to do this
   1. open file C:ProgramDataQlikSenseLogQlikCentralizedLogging.config
   2. Find and remove «<connectionStrings configProtectionProvider=»DataProtectionConfigurationProvider»> »  all the way to » </connectionStrings>» 
   3. Replace with with the connection string you saved in a., corrected with the new server FQDN

      <connectionStrings>
          <add name="qlogs_reader" connectionString="user id=qlogs_reader;password=123;host=QsDBserverFQDN;port=4432;database=QLogs;" providerName="Devart.Data.PostgreSql" />
          <add name="qlogs_writer" connectionString="user id=qlogs_writer;password=123;host=QsDBserverFQDN;port=4432;database=QLogs;" providerName="Devart.Data.PostgreSql" />
      </connectionStrings>​

   4. If it still does not work, and your Database is stored on the same server,  replace to host=localhost

I cannot start AD FS windows service in services.msc, it shows error:

Windows could not start AD FS 2.0 Windows Service service on Local Computer. 
Error 1064: An exception occurred in the service when handling the control request.

And i can see following error in Windows Event, what shall i do?  :

Log Name:      AD FS 2.0/Admin
Source:        AD FS 2.0
Date:          4/18/2012 4:26:02 PM
Event ID:      220
Task Category: None
Level:         Error
Keywords:      AD FS
User:          NETWORK SERVICE
Computer:      WIN-CITKF3C8R0O.guyuming.com
Description:
The Federation Service configuration could not be loaded correctly from the AD FS configuration database. 

Additional Data 
Error:  
There is already a listener on IP endpoint :::1500.  Make sure that you are not trying to use this endpoint multiple times in your application and that there are no other applications listening on this endpoint.
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
  <System>
    <Provider Name=»AD FS 2.0″ Guid=»{20E25DDB-09E5-404B-8A56-EDAE2F12EE81}» />
    <EventID>220</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000001</Keywords>
    <TimeCreated SystemTime=»2012-04-18T08:26:02.097156100Z» />
    <EventRecordID>1986</EventRecordID>
    <Correlation />
    <Execution ProcessID=»7256″ ThreadID=»7184″ />
    <Channel>AD FS 2.0/Admin</Channel>
    <Computer>WIN-CITKF3C8R0O.guyuming.com</Computer>
    <Security UserID=»S-1-5-20″ />
  </System>
  <UserData>
    <Event xmlns:auto-ns2=»http://schemas.microsoft.com/win/2004/08/events» xmlns=»http://schemas.microsoft.com/ActiveDirectoryFederationServices/2.0/Events»>
      <EventData>
        <Data>There is already a listener on IP endpoint :::1500.  Make sure that you are not trying to use this endpoint multiple times in your application and that there are no other applications listening on this endpoint.</Data>
      </EventData>
    </Event>
  </UserData>
</Event>

Log Name:      AD FS 2.0/Admin
Source:        AD FS 2.0
Date:          4/18/2012 4:26:02 PM
Event ID:      202
Task Category: None
Level:         Error
Keywords:      AD FS
User:          NETWORK SERVICE
Computer:      WIN-CITKF3C8R0O.guyuming.com
Description:
The Federation Service configuration service could not be opened. 

Additional Data 
Exception details: 
System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint :::1500.  Make sure that you are not trying to use this endpoint multiple times in your application and that there are no other applications listening on this
endpoint. —> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at System.ServiceModel.Channels.SocketConnectionListener.Listen()
   — End of inner exception stack trace —
   at System.ServiceModel.Channels.SocketConnectionListener.Listen()
   at System.ServiceModel.Channels.BufferedConnectionListener.Listen()
   at System.ServiceModel.Channels.ExclusiveTcpTransportManager.OnOpen()
   at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
   at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
   at System.ServiceModel.Channels.ConnectionOrientedTransportChannelListener.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.TcpChannelListener`2.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.IdentityServer.Service.SecurityTokenService.ServiceHostManager.Open(ServiceHostEntry entry)
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
  <System>
    <Provider Name=»AD FS 2.0″ Guid=»{20E25DDB-09E5-404B-8A56-EDAE2F12EE81}» />
    <EventID>202</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000001</Keywords>
    <TimeCreated SystemTime=»2012-04-18T08:26:02.070154600Z» />
    <EventRecordID>1984</EventRecordID>
    <Correlation />
    <Execution ProcessID=»7256″ ThreadID=»7184″ />
    <Channel>AD FS 2.0/Admin</Channel>
    <Computer>WIN-CITKF3C8R0O.guyuming.com</Computer>
    <Security UserID=»S-1-5-20″ />
  </System>
  <UserData>
    <Event xmlns:auto-ns2=»http://schemas.microsoft.com/win/2004/08/events» xmlns=»http://schemas.microsoft.com/ActiveDirectoryFederationServices/2.0/Events»>
      <EventData>
        <Data>configuration service</Data>
        <Data>System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint :::1500.  Make sure that you are not trying to use this endpoint multiple times in your application and that there are
no other applications listening on this endpoint. —&gt; System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
   at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Bind(EndPoint localEP)
   at System.ServiceModel.Channels.SocketConnectionListener.Listen()
   — End of inner exception stack trace —
   at System.ServiceModel.Channels.SocketConnectionListener.Listen()
   at System.ServiceModel.Channels.BufferedConnectionListener.Listen()
   at System.ServiceModel.Channels.ExclusiveTcpTransportManager.OnOpen()
   at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
   at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
   at System.ServiceModel.Channels.ConnectionOrientedTransportChannelListener.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.TcpChannelListener`2.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.IdentityServer.Service.SecurityTokenService.ServiceHostManager.Open(ServiceHostEntry entry)</Data>
      </EventData>
    </Event>
  </UserData>
</Event>