RE: repository limitations

Hello:
I think we reached the limits of number of developers per repository. We
have approximately 20 (or over) developers connected to one repository.
Breaking a repository, if one is working from base projects that are used in
one huge development application (consisting of several projects), will pose
a challenge unless one is very critical in the designing of such an
application from day one. Our developers are local as well as remote.
Most of our clients are 128 MB NT Workstations. All our developers are
advised to use the -fm flag and set the minimum and maximum memory limits.
Our developers are also encouraged to use shadows and compile on updates
which integrates compiled projects into the base. This is recommended by
Forte for performance gain ( keeping the base compiled). Our repository (on
NT server) is above a gigabyte consistently and we clean it nightly. Not
cleaning it consistently means a threat of the repository reaching its 2GB
limit whereby no activity can be performed on it except exporting and
recreating it.
Splitting a repository is entirely a design issue at this point, and
synchronizing ( even at a scripted level) does not work like synchronous
replication. You will not have a choice but to have difference in code if
you are using base projects in both repositories.
Good luck, and let me know if you find any breakthroughs.
Mohamed Nasser.
Systems and Database Engineer
Descartes Systems Group Inc.
-----Original Message-----
From: Jeanne Hesler [SMTP:[email protected]]
Sent: Thursday, December 31, 1998 8:55 PM
To: [email protected]
Subject: repository limitations
Hi all,
What do you feel is the practical limitation for the number of developers
that can be supported in a single repository? Are there other factors
that
play heavily in the limitation, such as server platform, or frequency and
timing of integrations and updates?
I am interested in hearing some real-world experiences with larger
development teams, plus any tricks and suggestions for dealing with the
concurrency and synchronation issues if it does become necessary to split
into multiple repositories.
Thanks in advance for your input,
Jeanne
=========================================
Jeanne Hesler <[email protected]>
MSF&W Software, Product Development
(217) 698-3535 ext 207
http://www.msfw.com
=========================================
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi Sandra,
You have to look into your Repository Design Model for optimized MDM performance like fields in main table, sub-tables, look-up fields, Tuples etc. Refer SAP Note, 1012745 - Tips for improving MDM performance
https://websmp130.sap-ag.de/sap/support/notes/1012745
Also refer, http://wiki.sdn.sap.com/wiki/display/SAPMDM/EfficientRepositoryDesigninginMDM
For Data volume, you have to look into how many number of records are you going to maintain in MDM repository, accordingly you need to do Sizing, refer Sizing Guide for more details:
https://websmp109.sap-ag.de/~sapidb/011000358700001921872008E
Hope this helps..
Regards,
Mandeep Saini

Similar Messages

[HELP] Error creating property: file. Please verify the Property size is within the Repository limits.

I am using portal 8.1
was trying to upload a file (.doc) to the repository, and encountered such error.
com.bea.content.RepositoryRuntimeException: Error creating property: file. Please
verify the Property size is within the Repository limits.
TIA

Hi,
hopefully this may help towards a solution.
Are you using the Loader EJB ?
1) Are you publishing to a root node within the "BEA repository" ?
-> does this work ?
Do you have code that reads something like:
loader.loadDirectory("firstNode");
loader.loadFile("firstNode", myBinaryValue, myBytes, myProperties);
-> Having banged our heads off a lot of walls on this, we think that it is only when you try to publish to a sub-node within the repository that problems appear.
2) Try publishing to a sub-node in this manner:
loader.loadDirectory("firstNode/secondNode"); // Ensure exist in Repository
String contentNodeName = "firstNode/secondNode/myContentNode");
loader.loadFile(contentNodeName, myBinaryValue, myBytes, myProperties);
--- Drop us a line as well as replying to this group (as I don't check daily etc). Myself and a collegue, Niamh Fitzpatrick, have been looking at this. Thanks Niamh.
Hopefully this will work.

Repository limitations

Hi all,
What do you feel is the practical limitation for the number of developers
that can be supported in a single repository? Are there other factors that
play heavily in the limitation, such as server platform, or frequency and
timing of integrations and updates?
I am interested in hearing some real-world experiences with larger
development teams, plus any tricks and suggestions for dealing with the
concurrency and synchronation issues if it does become necessary to split
into multiple repositories.
Thanks in advance for your input,
Jeanne
=========================================
Jeanne Hesler <[email protected]>
MSF&W Software, Product Development
(217) 698-3535 ext 207
http://www.msfw.com
=========================================
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

We have around 12 developers working on the same repository. This is about
as many as you would want. I think that it would be better to keep it under
10 if possible. We have had performance problems with the update, compile
and integration cycle as the repository has increased in size. We got
around this to some extent by bumping the memory on the development
workstations to around 96 MB and by running update/compiles on the server
using fscript.
David Campbell,
CSC Australia
To: [email protected]
cc: (bcc: David Campbell/AUST/CSC)
From: [email protected]
Date: 01/01/99 01:55:23 AM GMT
Subject: repository limitations
Hi all,
What do you feel is the practical limitation for the number of developers
that can be supported in a single repository? Are there other factors that
play heavily in the limitation, such as server platform, or frequency and
timing of integrations and updates?
I am interested in hearing some real-world experiences with larger
development teams, plus any tricks and suggestions for dealing with the
concurrency and synchronation issues if it does become necessary to split
into multiple repositories.
Thanks in advance for your input,
Jeanne
=========================================
Jeanne Hesler <[email protected]>
MSF&W Software, Product Development
(217) 698-3535 ext 207
http://www.msfw.com
=========================================
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

File System Repository limitations

Hi everyone
I'm currently involved in a SAP Enterprise Portal project where we among other things are utilizing KM.
One of my customer's requirements are that we integrate an existing fileshare into KM. This fileshare is currently at ~200 GB and is still growing.
Since this is an existing fileshare we are planning on creating a file system repository manager for integrating it into KM.
To verify that this will actually work I have been trying to find any information regarding limitations of file system repositories in KM, but thus far without any luck. It would be greatly appreciated if anyone could point me in the direction of such documentation.
Additionally it would be great if anyone could share their experiences with large file system repositories.
Thanks in advance
Best regards,
Svein Gunnar Standnes

Hello Svein,
Namespace Restrictions for Resource Names
·         Maximum length of resource names:
FSDB: Restrictions of the file system are valid (Windows: 255 characters)
DBFS and DB: 448 characters
·         Maximum length of path (URI without prefix):
FSDB: Restrictions of the file system are valid (Windows: 255 characters)
DBFS and DB: No restriction
·         Permitted characters in resource names:
FSDB: Restrictions of the file system are valid (Unicode or Windows)
DBFS and DB: All Unicode characters, but restrictions may exist for some components of the repository framework.
Do not put a full stop/period at the end of the resource name.
Database Restrictions
There are the following restrictions for the databases used:
●     Maximum number of resources (folders, documents) in a repository instance:
FSDB: No restriction (possibly limited by file system restrictions)
DBFS and DB: 2,147,483,648
●     Maximum size of an individual resource:
FSDB: No restriction (possibly limited by file system restrictions
DBFS: 8 exabytes (MS SQL Server 2000), 2 GB (Oracle)
DB: 2 GB
Maximum length of large property values (string type): 2,147,583,647 bytes (2 GB).
Hope this helps,
Axel
please keep rewarding points to helpful answers

Job Server/Repository Limits

Is there a limit to how many unique job servers/ports can be added for a single job server installation?
Is there a limit to the number of repositories that can be added to each named job server/port?

Joe, I believe the advantage of multiple Job servers (with unique ports) associated to a unique repositories or multiple repositories is only when you want to use server groups and choose 1 Job server from each physical box. You cannot use the job servers on the same machine within a server group.
The people running the job in this case will still have to choose the job server at run time. With Server Groups, the job server is automatically chosen based on load on the server and the distribution level you chose at runtime.
Box #1:
JS_M1a:3500
JS_M1b:3501
Box #2:
JS_M2a:3500
JS_M2b:3501
Server group
sg_3500 - Containing JS_M1a and JS_M2a
sg_3501 - Containing JS_M1b and JS_M2b
Hope this helps!
Regards
Tiji
Edited by: Tiji Mathew on May 6, 2009 12:08 PM
You can have each repository associated to the same job server (at port 3500). You need not have separate job servers for each repository. Just like you would assoicate your local and profiler repository to the same job server.

Can not create the node in Repository

Hi, 
I am trying to create a content node in BEA repository. But BEA is throwing following error:
Error creating Node: NODE NAME. Please verify the Node name size is within the Repository limits.
 
I have no idea why I am getting this error. I am creating node whose name is well under the size which is allowed by CM_NODE's node_name column. Have any one come across these kind of errors? Is there any place in portal administration where I can check for minimum/ maximum limits?
 
I really appreciate your help.
 
Thanks 
Sanjay

Hi All,
After wasting significant amount of time, I finally found the real cause of the problem. In our application, we have some indexes on CM_NODE table. Those indexes were in unusable state. So instead of giving that error, weblogic server was giving some other error as mentioned in the previous post which resulted in lot of wastage of time. But after looking at jdbc.log file, things got cleared up. So once we fix the indexes, every thing worked fine. Too bad that portal administartion tool could not throw that exact error in debugging console.
 
Thanks
 
Sanjay

Can't use Oracle 8.1.7 as WLP repository

OK, I've been racking my brain on this for three days now.. maybe someone has an
idea...
The basic problem is this: I have yet been able to make a WLP content repository
work with
Oracle 8.1.7 and WLP 8.1.
I have tried several methods, including the ones mentioned here:
http://e-docs.bea.com/wlp/docs81/db/3Oracle.html (to move cgPool to an Oracle
database), and by creating a completely new portal domain from scratch, using
"Custom" (instead of Express) from the configuration wizard, setting up the JDBC
pools to point to Oracle (connection passed, database load passed correctly).
I then deploy a simple Portal Application / Portal Project created in workshop
as an EAR
(let's call it testPortal). Deployment seems to go fine. The outcome of all
methods is the same: the administration portal works fine. When I click on "Content",
I see the BEA repository. I can add nodes to the repository, AS LONG AS THEY
ARE DIRECTLY UNDER the BEA repository (for example: BEA Repository/TestNode).
However, if I try to add a node under that node (for example: BEA Repository/TestNode/TestNodeChild),
I get the following error from the admin portal as a popup box:
- Error creating Node: TestChildNode. Please verify the Node name size is within
Repository limits.
I can add any number of content items (including the standard content types that
were loaded:
article, book, image, etc) or nodes directly under BEA Repository, but I cannot
add anything under other nodes or the above error appears.
Some data is definitely getting to Oracle. After adding a node under BEA Repository,
a record for that node shows up in the database. The JDBC log shows an ORA-2291
(constraint violated) error (from jdbc.log):
java.sql.SQLException: ORA-02291: integrity constraint (DIAGEOCMS.FK1_CM_NODE)
v
iolated - parent key not found
This foreign key constraint is a pointer for the parent id of the node, back into
the cm_node table.
If I roll back the cgPool to pointbase, it works fine. Just not with an Oracle
8.1.7 cgPool
(or any other name, for that matter). I have tested this under both Win 2K and
Linux AS.
Other details: I did use a non-XA driver as suggested in the edocs link above.
For the cgPool, I used the Oracle Type 4 non-XA driver. I changed all the relevant
data sources to point at the new pool. And I did change the cgJMS store to use
the new pool as well.
Is anyone else successfully using Oracle 8.1.7 and Portal 8.1 with the repository?
Sorry for the length of the message.. difficult one to explain.
Thanks,
Bob

D'oh.
OK, it turns out that our staging database was NOT the Oracle 8.1.7.4 I thought
it was. Migrated from the 8.1.7.0 database to 8.1.7.4 resolved this problem.
Bob
"Bob Robinson" <[email protected]> wrote:
>
OK, I've been racking my brain on this for three days now.. maybe someone
has an
idea...
The basic problem is this: I have yet been able to make a WLP content
repository
work with
Oracle 8.1.7 and WLP 8.1.
I have tried several methods, including the ones mentioned here:
http://e-docs.bea.com/wlp/docs81/db/3Oracle.html (to move cgPool to an
Oracle
database), and by creating a completely new portal domain from scratch,
using
"Custom" (instead of Express) from the configuration wizard, setting
up the JDBC
pools to point to Oracle (connection passed, database load passed correctly).
I then deploy a simple Portal Application / Portal Project created in
workshop
as an EAR
(let's call it testPortal). Deployment seems to go fine. The outcome
of all
methods is the same: the administration portal works fine. When I click
on "Content",
I see the BEA repository. I can add nodes to the repository, AS LONG
AS THEY
ARE DIRECTLY UNDER the BEA repository (for example: BEA Repository/TestNode).
However, if I try to add a node under that node (for example: BEA Repository/TestNode/TestNodeChild),
I get the following error from the admin portal as a popup box:
- Error creating Node: TestChildNode. Please verify the Node name size
is within
Repository limits.
I can add any number of content items (including the standard content
types that
were loaded:
article, book, image, etc) or nodes directly under BEA Repository, but
I cannot
add anything under other nodes or the above error appears.
Some data is definitely getting to Oracle. After adding a node under
BEA Repository,
a record for that node shows up in the database. The JDBC log shows
an ORA-2291
(constraint violated) error (from jdbc.log):
java.sql.SQLException: ORA-02291: integrity constraint (DIAGEOCMS.FK1_CM_NODE)
v
iolated - parent key not found
This foreign key constraint is a pointer for the parent id of the node,
back into
the cm_node table.
If I roll back the cgPool to pointbase, it works fine. Just not with
an Oracle
8.1.7 cgPool
(or any other name, for that matter). I have tested this under both
Win 2K and
Linux AS.
Other details: I did use a non-XA driver as suggested in the edocs link
above.
For the cgPool, I used the Oracle Type 4 non-XA driver. I changed all
the relevant
data sources to point at the new pool. And I did change the cgJMS store
to use
the new pool as well.
Is anyone else successfully using Oracle 8.1.7 and Portal 8.1 with the
repository?
Sorry for the length of the message.. difficult one to explain.
Thanks,
Bob

Increasing field size in content repository

What is the best way to increase the field size in the content repository? We are using MS SQL Server and I can't find a way to adjust field width in the Weblogic Administration interface for creating a new repository. Should this be done in the underlying SQL Server? It seems to me that even if we did that, there is a seperate setting in the repository limiting field width, but I don't know how to access that value.
Thanks Much,
Tim

The NoSquint seems to work. The other one didn't install. I may have made a misstep.

Need Help Badly, Repository Error.....

The Qualifier:
I've searched and read through the archives and googled this to death, to no avail. So this is my last resort.
The Problem:
I'm trying to load images into the bea data repository using the provided tools. I can load string data, descriptions, etc. When I try to load a file, any file doc,txt,jpg,gif any thing, it will not accept a file larger than 0 bytes. the error is
"Error creating property: file. Please verify the Property size is within the Repository limits." It worked with PointBase but is not working with Oracle. Everything else seems to be okay, so I'm inclined to believe that he db is setup correctly.
The set up:
BEA WebLogic 8.1 sp3 (Portal)
Oracle 9.2.0.7.0
I've tried changing the driver, I've tried all of the following:
oracle.jdbc.xa.client.OracleXADataSource
oracle.jdbc.OracleDrive
oracle.jdbc.driver.OracleDriver
weblogic.jdbc.oracle.OracleDriver
weblogic.jdbc.oci.Driver
and the file name I'm try to upload is as short as I could make it: D:\test.jpg
please, if you have any ideas, I would be most greatful.
-K

Your server listens on port 12347. Your client tries to connect to a different port. No server is listening on the other port, so the connection is refused. Solution: make client connect to port 12347.

WLS 5.1 and TX support

          The Weblogic 5.10 documentation states:
          "WebLogic Server Version 5.1 is compliant with the JavaSoft EJB 1.1 specification."
          Yet elsewhere in the documentation it states:
          "The following sections describe EJBs in several transaction scenarios. Note that in all cases EJB transactions should be restricted to a single persistent store, because WebLogic Server does not provide a two-phase commit protocol. EJBs that engage in distributed transactions (transactions that make updates in multiple datastores) cannot guarantee that all branches of the transaction commit or roll back as a logical unit."
          Wait a minute. I thought EJB 1.1 specified that an EJB container must provide a transaction coordinator to support distributed two-phase commit across multiple EJB servers.
          From the spec:
          "Regardless whether an enterprise bean uses bean-managed or container-managed transaction demarcation,
          the burden of implementing transaction management is on the EJB Container and Server Provider.
          The EJB Container and Server implement the necessary low-level transaction protocols, such as the
          two-phase commit protocol between a transaction manager and a database system, transaction context
          propagation, and distributed two-phase commit."
          The spec goes on to show several distributed transaction use cases that must be supported by the EJB container.
          This "single repository" limitation of Weblogic severely limits my options.
          What am I missing?
          Greg


I used Loadrunner's WLS monitor while running some performance scripts on our application. I ended up relying on the WLS Console and some SNMP traps (using HP Openview to review data) in order to acurately guauge utilization of system resources...Regards,Steve

Please Help in solving this problem

I am getting following error when i try to add content to a node using administration
tool.
I am using WL workshop 8.1 Sp1 and using pointbase database.
Error message is as follows
<Feb 19, 2004 4:49:12 PM GMT+05:30> <Error> <ContentManager> <BEA-415470> <Error
creating Node. Repository: BEA Repository ParentId: 10003 NodeName: date1 Type:
1
com.bea.content.RepositoryRuntimeException: Error creating property: t. Please
v
erify the Property size is within the Repository limits.
at com.bea.content.repo.internal.RepoNodeOpsBean.createProperty(RepoNode
The property type is date. and i am getting same error for String and Integer
also.
Please help.
Thanks in advance.
Mahesh

Thanks for your reply.
I tried changinging driver. but of no use problem persists.
error code generated is as follows
<Feb 23, 2004 11:00:26 AM GMT+05:30> <Error> <ContentManager> <BEA-415470> <Erro
r creating Node. Repository: BEA Repository ParentId: 10003 NodeName: t Type:
1
com.bea.content.RepositoryRuntimeException: Error creating property: t. Please
v
erify the Property size is within the Repository limits.
at com.bea.content.repo.internal.RepoNodeOpsBean.createProperty(RepoNode
OpsBean.java:808)
at com.bea.content.repo.internal.RepoNodeOpsBean.createProperties(RepoNo
deOpsBean.java:594)
at com.bea.content.repo.internal.RepoNodeOpsBean.addNodeContent(RepoNode
OpsBean.java:1407)
at com.bea.content.repo.internal.RepoNodeOpsBean.createNode(RepoNodeOpsB
ean.java:974)
at com.bea.content.repo.internal.RepoNodeOpsEJB_orx781_ELOImpl.createNod
e(RepoNodeOpsEJB_orx781_ELOImpl.java:412)
at com.bea.content.spi.internal.NodeOpsImpl.createNode(NodeOpsImpl.java:
172)
at com.bea.content.manager.internal.NodeOpsImpl.createContentNode(NodeOp
sImpl.java:288)
at com.bea.jsptools.content.backing.BrowseJspBacking.updateContent(Brows
eJspBacking.java:612)
at com.bea.jsptools.content.backing.BrowseJspBacking.handlePageActions(B
rowseJspBacking.java:229)
at com.bea.jsptools.common.AdminToolsBacking.handlePostbackData(AdminToo
lsBacking.java:95)
at com.bea.netuix.servlets.controls.content.JspContent.handlePostbackDat
a(JspContent.java:242)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:216)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
ava:278)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
ava:285)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
ava:285)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
ava:285)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
ava:285)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
ava:285)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
ava:285)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.j
ava:285)
Pls suggest solution
With regards
Mahesh
"Kailash" <[email protected]> wrote:
>
Hi
If you are using weblogic supplied JDBC type 4 driver, switch to vendor
supplied
type 4 (nonXA) driver and it may resolve your problem. For CMS related
tables,
binary files are stored as BLOB in db for which weblogic drivers has
problem.
Regards
"Mahesh" <[email protected]> wrote:
I am getting following error when i try to add content to a node using
administration
tool.
I am using WL workshop 8.1 Sp1 and using pointbase database.
Error message is as follows
<Feb 19, 2004 4:49:12 PM GMT+05:30> <Error> <ContentManager> <BEA-415470>
<Error
creating Node. Repository: BEA Repository ParentId: 10003 NodeName:
date1 Type:
1
com.bea.content.RepositoryRuntimeException: Error creating property:
t. Please
v
erify the Property size is within the Repository limits.
at com.bea.content.repo.internal.RepoNodeOpsBean.createProperty(RepoNode
The property type is date. and i am getting same error for String and
Integer
also.
Please help.
Thanks in advance.
Mahesh

FS Repository Manager depth limits - crawling problems

Ciao a tuti.
I have some really strange results from my Crawler. Here is the story:
After Crawling 50000 for indexing I have around 800 docs where I have the Error Type: crawler.
The interesting thing is that these documents have nothing in common & even via PCD there are "there" but after clicking on it, the message says: the document does not exist.
So where can I start with the research? Maybe out there has someone a good idea?!
Originally I thought, that I have a problem with the depth of the file structure, cause the structure is reallly complex. On the other hand I could not found any limitations for the FS Repository Manager.
Thanx in advance

Sir or madam -
First, you may be hitting a URL limit of 256 characters. Are you using the /irj/go/km/docs path to access the documents, or are you using the old method?
Second, if you create a CM repository with FSDB persistence, do you have the same issues?
Third, how deep into the repository does it go before an error is thrown? Have you tried creating a test index directly to the folder/document in question?
Good luck!
Kyle

Expand essbase alias length limitation via relational source in repository?

Essbase 9.3.1 + OBI 10.1.3.4
Essbase has limitation of 80 chr for every member or alias name.
1 dimension in essbase is to have members with length>>80 chr(up to 250)
Can i use codes in this dimension in essabase when calculating then anyhow federate in repository cube and relational table with 2 columns(code, fullname) and show in answers relational fullname instead of cube code?
Thanx))

Hi,
I do not think so, as evaluate would be your best option, but that would only 'point at' the underlying data source (essbase), NOT the rdbms in question.
You cannot even do the standard cross-database hybridisation with essbase / rdbms - unless anyone knows otherwise??
You could possibly export your data from essbase to your rdbms using the interface tables and then correct any data inadequacies in the rdbms table - but this is only okay if you are happy with it not being real-time.
Sorry to ask / hi-jack your thread, but I have been trying to crack using essbase in 10.1.3.4 for some time and have succeed apart from I am struggling on creating the Aliases that do not import into the repository on the initial import, would you mind sharing the 'trick' to getting ALIAS values into the reposity please?
Best regards,
Robert.

Database limits for Grid control repository?

Document "Oracle® Database Licensing Information / 10g Release 2 (10.2)" [Part Number B14199-10] discusses the restricted use license of database for grid control repository and rman repository use.
nfrastructure Repository Databases A separate Oracle Database can be installed and used as a Recovery Manager (RMAN) repository without additional license requirements, provided that all the Oracle databases managed in this repository are correctly licensed. This repository database may also be used for the Oracle Enterprise Grid Control repository. It may not be used or deployed for other uses.
A separate Oracle Database can be installed and used as a Oracle Enterprise Manager Grid Control (OEM Grid Control) repository without additional license requirements, provided that all the targets (databases, applications, and so forth) managed in this repository are correctly licensed. This database may also be used for the RMAN repository. It may not be used or deployed for other uses.
There is no discussion of licensing requirements for options of the database (RAC, partitioning, etc) when the database stays within these repository use restrictions. Therefore it is unclear whether the Grid Control can be configured to provide appropriate monitoring without additional licenses.

This is the reply I received from release
management:
If they have deployed an EE edition of the database
as an OEM repository, and then want to protect that
with RAC or Data Guard, or make more Secure with ASO
or Database Vault, or indeed get any of the
additional benefits any of the options provide, then
they will need to license the option.
Let me know if that is still not clear, and I'll go
back again.Thanks.
There is a minor inconsistency in their response ... they say "if deployed on EE". However, as far as I know OEM repository required VPD, which is available only on Enterprise Edition (see http://download-east.oracle.com/docs/cd/B16240_01/doc/em.102/e10953/pre-installation_req.htm#CHDGIEAD)
However, it is quite clear that 'they' are telling us that the RAC option is not inherent in the "Special Use Licensing" as described http://download.oracle.com/docs/cd/B19306_01/license.102/b14199/editions.htm#CJAHFHBJ .
The implication (not necessarily a topic for this forum) is that the OEM is not guaranteed to be able to provide basic monitoring and reporting functionality without additional license fees to make OEM more highly available than the targets being monitored.
It would be nice to have the information about which Oracle products (database and app server) have included licenses with a basic Grid Control install and which require additional licenses as part of Chapter 1 of http://download.oracle.com/docs/cd/B19306_01/license.102/b40010/toc.htm (That document goes into excruciating detail about the extra packs, but ignores the basics.)
For that matter, since OEM Grid Control can not be purchased, it would be nice to have a list of products that provide license to install Grid Control, again in Chapter 1 of the Grid Control Licensing document listed above.
I appreciate your time in having dug into this.

DFS replication stopped working and cannot be debugged because WMI repository cannot be accessed

Hello,
two days ago our DFS replication suddendly stopped working sometime around midnight local time. At least this is what our second domain controller is reporting. Event log is flooded with event id 5002 from DFSR. It is unclear what caused this sudden problem
and even worse, how to solve it. First thing I tried was to perform propagation tests. According to propagation report none of them was successful. Creating an integrity report brought me to another problem: It fails with two errors. First it is unable to
connect to the other DC. Second it is unable to access local WMI repository. This is true for both machines.
First I tried to find information on possible problems with WMI. WMIdiag provided a lot of information. However, opinions I found on the net largely disagree whether output from WMIdiag is useful or not. Yet I tried to re-compile .mof files and rebuild the
repository. So far, nothing changed. This is my output from WMIdiag:
34309 13:02:46 (0) ** WMIDiag v2.1 started on Donnerstag, 22. Mai 2014 at 12:49.
34310 13:02:46 (0) **
34311 13:02:46 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
34312 13:02:46 (0) **
34313 13:02:46 (0) ** This script is not supported under any Microsoft standard support program or service.
34314 13:02:46 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
34315 13:02:46 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
34316 13:02:46 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
34317 13:02:46 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
34318 13:02:46 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
34319 13:02:46 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
34320 13:02:46 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
34321 13:02:46 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
34322 13:02:46 (0) ** of the possibility of such damages.
34323 13:02:46 (0) **
34324 13:02:46 (0) **
34325 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34326 13:02:46 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
34327 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34328 13:02:46 (0) **
34329 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34330 13:02:46 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'COM\ABCDEF' on computer 'DC2'.
34331 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34332 13:02:46 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
34333 13:02:46 (0) ** INFO: => 1 possible incorrect shutdown(s) detected on:
34334 13:02:46 (0) ** - Shutdown on 01 April 2014 10:20:54 (GMT-0).
34335 13:02:46 (0) **
34336 13:02:46 (0) ** System drive: ....................................................................................................... C: (Datenträgernr. 0 Partitionsnr. 1).
34337 13:02:46 (0) ** Drive type: ......................................................................................................... SCSI (Adaptec Array SCSI Disk Device).
34338 13:02:46 (0) ** There are no missing WMI system files: .............................................................................. OK.
34339 13:02:46 (0) ** There are no missing WMI repository files: .......................................................................... OK.
34340 13:02:46 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
34341 13:02:46 (0) ** AFTER running WMIDiag:
34342 13:02:46 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
34343 13:02:46 (0) ** - Disk free space on 'C:': .......................................................................................... 10665 MB.
34344 13:02:46 (0) ** - INDEX.BTR, 4276224 bytes, 22.05.2014 12:52:30
34345 13:02:46 (0) ** - MAPPING1.MAP, 67248 bytes, 22.05.2014 12:52:30
34346 13:02:46 (0) ** - MAPPING2.MAP, 67168 bytes, 22.05.2014 12:48:33
34347 13:02:46 (0) ** - OBJECTS.DATA, 23126016 bytes, 22.05.2014 12:52:30
34348 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34349 13:02:46 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
34350 13:02:46 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
34351 13:02:46 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
34352 13:02:46 (0) ** => This will prevent any WMI remote connectivity to this computer except
34353 13:02:46 (0) ** if the following three inbound rules are ENABLED and non-BLOCKING:
34354 13:02:46 (0) ** - 'Windows Management Instrumentation (DCOM-In)'
34355 13:02:46 (0) ** - 'Windows Management Instrumentation (WMI-In)'
34356 13:02:46 (0) ** - 'Windows Management Instrumentation (ASync-In)'
34357 13:02:46 (0) ** Verify the reported status for each of these three inbound rules below.
34358 13:02:46 (0) **
34359 13:02:46 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' group rule: ............................................. DISABLED.
34360 13:02:46 (0) ** => This will prevent any WMI remote connectivity to/from this machine.
34361 13:02:46 (0) ** - You can adjust the configuration by executing the following command:
34362 13:02:46 (0) ** i.e. 'NETSH.EXE ADVFIREWALL FIREWALL SET RULE GROUP="Windows Management Instrumentation (WMI)" NEW ENABLE=YES'
34363 13:02:46 (0) ** Note: With this command all inbound and outbound WMI rules are activated at once!
34364 13:02:46 (0) ** You can also enable each individual rule instead of activating the group rule.
34365 13:02:46 (0) **
34366 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34367 13:02:46 (0) ** DCOM Status: ........................................................................................................ OK.
34368 13:02:46 (0) ** WMI registry setup: ................................................................................................. OK.
34369 13:02:46 (0) ** INFO: WMI service has dependents: ................................................................................... 1 SERVICE(S)!
34370 13:02:46 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
34371 13:02:46 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
34372 13:02:46 (0) ** Note: If the service is marked with (*), it means that the service/application uses WMI but
34373 13:02:46 (0) ** there is no hard dependency on WMI. However, if the WMI service is stopped,
34374 13:02:46 (0) ** this can prevent the service/application to work as expected.
34375 13:02:46 (0) **
34376 13:02:46 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
34377 13:02:46 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
34378 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34379 13:02:46 (0) ** WMI service DCOM setup: ............................................................................................. OK.
34380 13:02:46 (0) ** WMI components DCOM registrations: .................................................................................. OK.
34381 13:02:46 (0) ** WMI ProgID registrations: ........................................................................................... OK.
34382 13:02:46 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
34383 13:02:46 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
34384 13:02:46 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
34385 13:02:46 (2) !! WARNING: Some WMI providers EXE/DLL file(s) are missing: ............................................................ 1 WARNING(S)!
34386 13:02:46 (0) ** - ROOT/MICROSOFTACTIVEDIRECTORY, ReplProv1, replprov.dll
34387 13:02:46 (0) ** => This will make any operations related to the WMI class supported by the provider(s) to fail.
34388 13:02:46 (0) ** This can be due to:
34389 13:02:46 (0) ** - the de-installation of the software.
34390 13:02:46 (0) ** - the deletion of some files.
34391 13:02:46 (0) ** => If the software has been de-installed intentionally, then this information must be
34392 13:02:46 (0) ** removed from the WMI repository. You can use the 'WMIC.EXE' command to remove
34393 13:02:46 (0) ** the provider registration data.
34394 13:02:46 (0) ** i.e. 'WMIC.EXE /NAMESPACE:\\ROOT\MICROSOFTACTIVEDIRECTORY path __Win32Provider Where Name='ReplProv1' DELETE'
34395 13:02:46 (0) ** => If not, you must restore a copy of the missing provider EXE/DLL file(s) as indicated by the path.
34396 13:02:46 (0) ** You can retrieve the missing file from:
34397 13:02:46 (0) ** - A backup.
34398 13:02:46 (0) ** - The Windows CD.
34399 13:02:46 (0) ** - Another Windows installation using the same version and service pack level of the examined system.
34400 13:02:46 (0) ** - The original CD or software package installing this WMI provider.
34401 13:02:46 (0) **
34402 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34403 13:02:46 (0) ** INFO: User Account Control (UAC): ................................................................................... DISABLED.
34404 13:02:46 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
34405 13:02:46 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
34406 13:02:46 (0) ** privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
34407 13:02:46 (0) ** to ensure that administrative privileges are granted. If a Local User account is used for remote
34408 13:02:46 (0) ** accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
34409 13:02:46 (0) **
34410 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
34411 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\ANONYMOUS LOGON' has been REMOVED!
34412 13:02:46 (0) ** - REMOVED ACE:
34413 13:02:46 (0) ** ACEType: &h0
34414 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34415 13:02:46 (0) ** ACEFlags: &h0
34416 13:02:46 (0) ** ACEMask: &h7
34417 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34418 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
34419 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
34420 13:02:46 (0) **
34421 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34422 13:02:46 (0) ** Removing default security will cause some operations to fail!
34423 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34424 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34425 13:02:46 (0) **
34426 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
34427 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
34428 13:02:46 (0) ** - REMOVED ACE:
34429 13:02:46 (0) ** ACEType: &h0
34430 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34431 13:02:46 (0) ** ACEFlags: &h0
34432 13:02:46 (0) ** ACEMask: &h7
34433 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34434 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
34435 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
34436 13:02:46 (0) **
34437 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34438 13:02:46 (0) ** Removing default security will cause some operations to fail!
34439 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34440 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34441 13:02:46 (0) **
34442 13:02:46 (0) ** DCOM security for 'My Computer' (Access Permissions/Edit Limits): ................................................... MODIFIED.
34443 13:02:46 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
34444 13:02:46 (0) ** - REMOVED ACE:
34445 13:02:46 (0) ** ACEType: &h0
34446 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34447 13:02:46 (0) ** ACEFlags: &h0
34448 13:02:46 (0) ** ACEMask: &h7
34449 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34450 13:02:46 (0) ** DCOM_RIGHT_ACCESS_LOCAL
34451 13:02:46 (0) ** DCOM_RIGHT_ACCESS_REMOTE
34452 13:02:46 (0) **
34453 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34454 13:02:46 (0) ** Removing default security will cause some operations to fail!
34455 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34456 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34457 13:02:46 (0) **
34458 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
34459 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
34460 13:02:46 (0) ** - REMOVED ACE:
34461 13:02:46 (0) ** ACEType: &h0
34462 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34463 13:02:46 (0) ** ACEFlags: &h0
34464 13:02:46 (0) ** ACEMask: &h1F
34465 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34466 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34467 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34468 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34469 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34470 13:02:46 (0) **
34471 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34472 13:02:46 (0) ** Removing default security will cause some operations to fail!
34473 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34474 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34475 13:02:46 (0) **
34476 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
34477 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
34478 13:02:46 (0) ** - REMOVED ACE:
34479 13:02:46 (0) ** ACEType: &h0
34480 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34481 13:02:46 (0) ** ACEFlags: &h0
34482 13:02:46 (0) ** ACEMask: &h1F
34483 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34484 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34485 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34486 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34487 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34488 13:02:46 (0) **
34489 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34490 13:02:46 (0) ** Removing default security will cause some operations to fail!
34491 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34492 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34493 13:02:46 (0) **
34494 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Default): ..................................... MODIFIED.
34495 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
34496 13:02:46 (0) ** - REMOVED ACE:
34497 13:02:46 (0) ** ACEType: &h0
34498 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34499 13:02:46 (0) ** ACEFlags: &h0
34500 13:02:46 (0) ** ACEMask: &h1F
34501 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34502 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34503 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34504 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34505 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34506 13:02:46 (0) **
34507 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34508 13:02:46 (0) ** Removing default security will cause some operations to fail!
34509 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34510 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34511 13:02:46 (0) **
34512 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
34513 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
34514 13:02:46 (0) ** - REMOVED ACE:
34515 13:02:46 (0) ** ACEType: &h0
34516 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34517 13:02:46 (0) ** ACEFlags: &h0
34518 13:02:46 (0) ** ACEMask: &h1F
34519 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34520 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34521 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34522 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34523 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34524 13:02:46 (0) **
34525 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34526 13:02:46 (0) ** Removing default security will cause some operations to fail!
34527 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34528 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34529 13:02:46 (0) **
34530 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
34531 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\PERFORMANCE LOG USERS' has been REMOVED!
34532 13:02:46 (0) ** - REMOVED ACE:
34533 13:02:46 (0) ** ACEType: &h0
34534 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34535 13:02:46 (0) ** ACEFlags: &h0
34536 13:02:46 (0) ** ACEMask: &h1F
34537 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34538 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34539 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34540 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34541 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34542 13:02:46 (0) **
34543 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34544 13:02:46 (0) ** Removing default security will cause some operations to fail!
34545 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34546 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34547 13:02:46 (0) **
34548 13:02:46 (0) ** DCOM security for 'My Computer' (Launch & Activation Permissions/Edit Limits): ...................................... MODIFIED.
34549 13:02:46 (1) !! ERROR: Default trustee 'EVERYONE' has been REMOVED!
34550 13:02:46 (0) ** - REMOVED ACE:
34551 13:02:46 (0) ** ACEType: &h0
34552 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34553 13:02:46 (0) ** ACEFlags: &h0
34554 13:02:46 (0) ** ACEMask: &hB
34555 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34556 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34557 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34558 13:02:46 (0) **
34559 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34560 13:02:46 (0) ** Removing default security will cause some operations to fail!
34561 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34562 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34563 13:02:46 (0) **
34564 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34565 13:02:46 (1) !! ERROR: Default trustee 'BUILTIN\ADMINISTRATORS' has been REMOVED!
34566 13:02:46 (0) ** - REMOVED ACE:
34567 13:02:46 (0) ** ACEType: &h0
34568 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34569 13:02:46 (0) ** ACEFlags: &h0
34570 13:02:46 (0) ** ACEMask: &h1F
34571 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34572 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34573 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34574 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34575 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34576 13:02:46 (0) **
34577 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34578 13:02:46 (0) ** Removing default security will cause some operations to fail!
34579 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34580 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34581 13:02:46 (0) **
34582 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34583 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\INTERACTIVE' has been REMOVED!
34584 13:02:46 (0) ** - REMOVED ACE:
34585 13:02:46 (0) ** ACEType: &h0
34586 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34587 13:02:46 (0) ** ACEFlags: &h0
34588 13:02:46 (0) ** ACEMask: &h1F
34589 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34590 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34591 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34592 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34593 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34594 13:02:46 (0) **
34595 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34596 13:02:46 (0) ** Removing default security will cause some operations to fail!
34597 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34598 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34599 13:02:46 (0) **
34600 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34601 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\SYSTEM' has been REMOVED!
34602 13:02:46 (0) ** - REMOVED ACE:
34603 13:02:46 (0) ** ACEType: &h0
34604 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34605 13:02:46 (0) ** ACEFlags: &h0
34606 13:02:46 (0) ** ACEMask: &h1F
34607 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34608 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34609 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34610 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34611 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34612 13:02:46 (0) **
34613 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34614 13:02:46 (0) ** Removing default security will cause some operations to fail!
34615 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34616 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34617 13:02:46 (0) **
34618 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34619 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!
34620 13:02:46 (0) ** - REMOVED ACE:
34621 13:02:46 (0) ** ACEType: &h0
34622 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34623 13:02:46 (0) ** ACEFlags: &h0
34624 13:02:46 (0) ** ACEMask: &h1F
34625 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34626 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34627 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34628 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34629 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34630 13:02:46 (0) **
34631 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34632 13:02:46 (0) ** Removing default security will cause some operations to fail!
34633 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34634 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34635 13:02:46 (0) **
34636 13:02:46 (0) ** DCOM security for 'Microsoft WMI Provider Subsystem Host' (Launch & Activation Permissions): ........................ MODIFIED.
34637 13:02:46 (1) !! ERROR: Default trustee 'NT AUTHORITY\LOCAL SERVICE' has been REMOVED!
34638 13:02:46 (0) ** - REMOVED ACE:
34639 13:02:46 (0) ** ACEType: &h0
34640 13:02:46 (0) ** ACCESS_ALLOWED_ACE_TYPE
34641 13:02:46 (0) ** ACEFlags: &h0
34642 13:02:46 (0) ** ACEMask: &h1F
34643 13:02:46 (0) ** DCOM_RIGHT_EXECUTE
34644 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_LOCAL
34645 13:02:46 (0) ** DCOM_RIGHT_LAUNCH_REMOTE
34646 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_LOCAL
34647 13:02:46 (0) ** DCOM_RIGHT_ACTIVATE_REMOTE
34648 13:02:46 (0) **
34649 13:02:46 (0) ** => The REMOVED ACE was part of the DEFAULT setup for the trustee.
34650 13:02:46 (0) ** Removing default security will cause some operations to fail!
34651 13:02:46 (0) ** It is possible to fix this issue by editing the security descriptor and adding the ACE.
34652 13:02:46 (0) ** For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
34653 13:02:46 (0) **
34654 13:02:46 (0) **
34655 13:02:46 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
34656 13:02:46 (0) ** DCOM security error(s) detected: .................................................................................... 14.
34657 13:02:46 (0) ** WMI security warning(s) detected: ................................................................................... 0.
34658 13:02:46 (0) ** WMI security error(s) detected: ..................................................................................... 0.
34659 13:02:46 (0) **
34660 13:02:46 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
34661 13:02:46 (0) ** Overall WMI security status: ........................................................................................ OK.
34662 13:02:46 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
34663 13:02:46 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 1.
34664 13:02:46 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
34665 13:02:46 (0) ** 'select * from MSFT_SCMEventLogEvent'
34666 13:02:46 (0) **
34667 13:02:46 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
34668 13:02:46 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
34669 13:02:46 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
34670 13:02:46 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
34671 13:02:46 (0) ** - ROOT/SERVICEMODEL.
34672 13:02:46 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
34673 13:02:46 (0) ** use an encrypted connection by specifying the PACKET PRIVACY authentication level.
34674 13:02:46 (0) ** (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
34675 13:02:46 (0) ** i.e. 'WMIC.EXE /NODE:"ISWDC2" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
34676 13:02:46 (0) **
34677 13:02:46 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
34678 13:02:46 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
34679 13:02:46 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 32 ERROR(S)!
34680 13:02:46 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34681 13:02:46 (0) ** MOF Registration: ''
34682 13:02:46 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34683 13:02:46 (0) ** MOF Registration: ''
34684 13:02:46 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34685 13:02:46 (0) ** MOF Registration: ''
34686 13:02:46 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34687 13:02:46 (0) ** MOF Registration: ''
34688 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34689 13:02:46 (0) ** MOF Registration: ''
34690 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_BITS_BITSNetUtilization, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34691 13:02:46 (0) ** MOF Registration: ''
34692 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34693 13:02:46 (0) ** MOF Registration: ''
34694 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34695 13:02:46 (0) ** MOF Registration: ''
34696 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34697 13:02:46 (0) ** MOF Registration: ''
34698 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34699 13:02:46 (0) ** MOF Registration: ''
34700 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34701 13:02:46 (0) ** MOF Registration: ''
34702 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34703 13:02:46 (0) ** MOF Registration: ''
34704 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34705 13:02:46 (0) ** MOF Registration: ''
34706 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34707 13:02:46 (0) ** MOF Registration: ''
34708 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34709 13:02:46 (0) ** MOF Registration: ''
34710 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34711 13:02:46 (0) ** MOF Registration: ''
34712 13:02:46 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34713 13:02:46 (0) ** MOF Registration: ''
34714 13:02:46 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34715 13:02:46 (0) ** MOF Registration: ''
34716 13:02:46 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34717 13:02:46 (0) ** MOF Registration: ''
34718 13:02:46 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34719 13:02:46 (0) ** MOF Registration: ''
34720 13:02:46 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34721 13:02:46 (0) ** MOF Registration: ''
34722 13:02:46 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34723 13:02:46 (0) ** MOF Registration: ''
34724 13:02:46 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34725 13:02:46 (0) ** MOF Registration: ''
34726 13:02:46 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34727 13:02:46 (0) ** MOF Registration: ''
34728 13:02:46 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34729 13:02:46 (0) ** MOF Registration: ''
34730 13:02:46 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34731 13:02:46 (0) ** MOF Registration: ''
34732 13:02:46 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34733 13:02:46 (0) ** MOF Registration: ''
34734 13:02:46 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34735 13:02:46 (0) ** MOF Registration: ''
34736 13:02:46 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34737 13:02:46 (0) ** MOF Registration: ''
34738 13:02:46 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34739 13:02:46 (0) ** MOF Registration: ''
34740 13:02:46 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34741 13:02:46 (0) ** MOF Registration: ''
34742 13:02:46 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
34743 13:02:46 (0) ** MOF Registration: ''
34744 13:02:46 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
34745 13:02:46 (0) ** a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
34746 13:02:46 (0) ** You can refresh the WMI class provider buffer with the following command:
34747 13:02:46 (0) **
34748 13:02:46 (0) ** i.e. 'WINMGMT.EXE /SYNCPERF'
34749 13:02:46 (0) **
34750 13:02:46 (0) ** WMI MOF representations: ............................................................................................ OK.
34751 13:02:46 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
34752 13:02:46 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
34753 13:02:46 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
34754 13:02:46 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
34755 13:02:46 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
34756 13:02:46 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
34757 13:02:46 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
34758 13:02:46 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
34759 13:02:46 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
34760 13:02:46 (0) **
34761 13:02:46 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
34762 13:02:46 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
34763 13:02:46 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
34764 13:02:46 (0) ** WMI static instances retrieved: ..................................................................................... 1822.
34765 13:02:46 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
34766 13:02:46 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
34767 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34768 13:02:46 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
34769 13:02:46 (0) ** DCOM: ............................................................................................................. 0.
34770 13:02:46 (0) ** WINMGMT: .......................................................................................................... 0.
34771 13:02:46 (0) ** WMIADAPTER: ....................................................................................................... 0.
34772 13:02:46 (0) **
34773 13:02:46 (0) ** # of additional Event Log events AFTER WMIDiag execution:
34774 13:02:46 (0) ** DCOM: ............................................................................................................. 0.
34775 13:02:46 (0) ** WINMGMT: .......................................................................................................... 0.
34776 13:02:46 (0) ** WMIADAPTER: ....................................................................................................... 0.
34777 13:02:46 (0) **
34778 13:02:46 (0) ** 32 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
34779 13:02:46 (0) ** => This error is typically a WMI error. This WMI error is due to:
34780 13:02:46 (0) ** - a missing WMI class definition or object.
34781 13:02:46 (0) ** (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
34782 13:02:46 (0) ** You can correct the missing class definitions by:
34783 13:02:46 (0) ** - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
34784 13:02:46 (0) ** Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
34785 13:02:46 (0) ** (This list can be built on a similar and working WMI Windows installation)
34786 13:02:46 (0) ** The following command line must be used:
34787 13:02:46 (0) ** i.e. 'WMIDiag CorrelateClassAndProvider'
34788 13:02:46 (0) ** Note: When a WMI performance class is missing, you can manually resynchronize performance counters
34789 13:02:46 (0) ** with WMI by starting the ADAP process.
34790 13:02:46 (0) ** - a WMI repository corruption.
34791 13:02:46 (0) ** In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
34792 13:02:46 (0) ** to validate the WMI repository operations.
34793 13:02:46 (0) ** Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
34794 13:02:46 (0) ** executing the WriteInRepository command. To write temporary data from the Root namespace, use:
34795 13:02:46 (0) ** i.e. 'WMIDiag WriteInRepository=Root'
34796 13:02:46 (0) ** - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
34797 13:02:46 (0) ** the WMI repository must be reconstructed.
34798 13:02:46 (0) ** Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
34799 13:02:46 (0) ** otherwise some applications may fail after the reconstruction.
34800 13:02:46 (0) ** This can be achieved with the following command:
34801 13:02:46 (0) ** i.e. 'WMIDiag ShowMOFErrors'
34802 13:02:46 (0) ** Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
34803 13:02:46 (0) ** ALL fixes previously mentioned.
34804 13:02:46 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
34805 13:02:46 (0) **
34806 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34807 13:02:46 (0) ** WMI Registry key setup: ............................................................................................. OK.
34808 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34809 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34810 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34811 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34812 13:02:46 (0) **
34813 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34814 13:02:46 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
34815 13:02:46 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
34816 13:02:46 (0) **
34817 13:02:46 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\ABCDEF\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_ISWDC2_2014.05.22_12.49.13.LOG' for details.
34818 13:02:46 (0) **
34819 13:02:46 (0) ** WMIDiag v2.1 ended on Donnerstag, 22. Mai 2014 at 13:02 (W:89 E:52 S:1).
There are a lot of error in the report and I don't know, whether they are relevant or how to solve them. To my current knowledge, I need to solve at least some of them so that I can access the local WMI repository again and get replication back working.
But after hours of research I am stuck. Any hints are greatly appreciated.
Regards,
Oliver

I don't know why, but soon after posting this, I found a solution to the problem. The WMI part was solved in this thread:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/953be9ef-e9e3-4885-a5c4-47fc475ba562/dfs-is-not-working-anymore?forum=winserverfiles
The relevant portion is this:
Open a CMD prompt in %windir%\system32\wbem
mofcomp dfsrprovs.mof
net stop winmgmt
net start winmgmt
net start iphlpsvc
net stop dfsr
net start dfsr
I don't know why recompiling of all mof did not solve the problem, but the solution above did. Restarting the DCs solved the communication issue. I don't know why the primary DC forgot about the WMI DFS provider or why communication failed. However, it is
working again, it seems.

RE: repository limitations

Similar Messages

Maybe you are looking for