Node manager disconnection - more details

Hi,
thank you for the replies. Following more details about our actual
configuration.
The servers are Solaris based and the clients are both Solaris and NT based.
What happens exactly is:
1) the central env shuts down. Sometime we have to force the shutdown
manually when the overall applications gets stuck.
2) the client node managers remain active.
3) we restart the central env without restarting the client node managers.
4) we manually restart the node managers on the application servers.
5) we manually restart the server partition (where applicable).
6) the client node managers (on both Solaris and NT clients) don't manage to
reconnect to the central env and the client application (which uses the
launch service to start the applications) fails.
The problem is that we can easly stop and restart the client node manager
on the Solaris workstations (with rsh command), but we have poblems doing
the same with NT workstations. Of course we would like to avoid having to
restart the client node managers.
We strongly suspect there is something wrong in our
configuration/procedures ...
P.S.
In our clients, we use only one entry for FORTE_NS_ADDRESS (eg.
FORTE_NS_ADDRESS=poitdr:5018)
Massimiliano Ugolini
EDS Italy
Banking Division
Hi Massimiliano,
On which OS are you running ?
This case isn't normal at all. I tested it on NT Client and AIX server and it
worked well.
But you may have only a refresh problem on EConsole. Did you try to close and
re-open EConsole ?
[email protected] a écrit:
We have experienced that when shutting down the central environment, the
client node manager which remained active didn't reconnect to the central
env when restarted.
Is this normal or is there any special solution/procedure to solve this case ?
(we have many remote locations to administer).
Massimiliano Ugolini
EDS Italy
Banking Division
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Hi,
After what I've observed, the case is sometimes it will reconnect and
sometimes it won't depending on the loading of the environment manager.
Moreover, even if it reconnect, it would take a while ( a long while ).
Regards,
Peter Sham.
-----Original Message-----
From: [email protected]
[SMTP:[email protected]]
Sent: Tuesday, February 02, 1999 7:01 PM
To: [email protected]
Subject: node manager disconnection
We have experienced that when shutting down the central environment,
the
client node manager which remained active didn't reconnect to the
central
env when restarted.
Is this normal or is there any special solution/procedure to solve
this case ?
(we have many remote locations to administer).
Massimiliano Ugolini
EDS Italy
Banking Division
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Similar Messages

  • RE: node manager disconnection

    when we have this problem...we just remove the .btd & .btx files in
    %FORTE_ROOT\sysdata\envrepos on the offending client machine and bring the
    launcher distributed up again on that machine. I would be interested in
    knowing the cause and if there is a better solution too.
    -Ravi Kalidindi
    Born Information Svcs. Group
    -----Original Message-----
    From: [email protected] [SMTP:[email protected]]
    Sent: Tuesday, February 02, 1999 5:01 AM
    To: [email protected]
    Subject: node manager disconnection
    We have experienced that when shutting down the central environment, the
    client node manager which remained active didn't reconnect to the central
    env when restarted.
    Is this normal or is there any special solution/procedure to solve this
    case ?
    (we have many remote locations to administer).
    Massimiliano Ugolini
    EDS Italy
    Banking Division
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi,
    After what I've observed, the case is sometimes it will reconnect and
    sometimes it won't depending on the loading of the environment manager.
    Moreover, even if it reconnect, it would take a while ( a long while ).
    Regards,
    Peter Sham.
    -----Original Message-----
    From: [email protected]
    [SMTP:[email protected]]
    Sent: Tuesday, February 02, 1999 7:01 PM
    To: [email protected]
    Subject: node manager disconnection
    We have experienced that when shutting down the central environment,
    the
    client node manager which remained active didn't reconnect to the
    central
    env when restarted.
    Is this normal or is there any special solution/procedure to solve
    this case ?
    (we have many remote locations to administer).
    Massimiliano Ugolini
    EDS Italy
    Banking Division
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive
    <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • Gnome power managment - need more detailed control

    Is there something in the AUR or elsewhere that will allow one to specify per-disk spindown times?  For example, /dev/sda = never but /dev/sdb = 15 min.  Should I just call a script from /etc/rc.local that does it via hdparm or is there something more fancy?

    Assuming this is a laptop (if not ignore), you could have different spin-down times on AC vs battery if you ran the hdparm script through pm-utils, by adding a hook to pm-powersave and having it react to acpi events through acpid.

  • More Details about Multithreading Mode in User Management

    Good morning,
    we are working with Portal 7.0 on SP 14 and there is an option to activate the multithreading mode
    in the User Management part of the support desk. Since this option seems to significant speed up our
    login time i´am interested in more details about what is happening here. But i was unable to locate
    any documentation / forum entries / blogs about it. Another point is the question if it is possible
    to persist that option. After every Node / Serverrestart multithreading gets deactivated again.
    Any Ideas / Links / Helps would be appreciated and points will be rewarded.
    Thank you,
    Marco

    Hi
    Here is a useful HDD password summary:
    http://aps2.toshiba-tro.de/kb0/TSB6B01MC000CR01.htm
    _HDD User Password and HDD Master Password:_
    There are two levels of the HDD Password, the HDD User Password and the HDD master Password. If both levels of HDD Password have been registered, you can access the HDD by entering either of them. TOSHIBA Password Utility (TPU) only supports the HDD User Password. If you want to register both, open BIOS SETUP. If the HDD User Password has been registered, the HDD Master Password can not be registered
    Hope this helps a little bit

  • Can I run more than one Node Manager per machine?

    Hia,
    We have a situation in our project where we need to run different domains on a Solaris machine in different java modes.
    Say Domain1 should be running in 32bit version of java where as Domain2 should be running in 64bit mode due to the nature of testing currently going on in different domains.
    We could successfully get the two domains running in different java modes in parallel by modifying the start scripts to decide which Sud data model to start the servers based on certain parms. However, the pain here is with the Node Manager.
    My understanding is that there should be one Node Manager running per machine for all the domains running on that machine. So when ever I have to run a domain in a java mode different to that of what Node Manager is running on, I had to kill the node manager and start it in the same version that I want to start the other servers in since Node Manager uses its starting parms internally to start the Managed Servers (Note: there is no issue in running the Admin Server regardless of the node manager mode as expected).
    Can somebody advise me if there is any way to get around this hassle?
    I want to know if we can run more than one node manager per machine.
    Below are the details of my env.
    Weblogic Server 10.3
    Solaris 10 SPARC 64 bit (SunOS 5.10 Generic_142900-14 sun4v sparc)
    java version "1.6.0_20"
    Hope all this makes sense...
    Cheers,
    Satish.
    Edited by: apsnaidu on Mar 15, 2013 3:29 PM

    You can run as many node manager as you want in a particular machine.
    At the time of starting the node manager you need to pass hostname & Port.
    This will start the nodemanager on different ports of a machine.
    sh startNodeManager.sh <hostname> <port>
    eg:- sh startNodeManager.sh dev_machine_01 5556
    sh startNodeManager.sh dev_machine_01 5557
    sh startNodeManager.sh dev_machine_01 5558
    After starting your node manager in different ports you need to change machine details from admin console.

  • Node manager

    i have two managed servers MS_Dev1 and MS_Dev2 in MS windows 7 system. when starting the admin MS_Dev2 reaches to running mode as i configured node-manager for both server. But MS_Dev1 went to shutdown state, not able to start from Admin console. It went to Failed " FAILED_NOT_RESTARTABLE ". checked the log it says invalid password.
    i have re typed the pwd in Settings for MS_Dev1 -> Server Start -> username and password, again the same " FAILED_NOT_RESTARTABLE ". finally i went to C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\security and re typed the username and password in boot.properties file. Restarted the admin server but same " FAILED_NOT_RESTARTABLE " for MS_Dev1. Also i have tried to shutdown the MS_Dev1 in admin console, it throws below
    Message icon - Warning The server MS_Dev1 is in an incompatible state.
    Message icon - Warning All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
    Note: Pwd for Admin, MS_Dev1 and 2 are same
    Looking the solution to fix this issue ASAP, Thnks a lot in Advance !
    refer the logs below,
    dev_domain.log
    ####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989715> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989715> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989731> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 8:49:49 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362107989731> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    AdminServer.log
    ####<Mar 1, 2013 9:04:36 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108876293> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:04:36 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108876309> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:04:36 AM IST> <Notice> <Security> <Ram-PC> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108876309> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:05:04 AM IST> <Warning> <netuix> <Ram-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1362108904420> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=WLSServerControlTablePage.>
    ####<Mar 1, 2013 9:05:04 AM IST> <Warning> <Socket> <Ram-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108904872> <BEA-000449> <Closing socket as no data read from it on 192.168.56.1:58,895 during the configured idle timeout of 5 secs>
    ####<Mar 1, 2013 9:05:04 AM IST> <Warning> <Socket> <Ram-PC> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108904872> <BEA-000449> <Closing socket as no data read from it on 192.168.56.1:58,894 during the configured idle timeout of 5 secs>
    MS_Dev1.log
    ####<Mar 1, 2013 9:02:09 AM IST> <Notice> <Log Management> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729431> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    ####<Mar 1, 2013 9:02:09 AM IST> <Info> <Diagnostics> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729462> <BEA-320077> <Initialized the Diagnostic Accessor Service.>
    ####<Mar 1, 2013 9:02:09 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729493> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
    ####<Mar 1, 2013 9:02:09 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108729493> <BEA-000133> <Waiting to synchronize with other running members of Dev_Cluster.>
    ####<Mar 1, 2013 9:02:11 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <weblogic.cluster.MessageReceiver> <<WLS Kernel>> <> <> <1362108731677> <BEA-003107> <Lost 2 unicast message(s).>
    ####<Mar 1, 2013 9:02:25 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108745889> <BEA-000111> <Adding MS_Dev2 with ID -3996848074127341669S:192.168.56.1:[7004,7004,-1,-1,-1,-1,-1]:dev_domain:MS_Dev2 to cluster: Dev_Cluster view.>
    ####<Mar 1, 2013 9:02:25 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108745889> <BEA-000142> <Trying to download cluster JNDI tree from server MS_Dev2.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746139> <BEA-000128> <Updating -3996848074127341669S:192.168.56.1:[7004,7004,-1,-1,-1,-1,-1]:dev_domain:MS_Dev2 in the cluster.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746357> <BEA-000164> <Synchronized cluster JNDI tree from server MS_Dev2.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108746404> <BEA-000365> <Server state changed to ADMIN>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108746419> <BEA-000365> <Server state changed to RESUMING>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Cluster> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746451> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746778> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746841> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746841> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\JDK160~1\jre\lib\security\cacerts.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746903> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746903> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746919> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746934> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Security> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Info> <WebLogicServer> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-000307> <Exportable key maximum lifespan set to 500 uses.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Info> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-002610> <Dynamic Listener Service initialized.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746950> <BEA-002613> <Channel "Default" is now listening on 192.168.56.1:7003 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746965> <BEA-002613> <Channel "DefaultSecure" is now listening on 192.168.56.1:7503 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
    ####<Mar 1, 2013 9:02:26 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108746965> <BEA-000332> <Started WebLogic Managed Server "MS_Dev1" for domain "dev_domain" running in Development Mode>
    ####<Mar 1, 2013 9:02:27 AM IST> <Info> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108747028> <BEA-002635> <The server "AdminServer" connected to this server.>
    ####<Mar 1, 2013 9:02:27 AM IST> <Info> <JMX> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108747090> <BEA-149511> <Established JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://14.96.37.127:7001/jndi/weblogic.management.mbeanservers.domainruntime.>
    ####<Mar 1, 2013 9:02:27 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108747979> <BEA-000365> <Server state changed to RUNNING>
    ####<Mar 1, 2013 9:02:27 AM IST> <Notice> <WebLogicServer> <Ram-PC> <MS_Dev1> <main> <<WLS Kernel>> <> <> <1362108747995> <BEA-000360> <Server started in RUNNING mode>
    ####<Mar 1, 2013 9:02:27 AM IST> <Info> <J2EE> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108747995> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
    ####<Mar 1, 2013 9:02:29 AM IST> <Info> <Cluster> <Ram-PC> <MS_Dev1> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108749524> <BEA-000128> <Updating -3996848074127341669S:192.168.56.1:[7004,7004,-1,-1,-1,-1,-1]:dev_domain:MS_Dev2 in the cluster.>
    ####<Mar 1, 2013 9:03:26 AM IST> <Info> <Health> <Ram-PC> <MS_Dev1> <weblogic.GCMonitor> <<anonymous>> <> <> <1362108806365> <BEA-310002> <80% of the total memory in the server is free>
    ####<Mar 1, 2013 9:03:32 AM IST> <Info> <Server> <Ram-PC> <MS_Dev1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1362108812808> <BEA-002634> <The server "AdminServer" disconnected from this server.>

    Kishore,
    checked the boot.properties file, it not having .txt and find the nodemanager.log as given below,
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Boot identity properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\boot.properties">
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Startup configuration properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\startup.properties">
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00006">
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Starting WebLogic server with command line: C:\Oracle\Middleware\user_projects\domains\dev_domain\bin\startWebLogic.cmd >
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\dev_domain'>
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00007">
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
    <Mar 1, 2013 8:21:16 AM> <INFO> <dev_domain> <MS_Dev1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out'>
    <Mar 1, 2013 8:21:21 AM> <INFO> <dev_domain> <MS_Dev1> <Server failed during startup so will not be restarted>
    <Mar 1, 2013 8:21:21 AM> <WARNING> <Exception while starting server 'MS_Dev1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Boot identity properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\boot.properties">
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Startup configuration properties saved to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\data\nodemanager\startup.properties">
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00008">
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Starting WebLogic server with command line: C:\Oracle\Middleware\user_projects\domains\dev_domain\bin\startWebLogic.cmd >
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\dev_domain'>
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out00009">
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Server error log also redirected to server log>
    <Mar 1, 2013 8:24:53 AM> <INFO> <dev_domain> <MS_Dev1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\dev_domain\servers\MS_Dev1\logs\MS_Dev1.out'>
    <Mar 1, 2013 8:24:59 AM> <INFO> <dev_domain> <MS_Dev1> <Server failed during startup so will not be restarted>
    <Mar 1, 2013 8:24:59 AM> <WARNING> <Exception while starting server 'MS_Dev1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)

  • Unable to start Manager server using Node Manager

    Hi,
    I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
    Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
    but not able to start Managed server using node manager
    its giving exception as below;
    error:- wls:/nm/webdomain> nmStart('ms1')
    Starting server ms1 ...
    Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
    Managed server log: -
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    [root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    Nodemanager log:
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
    <Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
    <Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
    at weblogic.nodemanager.server.Handler.run(Handler.java:71)
    at java.lang.Thread.run(Thread.java:662)

    You can start a managed server as follows:
    print 'START NODE MANAGER';
    startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
    print 'CONNECT TO NODE MANAGER';
    nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
    print 'START ADMIN SERVER';
    nmStart('AdminServer');
    nmServerStatus('AdminServer');
    print 'CONNECT TO ADMIN SERVER';
    connect(adminusername, adminpassword);
    print 'START MANAGED SERVER';
    start('VideotheekWebServer','Server');
    nmServerStatus('VideotheekWebServer');
    print 'START CLUSTER';
    start('VideotheekCluster','Cluster');
    nmServerStatus('VideotheekServer1');
    nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
    The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.

  • Should BT be able to provide more detail about usa...

    Ok, so I've jut done a bit of searching and found what would be a solution to my problem in the "ideas" section... so commented there also, but so I may get a community opinion, what are your thoughts on the subject of BT providing more detailed usage statistics outside of the BroadBand usage monitor in My-BT? (i.e over the phone / by request on mail / even as an attachment on email notification of additional charges???)
    So my story that's prompted this...
    I have an option 1 10GB limited service and often get close to it - my average usage is actually 10.1Gb according to the usage monitor as I've had a couple of £5 additional use charges now in the past 6 months... However, today I've received a message saying I'd again exceeded the limit for Feb by using 16Gb... this is the most I've been over (plus £10 charge now) and to make matters worse in Feb, BT managed to disrupt my service (completely disconnected & long story!) for nearly 6 days and therefore I would like to "question" the exceeded usage for the first time - I'd raised a dispute today following the complaint process, and promptly received a returned call...
    What I wanted was a breakdown of the usage over Feb PER DAY as I'm pretty sure our surfing habits have not changed, yet I'm well above my average usage even considering I had no internet for 20% of the month!!
    I'd also like to have seen in the report that there was no increase of data consumed over the "6 day outage period" - as it would have confirmed to me there was nothing strange going on.
    FYI if its relevant to usage totals; to resolve my problem, a BT Openreach engineer was required to visit the exchange to re-patch the broadband service in to my residential line... after some other engineer pulled it out! So there is a risk (in my opinion) that the usage for Feb could be misleading if taken over 2 different connections.
    For instance, I know my line is syncing faster than previously & the engineer confirmed I'd been re-connected to different infrastructure in the exchange. (e.g from upto 8MB to the upto 20Mb service???)
    When I politely asked for the usage detail on the phone today, I had a point blank refusal! I know the customer version of the usage monitor doesnt provide this level of detail, but really BT, are you telling me you do not have (or could create a report) on my usage by day?
    This leaves me with a problem because (again in my opinion) BT are able to abuse the "usage" total and top up their revenue as & when they see fit!!! As a customer, I now feel powerless to challenge it!
    My only option is to upgrade to a higher service, when out of the principle of handing over more money, I'm not happy to do at the moment - again BT could easily abuse the supplier position to "push" customers into more expensive service!!!
    Back to the phone call today, after explaining my problem & concerns, I got nowhere but the BT agent agreed with everything I said (thanks??? ) and basically said she agreed it was a poor service! lol
    Is this a new tactic to agree with everything the customer says but then keep repeating the fact they cant help???
    So to wrap this up, I have lost trust in BT and the usage "statistics" and would love for them to try and improve this situation, even make some effort to try to rebuild my lost trust!
    I'm almost annoyed enough by this if there is a general consensus/concern to take it further to a watchdog type body, the analogy is putting fuel in the motor without any reading/display at the pump... i.e would you really trust the system is regulated and not open to abuse?? And if you ask for evidence and they wont provide any??? Come on BT, time to improve your customer service!!!
    Thanks for reading, please let me know if you have similar experiences

    Ok, so this is a list of your addons that will work:
    Ad-Block Plus: This will work. You'll have to update to version 2.2.2 after you install Firefox 18, but it will work fine.
    Autoformer: This will work fine
    iMacros for Firefox: This will also work after an update to 7.6.0.2
    Personas: You don't really need this anymore, Firefox has the ability to load Personas built in now. you can remove that add-ons. If you want the addon you can continue to use it.
    Tabkit: This was abandoned by it's developer, but you can uninstall it and use https://addons.mozilla.org/en-US/firefox/addon/tabkit-2nd-edition, which is the same thing, just compatible with modern versions of Firefox
    Tineye: This will also work after an update to 1.1
    All the other extensions you have are disabled.
    So, good news, it looks you only need to uninstall tabkit and install tabkit 2, and then update the other add-ons after you install Firefox 18.0.2.
    And of course update your plugins ;)

  • What is Node Manager ?

    Hi
    I have been reading documents on Oracle Fusion Middleware 11g. At lot of places 'Node Manager' is mentioned across these documents.
    Please can someone explain here what is Node Manager and what it is its role in OFMW 11g ?
    Cheers
    Mayur

    Hi Mayur,
    For more details please refer to: http://weblogic-wonders.com/weblogic/2010/06/18/weblogic-initials/
    <b><font color=maroon> What is NodeManager?</font></b>
    A Node Manager process is not associated with a specific WebLogic domain but with a machine. Node Manager process to control server instances in any WebLogic Server domain until the server instances reside on the same machine as the Node Manager process.
    Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.
    A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process.
    <b><font color=maroon>Why We Need Nodemanagers?</font></b>
    1). It can Start, Shut Down, and Restart an Administration Server which has assigned a Machine.
    2). It can Start, Shut Down, and Restart an Managed Server which has assigned a Machine.
    3). It can Restart Administration and Managed Servers. (Crash Recovery of Servers is an Interesting feature)
    4). It can be used to Monitor Servers and View Log Data
    <b><font color=maroon>Types of NodeManagers?</font></b>
    *1). Java Based Nodemanager:* This can be used in Windiows as well as UNIX based Operating systems. Java Based Node Manager is not supported on Open VMS, OS/390, AS400, UnixWare, or Tru64 UNIX.
    *2). Script Based Nodemanager:* This nodemanager can be used in UNIX based operating systems. The advantage of the script-based Node Manager is that it can remotely manage servers over a network that has been configured to use SSH.
    For More Information on NodeManager please refer to:
    http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html
    And
    http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
    Thanks
    Jay SenSharma

  • How to configure Node manager on Linux on ssl port

    Hi,
    I have installed SOA BPM 11.1.1.3 on linux with ssl enabled. I am trying to configure Node Manager but it's not working.
    Here are the steps I did to configure.
    1. Created a machine
    2. Added managed servers to the machine i.e. soa,bam
    3. Enroll domain using nmEnroll using
    cd $BEA_HOME/user_projects/domains/<domain_name>/bin/
    . setDomainEnv.sh
    java weblogic.WLST
    wls> connect(’weblogic’,'weblogic1’, ‘t3://mymachine.mydomain:7001’)
    wls> nmEnroll(’$BEA_HOME/user_projects/domains/<domain_name>’, ‘$BEA_HOME/wlserver_<version>/common/nodemanager’)
    here 7001 is the admin server non-ssl port but when I try 7002 ssl port it doesn't connect. But I need to enroll it on ssl port as I have ssl enabled.
    4. reset the node manager user/password same as weblogic console
    5. started the node manager using $WL_HOME\server\bin\startNodeManager.sh
    But when I log back into console and try to start my manage server it gives the following error
    SEVERE: java.io.FileNotFoundException: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/./config/jps-config.xml (No such file or directory)
    <Aug 6, 2010 5:30:16 PM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The dynamic loading of the OPSS java security policy provider class oracle.security.jps.internal.policystore.JavaPolicyProvider failed due to problem inside OPSS java security policy provider. Exception was thrown when loading or setting the JPSS policy provider. Enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: JPS-01538: The default policy provider was not found.I did not add my Admin server to be part of the machine.
    Any help if I am missing anything or doing anything wrong.
    Thanks

    Hi,
    Do I need to add Admin Server also part of the Machine where I added bam,soa servers. I tried again following the steps but gets the below error again. Appreciate if someone can list the steps as the docs are a bit vague:
    <Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh >
    Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
    INFO: Starting WebLogic server with command line: /usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/bin/startWebLogic.sh
    <Aug 6, 2010 6:14:01 PM> <INFO> <wcbpm_domain> <bam_server1> <Working directory is '/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain'>
    Aug 6, 2010 6:14:01 PM weblogic.nodemanager.server.ServerManager log
    '/usr3/app/oracle/Middleware/user_projects/domains/wcbpm_domain/servers/bam_server1/logs/bam_server1.out'
    <Aug 6, 2010 6:14:02 PM> <INFO> <wcbpm_domain> <bam_server1> <Server failed during startup so will not be restarted>
    Aug 6, 2010 6:14:02 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Aug 6, 2010 6:14:02 PM> <WARNING> <Exception while starting server 'bam_server1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
            at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
            at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
            at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
            at weblogic.nodemanager.server.Handler.run(Handler.java:70)
            at java.lang.Thread.run(Thread.java:619)
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    Unknown option or illegal argument: -XX:+UseParallelGC.
    Please check for incorrect spelling or review documentation of startup options.
    Could not create the Java virtual machine.
    <Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <Waiting for the process to die: 590>
    <Aug 6, 2010 6:14:02 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Aug 6, 2010 6:14:02 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>Don't know if I hve missed any steps in node manager configuration.
    Thanks

  • Unable to start SOA server through Node Manager

    Hi All,
    I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
    I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
    Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
    Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
    I am getting an error while trying to start soa server with nmStart() command, below is the error message...
    "Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
    I executed the dumpStack() command, and i am getting the output as "No stack trace available"
    If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
    I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
    I followed some of the blogs like...
    http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
    http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
    Experts, please give your advice.
    Many Thanks,
    N

    Hi Narsing,
    I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
    Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
    As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
    Regards,
    Neeraj Sehgal
    Hi Neeraj,
    I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
    I have made sure the property StartScriptEnabled= true.
    I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to      FAILED_NOT_RESTARTABLE status.
    If i see the log messages in the nodemanager.log, this is the below message...
    <Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
    <Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)
    The log message in the soa_server1.out file is as below...
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
    <Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
    Many Thanks.

  • Server state failed when starting through node manager

    Hi,
    I'm getting the below error while starting the managed server through node manager
    <Sep 14, 2010 3:49:34 PM> <Warning> <Exception while starting server 'ms01': java.io.IOException: Server failed to start up. See server
    output log for more details.>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
    at weblogic.nodemanager.server.Handler.run(Handler.java:66)
    at java.lang.Thread.run(Thread.java:619)
    I have checked the server logs and it shows the below error code
    ./admin-stdout.log:<Sep 15, 2010 4:15:56 PM PDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server ms01 : Exception while starting server 'ms01': java.io.IOException: Server failed to start up. See server output log for more details.>
    I have also checked WebLogic documentation for BEA-300048. It says "Cause: The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration".
    but I'm using Java based node manager
    All this is coming up when I enable StartScriptEnabled to true in nodemanager.properties.
    What could be reason for failure?

    Hi.
    If you are not using the latest service pack (sp2) please do so. If you are and are still seeing this
    problem please open a case with support.
    Thanks
    Michael
    Tim Dawson wrote:
    I get this message whenever I try to use the console to start a managed server
    on a remote system.
    <Jan 12, 2002 8:18:26 AM PST> <Emergency> <WebLogicServer> <Unable to create a
    server socket for: weblogic2.dev.wamnet.com/172.17.27.84, port: 7001. java.net.BindException:
    Cannot assign requested address: JVM_Bind Perhaps the address weblogic2.dev.wamnet.com/172.17.27.84
    is incorrect or another process is using port 7001.>
    I've checked and checked and the only thing running on that box is the node manager!
    The console will start a managed server on the local system (i.e. the system
    that the admin server is running on) without any complaints.
    Any ideas? Thanks,
    Tim--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Native IO Disabled when using node manager to start managed server

    Hi,
    I am able to start my node manager and the managed server from the Admin Console. OS is AIX, WebLogic 9.2 MP3. The managed server starts OK, but Native IO is disabled even though it is enabled in the Admin Console for that manager server:
    ####<Jul 28, 2009 8:25:00 AM CDT> <Info> <Socket> <pstps09.statefarm.com> <PIA2> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1248787500274> <BEA-000447> <Native IO Disabled. Using Java IO.>
    I set NativeVersionEnabled to False in nodemanager.properties as specified in the BEA documentation, but can get Native IO to work. The log file clearly indicates that the JDK version is 32-bit:
    java.fullversion = J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20071007 (JIT enabled)
    Any ideas how to fix this or is this working as designed for AIX platforms?
    Thanks!
    -Mary Manchukian

    The following document asks to set NativeVersionEnabled to False:
    http://edocs.bea.com/wls/docs61/adminguide/remotestart.html#1043956:
    The Node Manager is available for use only on Windows and UNIX platforms. Native libraries are available for running the Node Manager on Windows, Solaris, HP-UX, AIX and Red Hat Linux operating systems. For UNIX operating systems other than Solaris and HP UX, you will need to use the following argument on the java command line when starting the Node Manager:
    -Dweblogic.nodemanager.nativeVersionEnabled=false
    If we do not set NativeVersionEnabled to False, the managed server doesn't start at all and fails with the error:
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:296)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:511)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:115)
    at weblogic.nodemanager.server.Handler.run(Handler.java:66)
    at java.lang.Thread.run(Thread.java:810)
    All I want is to be able to start the managed server from the Admin Console > Remote Start tab.
    Thanks,
    -Mary

  • Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

    Hi all,
    I have TFS2012 and run several projects.
    We encounterwed with such an error while using Build server.
    Overall Build Process
    Initial Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    00:00
    Get the Build
    00:00
    Update Build Number
    Initial Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Final Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Result = Ephone_DIT_Deploy_20150424.1
    01:56
    Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
    Initial Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    00:00
    Get the Build Directory
    Initial Property Values
    Result = d:\temp\217\CTI\Ephone_DIT_Deploy
    01:53
    If Not String.IsNullOrEmpty(ConfigurationFolderPath)
    Initial Property Values
    Condition = True
    01:53
    Run TfsBuild for Configuration Folder
    Initial Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp" 
    00:08
    Getting sources
    00:02
    Labeling sources
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
    00:19
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:10
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    MSBuild Log File
    00:08
    Generating list of changesets
    00:20
    Built Skins\SkinEPhone.cs for default targets.
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
    Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
       at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
       at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
       at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
       at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
       at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
       at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
    00:03
    Creating work item
     Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
    Exception Stack Trace:    at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
       at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
       at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
    Final Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    Final Property Values
    Condition = True
    Final Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
    Final Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    Please have a look and guide where to find a problem
    Thanks ahead

    Hi Hooi,
    I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
    From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
    Best regards,

  • Where do I find the "Node Manager" service?

    Can anyone tell me where to find the "Node Manager Service" In Call Manager 5.1.2 or IPCC 4.5?
    My db_CRA database in IPCC is not updating the real time ICD statistics table and Bug CSCsc09160 seems to indicate that stopping and starting the "Node Managers" may fix the issue.
    From the bug report:
    Symptom:
    Under the db_cra two tables (RtCSQsSummary and RtICDStatistics) are not updating. They stop updating concurrently with engine failovers and reboots. Only a hard reboot or a
    service failover brings them back into an active state.
    When the RtCSQsSummary and RtICDStatistics tables do update on the
    primary DB they do not update on the secondary DB and the data on them
    doesnt get refreshed.
    Conditions:
    stopping Node manager on node 1, data fails to be written to node 2. Then when we start NM back up on node 1 data is still not written to either data store
    Workaround:
    Not much as a workaround, because the solution requirs stop on both Node
    Managers and bring up node 1 first and the data starts writing to DB
    again.
    Thanks,
    Brian

    Post Author: jsanzone
    CA Forum: Authentication
    Sven,
    The reference to Session Manager is more of a concept of operations versus an entity.  The portion of code that you copied and pasted in your post is actually part of the verbiage used in an ASP script that BusinessObjects expects you to create in order for you to obtain your objective.  You can use this coding to create your own customized script or you might be able to search around on the web for a more complete solution.

Maybe you are looking for

  • Bapi_equi_change - how can i change wbs_element?

    Hi experts, i try to change wbs element without success using this function. any idea what i doing wrong? thanks. Michal/

  • NEED A SAMPLE BADI PROGRAM

    Hi everybody,     I am learning BADi'S, so i need a sample program so that i can do it and learn how to design and implement a BADI.   I am thankful if any body help me regarding this. waiting for reply. thanks and regards, mahaboob subhani shaik.

  • Header text - DO to Billing

    Hi, can anyone advise if standard SAP behaviour such that the billing header text is copy from SO instead of DO even though the same text id and access seq appears in SO and DO header yext control configuration as well?  I found out this is bcos even

  • I can't open the file in word because it is corrupt and cannot be opened, what can i do?

    I can't open the file in word because it is corrupt and cannot be opened, what can i do?

  • Problem with Vista x64 and Audible in iTunes

    I've made a clean install of Vista x64. Installed iTunes and started it off reloading my music. When it came to .aa files from Audible it prompted me for my audible login - which I gave. It then rejected my login and skipped all my audible stuff. I'v