Jump to content


Photo

DSM - "Failed to connect to server or shared folder '<servername>'. Access is denied."


  • Please log in to reply
6 replies to this topic

#1 helpdesk.rce

helpdesk.rce

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 09 February 2015 - 09:12 AM

Hi,

 

I get error "Failed to connect to server or shared folder 'servername'. Access is denied.". I already try to troubleshoot by follow instruction in Netwrix KB.

 

1. Login using account that assign for DSM, Open MMC Snap in "Services" at problem server

                - Done and successful connected to remote server services

 

2. Map to \\servername\c$

                - Done and successful connected

 

But the error "Failed to connect to server or shared folder 'servername'. Access is denied." Still occur.

 

Thank you



#2 helpdesk.rce

helpdesk.rce

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 17 February 2015 - 09:36 AM

Admin...anybody can help me? This is URGENT



#3 dsmirnov

dsmirnov

    Advanced Member

  • Root Admin
  • PipPipPip
  • 58 posts
  • Gender:Male

Posted 17 February 2015 - 01:53 PM

Hi,

 

I get error "Failed to connect to server or shared folder 'servername'. Access is denied.". I already try to troubleshoot by follow instruction in Netwrix KB.

 

1. Login using account that assign for DSM, Open MMC Snap in "Services" at problem server

                - Done and successful connected to remote server services

 

2. Map to \\servername\c$

                - Done and successful connected

 

But the error "Failed to connect to server or shared folder 'servername'. Access is denied." Still occur.

 

Thank you

Hello,

 

did you try specifying another account, that is explicity added to Administrators group?

 

Also, can you please do the following test?

  1. Run wbemtest
  2. In a window that opens click Connect
  3. Specify the following as namespace \\%servername%\root\cimv2, where %servername% is the name of the problematic server.
  4. Click Connect

Do any errors occur dutring this?



#4 helpdesk.rce

helpdesk.rce

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 18 February 2015 - 01:53 AM

Hello,

 

did you try specifying another account, that is explicity added to Administrators group?

 

Also, can you please do the following test?

  1. Run wbemtest
  2. In a window that opens click Connect
  3. Specify the following as namespace \\%servername%\root\cimv2, where %servername% is the name of the problematic server.
  4. Click Connect

Do any errors occur dutring this?

 

Dsmirnov,

 

1. I already test use others admin account and result ok (can connect to problem server)

2. There is no error when run wbemtest and connect to problem server.

 

But still error "Failed to connect to server or shared folder '<servername>'. Access is denied."



#5 dsmirnov

dsmirnov

    Advanced Member

  • Root Admin
  • PipPipPip
  • 58 posts
  • Gender:Male

Posted 24 February 2015 - 09:47 PM

Please provide us with the following information:

  1. Configuration file C:\ProgramData\NetWrix\Disk Space Monitor\default.xml
  2. The product logs. The entire content of C:\Program Files (x86)\Netwrix\Disk Space Monitor\Tracing
  3. Example of e-mail report you get

Please zip it up and upload to www.netwrix.com/upload.

Please, reference "DSM forum" in the Subject field.



#6 helpdesk.rce

helpdesk.rce

    Newbie

  • Members
  • Pip
  • 4 posts

Posted 25 February 2015 - 01:07 AM

Dsmirnov,

 

Already upload the files



#7 dsmirnov

dsmirnov

    Advanced Member

  • Root Admin
  • PipPipPip
  • 58 posts
  • Gender:Male

Posted 25 February 2015 - 03:24 PM

Dsmirnov,

 

Already upload the files

You uploaded only logs, configuration file is missing.

 

However in the log I found the exact error message. The product cannot connect because of the Provider load failure WMI error.

 

It can happen because of WMI repository corruption on the monitored erver.

You can check it with the following command:

winmgmt /verifyrepository

 

Also the following article might be useful.

http://blogs.technet...-wmi-class.aspx

 

Most likely there is an issue with Win32_LogicalDisk WMI class






0 user(s) are reading this topic

0 members, guests, anonymous users