asked on

DFS replicated folders failing with ERROR ID 87

Hi,

I have two server 2008 R2 servers doing namespace with replication between them. Both are in separate AD sites.

The replication and namespace was working without issue until yesterday. Server A is fine and works without issue. Server B is reporting an "error ID: 87 and 4004". The folders on Server B are inaccessible. The original replicated folders (Shared, home, accounting) look like shortcut icons and in the same directory there are folders containing the data that have been named like "DFS.bac700da-1b77-4231-be27-56e4ead52068Shared". The system won't let me rename them.

If anybody can help me with this issue that would be great.

thanks

ASKER CERTIFIED SOLUTION

motnahp00

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

tnorman

ASKER

I haven't rebuilt the entire namespace but I have removed the targets from the server that is acting funny. I still can't delete the folder shortcuts with the original names.

motnahp00

DNS issues maybe?

tnorman

ASKER

I don't think so. It's strange what DFS has done here. The original replicated folders have been converted (by the system) to shortcuts that point nowhere. In the same directory it has created a second folder that has accessible data but is now named "DFS.bac700da-1b77-4231-be27-56e4ead52068Shared" instead of just "shared". These new long name folders are also shared with the same long share name. DFS can't replicate anymore because the original folders don't exist. Any Idea what is going on here?

motnahp00

I'm assuming you configured the namespace as AD integrated. Maybe something hiccuped with AD replication.

repadmin /syncall coming back clean?

tnorman

ASKER

repadmin comes back with no errors

tnorman

ASKER

Started over from scratch, and all is now working.

motnahp00

DFS replication can be funny like that. =)

motnahp00

Did you rebuild the server or the namespace / targets?