various DFS Errors CAN OCCUR common internet file sharing (CIFS) PROTOCOL

Created 2009-11-25

Summary: users could not get to mapped drives for a dfs namespace when 1 server went down. To note: this problem spawned two other problems mentioned below.

I was troubleshooting other problems associated with Microsoft DFS (Distributed file system)

and while I was troubleshooting other problems with DFS I had to reboot one of the two servers which were partners in a dfs namespace server. I thought this (the reboot) would not have any impact on our users but as soon as I brought the SERVERX down and rebooted it. We started to get phone calls complaining they could not get

To the drives and file systems. The file systems such as L: T: S: AND t: ALL STARTED TO GO

DOWN AND THE USERS COULD NOT GET BACK INTO THEM UNTIL SERVERX CAME BACK ONLINE. THE ACTIVE DIRECTORY COMMON NAMESPACE WAS DEFINATELY NOT WORKING.

It appeared it may be a problem with dns, settings if the dfs manager OR even active directory,

Since the namespace is managed by active directory and not DNS. “EMPLOYEEDATA” is the

Namespace.

ARE STARTED TO THINK IT WAS SETTINGS, DNS, ACTIVE DIRECTORY ETC.....DEFINEATELY NOT THOSE THINGS.

So I did a lot of searching on the internet for this problem….HERE ARE SOME SEARCH TERMS:

MICROSOFT dfs ERROR INFORMATION ABOUT THE SHARED FOLDER CANNOT BE RETRIEVED. THIS ERROR CAN OCCUR common internet file sharing (CIFS) PROTOCOL

dfs error this shared resource does not exist CIFS

dfs ERROR INFORMATION ABOUT THE SHARED FOLDER CANNOT BE RETRIEVED. this shared resource does not exist

THE OPERATION FAILED. SEE THE ERRORS TAB FOR DETAILS

CAN NOT MAP TO THE PARNTER IN THE SHARED ACTIVE DIRECTORY BASED NAMESPACE.

THE PROBLEM OCCURRED WHEN I CLICKED ON ANY OF TARGETS (USING THE DFS MANAGEMENT) ON SERVERZ "EMPLOYEEDATA" NAMESPACE. YES, SERVERX CONTINUED TO WORK.....THE PROBLEM EXISTED WHEN I SHUT DOWN SERVERX. SERVERZ SHOULD PICK UP AND WORK. WELL IT WAS NOT.....SO THIS IS WHY I WAS CLICKING ON THE TARGETS OF SERVERZ AND GETTING THIS ERROR

THIS IS THE PROBLEM AND CORRECTION:

The directory is wrong. Actually the directory was not wrong. It was just “NOT SHARING ANYMORE”.. FOR SOME

REASON THE WINDOWS “SHARE” WAS REMOVED FROM E:\SC_DATA. WHICH CAUSED THE ERROR. TO NOTE,

DFS REPLICATION WAS STILL WORKING; IT WAS THE NAMESPACE AND THE NAMESPACE TARGETS WHICH WERE

EFFECTIVELY BROKEN.

BY ESTABLISHING THE SHARE AGAIN….EVERYTHING STARTED TO WORK AGAIN. someone in the deparment accidently removed the "sharing" of the target. ONCE i started sharing that folder on our E: drive again (with the same name which was shown in the target). Everything started to work again.

here are two other links I posted to while troubleshooting the problem. Yes this was not the problem i originally started with . the below problems is what I originally was trying to fix.

CORRECTION and original PROBLEM #1

(HOW CAN I safely delete dfsrprivate\conflictanddeletd files)

reference:

http://blogs.technet.com/askds/archive/2008/10/06/manually-clearing-the-conflictanddeleted-folder-in-dfsr.aspx

1. Open a CMD prompt as an administrator on the DFSR server.
2. Get the GUID of the Replicated Folder you want to clean:

WMIC.EXE /namespace:\\root\microsoftdfs path dfsrreplicatedfolderconfig get replicatedfolderguid,replicatedfoldername

3. Then call the CleanupConflictDirectory method:
WMIC.EXE /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo where "replicatedfolderguid='<RF GUID>’" call cleanupconflictdirectory
Example output with a sample GUID:
WMIC.EXE /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo where "replicatedfolderguid='70bebd41-d5ae-4524-b7df-4eadb89e511e’" call cleanupconflictdirectory

4. At this point the ConflictAndDeleted folder will be empty and the ConflictAndDeletedManifest.xml will be deleted.

BUT HERE ARE MY REFERENCES I SEARCHED before I found this site which answered my question
========================================================================
Dfs conflictAndDeleted exceed capacity
manually purge Dfs conflictAndDeleted exceed capacity
manually purge Dfs conflictAndDeleted files
how long Dfs conflictAndDeleted are kept
Staging folders and Conflict and Deleted folder
how long DfsrPrivate conflictAndDeleted are kept
manually shrink DfsrPrivate conflictAndDeleted
manually shrink DfsrPrivate folder for distributed file system
shrink DfsrPrivate folder how to manually
shrink DfsrPrivate folder
DfsrPrivate Folder Cleanup
can i delete files in dfsrPrivate\ConflictAndDeleted

HERE IS THe ACTuAL WEbSIte where i fouND THE ANSWER FOR THE dfsrPrivate\ConflictAndDeleted

http://social.technet.microsoft.com/Forums/en/winserverfiles/thread/1b2a1d6b-d70f-4925-af2f-6ced059e904f

CORRECTiON and original PROBLEM #2
(File Server Resource Manager service can not start) it was set to start automatically; but it does not; I can not even start it manually) ...i though this problem would have corrected the above problem with the files in the dfsrPrivate\ConflictAndDeleted not being properly disposed of.

the solution can be found on the link below (please reference my addition)

The resolution was to replace the DFSext.dll file with the one extracted from the CD using the Windows Recovery Console.]

SEARCH ENGINE REFERENCE:
file server resource manager could not start service error 193: 0xc1
file server resource manager err 193: 0xc1
64 BIT FSR manager error 193: 0xc1
microsoft server 2003 R2 file server resource manager error 193: 0xc1
windows server 2003 64 bit File Server Resource Manager is not a valid Win32 application
64 bit File Server Resource Manager is not a valid Win32 application
File Server Resource Manager is not a valid Win32 application event id 7023
File Server Resource Manager event id 7023
srmsvc does not start
srmsvc does not start Error 193
windows server 2003 r2 File server resource manager error 193

http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/ab66bad3-e9b9-4b68-9ffd-1db0efb88ca2/

Doug Lubey and Family