JMS with Distributed clients.
I am planning on having JMS Queues in a cluster and a business component [EJBs] in a separate cluster.
I have distributed clients listening on a topic and when they get the message they process it and put the result on the Queue in my cluster.
One of my business components from the business components cluster gets that result from the queue and processes it.
Problem:
My requirement is to send a message to 2 of my distributed clients and when they process the message and put the results in the Queue, I want the results from both the clients to be processed by the same business component in the cluster.
Is it possible?
Thank you.
Edited by: user10510140 on Dec 9, 2010 12:49 PM
You will have to use MessageSelectors.
ram.
Similar Messages
-
JMS Failover with Distributed Destinations in 7.0
How does JMS failover with distributed destinations in WL 7.0?
In an environment using file stores for persistent messages, can a working server
automatically pick up unprocessed and persisted messages from a failed server?
If so, what's the best way to set this up?
Or, is this completely manual? In other words, we have to bring up a new server
pointing to the location of the file store from the failed server?
It appears that two JMSServers cannot share the same file store and, I'm assuming,
two file stores cannot be using the same directory for persistence.
So the HA you're talking about is something like Veritas automatically restarting
a server (or starting a new one) to process the messages in the persistent queue
that were unprocessed at the time of failure with the file store residing on some
sort of HA disk array.
The key point is that a message once it arrives at a server must be processed
by that server or, in the case of failure of that server, must be processed by
a server similarly configured to the one that failed so that it picks up the unprocessed
messages. The message can't be processed by another server in the cluster.
Or, is there some trick that could be employed to copy from the file store of
the failed server and repost the messages to the still operating servers?
"Zach" <[email protected]> wrote:
>Unless you have some sort of HA framework/hardware, this is a manual
>operation. You either point to the existing persistent storage (shared
>storage or JDBC connection pool), or you move the physical data.
>
>_sjz.
>
>"Jim Cross" <[email protected]> wrote in message
>news:[email protected]...
>>
>>
>> How does JMS failover with distributed destinations in WL 7.0?
>>
>> In an environment using file stores for persistent messages, can a
>working
>server
>> automatically pick up unprocessed and persisted messages from a failed
>server?
>> If so, what's the best way to set this up?
>>
>> Or, is this completely manual? In other words, we have to bring up
>a new
>server
>> pointing to the location of the file store from the failed server?
>
>
-
JMS Durable Distributed Topics
Please forgive my ignorance if I am doing something silly. I am new to Weblogic
and JMS, but learning a lot quickly. Any help will be greatly appreciated.
I am running weblogic 8.1 with no service packs in a development environment only.
We are trying to work out what is the expected behaviour for our current JMS Topic
framework.
I have a two server cluster with distributed topics configured. The two topics
are configured to be durable. I have a test which generates about 100 events for
test purposes. Under normal circumstances, each server processes about 50 messages.
(Load balancing!)
When the test is running, I kill one of the servers manually before it finishes.
(Not a gracefull shutdown). The killed server processes about 20 messages, and
the running server processes about 50. I can see that tables for the persistent
topics have something (I don't know what) representing about all 100 events sent.
When I bring the killed server back up, nothing happens. I would expect, from
the documentation that I read, that the remaining 30 or so events will be put
on the topic to be processed by our MDBs.
Why don't all the events get placed on the topic of the killed server when it
starts back up?
What is the expected behaviour here?
Is something wrong with my topic setup?
Thanks in advance for any help...
regards,
Patrick Parato
Hi Patrick,
Note 1: If you desire MDB to be transactional. Make sure
the assembly descriptor in ejb-jar.xml is set to
"Required" in addition to making the transaction-type
"Container" as you have already done.
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>YOUREJBNAME</ejb-name>
<method-name>onMessage()</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
Note 2: Your MDB is non-durable. It needs to be durable
to cause messages to persist. Add the following line
in the message-driven-destination clause of your ejb-jar.xml:
<subscription-durability>Durable</subscription-durability>
See the JMS FAQ on dev2dev.bea.com (or the JMS Performance
Guide white-paper) for information on how to make
sure a message is persistent.
Note 3: Only one durable subscriber MDB will
be able to attach to a given durable subscription, MDB's
on other servers won't be able to, so even if the MDB
is targeted at the cluster only one MDB will be able
to process messages. This is the nature
of durable subscriptions. I'm attaching some personal
notes on the subject.
Note 4: Durable subscriptions must refer to
the JNDI name of member destinations, not to
the distributed destination. WL does not support
durable subscriptions directly on a distributed topic.
Note 5: If you do not want message replication I'm not
sure why you are using a distributed topic. Use a
distributed queue.
Tom
Patrick Parato wrote:
> Tom,
>
> Thanks for the quick reply.
>
> The first thing I want to clarify is that we only have one subscriber (MDB) that
> is deployed once across multiple servers in a cluster. So this may explain why
> each server is getting half the messages.
Its still not clear. Each MDB pool should get each message.
The individual
instances in the pool will divide the messages sent to their MDB
pool's subscription among them.
>
>
>>2) Make sure that you are using durable subscribers. I suspect you
>>are not. Note that durable subscribers are not supported
>>for distributed destinations - they must refer directly to a member
>>destination instead.
>>
>
>
> We are definitely using a distributed topic. The entry for our MDB in the weblogic-ejb.jar.xml
> for the <destination-jndi-name> refers to the jndi name of the distributed topic.
> So if I understand you correctly you are saying that the <destination-jndi-name>
> should refer to the jndi name of an actual phyiscal topic on one of the servers.
> By tying an MDB to a regular topic, how do we achieve failover if the JMS server
> that the topic is associated with should fail?
>
>
>
> Here is a snippet of our config.xml:
> (Names have been changed for security reasons)
>
> <JMSServer Name="JMS Server1" Store="Event Store1" Targets="myserver1">
> <JMSTopic CreationTime="1065029382062"
> JNDIName="distributed.topic@JMS Server1"
> JNDINameReplicated="false"
> Name="Distributed Topic@JMS Server1"
> Template="Distributed Topic" TimeToDeliverOverride="5000"/>
> </JMSServer>
>
> <JMSServer Name="JMS Server2" Store="Event Store2" Targets="myserver2">
> <JMSTopic CreationTime="1065029382375"
> JNDIName="distributed.topic@JMS Server2"
> JNDINameReplicated="false"
> Name="Distributed Topic@JMS Server2"
> Template="Distributed Topic" TimeToDeliverOverride="5000"/>
> </JMSServer>
>
>
> <JMSDistributedTopic JNDIName="distributed.topic" Name="Distributed Topic" Targets="Cluster">
> <JMSTemplate DeliveryModeOverride="Persistent"
> Name="Distributed Topic" TimeToDeliverOverride="5000"/>
> <JMSDistributedTopicMember
> JMSTopic="distributed.topic@JMS Server1" Name="Distributed Topic@JMS
> Server1"/>
> <JMSDistributedTopicMember
> JMSTopic="distributed.topic@JMS Server2" Name="Distributed Topic@JMS
> Server2"/>
> </JMSDistributedTopic>
>
>
> ejb-jar.xml:
>
> <message-driven>
> <ejb-name>AnMDB</ejb-name>
> <ejb-class>package.AnMDB</ejb-class>
> <transaction-type>Container</transaction-type>
> <message-driven-destination>
> <destination-type>
> javax.jms.Topic
> </destination-type>
> </message-driven-destination>
> </message-driven>
>
> weblogic-ejb.jar.xml:
>
> <weblogic-enterprise-bean>
> <ejb-name>AnMDB</ejb-name>
> <message-driven-descriptor>
> <destination-jndi-name>distributed.topic</destination-jndi-name>
> </message-driven-descriptor>
> <enable-call-by-reference>True</enable-call-by-reference>
> <jndi-name>ejb.AnMDB</jndi-name>
> </weblogic-enterprise-bean>
>
> Thanks for you help and quick reply.
>
> regards,
> Patrick Parato
>
A durable topic subscriber MDB uses its name to generate its client-id.
Since JMS enforces uniqueness on this client-id, this means that if a durable
subscriber MDB is deployed to multiple servers only one server will be able
to connect. Some applications want a different behavior where
each MDB pool on each server gets its own durable subscription.
The MDB durable subscription id, which must be unique on its topic, comes from:
1) <jms-client-id>MyClientID</jms-client-id>
(the weblogic dtd)
2) if (1) is not set then the client-id
comes from the ejb name.
The durable subscription is uniquely identified within a cluster by a
combination of "connection-id" and "subscription-id". Only one active
connection may use a particular "connection-id" within a WebLogic cluster.
The connection id comes from:
1) The "ClientId" attribute configured on the WebLogic connection factory.
This defaults to null. Note that if the ClientId is set on a connection
factory, only one connection created by the factory
may be active at a time.
2) If (1) is not set, then, as with the subscriber-id,
the connection-id is derived from jms-client-id descriptor attribute:
<jms-client-id>MyClientID</jms-client-id>
(the weblogic dtd)
3) If (1) and (2) are not set, then, as with the subscriber-id,
the connection-id is derived from the ejb name.
Work-around:
A) Create a custom connection-factory for each server:
1) configure "JNDIName" to the same value across all servers
("myMDBCF" in this example)
2) configure "ClientId" to a unique value per server
3) enable "UserTransactionsEnabled"
4) enable "XAConnectionFactoryEnabled"
5) set "AcknowledgePolicy" to "ACKNOWLEDGE_PREVIOUS"
6) target the CF at a single WebLogic server
(Number 5 is required for non-transactional topic MDBs)
B) In the MDB's weblogic-ejb-jar.xml descriptor, set the MDB's connection
factory to the JNDI name of the custom connection factories configured in
(A). Optionally, also specify the subscriber-id via the jms-client-id
attribute.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>exampleBean</ejb-name>
<message-driven-descriptor>
<connection-factory-jndi-name>myMDBCF</connection-factory-jndi-name>
<jms-client-id>myClientID</jms-client-id>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
C) Target the application at the same servers that have the custom connection
factories targeted at them.
Notes/Limitations:
1) If the MDB is moved from one server to another, the MDB's corresponding
connection-factory must be moved with it.
2) This work-around will not work if the destination is not in the same
cluster as the MDB. (The MDB can not use the local connection factory, which
contains the connection-id, as connection factories do not work unless they
are in the same cluster as the destination.)
3) This work-around will not work for non-WebLogic JMS topics.
-
Changes needed with different client.
Hi,
we are using FILE,IDOC,JMS MQ ,ABAP Proxy and See burger adapters with sender and receiver aswell.
we are using Master SLD ..I mean single SLD.
Client has asked for testing the interfaces...
we are using
XI box with client as 200
R3 box with client as 217.
All the connections are done with R3 client 217.
No my problem is...
My client has asked to test my interfaces with R3 client 216.
what are the changes i need to change in XI for R3 client 216....please let me knowHi,
The Following things needs to be take care in this Activity
1) No Need to create Another TS for SAP R/3, this will not allow you to create another one.
2) Just Add the Business system for the Existing TS with Client 216 and also take care abt the Logical System Name here.
3) Refresh SLD Data Cache in IDEnvironment-
4) Now Use this New Business System for Communication which is having the New Client and Corresponding LS Name
REgards
Seshagiri -
How to do jms with netweaverdeveloperstudio
hi,
can u pls tell how to do jms with nwds ?
which things i need to configure in webas?
how to write client for jms?
regards
GuruPlease try the J2EE engine (JMS) example first to have a better understanding of JMS given in portal/index.html
I hope the following references may also help you
http://help.sap.com/saphelp_nw04/helpdata/en/a3/63af1bbf09469fa1615c05f0daff6f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/90/57849e5e3e45d784afc4e3bfa8136f/frameset.htm
Regards -
Siebel JMS with IBM Webshere MQ(7.5.0.1)
Hi Guys,
I try to configure MQ 7.5.0.1(with JMS) with Siebel so that I can send/receive messages using EAI JMS Transport. when I try to send a message, i get following error in jms log file:
[SIEBEL ERROR] Thread[main,5,main] [11:56:37.171 AM Fri Feb 28: ] Error invoking Send --
SiebelJMSException errorSubtype=JMS_EXCEPTION
at com.siebel.eai.jms.JMSBusinessService.doInvokeMethodWithExceptions(JMSBusinessService.java:582)
at com.siebel.eai.jms.JMSBusinessService.doInvokeMethod(JMSBusinessService.java:249)
at com.siebel.eai.SiebelBusinessService.invokeMethod(SiebelBusinessService.java:9)
[SIEBEL ERROR] Thread[main,5,main] [11:56:37.171 AM Fri Feb 28: ] Threw SiebelBusinessServiceException with
ErrorCode = JMS_EXCEPTION
ErrorMessage = An unexpected error occurred (see StackTrace): com.ibm.mq.jms.MQConnectionFactory cannot be cast to javax.jms.QueueConnectionFactory
StackTrace = SiebelJMSException errorSubtype=JMS_EXCEPTION
at com.siebel.eai.jms.JMSBusinessService.doInvokeMethodWithExceptions(JMSBusinessService.java:582)
at com.siebel.eai.jms.JMSBusinessService.doInvokeMethod(JMSBusinessService.java:249)
at com.siebel.eai.SiebelBusinessService.invokeMethod(SiebelBusinessService.java:9)
[SIEBEL DETAIL] Thread[main,5,main] [11:56:37.171 AM Fri Feb 28: ] Cumulative time = 2107
JAVA profile:
JVM Classpath C:\JAR;C:\JAR\SIEBEL.JAR;C:\JAR\SIEBELJI_ENU.JAR;C:\JAR\JNDI.JAR;C:\JAR\CONNECTOR.JAR;C:\JAR\JMS.JAR;C:\JAR\PROVIDERUTIL.JAR;C:JAR\FSCONTEXT.JAR;C:\JAR\COM.IBM.MQ.JAR;C:\JAR\COM.IBM.MQJMS.JAR;C:\JAR\COM.IBM.MQ.JMQI.JAR;C:\JAR\DHBCORE.JAR;
JVM DLL Name C:\Program Files (x86)\Java\jre7\bin\client\jvm.dll
JVM Options -Djms.log=C:\JMS\log\jms.log
binding file is located in folder c:\JAR
file jndi.properties:
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
java.naming.provider.url=file:/c:/JMS
Can anybody help me?
Thanks,
SN>
> I am trying to connect to Websphere MQ series via PI, Websphere MQ series is running on Linux environment and PI system running on AIX operating system, i got the drivers from linux environment where queue is running, can i deploy those drivers into my PI system?? because it is running on AIX.
>
It will work.
> Or else is there any different jar files for different operating systems???
as per my knowledge no.
Regards,
Raj -
Hi,
I would like to access to my shared variables using an OPC client. (a free software called powerOPC or any other one)
When I use it locally, everything goes well, I can access my shared variables, but when I try to access from a distantr PC, I cannot connect and get some errors. I've tried to open port 135 on the firewall, I've read the following post: http://forums.ni.com/t5/LabVIEW/opc-dcom-access-denied/m-p/822246/highlight/true#M373884
But I still can't access my variables.
The NI Distributed System Manager can access to the distant shared variables, so I don't know what's wrong with other clients.
Does anyone knows how to do?
Both PC are running win 7, one is 32 the other 64bit.
LV2011
RegardsHi toto26,
thank you for using National Instruments discussion forum.
Could you detail the way you use to communicate with your OPC server thanks share variable? Are you using datasocket like in this document or are you using DSC ?
Could you tell us more about the errors you get? Have you already seen this KB document and its first related link?
Thank you in advance
Regards,
Audrey_P
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm... -
JMS C/C++ client without a java proxy
Hey folks,
i am wondering if there is a C client for JMS which doesn't require a java-Proxy?
I know the active-mq website, but the c/c++ client section there is really confusing and it seems that no one takes care of it anymore:
The active-mq website suggest the following as c/c++-clients:
It is very common for an organisation to have lots of legacy C code which needs integration into the message bus. The current available solutions are
* use the OpenWire C Client which is only available in ActiveMQ 4.x or later.
* we are working on the OpenWire CPP Client
* the ActiveMQ C++ Clients is currently a C++ API to Stomp, and is a full-blown replacement for CMS for AMQ v4.0.1 and later. In the future this will be expanded to support OpenWire as well.
* the CMS C++ client which is a C++ API to Stomp which can also be implemented with OpenWire
* use the Stomp C Client for any version of ActiveMQ from 3.1 onwards. You can also use Stomp from many other languages like .Net, Python, Ruby, Perl etc.But:
a)
* use the OpenWire C Client which is only available in ActiveMQ 4.x or later.The only two links:
You can browse the code here
http://svn.activemq.org/branches/activemq-4-0/activemq/openwire-c/
e.g. here's an example of it in use...
http://svn.activemq.org/branches/activemq-4-0/activemq/openwire-c/src/examples/are deadlinks.
Google doesn't help as well, this project seems to be dead?
b)
we are working on the OpenWire CPP Clientok, nothing released yet (as far as i can tell)
c)
the ActiveMQ C++ Clients is currently a C++ API to Stomp, and is a full-blown replacement for CMS for AMQ v4.0.1 and later. In the future this will be expanded to support OpenWire as well.But if i click on the link i get redirected to
CMS is an easy-to-use JMS 1.1-like API. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.So it says " it is a full replacement for CMS", but leads me directly to CMS?
What the hack?
Furthermore - and even worse - __NOT__ a single download link is working as well as the link to the api-docs is broken (if it ever worked)...
d)
the CMS C++ client which is a C++ API to Stomp which can also be implemented with OpenWireYeah, see c)
e)
use the Stomp C Client for any version of ActiveMQ from 3.1 onwards. You can also use Stomp from many other languages like .Net, Python, Ruby, Perl etc.Almost no documentation at all.
So, in a nutshell, this whole "jms-c/c++ client" project seems to be just dead or unusable....
Has somebody any ideas for a:
- C/C++ JMS client
- which does not need a proxy
Thx for all clues in advance!I found the activemq open-wire projects for C/C++ under the sandbox. There are no examples for C++ using openwire yet. The repository paths for C and C++ are:
https://svn.apache.org/repos/asf/activemq/sandbox/openwire-c
https://svn.apache.org/repos/asf/activemq/sandbox/openwire-cpp -
WLS JMS supports the clients developed by using non-java program languages,such as,c++,VB...
WLS JMS supports the clients developed by using non-java program languages,such
as,c++,VB?
The short answer is yes. This is a frequently asked question. I
suggest searching this newsgroup in google using terms like "C++",
"IIOP", ".NET", "JCOM".
Note also that WL 8.1 (now out in beta) contains a thin java client
(something like 0 or 300K without JMS, 700k with. The 0K client comes
from leveraging WL's IIOP support.)
Tom, BEA
jerry8006 wrote:
> WLS JMS supports the clients developed by using non-java program languages,such
> as,c++,VB?
-
I get the following when trying to use JMS within XA.
XAResource jmsxa = _XAqueueSession.getXAResource();
produces error:
java.lang.IllegalStateException: can only be called from server
at weblogic.jms.client.JMSXASession.getXAResource(JMSXASession.java:87)
This code is being run outside of the WLS and I am trying to use JOTM as my transaction
manager implementation. The documentation refers to needing a different license
for using XA, is that the case here? Or is it plain old pilot error.
Thanks,
don.
Don Schafer wrote:
> Tom,
>
> thanks for your responce. Does this mean that for each XA transaction in a remote
> client I need to use (I am guessing here) RMI?
For remote WL JMS clients you need to use BEA's TM if
you want them to participate in a transaction.
Just start a JTA user transaction and commit it
when you are done.
There is nothing special about the way WL JMS is invoked:
Use a URL to get a WL JNDI context, look up a WL JMS connection
factory, and go. The fact that RMI is used as the
communication protocol is immaterial.
I suggest reading the doc:
http://edocs.bea.com/wls/docs81/jms/trans.html#1037593
http://edocs.bea.com/wls/docs81/jta/index.html
And checking out the sample code that comes
with WebLogic.
>
> Does that mean each enlist call, each commit call wil have additional remote overhead?
There is no need to manual enlist BEA's JMS with BEA's TM (we do it
automatically). In fact, it may negatively impact performance
to do so.
I think you need not worry about remote overhead.
>
> Thanks for your help,
> don.
>
> Tom Barnes <[email protected]> wrote:
>
>>Hi Don,
>>
>>No pilot error. The exception text is correct.
>>WebLogic does not support this call on remote clients.
>>The same call will work from code called from within a WebLogic
>>server.
>>
>>I suggest filing an enhancement request with customer
>>support, and letting your BEA sales rep know about your need.
>>
>>The alternative is to use BEA as the transaction monitor.
>>
>>Tom, BEA
>>
>>P.S. With the current product, JMS capability implies
>>that there must already be a XA capability. It is not
>>possible to purchase JMS capability without getting XA.
>>
>>Don Schaefer wrote:
>>
>>>I get the following when trying to use JMS within XA.
>>>
>>>XAResource jmsxa = _XAqueueSession.getXAResource();
>>>
>>>produces error:
>>>
>>>java.lang.IllegalStateException: can only be called from server
>>> at weblogic.jms.client.JMSXASession.getXAResource(JMSXASession.java:87)
>>>..
>>>
>>>This code is being run outside of the WLS and I am trying to use JOTM
>>
>>as my transaction
>>
>>>manager implementation. The documentation refers to needing a different
>>
>>license
>>
>>>for using XA, is that the case here? Or is it plain old pilot error.
>>>
>>>Thanks,
>>>don.
>>>
>>>
>>>
>>>
>>>
>>
>
-
How to share an unpublished folio with a client to review?
I am designing a DPS single edition publication for a client. Is there a way for me to share the unpublished folio with the client if they do not have an Adobe Creative Cloud account or an Adobe ID? If they just need to signup for an Adobe ID, what else do I (or they) need to do so that they are able to signin to the Adobe Content Viewer and see the unpublished folio?
They need an iPad, the Adobe Content Viewer and a free Adobe ID.
You share the folio via the folio builder panel to that ID.
That's it. When the client signs into the Content Viewer the folio will
be available for download. -
How to control one server with multiple clients via TCP/IP
I am wanting to control a single server with multiple clients. Only one client would be active at a time, so there would be no conflict. I want to use TCP/IP. So far, I have programmed a cluster that passes data back to the server with no problems. The challenge come in when a second client is added to the mix. I have't been able to figure out how to turn each client on and send the appropriate data and then turn it off so it doesn't keep sending the same data to the server.
Here are the things that I have considered and did some preliminary testing, but don't really know how to impliment:
1. Send a numeric on the front of the cluster packet that tells the server that data is on the way.
2. Send a boolean on the front of the cluster packet to somehow turn the server TCP/IP on.
The problem I have found is that LabVIEW TCP/IP doesn't like to be turned on and off. If it doesn't get the data it expects, it goes into a reset mode and that kills the response time.
Any help?You should consider implementing a set of simple one-byte commands that can be sent back and forth between the Server and the Clients. You can base all of these ideas off the example in the Example Finder under Networking >> TCP and UDP called Multiple Connections - Server.
You will have two loops in the server VI: one to wait for new connections, and one to send and receive data from the existing connections. For instance, after one of the clients connects, it can request control of the server to send data to it by sending the character "R" for request. Every time the send/receive loop of the Server executes, the first thing it can do is to check all the existing connections to see if any of the clients have sent a control request ("R"). If so, it will create a buffer (array) of control requests. This could be in the form of Connection IDs or indexes in the array for a particular Connection ID. Your choice.
After the Server receives a request for contol, if it is not already under control by another client, then it can send a response to the first client on the control request list. For instance, the server could send the first client a "S" command for send. Note that after the clients send their control request, they should execute a TCP Read and wait indefinitely for the server to respond with the one-byte "S" command. Then, once the client in control is finished sending data to the server, it could send the character "X" telling the Server to release it from control.
The example I mentioned above already does a similar thing. Note how when a client wants to disconnect, they send the letter "Q". You can see this in the Multiple Connections - Client VI. The Server then checks each individual connection to see if it's received this one-byte command, and if it has, it closes the connection to the client. This is what you would want to implement, but instead of having just one command, you'll have to distinguish between a few and build up a buffer of control requests.
Finally, if a client does decide to disconnect in your application, they could send the command "Q" just like the example above. At this point, close the connection and remove that Connection ID from the array of connections. You will also have to handle the case that this client was in the request control waiting line when it disconnected, in which case you need to delete it from that array as well.
This will definitely work for you, but it will take some work. Best of luck!
Jarrod S.
National Instruments -
Is SAP BI reporting is possible in ECC 6.0 with same client
Hi all,
My requirement is, we need to design SAP BI data flow in ECC 6.0 with same client only. Now I am designing the BI data models as per the requirement of SD sales reports in ECC 6.0.For this, when i was extracting the data from SD datasource(2lis_11_vahdr) in RSA3 its showing 0 records,actually as per VA01 some records are available but its not showing in the RSA3.
My doubt is , is it possible to extract the data from ECC 6.0 and load the data to the datatargets and get the SAP BI reports in ECC6.0 with the same client.
Please suggest as soon as possible.
ThanksIt is possible to load the data from the same client. It all depends on the source system and the client which has been connected in the RFC connection.
Let me know if this helps.
Regards,
Avinash -
New WSUS on Server 2012 - problem with win8 clients
Hi,
Two weeks ago we created a new Server 2012 and installed the WSUS role from scratch on it. Its version number is: 6.2.9200.16384. It replaced a Server 2008 WSUS server. After some time all the win7 clients updated and reported as
they did on the old and replaced server.
However all our win8 clients refuse to update against this server. They show correctly up in WSUS server console each with 107 needed updates day after day. We have rebooted them and done numerous wuauclt /resetauthorization /detectnow and wuauclt
/detectnow /reportnow, but to no avail.
I paste in some lines from a win8 client winupdate log at the end of this message if someone can figure out what I have to do to get these clients update as they did against the old wsus server. Thanks for help on this issue.
regards Tor
2014-02-03 08:33:38:008 920 153c Agent *************
2014-02-03 08:33:38:008 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:38:008 920 153c Agent *********
2014-02-03 08:33:38:008 920 153c Agent * Online = Yes; Ignore download priority = No
2014-02-03 08:33:38:008 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:38:008 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:38:008 920 153c Agent * Search Scope = {Machine & All Users}
2014-02-03 08:33:38:008 920 153c Agent * Caller SID for Applicability: S-1-5-18
2014-02-03 08:33:38:008 920 153c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2014-02-03 08:33:38:008 920 1990 AU >>## RESUMED ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-02-03 08:33:38:008 920 1990 AU # 0 updates detected
2014-02-03 08:33:38:008 920 1990 AU #########
2014-02-03 08:33:38:008 920 1990 AU ## END ## AU: Search for updates [CallId = {ABC7E77F-635F-4192-9B92-CBF9B1CB8AB0} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-02-03 08:33:38:008 920 1990 AU #############
2014-02-03 08:33:38:023 920 153c Misc Microsoft signed: Yes
2014-02-03 08:33:38:023 920 153c Misc Infrastructure signed: Yes
2014-02-03 08:33:38:023 920 153c EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe1.ws.microsoft.com/w8/2/redir/storeauth.cab"
2014-02-03 08:33:38:023 920 153c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
2014-02-03 08:33:38:039 920 153c Misc Microsoft signed: Yes
2014-02-03 08:33:38:039 920 153c Misc Infrastructure signed: Yes
2014-02-03 08:33:38:039 920 153c EP Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
2014-02-03 08:33:38:055 920 153c PT +++++++++++ PT: Synchronizing server updates +++++++++++
2014-02-03 08:33:38:055 920 153c PT + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL = https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
2014-02-03 08:33:38:055 920 153c Agent Reading cached app categories using lifetime 604800 seconds
2014-02-03 08:33:38:055 920 153c Agent Read 0 cached app categories
2014-02-03 08:33:39:211 920 153c Agent * Added update {E7FF661C-6A03-4387-A1EE-1D723B52EF60}.3 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:211 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:211 920 153c Agent * Found 13 updates and 31 categories in search; evaluated appl. rules of 69 out of 94 deployed entities
2014-02-03 08:33:39:211 920 153c Agent *********
2014-02-03 08:33:39:211 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:211 920 153c Agent *************
2014-02-03 08:33:39:211 920 1a64 Report REPORT EVENT: {0786C161-F6DC-4842-85D6-9506124654AD} 2014-02-03 08:33:38:008+0100 1
147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 Windows Update Command Line Success Software Synchronization
Windows Update Client successfully detected 0 updates.
2014-02-03 08:33:39:211 920 1a64 Report REPORT EVENT: {1E5D9728-220F-44A3-8BCC-ADE69687531D} 2014-02-03 08:33:38:008+0100 1
156 [AGENT_STATUS_30] 101 {00000000-0000-0000-0000-000000000000} 0 0 Windows Update Command Line Success Pre-Deployment Check
Reporting client status.
2014-02-03 08:33:39:211 920 1a64 Report REPORT EVENT: {57BAB7D0-685B-4D73-BDF7-82AFCE8675B0} 2014-02-03 08:33:39:211+0100 1
147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 Windows Update Command Line Success Software Synchronization
Windows Update Client successfully detected 13 updates.
2014-02-03 08:33:39:211 920 1a64 Report CWERReporter finishing event handling. (00000000)
2014-02-03 08:33:39:227 920 153c Agent *************
2014-02-03 08:33:39:227 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:227 920 153c Agent *********
2014-02-03 08:33:39:227 920 153c Agent * Online = No; Ignore download priority = No
2014-02-03 08:33:39:227 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:39:227 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:39:227 920 153c Agent * Search Scope = {Current User}
2014-02-03 08:33:39:227 920 153c Agent * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1155
2014-02-03 08:33:39:258 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {A9A0E183-0667-46D6-84E4-17CEBCEE5A22}.1 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:258 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:258 920 153c Agent * Found 11 updates and 29 categories in search; evaluated appl. rules of 58 out of 94 deployed entities
2014-02-03 08:33:39:258 920 153c Agent *********
2014-02-03 08:33:39:258 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:258 920 153c Agent *************
2014-02-03 08:33:39:258 920 153c Agent *************
2014-02-03 08:33:39:258 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:258 920 153c Agent *********
2014-02-03 08:33:39:258 920 153c Agent * Online = No; Ignore download priority = No
2014-02-03 08:33:39:258 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:39:258 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:39:258 920 153c Agent * Search Scope = {Current User}
2014-02-03 08:33:39:258 920 153c Agent * Caller SID for Applicability: S-1-5-21-2212025170-3189117132-1219651784-500
2014-02-03 08:33:39:305 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:305 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:305 920 153c Agent * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03 08:33:39:305 920 153c Agent *********
2014-02-03 08:33:39:305 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:305 920 153c Agent *************
2014-02-03 08:33:39:305 920 153c Agent *************
2014-02-03 08:33:39:305 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:305 920 153c Agent *********
2014-02-03 08:33:39:305 920 153c Agent * Online = No; Ignore download priority = No
2014-02-03 08:33:39:305 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:39:305 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:39:305 920 153c Agent * Search Scope = {Current User}
2014-02-03 08:33:39:305 920 153c Agent * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1323
2014-02-03 08:33:39:352 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:352 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:352 920 153c Agent * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03 08:33:39:352 920 153c Agent *********
2014-02-03 08:33:39:352 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:352 920 153c Agent *************
2014-02-03 08:33:39:352 920 153c Agent *************
2014-02-03 08:33:39:352 920 153c Agent ** START ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:352 920 153c Agent *********
2014-02-03 08:33:39:352 920 153c Agent * Online = No; Ignore download priority = No
2014-02-03 08:33:39:352 920 153c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation'
or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-02-03 08:33:39:352 920 153c Agent * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-02-03 08:33:39:352 920 153c Agent * Search Scope = {Current User}
2014-02-03 08:33:39:352 920 153c Agent * Caller SID for Applicability: S-1-5-21-4260610346-2664610402-3334891387-1282
2014-02-03 08:33:39:383 920 153c Agent * Added update {E8B477DF-479E-4BCA-B8F8-2D987A509009}.2 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {BB85CCA0-88DC-4DA7-8E81-B7F7E5E73B81}.100 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {18DEF1D9-4513-467E-9D7E-E1772855BB9E}.100 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {971D9BE4-5145-4DB5-962C-CEE2EE3A2842}.3 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {CCB380C9-29F5-4305-96DD-86DE2D00438B}.2 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {455BDD67-9ED0-4DE7-94F1-3480EA942414}.12 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {ADFBFCE0-FFD4-4826-B9CF-50AE8182E3C5}.2 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {BFA8C8B8-EEF7-4A82-A36C-8F760F792430}.3 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {3F05DE38-92BC-44B6-B06B-5217E5CF12CA}.1 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {36BEF0D5-80ED-4942-8457-6F9C88546E06}.1 to search result
2014-02-03 08:33:39:383 920 153c Agent * Added update {A292CD86-AB4E-4388-8C7B-CFB392EDE6AC}.1 to search result
2014-02-03 08:33:39:383 920 153c Agent * Found 11 updates and 30 categories in search; evaluated appl. rules of 60 out of 94 deployed entities
2014-02-03 08:33:39:383 920 153c Agent *********
2014-02-03 08:33:39:383 920 153c Agent ** END ** Agent: Finding updates [CallerId = Windows Update Command Line]
2014-02-03 08:33:39:383 920 153c Agent *************
2014-02-03 08:33:39:383 920 1990 AU >>## RESUMED ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-02-03 08:33:39:383 920 1990 AU # 12 updates detected
2014-02-03 08:33:39:383 920 1990 AU #########
2014-02-03 08:33:39:383 920 1990 AU ## END ## AU: Search for updates [CallId = {66AF0139-896D-4607-8660-B66D2B58EA26} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-02-03 08:33:39:383 920 1990 AU #############
2014-02-03 08:33:39:383 920 1990 AU All AU searches complete.
2014-02-03 08:33:39:383 920 1990 AU AU setting next detection timeout to 2014-02-03 10:18:51
2014-02-03 08:33:44:211 920 1a64 Report CWERReporter finishing event handling. (00000000)
2014-02-03 08:41:39:472 920 1a64 EP Got WSUS Client/Server URL: "http://elias:8530/ClientWebService/client.asmx"
2014-02-03 08:41:39:472 920 1a64 PT WARNING: Cached cookie has expired or new PID is available
2014-02-03 08:41:39:472 920 1a64 EP Got WSUS SimpleTargeting URL: "http://elias:8530"
2014-02-03 08:41:39:472 920 1a64 PT Initializing simple targeting cookie, clientId = c5e26849-287b-4b96-ba5d-1489d6fad2f2, target group = , DNS name = dt-ikt-tor.framnes.lan
2014-02-03 08:41:39:472 920 1a64 PT Server URL = http://elias:8530/SimpleAuthWebService/SimpleAuth.asmx
2014-02-03 08:41:39:519 920 1a64 EP Got WSUS Reporting URL: "http://elias:8530/ReportingWebService/ReportingWebService.asmx"
2014-02-03 08:41:39:519 920 1a64 Report Uploading 2 events using cached cookie, reporting URL = http://elias:8530/ReportingWebService/ReportingWebService.asmx
2014-02-03 08:41:39:566 920 1a64 Report Reporter successfully uploaded 2 events.
2014-02-03 08:42:13:212 920 178c Report WARNING: CSerializationHelper:: InitSerialize failed : 0x80070002
2014-02-03 08:43:40:450 920 178c AU ########### AU: Uninitializing Automatic Updates ###########
2014-02-03 08:43:40:450 920 178c WuTask Uninit WU Task Manager
2014-02-03 08:43:40:513 920 178c Service *********
2014-02-03 08:43:40:513 920 178c Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-02-03 08:43:40:513 920 178c Service *************Today I opened Control Panel / Windows Updates and first did a check for new updates (from the WSUS server). Nothing was found and it reported Windows is Updated. Then I clicked the link Check for updates from Microsoft via internet, and
it found around 24 updates.
This is confirmation of the point that I made in the previous post. The updates are *NEEDED* by this system, but the updates were not *AVAILABLE* from the assigned WSUS Server. You were able to get them from Windows Update, but that does not fix your continuing
issue with the WSUS Server.
but it still reported the original 108 Needed updates.
Exactly. As previously noted, the client is functioning perfectly. The problem is NOT with the client; the problem is with the WSUS Server. The updates that this client needed were not AVAILABLE to be downloaded from the WSUS server.
Why this is the case requires further investigation on your part, but is either because the updates are not properly approved, or the update FILES are not yet downloaded from Microsoft to the WSUS server.
It appears that the wsus server doesn't get any information back from the client despite that it displays new Last contact and Last Status report timestamps.
This conclusion is incorrect. The WSUS Server got every bit of information available from the client -- you've confirmed this by the number of updates reported as "Needed" by the Windows Update Agent to the WSUS Server.
I assumed that the log would display if the updates were downloaded or not.
It will log when the updates are actually downloaded. If there's no log entries for updates being downloaded, then they're not being downloaded. If the logfile says "Found 0 updates", then that means exactly what it says: It couldn't find any approved/available
updates to download.
In your case it "Found 11 updates", but now it will be impossible to diagnose that fault, because you went and got them from Windows Update.
All Win8 versions are checked in the WSUS server's Product list so the updates should at least have been downloaded to the server.
This is why understanding the infrastructure is so critical. Your conclusion is invalid based on the premise given, and you may be using improper terminology which only confuses the rest of us as well.
First, selecting updates for synchronization only gets the update metadata (i.e. the detection logic) downloaded to the WSUS database.
The Second Step in this process is to Approve those updates for one or more WSUS Target Groups that contain the appropriate client systems. Following the approval of an update, the WSUS Server downloads the INSTALLATION FILE for that update.
Once the WUAgent sees an approved update and the installation file is available, then the WUAgent will download the file and schedule the update for installation.
Most of the post I read about my problem is about upgrading a 2008 WSUS server to support Win8 / Server 12 clients. When I try to run this update on my Server 12 WSUS it refuses to run (probably because it is for Server 2008).
Yeah.. totally different issue in those posts than what you're describing here.
What should I do to try to track down the problem?
Well.... now that it's 11 days since the logfile was posted, and you've already updated that system, we'll first need to find another system exhibiting the same issue.
Then I'll need to ask a number of questions to properly understand the environment, as well as what you have or have not done.
Then, from there, we can attempt to figure out why your Windows 8 client apparently sees some updates as approved/available but is still not downloading them. We do not yet have sufficient information to even speculate on a possible cause -- there are several.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
Problem with VPN Client and network access
We are running VPN client 4.0.1 on our laptops, and there are a number of users who are getting documents they are using on the internal network (off VPN) corrupted. The initial cause seemed to be the stateful firewall, but I have that turned off, and we are still getting it.
It only seems to be on the machines with VPN client installed, and it is only happening when the user is working on a file direct from the network drive. They are not connecting via the VPN client when the problem occurs.
any suggestions?
William.Did you get any joy with this ? We seem to be having the same issue.
Thanks
Maybe you are looking for
-
How come the v$backup_piece.completion_time is earlier than DB creation time? SQL > select * from v$version where rownum < 2; BANNER Oracle Database 10g Release 10.2.0.4.0 - Production SQL > select to_CHAR(completion_Time,'MON-DD-YYYY') from 2 (
-
I am having trouble setting up the wireless connection on a hp deskjet 3520. I upgraded to os x.10.9 recently. I have updated to the most recent HP software update which is version 2.16.1. However, according to the os x: printer and scanner softw
-
Hi, I have a new iMac (with 3TB fusion drive) arriving soon. For my previous iMac (2010), I used a 2TB external HD (connected via FW800) to store and access all my content. This was because my internal HD was only a 256GB SSD, and used it solely fo
-
How to get active plan version dynamically
Hi all, I am making some HR reports in which I am pulling up position long text from hrp1001 by giving condition - where plavr = '01' . Now if the active plan version is not 01, my condition becomes vague. Please let me know how to determine the acti
-
How to change to working with referenced images but keep library on laptop
Hi, So, my iPhoto library is getting too big - I'd like to be able to have the images stored on an external drive and refer to them from within iPhoto, whilst keeping the iPhoto Library itself on the laptop. I know exactly how to do this from scratch