Maamulaha Server-ka Windows^{(Windows Server Manager)} waxa uu u sahlayaa shaqaalaha IT-ga in ay tab ku hayaan dhammaan server-yada lagu hayo shabakad. Qalabka Maareeyaha Server^{(Server Manager)} -ku wuxuu siinayaa shaqaalaha IT-ga awood ay ku maareeyaan doorarka server-ka iyaga oo aan marin jireed u lahayn server-yada. Haddii aadan awoodin inaad hesho Maareeyaha Adeegga^{(Server Manager)} , oo markaad gujiso Maareeyaha Adeegga^{(Server Manager)} , aad la kulanto fariinta khaladka ah ServerManager.exe - Codsigan lama bilaabi karo^{(ServerManager.exe – This application could not be started)} , ka dib xalalka lagu soo bandhigay boostadan waxaa loogu talagalay inay kaa caawiyaan xallinta arrin.

Markaad la kulanto arrintan, waxaad heli doontaa fariinta khaladka ah ee soo socota;

ServerManager.exe – This application could not be started. L?.
This application could not be started.
Do you want to view Information about this issue?

Waxaa laga yaabaa inaad la kulanto qaladkan mid ama dhowr ka mid ah sababahan soo socda aawadood:

• Furaha diiwaanka ee ServerManager.exe waa mid aan sax ahayn ama dhaawacmay.
• Malwareer kombuyuutarku^(Computer) wuxuu duray kood xaasidnimo ah oo wax ka beddelay faylka ServerManager.exe .
• Faylka ServerManager.exe waxaa furay software kale.
• Faylka ServerManager.exe waxaa si ula kac ah ama si qalad ah u tirtiray software kale.
• Nooca loo baahan yahay ee faylka ServerManager.exe waxaa dib u qoray software kale.
• Waxaa jira cillad hardware ah, sida Hard Disk-ga xun.

ServerManager.exe - Codsigan lama bilaabi karo

Haddii aad la kulanto arrintan, waxaad isku dayi kartaa xalalkayaga hoos ku qoran oo aan si gaar ah u kala horrayn oo arag haddii ay taasi caawinayso xallinta arrinta.

1. Orod amarka DISM
2. Gacanta ku tirtir faylka user.config
3. Wax ka beddel ServerList.xml
4. Samee Soo Celinta Nidaamka
5. Ku Samee Dayactir Kordhinta Goobta
6. Qaabee oo nadiifi ku rakib Server OS

Aynu eegno sharraxaadda habka ay khusayso mid kasta oo ka mid ah xalalka taxan.

1] Orod amarka DISM

Xalkani waxa uu kaaga baahan yahay inaad hagaajiso/dib u geliso .NET Frameworks noocyada 3 iyo 4 adoo isticmaalaya amarka DISM . Waa kan sida:

• Ku fur Command Prompt qaabka maamulka^{(Open Command Prompt in admin mode)} .
• Daaqadda degdegga ah ee CMD , ku socodsii amarka soo socda midba midka kale:

DISM.exe /online /enable-feature /all /featurename:NetFx3

DISM.exe /online /enable-feature /all /featurename:NetFx4

Ka dib, codsiga maamulaha serverku waa inuu furmo khalad la'aan.

2] Gacan ku tirtir faylka user.config

Samee kuwan soo socda:

• Riix Windows key + E si aad u furto File Explorer.
• U gudub dariiqa faylka hoose ee C drive-gaaga ama hoyga darawalnimada rakibaadda serverka ee loo aqoonsaday inuu yahay galka xididka:

C:\Users\<YourUserName>\AppData\Local\Microsoft_Corporation\ServerManager.exe_StrongName_m3xk0k0ucj0oj3ai2hibnhnv4xobnimj10.0.0.0user.config

• Goobta, tirtir faylka user.config  .
• Dib u bilaabo Maareeyaha Server^{(Restart Server Manager)} -ka - tani waxay dib u abuurtaa faylka waxayna sidoo kale wax ka qaban doontaa arrin kasta oo faylka la kharribmay iyo sida.

3] Wax ka beddel ServerList.xml

Haddii aad haysatid qalabyo badan oo OS ah oo server ah oo socda, waxaad ogaan kartaa in mid ka mid ah adeegayaasha uu mas'uul ka yahay qaladka Maareeyaha Server -ka. ^{(Server Manager)}Waxaad tan ku ogaan kartaa adigoo furaya Maareeyaha Server^{(Server Manager)} -ka ee adeegayaasha kale oo isku day inaad ku darto server. Dhammaan si wanaagsan ayey u socdaan ilaa aad isku daydo inaad sidaas oo kale ku sameyso server gaar ah, waa marka maamulaha server-ka uu shil galo oo uu joojiyo shaqada mar kale. Xaaladdan oo kale, waxaad wax ka beddeli kartaa ServerList.xml , oo aad ka saartaa serverka dhibaatada leh. Maareeyaha Server^{(Server Manager)} - ku waa inuu hadda si fiican u shaqeeyaa.

4] Samee Nidaamka Soo Celinta

Si la mid ah nidaamka hawlgalka macmiilka Windows 10, waxaad samayn kartaa nidaamka soo celinta oo arag haddii ay taasi ku caawin. Tani waa mid lagu dabaqi karo haddii aadan awoodin inaad bilowdo  Maamulaha Adeegga^{(Server Manager)}  dhawaanahan oo kaliya iyo in arrimuhu si fiican u shaqeeyeen kahor taas.

5] Samee Dayactir Casriyeyn oo Goobta ah

Sidoo kale, oo la mid ah macmiilka OS Windows 10 , waxaad samayn kartaa Dib-u-habayn Ku-meel-gaar ah oo arag haddii taasi ku caawinayso.

6] Qaabee^(Format) oo nadiifi ku rakib Server OS

Habka ugu dambeeya, waxaad qaabayn kartaa oo aad nadiifin kartaa rakibidda^{(clean install)} serverka OS.

Waxaan rajeyneynaa in wax halkan ku caawiyaan.

ServerManager.exe - This application could not be started

The Windows Server Manager enables the IT staff to keep a tab on all the servers hosted on a network. The Server Manager tool gives IT staff the ability to manage server roles without having physical access to the servers. If you’re unable to get the Server Manager working, whereby when you click on Server Manager, you encounter the error message ServerManager.exe – This application could not be started, then the solutions presented in this post are intended to help you resolve the issue.

When you encounter this issue, you’ll receive the following full error message;

ServerManager.exe – This application could not be started. L?.
This application could not be started.
Do you want to view Information about this issue?

You may encounter this error due to one or more of the following reasons:

• The registry key of ServerManager.exe is invalid or damaged.
• Computer malware has injected malicious code and modified ServerManager.exe file.
• The ServerManager.exe file was uninstalled by other software.
• The ServerManager.exe file was intentionally or mistakenly deleted by other software.
• The required version of ServerManager.exe file is overwritten by other software.
• There is a hardware failure, such as a bad hard disk.

ServerManager.exe – This application could not be started

If you’re faced with this issue, you can try our recommended solutions below in no particular order and see if that helps to resolve the issue.

1. Run DISM command
2. Manually delete user.config file
3. Edit the ServerList.xml
4. Perform System Restore
5. Perform In-place Upgrade Repair
6. Format and clean install Server OS

Let’s take a look at the description of the process involved concerning each of the listed solutions.

1] Run DISM command

This solution requires you to fix/reinstall .NET Frameworks versions 3 and 4 using the DISM command. Here’s how:

• Open Command Prompt in admin mode.
• In the CMD prompt window, run the following command one after the other:

DISM.exe /online /enable-feature /all /featurename:NetFx3

DISM.exe /online /enable-feature /all /featurename:NetFx4

Afterward, the server manager application should open without the error.

2] Manually delete user.config file

Do the following:

• Press Windows key + E to open File Explorer.
• Navigate to the file path below in your C drive or the drive housing the server installation identified as the root folder:

C:\Users\<YourUserName>\AppData\Local\Microsoft_Corporation\ServerManager.exe_StrongName_m3xk0k0ucj0oj3ai2hibnhnv4xobnimj10.0.0.0user.config

• At the location, delete the user.config file.
• Restart Server Manager – this recreates the file and will also address any issues of the file has become corrupted and such.

3] Edit the ServerList.xml

If you have multiple server OS installations running, you may discover that one of the servers is responsible for the Server Manager error. You can determine this by opening Server Manager on the other servers and try adding servers. All goes well until you try doing the same on a particular server, that’s when the server manager would crash and stop working again. In this case, you can edit the ServerList.xml, and remove the problematic server. The Server Manager should work fine now.

4] Perform System Restore

Similar to the client operating system Windows 10, you can perform a system restore and see if that helps. This is applicable if you are unable to start Server Manager only recently and that things worked fine prior to that.

5] Perform In-place Upgrade Repair

Also, similar to the client OS Windows 10, you can perform an In-place Upgrade Repair and see if that helps.

6] Format and clean install Server OS

As a last resort, you can format and clean install the server OS.

Hope something here helps you.

Related posts

• Fix ma gaadhi karo cilada VPN Server ee ku jirta PIA Windows 11

• Daaqadaha ma xaqiijin karaan saxiixa dhijitaalka ah (Koodhka 52)

• Hagaaji kaydku waa qaab aan la garanayn ama khalad dhaawacmay

• Habkani waxa uu u baahan yahay warbaahin meesha laga saari karo - Qaladka dib u dejinta erayga sirta ah

• Hagaaji cilada soo galitaanka dukaanka Microsoft 0x801901f4 Windows 11/10

• Khaladaadka hagaaji 0xC00D3E8E, Guriga waxaa lagu akhriyaa kaliya Windows 11/10

• Hid.dll lagama helin ama khalad ka maqan Windows 10

• Sida loo xaliyo dhibaatada isku dhaca Saxeexa Disk ee gudaha Windows 11/10

• Fadlan geli warbaahinta kaydinta dibadda oo tabo OK

• Hagaaji ShellExecuteEx qalad ku fashilmay Windows 11/10

• Hagaaji Qaladka Load Application 5:0000065434 Windows 10

• Sida loo hagaajiyo Start PXE IPV4 gudaha Windows 11/10

• Kumbuyuutarkan looma cusboonaysiin karo Windows 10 sababtoo ah Goobaha Kaydinta Lammaaniga ah

• Wax baa khaldamay, Demi software ka-hortagga fayraska, 0x8007045d

• Hagaaji Code Error Code 30038-28 marka la cusboonaysiinayo Xafiiska

• Aqoonsiga Dhacdada 158 qalad - Diskiga isku midka ah ee GUIDs ee ku jira Windows 10

• Cilada adeegga ciyaaraha 0x80073D26, 0x8007139F ama 0x00000001

• Hagaaji Crypt32.dll lagama helin ama khalad ka maqan Windows 11/10

• Darawalku waxa uu ku ogaaday cilad darawalka gudaha DeviceVBoxNetLwf

• Madax adag ayaa heshay fariin khaldan oo xog xun Windows 10