Multiple client version

Hello,
I have quite simple problem. I have two database servers (9i and 10g). If I install on my PC (windows XP) client for 10g, I could connect only to 10g server. If I have install both (9i and 10g) clients, I could connect to both servers. My question is, how sqlplus or other programs finds out which client to use?
SASA

Each executable has a dependent Oracle Core DLL, i.e. CORE35.DLL, CORE40.DLL, oracore8.dll etc., linked to it.
When you run an executable, PLUS33.EXE for example, your system searches the PATH for the dependent Oracle CORE DLL.
You can identify the DLL by using Dependency Walker (DEPENDS.EXT) from the NT Resource Kit or SDK.
The GetModuleFileName() funtion returns something like "C:\ORA805\BIN\xxxx.DLL" .
It strips the string from the "BIN\xxxx.DLL" and retrieves the ORACLE_HOME (eg: C:\ORA805).
With the string returned above, Oracle then checks the %ORACLE_HOME%\bin\ORACLE.KEY file which includes the Oracle Hive
for all of the Oracle products installed in the Oracle_HOME.
For example: If the ORACKLE.KEY file has the string "SOFTWARE/Oracle/HOME1"
the hive is HKEY_LOCAL_MACHINE/Software/Oracle/HOME1.
If the oracle.key file is not present, then the Default Oracle Home is used.
This is the case for Non-Multiple Oracle Home products.

Similar Messages

  • Multiple client version problem

    Is it possible to have 7.3.4 and 8.1.6/7 clients operating simultaneously on the same workstation?
    Chris Hoggarth

    Yes, but install first 7.3.4 and then 8.1.7

  • When trying to load multiple language versions of an ibook onto my iPad only the first document loads

    We have a sales tool that we have created for one of our clients in iBooks Author. They need the iBook creating in various languages.
    We need to be able to supply the multiple versions of the same document (in the different languages) to our client and they need to be able to install the different versions onto their iPads. And they want the options of having multiple language versions on the same iPads.
    We have already created two language versions of the document (a US English and an International English version).
    The two documents have different file names, (although they are based on the same document). We have just changed the spelling of some words accordingly. (And we will be producing other language variants based on the master file).
    We export the two documents via the File > Export > iBooks option. Then we are using Dropbox to upload the two files. The files are then accessed via the Dropbox App on the iPad.
    We can download the first document (International English) onto the iPad and view it as normal, but when we try and then download the other document (US English) it downloads in the Dropbox App, but when you click on view in iBooks it opens the first (International English) document into iBooks.
    You can only appear to have one version of the document installed at any one time. If you delete the first one you can then load the second one fine, but not both at the same time. If the file names are different it must be getting the identity of the document from somewhere else.
    This has only started happening since using iBooks Author 2.
    Can anyone offer any suggestions please. I've tried changing the version number in the option on export, but this doesn't seem to affect the result.
    Thanks in advance for any suggestions
    John

    Further to my earlier post we have now completed a test by saving our original document as a template, then creating a new document from the template, making necessary changes and saving as a new file. We can now upload the two separate versions to our iPad.
    You cannot "duplicate" the file in any way, either by the File > Duplicate method from within iBooks Author or by simply Duplicating the original .iba file in the Finder, as this will cause the problem outlined above. By Duplicating you are obviously also duplicating this "hidden metadata" which is stored somewhere within the file which iBooks on the iPad is using to identify the documents. So unless Apple update the software to allow us to change that metadata we are stuck to using the Templates route. (Didn't have this problem on the last version of iBooks Author).
    This works for what we are trying to do, which is create different language variants of the same book.
    Working from Templates is probably the correct way to do it anyway, but might not necessarily be right for everyone.
    Working in iBooks Author is proving to be a rather testing experience. You certainly need the patience of a Saint. Not sure it's of the standard we expect from Apple, but then I guess, as they are giving it away "free", they think they don't have to offer any support for it.
    I think I would prefer to pay a fee for it and have a support route from Apple, rather than rely on a community of equally frustrated users who are all playing guinea pig and simply sharing their workarounds for a half baked product.
    Good luck to everyone!!! 

  • Can JWS be used as a multiple Java version management tool?

    WinNT4 WKS with JRE 1.3.1 - 1.4.2 loaded on it using IExplorer or Netscape.
    We don't have a need for the JWS download features because our clients (and their applications) remain static for the most part. However, we do require multiple JRE version support because our customers have written class/objet "fixes" (mostly for text rendering) and these fixes break if you try and run the application on a different version of Java from which it was written. Basically, we can't have a default JRE on each machine and hope that it will work with all customer applications. So we will load all necessary Java components on our workstations (in this case JRE versions 1.3.1 - 1.4.2). I know that browsers can be forced to load with a specific Plug-in version (providing it exists on the machine) through Object & Embed tags in the HTML and that standalone apps can be directed to the correct Java directory path. My question is, can JWS automatically identify the Java requirements of our customers applications and act simply as a multi-version management tool to provide the right JRE/Plug-In for either standalone or browser applications? Keeping in mind that all the JREs will be loaded on the workstions and it won't need to download any components from some site.
    I've noticed that JWS identifies all JREs loaded on a machine in the Java tab so I'm wondering if it can "switch" the environment as needed for each application.
    Does anyone know if I can use JWS in the scenario I described above? Thanks!

    JWS can manage the multiple JREs installed if you run the application through a .jnlp. This can not "switch" the default JRE. It runs the application specified in the .jnlp using the requested version specified in the .jnlp.
    JWS does not apply to applets. You should use the object tags as you mentioned below.
    ...can JWS automatically identify the Java requirements of our customers applications
    No. You must determine this and setup the .jnlp appropriately.

  • What are the possible approches for hosting a product(custom SP application) for multiple clients on a single SharePoint farm?

    We have a product which is a custom application based on SharePoint Foundation 2010. Right now, for each of our client we create a dedicated server and host the application in the standalone deployment. Now, the requirement is to host multiple clients in a
    farm deployment.
    Challenges are: 1. The product has same name for the wsp that is deployed on different client servers as of now. How to distinguish for different clients on same farm
    Currently the product specific css and jquery is in 14 hive. These files will be of difefrent versions for different client. How to segregate that?
    How many web applications is recommend to be created in a single SPF 2010 farm? What are the challenges?
    There are a couple of DBs created in SQL for the application. What is the best way to separate those for the client?
    Essentially its the same product but with different versions for each client that we want to deploy in a single farm. What is the best practice to tackle this?

    For the most part, these are not SharePoint questions per se, but product-specific questions you'd better ask the vendor about. To get in some more detail:
    1. It totally depends on the scope of the solution. If its global, then you're out of luck and any changes you make affect all instances that use it. Better ask the vendor about it.
    2. Not that many, let's say < 10, assuming you're web applications have separate application pools. Check out  http://technet.microsoft.com/en-us/library/cc262787(v=office.14).aspx#WebApplication for
    more info.
    3. This is very application specific and really should be answered by the vendor. Not related to SharePoint at all.
    4. Again, really depends on the product so better ask the vendor.
    Good luck!
    Kind regards,
    Margriet Bruggeman
    Lois & Clark IT Services
    web site: http://www.loisandclark.eu
    blog: http://www.sharepointdragons.com

  • Problem using multiple Client Certificates

    Hi folks, I had (mistakenly) posted an earlier version of this question to the crypto forum.
    My problem is that I have multiple client certs in my keystore, but only one is being used as the selected certificate for client authentication for all connection�s. So, one connection works fine, the rest fail because the server doesn�t like the client cert being presented.
    I have been trying to get the JSSE to select the proper client certificate by making use of the chooseClientAlias method. (init the SSL context with a custom key manager that extends X509ExtendedKeyManager and implements the inherited abstract method X509KeyManager.chooseClientAlias(String[], Principal[], Socket))
    But, still no luck.. the JSSE is not calling in to the my version of chooseClientAlias, and it just keeps presenting the same client certificate.
    No clue why, any thoughts on how to get the JSSE to call my version of chooseClientAlias?
    Thanks!
    SSLContext sslContext = SSLContext.getInstance("TLS");
    sslContext.init(createCustomKeyManagers(Keystore, KeystorePassword),
                createCustomTrustManagers(Keystore, KeystorePassword),null);
    SSLSocketFactory factory = sslContext.getSocketFactory();
    URL url = new URL(urlString);
    URLConnection conn = url.openConnection();
    urlConn = (HttpsURLConnection) conn;
    urlConn.setSSLSocketFactory(factory);
    BufferedReader rd = new BufferedReader(new InputStreamReader(urlConn.getInputStream()));
    String line;
    while ((line = rd.readLine()) != null) {
         System.out.println(line);  }
    public class CustomKeyManager extends X509ExtendedKeyManager
        private X509ExtendedKeyManager defaultKeyManager;
        private Properties serverMap;
        public String chooseClientAlias(String[] keyType, Principal[] issuers, Socket socket)
            SocketAddress socketAddress = socket.getRemoteSocketAddress();
            String hostName = ((InetSocketAddress)socketAddress).getHostName().toUpperCase();
            String alias = null;
            if(serverMap.containsKey(hostName)){
                alias = serverMap.getProperty(hostName.toUpperCase());
                if(alias != null && alias.length() ==0){
                    alias = null; }
            else {
                alias = defaultKeyManager.chooseClientAlias(keyType, issuers, socket);
            return alias;
    .

    Topic was correctly answered by ejp in the crypto forum..
    namely: javax.net.ssl.X509KeyManager.chooseClientAlias() is called if there was an incoming CertificateRequest, according to the JSSE source code. If there's an SSLEngine it calls javax.net.ssl.X509ExtendedKeyManager.chooseEngineClientAlias() instead.*
    You can create your own SSLContext with your own X509KeyManager, get its socketFactory, and set that as the socket factory for HttpsURLConnection.*
    Edited by: wick123 on Mar 5, 2008 10:26 AM

  • TES 6.1.0.x Multiple Client Managers

    Hello:
    I am trying to find out if there is anyone else using multiple client managers on a load balancer and if we could have a discussion regarding such a setup. We have this in our envrionment and it does work, however sometimes I see oddities with in the client - even if I log directly into one of my client managers, by-passing the load balancer completely.
    Looking forward to hearing from anyone with a similar setup.
    Regards,
    Ceceil Rufo

    We haven't done a formal load testing yet.  But we have conducted training with 10 - 15 users and would experience performance sometimes people just getting kicked out.  At the time though we were still finagling with server configuration settings for threads, cache and java heap.  During training too what seemed to impact performance more was the browser and version, and workstation memory.  For a web app, TES 6.1 uses a LOT of memory so there were some suggested tweaks that had to be done on some machines.  We have more consistent performance on IE 9 (than IE 10), and Firefox 18+ was faster.
    I have installed Jconsole and am planning to conduct load testing sometime this month where i could monitor server resource from Jconsole to get an idea where bog down really is. 
    There is a TES 6.1 presentation doc that sort of outlines approx sizing based on concurrent users - we fit in the 10 -20 concurrent users given that our CM has 12GB RAM (allocated 10GB to TES) and 4 core.  So hopefully with two CMs we can have upto 40.  We are open to adding more mem if needed.  So what tools do you use for Load testing?  Also I wonder if it was possible to automate Load Testing like with Jmeter or something.  For now we just plan on getting 20 users together to perform set functions at the same time and measure that with 1 CM up and me looking in Jconsole.
    I also notice the multiple connections, even see myself twice even when I only have 1 browser session.  Not having had a chance to dig to deeply i was chalking it up to maybe that I didn't exit properly last time so that it has to wait 30 minuts to totally clear me (with time to live setting) out but haven't really tested formally.  I will see about adding that to my testing.  I would also think it would impact system in that some folks may cause the number of concurrent connections allowed to be exceeded if you have too many of these lying around but since they are not doing anything perhaps not performance as much?  It will be good to confirm though that a single web session really only takes 1 connection and won't potentially spawn another somehow.
    Our implementation being highly distributed with workgroups having full autonomy over their jobs - means every team needs to have access to Transporter.  We have over 15 teams. Which is scary since that also takes resources from the CM -  and also from a management and training perspective.  We also haven't load tested the Transporter server interms of number of concurrent users that can be running Transporter on it at one time.  Nor have any clear idea yet how we'll manage the mapping files.  But we are also opening up Transporter to be installed by teams on their team server (only that they have to patch themselves) - I really wonder if we should just restrict Transporter access to just the servers our team manage and no one else can install it anywhere else.

  • Client version vs Database version

    Is it possible to install Oracle8i, and Oracle9i databases in multiple (separate) Oracle homes on the same computers and have Oracle8i, and Oracle9i clients connecting to any or all of the databases.
    What is the relation existing between my client version and the database version?

    It's possible to have an arbitrary number of Oracle homes with an arbitrary number of different client & database versions on a single machine.
    If you install the Oracle database, the same version client will automatically be installed in that Oracle home. If you install an 8.1.7 Oracle database in OraHome817, the 8.1.7 Oracle client will automatically be installed in OraHome817.
    It's also possible to have a client-only install, i.e. you could install the 8.1.6 Oracle client to OraHome816 without having an 8.1.6 database installed.
    Connectivity should be possible (assuming appropriate tnsnames.ora files, etc) between clients and databases in any of these homes. The only limitation you have any chance of hitting is that communication between 9.2 and 7.3.4 clients & databases isn't allowed. Any 8.0+ client can communicate with any 8.0+ database.
    Justin

  • RAS Server allowing multiple clients in and telnet redirection to correct reciever.

    Product being used:
    IOS (tm) 3700 Software (C3725-ADVIPSERVICESK9-M), Version 12.3(26), RELEASE SOFTWARE (fc2)
    cisco 3725 (R7000) processor (revision 0.1) with 118784K/12288K bytes of memory.
    R7000 CPU at 240MHz, Implementation 39, Rev 3.3, 256KB L2 Cache
    MICA-6DM Firmware: CP ver 2940 - 7/24/2002, SP ver 2940 - 7/24/2002.
    Bridging software.
    X.25 software, Version 3.0.0.
    Primary Rate ISDN software, Version 1.1.
    2 FastEthernet/IEEE 802.3 interface(s)
    24 Serial network interface(s)
    24 terminal line(s)
    1 Channelized T1/PRI port(s)
    In combination with a server running:
    tac_plus version F4.0.3.alpha.v9 (Extended Tac_plus)
    • The goal is create a RAS Server to allow multiple clients to call in and separate them via DNIS.
    Then specify an auto-command to send the traffic to the correct receiver of that call.
    We are not stuck on doing this with tacacs if there is a more efficient way of doing this.
    The thought was to only send the authorization to tacacs to allow for the dnis map to point the traffic to the correct receiver.
    aaa authentication login DIALIN none
    aaa authorization exec DIALIN none
    • If we set aaa authentication login DIALIN none it works without any issues but does not go to the tacacs server and therefore does not allow us to use the dnis map commands.
    aaa authentication login DIALIN group AAA-mydial
    aaa authorization exec DIALIN none
    • If we set aaa authentication login DIALIN group AAA-mydial using the aaa group server tacacs+ AAA-mydial it goes out to the tacacs server as expected but then it requires a login ID at least in order to get into a session.
    aaa authentication login DIALIN none
    aaa authorization exec DIALIN group AAA-mydial
    • When we change the aaa authorization exec DIALIN group AAA-mydial it fails and does not even send the information out to the tacacs server.
    aaa authentication login DIALIN “see above for options “
    aaa authorization exec DIALIN “see above for options”
    aaa new-model
    aaa group server tacacs+ AAA-2035554677
    server 172.16.0.109
    aaa group server tacacs+ AAA-2035554570
    server 172.16.0.109
    aaa group server tacacs+ AAA-2035554571
    server 172.16.0.109
    aaa group server tacacs+ AAA-mydial
    server 172.16.0.109
    aaa authentication login DIALIN none
    aaa accounting exec default start-stop group AAA-2035554570
    aaa dnis map enable
    aaa dnis map 2035554677 authorization network group AAA-2035554677
    aaa dnis map 2035554677 accounting network start-stop group AAA-2035554677
    aaa dnis map 2035554570 authentication login group AAA-2035554570
    aaa dnis map 2035554570 authorization network group AAA-2035554570
    aaa dnis map 2035554570 accounting network start-stop group AAA-203554570
    aaa dnis map 2035554571 authorization network group AAA-2035554571
    aaa dnis map 2035554571 accounting network start-stop group AAA-2035554571
    aaa session-id common
    ip subnet-zero
    ip cef
    line con 0
    line 65 88
    no motd-banner
    no exec-banner
    privilege level 15
    no vacant-message
    login authentication DIALIN
    modem Dialin
    transport preferred none
    transport output telnet
    escape-character NONE
    telnet transparent
    line aux 0
    line vty 0
    exec-timeout 0 0
    password cisco
    line vty 1
    exec-timeout 0 0
    transport preferred telnet
    transport input all

    /* Style Definitions */
    table.MsoNormalTable
    {mso-style-name:"Table Normal";
    mso-tstyle-rowband-size:0;
    mso-tstyle-colband-size:0;
    mso-style-noshow:yes;
    mso-style-priority:99;
    mso-style-qformat:yes;
    mso-style-parent:"";
    mso-padding-alt:0in 5.4pt 0in 5.4pt;
    mso-para-margin:0in;
    mso-para-margin-bottom:.0001pt;
    mso-pagination:widow-orphan;
    font-size:11.0pt;
    font-family:"Calibri","sans-serif";
    mso-ascii-font-family:Calibri;
    mso-ascii-theme-font:minor-latin;
    mso-fareast-font-family:"Times New Roman";
    mso-fareast-theme-font:minor-fareast;
    mso-hansi-font-family:Calibri;
    mso-hansi-theme-font:minor-latin;}
    NOTHING LIKE ANSWERING YOUR OWN POST:::
    --Well after looking around I found the following on a forum which seems to have gotten us to our destination but uses local authentication to direct the DNIS numbers to the correct receiving system.  Just need to give things a final polishing to make the configuration as clean as possible.
    hostname Router
    boot-start-marker
    boot-end-marker
    logging buffered 65536 debugging
    enable password cisco
    clock timezone EDT -5
    clock summer-time EDT recurring
    aaa new-model
    aaa user profile TEST
    aaa group server tacacs+ AAA-mydial
    server 172.16.0.109
    !!!!!  Below defines the AAA-mydial group you are sending the accounting information to.
    aaa group server radius AAA-myradius
    server 172.16.0.109 auth-port 1645 acct-port 1646
    !!!!!  Below you are using the DNISTEST local group for authentication and authorization.
    aaa authentication banner ^C^C
    aaa authentication login DNISTEST local
    aaa authorization exec DNISTEST local
    aaa accounting update newinfo
    aaa accounting connection DNISTEST start-stop group tacacs+ group AAA-mydial
    aaa session-id common
    ip subnet-zero
    ip cef
    ip audit po max-events 100
    isdn switch-type primary-ni
    isdn voice-call-failure 0
    isdn logging
    !!!!!  Below you are directing which DNIS number goes to which receiving host.
    username cisco-kid password 0 cisco
    username DNIS##1212 nopassword dnis
    username DNIS##1212 autocommand telnet 172.16.0.5 22 /stream /quiet
    username DNIS##4677 nopassword dnis
    username DNIS##4677 autocommand telnet 172.16.0.6 22 /stream /quiet
    username DNIS##4570 nopassword dnis
    username DNIS##4570 autocommand telnet 172.16.0.7 22 /stream /quiet
    controller T1 1/0
    framing esf
    linecode b8zs
    pri-group timeslots 1-24
    interface FastEthernet0/0
    ip address 172.16.0.35 255.255.255.0
    speed auto
    full-duplex
    interface FastEthernet0/1
    no ip address
    shutdown
    duplex auto
    speed auto
    interface Serial1/0:23
    no ip address
    encapsulation hdlc
    isdn switch-type primary-ni
    isdn incoming-voice modem
    no cdp enable
    interface Group-Async0
    no ip address
    encapsulation slip
    dialer in-band
    dialer-group 1
    async mode interactive
    group-range 65 88
    interface Dialer0
    no ip address
    dialer in-band
    dialer idle-timeout 3600
    dialer-group 1
    ip classless
    ip route 0.0.0.0 0.0.0.0 172.16.0.254
    no ip http server
    no ip http secure-server
    ip tacacs source-interface FastEthernet0/0
    dialer-list 1 protocol ip permit
    !!!!!  Below you are further defining the tacacs server and the encryption key to be used.
    tacacs-server host 172.16.0.109 key cisco
    no tacacs-server directed-request
    radius-server host 172.16.0.109 auth-port 1645 acct-port 1646 key ras-secret123
    line con 0
    !!!!!  Below you are directing all calls to go to DNISTEST for authentication, authorization, & accounting.
    !!!!!  Then we are stripping all prompting so that the connection is completely clean.
    !!!!!  The only issue was that the aaa banner was still there which is why there is a
    !!!!!  “aaa authentication  banner ^C^C” above in the aaa section.
    line 65 88
    no motd-banner
    no exec-banner
    privilege level 15
    authorization exec DNISTEST
    accounting connection DNISTEST
    no vacant-message
    login authentication DNISTEST
    modem Dialin
    transport preferred none
    transport output telnet
    escape-character NONE
    telnet transparent
    line aux 0
    line vty 0 4
    exec-timeout 0 0
    password cisco
    transport preferred telnet
    transport input all
    transport output all
    escape-character NONE
    telnet transparent
    end
    tacacs+ config just needs to have an accounting log file defined and all output will be logged there:
    Here is my tac_plus.cfg file:
    ===========================================================
    key = "cisco"
    accounting file = /var/log/tac_plus-f404.log
    -----------------------  the info below this line is irrelevant  ---------------------------
    ---  Just from me trying to use tacacs for the authentication & authroization----
    user = default {
            login = nopassword
            service = exec {
                   autocmd = "telnet 172.16.0.5 22 /stream /quiet"
    user = Router {
            login = nopassword
            member = dialup
    group = dialup {
            default service = permit
            expires = "Apr 1 2010"
            service = exec {
                    idletime = 15
                    autocmd = "telnet 172.16.0.5 22 /stream /quiet"
            cmd = disconnect {
                    permit .*
    user = test {
            name = "Dial"
            login = nopassword
            member = dialup

  • SCCM 2012 R2 site server client installation error: The client version 5.00.7958.1000 does not match the MP version 5.00.7804.1000.

    Hello,
    When I try to install the client on the site server itself it gives me this error message and fails the ccmsetup. I only have this on the site server. Clients to other servers and computers are pushed fine. If I check the version of the MP it says 5.00.7958.1000
    in ADSI. I removed the MP object in CN=System, CN=System Management. Waited for it to be regenerated automatically by SCCM but the installation doesn't work still.
    I tried to install with several methods including directly from ccmsetup.exe in ccmsetup folder, pushing by sccm itself, running from commandline, ...
    I run SCCM 2012 R2 on Windows Server 2008 R2 and the database on SQL 2008 on Server 2008 R2
    Below you find the ccmsetup.log:
    <![LOG[==========[ ccmsetup started in process 5072 ]==========]LOG]!><time="07:29:25.392-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="7532" file="ccmsetup.cpp:9437">
    <![LOG[Running on platform X64]LOG]!><time="07:29:25.393-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="7532" file="util.cpp:1837">
    <![LOG[Updated security on object C:\Windows\ccmsetup\cache\.]LOG]!><time="07:29:25.394-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="7532" file="ccmsetup.cpp:9281">
    <![LOG[Launch from folder C:\Windows\ccmsetup\]LOG]!><time="07:29:25.394-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="7532" file="ccmsetup.cpp:721">
    <![LOG[CcmSetup version: 5.0.7958.1000]LOG]!><time="07:29:25.395-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="7532" file="ccmsetup.cpp:727">
    <![LOG[In ServiceMain]LOG]!><time="07:29:25.397-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="ccmsetup.cpp:3365">
    <![LOG[Running on 'Microsoft Windows Server 2008 R2 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 274. Product Type = 18]LOG]!><time="07:29:25.490-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="util.cpp:1919">
    <![LOG[Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="07:29:25.491-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:3590">
    <![LOG[Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.]LOG]!><time="07:29:25.491-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:3775">
    <![LOG[Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="07:29:25.491-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:3776">
    <![LOG[SslState value: 224]LOG]!><time="07:29:25.499-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="ccmsetup.cpp:4425">
    <![LOG[CCMHTTPPORT: 80]LOG]!><time="07:29:25.511-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:8617">
    <![LOG[CCMHTTPSPORT: 443]LOG]!><time="07:29:25.511-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:8632">
    <![LOG[CCMHTTPSSTATE: 224]LOG]!><time="07:29:25.511-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:8650">
    <![LOG[CCMHTTPSCERTNAME: ]LOG]!><time="07:29:25.511-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:8668">
    <![LOG[FSP: SCCMSRV-02]LOG]!><time="07:29:25.511-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:8720">
    <![LOG[CCMFIRSTCERT: 1]LOG]!><time="07:29:25.511-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:8778">
    <![LOG[Config file: C:\Windows\ccmsetup\MobileClientUnicode.tcf]LOG]!><time="07:29:25.513-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:4539">
    <![LOG[Retry time: 10 minute(s)]LOG]!><time="07:29:25.513-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:4540">
    <![LOG[MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log]LOG]!><time="07:29:25.513-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:4541">
    <![LOG[MSI properties: INSTALL="ALL" SMSSITECODE="ZAV" FSP="SCCMSRV-02" DISABLESITEOPT="TRUE" SMSCACHEDIR="CACHE" SMSCACHEFLAGS="MAXDRIVE" SMSCACHESIZE="20000" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"]LOG]!><time="07:29:25.514-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:4542">
    <![LOG[Source List:]LOG]!><time="07:29:25.514-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:4550">
    <![LOG[ \\SCCMSRV-02.snba.be\SMSClient]LOG]!><time="07:29:25.514-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:4557">
    <![LOG[ \\SCCMSRV-02.SNBA.BE\SMSClient]LOG]!><time="07:29:25.514-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:4566">
    <![LOG[MPs:]LOG]!><time="07:29:25.514-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:4569">
    <![LOG[ SCCMSRV-02.snba.be]LOG]!><time="07:29:25.514-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:4584">
    <![LOG[No version of the client is currently detected.]LOG]!><time="07:29:25.520-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:2748">
    <![LOG[Task 'Configuration Manager Client Retry Task' does not exist]LOG]!><time="07:29:25.525-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="wintask.cpp:634">
    <![LOG[Updated security on object C:\Windows\ccmsetup\.]LOG]!><time="07:29:25.529-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="ccmsetup.cpp:9281">
    <![LOG[Sending Fallback Status Point message to 'SCCMSRV-02', STATEID='100'.]LOG]!><time="07:29:25.530-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:9756">
    <![LOG[Failed to get client version for sending messages to FSP. Error 0x80041010]LOG]!><time="07:29:25.534-120" date="04-17-2014" component="ccmsetup" context="" type="2" thread="2724" file="ccmsetup.cpp:9838">
    <![LOG[Params to send FSP message '5.0.7958.1000 Deployment ']LOG]!><time="07:29:25.535-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="ccmsetup.cpp:9887">
    <![LOG[State message with TopicType 800 and TopicId {C6441082-A993-4410-9F89-D4CCB6624ED0} has been sent to the FSP]LOG]!><time="07:29:25.676-120" date="04-17-2014" component="FSPStateMessage" context="" type="1" thread="2724" file="fsputillib.cpp:752">
    <![LOG[Running as user "SYSTEM"]LOG]!><time="07:29:25.693-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:1995">
    <![LOG[Detected 20167 MB free disk space on system drive.]LOG]!><time="07:29:25.693-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="util.cpp:628">
    <![LOG[Checking Write Filter Status.]LOG]!><time="07:29:25.694-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:2024">
    <![LOG[This is not a supported write filter device. We are not in a write filter maintenance mode.]LOG]!><time="07:29:25.694-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:2051">
    <![LOG[Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=ZAV))']LOG]!><time="07:29:25.716-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="lsad.cpp:656">
    <![LOG[OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202EF308201D7A00302010202102F8856AD510DC3AB4F4908160FC3185E300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303830373134323233325A180F32313133303731353134323233325A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100DDAAEB161F4ACB759E0E56C6F784F3BEDD4DA0303B40657298A41D7F9714E112CC80272A238E605DADD2D409658211D40590BD92D0DFE4E50E8F5AF482BF747E8D00636C41F7F939EF53FA6581B173A15BE25BC24DB9E3620D78612650415DF862AFA17F75128A601A011358B27CFB9989EEBD128485F167A5E378A0A3A106DEE3DD6CE7C5804B0BA3724C4455D2EA8D646B47D989AFC7D2BACC6AD0E62FA0D6B338C2CD3B5879B4794F5D29A89ADC93489E43237E4C3BA30F645F4E4FE0E3B562ABCFC73F52C33B7D179DD10888D2EB00F6F4E121009F1CB80BCF4FA0F5CAA5BA167AE7DC0A767BC3C9031A95A42C791B100D7F15144B4FE5AC104C2BEB3EAB0203010001A3373035301D0603551D110416301482125343434D5352562D30322E736E62612E626530140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B050003820101004802B9C3A3A9EA0DB5C6624F9152C60CA38F2857691234B5FE13DDED32DB3BADF4C847F5EA097DB9918537F40A94D56A06364775E62B9F75C51189BC510EE8F2848B264C41A4E941C9CD996BEF70B9F72345BEB05F39B87BF88B3A461333BD61CD50E6E16B15709D58B78A7B385E914DF2C7949AA5BEEFC8199D69CD6DCA312DBCFE64AC43D6F13B80FED4967447532E1A65F5E0588CA7246B417DD8530E28E3DAD170F71C00B6D79645EC49332CD9F8815DB65AAB441E6C41F72C37F432E5B5E23065B6D308486C398F340B1FF2361F3C342A50EA9A02D01138BACEDCFA0E7FAA681C1FC6157797171A0593EA0ACE0BD7BBBEB26E2F34FFD461210C76669FE1</SiteSigningCert></SecurityConfiguration><RootSiteCode>ZAV</RootSiteCode><CCM> <CommandLine>SMSSITECODE=ZAV FSP=SCCMSRV-02 DISABLESITEOPT=True SMSCACHEDIR=Cache SMSCACHEFLAGS=MAXDRIVE SMSCACHESIZE=20000</CommandLine> </CCM><FSP> <FSPServer>SCCMSRV-02.snba.be</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="snba.be" /><Forest Value="snba.be" /></ClientOperationalSettings>']LOG]!><time="07:29:26.401-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="lsadcache.cpp:236">
    <![LOG[HTTP is selected for Client. The current state is 0.]LOG]!><time="07:29:26.403-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmutillib.cpp:420">
    <![LOG[The MP name retrieved is 'SCCMSRV-02.snba.be' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>']LOG]!><time="07:29:26.404-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="lsadcache.cpp:334">
    <![LOG[MP 'SCCMSRV-02.snba.be' is compatible]LOG]!><time="07:29:26.404-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="lsadcache.cpp:339">
    <![LOG[Retrieved 1 MP records from AD for site 'ZAV']LOG]!><time="07:29:26.404-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="lsadcache.cpp:287">
    <![LOG[Retrived site version '5.00.7958.1000' from AD for site 'ZAV']LOG]!><time="07:29:26.405-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="siteinfo.cpp:575">
    <![LOG[SiteCode: ZAV]LOG]!><time="07:29:26.405-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:2076">
    <![LOG[SiteVersion: 5.00.7958.1000]LOG]!><time="07:29:26.406-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:2077">
    <![LOG[Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.]LOG]!><time="07:29:26.406-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:2111">
    <![LOG[Deleted file C:\Windows\ccmsetup\client.msi]LOG]!><time="07:29:26.413-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:9493">
    <![LOG[Only one MP SCCMSRV-02.snba.be is specified. Use it.]LOG]!><time="07:29:26.414-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:10080">
    <![LOG[Searching for DP locations from MP(s)...]LOG]!><time="07:29:26.414-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:11018">
    <![LOG[Current AD site of machine is DAT]LOG]!><time="07:29:26.415-120" date="04-17-2014" component="LocationServices" context="" type="1" thread="2724" file="lsad.cpp:770">
    <![LOG[Local Machine is joined to an AD domain]LOG]!><time="07:29:26.415-120" date="04-17-2014" component="LocationServices" context="" type="0" thread="2724" file="lsad.cpp:714">
    <![LOG[Current AD forest name is snba.be, domain name is snba.be]LOG]!><time="07:29:26.419-120" date="04-17-2014" component="LocationServices" context="" type="1" thread="2724" file="lsad.cpp:842">
    <![LOG[DhcpGetOriginalSubnetMask entry point is supported.]LOG]!><time="07:29:26.424-120" date="04-17-2014" component="LocationServices" context="" type="0" thread="2724" file="ccmiputil.cpp:117">
    <![LOG[Begin checking Alternate Network Configuration]LOG]!><time="07:29:26.424-120" date="04-17-2014" component="LocationServices" context="" type="0" thread="2724" file="ccmiputil.cpp:1095">
    <![LOG[Finished checking Alternate Network Configuration]LOG]!><time="07:29:26.433-120" date="04-17-2014" component="LocationServices" context="" type="0" thread="2724" file="ccmiputil.cpp:1172">
    <![LOG[Sending message body '<ContentLocationRequest SchemaVersion="1.00">
    <AssignedSite SiteCode="ZAV"/>
    <ClientPackage/>
    <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0">
    <ADSite Name="DAT"/>
    <Forest Name="snba.be"/>
    <Domain Name="snba.be"/>
    <IPAddresses>
    <IPAddress SubnetAddress="172.31.20.0" Address="172.31.20.101"/>
    <IPAddress SubnetAddress="172.31.105.0" Address="172.31.105.17"/>
    <IPAddress SubnetAddress="172.31.109.0" Address="172.31.109.135"/>
    </IPAddresses>
    </ClientLocationInfo>
    </ContentLocationRequest>
    ']LOG]!><time="07:29:26.441-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="siteinfo.cpp:96">
    <![LOG[Sending message header '<Msg SchemaVersion="1.1"><ID>{76CC1A6C-D696-4C32-82D6-4F56FCA9E926}</ID><SourceHost>SCCMSRV-02</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:SCCMSRV-02:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>SCCMSRV-02.snba.be</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2014-04-17T05:29:26Z</SentTime><Body Type="ByteRange" Offset="0" Length="1338"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>']LOG]!><time="07:29:26.441-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="siteinfo.cpp:177">
    <![LOG[CCM_POST 'HTTP://SCCMSRV-02.snba.be/ccm_system/request']LOG]!><time="07:29:26.442-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="httphelper.cpp:807">
    <![LOG[Content boundary is '--aAbBcCdDv1234567890VxXyYzZ']LOG]!><time="07:29:27.999-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="httphelper.cpp:1972">
    <![LOG[Received header '<Msg SchemaVersion="1.1">
    <ID>{431A4120-7DA1-4EF2-8A6C-2EDEF4D9E169}</ID>
    <SourceID>GUID:1C3F455F-F166-4B50-BE8E-68FD4F565096</SourceID>
    <SourceHost>SCCMSRV-02</SourceHost>
    <TargetAddress>direct:SCCMSRV-02:LS_ReplyLocations</TargetAddress>
    <ReplyTo>MP_LocationManager</ReplyTo>
    <CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
    <Priority>3</Priority>
    <Timeout>600</Timeout>
    <TargetHost>SCCMSRV-02</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2014-04-17T05:29:27Z</SentTime><Body Type="ByteRange" Offset="0" Length="2504"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082019206092A864886F70D010702A08201833082017F020101310B300906052B0E03021A0500300B06092A864886F70D0107013182015E3082015A02010130373023311330110603550403130A5343434D5352562D3032310C300A06035504031303534D5302104BA58C43C476A39E491A7F539E935ED8300906052B0E03021A0500300D06092A864886F70D010101050004820100B7018B6C14F24335592C864FDFAC6E038A9B2AC9AF3819C692F3DE515F97BF701A47E8595CE6CAD80F209EFFF3B1009F5AE60858FA6839B32C36FF9514D291895613A1A447C27E2BB8B05D71775FF770FF962DCC98AD3FC0DE0D45DD6BC16C9BAB0F697EF098FFC99228E26C52E661D3F6C929FEF527383DEBFA9C15027C58BAF8A7FFE4205C0198A9163E86535716E344D5012887A6AD8F563F2528DE6BD62BF2BF20DFDA4DA061EF57E755178827DAD0CB6CFC65FF4AB235E5EAAFBA565DC1B6E4AE7C093199B95CFE792F5FA6D0625D0938DC4EAF1BE70E708864B1E79B00FB32A1E6E37CF94FF54AC10C7FF994B5945E9CA1A3FA16B2F9D35462AFFAC001</Property><Property Name="AuthSenderMachine">SCCMSRV-02;SCCMSRV-02.snba.be;</Property><Property Name="MPSiteCode">ZAV</Property></Hook></Hooks><Payload Type="inline"/></Msg>']LOG]!><time="07:29:27.999-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="httphelper.cpp:1724">
    <![LOG[Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="16777216"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="ZAV" MasterSiteCode="ZAV" SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="http://SCCMSRV-02.snba.be/SMS_DP_SMSPKG$/ZAV00114" Signature="http://SCCMSRV-02.snba.be/SMS_DP_SMSSIG$/ZAV00114"/><ADSite Name="DAT"/><IPSubnets><IPSubnet Address="172.31.20.0"/><IPSubnet Address="172.31.109.0"/><IPSubnet Address="172.31.105.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>SCCMSRV-02.snba.be</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord></LocationRecords></Site></Sites><ClientPackage FullPackageID="ZAV00114" FullPackageVersion="1" FullPackageHash="BFC11E099E8F451107B43E0DBEFD93B01DB2D6453DA74F8A2CB94B73D676C1CD" MinimumClientVersion="5.00.7958.1000" RandomizeMaxDays="7" ProgramEnabled="false" LastModifiedTime="30357216;2152392064" SiteVersionMatch="true" SiteVersion="5.00.7958.1000" EnablePeerCache="true"/><RelatedContentIDs/></ContentLocationReply>']LOG]!><time="07:29:28.000-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="siteinfo.cpp:221">
    <![LOG[Found local location 'http://SCCMSRV-02.snba.be/SMS_DP_SMSPKG$/ZAV00114']LOG]!><time="07:29:28.001-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="siteinfo.cpp:351">
    <![LOG[Discovered 1 local DP locations.]LOG]!><time="07:29:28.002-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:11153">
    <![LOG[PROPFIND 'http://SCCMSRV-02.snba.be/SMS_DP_SMSPKG$/ZAV00114']LOG]!><time="07:29:28.002-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="httphelper.cpp:807">
    <![LOG[Using DP location http://SCCMSRV-02.snba.be/SMS_DP_SMSPKG$/ZAV00114]LOG]!><time="07:29:28.009-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:11395">
    <![LOG[GET 'http://SCCMSRV-02.snba.be/SMS_DP_SMSPKG$/ZAV00114/ccmsetup.cab']LOG]!><time="07:29:28.009-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="httphelper.cpp:807">
    <![LOG[C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted.]LOG]!><time="07:29:28.090-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="util.cpp:1465">
    <![LOG[Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab.]LOG]!><time="07:29:28.101-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:6670">
    <![LOG[Retrieved client version '5.00.7958.1000' and minimum assignable site version '5.00.7845.1000' from manifest]LOG]!><time="07:29:28.104-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="siteinfo.cpp:668">
    <![LOG[Checking compatibility of site version '5.00.7958.1000', expect newer than '5.00.7845.1000']LOG]!><time="07:29:28.104-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="siteinfo.cpp:703">
    <![LOG[Site version '5.00.7958.1000' is compatible. Client deployment will continue.]LOG]!><time="07:29:28.104-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="siteinfo.cpp:726">
    <![LOG[Location 'http://SCCMSRV-02.snba.be/SMS_DP_SMSPKG$/ZAV00114' passed site version check.]LOG]!><time="07:29:28.104-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:6809">
    <![LOG[Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml]LOG]!><time="07:29:28.104-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:153">
    <![LOG[Successfully loaded ccmsetup manifest file.]LOG]!><time="07:29:28.106-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:171">
    <![LOG[Checking if manifest version '5.00.7958.1000' is newer than the ccmsetup version '5.0.7958.1000']LOG]!><time="07:29:28.106-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:10475">
    <![LOG[Running from temp downloaded folder or manifest is not newer than ccmsetup.]LOG]!><time="07:29:28.107-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:2213">
    <![LOG[Item 'i386/vcredist_x86.exe' is applicable. Add to the list.]LOG]!><time="07:29:28.212-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'x64/vcredist_x64.exe' is applicable. Add to the list.]LOG]!><time="07:29:28.269-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'i386/vc50727_x86.exe' is not applicable.]LOG]!><time="07:29:28.269-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'x64/vc50727_x64.exe' is applicable. Add to the list.]LOG]!><time="07:29:28.325-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'i386/WindowsUpdateAgent30-x86.exe' is not applicable.]LOG]!><time="07:29:28.325-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'x64/WindowsUpdateAgent30-x64.exe' is applicable. Add to the list.]LOG]!><time="07:29:28.380-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'i386/msxml6.msi' is not applicable.]LOG]!><time="07:29:28.380-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'x64/msxml6_x64.msi' is applicable. Add to the list.]LOG]!><time="07:29:28.433-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'i386/msrdcoob_x86.exe' is not applicable.]LOG]!><time="07:29:28.433-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'x64/msrdcoob_amd64.exe' is not applicable.]LOG]!><time="07:29:28.434-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'pkgmgr.exe' is not applicable.]LOG]!><time="07:29:28.434-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'dism.exe' is applicable. Add to the list.]LOG]!><time="07:29:28.504-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'wimgapi.msi' is not applicable.]LOG]!><time="07:29:28.504-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'i386/MicrosoftPolicyPlatformSetup.msi' is not applicable.]LOG]!><time="07:29:28.504-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'x64/MicrosoftPolicyPlatformSetup.msi' is applicable. Add to the list.]LOG]!><time="07:29:28.560-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'i386/WindowsFirewallConfigurationProvider.msi' is not applicable.]LOG]!><time="07:29:28.561-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'x64/WindowsFirewallConfigurationProvider.msi' is applicable. Add to the list.]LOG]!><time="07:29:28.615-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'i386/Silverlight.exe' is applicable. Add to the list.]LOG]!><time="07:29:28.670-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'i386/wic_x86_enu.exe' is not applicable.]LOG]!><time="07:29:28.670-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'x64/wic_x64_enu.exe' is not applicable.]LOG]!><time="07:29:28.670-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'i386/dotNetFx40_Client_x86_x64.exe' is applicable. Add to the list.]LOG]!><time="07:29:28.723-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'SCEPInstall.exe' is applicable. Add to the list.]LOG]!><time="07:29:28.779-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Item 'i386/client.msi' is not applicable.]LOG]!><time="07:29:28.779-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:348">
    <![LOG[Item 'x64/client.msi' is applicable. Add to the list.]LOG]!><time="07:29:28.841-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:343">
    <![LOG[Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider]LOG]!><time="07:29:28.842-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="ccmutillib.cpp:1363">
    <![LOG[Default CSP Type is 24]LOG]!><time="07:29:28.842-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="ccmutillib.cpp:1364">
    <![LOG[Discovering whether item 'i386/vcredist_x86.exe' exists.]LOG]!><time="07:29:28.842-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Detected item 'i386/vcredist_x86.exe']LOG]!><time="07:29:28.842-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'x64/vcredist_x64.exe' exists.]LOG]!><time="07:29:28.842-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Detected item 'x64/vcredist_x64.exe']LOG]!><time="07:29:28.843-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'x64/vc50727_x64.exe' exists.]LOG]!><time="07:29:28.843-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Upgrade code '{A8D19029-8E5C-4E22-8011-48070F9E796E}': product = '{ad8a2fa1-06e7-4b0d-927d-6e54b3d31028}', installed = 1, version = 8.0.61000]LOG]!><time="07:29:28.843-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="msiutil.cpp:1273">
    <![LOG[Checking '{A8D19029-8E5C-4E22-8011-48070F9E796E}' version '8.0.61000' expecting >= '8.0.61000'.]LOG]!><time="07:29:28.844-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="manifest.cpp:873">
    <![LOG[Detected item 'x64/vc50727_x64.exe']LOG]!><time="07:29:28.844-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'x64/WindowsUpdateAgent30-x64.exe' exists.]LOG]!><time="07:29:28.844-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Checking file 'C:\Windows\system32\wuapi.dll' version '7.6.7600.0256' expecting >= '7.4.7600.226'.]LOG]!><time="07:29:28.846-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="manifest.cpp:1278">
    <![LOG[Detected item 'x64/WindowsUpdateAgent30-x64.exe']LOG]!><time="07:29:28.846-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'x64/msxml6_x64.msi' exists.]LOG]!><time="07:29:28.846-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Checking file 'C:\Windows\system32\msxml6.dll' version '6.30.7601.17857' expecting >= '6.10.1129.0'.]LOG]!><time="07:29:28.847-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="manifest.cpp:1278">
    <![LOG[Detected item 'x64/msxml6_x64.msi']LOG]!><time="07:29:28.847-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'dism.exe' exists.]LOG]!><time="07:29:28.847-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[File 'C:\Windows\system32\msrdc.dll' exists. Discovery passed]LOG]!><time="07:29:28.848-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="manifest.cpp:1250">
    <![LOG[Detected item 'dism.exe']LOG]!><time="07:29:28.848-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'x64/MicrosoftPolicyPlatformSetup.msi' exists.]LOG]!><time="07:29:28.848-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Upgrade code '{19B9818B-7432-49E9-BC02-B126025EE235}': product = '{90D295B8-BA08-487E-B904-0E624209A410}', installed = 1, version = 1.2.3602.0]LOG]!><time="07:29:28.849-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="msiutil.cpp:1273">
    <![LOG[Checking '{19B9818B-7432-49E9-BC02-B126025EE235}' version '1.2.3602.0' expecting >= '1.2.3602.0'.]LOG]!><time="07:29:28.849-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="manifest.cpp:873">
    <![LOG[Detected item 'x64/MicrosoftPolicyPlatformSetup.msi']LOG]!><time="07:29:28.849-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'x64/WindowsFirewallConfigurationProvider.msi' exists.]LOG]!><time="07:29:28.849-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Validated file 'C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi' hash '3BF0651FD4A01170925CEF694468D4EF6F64D76FD3413DEBD14CB8DE019AA10E']LOG]!><time="07:29:28.868-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="util.cpp:2609">
    <![LOG[File 'C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi' exists. Discovery passed]LOG]!><time="07:29:28.868-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="manifest.cpp:1250">
    <![LOG[Detected item 'x64/WindowsFirewallConfigurationProvider.msi']LOG]!><time="07:29:28.868-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'i386/Silverlight.exe' exists.]LOG]!><time="07:29:28.869-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[32-bit Hive selected]LOG]!><time="07:29:28.869-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:948">
    <![LOG[Detected item 'i386/Silverlight.exe']LOG]!><time="07:29:28.869-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'i386/dotNetFx40_Client_x86_x64.exe' exists.]LOG]!><time="07:29:28.869-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Detected item 'i386/dotNetFx40_Client_x86_x64.exe']LOG]!><time="07:29:28.869-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'SCEPInstall.exe' exists.]LOG]!><time="07:29:28.870-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Validated file 'C:\Windows\ccmsetup\SCEPInstall.exe' hash 'FDDB17A148D8358B5BFBF63BBB3CDE902DCE807366081FE16B8E6042DCB47C71']LOG]!><time="07:29:29.649-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="util.cpp:2609">
    <![LOG[Checking file 'C:\Windows\ccmsetup\SCEPInstall.exe' version '4.3.0220.0000' expecting >= '4.3.220.0'.]LOG]!><time="07:29:29.651-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="manifest.cpp:1278">
    <![LOG[Detected item 'SCEPInstall.exe']LOG]!><time="07:29:29.651-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:614">
    <![LOG[Discovering whether item 'x64/client.msi' exists.]LOG]!><time="07:29:29.651-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:553">
    <![LOG[Item x64/client.msi has not been installed yet. Put to pending install list.]LOG]!><time="07:29:29.651-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="manifest.cpp:609">
    <![LOG[PROPFIND 'http://SCCMSRV-02.snba.be/SMS_DP_SMSPKG$/ZAV00114']LOG]!><time="07:29:29.651-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="httphelper.cpp:807">
    <![LOG[No client patches are detected.]LOG]!><time="07:29:29.658-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="ccmsetup.cpp:1736">
    <![LOG[PROPFIND 'http://SCCMSRV-02.snba.be/SMS_DP_SMSPKG$/ZAV00114']LOG]!><time="07:29:29.658-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="httphelper.cpp:807">
    <![LOG[No client language packs are detected.]LOG]!><time="07:29:29.664-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="ccmsetup.cpp:1777">
    <![LOG[Searching for available transform]LOG]!><time="07:29:29.665-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:1807">
    <![LOG[PROPFIND 'http://SCCMSRV-02.snba.be/SMS_DP_SMSPKG$/ZAV00114']LOG]!><time="07:29:29.665-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="httphelper.cpp:807">
    <![LOG[No transform available for this locale. Installation will proceed with no transformation.]LOG]!><time="07:29:29.671-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:1892">
    <![LOG[File 'C:\Windows\ccmsetup\client.msi' doesn't exist.]LOG]!><time="07:29:29.672-120" date="04-17-2014" component="ccmsetup" context="" type="2" thread="2724" file="util.cpp:2595">
    <![LOG[Using branch cache option.]LOG]!><time="07:29:29.690-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:6443">
    <![LOG[Adding file 'http://SCCMSRV-02.snba.be:80/SMS_DP_SMSPKG$/ZAV00114/x64/client.msi' to BITS job, saving as 'C:\Windows\ccmsetup\client.msi'.]LOG]!><time="07:29:29.690-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:6474">
    <![LOG[Starting BITS download for client deployment files.]LOG]!><time="07:29:29.698-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:6487">
    <![LOG[Download Update: 32616448 out of 32616448 bytes transferred.]LOG]!><time="07:29:30.700-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:6578">
    <![LOG[Successfully completed BITS download for client deployment files.]LOG]!><time="07:29:32.701-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:6536">
    <![LOG[Retrieved client version '5.00.7958.1000' and minimum assignable site version '5.00.7845.1000' from client package]LOG]!><time="07:29:34.020-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="siteinfo.cpp:678">
    <![LOG[Checking compatibility of site version '5.00.7958.1000', expect newer than '5.00.7845.1000']LOG]!><time="07:29:34.020-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="siteinfo.cpp:703">
    <![LOG[Site version '5.00.7958.1000' is compatible. Client deployment will continue.]LOG]!><time="07:29:34.020-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="siteinfo.cpp:726">
    <![LOG[Successfully downloaded client files via BITS.]LOG]!><time="07:29:34.020-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:1396">
    <![LOG[Validated file 'C:\Windows\ccmsetup\client.msi' hash 'A5732CE24F2B1545E9FBA458971E0A5504093E0F743CA9E8BD9C047582902878']LOG]!><time="07:29:35.032-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="util.cpp:2609">
    <![LOG[An MP exists on this machine.]LOG]!><time="07:29:35.048-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="msiutil.cpp:565">
    <![LOG[The client version 5.00.7958.1000 does not match the MP version 5.00.7804.1000. The client will not be installed.]LOG]!><time="07:29:35.048-120" date="04-17-2014" component="ccmsetup" context="" type="3" thread="2724" file="msiutil.cpp:583">
    <![LOG[Sending Fallback Status Point message to 'SCCMSRV-02', STATEID='318'.]LOG]!><time="07:29:35.049-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="2724" file="ccmsetup.cpp:9756">
    <![LOG[Failed to get client version for sending messages to FSP. Error 0x80041010]LOG]!><time="07:29:35.054-120" date="04-17-2014" component="ccmsetup" context="" type="2" thread="2724" file="ccmsetup.cpp:9838">
    <![LOG[Params to send FSP message '5.0.7958.1000 Deployment ']LOG]!><time="07:29:35.054-120" date="04-17-2014" component="ccmsetup" context="" type="0" thread="2724" file="ccmsetup.cpp:9887">
    <![LOG[State message with TopicType 800 and TopicId {5FF017B3-AF3F-4D38-B037-0A7EE1F479C5} has been sent to the FSP]LOG]!><time="07:29:35.075-120" date="04-17-2014" component="FSPStateMessage" context="" type="1" thread="2724" file="fsputillib.cpp:752">
    <![LOG[InstallFromManifest failed 0x80004005]LOG]!><time="07:29:35.084-120" date="04-17-2014" component="ccmsetup" context="" type="3" thread="2724" file="ccmsetup.cpp:7202">
    <![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="07:29:35.086-120" date="04-17-2014" component="ccmsetup" context="" type="1" thread="7532" file="ccmsetup.cpp:10879">
    I hope someone can help me with this.
    Kind regards

    I agree with Idan. You can easily remove the Management Point Site System role and add it again with no adverse effect. This should solve your problem.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Accessing the same stateful session bean from multiple clients in a clustered environment

    I am trying to access the same stateful session bean from multiple
              clients. I also want this bean to have failover support so we want to
              deploy it in a cluster. The following description is how we have tried
              to solve this problem, but it does not seem to be working. Any
              insight would be greatly appreciated!
              I have set up a cluster of three servers. I deployed a stateful
              session bean with in memory replication across the cluster. A client
              obtains a reference to an instance of one of these beans to handle a
              request. Subsequent requests will have to use the same bean and could
              come from various clients. So after using the bean the first client
              stores the handle to the bean (actually the replica aware stub) to be
              used by other clients to be able to obtain the bean. When another
              client retrieves the handle gets the replica aware stub and makes a
              call to the bean the request seems to unpredictably go to any of the
              three servers rather than the primary server hosting that bean. If the
              call goes to the primary server everything seems to work fine the
              session data is available and it gets backed up on the secondary
              server. If it happens to go to the secondary server a bean that has
              the correct session data services the request but gives the error
              <Failed to update the secondary copy of a stateful session bean from
              home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
              to the primary server will not reflect changes made on the secondary
              and vice versa. If the request happens to go to the third server that
              is not hosting an instance of that bean then the client receives an
              error that the bean was not available. From my understanding I thought
              the replica aware stub would know which server is the primary host for
              that bean and send the request there.
              Thanks in advance,
              Justin
              

              If 'allow-concurrent-call' does exactly what you need, then you don't have a problem,
              do you?
              Except of course if you switch ejb containers. Oh well.
              Mike
              "FBenvadi" <[email protected]> wrote:
              >I've got the same problem.
              >I understand from you that concurrent access to a stateful session bean
              >is
              >not allowed but there is a
              >token is weblogic-ejb-jar.xml that is called 'allow-concurrent-call'
              >that
              >does exactly what I need.
              >What you mean 'you'll get a surprise when you go to production' ?
              >I need to understand becouse I can still change the design.
              >Thanks Francesco
              >[email protected]
              >
              >"Mike Reiche" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >> Get the fix immediately from BEA and test it. It would be a shame to
              >wait
              >until
              >> December only to get a fix - that doesn't work.
              >>
              >> As for stateful session bean use - just remember that concurrent access
              >to
              >a stateful
              >> session bean is not allowed. Things will work fine until you go to
              >production
              >> and encounter some real load - then you will get a surprise.
              >>
              >> Mike
              >>
              >> [email protected] (Justin Meyer) wrote:
              >> >I just heard back from WebLogic Tech Support and they have confirmed
              >> >that this is a bug. Here is their reply:
              >> >
              >> >There is some problem in failover of stateful session beans when its
              >> >run from a java client.However, it is fixed now.
              >> >
              >> >The fix will be in SP2 which will be out by december.
              >> >
              >> >
              >> >Mike,
              >> >Thanks for your reply. I do infact believe we are correctly using
              >a
              >> >stateful session bean however it may have been misleading from my
              >> >description of the problem. We are not accessing the bean
              >> >concurrently from 2 different clients. The second client will only
              >> >come into play if the first client fails. In this case we want to
              >be
              >> >able to reacquire the handle to our stateful session bean and call
              >it
              >> >from the secondary client.
              >> >
              >> >
              >> >Justin
              >> >
              >> >"Mike Reiche" <[email protected]> wrote in message
              >news:<[email protected]>...
              >> >> You should be using an entity bean, not a stateful session bean
              >for
              >> >this application.
              >> >>
              >> >> A stateful session bean is intended to be keep state (stateful)
              >for
              >> >the duration
              >> >> of a client's session (session).
              >> >>
              >> >> It is not meant to be shared by different clients - in fact, if
              >you
              >> >attempt to
              >> >> access the same stateful session bean concurrently - it will throw
              >> >an exception.
              >> >>
              >> >> We did your little trick (storing/retrieving handle) with a stateful
              >> >session bean
              >> >> on WLS 5.1 - and it did work properly - not as you describe. Our
              >sfsb's
              >> >were not
              >> >> replicated as yours are.
              >> >>
              >> >> Mike
              >> >>
              >> >> [email protected] (Justin Meyer) wrote:
              >> >> >I am trying to access the same stateful session bean from multiple
              >> >> >clients. I also want this bean to have failover support so we want
              >> >to
              >> >> >deploy it in a cluster. The following description is how we have
              >tried
              >> >> >to solve this problem, but it does not seem to be working. Any
              >> >> >insight would be greatly appreciated!
              >> >> >
              >> >> >I have set up a cluster of three servers. I deployed a stateful
              >> >> >session bean with in memory replication across the cluster. A client
              >> >> >obtains a reference to an instance of one of these beans to handle
              >> >a
              >> >> >request. Subsequent requests will have to use the same bean and
              >could
              >> >> >come from various clients. So after using the bean the first client
              >> >> >stores the handle to the bean (actually the replica aware stub)
              >to
              >> >be
              >> >> >used by other clients to be able to obtain the bean. When another
              >> >> >client retrieves the handle gets the replica aware stub and makes
              >> >a
              >> >> >call to the bean the request seems to unpredictably go to any of
              >the
              >> >> >three servers rather than the primary server hosting that bean.
              >If
              >> >the
              >> >> >call goes to the primary server everything seems to work fine the
              >> >> >session data is available and it gets backed up on the secondary
              >> >> >server. If it happens to go to the secondary server a bean that
              >has
              >> >> >the correct session data services the request but gives the error
              >> >> ><Failed to update the secondary copy of a stateful session bean
              >from
              >> >> >home:ejb20-statefulSession-TraderHome>. Then any subsequent requests
              >> >> >to the primary server will not reflect changes made on the secondary
              >> >> >and vice versa. If the request happens to go to the third server
              >that
              >> >> >is not hosting an instance of that bean then the client receives
              >an
              >> >> >error that the bean was not available. From my understanding I
              >thought
              >> >> >the replica aware stub would know which server is the primary host
              >> >for
              >> >> >that bean and send the request there.
              >> >> >
              >> >> >Thanks in advance,
              >> >> >Justin
              >>
              >
              >
              

  • My outgoing mail is not working after the upgrade OS to mavericks. my mail client version is 7.1 . please help me resolve this issue

    My outgoing mail is not working after the upgrade OS to the mavericks. my mail client version is 7.1 . please help me out resolve this issue

    Please let me know , How we can reinstall apple mail ? .
    1 . We updated OS to mavericks few machine in last december and still does't works SMTP (Out going mail) on those MAC.
    2.  After that most recently we updated OS to mavericks few machine those are working will with SMTP server .
             a)Not showing any SMTP connection in TCP trace ,
             b) Connection docter every time Says "Connecting to the server "
    3, Then we have installed thunderberd (another mail) client on maverick os, which OS related to apple mail client not woking . It seems other mail client is working well with SMTP server .
    Please help me .
    Thanks,
    Ranesh..

  • We have created shared folder on multiple client machine in domain environment on different 2 OS like-XP,Vista, etc. from some day's When we facing problem when we are access from host name that shared folder is accessible but same time same computer when

    Hello All,
    we have created shared folder on multiple client machine in domain environment on different 2 OS like-XP,Vista, etc.
    from some day's When we facing problem when we are access from host name that shared folder is accessible but same time same computer when we are trying to access the share folder with IP it asking for credentials i have type again and again
    correct credential but unable to access that. If i re-share the folder then we are access it but when we are restarted the system then same problem is occurring.
    I have checked IP,DNS,Gateway and more each & everything is well.
    Pls suggest us.
    Pankaj Kumar

    Hi,
    According to your description, my understanding is that the same shared folder can be accessed by name, but can’t be accessed be IP address and asks for credentials.
    Please try to enable the option below on the device which has shared folder:
    Besides, check the Advanced Shring settings of shared folder and confrim that if there is any limitation settings.
    Best Regards,
    Eve Wang
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • API5036: Client version 10.2.0.1.31 is not compatible with repository ver..

    API5036: Client version 10.2.0.1.31 is not compatible with repository version 10.2.0.2.0
    I got this error after upgraded with patch p5696353_10202_AIX64-5L
    I tried to log in but there was a pop up dialog told me about this error. Do I have to install new client version?? I cannot find owb client 10.2.0.2.0 on the download site. Would you guys help me to get though this please?? Any solotion if I still used owb client version 10.2.0.1??
    Rgds,
    Godtee

    Hi Godtee,
    you have to use the same version on the client as on the server.
    There is only one software package containing owb client and server components. Use it for server and client side installations.
    It seems that you have patched your server installation to 10.2.0.2.0. Apply this patch to your client installation and you will be able to connect to the repository with version 10.2.0.2.0
    Regards,
    Carsten.

  • API5036: Client Version 10.1.0.4 is not compatible with Repository version

    I have an OWB repository version 10.1.0.1.0 and a client of 10.1.0.2.0. We have have been running this fine. I need to upgrade to 10.1.0.4.0 of OWB so I can begin to use a 10gR2 database as my target. I exported (database wise) my repository and imported it into the 10.2.0.1 database - all went well. I now went to upgrade the repository from 10.1.0.1.0 to 10.1.0.4.0 and ran the shell in the ../bin/unix dierctory. It ran fine, yet when I connect to the repository using the 10.1.0.4 client I get the "API5036: Client Version 10.1.0.4 is not compatible with Repository version 10.1.0.1.0" as if I never ran the DT upgrade shell. I then noticed the shell provided with the 10.1.0.4 install is DTupg92to10g.sh and I am not upgrading a 92 repos to a 10 repos. Is there a upgrade for 10.1.0.1.0 to 10.1.0.4.0?
    Thanks,
    Sean

    for OWB metadata, run this following script
    <OWB_HOME>/owb/reposasst/upg/upg10gTo10104.sql
    For runtime data
    <OWB_HOME>/owb/bin/unix/RT_upgrade_to_10_1
         This is only if it's NOT upgrading to 10gR2 database
    If you are upgrading to Oracle10g Release 2 with partial export and
    import and if you are changing the database instance or the computer
    hosting the database, then run the migration script:
    – For UNIX, navigate to OWB_HOME/owb/bin/unix and run
    RT_migrate_to_10_1.sh.
    The RT_migrate_to_10_1.sh prompts you for several parameters:
    the User Name and Password of your original Runtime Repository
    schema, the database connection string for your original Runtime
    Repository (in the form of host:port:servicename), the User Name
    and Password for your new Runtime Repository schema (whose values
    should match the original Runtime Repository), and the database
    connection string for the new Runtime Repository (also in the form of
    host:port:servicename). Additionally, as it runs, the script prompts
    you for SYS User Names and Passwords for the Oracle Database
    instances for any Target Schemas and Oracle Workflows being upgraded.

Maybe you are looking for