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

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.

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

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?

Problem connecting to the Admin Session Microsoft Remote Desktop Mac 8.0.12 (Build 25282)

I try to connect to an RDP Admin Session (there are two normal connections at the moment). It will not let me giving me the following errors. Previously I could have a total of 3 sessions, 2 normal and one admin. I can still connect to the admin session
using the older iTap RDP.

Hi,
There is same issue with other users, already forwarded issue to product group for further research.
OSX: Connecting to admin session not working anymore since 8.0.12
https://social.technet.microsoft.com/Forums/en-US/4c3c36f0-d272-4e54-be70-91d2b92f292e/osx-connecting-to-admin-session-not-working-anymore-since-8012
Thanks for your understanding and Support!
Regards.
Dharmesh Solanki
TechNet Community Support
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]

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.

Having problem connecting to the livecache server from APO instance

Could not able to connect to the live cache server from the APO server after installing both the instances separately on two different systems, while using the T-code LC10 to make a connection from APO DDIC login its displaying the following message
""timeout during allocate / CPI-C error CM_PRODUCT_SPECIFIC_ERROR ""
after entering the Livecache name and Livecache hostname correctly in the livecache integration..both the instance are on the same network and able to ping each other with the hostname and IP addressess..
It will be great if somebody help me in solving the problem..
Thanks in Advance
Srikanth

is this query resolved at your end? or you still looking for ans.

My iPod touch 3rd gen is not updating to the latest software, iTunes keeps saying that there was a problem connecting to the update server...

I don't think I ever registered my 3rd gen iPod. I was never able to update it past its original software because iTunes could never recognize it. Unfortunately, my wife had installed data on it (old & recently purchased) so I've been very hesitant to "Restore" it. I recently plugged it into my laptop & it prompted me to install the iOS 5.0.1 software, but after multiple attempts to do so iTunes keeps giving me the same error message "update install failed. Connection to the update software server has timed out". How do I update the software without losing all my wife's data?

If you already have iOS5.0, Go to settings-general-software update, scroll to the bottom and hit download and install and this should update it without the computer. Then when you connect the iPod to iTunes, it should say 5.0.1. If this doesn't work, DON'T ERASE IT. Just bring it in to Apple. I had the same issue trying to update to 5.0. and eventually I got it to work after waiting for a little while. Good luck!

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]

Problem connecting with the company server

I can see the various server when I use the finder, but when I try to access a server by press connect, it tells me that it is an alias.
Any ideas out there?
Powerbook G4 Mac OS X (10.4.7)

Try Go>Connect to Server... then type in either "SMB://" plus the IP, or "AFP://" plus the IP... as a temporary fix.

What is this "There was a problem connecting to the 'PEGASUS' server."?

Hi,
I've been getting this pop up on my work iMac for almost two years and have not been able to figure out what it means. And as far as I know, there isn't a PEGASUS server in the office, it that is where it is saying it should be. It happens on start up after the desktop loads.
Does anyone have any suggestions on how to fix this or what it means? Screenshot is below.
Thanks!

Hey Rob,
Thanks for the quick post! I checked the Login Items and it looked like there were three applications checked off that had uknown types next to their names. I unchecked them and hope to see this fix the pop up box.
I'll respond if this does or does not fix the pop up.
Thanks!

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

I'm trying to set up my Ipod, but when I go to sign in with an apple ID it says 'Could not sign in: there was a problem connecting to the server'.

I just bought a 3rd generation ipod touch. It was professionally refurbished. I'm trying to set it up, and everything seems to be working fine, until we get to the wifi. I live on campus and our wifi is username and password protected. I signed in and everything seemed to work fine, and in the top left hand corner I have all the bars for wifi. However, when I go to sign in with an apple ID it says 'Could no sign in: there was a problem connecting to the server'. I've tried turning it on and off again, tried signing on to our wifi again, but it all isn't working. What can I do?

I also encountered the same problem. Try using a different email address or try signing in later.

Problems connecting to the Admin Server

Similar Messages

Maybe you are looking for