ARS server does not exist or could not be contacted

ARS server does not exist or could not be contacted

Yeah sure!  This is the type of error that on the wrong day will bring out the Basil Fawlty in all of us.

If you are running Active Roles make sure you get the correct version of the cmdlets to match – I’ve listed the versions in a table below to save you searching for it – I can google that for you 🙂 .

If you load the latest cmdlets I’m sure you will be bristling with pride with all the clever stuff you can do with them….. but you won’t be communicating with your ARS service because it will ignore you completely.  Also annoyingly the error message will be next to useless, see below two possible errors you will see.  Worse the reason for the connection failure may not even be the version of the cmdlets you are running.  I’m sure there is a tech note somewhere explaining that the -proxy switch only works when the MMC is installed – perhaps someone can google that for me, as I was unable to find the link to post here.

So you have three things to check.  The ARS server version you are running, the cmdlet version and is the MMC installed.

unabletoconnect14

unabletoconnect

How then do I check these things?

Manually it’s easy – open the ARS MMC ( check one item off the list 🙂 Assuming the MMC can connect, help about will confirm the version No. for you.  Now open the ActiveRoles Management Shell for Active Directory and the version number will be displayed at the top of the window.  Now you can check the table below to ensure the versions all match up and they can start their play date together.

You wont get in this mess if you install the MMC first as it won’t let you install an incompatible version of the cmdlets but the reverse doesn’t happen.  The MMC will happily install on top of any version of the cmdlets.

What if I wanted to check in a script which version of the cmdlets were installed as this script might be run on multiple PCs or Servers where the cmdlets might not even be installed.  That’s relatively simple too and I’ll bundle that info into a combined post explaining how to find out the PowerShell version you are running as well.

Now where did I leave the keys to the Austin 1100 Sybil must be wondering where I am…

Date Posted Name Version File Type Size
May 16 2011 ActiveRoles Management Shell for Active Directory 32-bitAD Management Shell 1.5.1 is compatible with only ARS 6.7.0 1.5.1 20.08 MB
Oct 29 2012 Quest One ActiveRoles Management Shell for Active Directory 32-bit – ZipAD Management Shell 1.6.0 is compatible with only ARS 6.8.0 1.6.0 21.95 MB
May 16 2011 ActiveRoles Management Shell for Active Directory 64-bitAD Management Shell 1.5.1 is compatible with only ARS 6.7.0 1.5.1 32.73 MB
Oct 29 2012 Quest One ActiveRoles Management Shell for Active Directory 64-bit – ZipAD Management Shell 1.6.0 is compatible with only ARS 6.8.0 1.6.0 36.79 MB
Advertisements

One thought on “ARS server does not exist or could not be contacted

  1. With ActiveRoles 6.9 the ManagementShell does work without the MMC being installed.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.