Home > OCS 2007 / Lync 2010 > Lync Server 2010: Topology Deployment error

Lync Server 2010: Topology Deployment error

When I published my standard Edition topology I received the following error:

An error occurred: “Microsoft.Rtc.Management.Deployment.DeploymentException” “Cannot determine where to install database files because Windows Management Instrumentation on the database server is unavailable from your computer or user account. To continue, you can resolve this issue, or you can specify where you want to install the files.”

This error indicates that the server is not able to find the database server? But the database is on the standard Edition server! After a quick review in the Topology builder I found that I made a typo in the Topology Builder. The Pool name didn’t match my FQDN of the standard Edition server.

In case of a Standard Edition the pool name must be the FQDN of the Standard Edition server.

Advertisements
Categories: OCS 2007 / Lync 2010
  1. Fuk YEAH
    March 31, 2011 at 8:58 pm

    Cheets Buddy , I had a typo too!

  2. Ankur Desai
    June 3, 2011 at 9:21 pm

    I am trying to install lync 2010. I had some issues and had to reinstall it fresh. I keep getting these errors when I attempto to publish the topology. Please help!
    Error: A trusted server with the fully qualified domain name (FQDN) “msilync.ad.mosys” was found for unmatched Globally Routable User Agent URI (GRUU).
    ▼ Details
    └ Type: DeploymentException
    └ ▼ Stack Trace
    └ at Microsoft.Rtc.Management.Deployment.Core.CompatTrustedServer.Create()
    at Microsoft.Rtc.Management.Deployment.Roles.Registrar.CreateTrustedServerEntry(RegistrarService registrar, Fqdn hostFqdn)
    at Microsoft.Rtc.Management.Deployment.Roles.Registrar.GlobalActivate(IService service)
    at Microsoft.Rtc.Management.Deployment.Core.Service.GlobalActivate()
    at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action)

    6/3/2011 2:54:18 PM Error

    └ Error: A trusted server with the fully qualified domain name (FQDN) “msilync.ad.mosys” was found for unmatched Globally Routable User Agent URI (GRUU).

  3. Joris
    June 6, 2011 at 10:51 am

    You had probably OCS 2007 installed in your domain? Did you performed an unprep of OCS 2007?

    http://technet.microsoft.com/en-us/library/bb905981%28office.12%29.aspx

    LCSCmd.exe /Domain[:] /Action:DomainUnPrep
    LCSCmd.exe /Domain:contoso.com /Action:DomainUnPrep

  4. bill
    July 18, 2011 at 7:23 pm

    regarding the original article, what pool are you refering too? you said: “In case of a Standard Edition the pool name must be the FQDN of the Standard Edition server.”

    which pool is that? I cant find any typos anywhere and I’m not sure which pool has to have the same FQDN. I dont have the director, enterprise edition, or edge pools created, is that the problem?

    thank you in advance.

  5. Joris
    July 18, 2011 at 7:55 pm

    During the topology deployment wizard there is a step “Define the front end pool FQDN” where you have two options:

    -> Enterprise Edition Front End Pool
    -> Standard Edition Server

    In case you choose “Standard Edition server ” you must enter the Fully qualified name of your Lync server in the Pool FQDN field.

  6. June 28, 2013 at 9:38 am

    I got this error when installing Lync 2013 in a new 2012 domain.

    After making sure that
    A) my firewall setting had “Remote Administration” enabled (allow)
    B) DNS A/Cname records were correct for the FE server & pools
    C) At publishing time, choose “Use Database server instance defaults” for both FE-pool and SQL server…

    It worked! I had been banging my head on my keyboard for some time before I found this hidden “Advanced” config.

    Apparently, the “Automatic…” option to determine where to store the files failed to work… Hope this helps someone…

  1. No trackbacks yet.

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s

%d bloggers like this: