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

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

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
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.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<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.
<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.
<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).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<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.
<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.
</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.
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.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<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.
<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.
<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.
</UL>
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.

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

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
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.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<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.
<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.
<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).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<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.
<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.
</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.
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.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<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.
<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.
<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.
</UL>
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.

The WSUS administration console was unable to connect to the WSUS Server via the remote API. (Server 2k8)

I have installed a new server for WSUS on Server 2k8, This is a stand alone server on Internet No client system is connected on this server as I have to copy these updates to my LAN which never connects to internet. (Previously I was using server 2k3. for
online & server 2008 on my LAN , now I have changed the server for Online)
Wsus has finished the synchronization & downloaded updates of around 67GB & its downloading more updates. The server shows me some updates are waiting to approved. but when I click the link for those updates I get following error message.
error code is as follows -
The WSUS administration console was unable to connect to the WSUS Server via the remote API.
Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.
System.Net.WebException -- The operation has timed out
Source
System.Web.Services
Stack Trace:
   at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
   at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, Int32 publicationState)
   at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
   at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(UpdateScope searchScope)
   at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
   at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetAndCacheUpdates(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.UpdatesListPage.GetListRows()
I Have tried desabling the firewall,disabling the antivirus protection. Tried by changing the default rule Please Help.

Hi Sagar,
First, please check if the RAM is exhausted. When there is not enough RAM, this issue may occurs.
Please try to run iisreset on the WSUS server, then try to reconnect.
Also, please try to run the server cleanup wizard to remove the unused update.
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Problems connecting to the Admin Server

My browser can't connect to the Admin Server. Why not?

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

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?

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]

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.

Trying to connect to a WebLogic Admin server via WLST

I am trying to write a script that will connect to a Admin Server via WLST using a stored config file. I have the written the following:
import os
HASCONFIGFILE = os.path.isfile("/beadev/wls10/data/UserConfigInfo/configfile.secure")
HASKEYFILE = os.path.isfile("/beadev/wls10/data/UserConfigInfo/keyfile.secure")
if HASCONFIGFILE:
CONFIGFILE = "/beadev/wls10/data/UserConfigInfo/configfile.secure"
print "INFO: CONFIGFILE = %s" % CONFIGFILE
if HASKEYFILE:
KEYFILE = "/beadev/wls10/data/UserConfigInfo/keyfile.secure"
print "INFO: KEYFILE = %s" % KEYFILE
connect(userConfigFile=CONFIGFILE, userKeyFIle=KEYFILE, url='t3://165.79.164.14:21001')
else:
print "ERROR:Unable to obtain authentication parameters."
exit()
else:
print "Unable to find user config and keyfiles."
exit()
connect(userConfigFile='/beadev/wls10/data/UserConfigInfo/configfile.secure', userKeyFIle='/beadev/wls10/data/UserConfigInfo/keyfile.secure', url='t3://165.79.164.14:21001')
How ever when I run the script, I get the following WLSTException:
beaadmin@moorea:/home/beaadmin/bin/scripts/wlst> java weblogic.WLST findFile.py
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
INFO: CONFIGFILE = /beadev/wls10/data/UserConfigInfo/configfile.secure
INFO: KEYFILE = /beadev/wls10/data/UserConfigInfo/keyfile.secure
This Exception occurred at Fri Jul 24 13:10:47 PDT 2009.
weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:78)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:94)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:87)
at weblogic.security.UserConfigFileManager.getUandP(UserConfigFileManager.java:537)
at weblogic.security.UserConfigFileManager.retrieveUandPValues(UserConfigFileManager.java:518)
at weblogic.security.UserConfigFileManager.getUsernameAndPassword(UserConfigFileManager.java:179)
at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:130)
at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:60)
at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
at org.python.core.PyMethod.__call__(PyMethod.java:96)
at org.python.core.PyObject.__call__(PyObject.java:248)
at org.python.core.PyObject.invoke(PyObject.java:2016)
at org.python.pycode._pyx6.connect$1(<iostream>:16)
at org.python.pycode._pyx6.call_function(<iostream>)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyTableCode.call(PyTableCode.java:404)
at org.python.core.PyFunction.__call__(PyFunction.java:184)
at org.python.pycode._pyx18.f$0(/home/beaadmin/bin/scripts/wlst/findFile.py:13)
at org.python.pycode._pyx18.call_function(/home/beaadmin/bin/scripts/wlst/findFile.py)
at org.python.core.PyTableCode.call(PyTableCode.java:208)
at org.python.core.PyCode.call(PyCode.java:14)
at org.python.core.Py.runCode(Py.java:1135)
at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
at weblogic.management.scripting.WLST.main(WLST.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at weblogic.WLST.main(WLST.java:29)
Caused by: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at com.rsa.jsafe.JA_PKCS5Padding.a(Unknown Source)
at com.rsa.jsafe.JG_BlockCipher.decryptFinal(Unknown Source)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:68)
... 33 more
Problem invoking WLST - Traceback (innermost last):
File "/home/beaadmin/bin/scripts/wlst/findFile.py", line 13, in ?
File "<iostream>", line 22, in connect
WLSTException: 'Error occured while performing connect : Error connecting to the servercom.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte. Use dumpStack() to view the full stacktrace'
Any ideas why this is not working or what 'Could not perform unpadding: invalid pad byte.' means?

Nope, that wasn't me and bless me if I'm wrong but I'm generating this error because I have a non-encrypted string where I need an encrypted string. By that I mean the following line 'CONFIGFILE = "/beadev/wls10/data/UserConfigInfo/configfile.secure" Has a non encrypted string '/beadev/wls10/data/UserConfigInfo/' concatenated to the encrypted file configfile.secure? I wonder if it would just be easier to 'cd' into the directory where the config files live and run the connect from there, either way I have something to go on, thanks for that link.

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.

The admin server could not be reached

Dear All,
I have oracle weblogic server running on red hat enterprise Linux, with one managed server. I created a self-signed certificate to access the admin server using SSL connection, after creating the certificate and start running the domain, The admin server run fine, but when i start running the managed server using
$ ./startManagedWebLogic.sh osb_server1 https://server_ip:7006 i got that error, " The admin server could not be reached on https://server_ip:7006
and the managed server running independence of admin server, as well as admin server can not establish jmx:t3 connection with the managed server on its SSL port
also in admin server log i got this error
<Sep 30, 2013 6:51:00 PM EET> <Warning> <JMX> <BEA-149504> <The adminstration server was unable to establish JMX Connectivity with the osb_server1 at the JMX Service URL of service:jmx:t3://172.17.11.13:8011/jndi/weblogic.management.mbeanservers.runtime.>
how can i resolve this error?
thanks in advanced

Hi John,
Thanks. Notable errors in this log are:
Failed to connect.[Root Cause: Connection refused ] com.hyperion.css.spi.util.jndi.pool.JNDIConnectionPool.validateSocketConnection(Unknown Source)
Native Directory is not reachable. Will try to re-connect after 3 seconds... com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
Attempting to connect to Native Directory: Retry Count: 10 com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
Failed to connect to native directory. com.hyperion.css.spi.CSSManager.getProviderInstance(Unknown Source)
Any ideas?
Thanks.
Edited by: 960369 on 21-Sep-2012 02:56
Edited by: 960369 on 21-Sep-2012 03:33

Mobile Access + Wiki Server via SSL Question

If MAS is running with SSL, does that SSL continue for the entire session? Or just the initial passing of credentials?
I'd like to not have the wiki server running SSL for internal use if MAS encrypts all the traffic. The reason for the question is when connecting to the wiki server via MAS, there is no SSL lock on the browser, telling me it's in the clear.

Mobile Access Server does not provide proxy access to 10.6 server Wiki.
hth,
b.

"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

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

I still have problems with getting my website online. I have defined my server. Then I did the test and there was a connection via FTP. I put my files on the external server and there is a connection with the external server. But when I check to see my we

I still have problems with getting my website online. I have defined my server. Then I did the test and there was a connection via FTP. I put my files on the external server and there is a connection with the external server. But when I check to see my website online (with Firefox, Explorer, Chrome browser) I always get the message 'Forbidden, You don't have permission to access / on this server.' Can somebody help me please? I have to get my website online..Thank you!

Hello Els,
it's well known, that in all these cases you describe I'm not a friend of a detailed Troubleshooting (I see Nancy#s smile already).
To be able to be independent in all this things It is one of the reasons why I prefer an external FTP program. The difficulties with which you have to fight encourage me in this opinion, not least because we always search for experts, we don't charge a "jack of all trades".
To manage several websites or to upload my files and sometimes for the opposite way, for a necessary download from my server or to use a "a site-wide synch", I'm using FileZilla. It simply looks easier for me to keep track of all operations precisely and generate or reflect easily the desired tree structure.
Above all, FileZilla has a feature (translation from my German FileZilla) called "compare file list". Here it's possible to use file size or modification time as a criterion. There is also the possibility to "hide identical files", so that only these files which you want to redact remain visible.
And even if it means you have to install a new program, I am convinced that there is an advantage. Here is the link to get it and where you can read informations about how it works:
http://filezilla-project.org/ and http://wiki.filezilla-project.org/Tutorial#Using_the_site_manager
Mac: Mac OS X (Use: Show additional download options)
http://filezilla-project.org/download.php
Of course, you also need all the access data to reach your server and for MIME issues, you should contact your web host/provider.
Good luck!
Hans-Günter
P.S.
Since I use two screens, the whole thing became even more comfortable.

Connecting to the admin server via SSL

Similar Messages

Maybe you are looking for