Servermanager exe ошибка приложения

Коллеги, добрый день.

Помогите решить проблему с запуском Server
Manager.

Поиски в интернете ни к чему не привели. Пробовал устанавливать обновления касательно фреймфорк.

При попытке запуска Server
Manager выдается ошибка:

Сигнатура проблемы:

 
Имя события проблемы:                
CLR20r3

 
Сигнатура проблемы 01:                
servermanager.exe

 
Сигнатура проблемы 02:                
6.2.9200.16384

 
Сигнатура проблемы 03:                
50107b22

 
Сигнатура проблемы 04:                
PresentationCore

 
Сигнатура проблемы 05:                
4.0.30319.18053

 
Сигнатура проблемы 06:                
51907cf0

 
Сигнатура проблемы 07:                
11b

 
Сигнатура проблемы 08:                
3c

 
Сигнатура проблемы 09:                
System.IO.FileLoadException

 
Версия ОС:                                         
6.2.9200.2.0.0.272.7

 
Код языка:                                         
1049

 
Дополнительные сведения 1:       
dcd4

 
Дополнительные сведения 2:       
dcd4802118774a4fbc03060d99f291d2

 
Дополнительные сведения 3:       
967a

 
Дополнительные сведения 4:       
967a6883d8f2fc3ba33bd4136795c8c5

И в журнале событий появляются события:

Имя журнала:   Application

Источник:      .NET Runtime

Дата:          31.07.2013 12:05:45

Код события:   1026

Категория задачи:Отсутствует

Уровень:       Ошибка

Ключевые слова:Классический

Пользователь:  Н/Д

Компьютер:     srv.firma.ru

Описание:

Приложение: ServerManager.exe

Версия платформы: v4.0.30319

Описание. Процесс был завершен из-за необработанного исключения.

Сведения об исключении: System.IO.FileLoadException

Стек:

   в MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   в System.Windows.Threading.DispatcherOperation.InvokeImpl()

   в System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   в System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   в System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

   в System.Windows.Threading.DispatcherOperation.Invoke()

   в System.Windows.Threading.Dispatcher.ProcessQueue()

   в System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   в MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   в MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

   в System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

   в MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   в System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

   в MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

   в MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

   в MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

   в System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)

   в System.Windows.Application.RunInternal(System.Windows.Window)

   в Microsoft.Windows.ServerManager.SingleInstanceAppLauncher.StartApplication(Microsoft.Windows.ServerManager.Common.ArgumentsProcessor)

   в Microsoft.Windows.ServerManager.MainApplication.Main(System.String[])

Xml события:

<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>

  <System>

    <Provider Name=».NET Runtime» />

    <EventID Qualifiers=»0″>1026</EventID>

    <Level>2</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime=»2013-07-31T08:05:45.000000000Z» />

    <EventRecordID>682290</EventRecordID>

    <Channel>Application</Channel>

    <Computer> srv.firma.ru
</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Приложение: ServerManager.exe

Версия платформы: v4.0.30319

Описание. Процесс был завершен из-за необработанного исключения.

Сведения об исключении: System.IO.FileLoadException

Стек:

   в MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   в System.Windows.Threading.DispatcherOperation.InvokeImpl()

   в System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   в System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   в System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

   в System.Windows.Threading.DispatcherOperation.Invoke()

   в System.Windows.Threading.Dispatcher.ProcessQueue()

   в System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   в MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   в MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

   в System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

   в MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   в System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

   в MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

   в MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

   в MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)

   в System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)

   в System.Windows.Application.RunInternal(System.Windows.Window)

   в Microsoft.Windows.ServerManager.SingleInstanceAppLauncher.StartApplication(Microsoft.Windows.ServerManager.Common.ArgumentsProcessor)

   в Microsoft.Windows.ServerManager.MainApplication.Main(System.String[])

</Data>

  </EventData>

</Event>

Имя журнала:   Application

Источник:      Application Error

Дата:          31.07.2013 12:05:46

Код события:   1000

Категория задачи:(100)

Уровень:       Ошибка

Ключевые слова:Классический

Пользователь:  Н/Д

Компьютер:      srv.firma.ru 

Описание:

Имя сбойного приложения: ServerManager.exe, версия: 6.2.9200.16384, метка времени: 0x50107b22

Имя сбойного модуля: KERNELBASE.dll, версия: 6.2.9200.16451, метка времени: 0x50988aa6

Код исключения: 0xe0434352

Смещение ошибки: 0x000000000003811c

Идентификатор сбойного процесса: 0x1ca0

Время запуска сбойного приложения: 0x01ce8dc4c21cc161

Путь сбойного приложения: C:Windowssystem32ServerManager.exe

Путь сбойного модуля: C:Windowssystem32KERNELBASE.dll

Идентификатор отчета: 006e019a-f9b8-11e2-93f1-6eae8b612e09

Полное имя сбойного пакета:

Код приложения, связанного со сбойным пакетом:

Xml события:

<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>

  <System>

    <Provider Name=»Application Error» />

    <EventID Qualifiers=»0″>1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime=»2013-07-31T08:05:46.000000000Z» />

    <EventRecordID>682291</EventRecordID>

    <Channel>Application</Channel>

    <Computer> srv.firma.ru
</Computer>

    <Security />

  </System>

  <EventData>

    <Data>ServerManager.exe</Data>

    <Data>6.2.9200.16384</Data>

    <Data>50107b22</Data>

    <Data>KERNELBASE.dll</Data>

    <Data>6.2.9200.16451</Data>

    <Data>50988aa6</Data>

    <Data>e0434352</Data>

    <Data>000000000003811c</Data>

    <Data>1ca0</Data>

    <Data>01ce8dc4c21cc161</Data>

    <Data>C:Windowssystem32ServerManager.exe</Data>

    <Data>C:Windowssystem32KERNELBASE.dll</Data>

    <Data>006e019a-f9b8-11e2-93f1-6eae8b612e09</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

IT staff in organizations uses the Windows Server Manager to keep tabs on all servers hosted on a network. The Server Manager basically gives administrators the ability to manage local and remote servers without the need for physical access to the servers.

However, despite the advanced technology used in the Windows Server Manager, things can go wrong. One such error is when you try to launch the Server Manager but it fails to run and instead displays the error notification below:

“ServerManager.exe – This application could not be started.

This application could not be started.

Do you want to view the information about this issue?”

What Is the Windows Server Manager?

The Windows Server Manager is a tool developed by Microsoft to view and manage network roles, such as Web Server, Domain Controller, File Server, and Print Server. IT professionals use the Server Manager to manage both local and Windows-based servers from their desktops without requiring physical access or the need to enable Remote Desktop Protocol (RDP) connections to each server.

The feature was first introduced in Windows Server 2008 to allow administrators to install, configure and manage server roles and features. Microsoft updated the Server Manager in Windows Server 2012, introducing new features, like the ability to change roles over the network and manage multiple servers simultaneously.

Windows Server 2012 can manage up to 100 servers, depending on the workloads run by the servers. The Windows Server Manager comes installed by default on all versions of Windows Server 2012 and Windows Server 2012 R2.

Now that you know what the Windows Server Manager is, you might be wondering what ServerManager.exe is in Windows 10.

ServerManager.exe is an executable file and part of the Windows operating system. It’s required by the system to run the Server Manager and gets installed when you install the Server Manager on your personal computer.

What Causes the ServerManager.exe Error in Windows 10?

You’re seeing the “ServerManager.exe – This application could not be started’ error message due to one of the following reasons:

• The ServerManager.exe file has been corrupted or altered by malware.
• The ServerManager.exe file’s registry entry has been damaged or corrupted.
• Third-party software uninstalled the ServerManager.exe file.
• A third-party program unintentionally deleted the ServerManager.exe file.
• A hardware failure, such as a hard disk drive crash or malfunction, occured.

How to Fix the “ServerManager.exe – This Application Could Not Be Started” Error

Solution 1: Run a DISM Scan

The first fix involves repairing .NET Framework versions 3 and 4 by performing a DISM scan. Here are the steps:

1. Launch the Command Prompt with administrator rights. To do that, press the Windows logo on your keyboard and type cmd. From the results, select “Run as administrator” in the right sidebar.
2. In the Administrator Command Prompt window, type the commands below one by one and hit the “Enter” key after each command:

After the commands have been executed successfully, the Windows Server Manager should launch without any errors.

Solution 2: Run an SFC Scan

To repair system files, including the ServerManager.exe file, that may have been deleted or corrupted, you need to perform an SFC scan. The System File Checker tool comes built into Windows machines to help fix the corruption of system files.

To use the SFC tool, follow the steps below:

1. Launch the Command Prompt with elevated rights as outlined above.
2. Type the command sfc /scannow and press “Enter”.

The scan will take several minutes to complete.

Once it does, any corrupt or missing system files should be repaired or replaced, thus getting rid of the ServerManager.exe error.

Solution 3: Manually Delete the User.config File

The user.config file, which holds all your unique settings, can become corrupted and cause the “ServerManager.exe. This application could not be started” error message. To resolve this problem, try manually deleting the file. It will then be recreated when you run the Server Manager.

Here’s how:

1. Launch File Explorer using the Win + E shortcut.

• Open the location containing the config file. Usually, the default location is on the C: drive. Here’s the full path:
  • C:UsersYourUserNameAppDataLocalMicrosoft_CorporationServerManager.exe_StrongName_m3xk0k0ucj0oj3ai2hibnhnv4xobnimj10.0.0.0user.config

• Delete the config file and restart the Server Manager. This recreates the user.config file, fixing other issues, like file corruption, in the process.

Hopefully, deleting the user.config file fixes the ServerManager.exe error.

Solution 4: Reconfigure ServerList.xml

If you’re running multiple server operating system installations, one of the servers might be causing the error. To identify the culprit, open the Server Manager on all the servers and try adding servers.

Servers that are functioning correctly will be added without problems. However, when you get to the problematic server, the Server Manager will crash and stop working. After you identify the server causing the error, try editing ServerList.xml and removing the server.

This should get rid of the Server Manager error.

Solution 5: Roll Back the Changes

If the Server Manager had been working fine and only started throwing up the error recently, you can try rolling back the changes to remove any conflicting software. System Restore is a Windows feature that will help you since it allows you to undo system changes.

Here are the steps you should take:

1. Press the Win + R keyboard shortcut and type rstrui.exe into the “Run” dialog box. Press “Enter” to launch System Restore.
2. In the “System Restore” window, click “Next”.
3. Select a restore point.
4. Click on “Next” and review the details.
5. If you’re satisfied, click on “Finish”.
6. Click “Yes” to proceed.

The system will be restored to the date you selected as the restore point. Hopefully, you can access the Server Manager without further issues.

Solution 6: Update Windows

Updating Windows installs the latest version of .NET components, which are crucial for the smooth running of the server. It also installs upgraded features and updates that may help to fix issues with the Server Manager. To proceed, follow the steps below:

1. Press the Windows logo on your keyboard and type “Update” (without quotes).
2. Select “Check for updates” and you’ll be taken to the “Windows Update” screen in the “Settings” app.
3. Click on the “Check for updates” button to see if there are any updates available. Install any that are pending.
4. Also, be sure to install the latest version of Remote Server Administration Tools for Windows 10. The tool is included as a set of “Features on Demand” in Windows 10:
5. Open the “Settings” app (Win + I).
6. Go to Apps.
7. Click the “Optional features” link.
8. On this screen, click on “Add a feature” and then select and install the specific RSAT version you need.

Solution 7: Clean Install the Server Operating System

Just like you’d clean install the Windows 10 OS if it throws up errors that you can’t resolve, you can do the same with the server OS. A clean install erases all existing programs and settings and installs a clean copy of the server. It’s a useful process, especially if other methods to get rid of a troublesome error fail to work.

But before you start, it’s advisable to back up your data to an external storage device so that you can access it later. A clean install is different from an in-place upgrade, where you go from an older OS to a newer one, keeping your settings, server roles, and data intact.

Use this method as a last resort since you have to start from scratch.

The “ServerManager.exe. This application could not start” error should no longer be a problem after performing a clean install.

Meanwhile, you need to ensure that your system is always running at peak levels. You see, over time, the constant use of your operating system causes problems here and there. From performance issues and slow boot times to applications loading slowly and the system crashing unexpectedly, these issues can interfere with the user experience.

Luckily, you can avoid all that using a PC optimization tool like Auslogics BoostSpeed. It’s an all-in-one utility program that gives you access to more than a dozen tools to tweak your system.

Whether it’s the registry, your hard disks, or even browsers, BoostSpeed will optimize them, leaving your system slim and fast. You don’t have to deal with computer lags every time you use your PC. Simply install Auslogics BoostSpeed and enjoy smooth and stable performance.

Уже втрой раз за несколько месяцев после установки ежемесячных обновлений Service Manager не может запуститься и подает в дамп.

Ситуация описана в https://social.technet.microsoft.com/Forums/en-US/d7e48460-bc23-4288-b976-98e7952d1517/server-manager-crashes-on-opening-on-windows-server-2016?forum=winservermanager

Код ошибки 1026. Смое важное в сообщении об ошибке:

Microsoft.Windows.ServerManager.Common.Data.RoleFeatureRoot..ctor(System.Collections.Generic.ICollection`1<Microsoft.Windows.ServerManager.Common.Data.IFeature>)
   at Microsoft.Windows.ServerManager.Common.Data.Server.UpdateFeatures(System.Collections.Generic.ICollection`1<Microsoft.Windows.ServerManager.Common.Data.IFeature>,

Статья на форуме Technet полезная, но не раскрывает всех секретов.

«UpdateFeatures» в сообщении об ошибке навивает на мысли. Фактически Server Manager не может получить список установленных компонентов.

Основная хитрость в том, что Server Manager использует PowerShell Remoting для подключения к серверам. Иначе говоря, если вы будете делать проверки локально, то не увидите проблему. Нужно проверять именно удаленное подключение.

Service Manager фактически использует для получения списка установленных компонент командлет Get-WindowsFeatures. Чтобы выполнить проверку правильно даже на локальном сервере, необходимо использовать параметер ComputerName:

Get-WindowsFeatures -ComputerName "server"

Если этот командлет вернет ошибку «Данный ключ отсутствует в словаре.» / «The given key was not present in the dictionary.», значит вы нашли поврежденный сервер.

Для лечения выполняем на нём команду:

dism /online /enable-feature /featurename:IIS-ASPNET45 /all

Остаётся только один вопрос: что если в Service Manager добавлено много серверов? Перебирать их вручную не очень интересное занятие. К тому же поврежденными могут оказаться серверы не подключенные в данный момент к Service Manager, но проблема может всплыть позднее в самое неподходящее время. Следовательно надо проверить все серверы и вылечить их.

# Получить список имен серверов, которые пингуются.
# Это значительно ускоряет процесс.
$servers = Get-ADComputer -SearchBase "OU=Servers,DC=firm,DC=ru" -Filter * | Select-Object -ExpandProperty Name | Where-Object { Test-Connection -ComputerName $_ -Count 1 -ErrorAction SilentlyContinue }

# Проверяем каждый сервер на конкретную этой ситуации ошибку.
$brokenServers = $servers | Where-Object { (Get-WindowsFeature -ComputerName $_ -ErrorVariable err -ErrorAction SilentlyContinue) -and ($err.Exception -is "System.Collections.Generic.KeyNotFoundException") }

$brokenServers

# Если найден поврежденный сервер, то выполняем на нем команду:
dism /online /enable-feature /featurename:IIS-ASPNET45 /all

Filed under: Active Directory, Powershell, Windows | Tagged: Powershell, Windows |