new server 2022 - WSEE dashboard empty!!

Answered
0

i have a new install of 2022 w/WSEE

added all my client computers & migrated their profiles

moved MB to a new case, 2022 starts up, WSEE dashboard took quite a while to finally start up – OS on NVME drive – no new drives connected

everything is gone!

no server or client computers or users??

what happened

updated WSEE yesterday

all client computers in active directory along with users

still running evaluation copy of 2022

update:

Windows Server Essentials Management Service not tunning – will not start

WSEE Installer / WSEE Updater
  • You must to post comments.
Filter
Sort by: Oldest First
Post Answer
Good Answer
0

The server Dashboard will indeed be very slow to start, and then be missing the users, computers, etc., when one or more of the Windows Server Essentials services are not running. You will need to ensure that all of the Essentials services are working properly in order to correct that issue.

If the Windows Server Essentials Management service is not starting properly on your server, then you should take a look in the server’s “Logs” folder to see if any of the log files within that folder (such as Dashboard.log, etc.) give any indication as to why the service isn’t starting (i.e. is crashing, etc.). You can find the server’s Logs folder located at:

C:\ProgramData\Microsoft\Windows Server\Logs

  • You must to post comments.
0

i’m not sure what is significant in the log below – empty log, 1 attempt to start the dashboard – maybe someone can see something i can’t

this happened 1st boot after installing WSEE revision 1, tried installing again, no change

here are parts of the log that might be significant

=======================

[12392] 250820.153909.9180: PluginManager: Unable to retrieve digital certificate for C:\Windows\system32\Essentials\AzureVirtualNetworkAddin.dll: Cannot find the requested object.

[12392] 250820.153909.9337: PluginManager: Unable to retrieve digital certificate for C:\Windows\system32\Essentials\OIMAddin.dll: Cannot find the requested object.

[12392] 250820.153909.9337: PluginManager: Unable to retrieve digital certificate for C:\Windows\system32\Essentials\Microsoft.WindowsServerSolutions.Console.AddIns.OnlineBackup.dll: Cannot find the requested object.

[12392] 250820.153909.9337: PluginManager: Unable to retrieve digital certificate for C:\Windows\system32\Essentials\Microsoft.WindowsServerSolutions.Console.AddIns.RecoveryService.dll: Cannot find the requested object.

[12392] 250820.153910.0430: Dashboard.Forms: Creating TabPage for node E14FC830-F3A5-4ae6-BA8F-35A083EA5654 with display name “HOME” for TabControl
[12392] 250820.153910.1837: PluginManager: Unable to retrieve digital certificate for C:\Windows\system32\Essentials\AlertViewerSubTab.dll: Cannot find the requested object.

[12392] 250820.153910.1993: PluginManager: Unable to retrieve digital certificate for C:\Windows\system32\Essentials\HomePage.dll: Cannot find the requested object.

[12392] 250820.153910.4181: PluginManager: Unable to retrieve digital certificate for C:\Windows\system32\Essentials\AlertViewerSubTab.dll: Cannot find the requested object.

[12392] 250820.153910.4181: PluginManager: Unable to retrieve digital certificate for C:\Windows\system32\Essentials\HomePage.dll: Cannot find the requested object.

==============================

[12392] 250820.154117.0867: Dashboard.Forms: Creating TabPage for node 3d0214d7-e05d-43c3-aad5-efdc96dcc367 with display name “WSEE Installer” for TabControl
[12392] 250820.154117.1477: Dashboard.Forms: TabControl created. Name: PrimaryTabs, Tab count: 9
[12392] 250820.154117.2527: Dashboard.Forms: Page selected: ffc2b311-08ca-4200-9719-bf0119740eba
[12392] 250820.154117.2657: General: Failed to open Dashboard\Home registry key.

  • You must to post comments.
0

from another log

======================

[13260] 250820.151848.0102: SharedServiceHost: Information: [0] : ==========================================================
[13260] 250820.151848.1508: SharedServiceHost: Information: [0] : “C:\Windows\System32\Essentials\SharedServiceHost.exe” C:\Windows\System32\Essentials\ManagementServiceConfig
[13260] 250820.151848.1508: SharedServiceHost: Information: [0] : Loading service information from “C:\Windows\System32\Essentials\ManagementServiceConfig”.
[11956] 250820.151848.1977: Services: Information: [0] : OnStart: service “WseMgmtSvc” starting up.
[11956] 250820.151848.2133: GenBmr: Failed to read the xml file C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\GenBmrState.xml. System.IO.DirectoryNotFoundException:Could not find a part of the path ‘C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\GenBmrState.xml’.
[11956] 250820.151848.2133: GenBmr: Failed to read the xml file C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\GenBmrState.xml.bak. System.IO.DirectoryNotFoundException:Could not find a part of the path ‘C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\GenBmrState.xml.bak’.
[11956] 250820.151848.2133: GenBmr: Checking existance of OEM images.
[11956] 250820.151848.2290: GenBmr: AdkReady in AdkInfo = False
[11956] 250820.151848.2290: GenBmr: Failed to read the xml file C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\GenBmrArgsType.xml. System.IO.DirectoryNotFoundException:Could not find a part of the path ‘C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\GenBmrArgsType.xml’.
[11956] 250820.151848.2290: GenBmr: Failed to read the xml file C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\GenBmrArgsType.xml.bak. System.IO.DirectoryNotFoundException:Could not find a part of the path ‘C:\ProgramData\Microsoft\Windows Server\Data\ClientRestore\GenBmrArgsType.xml.bak’.
[11956] 250820.151848.2290: GenBmr: Failed to load type .
[11956] 250820.151848.2290: GenBmr: Failed to load type .
[11956] 250820.151848.2290: GenBmr: Failed to load type .
[11956] 250820.151848.2290: GenBmr: Failed to load type .

  • Mike
    These appear to be a bit more helpful. I’ve never come across these errors before, but they do seem to indicate something missing/corrupted in the client backups (see links in my other post).
  • You must to post comments.
0

Those just look like standard logged items to me (i.e. nothing relevant in what you’ve shared). Your best bet would be to sort the Logs folder by date modified, so that the log files that are newly written to appear up at the top, and then go and open the Services applet and attempt to start the failing service. After that try looking at the recently modified logs to see if there’s anything in there pertaining to the failing service. If nothing appears, then try doing the same after attempting to start the server Dashboard.

BTW, in my experience, when the management service won’t start, it’s most likely due to hard drive issues and/or client/server backup corruption. For examples see:

The Windows Server Essentials Management Service

After Disk Changes, WSEE Management Service Fails Start

WSE Management Service Will not Start error 1067 Post Update

You might also want to try performing an Internet search on the issue and see if others have posted anything helpful.

  • You must to post comments.
0

thanks, deleting the backup catalog fixed it!!

  • You must to post comments.
Showing 5 results
Your Answer
Post as a guest by filling out the fields below, or you may to post using your existing user account (register to create a user account if you do not already have one). Guest's questions will be moderated before being posted. NOTE: Your email address will not be published, nor will it be used for marketing purposes, etc. (as per our privacy statement).
Name*
E-mail*
Answer Details*
Screenshots
File Name Size
There are currently no files uploaded.
Maximum number of files 4, maximum file size 5MB.
Supported file formats: gif jpeg jpg png

Featured Questions

Recent Questions & Answers

Q&A Toolbox

Log in | Register

Ask a question

View all questions