Debug replication
Hi,
I am trying to replicate cProject to R/3 for accounting integration functions using single-object controlling in SAP CO. The information is transferred to the backend system. But an internal order is not created. The controlling cockpit shows the message that a company code could not be determined for the internal order.
I did not transfer HR organization information to cProjects. So I belive the company code should be determined from the model order for order type CPR1, which is not happening in my case.
Can any one provide some information on how to debug the replication process.
Thanks,
Rajesh.
Hi,
- Stop the outbound queue of the CRM system (transaction smqr).
- Resend/ Reprocess the bdoc.
(another possibility is to reprocess the bdoc while entering debugging and flagging the "in background task: do no process'-flag in the debug settings)
- Find the entry in the outbound queue in 'ready' state.
- Make sure the user specified in the queue is a dialog user in both systems.
- Debug the queue-entry from the outbound queue.
You can also find a best practice document for bdoc errors on the following location:
https://websmp202.sap-ag.de/crm-mw
Kind regards,
Michael Van Geet.
Similar Messages
-
Session Replication doesn't work when using a custom Unicast Channel
Hello!
After configure a WLS Cluster for an WebApp with session replication support enabled I faced some issues with cluster configuration.
My LAB env used for this configurations is:
One Solaris 10 SPARC box.
-- One WLS 11g (10.3.6) domain with:
---- 4 Managed servers:
---- Admin server
---- server-1
---- server-2
---- Proxy Server (HttpClusterServlet)
--- 1 Cluster composed by:
---- server-1
---- server-2In that setup I noticed if I define a custom network channel for servers ( server>protocols>channels ) in the cluster and set Cluster Messaging Mode as Unicast* in the Cluster config ( Cluster>Configuration>Messaging>Messaging Mode ), so the session state replication does not work.
When I enable the cluster replication debug for managed servers the following messages appears:
<> <> <1358966729933> <BEA-000000> <[roid:-1772481434088297851] Creating primary for application key /webapp>
####<Jan 23, 2013 4:45:29 PM BRST> <Debug> <ReplicationDetails> <de25503> <server-1> <[ACTIVE] ExecuteThread: '5' for queue: > 'weblogic.kernel.Default (self-tuning)'> <<ano
nymous>> <> <> <1358966729958> <BEA-000000> *<Has secondary servers? false>*
####<Jan 23, 2013 4:45:29 PM BRST> <Debug> <ReplicationDetails> <de25503> <server-1> <[ACTIVE] ExecuteThread: '5' for queue: >'weblogic.kernel.Default (self-tuning)'> <<ano
nymous>> <> <> <1358966729959> <BEA-000000> *<Current secondary server? null>*
####<Jan 23, 2013 4:45:29 PM BRST> <Debug> <Replication> <de25503> <server-1> <[ACTIVE] ExecuteThread: '5' for queue: >'weblogic.kernel.Default (self-tuning)'> <<anonymous>
<> <> <1358966729959> <BEA-000000> <[roid:-1772481434088297851] Unable to create secondary on null>
####<Jan 23, 2013 4:45:31 PM BRST> <Debug> <ReplicationDetails> <de25503> <server-1> <[ACTIVE] ExecuteThread: '5' for queue: >'weblogic.kernel.Default (self-tuning)'> After eliminate all possible issues with my webapp (serialization, weblogic descriptor configuration, etc) and try many cluster network configurations I noticed that this problem only occurs when I use Unicast for Cluster's Messaging.
At the end of the day I really would like to understand why the session replication only works for Cluster's Messaging using Multicast mode. I read a lot the WLS docs (specifically the cluster/network topics) [1][2], but I can't find an official explanation about this.
Can someone help me understand this behavior?
Many thanks.
[1] http://docs.oracle.com/cd/E15523_01/web.1111/e13701/network.htm
[2] http://docs.oracle.com/cd/E15523_01/web.1111/e13709/setup.htmI have Fluxbox started with Slim and .xinitrc. Dbus works only with:
exec ck-launch-session startfluxbox
you need run Openbox with ck-launch-session:
exec ck-launch-session openbox-session
Bye!! -
3rd party distributed SW load balancing with In-Memory Replication
Hi,
Could someone please comment on the feasibility of the following setup?
I've started testing replication with a software load balancing product. This
product lets all nodes receive all packets and uses a kernel-level filter
to let only one node at the time receive it. Since there's minimum 1 heartbeat
between the nodes, there are several NICs in each node.
At the moment it seems like it doesn't work: - I use the SessionServlet - with
a 2-node cluster I first have the 2 nodes up and I access it with a single client:
.the LB is configured to be sticky wrt. source IP address, so the same node gets
all the traffic - when I stop the node receiving the traffic the other node takes
over (I changed the colours of SessionServlet) . however, the counter restarts
at zero
From what I read of the in-memory replication documentation I thought that it
might work also with a distributed software load balancing cluster. Any comments
on the feasability of this?
Is there a way to debug replication (in WLS6SP1)? I don't see any replication
messages in the logs, so I'm not even sure that it works at all. - I do get a
message about "Clustering Services startting" when I start the examples server
on each node - is there anything tto look for in the console to make sure that
things are working? - the evaluation license for WLS6SP1 on NT seems to support
In-Memory Replication and Cluster. However, I've also seen a Cluster-II somewhere:
is that needed?
Thanks for your attention!
Regards, Frank Olsen
We are considering Resonate as one of the software load balancer. We haven't certified
them yet. I have no idea how long its going to take.
As a base rule if the SWLB can do the load balancing and maintain stickyness that is fine
with us as long as it doesn't modify the cookie or the URL if URL rewriting is enabled.
Having said that if you run into problems we won't be able to support you since it is not
certified.
-- Prasad
Frank Olsen wrote:
> Prasad Peddada <[email protected]> wrote:
> >Frank Olsen wrote:
> >
> >> Hi,
> >>
> > We don't support any 3rd party software load balancers.
>
> Does that mean that there are technical reasones why it won't work, or just that
> you haven't tested it?
>
> > As >I said before I am thinking your configuration is >incorrect if n-memory
> replication is not working. I would >strongly suggest you look at webapp deployment
> descriptor and >then the config.xml file.
>
> OK.
>
> >Also doing sticky based on source ip address is not good. You >should do it based
> on passive cookie persistence or active >cookie persistence (with cookie insert,
> a new one).
> >
>
> I agree that various source-based sticky options (IP, port; network) are not the
> best solution. In our current implementation we can't do this because the SW load
> balancer is based on filtering IP packets on the driver level.
>
> Currently I'm more interested in understanding whether it can our SW load balancer
> can work with your replication at all?
>
> What makes me think that it could work is that in WLS6.0 a session failed over
> to any cluster node can recover the replicated session.
>
> Can there be a problem with the cookies?
> - are the P/S for replication put in the cookie by the node itself or by the proxy/HW
> load balancer?
>
> >
> >The options are -Dweblogic.debug.DebugReplication=true and
> >-Dweblogic.debug.DebugReplicationDetails=true
> >
>
> Great, thanks!
>
> Regards,
> Frank Olsen
-
Strange errors in session replication
I get following errors in session replication :
weblogic.utils.NestedError: Tried to update secondary, but it thought
it was the primary
- with nested exception:
[weblogic.cluster.replication.BadStatusException: updateSecondary
found
-148099416498695151 but it is not the primary]
Using Weblogic451, SP7 on Solaris 2.6.
Any clues ??
-Kuntal Shah.
Hello,
> > Alteon is set to use "permanent hashing" to route the client into
> > the same server in each request.
>
> How do you expect the switch to know about the secondary node
> if the primary fails? This information is stored in the URL and
> parsed by a proxy.
It took a couple of days and fair amount of documentation to understand
the behaviour of the web cluster...;-)
We changed the configuration to include two proxy servers between the
Alteon switch and web cluster, but we ended up with a different problem.
The setup at the moment is:
- Sun Solaris 2.6, native threads, JDK 1.1.7B_008
- two WLS 4.51 SP7 running in cluster using in-memory replication
- only servlets deployed in the servers
- Two WLS proxies between the webcluster and alteon switch. Both proxies are
configured to use both of the web servers. they do not belong to the web
cluster.
The proxies are configured in the following way:
weblogic.httpd.session.enable=true
weblogic.httpd.session.timeoutSecs=1800
weblogic.httpd.session.invalidationIntervalSecs=600
weblogic.httpd.session.URLRewriting.enable=true
weblogic.httpd.session.cookies.enable=true
weblogic.httpd.session.cookie.maxAgeSecs=-1
weblogic.httpd.session.cookie.domain=some.domain.name
weblogic.httpd.register.cluster=weblogic.servlet.internal.HttpClusterServlet
weblogic.httpd.initArgs.cluster=defaultServers=x.y.z.a1:9001|x.y.z.a2:9001
weblogic.httpd.defaultServlet=cluster
weblogic.allow.execute.weblogic.servlet=everyone
Probably most of the configuration parameters are not necessary, can
somebody tell me which are
and which are not?
The servers in the web cluster are configured in the following way:
The following parameters are in the start-up script of the servers:
-Dweblogic.cluster.enable=true \
-Dweblogic.system.name=somehost \
-Dweblogic.cluster.name=someclustercluster \
-Dweblogic.cluster.multicastAddress=237.0.0.1 \
-Dweblogic.system.bindAddr=x.y.z.a1 \
-Dweblogic.system.nativeIO.enable=true \
-Dweblogic.debug.replication=1 \
And the following are in the cluster-wide properties file:
weblogic.httpd.clustering.enable=true
weblogic.httpd.session.persistence=true
weblogic.httpd.session.persistentStoreType=replicated
weblogic.httpd.session.enable=true
weblogic.httpd.session.timeoutSecs=1800
weblogic.httpd.session.invalidationIntervalSecs=600
weblogic.httpd.session.URLRewriting.enable=true
weblogic.httpd.session.cookies.enable=true
weblogic.httpd.session.cookie.domain=some.domain.name
The IP-address of the Alteon box in front of the proxies is bound to
'some.domain.name'.
The first problem seems to be very poor performance. The overall throughtput
is vveeeerrryyy slow, comparing
to the configuration where there is no proxy sitting in front of the
cluster. Furthermore, at some stage the proxy
starts to print out error messages: java.lang.InvalidStateException: broken
pipe [...] . After those exceptions no
client get any response anymore.
Could someone give some hints what are the most essential items in the
weblogic.properties -file for the
proxy server? Also, if someone has some experience from setting up a
configuration similar to ours: one hardware
load-balancer in front of two proxies, and eventually two web servers
running in a web cluster.
Cheers,
Jarno.
-
HTTP Session replication problem
Hi all,
After 3 days trying to make the http session replication work in my cluster is time to ask some help.
I´m trying to make a simple application (only a servlet) simulate a http session replication.
I´ve investigated all the possible problems that i encountered in google :
Here is my multicast tests :
SERVER 1
D:\>java -cp d:\bea\weblogic92\server\lib\weblogic.jar utils.MulticastTest -N SE
RVER1 -A 237.0.0.1 -p 12809
***** WARNING ***** WARNING ***** WARNING *****
Do NOT use the same multicast address as a running WLS cluster.
Starting test. Hit any key to abort
Using multicast address 237.0.0.1:12809
Will send messages under the name SERVER1 every 2 seconds
Will print warning every 600 seconds if no messages are received
I (SERVER1) sent message num 1
I (SERVER1) sent message num 2
Received message 2 from SERVER1
I (SERVER1) sent message num 3
Received message 3 from SERVER1
I (SERVER1) sent message num 4
Received message 4 from SERVER1
I (SERVER1) sent message num 5
Received message 5 from SERVER1
I (SERVER1) sent message num 6
Received message 6 from SERVER1
I (SERVER1) sent message num 7
Received message 7 from SERVER1
I (SERVER1) sent message num 8
Received message 8 from SERVER1
I (SERVER1) sent message num 9
Received message 9 from SERVER1
I (SERVER1) sent message num 10
Received message 10 from SERVER1
Received message 11 from SERVER1
I (SERVER1) sent message num 11
I (SERVER1) sent message num 12
Received message 12 from SERVER1
I (SERVER1) sent message num 13
Received message 13 from SERVER1
Received message 14 from SERVER1
I (SERVER1) sent message num 14
I (SERVER1) sent message num 15
Received message 15 from SERVER1
I (SERVER1) sent message num 16
Received message 16 from SERVER1
SERVER 2
D:\>java -cp d:\bea\weblogic92\server\lib\weblogic.jar utils.MulticastTest -N SE
RVER2 -A 237.0.0.1 -p 12809
***** WARNING ***** WARNING ***** WARNING *****
Do NOT use the same multicast address as a running WLS cluster.
Starting test. Hit any key to abort
Using multicast address 237.0.0.1:12809
Will send messages under the name SERVER2 every 2 seconds
Will print warning every 600 seconds if no messages are received
I (SERVER2) sent message num 1
I (SERVER2) sent message num 2
Received message 2 from SERVER2
I (SERVER2) sent message num 3
Received message 3 from SERVER2
I (SERVER2) sent message num 4
Received message 4 from SERVER2
I (SERVER2) sent message num 5
Received message 5 from SERVER2
I (SERVER2) sent message num 6
Received message 6 from SERVER2
I (SERVER2) sent message num 7
Received message 7 from SERVER2
I (SERVER2) sent message num 8
Received message 8 from SERVER2
I (SERVER2) sent message num 9
Received message 9 from SERVER2
I (SERVER2) sent message num 10
Received message 10 from SERVER2
I (SERVER2) sent message num 11
Received message 11 from SERVER2
I (SERVER2) sent message num 12
Received message 12 from SERVER2
Weblogic.XML descriptor
<session-descriptor>
<session-param>
<param-name>PersistentStoreType</param-name>
<param-value>replicated</param-value>
</session-param>
</session-descriptor>
CODE of the Servlet
HttpSession session = request.getSession();
String sessionIdentif = (String)session.getAttribute("SESSIONIDENTIF");
boolean boolNewSession = true;
if(sessionIdentif == null) {
session.setAttribute("SESSIONIDENTIF", "1234567890");
} else
boolNewSession = false;
As you can see the object that i put in session is a String, so Serializable....
All the requirements are validated (i think...) but it still not working ... i get the SESSION ID : WvHQMKzBh9T35BPhGJxyhQtGks5Q3qJmxnJwGn8mn7V24FM92cnh!949557342! NONE !1284141857480
And the NONE said that the session isn´t replicated.
Any idea what´s wrong with my try of getting http session replication working??
cheers,Hi,
Thanks for your help.
I´ve tried your application with your proxy application but still no work...
I´m getting :
####<13/Set/2010 15H59m BST> <Debug> <Replication> <DST01VS51> <VIACTT2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1284389948055> <000000> <Creating primary 1678977133045201960>
####<13/Set/2010 15H59m BST> <Debug> <ReplicationDetails> <DST01VS51> <VIACTT2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1284389948055> <000000> <Unable to create secondary for 1678977133045201960 on null>
####<13/Set/2010 15H59m BST> <Debug> <ReplicationDetails> <DST01VS51> <VIACTT2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1284389948181> <000000> <Unable to create secondary for 1678977133045201960 on null>
In my early post i forgot to mention that i´m using an Apache 2.2 in the front-end with Weblogic 9.2 (cluster).
What is happening in this weblogic configuration so that this session replication don´t work.
cheers, -
Long Email!
Is there any way to increase the speed of the heartbeat between the primary
and secondary application servers in a cluster?
OS: Solaris 2.6
Weblogic 4.51
Java 1.2.1
IIS Web Server using ISAPI plugin.
Objective:
Replicate session object.
Scenario:
I start 3 weblogic application servers which all join a cluster, they
are not using a shared
filesystem, and its not even an option. They all join successfully and
they recognize each other,
which is good up to this point. I've created 2 test jsp's,
"valueStore.jsp"
places a value in a session using session.putValue('Value', id),
and the other jsp "valueGet.jsp" does a simple
session.getValue('Value').
At this point all of the appservers have joined the cluster and everyone
appears
to be happy. Using a web browser, I type the URL to the proxy server
which
has all the necessary settings in the "iisproxy.ini" so that a request
gets forwarded
on to the cluster. The "valueStore.jsp" gets compiled and everything
looks fine, I run
the "valueGet.jsp" and the value is successfully retrieved, life is
great at this point.
Now I run the "valueStore.jsp", shutdown the appserver which is handling
the request,
and run "valueGet.jsp", an exception occurs on the secondary app server,
"ServletRequestImpl: Exception creating new session"
"java.lang.IllegalStateException:Page needs a session a but is none
available".
I hit refresh a couple of times, same error!
A couple of seconds later I see a message in the secondary appserver
which says
<I> <PosixSocketMux> EOF on socket type t3
<I> <RJVM> Closing connection to 111.222.333.444/111.222.333.444 t3:9051
http:9051 t3s:8052 https:8052 -212134342342
<I> <RepMan>
Removing -212134342342S111.222.333.4444:[9051,9051,8052,8052,-1] from the
cluster
I hit the refresh button and the valueGet.jsp works fine, and the
correct value is getting
retrieved.
My guess at this point is that the proxyserver is aware that one server
is down so
it sends the request to the secondary server. However the secondary
server
does not know the primary server is down so it attempts to replicate the
session
object over, its unsuccessful so it fails. When it finally does realize
the primary server is
down, it works fine. Now, how do I increase the heartbeat between the 2
appservers,
or is that the incorrect way of proceeding? Also, considering that I
will not be able
to use a shared filesystem, would I run into any problems?
weblogic.properties file in the mycluster directory.
weblogic.httpd.clustering.enable=true
weblogic.httpd.session.persistence=true
weblogic.httpd.session.persistentStoreType=replicated
weblogic.debug.replication=2
Currently it is not a tunable property. Could you send the log files with time
stamps around that time period when you brought down a server.
Which version of service pack are you using. Typically it doesn't matter if you
use shared file system or not. But I would like to take a look at the log files
first.
Thanks
- Prasad
G wrote:
> Long Email!
>
> Is there any way to increase the speed of the heartbeat between the primary
> and secondary application servers in a cluster?
>
> OS: Solaris 2.6
> Weblogic 4.51
> Java 1.2.1
> IIS Web Server using ISAPI plugin.
>
> Objective:
> Replicate session object.
>
> Scenario:
> I start 3 weblogic application servers which all join a cluster, they
> are not using a shared
> filesystem, and its not even an option. They all join successfully and
> they recognize each other,
> which is good up to this point. I've created 2 test jsp's,
> "valueStore.jsp"
> places a value in a session using session.putValue('Value', id),
> and the other jsp "valueGet.jsp" does a simple
> session.getValue('Value').
> At this point all of the appservers have joined the cluster and everyone
> appears
> to be happy. Using a web browser, I type the URL to the proxy server
> which
> has all the necessary settings in the "iisproxy.ini" so that a request
> gets forwarded
> on to the cluster. The "valueStore.jsp" gets compiled and everything
> looks fine, I run
> the "valueGet.jsp" and the value is successfully retrieved, life is
> great at this point.
> Now I run the "valueStore.jsp", shutdown the appserver which is handling
> the request,
> and run "valueGet.jsp", an exception occurs on the secondary app server,
> "ServletRequestImpl: Exception creating new session"
> "java.lang.IllegalStateException:Page needs a session a but is none
> available".
> I hit refresh a couple of times, same error!
> A couple of seconds later I see a message in the secondary appserver
> which says
> <I> <PosixSocketMux> EOF on socket type t3
> <I> <RJVM> Closing connection to 111.222.333.444/111.222.333.444 t3:9051
> http:9051 t3s:8052 https:8052 -212134342342
> <I> <RepMan>
> Removing -212134342342S111.222.333.4444:[9051,9051,8052,8052,-1] from the
> cluster
> I hit the refresh button and the valueGet.jsp works fine, and the
> correct value is getting
> retrieved.
>
> My guess at this point is that the proxyserver is aware that one server
> is down so
> it sends the request to the secondary server. However the secondary
> server
> does not know the primary server is down so it attempts to replicate the
> session
> object over, its unsuccessful so it fails. When it finally does realize
> the primary server is
> down, it works fine. Now, how do I increase the heartbeat between the 2
> appservers,
> or is that the incorrect way of proceeding? Also, considering that I
> will not be able
> to use a shared filesystem, would I run into any problems?
>
> weblogic.properties file in the mycluster directory.
> weblogic.httpd.clustering.enable=true
> weblogic.httpd.session.persistence=true
> weblogic.httpd.session.persistentStoreType=replicated
>
> weblogic.debug.replication=2
-
Hi,
I have a configuration where a single Apache running the WLS-plugin
fronts two WLS instances executing on the same, multihomed Solaris
machine. The cluster specific weblogic.properties file contains the
following:
weblogic.httpd.clustering.enable=true
weblogic.httpd.session.persistence=true
weblogic.httpd.session.persistentStoreType=replicated
Static pages and servlets not depending on HTTP session state work fine
but when I try to run the example session servlet
(examples.servlets.SessionServlet) the web browser never gets any
response. I can't find anything suspicous in the log files.
Does anybody have any idea of what could be wrong? Is there a simple way
to verify that the clustering config, the multicast address etc is okay?
Thank you
Patrik
Yep, that definately made a difference. It works now - thanks!
Cheers
Patrik
Wei Guan skrev:
> What is your SP? Could you try SP4?
>
> --
> Cheers - Wei
>
> Patrik Gottfridsson <[email protected]> wrote in message
> news:[email protected]...
> >
> > The weblogic.httpd.clustering.enable is set on the command line in the
> startup
> > script. Also, I ran the multicastTest utility after shutting down the
> > application server. So neither of these should cause any problems. The
> strange
> > thing is that everything looks normal. I get some nice messages in the
> > weblogic.log saying that both WLS instances join the cluster and so on.
> >
> > To debug I tried set this property in the cluster-wide config file:
> >
> > weblogic.debug.replication=2
> >
> > and this resulted in the following message in the weblogic.log of the
> primary
> > WLS:
> >
> > Thu Aug 17 16:36:35 GMT+02:00 2000:<I> <RepMan> Trying to create secondary
> for
> > 5449997915261938767 on new host
> > 5557948761125425783S192.168.1.235:[7001,7001,7002,7002,7001,-1]
> >
> > and then nothing more (browser hung). Should the trace contain something
> more,
> > e.g. "Secondary created ok .."? I guess this would imply that the
> replication
> > fails in some way.
> >
> > Cheers
> >
> > Patrik
> >
> >
> >
> > Wei Guan skrev:
> >
> > > weblogic.httpd.clustering.enable=true must be set in startup script.
> > >
> > > --
> > > Cheers - Wei
> > >
> > > Vincent Wong <[email protected]> wrote in message
> > > news:[email protected]...
> > > >
> > > > Hi,
> > > >
> > > > I have a configuration where a single Apache running the WLS-plugin
> > > > fronts two WLS instances executing on the same, multihomed Solaris
> > > > machine. The cluster specific weblogic.properties file contains the
> > > > following:
> > > >
> > > > weblogic.httpd.clustering.enable=true
> > > > weblogic.httpd.session.persistence=true
> > > > weblogic.httpd.session.persistentStoreType=replicated
> > > >
> > > > Static pages and servlets not depending on HTTP session state work
> fine
> > > > but when I try to run the example session servlet
> > > > (examples.servlets.SessionServlet) the web browser never gets any
> > > > response. I can't find anything suspicous in the log files.
> > > >
> > > > Does anybody have any idea of what could be wrong? Is there a simple
> way
> > > > to verify that the clustering config, the multicast address etc is
> okay?
> > > >
> > > > Thank you
> > > >
> > > > Patrik
> > > >
> >
-
Automatic assignment products in catalog, looking for badi or userexit.
From ecc I get a new/adjusted product in CRM,
Somehow this product gets automaticaly into the catalog.
I want to create a filter that does some validation check on products and if it is ok they may enter in catalog otherwise they may not.
I was hoping to find badi's for it but i didn't.
I tried to change a product in ecc-> then debug in bdoc-> but my breakpoint in the normal * prodca t* badi's dont get triggerd.
Anyone that can help me on this subject?
Regards
Edited by: bjorn corluy on Apr 1, 2010 3:23 PM
Edited by: bjorn corluy on Apr 1, 2010 3:24 PM
Edited by: bjorn corluy on Apr 1, 2010 3:25 PMI found it myself:
In your catalog in crm backend, go to a catalog area that is automaticaly filled..
open header tab.-> basic data.
Now you can see : Product Cat. with some value
this value you can find in the product masterdata :
check the category ID : that value should be the same as the Product Cat value in the catlog .
now every time you open your catalog and click your automated catalog area .. it will check all product with this category ID and fills up the catalog area. (could take some realy long time if you have much products)
Also with replication it does this reading step It seems.. when i was debugging replication process.
Regards.
Bjorn -
CUCM 9.1.1.2 - NTP unsynchronised
Hello,
I have a problem with the ntp service. The publisher is unsynchronised.
However, the ntp server is reachable by the publisher.
I tried to restart the ntp service but nothing change.
Do I need to restart the server?
Thanks
FredericHello Manish,
the CUCM version is : 9.1.1.20000-5. there are 4 servers. The NTP server is the core switch with a stratum at 1.
Here the result of utils dbreplication status :
Mon Jan 26 17:43:22 2015 main() DEBUG: Replication cluster summary:
SERVER ID STATE STATUS QUEUE CONNECTION CHANGED
D_sub_ccm9_1_1_20000_5 6 Active Connected 0 Jan 6 19:26:14
A_ccm9_1_1_20000_5 2 Active Local 0
B_sub_ccm9_1_1_20000_5 7 Active Connected 0 Jan 6 19:26:14
C_sub_ccm9_1_1_20000_5 5 Active Connected 1060 Jan 6 19:26:37
For NTP service, what file do you need? ntpd?
I checked the logs before to restart the service and the NTP service had already been restarted by itself. -
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,
OliverI 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. -
I've had 2 DFSR servers replicating for about 12 months now with no issue, with in the last week one server has stopped replicating some files, ie will have a directory with 30 jpg files on server a, server b will only receive 15 of the files.
in the DFSR log i just see this log repeated over and over again for all the different files it wont replicate
20140705 18:03:16.674 4072 SRTR 2344 [WARN] InitializeFileTransferAsyncState::ProcessIoCompletion Failed connId:{20AEF2C3-92EC-41B2-A161-D26B164F2A73} rdc:1 uid:{75E65307-2678-4C2B-B808-0C321E8D4383}-v7123
gsvn:{75E65307-2678-4C2B-B808-0C321E8D4383}-v7127 Error:[Error:170(0xaa) InitializeFileTransferAsyncState::ProcessIoCompletion servertransport.cpp:2235 4072 W The requested resource is in use.] completion:0 ptr:000000000D411160
i've tried everything i can think from disabling the AV to completely deleting this folder from the namespace, copying all the files to a new hard disk and starting again with a new folder in the namespace,
but i still receive the same error.
All other folders replicating from this server are still working and replicating correctlyHi,
Please create a Diagnostic Report for DFS Replication to see if there is any error message.
http://technet.microsoft.com/en-us/library/cc754227.aspx
Install latest DFSR hot fixes and adjust the DFSR tuning settings to improve the replication performance and improve the network connection condition to check the result.
Regards,
Mandy
If you have any feedback on our support, please click
here .
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
BSOD on Server 2012 running dfs namespace and dfs replication roles with deduplication
Hello,
I have recently setup 2 dfsn & dfsr servers, both 2012 one physical the other virtual.
The idea is to have one server as primary and the other as a failover \ DR.
The primary server is virtual and connects via mpio \ iscsi to a dell san, using the provided dell DSM Drivers.
The secondary server is physical with local disk for storage.
I copy files to a namespace setup to always prefer the primary server, these files are then replicated across to the secondary.
I have also turned on deduplication on both servers to get the most out of the available storage.
This has been working well for 6 months or so, there have however been 2-3 occasions where the primary virtual server has crashed and blue screened causing the DFSR database to undergo a full consistency check.
The bug check errors i have managed to extract from the Memory.dmp and mini dump are as follows:
* Bugcheck Analysis
REFERENCE_BY_POINTER (18)
Arguments:
Arg1: 0000000000000000, Object type of the object whose reference count is being lowered
Arg2: fffffa80379a3070, Object whose reference count is being lowered
Arg3: 0000000000000002, Reserved
Arg4: ffffffffffffffff, Reserved
The reference count of an object is illegal for the current state of the object.
Each time a driver uses a pointer to an object the driver calls a kernel routine
to increment the reference count of the object. When the driver is done with the
pointer the driver calls another kernel routine to decrement the reference count.
Drivers must match calls to the increment and decrement routines. This bugcheck
can occur because an object's reference count goes to zero while there are still
open handles to the object, in which case the fourth parameter indicates the number
of opened handles. It may also occur when the object?s reference count drops below zero
whether or not there are open handles to the object, and in that case the fourth parameter
contains the actual value of the pointer references count.
Debugging Details:
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x18
PROCESS_NAME: dfsrs.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff800999ee0d7 to fffff8009985a440
STACK_TEXT:
fffff880`0bf3fb48 fffff800`999ee0d7 : 00000000`00000018 00000000`00000000 fffffa80`379a3070 00000000`00000002 : nt!KeBugCheckEx
fffff880`0bf3fb50 fffff800`99c33529 : fffffa80`379a3070 fffff8a0`0244adc0 00000000`000017e4 0000001b`930b60d8 : nt! ?? ::FNODOBFM::`string'+0x38605
fffff880`0bf3fb90 fffff800`99859453 : fffffa80`4063db00 fffffa80`4063db00 fffff880`0bf3fcc0 00000000`00000001 : nt!NtClose+0x239
fffff880`0bf3fc40 000007ff`5e8d2cda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000001b`9069f398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007ff`5e8d2cda
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+38605
fffff800`999ee0d7 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+38605
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 51a966cd
IMAGE_VERSION: 6.2.9200.16628
BUCKET_ID_FUNC_OFFSET: 38605
FAILURE_BUCKET_ID: 0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x18_over_dereference_nt!_??_::fnodobfm::_string_
FAILURE_ID_HASH: {eaf19261-0688-f327-a17d-6f7960ac4ebd}
Followup: MachineOwner
rax=0000000000000000 rbx=ffffffffffffffff rcx=0000000000000018
rdx=0000000000000000 rsi=fffffa80379a3070 rdi=00000000fffc000c
rip=fffff8009985a440 rsp=fffff8800bf3fb48 rbp=fffffa80379a3040
r8=fffffa80379a3070 r9=0000000000000002 r10=fffffa8030d89190
r11=fffffa804063db00 r12=00000000000017e4 r13=0000000000000000
r14=fffff8a00a548f90 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000246
nt!KeBugCheckEx:
fffff800`9985a440 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`0bf3fb50=0000000000000018
Child-SP RetAddr : Args to Child
: Call Site
fffff880`0bf3fb48 fffff800`999ee0d7 : 00000000`00000018 00000000`00000000 fffffa80`379a3070 00000000`00000002 : nt!KeBugCheckEx
fffff880`0bf3fb50 fffff800`99c33529 : fffffa80`379a3070 fffff8a0`0244adc0 00000000`000017e4 0000001b`930b60d8 : nt! ?? ::FNODOBFM::`string'+0x38605
fffff880`0bf3fb90 fffff800`99859453 : fffffa80`4063db00 fffffa80`4063db00 fffff880`0bf3fcc0 00000000`00000001 : nt!NtClose+0x239
fffff880`0bf3fc40 000007ff`5e8d2cda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0bf3fc40)
0000001b`9069f398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007ff`5e8d2cda
start end module name
fffff800`987b1000 fffff800`987ba000 kd kd.dll Thu Jul 26 03:30:34 2012 (5010ABCA)
fffff800`99800000 fffff800`99f4c000 nt ntkrnlmp.exe Sat Jun 01 04:13:17 2013 (51A966CD)
fffff800`99f4c000 fffff800`99fb8000 hal hal.dll Wed Oct 24 04:03:21 2012 (50875A79)
fffff880`00a00000 fffff880`00a34000 ataport ataport.SYS Thu Jul 26 03:29:04 2012 (5010AB70)
fffff880`00a34000 fffff880`00a51000 lsi_sas lsi_sas.sys Fri May 11 20:40:21 2012 (4FAD6B25)
fffff880`00a51000 fffff880`00a5e000 serenum serenum.sys Thu Jul 26 03:30:13 2012 (5010ABB5)
fffff880`00a5e000 fffff880`00a6c000 fdc fdc.sys Thu Jul 26 03:30:15 2012 (5010ABB7)
fffff880`00a7b000 fffff880`00adb000 volmgrx volmgrx.sys Thu Jul 26 03:29:59 2012 (5010ABA7)
fffff880`00adb000 fffff880`00ae4000 intelide intelide.sys Thu Jul 26 03:29:52 2012 (5010ABA0)
fffff880`00ae4000 fffff880`00af3000 PCIIDEX PCIIDEX.SYS Thu Jul 26 03:29:09 2012 (5010AB75)
fffff880`00af3000 fffff880`00b56000 md3dsm md3dsm.sys Wed Aug 22 22:14:46 2012 (50354BC6)
fffff880`00b56000 fffff880`00b87000 msdsm msdsm.sys Sat Oct 05 04:32:09 2013 (524F8839)
fffff880`00b87000 fffff880`00ba0000 vmci vmci.sys Tue May 01 02:14:27 2012 (4F9F38F3)
fffff880`00ba0000 fffff880`00bb5000 vsock vsock.sys Fri Aug 30 20:25:34 2013 (5220F1AE)
fffff880`00bb5000 fffff880`00bcf000 mountmgr mountmgr.sys Thu Jul 26 03:29:33 2012 (5010AB8D)
fffff880`00bcf000 fffff880`00bd9000 atapi atapi.sys Thu Jul 26 03:30:33 2012 (5010ABC9)
fffff880`00bd9000 fffff880`00bf0000 vmxnet3n61x64 vmxnet3n61x64.sys Fri Sep 27 10:40:11 2013 (5245527B)
fffff880`00bf0000 fffff880`00bfa000 pnpmem pnpmem.sys Thu Jul 26 03:30:11 2012 (5010ABB3)
fffff880`00c40000 fffff880`00c9f000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Thu Jul 26 03:30:12 2012 (5010ABB4)
fffff880`00c9f000 fffff880`00cfb000 CLFS CLFS.SYS Thu Jul 26 03:29:39 2012 (5010AB93)
fffff880`00cfb000 fffff880`00d1e000 tm tm.sys Thu Jul 26 03:29:01 2012 (5010AB6D)
fffff880`00d1e000 fffff880`00d33000 PSHED PSHED.dll Thu Jul 26 05:53:53 2012 (5010CD61)
fffff880`00d33000 fffff880`00d3d000 BOOTVID BOOTVID.dll Thu Jul 26 03:30:22 2012 (5010ABBE)
fffff880`00d3d000 fffff880`00dbc000 CI CI.dll Thu Mar 28 03:30:42 2013 (5153B962)
fffff880`00dbc000 fffff880`00de1000 rasl2tp rasl2tp.sys Thu Jul 26 03:23:16 2012 (5010AA14)
fffff880`00e00000 fffff880`00e49000 spaceport spaceport.sys Sat Oct 05 04:32:08 2013 (524F8838)
fffff880`00e49000 fffff880`00e61000 volmgr volmgr.sys Thu Jul 26 03:29:22 2012 (5010AB82)
fffff880`00e61000 fffff880`00ea9000 vm3dmp vm3dmp.sys Wed Oct 09 05:25:53 2013 (5254DAD1)
fffff880`00eb5000 fffff880`00f41000 cng cng.sys Thu Oct 11 06:17:34 2012 (5076566E)
fffff880`00f41000 fffff880`00f5b000 raspppoe raspppoe.sys Thu Jul 26 03:24:55 2012 (5010AA77)
fffff880`00f5c000 fffff880`00f99000 mpio mpio.sys Sat Sep 28 04:37:24 2013 (52464EF4)
fffff880`00f99000 fffff880`00fd3000 md3utm md3utm.sys Wed Aug 22 22:14:56 2012 (50354BD0)
fffff880`00fd3000 fffff880`00fef000 intelppm intelppm.sys Tue Nov 06 03:55:02 2012 (50988A16)
fffff880`01000000 fffff880`0106d000 ACPI ACPI.sys Thu Sep 20 07:09:16 2012 (505AB30C)
fffff880`01075000 fffff880`010d8000 msrpc msrpc.sys Thu Jul 26 03:28:37 2012 (5010AB55)
fffff880`010d8000 fffff880`0119a000 Wdf01000 Wdf01000.sys Sat Jun 22 04:13:05 2013 (51C51641)
fffff880`0119a000 fffff880`011aa000 WDFLDR WDFLDR.SYS Sat Jun 22 04:14:38 2013 (51C5169E)
fffff880`011aa000 fffff880`011c1000 acpiex acpiex.sys Thu Jul 26 03:25:57 2012 (5010AAB5)
fffff880`011c1000 fffff880`011cc000 WppRecorder WppRecorder.sys Thu Jul 26 03:29:07 2012 (5010AB73)
fffff880`011cc000 fffff880`011d6000 WMILIB WMILIB.SYS Thu Jul 26 03:30:04 2012 (5010ABAC)
fffff880`011d6000 fffff880`011f7000 raspptp raspptp.sys Thu Jul 26 03:23:13 2012 (5010AA11)
fffff880`01400000 fffff880`0140d000 vdrvroot vdrvroot.sys Thu Jul 26 03:27:29 2012 (5010AB11)
fffff880`0140d000 fffff880`01424000 pdc pdc.sys Fri Mar 01 04:58:34 2013 (5130357A)
fffff880`01424000 fffff880`0143e000 partmgr partmgr.sys Wed Jan 09 04:01:42 2013 (50ECEBA6)
fffff880`01444000 fffff880`0153f000 NDIS NDIS.SYS Sat Jun 15 06:11:35 2013 (51BBF787)
fffff880`0153f000 fffff880`015ae000 NETIO NETIO.SYS Thu Oct 11 06:16:20 2012 (50765624)
fffff880`015ae000 fffff880`015b8000 msisadrv msisadrv.sys Thu Jul 26 03:28:02 2012 (5010AB32)
fffff880`015b8000 fffff880`015f5000 pci pci.sys Thu Jul 26 03:27:43 2012 (5010AB1F)
fffff880`01800000 fffff880`01816000 datascrn datascrn.sys Thu Jul 26 03:29:13 2012 (5010AB79)
fffff880`01816000 fffff880`01824000 cbafilt cbafilt.sys Thu Jul 26 03:29:05 2012 (5010AB71)
fffff880`01824000 fffff880`0186c000 msiscsi msiscsi.sys Mon Feb 03 16:23:09 2014 (52EFC26D)
fffff880`0186c000 fffff880`01877000 kdnic kdnic.sys Thu Jul 26 03:27:41 2012 (5010AB1D)
fffff880`01877000 fffff880`01889000 umbus umbus.sys Thu Jul 26 03:27:39 2012 (5010AB1B)
fffff880`01889000 fffff880`018a9000 i8042prt i8042prt.sys Thu Jul 26 03:28:50 2012 (5010AB62)
fffff880`018a9000 fffff880`018b8000 kbdclass kbdclass.sys Thu Jul 26 03:28:47 2012 (5010AB5F)
fffff880`018b8000 fffff880`018c7000 mouclass mouclass.sys Thu Jul 26 03:28:47 2012 (5010AB5F)
fffff880`018c7000 fffff880`018e5000 parport parport.sys Thu Jul 26 03:29:53 2012 (5010ABA1)
fffff880`018e5000 fffff880`018fd000 serial serial.sys Thu Jul 26 03:30:01 2012 (5010ABA9)
fffff880`018fd000 fffff880`01952000 storport storport.sys Mon Feb 03 16:23:24 2014 (52EFC27C)
fffff880`01952000 fffff880`019b2000 fltmgr fltmgr.sys Thu Jul 26 03:30:09 2012 (5010ABB1)
fffff880`019b2000 fffff880`019e0000 quota quota.sys Thu Jul 26 03:29:14 2012 (5010AB7A)
fffff880`019e0000 fffff880`019f4000 dfsrro dfsrro.sys Thu Jul 26 03:29:13 2012 (5010AB79)
fffff880`019f4000 fffff880`01a00000 BATTC BATTC.SYS Thu Oct 11 06:19:58 2012 (507656FE)
fffff880`01a00000 fffff880`01a2c000 tunnel tunnel.sys Thu Jul 26 03:23:04 2012 (5010AA08)
fffff880`01a2c000 fffff880`01a3b000 CompositeBus CompositeBus.sys Thu Jul 26 03:28:03 2012 (5010AB33)
fffff880`01a3b000 fffff880`01a45000 vmgencounter vmgencounter.sys Thu Jul 26 03:27:58 2012 (5010AB2E)
fffff880`01a45000 fffff880`01c2a000 Ntfs Ntfs.sys Sun Jan 26 23:28:35 2014 (52E59A23)
fffff880`01c2a000 fffff880`01c45000 ksecdd ksecdd.sys Thu Sep 20 07:09:16 2012 (505AB30C)
fffff880`01c45000 fffff880`01c56000 pcw pcw.sys Thu Jul 26 03:28:44 2012 (5010AB5C)
fffff880`01c56000 fffff880`01c60000 Fs_Rec Fs_Rec.sys Thu Jul 26 03:30:08 2012 (5010ABB0)
fffff880`01c60000 fffff880`01c8f000 ksecpkg ksecpkg.sys Thu Oct 11 06:16:46 2012 (5076563E)
fffff880`01c8f000 fffff880`01cc0000 cdrom cdrom.sys Thu Jul 26 03:26:36 2012 (5010AADC)
fffff880`01cc0000 fffff880`01d2b000 dedup dedup.sys Sat Oct 05 04:31:38 2013 (524F881A)
fffff880`01d2b000 fffff880`01d3a000 vmrawdsk vmrawdsk.sys Sun Dec 15 03:36:38 2013 (52AD23C6)
fffff880`01d3a000 fffff880`01d47000 BasicRender BasicRender.sys Thu Jul 26 03:28:51 2012 (5010AB63)
fffff880`01d47000 fffff880`01d53000 mssmbios mssmbios.sys Thu Jul 26 03:29:19 2012 (5010AB7F)
fffff880`01d53000 fffff880`01d64000 discache discache.sys Thu Jul 26 03:28:23 2012 (5010AB47)
fffff880`01d64000 fffff880`01d85000 dfsc dfsc.sys Wed Jan 15 23:42:58 2014 (52D71D02)
fffff880`01d85000 fffff880`01d91000 ndistapi ndistapi.sys Thu Sep 20 07:09:19 2012 (505AB30F)
fffff880`01d91000 fffff880`01dc0000 ndiswan ndiswan.sys Thu Jul 26 03:23:13 2012 (5010AA11)
fffff880`01dc0000 fffff880`01dde000 rassstp rassstp.sys Thu Jul 26 03:23:59 2012 (5010AA3F)
fffff880`01dde000 fffff880`01df6000 AgileVpn AgileVpn.sys Thu Jul 26 03:23:11 2012 (5010AA0F)
fffff880`01df6000 fffff880`01dfc400 CmBatt CmBatt.sys Thu Jul 26 03:29:20 2012 (5010AB80)
fffff880`01e00000 fffff880`01e54000 CLASSPNP CLASSPNP.SYS Sat Jun 29 04:07:45 2013 (51CE4F81)
fffff880`01e54000 fffff880`01e68000 crashdmp crashdmp.sys Fri Aug 30 04:11:28 2013 (52200D60)
fffff880`01e75000 fffff880`01e7e000 Null Null.SYS Thu Jul 26 03:30:16 2012 (5010ABB8)
fffff880`01e81000 fffff880`020ba000 tcpip tcpip.sys Wed Jan 22 04:28:22 2014 (52DF48E6)
fffff880`020ba000 fffff880`02122000 fwpkclnt fwpkclnt.sys Fri Mar 01 04:55:54 2013 (513034DA)
fffff880`02122000 fffff880`0213d000 wfplwfs wfplwfs.sys Thu Oct 10 04:32:19 2013 (52561FC3)
fffff880`0213d000 fffff880`02191000 volsnap volsnap.sys Sat Jun 01 04:10:22 2013 (51A9661E)
fffff880`02191000 fffff880`021a8000 mup mup.sys Thu Jul 26 03:30:00 2012 (5010ABA8)
fffff880`021a8000 fffff880`021b4000 npsvctrig npsvctrig.sys Thu Jul 26 03:27:33 2012 (5010AB15)
fffff880`021b4000 fffff880`021d0000 disk disk.sys Sat Oct 12 07:31:15 2013 (5258ECB3)
fffff880`021ed000 fffff880`021ff000 dfs dfs.sys Thu Jul 26 03:28:21 2012 (5010AB45)
fffff880`03800000 fffff880`03863000 mrxsmb mrxsmb.sys Tue Feb 05 22:29:08 2013 (511187B4)
fffff880`0389c000 fffff880`038eb000 ks ks.sys Sat Feb 02 07:25:50 2013 (510CBF7E)
fffff880`038eb000 fffff880`038f6000 rdpbus rdpbus.sys Thu Jul 26 03:28:19 2012 (5010AB43)
fffff880`038f6000 fffff880`0390a000 NDProxy NDProxy.SYS Tue Apr 09 03:33:41 2013 (51637E05)
fffff880`0390a000 fffff880`03915000 flpydisk flpydisk.sys Thu Jul 26 03:30:15 2012 (5010ABB7)
fffff880`03915000 fffff880`03922000 dump_diskdump dump_diskdump.sys Thu Jul 26 03:29:58 2012 (5010ABA6)
fffff880`03922000 fffff880`0393f000 dump_LSI_SAS dump_LSI_SAS.sys Fri May 11 20:40:21 2012 (4FAD6B25)
fffff880`0393f000 fffff880`03947000 HIDPARSE HIDPARSE.SYS Sat Jun 29 04:08:18 2013 (51CE4FA2)
fffff880`03947000 fffff880`03955000 monitor monitor.sys Fri Mar 01 04:56:18 2013 (513034F2)
fffff880`03955000 fffff880`0397d000 luafv luafv.sys Thu Jul 26 03:29:13 2012 (5010AB79)
fffff880`0397d000 fffff880`03991000 lltdio lltdio.sys Thu Jul 26 03:24:02 2012 (5010AA42)
fffff880`03991000 fffff880`039a9000 rspndr rspndr.sys Thu Jul 26 03:24:06 2012 (5010AA46)
fffff880`039a9000 fffff880`039c9000 bowser bowser.sys Thu Jul 26 03:28:01 2012 (5010AB31)
fffff880`039c9000 fffff880`039e0000 mpsdrv mpsdrv.sys Thu Oct 31 03:42:19 2013 (5271D19B)
fffff880`03c00000 fffff880`03c73000 rdbss rdbss.sys Sat May 04 05:47:00 2013 (518492C4)
fffff880`03c73000 fffff880`03c8d000 wanarp wanarp.sys Tue Apr 09 03:31:00 2013 (51637D64)
fffff880`03c8d000 fffff880`03c9b000 nsiproxy nsiproxy.sys Thu Jul 26 03:25:00 2012 (5010AA7C)
fffff880`03c9b000 fffff880`03ca3000 vmmouse vmmouse.sys Mon Jun 04 10:34:25 2012 (4FCC8121)
fffff880`03ca3000 fffff880`03e0c000 dxgkrnl dxgkrnl.sys Thu Sep 19 04:16:23 2013 (523A6C87)
fffff880`03e0c000 fffff880`03e1d000 watchdog watchdog.sys Thu Jul 26 03:29:05 2012 (5010AB71)
fffff880`03e1d000 fffff880`03e6b000 dxgmms1 dxgmms1.sys Wed Jan 09 03:58:58 2013 (50ECEB02)
fffff880`03e6b000 fffff880`03e7c000 BasicDisplay BasicDisplay.sys Thu Jul 26 03:29:08 2012 (5010AB74)
fffff880`03e7c000 fffff880`03e8e000 Npfs Npfs.SYS Thu Jul 26 03:30:26 2012 (5010ABC2)
fffff880`03e8e000 fffff880`03e9a000 Msfs Msfs.SYS Thu Jul 26 03:30:24 2012 (5010ABC0)
fffff880`03e9a000 fffff880`03ebc000 tdx tdx.sys Thu Jul 26 03:24:58 2012 (5010AA7A)
fffff880`03ebc000 fffff880`03eca000 TDI TDI.SYS Thu Jul 26 03:27:59 2012 (5010AB2F)
fffff880`03eca000 fffff880`03ed6000 ws2ifsl ws2ifsl.sys Thu Sep 20 07:09:50 2012 (505AB32E)
fffff880`03ed6000 fffff880`03f2e000 netbt netbt.sys Thu Jul 26 03:24:26 2012 (5010AA5A)
fffff880`03f2e000 fffff880`03fc4000 afd afd.sys Wed Sep 04 04:11:20 2013 (5226A4D8)
fffff880`03fc4000 fffff880`03fee000 pacer pacer.sys Thu Jul 26 03:23:05 2012 (5010AA09)
fffff880`03fee000 fffff880`03ffe000 netbios netbios.sys Thu Jul 26 03:28:19 2012 (5010AB43)
fffff880`03ffe000 fffff880`03fff480 swenum swenum.sys Thu Jul 26 03:28:53 2012 (5010AB65)
fffff880`0ac00000 fffff880`0acdf000 HTTP HTTP.sys Fri Mar 15 00:17:15 2013 (5142688B)
fffff880`0acdf000 fffff880`0ace7000 vmmemctl vmmemctl.sys Sun Dec 15 03:36:24 2013 (52AD23B8)
fffff880`0acf8000 fffff880`0ad43000 mrxsmb10 mrxsmb10.sys Thu Jul 26 03:23:06 2012 (5010AA0A)
fffff880`0ad43000 fffff880`0ad7e000 mrxsmb20 mrxsmb20.sys Tue Feb 05 22:28:36 2013 (51118794)
fffff880`0b200000 fffff880`0b20d000 condrv condrv.sys Thu Jul 26 03:30:08 2012 (5010ABB0)
fffff880`0b20d000 fffff880`0b2ae000 srv2 srv2.sys Tue Apr 09 03:33:02 2013 (51637DDE)
fffff880`0b2cd000 fffff880`0b399000 peauth peauth.sys Tue Apr 09 03:32:01 2013 (51637DA1)
fffff880`0b399000 fffff880`0b3a4000 secdrv secdrv.SYS Wed Sep 13 14:18:38 2006 (4508052E)
fffff880`0b3a4000 fffff880`0b3e8000 srvnet srvnet.sys Tue Apr 09 03:31:13 2013 (51637D71)
fffff880`0b3e8000 fffff880`0b3fa000 tcpipreg tcpipreg.sys Thu Jul 26 03:23:13 2012 (5010AA11)
fffff880`0b4e3000 fffff880`0b570000 srv srv.sys Thu Jul 26 03:25:28 2012 (5010AA98)
fffff880`0b570000 fffff880`0b57b000 rdpvideominiport rdpvideominiport.sys Fri Oct 12 06:48:28 2012 (5077AF2C)
fffff880`0b57b000 fffff880`0b5ac000 rdpdr rdpdr.sys Thu Jul 26 03:25:18 2012 (5010AA8E)
fffff880`0b5ac000 fffff880`0b5b9000 terminpt terminpt.sys Thu Jul 26 03:28:53 2012 (5010AB65)
fffff960`00118000 fffff960`00508000 win32k win32k.sys Sat Feb 08 04:34:05 2014 (52F5B3BD)
fffff960`006cb000 fffff960`006d4000 TSDDD TSDDD.dll Thu Jul 26 03:30:25 2012 (5010ABC1)
fffff960`00879000 fffff960`008af000 cdd cdd.dll Thu Jul 26 05:49:37 2012 (5010CC61)
fffff960`00a21000 fffff960`00a60000 RDPUDD RDPUDD.dll Fri Oct 12 06:50:01 2012 (5077AF89)
Unloaded modules:
fffff880`01e68000 fffff880`01e75000 dump_storport.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000D000
fffff880`021d0000 fffff880`021ed000 dump_LSI_SAS.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0001D000
fffff880`021a8000 fffff880`021b4000 hwpolicy.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000C000
fffff880`00f41000 fffff880`00f5c000 sacdrv.sys
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0001B000
fffff880`00c33000 fffff880`00c40000 ApiSetSchema.dll
Timestamp: unavailable (00000000)
Checksum: 00000000
ImageSize: 0000D000
I have searched for others having a similar problem but have not managed to find much.
The memory dump at the time of the crash does seem to hint at a problem with DFSR.exe.
The setup seems to be running fine again now and is going through its consistency checks, it is just a major inconvenience and will only get worse as the DFS becomes busier and approaches capacity.
The plan was to put this setup into production however with the unpredictability of blue screen reboots I cannot see this happening until I can find a fix or work around.
I have yet to see this problem occur on the other (physical) server, this is pretty much identical in configuration apart from its storage access.
My thoughts are a possible bug in the DFSR component or a bug in the DSM Drivers used for the iSCSI SAN connection or maybe a combination of the two.
Any help, thoughts or suggestions greatly appreciated
ThanksHi,
Please install the current version of Dfssvc.exe Dfsc.sys Dfsrs.exe for Windows Server 2012.
List of currently available hotfixes for Distributed File System (DFS) technologies in Windows Server 2012 and Windows Server 2012 R2
http://support.microsoft.com/kb/2951262
The issue may be due to the DFSRoot folder has lost NTFS permission. Some reasons why DFS root lose ACLs Links are listed in the article below:
How to implement Windows Server 2003 Access-based Enumeration in a DFS environment
http://support.microsoft.com/kb/907458/en-us
You could use dfsutil to set NTFS permission: dfsutil property ACL \\DFS-namespace
Using the Windows Server 2008 DFSUTIL.EXE command line to manage DFS-Namespaces
http://blogs.technet.com/b/josebda/archive/2009/05/01/using-the-windows-server-2008-dfsutil-exe-command-line-to-manage-dfs-namespaces.aspx
To narrow down the issue, you could remove the DFS role to check if the issue related to the dfs namespace and dfs replication roles.
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
BP replication from CRM to R3 Error
Hi All,
We are working on CRM 4.0 Unicode version. The details of the system are as follows
SAP_BASIS 620 0056 SAPKB62056
SAP_ABA 620 0056 SAPKA62056
BBPCRM 400 0009 SAPKU40009
PI_BASIS 2005_1_620 0005 SAPKIPYJ55
We are working with R/3 4.7 Non Unicode version the details of which are as follows
SAP_BASIS 620 0056 SAPKB62056
SAP_ABA 620 0056 SAPKA62056
SAP_APPL 470 0021 SAPKH47021
SAP_HR 470 0030 SAPKE47030
ABA_PLUS 100 0009 SAPKGPBA09
EA-IPPE 200 0013 SAPKGPIB13
PI 2004_1_470 0001 SAPKIPZI51
PI_BASIS 2005_1_620 0005 SAPKIPYJ55
EA-APPL 200 0007 SAPKGPAB07
EA-DFPS 200 0007 SAPKGPDB07
EA-FINSERV 200 0007 SAPKGPFB07
EA-GLTRADE 200 0007 SAPKGPGB07
EA-HR 200 0011 SAPKGPHB11
EA-PS 200 0007 SAPKGPPB07
EA-RETAIL 200 0007 SAPKGPRB07
BP-R3PF 470V2 0000 -
ST-A/PI 01F_R3_470 0000 -
ST-PI 003C_620 0000 -
I ] Problem
We are having problem while replicating the Business Partners from CRM to R3. When we create a Business Partner ( Type People) through transaction BP on the CRM server it creates an entry in table but000 on the CRM side but the same entry does not exist in kna1 table on R/3 server.
When we check the BDOC through transaction smw01 on the CRM server there exist an entry with BDOC State Description " Send to receivers (not all have confirmed)" for BDOC Type BUPA_MAIN.
II ] Configurations
We have done following settings before creating Business Partners through CRM
Settings on CRM Server
1> RFC Destination "CARDONR3_DEV" for R3 server is defined in sm59 on the CRM side and is working OK.
2> Through transaction BUCF we have defined a number range named C1 ( 0005000000 to 0005999999) with External flag deselected.
3> Through SPRO we have defined a grouring C001 (CRM Customer) and assigned number range C1 to it.
Settings on the R3 server
1> RFC Destination "CMDCLNT110" for CRM server is defined in sm59 on the R3 side and is working OK.
2> Through transaction OVZC we have defined cutomer number range named C1 ( 0005000000 to 0005999999) with External flag selected.
3> Through transaction OVT0 we have created Cutomer Account Group named Z001 which is copy of 0001 (Sold to Party). Number range C1 is assigned to the account group Z001.
4> Through transaction VOPA we have maintained the Partner function for customer master i.e Acct Grp Z001 is assigned to Function SP.
5> In transaction PIDE under CRM -> R3 assignment we have selected account group Z001 to Classification type B (i.e Customer)
III ] Procedure Followed
1> On the CRM server we execute the transaction "BP" .
2> We Click on Create Person button.
3> Following Selections are made
a) Create in role : Sold-To-Party
b) Grouping : CRM Customer
c) Field Title, First name and Last name are selected
d) In the tab Classification we select R/3 Account Group as "0001". System does not allow us to select the R/3 Account group "Z001"
4> On Saving the entry Business Partner is created in table but000 on the CRM side.
5> The above entry is not replicated in table kna1 on R3 side as expected.
IV ] Observation
We are not able to select account group "Z001" in the BP creation screen. When we run the Intial Load (R3AS) on CRM server for object "DNL_CUST_ACGRPB" (i.e AccountingGrp Business Partner) (Replication from R3 to CRM) it shows the status done in screen R3AM1 but the entry for account grouip Z001 which is created manually on R3 side during the configuration phase is not replicated on the CRM side.
We have referred a note for the above error which said that the basis patch "SAP_BASIS" should be at level 56 but we are already on Patch Level 56.
Please guide us.
Thanks & Regards,
YatinHi Yatin,
Glad to hear one of the problem has resolved.
In order to simplify the analysis, I assume few things
from your information :
1. Connection between CRM and R/3 are correctly run
2. Other necessary customizing Objects relate to BP
have been downloaded properly to CRM.
Few things you can check :
1. Did you enter Correspondence Language & Language
in CRM BP ? just make sure you did.
2. Try to complete minimum data such as Search Term,
Street/House, Postal Code / City and Country in CRM BP.
3. Check the detail Error message in SMW01 (can you get
more detail - normally you can click on SHOW BDOC Msg
ERROR)
You also can trace/debug LUW,:
- use tcode SMQ1 to see the stopped queue for that error
transfer
- Click menu Go To -> QOUT Scheduler
Click on R/3 destination and deactivate/deregister it
- In SMQ1 select the error queue, double click on it.
and after next screen double click again
- Then Start DEBUG LUW
- Insert debug breakpoint in statement Call Transaction
and execute F8
- When it stopped, Change the variable mode to A
it will show you the missing/incomplete fields.
You need to register/activate back the R/3 destination after you have finish debugging.
Hope this helps, let me know the result
Cheers,
Gun. -
No Material Master replication from R/3 to CRM
Hallo guys,
i've got no replication of material master, haven't tried any other object except customizing but customizing is triggered from CRM and was replicated fine. Can anybody help me how can i debug the replication process from R/3?
Thanks for your help in advance.Dmitry,
You first need to determine where your errors are happening?
1. Do you have blocked queues on CRM? If you see a blocked inbound/outbound queue on CRM via SMQ1 or SMQ2, then you can try to rerun the BDOC message in the queue.
2. Is there tax code customizing not downloaded correctly into CRM? This sometimes can hang up your download of materials?
3. Have you looked at SMW01 after the load to see if you have any BDOC's in error, the queues were empty?
4. What is the status of the initial load R3AM1?
I would hold off from debugging until I figure out where in the download process that I am receiving the error. Once I know that fact them I can debug a single download. You will have to set a filter on the material object to a single material and attempt an initial download. When you perform the initial download you will need all queues deregistered on the CRM side, so that you manually execute the BDOC import into CRM.
The last step will require placing a breakpoint into the validation function module for material.
I believe validation function module is: COM_PRODUCT_MAT_VALIDATE. If you have questions along the way of debugging the flow, please reply back and I will try to see if I can answer them. It has been a little while since I had to debug our middleware downloads.
Good Luck,
Stephen -
In memory replication not working
We are using Weblogic 4.5.1 SP5 (I know that is an old service pack -
but this is in a production system and it usually takes a guarantee that
a change will fix a bug before being allowed).
We are clustering two weblogic servers.
In our test systems everything works great.
In our production systems, failover works, but not in memory
replication. With the replication debugging output turned on I see the
following output:
<WebLogicServer> WebLogic Server started
<RJVM> Creating connection to 10.100.35.90/10.100.35.80 ...
(I should point out that this RJVM message only appears on one of the
servers, appears whether or not the other server is running, and
10.100.35.80 is not the IP address of the other server nor of this
server.)
(Note, it never prints the typical <RepMan>Adding XXXXXX to the cluster)
When a user connects and a session is created, we see the following:
<RepMan>Unable to create secondary for XXXXXXX
<RepMan>Registered XXXXXX
<RepMan>Get Secondary JVMID returning null for XXXXXXX
<RepMan>updateSecondary called on unpaired primary
<RepMan>lookup found for XXXXXX
The second server never outputs any new information.
It's not the code, this works in test, and we have poured over the
configuration, and all configuration files look correct.
The MulticastTest also works in the production system.
Any ideas?
Looks like they are not in cluster..
double check the configuration and check in weblogic console whether you see both servers under the cluster name...
Robert Antonucci <[email protected]> wrote:
>We are using Weblogic 4.5.1 SP5 (I know that is an old service pack -
>but this is in a production system and it usually takes a guarantee that
>a change will fix a bug before being allowed).
>
>We are clustering two weblogic servers.
>In our test systems everything works great.
>In our production systems, failover works, but not in memory
>replication. With the replication debugging output turned on I see the
>following output:
>
><WebLogicServer> WebLogic Server started
><RJVM> Creating connection to 10.100.35.90/10.100.35.80 ...
>(I should point out that this RJVM message only appears on one of the
>servers, appears whether or not the other server is running, and
>10.100.35.80 is not the IP address of the other server nor of this
>server.)
>(Note, it never prints the typical <RepMan>Adding XXXXXX to the cluster)
>
>When a user connects and a session is created, we see the following:
>
><RepMan>Unable to create secondary for XXXXXXX
><RepMan>Registered XXXXXX
><RepMan>Get Secondary JVMID returning null for XXXXXXX
><RepMan>updateSecondary called on unpaired primary
><RepMan>lookup found for XXXXXX
>
>The second server never outputs any new information.
>
>It's not the code, this works in test, and we have poured over the
>configuration, and all configuration files look correct.
>The MulticastTest also works in the production system.
>
>Any ideas?
>
Maybe you are looking for
-
Problem with if/else statement for adventure game
Can anyone offer a hint as to why I am getting a null value printed out in the last line. I have comments that indicate what progress or validation step has occurred to move forward. There is something obviously not working with my user input if/else
-
ITunes 8 and Windows Vista "sound effect"
So ever since iTunes 8 came out, I get that stupid annoying sound effect whenever doing anything in iTunes. I can turn off the sidebar and it will stop for the most part, but I still get it when going to the iTunes Store or going to my iPod list. I w
-
Airport Express and Airtunes not working
Hi all. I have a Digital Audio G4. I've been able to use my G4 with iTunes and my Airport Express for quite a while. All of sudden iTunes no longer sees it. The Airport Admin Utility doesn't see it either. But I can still connect to the internet with
-
Hello, I m working on SRM-MDM scenario. I m sending CatalogUpdateNotification_Out using BBP_CCM_TRANSFER transaction from SRM But in the xml file which i receive in XI, Catalog Content data is missing. I dont know anything in SRM. Plz help. Thanks, M
-
Re: help.... built in isight on macbook
I am experiencing the same problem on my MBP. I was in the middle of a video chat using Skype, when the window froze, the green status light went out, and my conversation got cut off. Now, the camera is not accessible by any program. I too get the ca