Connecting to the admin context

Hi All
I seem to find myself in a bit of a quandary - in that i cannot currently connect to the admin
context remotely while i have access to the testing context i set up and i am unsure how
to connect so as to be able to talk to both the admin context and the testing context.
I have two vlans i am using both of which have interfaces on the test context -
shall we call them xx.xx.151.0/24 and xx.xx.152.0/24.
Now xx.xx.151.0 is where the servers will be and only exists beyond the vip.
xx.xx.152.0 is connected through to the rest of our network.
Now my initial thought was that we could use another 152 vlan int on the 'internal'
side - that is the admin context - but mt tech supportb has kindly pointed out that
i cannot do this -
I believe you get the same mac address on both sides which may cause issues.
So the layer2 resolution to pass data may not work correctly
I believe you get the same mac address on both sides which may cause issues.
So the layer2 resolution to pass data may not work correctly.
So can someone tell me how i get access to the admin context - do i need
another vlan or ip address not on these ranges - just to manage the admin
context ?
Steve

Hi Steve,
You can share the vlan between 2 contexts and use seperate IP address for the admin context to manage it.
However , Cisco dont recommend to use same VLAN to be shared in two context especially for the admin context ,which generally uses the management VLAN .
HTH,
Regards,
Parves

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

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]

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

ACE10 - Backing up multiple contexts from the Admin context.

I have have several contexts configured on the ACE blade i was wondering if there was a way of backing up all of these from the Admin context.
I was hoping that i could copy the running config to the disk0: from each context and then return to Admin context to copy the individual named contexts in disk0: to a TFTP server.
The reason why i'm asking is that Admin context has the only routeable network through my firewall as the other contexts are standalone.
Thanks

Thanks Rocash that worked.
For others this is what i did, very easy process.
Logged into the Admin context and issued the following command
admin#Backup all
then wait a few minutes for the process to complete.
admin#Show backup status detail.
This will show all the contexts backup along with certs, probes etc saved.
The backup file is saved to disk0: as .tgz file.
To backup this file to a FTP server.
Copy backup-all ftp:
enter the address of the FTP server.
Then choose passive and BIN file options
Once copied to the FTP server use WINRAR application to open the.tgz and you can see the individual contexts and view the config using wordpad.

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?

Cannot connect to the admin page for my E900

A while ago I was doing some port forwarding to set up a game server. I couldn't get the port to stay open and was messing around a bit with different things. Now I can't access the admin page at all. It keeps giving me a "The Connection Reset" error. I've reset my router twice, but that hasn't done much. I can still access the web just fine. I did a quick google search and saw something about my router and modem might be on the same IP. If so, how would I check this, and how would I fix it?

Does your computer still have access to the internet? Maybe your computer is getting another IP address, or worse, it's not getting anything at all. Check it first. Follow this link on how to do that.
Checking your computer’s IP address
http://kb.linksys.com/Linksys/GetArticle.aspx?docid=d02ed3aa3e704caea42f5c007b8c6472_3996.xml
Whatever default gateway/router your getting is the one you need to enter on the address bar.

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.

Admin Context - Do i need to assign interfaces for Mgmt?

I am building out 2 virtual firewalls using contexts in an active/active F/O pair, and would like to know if it is necessary to assign at least one interface to the admin context?
My other contexts will have outside, inside, DMZ and stateful F/O interfaces. And i plan on administering these contexts by SSH to the inside of one of the active Firewall contexts.
Also from what i am reading i see the system/admin context does AAA, Syslog, F/O config, interface allocations, etc. So, in the Firewalls I assume i dont need to configure AAA, syslog, etc. Is this a correct statement?
Thanks,
Mike

We do not assign interfaces to admin context but to do assign interfaces to other context from admin. So innitially you get only admin context from where you allocate interface/resources to other contexts.
Here are the links for ref-
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00808d2b63.shtml
http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a0080834058.shtml
Thanks
Ajay

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.

Cannot connect to the configuration database

I tried to configure my server with active directory after I have successfully configured sharepoint . For a mistake , they made me delete the active directory and now when I try to connect to the admin section or site page it me give the following error :
"Cannot connect to the configuration database"
Deleting the active directory ; I noticed that all the other users have disappeared and the service : SQL AGENT ( Sharepoint ) not run and the error is :
" This installation of SQL Server Agent is disabled. The edition of SQL Server that installed this service does not support SQL Server Agent." Thank you for the Help

Was the active directory server that you removed the last active directory server in the farm? If so then your only two real choices are to rebuild everything from scratch or restore everything from backup.
If it was just that you were trying to make the SharePoint server into a Domain Controller, then I still think you may need to rebuild. But you can try re-adding the SharePoint server to the Domain. It may have lost its Domain membership when you removed
AD from it and gone back to being a standalone server.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

SCVMM 2012: Unable to connect to the VMM management server localhost:8100

Hi everyone
I have difficulties connecting with the Admin UI to the SCVMM server running on the same machine. This is the error message I see:
Unable to connect to the VMM management server localhost. The Virtual Machine Manager service on that server did not respond.
Verify that Virtual Machine Manager has been installed on the server and that the Virtual Machine Manager service is running.
Then try to connect again. If the problem persists, restart the Virtual Machine Manager service.
ID: 1602
I checked that the service is running and checked with the Resource Monitor that vmmservice.exe is really listening on port 8100. The Resource Monitor also shows some traffic between itself, the service and the DC. But all traffic dies down after a few seconds,
then nothing happens for a minute, then I get the above error message. The only SCVMM related entry in the eventlog is this (was logged when I manually tried restarting the service):
Failed to stop service. System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.VirtualManager.Engine.VirtualManagerService.OnStop()
at System.ServiceProcess.ServiceBase.DeferredStop()
But I guess that entry is of no help. Other important things that might be relevant:
This installation worked fine three months ago. Since then only the automatic updates were installed.
DPM (the 2012 CTP for Win8) is installed on the same server.
After it didn't work I installed SQL Server 2008 R2 SP1 (offered by Microsoft Update)
SCVMM is part of a small test installation (~10 VMs or so), no valuable data, so there's no risk when messing around
Control panel shows the version number 3.1.1042.0 for "Microsoft System Center 2012 Virtual Machine Manager".
Is there anything else I could try? How can SCVMM stop to work, all by itself? Leaves a sour taste...
Cheers,
Simon

When such odd behaviour occur, it is a good tip to start a VMM trace to see where things are actually going wrong. And suck files is interestin for MS support once the obvious things for errors, are eliminated out of the picture.
VMM has dependencies such as SQL, permissions and service accounts. All of these variables does
also have dependencies that should be verified. Verify that the account for the service does is not locked/expired pwd, that the SQL is up and running - and actually is working. There is a lot of logs to check in order to determine the root cause of
this behaviour.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Connecting to the admin context

Similar Messages

Maybe you are looking for