Discussion:
DFS on Server 2008, Refusing to start Replication after one of the members was rebuilt. - WMI Error
(too old to reply)
l***@gmail.com
2009-02-23 05:44:57 UTC
Permalink
Wow, I have come to hate DFS right now.. Its pretty frustrating!

So, We had a bunch of folders, replicating between two servers, lets
call them Server1 and Server2...
Then, last week, Server2 packed it in.

Both servers are Windows Server 2008. Both are 32bit.
I've gone through, and made sure that all the existing file shares are
shared again on Server2.

I re-created the namespace (twice, with different names incase it was
Active Directory), and re-created the folders in the Namespace, and
then the replication of the two folders.

Whether it is server1 or server2 that is set as the primary server, it
appears that replication just NEVER starts?

Running a Health Report on the Replication point shows the following:
SERVER1 (1 error) (View Server Details)
Communication errors are preventing replication with partner
SERVER2.

SERVER2 (1 error) (View Server Details)
Cannot access the local WMI repository.


All I can think of is that it keeps coming back to WMI Error ID:
0x80041002, which is this mess:
"(WBEM_E_NOT_FOUND) Object cannot be found"
I have looked at trying to fix WMI. I've run WMIDiag (added log file
below), and even run WMIDiag -WriteInRepository
I can't figure out what to do with the whole reconstruction thing,
because I can't tell what file its missing, just that it can't find
the object?

No where has Server 2008 fixes for this problem. I'm sure that DFS is
supposed to work better than this! Any help massively appreciated!

DNS name: server1.xxxxxxxxx.local
Domain name: xxxxxxxxxx.local
Reference domain controller: server3.xxxxxxx.local
ERRORS (There is 1 error to report)

Communication errors are preventing replication with partner
SERVER2.
Affected replicated folders: All replicated folders on this server.
Description: DFS Replication cannot replicate with partner SERVER2
for replication group xxxxxxxxx.local\fileserver\foldername. The
partner did not recognize the connection or the replication group
configuration. The DFS Replication service used partner DNS name
Server2.xxxxxxxx.local, IP address 192.168.x.x, and WINS address
Server2 but failed with error ID: 9026 (The connection is invalid).
Event ID: 5012
Last occurred: Monday, 23 February 2009
Suggested action: This error can occur when the partner does not
have the latest DFS Replication configuration information. The service
will retry the connection periodically. For troubleshooting
information, , see The Microsoft Web Site.

WARNINGS (There is 1 warning to report)

This member is waiting for initial replication for replicated folder
foldername.
Affected replicated folders: foldername
Description: This member is waiting for initial replication for
replicated folder foldername and is not currently participating in
replication. This delay can occur because the member is waiting for
the DFS Replication service to retrieve replication settings from
Active Directory Domain Services. After the member detects that it is
part of replication group, the member will begin initial
replication.
Last occurred: Monday, 23 February 2009
Suggested action: Replication will begin after initial replication
is complete. If this state does not change, see The Microsoft Web
Site.

-------------------------------------------------------------------------------------------------------------------------

DNS name: server2.xxxxxxxxxx.local
Domain name: xxxxxxxxxxx.local
Reference domain controller: --
ERRORS (There is 1 error to report)

Cannot access the local WMI repository.
Affected replicated folders: All replicated folders on this server.
Description: Due to the following error, the DFS Replication
reporting mechanism cannot access the WMI (Windows Management
Instrumentation) namespace to retrieve certain reporting information.
Error ID: 0x80041002.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting WMI errors,
see WMI help.

WARNINGS (There is 1 warning to report)

Reference member returned no replicated folders.
Description: Backlog calculations cannot be performed because the
reference member returned zero replicated folders.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting backlog
problems, see The Microsoft Web Site.



27890 12:21:50 (0) ** WMIDiag v2.0 started on Monday, February 23,
2009 at 12:06.
27891 12:21:50 (0) **
27892 12:21:50 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
27893 12:21:50 (0) **
27894 12:21:50 (0) ** This script is not supported under any Microsoft
standard support program or service.
27895 12:21:50 (0) ** The script is provided AS IS without warranty of
any kind. Microsoft further disclaims all
27896 12:21:50 (0) ** implied warranties including, without
limitation, any implied warranties of merchantability
27897 12:21:50 (0) ** or of fitness for a particular purpose. The
entire risk arising out of the use or performance
27898 12:21:50 (0) ** of the scripts and documentation remains with
you. In no event shall Microsoft, its authors,
27899 12:21:50 (0) ** or anyone else involved in the creation,
production, or delivery of the script be liable for
27900 12:21:50 (0) ** any damages whatsoever (including, without
limitation, damages for loss of business profits,
27901 12:21:50 (0) ** business interruption, loss of business
information, or other pecuniary loss) arising out of
27902 12:21:50 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
27903 12:21:50 (0) ** of the possibility of such damages.
27904 12:21:50 (0) **
27905 12:21:50 (0) **
27906 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27907 12:21:50 (0) **
----------------------------------------------------- WMI REPORT:
BEGIN ----------------------------------------------------------
27908 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27909 12:21:50 (0) **
27910 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27911 12:21:50 (0) ** Windows Longhorn Server - No service pack - 32-
bit (6001) - User 'xxxxxxxxxxxx\ADMINISTRATOR' on computer 'SERVER2'.
27912 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27913 12:21:50 (0) **
Environment: ........................................................................................................
OK..
27914 12:21:50 (0) ** System
drive: .......................................................................................................
C: (Disk #0 Partition #0).
27915 12:21:50 (0) ** Drive
type: .........................................................................................................
IDE (SAMSUNG HD753LJ ATA Device).
27916 12:21:50 (0) ** INFO: The following UNEXPECTED binary files are/
is found in the WBEM folder: ........................................
2 FILE(S)!
27917 12:21:50 (0) ** - DNSPROV.DLL, 203776
bytes, 1/19/2008 10:24:47 PM
27918 12:21:50 (0) ** - SERVERCOMPPROV.DLL, 32768
bytes, 1/19/2008 10:23:36 PM
27919 12:21:50 (0) ** => This list is provided for information.
Unexpected binary file(s) in 'C:\WINDOWS\SYSTEM32\WBEM\'
27920 12:21:50 (0) ** do not necessarily represent an error. For
instance, the file(s) listed can be added by
27921 12:21:50 (0) ** any applications implementing WMI providers.
27922 12:21:50 (0) ** => NO ACTION is required.
27923 12:21:50 (0) **
27924 12:21:50 (1) !! ERROR: The following WMI system file(s) is/are
missing: .............................................................
3 ERROR(S)!
27925 12:21:50 (0) ** - C:\Windows\System32\WBEM\framedyn.dll
27926 12:21:50 (0) ** - C:\Windows\System32\WBEM\provthrd.dll
27927 12:21:50 (0) ** - C:\Windows\System32\WBEM\wbemcomn.dll
27928 12:21:50 (0) ** => Recopy from a working system the missing WMI
system files to 'C:\WINDOWS\SYSTEM32\WBEM\'
27929 12:21:50 (0) **
27930 12:21:50 (0) ** There are no missing WMI repository
files: ..........................................................................
OK.
27931 12:21:50 (0) ** WMI repository
state: ...............................................................................................
CONSISTENT.
27932 12:21:50 (0) ** BEFORE running WMIDiag:
27933 12:21:50 (0) ** The WMI repository has a size
of: ...................................................................................
26 MB.
27934 12:21:50 (0) ** - Disk free space on
'C:': ..........................................................................................
10916 MB.
27935 12:21:50 (0) ** - INDEX.BTR, 3309568
bytes, 2/23/2009 11:37:33 AM
27936 12:21:50 (0) ** - MAPPING1.MAP, 75372
bytes, 2/23/2009 11:29:33 AM
27937 12:21:50 (0) ** - MAPPING2.MAP, 75372
bytes, 2/23/2009 11:37:34 AM
27938 12:21:50 (0) ** - OBJECTS.DATA, 23576576
bytes, 2/23/2009 11:37:33 AM
27939 12:21:50 (0) ** AFTER running WMIDiag:
27940 12:21:50 (0) ** The WMI repository has a size
of: ...................................................................................
26 MB.
27941 12:21:50 (0) ** - Disk free space on
'C:': ..........................................................................................
10909 MB.
27942 12:21:50 (0) ** - INDEX.BTR, 3309568
bytes, 2/23/2009 12:17:04 PM
27943 12:21:50 (0) ** - MAPPING1.MAP, 75372
bytes, 2/23/2009 12:17:04 PM
27944 12:21:50 (0) ** - MAPPING2.MAP, 75372
bytes, 2/23/2009 11:37:34 AM
27945 12:21:50 (0) ** - OBJECTS.DATA, 23576576
bytes, 2/23/2009 12:17:04 PM
27946 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27947 12:21:50 (0) ** INFO: Windows Firewall
status: ......................................................................................
ENABLED.
27948 12:21:50 (0) ** Windows Firewall
Profile: ...........................................................................................
DOMAIN.
27949 12:21:50 (0) ** Inbound connections that do not match a rule
BLOCKED: ...............................................................
ENABLED.
27950 12:21:50 (0) ** => This will prevent any WMI remote connectivity
to this computer except
27951 12:21:50 (0) ** if the following three inbound rules are
ENABLED and non-BLOCKING:
27952 12:21:50 (0) ** - 'Windows Management Instrumentation (DCOM-
In)'
27953 12:21:50 (0) ** - 'Windows Management Instrumentation (WMI-
In)'
27954 12:21:50 (0) ** - 'Windows Management Instrumentation (ASync-
In)'
27955 12:21:50 (0) ** Verify the reported status for each of these
three inbound rules below.
27956 12:21:50 (0) **
27957 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (WMI)' GROUP
rule: ............................................. ENABLED.
27958 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (ASync-In)'
rule: .............................................. ENABLED.
27959 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (WMI-Out)'
rule: ............................................... ENABLED.
27960 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (WMI-In)'
rule: ................................................ ENABLED.
27961 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (DCOM-In)'
rule: ............................................... ENABLED.
27962 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27963 12:21:50 (0) ** DCOM
Status: ........................................................................................................
OK.
27964 12:21:50 (0) ** WMI registry
setup: .................................................................................................
OK.
27965 12:21:50 (0) ** INFO: WMI service has
dependents: ...................................................................................
1 SERVICE(S)!
27966 12:21:50 (0) ** - Internet Connection Sharing (ICS)
(SHAREDACCESS, StartMode='Disabled')
27967 12:21:50 (0) ** => If the WMI service is stopped, the listed
service(s) will have to be stopped as well.
27968 12:21:50 (0) ** Note: If the service is marked with (*), it
means that the service/application uses WMI but
27969 12:21:50 (0) ** there is no hard dependency on WMI.
However, if the WMI service is stopped,
27970 12:21:50 (0) ** this can prevent the service/
application to work as expected.
27971 12:21:50 (0) **
27972 12:21:50 (0) ** RPCSS
service: ......................................................................................................
OK (Already started).
27973 12:21:50 (0) ** WINMGMT
service: ....................................................................................................
OK (Already started).
27974 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27975 12:21:50 (0) ** WMI service DCOM
setup: .............................................................................................
OK.
27976 12:21:50 (0) ** WMI components DCOM
registrations: ..................................................................................
OK.
27977 12:21:50 (0) ** WMI ProgID
registrations: ...........................................................................................
OK.
27978 12:21:50 (0) ** WMI provider DCOM
registrations: ....................................................................................
OK.
27979 12:21:50 (0) ** WMI provider CIM
registrations: .....................................................................................
OK.
27980 12:21:50 (0) ** WMI provider
CLSIDs: ................................................................................................
OK.
27981 12:21:50 (2) !! WARNING: Some WMI providers EXE/DLL file(s) are
missing: ............................................................
1 WARNING(S)!
27982 12:21:50 (0) ** - ROOT/MICROSOFTACTIVEDIRECTORY, ReplProv1,
replprov.dll
27983 12:21:50 (0) ** => This will make any operations related to the
WMI class supported by the provider(s) to fail.
27984 12:21:50 (0) ** This can be due to:
27985 12:21:50 (0) ** - the de-installation of the software.
27986 12:21:50 (0) ** - the deletion of some files.
27987 12:21:50 (0) ** => If the software has been de-installed
intentionally, then this information must be
27988 12:21:50 (0) ** removed from the WMI repository. You can use
the 'WMIC.EXE' command to remove
27989 12:21:50 (0) ** the provider registration data.
27990 12:21:50 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT
\MICROSOFTACTIVEDIRECTORY path __Win32Provider Where Name='ReplProv1'
DELETE'
27991 12:21:50 (0) ** => If not, you must restore a copy of the
missing provider EXE/DLL file(s) as indicated by the path.
27992 12:21:50 (0) ** You can retrieve the missing file from:
27993 12:21:50 (0) ** - A backup.
27994 12:21:50 (0) ** - The Windows CD.
27995 12:21:50 (0) ** - Another Windows installation using the same
version and service pack level of the examined system.
27996 12:21:50 (0) ** - The original CD or software package
installing this WMI provider.
27997 12:21:50 (0) **
27998 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27999 12:21:50 (0) ** INFO: User Account Control
(UAC): ...................................................................................
ENABLED.
28000 12:21:50 (0) ** => WMI tasks requiring Administrative privileges
on this computer MUST run in an elevated context.
28001 12:21:50 (0) ** i.e. You can start your scripts or WMIC
commands from an elevated command
28002 12:21:50 (0) ** prompt by right clicking on the 'Command
Prompt' icon in the Start Menu and
28003 12:21:50 (0) ** selecting 'Run as Administrator'.
28004 12:21:50 (0) ** i.e. You can also execute the WMI scripts or
WMIC commands as a task
28005 12:21:50 (0) ** in the Task Scheduler within the right
security context.
28006 12:21:50 (0) **
28007 12:21:50 (0) ** INFO: Local Account
Filtering: ......................................................................................
ENABLED.
28008 12:21:50 (0) ** => WMI tasks remotely accessing WMI information
on this computer and requiring Administrative
28009 12:21:50 (0) ** privileges MUST use a DOMAIN account part of
the Local Administrators group of this computer
28010 12:21:50 (0) ** to ensure that administrative privileges are
granted. If a Local User account is used for remote
28011 12:21:50 (0) ** accesses, it will be reduced to a plain user
(filtered token), even if it is part of the Local Administrators
group.
28012 12:21:50 (0) **
28013 12:21:50 (0) ** Overall DCOM security
status: .......................................................................................
OK.
28014 12:21:50 (0) ** Overall WMI security
status: ........................................................................................
OK.
28015 12:21:50 (0) ** - Started at 'Root'
--------------------------------------------------------------------------------------------------------------
28016 12:21:50 (0) ** INFO: WMI permanent SUBSCRIPTION
(S): ................................................................................
1.
28017 12:21:50 (0) ** - ROOT/SUBSCRIPTION,
NTEventLogEventConsumer.Name="SCM Event Log Consumer".
28018 12:21:50 (0) ** 'select * from MSFT_SCMEventLogEvent'
28019 12:21:50 (0) **
28020 12:21:50 (0) ** WMI TIMER instruction
(s): ...........................................................................................
NONE.
28021 12:21:50 (0) ** INFO: WMI namespace(s) requiring PACKET
PRIVACY: ....................................................................
2 NAMESPACE(S)!
28022 12:21:50 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
28023 12:21:50 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
28024 12:21:50 (0) ** => When remotely connecting, the namespace(s)
listed require(s) the WMI client to
28025 12:21:50 (0) ** use an encrypted connection by specifying the
PACKET PRIVACY authentication level.
28026 12:21:50 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy
flags)
28027 12:21:50 (0) ** i.e. 'WMIC.EXE /NODE:"SERVER2" /
AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\CIMV2\TERMINALSERVICES Class
__SystemSecurity'
28028 12:21:50 (0) **
28029 12:21:50 (0) ** WMI MONIKER
CONNECTIONS: ............................................................................................
OK.
28030 12:21:50 (0) ** WMI
CONNECTIONS: ....................................................................................................
OK.
28031 12:21:50 (1) !! ERROR: WMI GET operation errors
reported: ...........................................................................
2 ERROR(S)!
28032 12:21:50 (0) ** - Root/CIMV2,
Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 -
(WBEM_E_NOT_FOUND) Object cannot be found.
28033 12:21:50 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMIPERFINST.MOF'
28034 12:21:50 (0) ** - Root/CIMV2,
Win32_PerfRawData_TermService_TerminalServices, 0x80041002 -
(WBEM_E_NOT_FOUND) Object cannot be found.
28035 12:21:50 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMIPERFINST.MOF'
28036 12:21:50 (0) ** => When a WMI performance class is missing (i.e.
'Win32_PerfRawData_TermService_TerminalServices'), it is generally due
to
28037 12:21:50 (0) ** a lack of buffer refresh of the WMI class
provider exposing the WMI performance counters.
28038 12:21:50 (0) ** You can refresh the WMI class provider buffer
with the following command:
28039 12:21:50 (0) **
28040 12:21:50 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
28041 12:21:50 (0) **
28042 12:21:50 (0) ** WMI MOF
representations: ............................................................................................
OK.
28043 12:21:50 (0) ** WMI QUALIFIER access
operations: ....................................................................................
OK.
28044 12:21:50 (0) ** WMI ENUMERATION
operations: .........................................................................................
OK.
28045 12:21:50 (0) ** WMI EXECQUERY
operations: ...........................................................................................
OK.
28046 12:21:50 (2) !! WARNING: WMI GET VALUE operation errors
reported: ...................................................................
5 WARNING(S)!
28047 12:21:50 (0) ** - Root, Instance:
__EventConsumerProviderCacheControl=@, Property:
ClearAfter='00000000000030.000000:000' (Expected
default='00000000000500.000000:000').
28048 12:21:50 (0) ** - Root, Instance: __EventProviderCacheControl=@,
Property: ClearAfter='00000000000030.000000:000' (Expected
default='00000000000500.000000:000').
28049 12:21:50 (0) ** - Root, Instance: __EventSinkCacheControl=@,
Property: ClearAfter='00000000000015.000000:000' (Expected
default='00000000000230.000000:000').
28050 12:21:50 (0) ** - Root, Instance:
__ObjectProviderCacheControl=@, Property:
ClearAfter='00000000000030.000000:000' (Expected
default='00000000000500.000000:000').
28051 12:21:50 (0) ** - Root, Instance:
__PropertyProviderCacheControl=@, Property:
ClearAfter='00000000000030.000000:000' (Expected
default='00000000000500.000000:000').
28052 12:21:50 (0) **
28053 12:21:50 (0) ** WMI WRITE
operations: ...............................................................................................
NOT TESTED.
28054 12:21:50 (0) ** WMI PUT
operations: .................................................................................................
NOT TESTED.
28055 12:21:50 (0) ** WMI DELETE
operations: ..............................................................................................
NOT TESTED.
28056 12:21:50 (0) ** WMI static instances
retrieved: .....................................................................................
1730.
28057 12:21:50 (0) ** WMI dynamic instances
retrieved: ....................................................................................
0.
28058 12:21:50 (0) ** WMI instance request cancellations (to limit
performance
impact): ................................................... 1.
28059 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28060 12:21:50 (0) ** # of Event Log events BEFORE WMIDiag execution
since the last 20 day(s):
28061 12:21:50 (0) **
DCOM: .............................................................................................................
0.
28062 12:21:50 (0) **
WINMGMT: ..........................................................................................................
0.
28063 12:21:50 (0) **
WMIADAPTER: .......................................................................................................
0.
28064 12:21:50 (0) **
28065 12:21:50 (0) ** # of additional Event Log events AFTER WMIDiag
execution:
28066 12:21:50 (0) **
DCOM: .............................................................................................................
0.
28067 12:21:50 (0) **
WINMGMT: ..........................................................................................................
0.
28068 12:21:50 (0) **
WMIADAPTER: .......................................................................................................
0.
28069 12:21:50 (0) **
28070 12:21:50 (0) ** 2 error(s) 0x80041002 - (WBEM_E_NOT_FOUND)
Object cannot be found
28071 12:21:50 (0) ** => This error is typically a WMI error. This WMI
error is due to:
28072 12:21:50 (0) ** - a missing WMI class definition or object.
28073 12:21:50 (0) ** (See any GET, ENUMERATION, EXECQUERY and
GET VALUE operation failures).
28074 12:21:50 (0) ** You can correct the missing class
definitions by:
28075 12:21:50 (0) ** - Manually recompiling the MOF file(s) with
the 'MOFCOMP <FileName.MOF>' command.
28076 12:21:50 (0) ** Note: You can build a list of classes in
relation with their WMI provider and MOF file with WMIDiag.
28077 12:21:50 (0) ** (This list can be built on a similar
and working WMI Windows installation)
28078 12:21:50 (0) ** The following command line must be
used:
28079 12:21:50 (0) ** i.e. 'WMIDiag
CorrelateClassAndProvider'
28080 12:21:50 (0) ** Note: When a WMI performance class is
missing, you can manually resynchronize performance counters
28081 12:21:50 (0) ** with WMI by starting the ADAP
process.
28082 12:21:50 (0) ** - a WMI repository corruption.
28083 12:21:50 (0) ** In such a case, you must rerun WMIDiag with
'WriteInRepository' parameter
28084 12:21:50 (0) ** to validate the WMI repository operations.
28085 12:21:50 (0) ** Note: ENSURE you are an administrator with
FULL access to WMI EVERY namespaces of the computer before
28086 12:21:50 (0) ** executing the WriteInRepository
command. To write temporary data from the Root namespace, use:
28087 12:21:50 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
28088 12:21:50 (0) ** - If the WriteInRepository command fails,
while being an Administrator with ALL accesses to ALL namespaces
28089 12:21:50 (0) ** the WMI repository must be reconstructed.
28090 12:21:50 (0) ** Note: The WMI repository reconstruction
requires to locate all MOF files needed to rebuild the repository,
28091 12:21:50 (0) ** otherwise some applications may fail
after the reconstruction.
28092 12:21:50 (0) ** This can be achieved with the following
command:
28093 12:21:50 (0) ** i.e. 'WMIDiag ShowMOFErrors'
28094 12:21:50 (0) ** Note: The repository reconstruction must be a
LAST RESORT solution and ONLY after executing
28095 12:21:50 (0) ** ALL fixes previously mentioned.
28096 12:21:50 (2) !! WARNING: Static information stored by external
applications in the repository will be LOST! (i.e. SMS Inventory)
28097 12:21:50 (0) **
28098 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28099 12:21:50 (0) ** WMI Registry key
setup: .............................................................................................
OK.
28100 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28101 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28102 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28103 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28104 12:21:50 (0) **
28105 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28106 12:21:50 (0) **
------------------------------------------------------ WMI REPORT: END
-----------------------------------------------------------
l***@gmail.com
2009-02-23 05:50:02 UTC
Permalink
Trying some followup checks.

Opening WBEMTest and trying to connect to root\MicrosoftDFSR I get a
response: Number 0x8004100e, Facility WMI, Description Invalid
Namespace.
Isaac Oben -MCSE, MCITP
2009-02-23 09:27:34 UTC
Permalink
Hello,
Looking at your error I am thinking it might be namespace related issue. DFS
might still be looking to communicate with the older namespace which no
longer exists, hence giving you the communication error...You can try to
restart both the dfsrs and the dfssvc and see if this helps resolve the
issue. I meant to ask, is this a domain base or standalone dfs?

Isaac
Post by l***@gmail.com
Wow, I have come to hate DFS right now.. Its pretty frustrating!
So, We had a bunch of folders, replicating between two servers, lets
call them Server1 and Server2...
Then, last week, Server2 packed it in.
Both servers are Windows Server 2008. Both are 32bit.
I've gone through, and made sure that all the existing file shares are
shared again on Server2.
I re-created the namespace (twice, with different names incase it was
Active Directory), and re-created the folders in the Namespace, and
then the replication of the two folders.
Whether it is server1 or server2 that is set as the primary server, it
appears that replication just NEVER starts?
SERVER1 (1 error) (View Server Details)
Communication errors are preventing replication with partner
SERVER2.
SERVER2 (1 error) (View Server Details)
Cannot access the local WMI repository.
"(WBEM_E_NOT_FOUND) Object cannot be found"
I have looked at trying to fix WMI. I've run WMIDiag (added log file
below), and even run WMIDiag -WriteInRepository
I can't figure out what to do with the whole reconstruction thing,
because I can't tell what file its missing, just that it can't find
the object?
No where has Server 2008 fixes for this problem. I'm sure that DFS is
supposed to work better than this! Any help massively appreciated!
DNS name: server1.xxxxxxxxx.local
Domain name: xxxxxxxxxx.local
Reference domain controller: server3.xxxxxxx.local
ERRORS (There is 1 error to report)
Communication errors are preventing replication with partner
SERVER2.
Affected replicated folders: All replicated folders on this server.
Description: DFS Replication cannot replicate with partner SERVER2
for replication group xxxxxxxxx.local\fileserver\foldername. The
partner did not recognize the connection or the replication group
configuration. The DFS Replication service used partner DNS name
Server2.xxxxxxxx.local, IP address 192.168.x.x, and WINS address
Server2 but failed with error ID: 9026 (The connection is invalid).
Event ID: 5012
Last occurred: Monday, 23 February 2009
Suggested action: This error can occur when the partner does not
have the latest DFS Replication configuration information. The service
will retry the connection periodically. For troubleshooting
information, , see The Microsoft Web Site.
WARNINGS (There is 1 warning to report)
This member is waiting for initial replication for replicated folder
foldername.
Affected replicated folders: foldername
Description: This member is waiting for initial replication for
replicated folder foldername and is not currently participating in
replication. This delay can occur because the member is waiting for
the DFS Replication service to retrieve replication settings from
Active Directory Domain Services. After the member detects that it is
part of replication group, the member will begin initial
replication.
Last occurred: Monday, 23 February 2009
Suggested action: Replication will begin after initial replication
is complete. If this state does not change, see The Microsoft Web
Site.
-------------------------------------------------------------------------------------------------------------------------
DNS name: server2.xxxxxxxxxx.local
Domain name: xxxxxxxxxxx.local
Reference domain controller: --
ERRORS (There is 1 error to report)
Cannot access the local WMI repository.
Affected replicated folders: All replicated folders on this server.
Description: Due to the following error, the DFS Replication
reporting mechanism cannot access the WMI (Windows Management
Instrumentation) namespace to retrieve certain reporting information.
Error ID: 0x80041002.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting WMI errors,
see WMI help.
WARNINGS (There is 1 warning to report)
Reference member returned no replicated folders.
Description: Backlog calculations cannot be performed because the
reference member returned zero replicated folders.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting backlog
problems, see The Microsoft Web Site.
27890 12:21:50 (0) ** WMIDiag v2.0 started on Monday, February 23,
2009 at 12:06.
27891 12:21:50 (0) **
27892 12:21:50 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
27893 12:21:50 (0) **
27894 12:21:50 (0) ** This script is not supported under any Microsoft
standard support program or service.
27895 12:21:50 (0) ** The script is provided AS IS without warranty of
any kind. Microsoft further disclaims all
27896 12:21:50 (0) ** implied warranties including, without
limitation, any implied warranties of merchantability
27897 12:21:50 (0) ** or of fitness for a particular purpose. The
entire risk arising out of the use or performance
27898 12:21:50 (0) ** of the scripts and documentation remains with
you. In no event shall Microsoft, its authors,
27899 12:21:50 (0) ** or anyone else involved in the creation,
production, or delivery of the script be liable for
27900 12:21:50 (0) ** any damages whatsoever (including, without
limitation, damages for loss of business profits,
27901 12:21:50 (0) ** business interruption, loss of business
information, or other pecuniary loss) arising out of
27902 12:21:50 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
27903 12:21:50 (0) ** of the possibility of such damages.
27904 12:21:50 (0) **
27905 12:21:50 (0) **
27906 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27907 12:21:50 (0) **
BEGIN ----------------------------------------------------------
27908 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27909 12:21:50 (0) **
27910 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27911 12:21:50 (0) ** Windows Longhorn Server - No service pack - 32-
bit (6001) - User 'xxxxxxxxxxxx\ADMINISTRATOR' on computer 'SERVER2'.
27912 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27913 12:21:50 (0) **
........................................................................................................
OK..
27914 12:21:50 (0) ** System
.......................................................................................................
C: (Disk #0 Partition #0).
27915 12:21:50 (0) ** Drive
.........................................................................................................
IDE (SAMSUNG HD753LJ ATA Device).
27916 12:21:50 (0) ** INFO: The following UNEXPECTED binary files are/
is found in the WBEM folder: ........................................
2 FILE(S)!
27917 12:21:50 (0) ** - DNSPROV.DLL, 203776
bytes, 1/19/2008 10:24:47 PM
27918 12:21:50 (0) ** - SERVERCOMPPROV.DLL, 32768
bytes, 1/19/2008 10:23:36 PM
27919 12:21:50 (0) ** => This list is provided for information.
Unexpected binary file(s) in 'C:\WINDOWS\SYSTEM32\WBEM\'
27920 12:21:50 (0) ** do not necessarily represent an error. For
instance, the file(s) listed can be added by
27921 12:21:50 (0) ** any applications implementing WMI providers.
27922 12:21:50 (0) ** => NO ACTION is required.
27923 12:21:50 (0) **
27924 12:21:50 (1) !! ERROR: The following WMI system file(s) is/are
missing: .............................................................
3 ERROR(S)!
27925 12:21:50 (0) ** - C:\Windows\System32\WBEM\framedyn.dll
27926 12:21:50 (0) ** - C:\Windows\System32\WBEM\provthrd.dll
27927 12:21:50 (0) ** - C:\Windows\System32\WBEM\wbemcomn.dll
27928 12:21:50 (0) ** => Recopy from a working system the missing WMI
system files to 'C:\WINDOWS\SYSTEM32\WBEM\'
27929 12:21:50 (0) **
27930 12:21:50 (0) ** There are no missing WMI repository
..........................................................................
OK.
27931 12:21:50 (0) ** WMI repository
...............................................................................................
CONSISTENT.
27933 12:21:50 (0) ** The WMI repository has a size
...................................................................................
26 MB.
27934 12:21:50 (0) ** - Disk free space on
..........................................................................................
10916 MB.
27935 12:21:50 (0) ** - INDEX.BTR, 3309568
bytes, 2/23/2009 11:37:33 AM
27936 12:21:50 (0) ** - MAPPING1.MAP, 75372
bytes, 2/23/2009 11:29:33 AM
27937 12:21:50 (0) ** - MAPPING2.MAP, 75372
bytes, 2/23/2009 11:37:34 AM
27938 12:21:50 (0) ** - OBJECTS.DATA, 23576576
bytes, 2/23/2009 11:37:33 AM
27940 12:21:50 (0) ** The WMI repository has a size
...................................................................................
26 MB.
27941 12:21:50 (0) ** - Disk free space on
..........................................................................................
10909 MB.
27942 12:21:50 (0) ** - INDEX.BTR, 3309568
bytes, 2/23/2009 12:17:04 PM
27943 12:21:50 (0) ** - MAPPING1.MAP, 75372
bytes, 2/23/2009 12:17:04 PM
27944 12:21:50 (0) ** - MAPPING2.MAP, 75372
bytes, 2/23/2009 11:37:34 AM
27945 12:21:50 (0) ** - OBJECTS.DATA, 23576576
bytes, 2/23/2009 12:17:04 PM
27946 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27947 12:21:50 (0) ** INFO: Windows Firewall
......................................................................................
ENABLED.
27948 12:21:50 (0) ** Windows Firewall
...........................................................................................
DOMAIN.
27949 12:21:50 (0) ** Inbound connections that do not match a rule
BLOCKED: ...............................................................
ENABLED.
27950 12:21:50 (0) ** => This will prevent any WMI remote connectivity
to this computer except
27951 12:21:50 (0) ** if the following three inbound rules are
27952 12:21:50 (0) ** - 'Windows Management Instrumentation (DCOM-
In)'
27953 12:21:50 (0) ** - 'Windows Management Instrumentation (WMI-
In)'
27954 12:21:50 (0) ** - 'Windows Management Instrumentation (ASync-
In)'
27955 12:21:50 (0) ** Verify the reported status for each of these
three inbound rules below.
27956 12:21:50 (0) **
27957 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (WMI)' GROUP
rule: ............................................. ENABLED.
27958 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (ASync-In)'
rule: .............................................. ENABLED.
27959 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (WMI-Out)'
rule: ............................................... ENABLED.
27960 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (WMI-In)'
rule: ................................................ ENABLED.
27961 12:21:50 (0) ** Windows Firewall 'Windows Management
Instrumentation (DCOM-In)'
rule: ............................................... ENABLED.
27962 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27963 12:21:50 (0) ** DCOM
........................................................................................................
OK.
27964 12:21:50 (0) ** WMI registry
.................................................................................................
OK.
27965 12:21:50 (0) ** INFO: WMI service has
...................................................................................
1 SERVICE(S)!
27966 12:21:50 (0) ** - Internet Connection Sharing (ICS)
(SHAREDACCESS, StartMode='Disabled')
27967 12:21:50 (0) ** => If the WMI service is stopped, the listed
service(s) will have to be stopped as well.
27968 12:21:50 (0) ** Note: If the service is marked with (*), it
means that the service/application uses WMI but
27969 12:21:50 (0) ** there is no hard dependency on WMI.
However, if the WMI service is stopped,
27970 12:21:50 (0) ** this can prevent the service/
application to work as expected.
27971 12:21:50 (0) **
27972 12:21:50 (0) ** RPCSS
......................................................................................................
OK (Already started).
27973 12:21:50 (0) ** WINMGMT
....................................................................................................
OK (Already started).
27974 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27975 12:21:50 (0) ** WMI service DCOM
.............................................................................................
OK.
27976 12:21:50 (0) ** WMI components DCOM
..................................................................................
OK.
27977 12:21:50 (0) ** WMI ProgID
...........................................................................................
OK.
27978 12:21:50 (0) ** WMI provider DCOM
....................................................................................
OK.
27979 12:21:50 (0) ** WMI provider CIM
.....................................................................................
OK.
27980 12:21:50 (0) ** WMI provider
................................................................................................
OK.
27981 12:21:50 (2) !! WARNING: Some WMI providers EXE/DLL file(s) are
missing: ............................................................
1 WARNING(S)!
27982 12:21:50 (0) ** - ROOT/MICROSOFTACTIVEDIRECTORY, ReplProv1,
replprov.dll
27983 12:21:50 (0) ** => This will make any operations related to the
WMI class supported by the provider(s) to fail.
27985 12:21:50 (0) ** - the de-installation of the software.
27986 12:21:50 (0) ** - the deletion of some files.
27987 12:21:50 (0) ** => If the software has been de-installed
intentionally, then this information must be
27988 12:21:50 (0) ** removed from the WMI repository. You can use
the 'WMIC.EXE' command to remove
27989 12:21:50 (0) ** the provider registration data.
27990 12:21:50 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT
\MICROSOFTACTIVEDIRECTORY path __Win32Provider Where Name='ReplProv1'
DELETE'
27991 12:21:50 (0) ** => If not, you must restore a copy of the
missing provider EXE/DLL file(s) as indicated by the path.
27993 12:21:50 (0) ** - A backup.
27994 12:21:50 (0) ** - The Windows CD.
27995 12:21:50 (0) ** - Another Windows installation using the same
version and service pack level of the examined system.
27996 12:21:50 (0) ** - The original CD or software package
installing this WMI provider.
27997 12:21:50 (0) **
27998 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27999 12:21:50 (0) ** INFO: User Account Control
...................................................................................
ENABLED.
28000 12:21:50 (0) ** => WMI tasks requiring Administrative privileges
on this computer MUST run in an elevated context.
28001 12:21:50 (0) ** i.e. You can start your scripts or WMIC
commands from an elevated command
28002 12:21:50 (0) ** prompt by right clicking on the 'Command
Prompt' icon in the Start Menu and
28003 12:21:50 (0) ** selecting 'Run as Administrator'.
28004 12:21:50 (0) ** i.e. You can also execute the WMI scripts or
WMIC commands as a task
28005 12:21:50 (0) ** in the Task Scheduler within the right
security context.
28006 12:21:50 (0) **
28007 12:21:50 (0) ** INFO: Local Account
......................................................................................
ENABLED.
28008 12:21:50 (0) ** => WMI tasks remotely accessing WMI information
on this computer and requiring Administrative
28009 12:21:50 (0) ** privileges MUST use a DOMAIN account part of
the Local Administrators group of this computer
28010 12:21:50 (0) ** to ensure that administrative privileges are
granted. If a Local User account is used for remote
28011 12:21:50 (0) ** accesses, it will be reduced to a plain user
(filtered token), even if it is part of the Local Administrators
group.
28012 12:21:50 (0) **
28013 12:21:50 (0) ** Overall DCOM security
.......................................................................................
OK.
28014 12:21:50 (0) ** Overall WMI security
........................................................................................
OK.
28015 12:21:50 (0) ** - Started at 'Root'
--------------------------------------------------------------------------------------------------------------
28016 12:21:50 (0) ** INFO: WMI permanent SUBSCRIPTION
................................................................................
1.
28017 12:21:50 (0) ** - ROOT/SUBSCRIPTION,
NTEventLogEventConsumer.Name="SCM Event Log Consumer".
28018 12:21:50 (0) ** 'select * from MSFT_SCMEventLogEvent'
28019 12:21:50 (0) **
28020 12:21:50 (0) ** WMI TIMER instruction
...........................................................................................
NONE.
28021 12:21:50 (0) ** INFO: WMI namespace(s) requiring PACKET
....................................................................
2 NAMESPACE(S)!
28022 12:21:50 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
28023 12:21:50 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
28024 12:21:50 (0) ** => When remotely connecting, the namespace(s)
listed require(s) the WMI client to
28025 12:21:50 (0) ** use an encrypted connection by specifying the
PACKET PRIVACY authentication level.
28026 12:21:50 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy
flags)
28027 12:21:50 (0) ** i.e. 'WMIC.EXE /NODE:"SERVER2" /
AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\CIMV2\TERMINALSERVICES Class
__SystemSecurity'
28028 12:21:50 (0) **
28029 12:21:50 (0) ** WMI MONIKER
............................................................................................
OK.
28030 12:21:50 (0) ** WMI
....................................................................................................
OK.
28031 12:21:50 (1) !! ERROR: WMI GET operation errors
...........................................................................
2 ERROR(S)!
28032 12:21:50 (0) ** - Root/CIMV2,
Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 -
(WBEM_E_NOT_FOUND) Object cannot be found.
28033 12:21:50 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMIPERFINST.MOF'
28034 12:21:50 (0) ** - Root/CIMV2,
Win32_PerfRawData_TermService_TerminalServices, 0x80041002 -
(WBEM_E_NOT_FOUND) Object cannot be found.
28035 12:21:50 (0) ** MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM
\WMIPERFINST.MOF'
28036 12:21:50 (0) ** => When a WMI performance class is missing (i.e.
'Win32_PerfRawData_TermService_TerminalServices'), it is generally due
to
28037 12:21:50 (0) ** a lack of buffer refresh of the WMI class
provider exposing the WMI performance counters.
28038 12:21:50 (0) ** You can refresh the WMI class provider buffer
28039 12:21:50 (0) **
28040 12:21:50 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
28041 12:21:50 (0) **
28042 12:21:50 (0) ** WMI MOF
............................................................................................
OK.
28043 12:21:50 (0) ** WMI QUALIFIER access
....................................................................................
OK.
28044 12:21:50 (0) ** WMI ENUMERATION
.........................................................................................
OK.
28045 12:21:50 (0) ** WMI EXECQUERY
...........................................................................................
OK.
28046 12:21:50 (2) !! WARNING: WMI GET VALUE operation errors
...................................................................
5 WARNING(S)!
ClearAfter='00000000000030.000000:000' (Expected
default='00000000000500.000000:000').
Property: ClearAfter='00000000000030.000000:000' (Expected
default='00000000000500.000000:000').
Property: ClearAfter='00000000000015.000000:000' (Expected
default='00000000000230.000000:000').
ClearAfter='00000000000030.000000:000' (Expected
default='00000000000500.000000:000').
ClearAfter='00000000000030.000000:000' (Expected
default='00000000000500.000000:000').
28052 12:21:50 (0) **
28053 12:21:50 (0) ** WMI WRITE
...............................................................................................
NOT TESTED.
28054 12:21:50 (0) ** WMI PUT
.................................................................................................
NOT TESTED.
28055 12:21:50 (0) ** WMI DELETE
..............................................................................................
NOT TESTED.
28056 12:21:50 (0) ** WMI static instances
.....................................................................................
1730.
28057 12:21:50 (0) ** WMI dynamic instances
....................................................................................
0.
28058 12:21:50 (0) ** WMI instance request cancellations (to limit
performance
impact): ................................................... 1.
28059 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28060 12:21:50 (0) ** # of Event Log events BEFORE WMIDiag execution
28061 12:21:50 (0) **
.............................................................................................................
0.
28062 12:21:50 (0) **
..........................................................................................................
0.
28063 12:21:50 (0) **
.......................................................................................................
0.
28064 12:21:50 (0) **
28065 12:21:50 (0) ** # of additional Event Log events AFTER WMIDiag
28066 12:21:50 (0) **
.............................................................................................................
0.
28067 12:21:50 (0) **
..........................................................................................................
0.
28068 12:21:50 (0) **
.......................................................................................................
0.
28069 12:21:50 (0) **
28070 12:21:50 (0) ** 2 error(s) 0x80041002 - (WBEM_E_NOT_FOUND)
Object cannot be found
28071 12:21:50 (0) ** => This error is typically a WMI error. This WMI
28072 12:21:50 (0) ** - a missing WMI class definition or object.
28073 12:21:50 (0) ** (See any GET, ENUMERATION, EXECQUERY and
GET VALUE operation failures).
28074 12:21:50 (0) ** You can correct the missing class
28075 12:21:50 (0) ** - Manually recompiling the MOF file(s) with
the 'MOFCOMP <FileName.MOF>' command.
28076 12:21:50 (0) ** Note: You can build a list of classes in
relation with their WMI provider and MOF file with WMIDiag.
28077 12:21:50 (0) ** (This list can be built on a similar
and working WMI Windows installation)
28078 12:21:50 (0) ** The following command line must be
28079 12:21:50 (0) ** i.e. 'WMIDiag
CorrelateClassAndProvider'
28080 12:21:50 (0) ** Note: When a WMI performance class is
missing, you can manually resynchronize performance counters
28081 12:21:50 (0) ** with WMI by starting the ADAP
process.
28082 12:21:50 (0) ** - a WMI repository corruption.
28083 12:21:50 (0) ** In such a case, you must rerun WMIDiag with
'WriteInRepository' parameter
28084 12:21:50 (0) ** to validate the WMI repository operations.
28085 12:21:50 (0) ** Note: ENSURE you are an administrator with
FULL access to WMI EVERY namespaces of the computer before
28086 12:21:50 (0) ** executing the WriteInRepository
28087 12:21:50 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
28088 12:21:50 (0) ** - If the WriteInRepository command fails,
while being an Administrator with ALL accesses to ALL namespaces
28089 12:21:50 (0) ** the WMI repository must be reconstructed.
28090 12:21:50 (0) ** Note: The WMI repository reconstruction
requires to locate all MOF files needed to rebuild the repository,
28091 12:21:50 (0) ** otherwise some applications may fail
after the reconstruction.
28092 12:21:50 (0) ** This can be achieved with the following
28093 12:21:50 (0) ** i.e. 'WMIDiag ShowMOFErrors'
28094 12:21:50 (0) ** Note: The repository reconstruction must be a
LAST RESORT solution and ONLY after executing
28095 12:21:50 (0) ** ALL fixes previously mentioned.
28096 12:21:50 (2) !! WARNING: Static information stored by external
applications in the repository will be LOST! (i.e. SMS Inventory)
28097 12:21:50 (0) **
28098 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28099 12:21:50 (0) ** WMI Registry key
.............................................................................................
OK.
28100 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28101 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28102 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28103 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28104 12:21:50 (0) **
28105 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
28106 12:21:50 (0) **
------------------------------------------------------ WMI REPORT: END
-----------------------------------------------------------
l***@gmail.com
2009-02-24 01:04:11 UTC
Permalink
What is the DFSRS and how is it different from the DFS Replication
Service?

I've rebooted both servers involved last night, and it DID actually
sync the one folder I had reconfigured.

I've re-added all the sync folders now, and am hoping to see it
complete syncs throughout the day.

Sadly, Server2 can't open the DFS management console, its gone and
broken itself.. so I'm configuring it all from Server1 (had tried both
previously, so this isnt a fix)

On Feb 23, 8:27 pm, "Isaac Oben -MCSE, MCITP"
Post by Isaac Oben -MCSE, MCITP
Hello,
Looking at your error I am thinking it might be namespace related issue. DFS
might still be looking to communicate with the older namespace which no
longer exists, hence giving you the communication error...You can try to
restart both the dfsrs and the dfssvc and see if this helps resolve the
issue. I meant to ask, is this a domain base or standalone dfs?
Isaac
Post by l***@gmail.com
Wow, I have come to hate DFS right now.. Its pretty frustrating!
So, We had a bunch of folders, replicating between two servers, lets
call them Server1 and Server2...
Then, last week, Server2 packed it in.
Both servers are Windows Server 2008.  Both are 32bit.
I've gone through, and made sure that all the existing file shares are
shared again on Server2.
I re-created the namespace (twice, with different names incase it was
Active Directory), and re-created the folders in the Namespace, and
then the replication of the two folders.
Whether it is server1 or server2 that is set as the primary server, it
appears that replication just NEVER starts?
 SERVER1   (1 error)    (View Server Details)
 Communication errors are preventing replication with partner
SERVER2.
 SERVER2   (1 error)    (View Server Details)
 Cannot access the local WMI repository.
"(WBEM_E_NOT_FOUND) Object cannot be found"
I have looked at trying to fix WMI.  I've run WMIDiag (added log file
below), and even run WMIDiag -WriteInRepository
I can't figure out what to do with the whole reconstruction thing,
because I can't tell what file its missing, just that it can't find
the object?
No where has Server 2008 fixes for this problem.  I'm sure that DFS is
supposed to work better than this!  Any help massively appreciated!
DNS name: server1.xxxxxxxxx.local
Domain name: xxxxxxxxxx.local
Reference domain controller: server3.xxxxxxx.local
ERRORS (There is 1 error to report)
Communication errors are preventing replication with partner
SERVER2.
 Affected replicated folders: All replicated folders on this server.
 Description: DFS Replication cannot replicate with partner SERVER2
for replication group xxxxxxxxx.local\fileserver\foldername. The
partner did not recognize the connection or the replication group
configuration. The DFS Replication service used partner DNS name
Server2.xxxxxxxx.local, IP address 192.168.x.x, and WINS address
Server2 but failed with error ID: 9026 (The connection is invalid).
Event ID: 5012
 Last occurred: Monday, 23 February 2009
 Suggested action: This error can occur when the partner does not
have the latest DFS Replication configuration information. The service
will retry the connection periodically. For troubleshooting
information, , see The Microsoft Web Site.
WARNINGS (There is 1 warning to report)
This member is waiting for initial replication for replicated folder
foldername.
 Affected replicated folders: foldername
 Description: This member is waiting for initial replication for
replicated folder foldername and is not currently participating in
replication. This delay can occur because the member is waiting for
the DFS Replication service to retrieve replication settings from
Active Directory Domain Services. After the member detects that it is
part of replication group, the member will begin initial
replication.
 Last occurred: Monday, 23 February 2009
 Suggested action: Replication will begin after initial replication
is complete. If this state does not change, see The Microsoft Web
Site.
-------------------------------------------------------------------------------------------------------------------------
DNS name: server2.xxxxxxxxxx.local
Domain name: xxxxxxxxxxx.local
Reference domain controller: --
ERRORS (There is 1 error to report)
Cannot access the local WMI repository.
 Affected replicated folders: All replicated folders on this server.
 Description: Due to the following error, the DFS Replication
reporting mechanism cannot access the WMI (Windows Management
Instrumentation) namespace to retrieve certain reporting information.
Error ID: 0x80041002.
 Last occurred: Monday, 23 February 2009
 Suggested action: For information about troubleshooting WMI errors,
see WMI help.
WARNINGS (There is 1 warning to report)
Reference member returned no replicated folders.
 Description: Backlog calculations cannot be performed because the
reference member returned zero replicated folders.
 Last occurred: Monday, 23 February 2009
 Suggested action: For information about troubleshooting backlog
problems, see The Microsoft Web Site.
27890 12:21:50 (0) ** WMIDiag v2.0 started on Monday, February 23,
2009 at 12:06.
27891 12:21:50 (0) **
27892 12:21:50 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
27893 12:21:50 (0) **
27894 12:21:50 (0) ** This script is not supported under any Microsoft
standard support program or service.
27895 12:21:50 (0) ** The script is provided AS IS without warranty of
any kind. Microsoft further disclaims all
27896 12:21:50 (0) ** implied warranties including, without
limitation, any implied warranties of merchantability
27897 12:21:50 (0) ** or of fitness for a particular purpose. The
entire risk arising out of the use or performance
27898 12:21:50 (0) ** of the scripts and documentation remains with
you. In no event shall Microsoft, its authors,
27899 12:21:50 (0) ** or anyone else involved in the creation,
production, or delivery of the script be liable for
27900 12:21:50 (0) ** any damages whatsoever (including, without
limitation, damages for loss of business profits,
27901 12:21:50 (0) ** business interruption, loss of business
information, or other pecuniary loss) arising out of
27902 12:21:50 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
27903 12:21:50 (0) ** of the possibility of such damages.
27904 12:21:50 (0) **
27905 12:21:50 (0) **
27906 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27907 12:21:50 (0) **
BEGIN ----------------------------------------------------------
27908 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27909 12:21:50 (0) **
27910 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27911 12:21:50 (0) ** Windows Longhorn Server - No service pack - 32-
bit (6001) - User 'xxxxxxxxxxxx\ADMINISTRATOR' on computer 'SERVER2'.
27912 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27913 12:21:50 (0) **
........................................................................................................
OK..
27914 12:21:50 (0) ** System
.......................................................................................................
C: (Disk #0 Partition #0).
27915 12:21:50 (0) ** Drive
.........................................................................................................
IDE (SAMSUNG HD753LJ ATA Device).
27916 12:21:50 (0) ** INFO: The following UNEXPECTED binary files are/
is found in the WBEM folder: ........................................
2 FILE(S)!
27917 12:21:50 (0) **   - DNSPROV.DLL,                   203776
bytes,       1/19/2008 10:24:47 PM
27918 12:21:50 (0) **   - SERVERCOMPPROV.DLL,            32768
bytes,        1/19/2008 10:23:36 PM
27919 12:21:50 (0) ** => This list is provided for information.
Unexpected binary file(s) in 'C:\WINDOWS\SYSTEM32\WBEM\'
27920 12:21:50 (0) **    do not necessarily represent an error. For
instance, the file(s) listed can be added by
27921 12:21:50 (0) **    any applications implementing WMI providers.
27922 12:21:50 (0) ** => NO ACTION is required.
27923 12:21:50 (0) **
27924 12:21:50 (1) !! ERROR: The following WMI system file(s) is/are
missing: .............................................................
3 ERROR(S)!
27925 12:21:50 (0) ** - C:\Windows\System32\WBEM\framedyn.dll
27926 12:21:50 (0) ** - C:\Windows\System32\WBEM\provthrd.dll
27927 12:21:50 (0) ** - C:\Windows\System32\WBEM\wbemcomn.dll
27928 12:21:50 (0) ** => Recopy from a working system the missing WMI
system files to 'C:\WINDOWS\SYSTEM32\WBEM\'
27929 12:21:50 (0) **
27930 12:21:50 (0) ** There are no missing WMI repository
..........................................................................
OK.
27931 12:21:50 (0) ** WMI repository
...............................................................................................
CONSISTENT.
27933 12:21:50 (0) ** The WMI repository has a size
...................................................................................
26 MB.
27934 12:21:50 (0) ** - Disk free space on
..........................................................................................
10916 MB.
27935 12:21:50 (0) **   - INDEX.BTR,                     3309568
bytes,      2/23/2009 11:37:33 AM
27936 12:21:50 (0) **   - MAPPING1.MAP,                  75372
bytes,        2/23/2009 11:29:33 AM
27937 12:21:50 (0) **   - MAPPING2.MAP,  
...
read more »
Isaac Oben -MCSE, MCITP
2009-02-24 03:58:48 UTC
Permalink
same thing just abbreviated, no difference. dfsr = DFS replication and dfs =
DFS Namespace

<***@gmail.com> wrote in message news:8d279549-1be6-414e-8eb5-***@c36g2000yqn.googlegroups.com...
What is the DFSRS and how is it different from the DFS Replication
Service?

I've rebooted both servers involved last night, and it DID actually
sync the one folder I had reconfigured.

I've re-added all the sync folders now, and am hoping to see it
complete syncs throughout the day.

Sadly, Server2 can't open the DFS management console, its gone and
broken itself.. so I'm configuring it all from Server1 (had tried both
previously, so this isnt a fix)

On Feb 23, 8:27 pm, "Isaac Oben -MCSE, MCITP"
Post by Isaac Oben -MCSE, MCITP
Hello,
Looking at your error I am thinking it might be namespace related issue. DFS
might still be looking to communicate with the older namespace which no
longer exists, hence giving you the communication error...You can try to
restart both the dfsrs and the dfssvc and see if this helps resolve the
issue. I meant to ask, is this a domain base or standalone dfs?
Isaac
Post by l***@gmail.com
Wow, I have come to hate DFS right now.. Its pretty frustrating!
So, We had a bunch of folders, replicating between two servers, lets
call them Server1 and Server2...
Then, last week, Server2 packed it in.
Both servers are Windows Server 2008. Both are 32bit.
I've gone through, and made sure that all the existing file shares are
shared again on Server2.
I re-created the namespace (twice, with different names incase it was
Active Directory), and re-created the folders in the Namespace, and
then the replication of the two folders.
Whether it is server1 or server2 that is set as the primary server, it
appears that replication just NEVER starts?
SERVER1 (1 error) (View Server Details)
Communication errors are preventing replication with partner
SERVER2.
SERVER2 (1 error) (View Server Details)
Cannot access the local WMI repository.
"(WBEM_E_NOT_FOUND) Object cannot be found"
I have looked at trying to fix WMI. I've run WMIDiag (added log file
below), and even run WMIDiag -WriteInRepository
I can't figure out what to do with the whole reconstruction thing,
because I can't tell what file its missing, just that it can't find
the object?
No where has Server 2008 fixes for this problem. I'm sure that DFS is
supposed to work better than this! Any help massively appreciated!
DNS name: server1.xxxxxxxxx.local
Domain name: xxxxxxxxxx.local
Reference domain controller: server3.xxxxxxx.local
ERRORS (There is 1 error to report)
Communication errors are preventing replication with partner
SERVER2.
Affected replicated folders: All replicated folders on this server.
Description: DFS Replication cannot replicate with partner SERVER2
for replication group xxxxxxxxx.local\fileserver\foldername. The
partner did not recognize the connection or the replication group
configuration. The DFS Replication service used partner DNS name
Server2.xxxxxxxx.local, IP address 192.168.x.x, and WINS address
Server2 but failed with error ID: 9026 (The connection is invalid).
Event ID: 5012
Last occurred: Monday, 23 February 2009
Suggested action: This error can occur when the partner does not
have the latest DFS Replication configuration information. The service
will retry the connection periodically. For troubleshooting
information, , see The Microsoft Web Site.
WARNINGS (There is 1 warning to report)
This member is waiting for initial replication for replicated folder
foldername.
Affected replicated folders: foldername
Description: This member is waiting for initial replication for
replicated folder foldername and is not currently participating in
replication. This delay can occur because the member is waiting for
the DFS Replication service to retrieve replication settings from
Active Directory Domain Services. After the member detects that it is
part of replication group, the member will begin initial
replication.
Last occurred: Monday, 23 February 2009
Suggested action: Replication will begin after initial replication
is complete. If this state does not change, see The Microsoft Web
Site.
-------------------------------------------------------------------------------------------------------------------------
DNS name: server2.xxxxxxxxxx.local
Domain name: xxxxxxxxxxx.local
Reference domain controller: --
ERRORS (There is 1 error to report)
Cannot access the local WMI repository.
Affected replicated folders: All replicated folders on this server.
Description: Due to the following error, the DFS Replication
reporting mechanism cannot access the WMI (Windows Management
Instrumentation) namespace to retrieve certain reporting information.
Error ID: 0x80041002.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting WMI errors,
see WMI help.
WARNINGS (There is 1 warning to report)
Reference member returned no replicated folders.
Description: Backlog calculations cannot be performed because the
reference member returned zero replicated folders.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting backlog
problems, see The Microsoft Web Site.
27890 12:21:50 (0) ** WMIDiag v2.0 started on Monday, February 23,
2009 at 12:06.
27891 12:21:50 (0) **
27892 12:21:50 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
27893 12:21:50 (0) **
27894 12:21:50 (0) ** This script is not supported under any Microsoft
standard support program or service.
27895 12:21:50 (0) ** The script is provided AS IS without warranty of
any kind. Microsoft further disclaims all
27896 12:21:50 (0) ** implied warranties including, without
limitation, any implied warranties of merchantability
27897 12:21:50 (0) ** or of fitness for a particular purpose. The
entire risk arising out of the use or performance
27898 12:21:50 (0) ** of the scripts and documentation remains with
you. In no event shall Microsoft, its authors,
27899 12:21:50 (0) ** or anyone else involved in the creation,
production, or delivery of the script be liable for
27900 12:21:50 (0) ** any damages whatsoever (including, without
limitation, damages for loss of business profits,
27901 12:21:50 (0) ** business interruption, loss of business
information, or other pecuniary loss) arising out of
27902 12:21:50 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
27903 12:21:50 (0) ** of the possibility of such damages.
27904 12:21:50 (0) **
27905 12:21:50 (0) **
27906 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27907 12:21:50 (0) **
BEGIN ----------------------------------------------------------
27908 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27909 12:21:50 (0) **
27910 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27911 12:21:50 (0) ** Windows Longhorn Server - No service pack - 32-
bit (6001) - User 'xxxxxxxxxxxx\ADMINISTRATOR' on computer 'SERVER2'.
27912 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27913 12:21:50 (0) **
........................................................................................................
OK..
27914 12:21:50 (0) ** System
.......................................................................................................
C: (Disk #0 Partition #0).
27915 12:21:50 (0) ** Drive
.........................................................................................................
IDE (SAMSUNG HD753LJ ATA Device).
27916 12:21:50 (0) ** INFO: The following UNEXPECTED binary files are/
is found in the WBEM folder: ........................................
2 FILE(S)!
27917 12:21:50 (0) ** - DNSPROV.DLL, 203776
bytes, 1/19/2008 10:24:47 PM
27918 12:21:50 (0) ** - SERVERCOMPPROV.DLL, 32768
bytes, 1/19/2008 10:23:36 PM
27919 12:21:50 (0) ** => This list is provided for information.
Unexpected binary file(s) in 'C:\WINDOWS\SYSTEM32\WBEM\'
27920 12:21:50 (0) ** do not necessarily represent an error. For
instance, the file(s) listed can be added by
27921 12:21:50 (0) ** any applications implementing WMI providers.
27922 12:21:50 (0) ** => NO ACTION is required.
27923 12:21:50 (0) **
27924 12:21:50 (1) !! ERROR: The following WMI system file(s) is/are
missing: .............................................................
3 ERROR(S)!
27925 12:21:50 (0) ** - C:\Windows\System32\WBEM\framedyn.dll
27926 12:21:50 (0) ** - C:\Windows\System32\WBEM\provthrd.dll
27927 12:21:50 (0) ** - C:\Windows\System32\WBEM\wbemcomn.dll
27928 12:21:50 (0) ** => Recopy from a working system the missing WMI
system files to 'C:\WINDOWS\SYSTEM32\WBEM\'
27929 12:21:50 (0) **
27930 12:21:50 (0) ** There are no missing WMI repository
..........................................................................
OK.
27931 12:21:50 (0) ** WMI repository
...............................................................................................
CONSISTENT.
27933 12:21:50 (0) ** The WMI repository has a size
...................................................................................
26 MB.
27934 12:21:50 (0) ** - Disk free space on
..........................................................................................
10916 MB.
27935 12:21:50 (0) ** - INDEX.BTR, 3309568
bytes, 2/23/2009 11:37:33 AM
27936 12:21:50 (0) ** - MAPPING1.MAP, 75372
bytes, 2/23/2009 11:29:33 AM
27937 12:21:50 (0) ** - MAPPING2.MAP,
...
read more »
l***@gmail.com
2009-02-24 23:36:12 UTC
Permalink
Restarting the DFS Replication Service does not assist in the
processing of the Replication groups!


On Feb 24, 2:58 pm, "Isaac Oben -MCSE, MCITP"
Post by Isaac Oben -MCSE, MCITP
same thing just abbreviated, no difference. dfsr = DFS replication and dfs =
DFS Namespace
What is the DFSRS and how is it different from the DFS Replication
Service?
I've rebooted both servers involved last night, and it DID actually
sync the one folder I had reconfigured.
I've re-added all the sync folders now, and am hoping to see it
complete syncs throughout the day.
Sadly, Server2 can't open the DFS management console, its gone and
broken itself.. so I'm configuring it all from Server1 (had tried both
previously, so this isnt a fix)
On Feb 23, 8:27 pm, "Isaac Oben -MCSE, MCITP"
Post by Isaac Oben -MCSE, MCITP
Hello,
Looking at your error I am thinking it might be namespace related issue. DFS
might still be looking to communicate with the older namespace which no
longer exists, hence giving you the communication error...You can try to
restart both the dfsrs and the dfssvc and see if this helps resolve the
issue. I meant to ask, is this a domain base or standalone dfs?
Isaac
Post by l***@gmail.com
Wow, I have come to hate DFS right now.. Its pretty frustrating!
So, We had a bunch of folders, replicating between two servers, lets
call them Server1 and Server2...
Then, last week, Server2 packed it in.
Both servers are Windows Server 2008. Both are 32bit.
I've gone through, and made sure that all the existing file shares are
shared again on Server2.
I re-created the namespace (twice, with different names incase it was
Active Directory), and re-created the folders in the Namespace, and
then the replication of the two folders.
Whether it is server1 or server2 that is set as the primary server, it
appears that replication just NEVER starts?
SERVER1 (1 error) (View Server Details)
Communication errors are preventing replication with partner
SERVER2.
SERVER2 (1 error) (View Server Details)
Cannot access the local WMI repository.
"(WBEM_E_NOT_FOUND) Object cannot be found"
I have looked at trying to fix WMI. I've run WMIDiag (added log file
below), and even run WMIDiag -WriteInRepository
I can't figure out what to do with the whole reconstruction thing,
because I can't tell what file its missing, just that it can't find
the object?
No where has Server 2008 fixes for this problem. I'm sure that DFS is
supposed to work better than this! Any help massively appreciated!
DNS name: server1.xxxxxxxxx.local
Domain name: xxxxxxxxxx.local
Reference domain controller: server3.xxxxxxx.local
ERRORS (There is 1 error to report)
Communication errors are preventing replication with partner
SERVER2.
Affected replicated folders: All replicated folders on this server.
Description: DFS Replication cannot replicate with partner SERVER2
for replication group xxxxxxxxx.local\fileserver\foldername. The
partner did not recognize the connection or the replication group
configuration. The DFS Replication service used partner DNS name
Server2.xxxxxxxx.local, IP address 192.168.x.x, and WINS address
Server2 but failed with error ID: 9026 (The connection is invalid).
Event ID: 5012
Last occurred: Monday, 23 February 2009
Suggested action: This error can occur when the partner does not
have the latest DFS Replication configuration information. The service
will retry the connection periodically. For troubleshooting
information, , see The Microsoft Web Site.
WARNINGS (There is 1 warning to report)
This member is waiting for initial replication for replicated folder
foldername.
Affected replicated folders: foldername
Description: This member is waiting for initial replication for
replicated folder foldername and is not currently participating in
replication. This delay can occur because the member is waiting for
the DFS Replication service to retrieve replication settings from
Active Directory Domain Services. After the member detects that it is
part of replication group, the member will begin initial
replication.
Last occurred: Monday, 23 February 2009
Suggested action: Replication will begin after initial replication
is complete. If this state does not change, see The Microsoft Web
Site.
-------------------------------------------------------------------------------------------------------------------------
DNS name: server2.xxxxxxxxxx.local
Domain name: xxxxxxxxxxx.local
Reference domain controller: --
ERRORS (There is 1 error to report)
Cannot access the local WMI repository.
Affected replicated folders: All replicated folders on this server.
Description: Due to the following error, the DFS Replication
reporting mechanism cannot access the WMI (Windows Management
Instrumentation) namespace to retrieve certain reporting information.
Error ID: 0x80041002.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting WMI errors,
see WMI help.
WARNINGS (There is 1 warning to report)
Reference member returned no replicated folders.
Description: Backlog calculations cannot be performed because the
reference member returned zero replicated folders.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting backlog
problems, see The Microsoft Web Site.
27890 12:21:50 (0) ** WMIDiag v2.0 started on Monday, February 23,
2009 at 12:06.
27891 12:21:50 (0) **
27892 12:21:50 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
27893 12:21:50 (0) **
27894 12:21:50 (0) ** This script is not supported under any Microsoft
standard support program or service.
27895 12:21:50 (0) ** The script is provided AS IS without warranty of
any kind. Microsoft further disclaims all
27896 12:21:50 (0) ** implied warranties including, without
limitation, any implied warranties of merchantability
27897 12:21:50 (0) ** or of fitness for a particular purpose. The
entire risk arising out of the use or performance
27898 12:21:50 (0) ** of the scripts and documentation remains with
you. In no event shall Microsoft, its authors,
27899 12:21:50 (0) ** or anyone else involved in the creation,
production, or delivery of the script be liable for
27900 12:21:50 (0) ** any damages whatsoever (including, without
limitation, damages for loss of business profits,
27901 12:21:50 (0) ** business interruption, loss of business
information, or other pecuniary loss) arising out of
27902 12:21:50 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
27903 12:21:50 (0) ** of the possibility of such damages.
27904 12:21:50 (0) **
27905 12:21:50 (0) **
27906 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27907 12:21:50 (0) **
BEGIN ----------------------------------------------------------
27908 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27909 12:21:50 (0) **
27910 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27911 12:21:50 (0) ** Windows Longhorn Server - No service pack - 32-
bit (6001) - User 'xxxxxxxxxxxx\ADMINISTRATOR' on computer 'SERVER2'.
27912 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27913 12:21:50 (0) **
........................................................................................................
OK..
27914 12:21:50 (0) ** System
.......................................................................................................
C: (Disk #0 Partition #0).
27915 12:21:50 (0) ** Drive
.........................................................................................................
IDE (SAMSUNG HD753LJ ATA Device).
27916 12:21:50 (0) ** INFO: The following UNEXPECTED binary files are/
is found in the WBEM folder: ........................................
2 FILE(S)!
27917 12:21:50 (0) ** - DNSPROV.DLL, 203776
bytes, 1/19/2008 10:24:47 PM
27918 12:21:50 (0) ** - SERVERCOMPPROV.DLL, 32768
bytes, 1/19/2008 10:23:36 PM
27919 12:21:50 (0) ** => This list is provided for information.
Unexpected binary file(s) in 'C:\WINDOWS\SYSTEM32\WBEM\'
27920 12:21:50 (0) ** do not necessarily represent an error. For
instance, the file(s) listed can be added by
27921 12:21:50 (0) ** any applications implementing WMI providers.
27922 12:21:50 (0) ** => NO ACTION is required.
27923 12:21:50 (0) **
27924 12:21:50 (1) !! ERROR: The following WMI system file(s) is/are
missing: .............................................................
3 ERROR(S)!
27925 12:21:50 (0) ** - C:\Windows\System32\WBEM\framedyn.dll
27926 12:21:50 (0) ** - C:\Windows\System32\WBEM\provthrd.dll
27927 12:21:50 (0) ** - C:\Windows\System32\WBEM\wbemcomn.dll
27928 12:21:50 (0) ** => Recopy from a working system the missing WMI
system
...
read more »
l***@gmail.com
2009-02-25 00:18:14 UTC
Permalink
Post by l***@gmail.com
Restarting the DFS Replication Service does not assist in the
processing of the Replication groups!
On Feb 24, 2:58 pm, "Isaac Oben -MCSE, MCITP"
Post by Isaac Oben -MCSE, MCITP
same thing just abbreviated, no difference. dfsr = DFS replication and dfs =
DFS Namespace
What is the DFSRS and how is it different from the DFS Replication
Service?
I've rebooted both servers involved last night, and it DID actually
sync the one folder I had reconfigured.
I've re-added all the sync folders now, and am hoping to see it
complete syncs throughout the day.
Sadly, Server2 can't open the DFS management console, its gone and
broken itself.. so I'm configuring it all from Server1 (had tried both
previously, so this isnt a fix)
On Feb 23, 8:27 pm, "Isaac Oben -MCSE, MCITP"
Post by Isaac Oben -MCSE, MCITP
Hello,
Looking at your error I am thinking it might be namespace related issue. DFS
might still be looking to communicate with the older namespace which no
longer exists, hence giving you the communication error...You can try to
restart both the dfsrs and the dfssvc and see if this helps resolve the
issue. I meant to ask, is this a domain base or standalone dfs?
Isaac
Post by l***@gmail.com
Wow, I have come to hate DFS right now.. Its pretty frustrating!
So, We had a bunch of folders, replicating between two servers, lets
call them Server1 and Server2...
Then, last week, Server2 packed it in.
Both servers are Windows Server 2008. Both are 32bit.
I've gone through, and made sure that all the existing file shares are
shared again on Server2.
I re-created the namespace (twice, with different names incase it was
Active Directory), and re-created the folders in the Namespace, and
then the replication of the two folders.
Whether it is server1 or server2 that is set as the primary server, it
appears that replication just NEVER starts?
SERVER1 (1 error) (View Server Details)
Communication errors are preventing replication with partner
SERVER2.
SERVER2 (1 error) (View Server Details)
Cannot access the local WMI repository.
"(WBEM_E_NOT_FOUND) Object cannot be found"
I have looked at trying to fix WMI. I've run WMIDiag (added log file
below), and even run WMIDiag -WriteInRepository
I can't figure out what to do with the whole reconstruction thing,
because I can't tell what file its missing, just that it can't find
the object?
No where has Server 2008 fixes for this problem. I'm sure that DFS is
supposed to work better than this! Any help massively appreciated!
DNS name: server1.xxxxxxxxx.local
Domain name: xxxxxxxxxx.local
Reference domain controller: server3.xxxxxxx.local
ERRORS (There is 1 error to report)
Communication errors are preventing replication with partner
SERVER2.
Affected replicated folders: All replicated folders on this server.
Description: DFS Replication cannot replicate with partner SERVER2
for replication group xxxxxxxxx.local\fileserver\foldername. The
partner did not recognize the connection or the replication group
configuration. The DFS Replication service used partner DNS name
Server2.xxxxxxxx.local, IP address 192.168.x.x, and WINS address
Server2 but failed with error ID: 9026 (The connection is invalid).
Event ID: 5012
Last occurred: Monday, 23 February 2009
Suggested action: This error can occur when the partner does not
have the latest DFS Replication configuration information. The service
will retry the connection periodically. For troubleshooting
information, , see The Microsoft Web Site.
WARNINGS (There is 1 warning to report)
This member is waiting for initial replication for replicated folder
foldername.
Affected replicated folders: foldername
Description: This member is waiting for initial replication for
replicated folder foldername and is not currently participating in
replication. This delay can occur because the member is waiting for
the DFS Replication service to retrieve replication settings from
Active Directory Domain Services. After the member detects that it is
part of replication group, the member will begin initial
replication.
Last occurred: Monday, 23 February 2009
Suggested action: Replication will begin after initial replication
is complete. If this state does not change, see The Microsoft Web
Site.
-------------------------------------------------------------------------------------------------------------------------
DNS name: server2.xxxxxxxxxx.local
Domain name: xxxxxxxxxxx.local
Reference domain controller: --
ERRORS (There is 1 error to report)
Cannot access the local WMI repository.
Affected replicated folders: All replicated folders on this server.
Description: Due to the following error, the DFS Replication
reporting mechanism cannot access the WMI (Windows Management
Instrumentation) namespace to retrieve certain reporting information.
Error ID: 0x80041002.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting WMI errors,
see WMI help.
WARNINGS (There is 1 warning to report)
Reference member returned no replicated folders.
Description: Backlog calculations cannot be performed because the
reference member returned zero replicated folders.
Last occurred: Monday, 23 February 2009
Suggested action: For information about troubleshooting backlog
problems, see The Microsoft Web Site.
27890 12:21:50 (0) ** WMIDiag v2.0 started on Monday, February 23,
2009 at 12:06.
27891 12:21:50 (0) **
27892 12:21:50 (0) ** Copyright (c) Microsoft Corporation. All rights
reserved - January 2007.
27893 12:21:50 (0) **
27894 12:21:50 (0) ** This script is not supported under any Microsoft
standard support program or service.
27895 12:21:50 (0) ** The script is provided AS IS without warranty of
any kind. Microsoft further disclaims all
27896 12:21:50 (0) ** implied warranties including, without
limitation, any implied warranties of merchantability
27897 12:21:50 (0) ** or of fitness for a particular purpose. The
entire risk arising out of the use or performance
27898 12:21:50 (0) ** of the scripts and documentation remains with
you. In no event shall Microsoft, its authors,
27899 12:21:50 (0) ** or anyone else involved in the creation,
production, or delivery of the script be liable for
27900 12:21:50 (0) ** any damages whatsoever (including, without
limitation, damages for loss of business profits,
27901 12:21:50 (0) ** business interruption, loss of business
information, or other pecuniary loss) arising out of
27902 12:21:50 (0) ** the use of or inability to use the script or
documentation, even if Microsoft has been advised
27903 12:21:50 (0) ** of the possibility of such damages.
27904 12:21:50 (0) **
27905 12:21:50 (0) **
27906 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27907 12:21:50 (0) **
BEGIN ----------------------------------------------------------
27908 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27909 12:21:50 (0) **
27910 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27911 12:21:50 (0) ** Windows Longhorn Server - No service pack - 32-
bit (6001) - User 'xxxxxxxxxxxx\ADMINISTRATOR' on computer 'SERVER2'.
27912 12:21:50 (0) **
----------------------------------------------------------------------------------------------------------------------------------
27913 12:21:50 (0) **
........................................................................................................
OK..
27914 12:21:50 (0) ** System
.......................................................................................................
C: (Disk #0 Partition #0).
27915 12:21:50 (0) ** Drive
.........................................................................................................
IDE (SAMSUNG HD753LJ ATA Device).
27916 12:21:50 (0) ** INFO: The following UNEXPECTED binary files are/
is found in the WBEM folder: ........................................
2 FILE(S)!
27917 12:21:50 (0) ** - DNSPROV.DLL, 203776
bytes, 1/19/2008 10:24:47 PM
27918 12:21:50 (0) ** - SERVERCOMPPROV.DLL, 32768
bytes, 1/19/2008 10:23:36 PM
27919 12:21:50 (0) ** => This list is provided for information.
Unexpected binary file(s) in 'C:\WINDOWS\SYSTEM32\WBEM\'
27920 12:21:50 (0) ** do not necessarily represent an error. For
instance, the file(s) listed can be added by
27921 12:21:50 (0) ** any applications implementing WMI
...
read more »
What drives me nuts is that there is a hotfix for pretty much this
problem for DFS for Server 2003. Yet no such hotfix for Server 2008!.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;931685

Loading...