Jump to content


Photo

The drive record cannot be found in the mount manager's persistent name database for target host


  • Please log in to reply
7 replies to this topic

#1 jgrandin

jgrandin

    Newbie

  • Members
  • Pip
  • 1 posts
  • Gender:Male
  • Location:Suisse

Posted 22 August 2018 - 06:35 AM

I have a probleme when I tried to monitor my fileserver.

 

I have this problem:

 

Source: File Storage Audit Service  
Event ID: 6136 
Time: 22.08.2018 08:20:39 
User: N/A
Computer: XXX
Description: Monitoring plan: XXX
Item: XXX 
 
Server: XXX
Cannot resolve a drive letter for the object: \Device\HarddiskVolume24\. The drive record cannot be found in the mount manager's persistent name database for target host. 
This may lead to the loss of detected changes.  
 
I find nothing for this problem then i tried with dfs but i have an other problem :
 
Source: File Storage Audit Service  
Event ID: 6104 
Time: 22.08.2018 08:20:31 
User: N/A
Computer: XXX
Description: Monitoring plan: XXX
Item: XXX
 
Unable to process item: Failed to create DFS structure. 
Analyzed data:  
XXX
Contact Netwrix technical support at www.netwrix.com/support.html.
 
thanks in advance for help
 

 



#2 Kirill K

Kirill K

    Advanced Member

  • Administrators
  • PipPipPip
  • 119 posts
  • Gender:Male

Posted 22 August 2018 - 02:55 PM

Hi there,

 

As long as the volume(\Device\HarddiskVolume24\) is not assigned to a specific drive letter, Netwrix Auditor is unable to determine a bind between UNC path and physical path of a certain shared folder, so it does not matter how the item is specified in the settings of Monitoring Plan, whether it is specified like common shared folder or DFS Namespace, each volume has to be assigned to the drive letter, this is by design.


Best regards,
Forum Engineer
 


#3 Thierryvdv

Thierryvdv

    Newbie

  • Members
  • Pip
  • 8 posts

Posted 28 September 2018 - 09:15 AM

Hi, I have the same issue, but the path points to a shadow copy?? This with the two UNC paths that I'm monitoring (and both are reporting the same issue with the same path):

Cannot resolve a drive letter for the object: \Device\HarddiskVolumeShadowCopy637\Program Files\Internet Explorer\pris. The drive record cannot be found in the mount manager's persistent name database for target host.

 

How can I solve this?



#4 Kirill K

Kirill K

    Advanced Member

  • Administrators
  • PipPipPip
  • 119 posts
  • Gender:Male

Posted 28 September 2018 - 09:39 AM

Hi there,

 

Such warning message is expected when the shadow copy works, it creates temporary volume which is not assigned with drive letter and Netwrix Auditor returns that.

 

You should ignore the warning message or exclude it by adding the omit line at:

C:\Program Files (x86)\Netwrix Auditor\File Server Auditing\omiterrors.txt

 

*,*,*HarddiskVolumeShadowCopy*


Best regards,
Forum Engineer
 


#5 btran

btran

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 31 January 2019 - 10:17 PM

Cannot resolve a drive letter for the object: \Device\Ide\IdeDeviceP1T0L0-2. The drive record cannot be found in the mount manager's persistent name database for target host. 
This may lead to the loss of detected changes.
 
I have the same issue but the above explains it but how can we rid of this warning?


#6 Kirill K

Kirill K

    Advanced Member

  • Administrators
  • PipPipPip
  • 119 posts
  • Gender:Male

Posted 01 February 2019 - 09:38 AM

Hi there,

 

Do you know what device does belong to '\Device\Ide\IdeDeviceP1T0L0-2'?


Best regards,
Forum Engineer
 


#7 callen666

callen666

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 19 June 2019 - 04:55 PM

Hi,

 

I have a similar device to btran, and it looks like it is a virtual DVD from vmware.

How do I exclude this in omitcollectlist.txt so that the 6136 error is not flagged?



#8 Kirill K

Kirill K

    Advanced Member

  • Administrators
  • PipPipPip
  • 119 posts
  • Gender:Male

Posted 20 June 2019 - 10:18 AM

How do I exclude this in omitcollectlist.txt so that the 6136 error is not flagged?

 

Take a look above, you should you use omiterrors.txt instead, it should look like this

*,*,*IdeDevice*


Best regards,
Forum Engineer
 





0 user(s) are reading this topic

0 members, guests, anonymous users