Unable to connect to Logical Disk Manager service
All I need to do is get into Disk Management and assign a drive letter.
I am able to see the new disk in devmgmt.msc (Device Manager). I added a new physical drive to the server. It is not a part of any local raid array. The Logical Disk Manager and Logical Disk Manager Administrative Service services are started and automatic.
However, every time I open diskmgmt.msc (Disk Management), the mmc hangs for a few seconds (displays "Connecting to Logical Disk Manager serive..") and then produces the error "Server execution failed".
I've tried to get around this by trying to find a command line solution to this problem, but have been unsuccessful.
I am able to see the new disk in devmgmt.msc (Device Manager). I added a new physical drive to the server. It is not a part of any local raid array. The Logical Disk Manager and Logical Disk Manager Administrative Service services are started and automatic.
However, every time I open diskmgmt.msc (Disk Management), the mmc hangs for a few seconds (displays "Connecting to Logical Disk Manager serive..") and then produces the error "Server execution failed".
I've tried to get around this by trying to find a command line solution to this problem, but have been unsuccessful.
Last Comment
ASKER
Even after a restart with no other users logged in it gives me the same error while running on it's own.
Thanks for the idea though, keep them coming...
Thanks for the idea though, keep them coming...
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
HI,
The problem can be caused by GP Changes too
I experinced that when was hardening the GP on one of our new BDC'S
if you try to remove "EVERYONE" AND " USERS" Group from the "Bypass traverse checking" privilege
which can be accessded through "Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment" , after rebooting/updateing the Server , you may get the error.
be wised that the correct harden values for this privilege are :
On Workstations and Servers(Member server / Stand Alone )
Administrators
Backup Operators
Power Users
Users
Everyone
ON Domain Controllers
Administrators
Authenticated Users
Everyone
Good Luck
The problem can be caused by GP Changes too
I experinced that when was hardening the GP on one of our new BDC'S
if you try to remove "EVERYONE" AND " USERS" Group from the "Bypass traverse checking" privilege
which can be accessded through "Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment" , after rebooting/updateing the Server , you may get the error.
be wised that the correct harden values for this privilege are :
On Workstations and Servers(Member server / Stand Alone )
Administrators
Backup Operators
Power Users
Users
Everyone
ON Domain Controllers
Administrators
Authenticated Users
Everyone
Good Luck
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
Good luck