Cann't connect to the Admin Server!

Hi,everyone:
when I "startconsole",error appears:
"Cann't connect to Admin Server:http://myhostname.mydomain:port number,the URL is not correct or the server is not running "
how can I resolve this problem?
Thanks

This may seem like a dumb question, but
Is the Admin Server running on myhostname.mydomain:port number?

Similar Messages

  • "Unauthorized Host" error when you try to connect to the admin server

    "Unauthorized Host" error when you try to connect to the admin server
    <p>
    If you see this error message when you try to connect to a Netscape
    administration server:<P>
    Internal Error
    The administration server was unable to fulfill your request.
    Reason: Unauthorized host
    --------------------------<P>
    Here is how to solve the problem and gain access. First you should
    temporarily open access to all sites, and then once you make sure that
    this lets you get into your administration server, try again to set up
    the domain name or IP address access restrictions you want.<P>
    For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
    Communications servers (1.x) on Unix:<P>
    <OL>
    <LI>Open the "ns-admin.conf" file with a text editor. You can
    find this file in the "admserv" directory under your Netscape
    server root. The directory is named "admin-serv" in 3.x servers.<P>
    <LI>Delete the "Hosts" and "Addresses" lines you see there (either one
    of them might not be present). Don't confuse the "Addresses" line,
    which you should delete, with the "Address" line, which you should NOT
    delete.<P>
    <LI>Save the file, then restart your administration server (on Unix run
    "stop-admin" then "start-admin"; on Windows NT go into the Services
    control panel and stop/start the "Netscape Admin Server" service).<P>
    </OL><P>
    For Commerce Server or Communications Server (1.x) on Windows NT:<P>
    <OL>
    <LI>Go into the registry editor. On Windows NT 4.0, run the command
    "regedit". On Windows 3.51, run the command
    "regedt32".<P>
    <LI>Navigate down to the section
    "HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".<P>
    <LI>Delete the "Hosts" and "Addresses" entries you see there (either one
    of them might not be present). Don't confuse the "Addresses" entry,
    which you should delete, with the "Address" entry, which you should NOT
    delete.<P>
    <LI>Close the registry editor, then restart your administration server
    by going into the Services control panel and stopping then starting the
    "Netscape Administration" service.<P>
    </OL>
    Now try again to access your administration server. Remember, the URL
    will be something like "http://servername:12345/", where
    "12345" is where the administration server's port number goes.<P>
    If you still get the same "Unauthorized host" error, then make sure that
    your "ns-admin.conf" file really doesn't contain any "Hosts" or
    "Addresses" lines any more, and try stopping your administration server
    again then starting it back up.<P>
    Once you have access to your administration server, you can try again to
    set up the access controls you want.<P>
    <UL>
    <LI>For the administration server on a 3.x server installation, select
    "Admin Preferences" from the General Administration page (the first page
    you see when you connect to the admin server), then click on "Superuser Access
    Control" and enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the subsrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that
    your DNS can resolve those hostnames -- it's generally safer to stick
    with IP address restrictions. When you're finished configuring this,
    click "OK" then restart your admin server.<P>
    <LI>For the administration server on a 2.x server installation, select
    "Configure Administration" from the Server Selector page (the first page
    you see when you connect to the admin server), then click on "Access
    Control" and enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the subsrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that
    your DNS can resolve those hostnames -- it's generally safer to stick
    with IP address restrictions. When you're finished configuring this,
    click "OK" then restart your admin server.<P>
    <LI>For the administration server on a 1.x server installation, select
    "Configure Administration Server" from the bottom of the Server Manager
    page, then enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the substrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that your
    DNS can resolve those hostnames -- it's generally safer to stick with IP address
    restrictions.
    When you're finished configuring this, click "Make These Changes" then
    restart your admin server.<P>
    </UL><P>
    If you still find yourself getting an "Unauthorized host" error message,
    you can use the above steps to open up access and try different
    settings.<P>

    "Unauthorized Host" error when you try to connect to the admin server
    <p>
    If you see this error message when you try to connect to a Netscape
    administration server:<P>
    Internal Error
    The administration server was unable to fulfill your request.
    Reason: Unauthorized host
    --------------------------<P>
    Here is how to solve the problem and gain access. First you should
    temporarily open access to all sites, and then once you make sure that
    this lets you get into your administration server, try again to set up
    the domain name or IP address access restrictions you want.<P>
    For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
    Communications servers (1.x) on Unix:<P>
    <OL>
    <LI>Open the "ns-admin.conf" file with a text editor. You can
    find this file in the "admserv" directory under your Netscape
    server root. The directory is named "admin-serv" in 3.x servers.<P>
    <LI>Delete the "Hosts" and "Addresses" lines you see there (either one
    of them might not be present). Don't confuse the "Addresses" line,
    which you should delete, with the "Address" line, which you should NOT
    delete.<P>
    <LI>Save the file, then restart your administration server (on Unix run
    "stop-admin" then "start-admin"; on Windows NT go into the Services
    control panel and stop/start the "Netscape Admin Server" service).<P>
    </OL><P>
    For Commerce Server or Communications Server (1.x) on Windows NT:<P>
    <OL>
    <LI>Go into the registry editor. On Windows NT 4.0, run the command
    "regedit". On Windows 3.51, run the command
    "regedt32".<P>
    <LI>Navigate down to the section
    "HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".<P>
    <LI>Delete the "Hosts" and "Addresses" entries you see there (either one
    of them might not be present). Don't confuse the "Addresses" entry,
    which you should delete, with the "Address" entry, which you should NOT
    delete.<P>
    <LI>Close the registry editor, then restart your administration server
    by going into the Services control panel and stopping then starting the
    "Netscape Administration" service.<P>
    </OL>
    Now try again to access your administration server. Remember, the URL
    will be something like "http://servername:12345/", where
    "12345" is where the administration server's port number goes.<P>
    If you still get the same "Unauthorized host" error, then make sure that
    your "ns-admin.conf" file really doesn't contain any "Hosts" or
    "Addresses" lines any more, and try stopping your administration server
    again then starting it back up.<P>
    Once you have access to your administration server, you can try again to
    set up the access controls you want.<P>
    <UL>
    <LI>For the administration server on a 3.x server installation, select
    "Admin Preferences" from the General Administration page (the first page
    you see when you connect to the admin server), then click on "Superuser Access
    Control" and enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the subsrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that
    your DNS can resolve those hostnames -- it's generally safer to stick
    with IP address restrictions. When you're finished configuring this,
    click "OK" then restart your admin server.<P>
    <LI>For the administration server on a 2.x server installation, select
    "Configure Administration" from the Server Selector page (the first page
    you see when you connect to the admin server), then click on "Access
    Control" and enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the subsrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that
    your DNS can resolve those hostnames -- it's generally safer to stick
    with IP address restrictions. When you're finished configuring this,
    click "OK" then restart your admin server.<P>
    <LI>For the administration server on a 1.x server installation, select
    "Configure Administration Server" from the bottom of the Server Manager
    page, then enter hostname and IP address restrictions. If you want
    allow access to multiple clients, you'll have to use wildcard patterns
    (separate the substrings with a pipe character, like
    "(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
    If you're setting up hostname restrictions, you'll need to make sure that your
    DNS can resolve those hostnames -- it's generally safer to stick with IP address
    restrictions.
    When you're finished configuring this, click "Make These Changes" then
    restart your admin server.<P>
    </UL><P>
    If you still find yourself getting an "Unauthorized host" error message,
    you can use the above steps to open up access and try different
    settings.<P>

  • Connecting to the admin server via SSL

    Hi there,
    I'm trying to connect to our Admin server in a testing environment in a DMZ from another linux box. We've tried the same method on previous testing environments and its worked ok with a .conf and .key file.
    java -Dssl.debug=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeySore=DemoTrust weblogic.WLST
    wls:/offline> connect(userConfigFile='../acols_cobb.conf', userKeyFile='../acols_cobb.key', url='https://cobb.workcover.dmz:9191')
    Connecting to https://cobb.workcover.dmz:9191 with userid system ...
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 8620279>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will NOT be Muxing>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <write SSL_20_RECORD>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <4600242 SSL3/TLS MAC>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <4600242 received HANDSHAKE>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <4600242 SSL3/TLS MAC>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <4600242 received HANDSHAKE>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 50788157593152036917613181257703108893
    Issuer:C=US, ST=MyState, L=MyTown, O=MyOrganization, OU=FOR TESTING ONLY, CN=CertGenCAB
    Subject:C=US, ST=MyState, L=MyTown, O=MyOrganization, OU=FOR TESTING ONLY, CN=cobb
    Not Valid Before:Thu May 21 11:13:10 EST 2009
    Not Valid After:Wed May 22 11:13:10 EST 2024
    Signature Algorithm:MD5withRSA
    >
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
    <Dec 31, 2009 11:21:27 AM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 50788157593152036917613181257703108893
    Issuer:C=US, ST=MyState, L=MyTown, O=MyOrganization, OU=FOR TESTING ONLY, CN=CertGenCAB
    Subject:C=US, ST=MyState, L=MyTown, O=MyOrganization, OU=FOR TESTING ONLY, CN=cobb
    Not Valid Before:Thu May 21 11:13:10 EST 2009
    Not Valid After:Wed May 22 11:13:10 EST 2024
    Signature Algorithm:MD5withRSA
    >
    <Dec 31, 2009 11:21:27 AM EST> <Warning> <Security> <BEA-090542> <Certificate chain received from cobb.workcover.dmz - 203.82.216.131 was not trusted causing SSL handshake failure. Check the certificate chain to determine if it should be trusted or not. If it should be trusted, then update the client trusted CA configuration to trust the CA certificate that signed the peer certificate chain. If you are connecting to a WLS server that is using demo certificates (the default WLS server behavior), and you want this client to trust demo certificates, then specify -Dweblogic.security.TrustKeyStore=DemoTrust on the command line for this client.>

    Hi,
    You are not able to establish connection with the Admin server because there is no trust between the two.
    D:\weblogic\wls924\user_projects\domains\saml_1.1_source_post>java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.CustomTrustKeyStoreType="JKS" -Dweblogic.security.TrustKeyStore=CustomTrust -Dweblogic.security.CustomTrustKeyStoreFileName="D:/weblogic/wls924/user_projects/domains/saml_1.1_source_post/trust.jks" weblogic.WLST
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    wls:/offline> connect()
    Please enter your username [weblogic] :weblogic
    Please enter your password [weblogic] :
    Please enter your server URL [t3://localhost:7001] :t3s://localhost:7002
    Connecting to t3s://localhost:7002 with userid weblogic ...
    Successfully connected to Admin Server 'AdminServer' that belongs to domain 'sam
    l_1.1_source_post'.
    wls:/saml_1.1_source_post/serverConfig>
    Regards,
    Puneeth P

  • Problems connecting to the Admin Server

    My browser can't connect to the Admin Server. Why not?
    <P>
    If you cannot connect to the Admin Server, ensure that the masks of
    Hosts and Addresses entries in /admin-serv/config/ns-admin.conf
    include the host and address you are connecting from. After changing
    these parameters, stop and start the Admin Server by running the shell
    scripts /stop-admin and
    /start-admin.

    Thanx for the reply Shane.
    i had just stumbled upon the imap log before seeing your answer. i've found and fixed the problem.
    the imap log showed the following message
    Access to imap service for user@domain denied from client address (*mailAllowedServiceAccess)while the http log showed the following message
    Access to smime service for user@domain denied from client address (mailAllowedServiceAccess)after some digging, i understood that th mailAllowedServiceAccess is a user profile property.
    For my non-admin user, it was set to +imaps:ALL$+pops:ALL$+smtp:ALL$+http:ALL i modified it to include simple imap and the problem was solved.
    ps: some threads that pointed me in the right direction
    [http://forums.sun.com/thread.jspa?threadID=5361414]
    [http://forums.sun.com/thread.jspa?forumID=708&threadID=5099841]
    [http://forums.sun.com/thread.jspa?forumID=708&threadID=5401855]
    Thank you very much for your help
    Pier

  • Directories on 2 machines. Connect to 1 using console program on the other : "Cannot connect to the Admin Server.The url is not correct or the server is not running." URL is ok, server  is running.

     

    Which version of iDS ?
    Could you show us the URL ?
    I think 4.x Admin Server has the IP address of the hosts that can connect in its configuration. If both servers have 2 different configuration Directory and 2 admin servers, that is eventually where to look for a solution.
    Regards,
    Ludovic.

  • Error Trying to get a managed server connected to the admin server

    I am getting the following error when I try starting up a managed server. I
    put -Dweblogic.management.server=http://host:port
    The managed server starts with out setting the management.server setting.
    It gives the error below when I put the management server setting in
    <Error deploying application DefaultWebApp_online: error retrieving
    component [Caching Stub]Proxy for
    rnd2Domain:Name=DefaultWebApp_online,Location=online,Type=WebAppComponentCon
    fig,ApplicationConfig=DefaultWebApp_online>
    Thanks,
    Scott Jones
    [email protected]

    Can you post the error message from both admin as well as managed servers?
    Viresh Garg
    Principal Developer Relations Engineer
    BEA Systems
    Scott Jones wrote:
    I am getting the following error when I try starting up a managed server. I
    put -Dweblogic.management.server=http://host:port
    The managed server starts with out setting the management.server setting.
    It gives the error below when I put the management server setting in
    <Error deploying application DefaultWebApp_online: error retrieving
    component [Caching Stub]Proxy for
    rnd2Domain:Name=DefaultWebApp_online,Location=online,Type=WebAppComponentCon
    fig,ApplicationConfig=DefaultWebApp_online>
    Thanks,
    Scott Jones
    [email protected]
    [att1.html]

  • How can i start the Admin server? may be this will be like clue: "When i try to start the iplanet suite with the start-admin script, i receive the following error:

    bash-2.03# ./start-admin
    AdmInit: Failed to perform security initialization for communicate with LDAP in SSL mode (error code = -1) Exit
    so i can not login to console (./startconsole) because the "admin-serv" is not up: "Can not connect to the Admin Server "http://myserver.com:myportnumber/" The URL is not correct or the server is not running." any ideas..."
    ---------------------Seumas Froemke on 1/15/2002 said: ----------------
    "I'm not familiar with the error, but I'll throw in my two cents and hope it leads you somewhere.
    First, be sure you start things in the correct order. LDAP->Admin->Console.
    Be sure you've set nsadminservaccessaddresses and nsadminaccesshosts.
    Do you have problems starting everything up when you aren't using SSL mode?
    You can put startconsole into debug mode with startconsole -D 9 but I don't think there is a start-admin debug mode. You'd have to settle for a truss.
    All in all, you should ask this in the LDAP (User Management & Policy) forum."
    --------------------and i wrote: -------------------------------------
    Homero Borgo Valdez on 1/18/2002 said:
    "I start things in the correct order.
    how can i check the nsadminservaccessaddresses and nsadminaccesshosts settings (i'm new on this suite as you can see).
    if i moved some checkbox when the console was ok how can i view that settings in text mode?
    by the way i have another server that can sun console well (port 2125) so what file can i compare to change some wrong settings?
    thanks anyway, another idea?"
    --------------------so following the commnets i put this history here ----
    help please!!

    jvm file is in your system file folder.so you can delete that jvm file and to run as it is.

  • BEA-141151 The admin server could not be reached at ...

    I have been at this for 3 days now... I created a new ManagedServer, but I'm not able to make it connect to the Admin server.
    The Admin server is running and listening on port 5306. I can connect to the Admin Console (web).
    I can also connect to the Admin server via WLST, using this command: connect('operator','operator01','t3://localhost:5306')
    However, when I try to run the managed server from a script, it does not see the Admin server. This is the command I run:
    java -Dweblogic.Name=ManSer1 -Dweblogic.management.server=t3://localhost:5306 -Dweblogic.RootDirectory=<path to my domain> weblogic.Server
    This is the error I get:
    <BEA-141151> <The admin server could not be reached at http://localhost:5306.>
    I believe it's trying to connect using "http", because I've never actually connected in the past. Here is a website explaining this: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13749/weblogicserver.htm#i1031832
    Note: Regardless of which protocol you specify, the initial download of a Managed Server's configuration is over HTTP or HTTPS. After the RMI subsystem initializes, the server instance can use the T3 or T3S protocol.
    I'm not sure what else to try... Firewalls are not in play, since this is traffic moving around on the local machine. I'm running on SunOS. Weblogic is version 9.2 MP3.
    Appreciate any help.

    Is the NodeManager , AdminServer running ?The NodeManager is not running. Is it required?
    Also, I haven't closed the command prompt.
    I noticed the issue when I tried to deploy my project. Connected to Localhost/7001 but in the deploy project window, I dont see any soa_server instance
    running. Also, in the console the soa_server status is shutdown.

  • Unable to connect to the Essbase server from Admin console

    Hi,
    I have installed Essbase Server 9.3, Client 9.3 and Administration Server 9.3 in my laptop.
    The Essbase server is working fine. I am able to see all the sample applications from Excel add in. (This mean client is also working fine).
    But, the problem is when i try to connect to the Essbase server, its not allowing me by producing an error:
    "Unable to connect to the Essbase server please check the user name & password"
    username: admin
    password; password.
    i tried several times...but its not working.
    Please advise me.
    FYI, The admin server service is started already.

    Hi Subrahmanyam,
    Here , there are 2 things
    1. Check, your essbase server is up and running ,and your admin service is up. Now , when you open the 'essbase admin console ' , provide user name and password as
    admin
    password
    2. After you are connected to the console i.e admin console .
    You see
    enterprise view -> essbase analytic server -> under this , you might see your host name ( i.e of your laptop).
    This host is your essbase server , and if you want to connect to it .Provide 'username' and 'password' ,which you have give after your essbase installation
    So, conclusively, here we are dealing with 2 different sets of 'username' and 'passwords'
    In step 1-> to connect to console , use 'admin' 'password'
    In step 2-> to connect ot essbase server, use the credentials wchih you had given after installation of essbase server
    Hope this clarifies you, as this is a lil confusion to many
    Sandeep Reddy Enti
    HCC
    http://analytiks.blogspot.com

  • "System cannot connect to the application server" (Admin Client only)

    Hello Experts,
    I have a strange issue: I am getting "system cannot connect to the application server" when I am trying to launch BPC Admin.
    I successfully connect to the same application server with Excel client on the same PC.
    I am able to connect via Admin from another PC.
    The installation in question is a new installation. The only difference between my PC and a troubled one is IE7 vs. IE8 - IE8 is the one giving issues.
    BPC site is in Local Intranet zone. Windows Authentication is enabled. What am I missing? Local Policy? IE8 settings? Folder permissions (I'm local admin on both PCs)?
    It's BPC 7.5 SP05.
    Thanks in advance,
    Akim
    P.S. OS: Windows Server 2003 SP2 32-bit (Citrix box).
    Edited by: Akim Zubarchuk on Mar 30, 2011 12:28 AM

    Hi Akim,
    Check client diagnostic for admin client can provide good information.
    Any way if you are able to connect with excel client not with admin client I will say:
    1. Check the rights of user used to connect with admin console
    2. Check proxy settings
    3. Disable antivorus or firewall into that computer.
    4. Make sure the installation of admin client was correct done.
    In my opinion it is a big probability to be point 3 or 4.
    Regards
    Sorin Radulescu

  • Trying to run the SOA/BPM managed server withOUT running the Admin server

    (This is for demo/development purposes... Using 11.1.1.4 in Windows 7 with 4gb)
    Because of memory constrains I am trying to run the BPM/workspaces application without needing the Admin to be running.
    When they both run, I can use the credentials I create with the Admin server but the response time is prohibitive and all my memory is used...
    It seems to run much faster when only the bpm managed server is running but then I cannot login ...
    So my question is simply: Whats the easiest way to set it up so I can use credentials elsewhere without requiring the admin server to be running?
    ( I could connect to an OID instance I have outside this server or the seeded demo they refer to in other posts ... but do these also require the admin server to be running???)
    aTdHvAaNnKcSe ! (thanks IN advance)
    Claudio
    Edited by: clichten on Aug 20, 2011 9:35 AM

    I don't know if what you want is possible. Only did a suggestion that works fine for me. I'm running SOA Suite and BPM Suite 11.1.1.5 on WLS 10.3.5
    Configure a new WLS domain and see if the BPM Dev template is available in your version.
    I've tuned my startup script (setSOADomainEnv.cmd) as follows:
    set JAVA_OPTIONS=%JAVA_OPTIONS%
    set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
    set PORT_MEM_ARGS=-Xms1536m -Xmx1536m
    if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
    set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
    set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
    Use visualvm that's available from your jdk/bin directory to monitor your jvm and optimize it accordingly
    Regards,
    Melvin

  • Possible workaround for: Launch Debugger Error "Unable to connect to the RDS server"

    I do not yet have a reproducible case for this. *Sometimes* ColdFusion Builder throws the "Unable to connect to the RDS server" error, when attempting to start a debug session against a remote server. However, "RDS Dataview" and "RDS Fileview" views correctly list the servers and their related data/file, and testing RDS connection result is "Test connection was successful". The workaround is:
    1. Login to the ColdFusion Administrator
    2. Navigate to "Debugger Settings" page (beneath "Debugging & Logging")
    3. Click on "Stop Debugger Server" -or- "Restart Debugger Server"
    4. Restart ColdFusion Application Server
    Notes:
    a) Step #3 must be done via ColdFusion Administrator, not via ColdFusion Admin API (stopLineDebugger()|restartLineDebugger())
    b) Step #4 can be done via ColdFusion Administrator -or- ColdFusion Builder
    c) Note that there is a CF9 Release Note for Bug #78488: "When a server having "Windows service option" ENABLED is added as a remote server, then Start-Stop-Restart operation cannot be done on it."  However, I've found that "Restarting" a remote server, that is running as a Windows service, is possible in ColdFusion Builder (at least this is so on standalone developer edition).  Like Bug #78488 says, I am unable to "Stop|Start" a remote server that is running as a Windows service. I'm just mentioning all of this, due to my suggestion in "b", that CF can also be restarted via ColdFusion Builder.
    It is interesting that attempts to stop|restart the debugger server, via CF Admin API, do not resolve the issue. So, it seems that the "Stop Debugger Server" and "Restart Debugger Server" buttons, in CF Admin, are doing more than calling the corresponding CF Admin API methods.
    Attached is an image of the error.
    Just posting all of this as an FYI, in case it helps anyone.
    Thanks!,
    -Aaron Neff
    (OH.. I'm unable to attach images at this time *DOH!* ..well, I'll try to remember to update this post w/ the image, once I see that attachments are allowed.)
    I'll try to describe the error message window:
    - It is 494x452 pixels
    - Title of the window is "Error occurred while launching the Debugger"
    - Body content of the window is as follows:
    Unable to connect to the RDS server 'ServerNameHere'
    Ensure that the server is currently running and that line debugging and RDS are enabled. You may also need to check your RDS connection settings in Eclipse to ensure that they are correct.
    Error Message:
    -1:Error connecting to JVM for debugging at localhost:5005. Could not attach to the VM at port 5005. You must specify this debugger port in the JVM settings of your application server, for example: -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005. You will also need to make sure that another debugger is not currently connected to the CF JVM at the same port (5005).
    Root cause ->
    Connect refused: connect

    hi,
    I have been facing the same problems while connecting to Oracle Web Conferencing and is getting error message :Unable to connect to the server. The Web COnferencing Console will now close. Please try again later. If the problem persist, contact your system administrator.
    Diagnostic report shows failed on the connectivity part
    Connectivity
    mx-direct Failed
    0:00:00.719 Connecting to web331.oracle.com:1025
    0:00:00.922 Name resolved to 148.87.108.234
    0:00:21.906 connect() failed (0x8007274C)
    0:00:21.906 Connection failed (0x8007274C)
    Pl help me to fix the problem.
    Regards
    Gobind Ahuja

  • MS SQL Server 2008 not getting installed properly - MOF compiler could not connect with the WMI server

    I am trying to install SQL Server 2008 in my local machine. However, I kept running into errors with the following error message:
    "The MOF Compiler could not connect with the WMI Server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such
    as the failure of the WMI Server to start".
    I also ran "rundll32 wbemupgd, UpgradeRepository" to rebuild WMI repository, it doesn't help either. I got the same error message. 
    Any ideas what settings I need to change in order to ensure a successful installation of SQL Server 2008?

    "The MOF Compiler could not connect with the WMI Server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such
    as the failure of the WMI Server to start".
    I also ran "rundll32 wbemupgd, UpgradeRepository" to rebuild WMI repository, it doesn't help either. I got the same error message. 
    Any ideas what settings I need to change in order to ensure a successful installation of SQL Server 2008?
    can you check below two links.Make sure previous failed installation is removed completely.
    http://connect.microsoft.com/SQLServer/feedback/details/356258/the-mof-compiler-could-not-connect-with-the-wmi-server#
    Solution given by Connect MS is:
    Possibly the issue was caused by uninstalling from add-remove programs - at any rate, using aaron bertrand's suggestion below fixed the issue. Also of note - I used the local admin for the install.
    http://sqlblog.com/blogs/aaron_bertrand/archive/2009/02/20/the-xp-sp3-msxml6-sp2-sql-server-debacle.aspx
    yes - remove msxml6 and any other half installed portion of sql 2008 and REBOOT and install sql
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • BPC 75M - Modify Application error "Cannot connect to the Reporting Server"

    I have trouble with Modify Application, also in ApShell. Maybe you have a clue what it can be the problem.
    Configuration: single server BPC 7.5M SP3, Windows Server 2008 SP2, SQL Server 2008 SP2
    Installation user is a domain user.
    No errors during installation, no error in Server Manager diagnostics.
    But when I try to modify an Application from BPC Admin it gives an error for step "Make OLAP database and Journal/Audit reports. / Validate dimension formulas.".
    In tblLogs I see the error message:
    ==============[System Error Tracing]============== [System Name] :
    AdminServerHandler [Message Type] : ErrorMessage [Job Name] :  
    AdminApplicationHandler : ExecuteModIfyApplication [DateTime] :
    10/19/2010 1:19:13 PM [UserId] : MYDOMAIN\MYUSER
    [Exception] DetailMsg : {System.Exception: Cannot connect to the Reporting Server at
    OSoft.Services.Application.AdminMainServer.AdminApplicationHandler.SetChangeDimensionForAudit(String strAppset, String strApp, String  strUserID, Boolean blnIsChangedDimension, String& strErrMsg) at
    OSoft.Services.Application.AdminMainServer.AdminApplicationHandler.ExecuteModIfyApplication(String strAppSet, String strApplicationName, String strApplicationDescription, String strSourceApplicationType, String 
    strNewApplicationType, String strRateApplicationName, String
    strOwnerShipApplicationName, String strCurrencyConversionsCalculation, 
    String strCalculation, String strIntercompanyBookings, String  
    strUSEliminations, String strOpeningBalance, String strValidations,
    String strIntercompanyEliminations, DataTable dtDimensionList, Boolean 
    bReassignSQLIndex, Boolean bProcessApplication, Boolean bDeleteFact,
    String strChangeAppType, String strUserID, String strReportBackID)}
    ==============[System Error Tracing End ]==============
    Edited by: Alexandru Berindei on Oct 26, 2010 7:57 PM
    Edited by: Alexandru Berindei on Oct 26, 2010 7:58 PM

    There were problems accessing the web page   HTTP://server/reports
    Error message:   "Reporting services 2008 user does not have required permissions"
    It was possible to open the page  HTTP://server/reports with local administrator user and  I fixed this problem by performin following:
    - add Content Manager right to bpc installation user
    - disable UAC from Windows Control Panel  > User Accounts
    Still Modify Application gives the same "Cannot connect to Reporting Services".
    I tried:
    - check that BPC Installation User is part of Local Administrators
    - reboot server
    - reinstall BPC after disabling UAC
    - reinstall everything except the Windows Server 2008
    - I installed another computer with the same exact configuration but with a local BPC Installation User and it works.
    Have anyone installed BPC 7.5M SP3 on single Windows Server 2008 SP2 , with SQL Server 2008 SP2 and with BPC Installation user a domain user?
    Maybe you have an idea of what I should check next.
    Thank you,
    Alex

  • No trusted certificate found (91);Cannot connect to the LDAP server

    HI All,
    I am trying to connect to LDAP server with the following code.
    JSSESocketFactory fact = null;
    private LDAPConnection conn = null;
    String keystore = "C:\\j2sdk1.4.2_15\\jre\\lib\\security\\cacerts";
    System.setProperty("javax.net.ssl.trustStore",keystore);
    fact = new JSSESocketFactory(null);
    conn = new LDAPConnection(fact);
    int ldapVersion = 3;//LDAPConnection.LDAP_V3; //defualt values of LDAP settings
    private int ldapPort = 636;
    LDAPAttributeSet ldapAtrbSet;
    String ldapHost;
    String loginDN;
    String loginDN_Password;
    And it is gicving me error :
    Error: netscape.ldap.LDAPException: SSL connection to 192.168.10.8:636, sun.security.validator.ValidatorException: No trusted certificate found (91); Cannot connect to the LDAP server
    netscape.ldap.LDAPException: SSL connection to 192.168.10.8:636, sun.security.validator.ValidatorException: No trusted certificate found (91); Cannot connect to the LDAP server
         at netscape.ldap.factory.JSSESocketFactory.makeSocket(JSSESocketFactory.java:105)
         at netscape.ldap.LDAPConnSetupMgr.connectServer(LDAPConnSetupMgr.java:418)
         at netscape.ldap.LDAPConnSetupMgr.openSerial(LDAPConnSetupMgr.java:350)
         at netscape.ldap.LDAPConnSetupMgr.connect(LDAPConnSetupMgr.java:244)
         at netscape.ldap.LDAPConnSetupMgr.openConnection(LDAPConnSetupMgr.java:170)
         at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:1042)
         at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:924)
         at netscape.ldap.LDAPConnection.connect(LDAPConnection.java:768)
         at com.reflexis.LDAP.LdapTestSSL.createConnection(LdapTestSSL.java:522)
         at com.reflexis.LDAP.LdapTestSSL.checkLdap(LdapTestSSL.java:118)
         at com.reflexis.LDAP.LdapTestSSL.main(LdapTestSSL.java:52)
    Unable to connect to LDAP server
    I have imported atr certificate also by using command:
    "keytool -import -alias jag -file c:\x225.cer -keystore c:\j
    2sdk1.4.2_15\jre\lib\security\cacerts"
    I am running my java code from eclipse. And do i have to set any thing in eclipse for certificate. I Have imported certificate from command prompt.
    Can any one please help me.It is very important for me.
    Please its very urgent.
    THanks,
    Ankush Patni

    As previously said network is a possible cause.Other things could be time on filer is too far off time on DC.AD object for filer has been deleted or change by a Windows admin.If all users are experiencing a problem, you may need to rebind it to AD - run CIFS setup at command prompt

Maybe you are looking for