Video Screencast Help

VxMS NTFS Mapping Plug-in Warning Event ID: 4183

Created: 29 Oct 2010 | 1 comment

Are these messages indicative of a problem or not? If so, what? If not, why?

There is an old thread on this site without useful answers (URL: https://www-secure.symantec.com/connect/forums/event-id-4183-hunh). Another thread (URL: https://www-secure.symantec.com/connect/forums/vxms-ntfs-mapping-plug-cannot-be-found) didn't help either. The latter references a tech note (URL: http://www.symantec.com/business/support/index?page=content&id=TECH87298) which does not apply since this message (below) is not on a Microsoft clustered server.

I am starting a new thread hoping someone else is getting this warning message and can explain it.

I always get four of these messages in the Windows System Log when the NetBackup media server starts its scheduled backup.

Event Type: Warning
Event Source: VxMS NTFS Mapping Plug-in
Event Category: None
Event ID: 4183
Date:  10/28/2010
Time:  6:22:37 PM
User:  N/A
Computer: PCWMS25
Description:
The description for Event ID ( 4183 ) in Source ( VxMS NTFS Mapping Plug-in ) cannot be found. Either the component that raises this event is not installed on your local computer, or the installation is corrupted. You can install or repair the component on the local computer, or contact the component manufacturer for a newer version. If the event was saved from another computer or forwarded from a remote computer, you might have to include display information with the events when saving them or when setting up the forwarding s Error: 0x00001057, in file .\NtfsFileByHandle.cpp, line 1836.

The media server is NetBackup 6.5.3 running on Windows Server 2003 R2. A search of the file system does not find a file named "NtfsFileByHandle.cpp". Googling either "VxMS NTFS Mapping Plug-in" or "NtfsFileByHandle.cpp" are also fruitless.

 

 

 

Comments 1 CommentJump to latest comment

Yasuhisa Ishikawa's picture

Once try to remove snapshots followig the technote(http://www.symantec.com/docs/TECH87298) although your servers are not in cluster.  I understand this technote as it happened typically in cluster, but might happen in non-cluster environment due to orphaned snapshot.

Running chkdsk might also effect.

When these result in vain, enable VxMS logging(http://www.symantec.com/docs/TECH72862), reproduce the error, an open a support case.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan