Microsoft 2011 For Mac Reporting Unable Locate Server

Posted on
Microsoft 2011 For Mac Reporting Unable Locate Server Rating: 8,6/10 6072 votes

One place for all extensions for Visual Studio, Azure DevOps Services, Azure DevOps Server and Visual Studio Code. Discover and install extensions and subscriptions to create the dev environment you need. Some features of Microsoft Exchange accounts depend on the version of Exchange that your account connects to. An example is the Outlook Anywhere feature. Exchange admin center in Exchange Server. 2/8/2020; 12 minutes to read +5; In this article. The Exchange admin center (EAC) is the web-based management console in Exchange Server that's optimized for on-premises, online, and hybrid Exchange deployments.

  1. Microsoft 2011 For Mac Reporting Unable Locate Server Free
  2. Microsoft 2011 For Mac Reporting Unable Locate Server Windows 10
  3. Microsoft 2011 For Mac Reporting Unable Locate Server List
  4. Microsoft 2011 For Mac Reporting Unable Locate Server Download
  5. Microsoft 2011 For Mac Reporting Unable Locate Server Windows 7
-->

2011-12-2  Summary: In this guest blog article written by Microsoft MVP, Jan Egil Ring, you will learn how to use Exchange Web Services (EWS) with Windows PowerShell. Microsoft Scripting Guy, Ed Wilson, is here. Today, we begin Guest Blogger Weekend. We are really fortunate today to have a great blog post by Microsoft Windows PowerShell MVP. 2017-2-4  SSRS Report Issue in Chrome/Firefox, ok in IE. Popular Topics in Microsoft SQL Server. Are you smarter than most IT pros? Take the Daily Challenge ». FYI I did read that Chrome is a fully supported browser for interacting with Reporting Services when used with SQL Server 2016. How to issue WSUS certificate from local Certificate Authority. Unable to configure Parallels OS X Software Update Service: The WSUS signing certificate must be deployed and accessible by: Cause. WSUS certificate should be issued to configure Parallels OS X.

The Exchange admin center (EAC) is the web-based management console in Exchange Server that's optimized for on-premises, online, and hybrid Exchange deployments. The EAC was introduced in Exchange Server 2013, and replaces the Exchange Management Console (EMC) and the Exchange Control Panel (ECP), which were the two management interfaces in Exchange Server 2010.

Looking for the Exchange Online version of this topic? See Exchange admin center in Exchange Online.

Looking for the Exchange Online Protection version of this topic? See Exchange admin center in Exchange Online Protection.

Accessing the EAC

The URL of the EAC is controlled by the Internet Information Services (IIS) virtual directory named ECP in the Client Access (frontend) services on the Mailbox server. Yes, the virtual directory is named ECP, not EAC.

  • Internal URL: By default, this value contains the fully-qualified domain name (FQDN) of the Exchange server in the format https://<ServerFQDN>/ecp. For example, https://mailbox01.contoso.com/ecp. To access the EAC in a web browser on the Exchange server itself, you can use the value https://localhost/ecp.

  • External URL: By default, this value is unconfigured. Before you can connect to the EAC from the Internet, you need to configure the following settings:

    • The external URL value on the ECP virtual directory. For more information, see Step 4: Configure external URLs in Configure mail flow and client access on Exchange servers.

    • A corresponding record in your public DNS.

    • A TLS certificate that contains or matches the host name entry. Very likely, this will be a subject alternative name (SAN) certificate or a wildcard certificate, because most of the client services are all available under the same website on the Exchange server. For more information, see Certificate requirements for Exchange services.

      After you configure the settings, a common external URL value for the EAC would resemble https://mail.contoso.com/ecp.

      Note: External users who connect to Outlook on the web (formerly known as Outlook Web App) also need access to the EAC to access their own Options page. You can disable external administrator access to the EAC while still allowing users to access their Options page in Outlook on the web. For more information, see Turn off access to the Exchange admin center.

The easiest way to find the internal and external URL values for the EAC (without using Servers > Virtual directories in the EAC itself) is by using the Get-EcpVirtualDirectory cmdlet in the Exchange Management Shell. To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see Open the Exchange Management Shell.

These examples show you how to find the internal and external URL values for the EAC virtual directories in your organization:

  • To find the values on all Exchange servers in your organization, run the following command:

  • To find the values on the server named Mailbox01, run the following command:

  • To find the value for the virtual directory named 'ecp (Default Web Site)' on the server named Mailbox01, run the following command.

For more information, see Get-EcpVirtualDirectory.

In Exchange 2016, if you're in a coexistence environment with Exchange 2010, the location of your mailbox controls the default behavior for opening the EAC or ECP:

  • If your mailbox is located on the Exchange 2010 Mailbox server, you get the Exchange 2010 ECP by default. You can access the EAC by adding the Exchange version to the URL (which is 15 for both Exchange 2013 and Exchange 2016). For example, to access the EAC through the Client Access (frontend) services on the Mailbox server named Mailbox01, use the following URL: https://Mailbox01/ecp/?ExchClientVer=15.

  • If your mailbox is located on an Exchange 2016 Mailbox server, and you want to access the ECP on the Exchange 2010 Client Access server named CAS01, use the following URL: https://CAS01/ecp/?ExchClientVer=14.

Common user interface elements in the EAC

The section describes the user interface elements that are common across the EAC.

1: Cross-premises navigation

The cross-premises navigation allows you to easily switch between your Exchange Online and on-premises Exchange deployments. If you don't have an Exchange Online organization, the Office 365 link takes you to a page that compares plans and pricing for Office 365 services.

2: Feature pane

The feature pane is the first level of navigation for most of the tasks that you'll perform in the EAC, and is organized by the following feature areas:

  • Recipients: Manage mailboxes, groups, resource mailboxes (room and equipment mailboxes), contacts, shared mailboxes, and mailbox migrations and moves. For more information, see the following topics:

    • Create user mailboxes in Exchange Server and Manage user mailboxes

    • Manage distribution groups and Manage dynamic distribution groups

    • Manage mail contacts and Manage mail users

  • Permissions: Manage role-based access control (RBAC) administrator roles, user roles, and Outlook on the web policies. For more information, see the following topics.

    • Manage role groups , Manage role group members, and Manage role assignment policies.

      2011

  • Compliance management: This is where you'll manage In-Place eDiscovery, In-Place Hold, auditing (mailbox audit logging and administrator audit logging), data loss prevention (DLP), retention policies, retention tags, and journal rules. For more information, see the following topics:

    • In-Place eDiscovery in Exchange Server and In-Place Hold and Litigation Hold in Exchange Server

    • Mailbox audit logging in Exchange Server and Administrator audit logging in Exchange Server

    • Retention policies and Retention tags.

  • Organization: Manage federated sharing, Outlook Apps, and address lists. For more information, see the following topics:

  • Protection: Manage antimalware protection for your organization. For more information, see Antimalware protection in Exchange Server.

  • Mail flow: Manage mail flow rules (also known as transport rules), delivery reports, accepted domains, remote domains, email address policies, Receive connectors, and Send connectors. For more information, see the following topics:

  • Mobile: Manage the mobile devices that you allow to connect to your organization. You can manage mobile device access and mobile device mailbox policies. For more information, see the following topics:

  • Public folders: Manage public folders and public folder mailboxes. For more information, see Public folders.

  • Unified Messaging: Manage UM dial plans and UM IP gateways. (UM is not available in Exchange 2019.) For more information, see the following topics:

  • Servers: View and manage server-specific settings, databases, database availability groups (DAGs), virtual directories, and certificates. For more information, see the following topics:

    • Configure the Startup Mode on a Client Access Server and Configure the Startup Mode on a Mailbox Server

    • Configure message tracking , Configure connectivity logging in Exchange Server, and Protocol logging

  • Hybrid: Set up and configure a Hybrid organization.

  • Tools: Check your Exchange server with the Office 365 Best Practices Analyzer. For more information, see About the Office 365 Best Practices Analyzer for Exchange Server.

3: Tabs

The tabs are your second level of navigation. Typically, each feature pane contains multiple tabs that represent complete features. However, the Tools and Hybrid panes each contain only one tab: the Checks tab to install and run the Office 365 Best Practices Analyzer, or the Setup tab that allows you to run the Hybrid Configuration Wizard, or modify the settings of your existing hybrid deployment.

4: Toolbar

When you click most tabs, you'll see a toolbar. The toolbar has icons that perform specific actions. The following table describes the most common icons and their actions. To see the action that's associated with an icon (the icon's title), simply hover over the icon.

IconNameAction
Add, NewCreate a new object.
Some of these icons have an associated down arrow you can click to show additional objects you can create. For example, in Recipients > Mailboxes, clicking the down arrow displays User mailbox and Linked mailbox as additional options.
EditEdit an object.
DeleteDelete an object. Some delete icons have a down arrow you can click to show additional options.
SearchOpen a search box so you can enter text for an object that you want to find you want to find in a long list of objects. Check out Advanced search for more search options.
RefreshRefresh the list view.
More optionsView more actions you can perform for that tab's objects.
For example, in Recipients > Mailboxes clicking this icon shows the following options: Disable, Add/Remove columns, Export data to a CSV file, Connect a mailbox, and Advanced search.

Up arrow and down arrowMove an object up or down in the list, when the order is important.
For example, in Mail flow > Email address policies click the up arrow to move the policy higher in the list, which increases the priority of the policy by specifying which policy is applied first.
You can also use these arrows to navigate the public folder hierarchy and to move rules up or down in the list view.
CopyCopy an object so you can make changes to it without changing the original object.
For example, in Permissions > Admin roles, select a role from the list view, and then click this icon to create a new role group based on an existing one.
RemoveRemove an item from a list.
For example, in the Public Folder Permissions dialog box, you can remove users from the list of users allowed to access the public folder by selecting the user and clicking this icon.

5: List view

Tabs that contain many objects display those objects in a list view. The viewable limit in the EAC list view is approximately 20,000 objects. Paging is included so you can skip to the results that you want to see. In the Recipients list view, you can also configure page size and export the data to a CSV file.

6: Details pane

When you select an object from the list view, more information about that object is displayed in the details pane. For some object types, the details pane includes quick management tasks. For example, if you navigate to Recipients > Mailboxes and select a mailbox from the list view, the details pane (among other options) displays an option to enable or disable the archive for that mailbox.

Some object types also allow you to bulk edit multiple objects in the details pane. You can select multiple objects in the list view by selecting an object, holding the Shift key, and selecting an object farther down in the list, or by holding down the CTRL key as you select each object. If bulk edit is available for the object types that you selected, you'll see the available options in the details pane. For example, at Recipients > Mailboxes, when you select multiple mailboxes of the same type, the title of the details pane changes to Bulk Edit, and you can update contact and organization information, custom attributes, mailbox quotas, Outlook on the web settings, and more.

7: Notifications

The EAC includes a notification viewer that displays information about:

  • Expiring and expired certificates.

  • The status of mailbox moves and migrations (also known as Mailbox Replication Service tasks or MRS tasks). You can also use the notification viewer to opt-in to receive email notifications about these tasks.

  • Exporting mailbox content to .pst files.

To show or hide the notification viewer, click the icon ().

Notifications are alerts that are sent to the arbitration mailbox named FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042. The EAC checks this mailbox for alerts every 30 seconds. Notifications remain in the arbitration mailbox until they are removed by the component that sent them, or until they expire (they should be removed by the Managed Folder Assistant after 30 days).

You can also use the Get-Notification cmdlet in the Exchange Management Shell to view more details about notifications, and the Set-Notification cmdlet to request notification emails for future alerts.

8: Me tile and Help

The Me tile allows you to sign out of the EAC and sign in as a different user by clicking on the drop-down menu that's next to your account name.

Click the help icon () to view the help content for the tab that you're currently on. If you click on the drop-down menu that's next to the help icon, you can perform the following additional actions:

  • Disable Help bubble: The Help bubble displays contextual help for fields when you create or edit objects in the EAC. From here, you can globally turn off or turn on the Help bubble for all fields in the EAC.

  • Performance console: The Performance console displays many counters that relate to the performance of the EAC.

  • Copyright and Privacy: Click these links to read the copyright and privacy information for Exchange Server.

Supported browsers

The levels of support for operating system and browser combinations that you can use to access the EAC are described in the following tables.

Notes:

Microsoft 2011 For Mac Reporting Unable Locate Server Free

  • The levels of support for the EAC are:

    • Supported: All functionality and features are supported and have been fully tested.

    • Unsupported: The browser and operating system combination isn't supported, or hasn't been tested. For more information about supported versions of Internet Explorer on Windows, see Internet Explorer Support Announcement.

    • n/a: The browser and operating system combination isn't possible. For example, an older browser on a newer operating system, or vice-versa.

  • Operating system and browser combinations that aren't listed are unsupported. This includes iOS, Android, and Windows Phone.

  • Third-party plug-ins might cause issues with the EAC for supported browsers.

Client operating systems

Web browserWindows 7Windows 8.1Windows 10Mac OS XLinux
Internet Explorer 9Unsupportedn/an/an/an/a
Internet Explorer 10Unsupportedn/an/an/an/a
Internet Explorer 11SupportedSupportedSupportedn/an/a
Microsoft Edgen/an/aSupportedn/an/a
Mozilla Firefox latest version or one previousSupportedSupportedSupportedSupportedSupported
Apple Safari 6 or later versionsn/an/an/aSupportedn/a
Google Chrome latest version or one previousSupportedSupportedSupportedSupportedSupported

Windows Server operating systems

Web browserWindows Server 2008 R2Windows Server 2012Windows Server 2012 R2Windows Server 2016
Internet Explorer 9Unsupportedn/an/an/a
Internet Explorer 10UnsupportedSupportedn/an/a
Internet Explorer 11Supportedn/aSupportedSupported
-->

APPLIES TO: SQL Server (Linux only) Azure SQL Database Azure Synapse Analytics (SQL DW) Parallel Data Warehouse

In this quickstart, you use Docker to pull and run the SQL Server 2017 container image, mssql-server-linux. Then connect with sqlcmd to create your first database and run queries.

Tip

If you want to run SQL Server 2019 containers, see the SQL Server 2019 version of this article.

Note

Starting with SQL Server 2019 CU3, Ubuntu 18.04 is supported.

In this quickstart, you use Docker to pull and run the SQL Server 2019 container image, mssql-server. Then connect with sqlcmd to create your first database and run queries.

Tip

This quickstart creates SQL Server 2019 containers. If you prefer to create SQL Server 2017 containers, see the SQL Server 2017 version of this article.

This image consists of SQL Server running on Linux based on Ubuntu 18.04. It can be used with the Docker Engine 1.8+ on Linux or on Docker for Mac/Windows. This quickstart specifically focuses on using the SQL Server on linux image. The Windows image is not covered, but you can learn more about it on the mssql-server-windows-developer Docker Hub page.

Microsoft 2011 For Mac Reporting Unable Locate Server Windows 10

Prerequisites

  • Docker Engine 1.8+ on any supported Linux distribution or Docker for Mac/Windows. For more information, see Install Docker.
  • Docker overlay2 storage driver. This is the default for most users. If you find that you are not using this storage provider and need to change, please see the instructions and warnings in the docker documentation for configuring overlay2.
  • Minimum of 2 GB of disk space.
  • Minimum of 2 GB of RAM.
  • System requirements for SQL Server on Linux.

Pull and run the container image

Before starting the following steps, make sure that you have selected your preferred shell (bash, PowerShell, or cmd) at the top of this article.

  1. Pull the SQL Server 2017 Linux container image from Microsoft Container Registry.

    Tip

    If you want to run SQL Server 2019 containers, see the SQL Server 2019 version of this article.

    The previous command pulls the latest SQL Server 2017 container image. If you want to pull a specific image, you add a colon and the tag name (for example, mcr.microsoft.com/mssql/server:2017-GA-ubuntu). To see all available images, see the mssql-server Docker hub page.

    For the bash commands in this article, sudo is used. On macOS, sudo might not be required. On Linux, if you do not want to use sudo to run Docker, you can configure a docker group and add users to that group. For more information, see Post-installation steps for Linux.

  2. To run the container image with Docker, you can use the following command from a bash shell (Linux/macOS) or elevated PowerShell command prompt.

    Note

    The password should follow the SQL Server default password policy, otherwise the container can not setup SQL server and will stop working. By default, the password must be at least 8 characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols. You can examine the error log by executing the docker logs command.

    Note

    By default, this creates a container with the Developer edition of SQL Server 2017. The process for running production editions in containers is slightly different. For more information, see Run production container images.

    The following table provides a description of the parameters in the previous docker run example:

    ParameterDescription
    -e 'ACCEPT_EULA=Y'Set the ACCEPT_EULA variable to any value to confirm your acceptance of the End-User Licensing Agreement. Required setting for the SQL Server image.
    -e 'SA_PASSWORD=<YourStrong@Passw0rd>'Specify your own strong password that is at least 8 characters and meets the SQL Server password requirements. Required setting for the SQL Server image.
    -p 1433:1433Map a TCP port on the host environment (first value) with a TCP port in the container (second value). In this example, SQL Server is listening on TCP 1433 in the container and this is exposed to the port, 1433, on the host.
    --name sql1Specify a custom name for the container rather than a randomly generated one. If you run more than one container, you cannot reuse this same name.
    -d mcr.microsoft.com/mssql/server:2017-latestThe SQL Server 2017 Linux container image.

  3. To view your Docker containers, use the docker ps command.

    You should see output similar to the following screenshot:

  4. If the STATUS column shows a status of Up, then SQL Server is running in the container and listening on the port specified in the PORTS column. If the STATUS column for your SQL Server container shows Exited, see the Troubleshooting section of the configuration guide.

The -h (host name) parameter is also useful, but it is not used in this tutorial for simplicity. This changes the internal name of the container to a custom value. This is the name you'll see returned in the following Transact-SQL query:

Setting -h and --name to the same value is a good way to easily identify the target container.

Pull and run the container image

Before starting the following steps, make sure that you have selected your preferred shell (bash, PowerShell, or cmd) at the top of this article.

  1. Pull the SQL Server 2019 Linux container image from Docker Hub.

    Tip

    This quickstart uses the SQL Server 2019 Docker image. If you want to run the SQL Server 2017 image, see the SQL Server 2017 version of this article.

    The previous command pulls the SQL Server 2019 container image based on Ubuntu. To instead use container images based on RedHat, see Run RHEL-based container images. To see all available images, see the mssql-server-linux Docker hub page.

    For the bash commands in this article, sudo is used. On macOS, sudo might not be required. On Linux, if you do not want to use sudo to run Docker, you can configure a docker group and add users to that group. For more information, see Post-installation steps for Linux.

  2. To run the container image with Docker, you can use the following command from a bash shell (Linux/macOS) or elevated PowerShell command prompt.

    Note

    The password should follow the SQL Server default password policy, otherwise the container can not setup SQL server and will stop working. By default, the password must be at least 8 characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols. You can examine the error log by executing the docker logs command.

    Note

    By default, this creates a container with the Developer edition of SQL Server 2019.

    The following table provides a description of the parameters in the previous docker run example:

    ParameterDescription
    -e 'ACCEPT_EULA=Y'Set the ACCEPT_EULA variable to any value to confirm your acceptance of the End-User Licensing Agreement. Required setting for the SQL Server image.
    -e 'SA_PASSWORD=<YourStrong@Passw0rd>'Specify your own strong password that is at least 8 characters and meets the SQL Server password requirements. Required setting for the SQL Server image.
    -p 1433:1433Map a TCP port on the host environment (first value) with a TCP port in the container (second value). In this example, SQL Server is listening on TCP 1433 in the container and this is exposed to the port, 1433, on the host.
    --name sql1Specify a custom name for the container rather than a randomly generated one. If you run more than one container, you cannot reuse this same name.
    mcr.microsoft.com/mssql/server:2019-CU3-ubuntu-18.04The SQL Server 2019 Ubuntu Linux container image.

  3. To view your Docker containers, use the docker ps command.

    You should see output similar to the following screenshot:

  4. If the STATUS column shows a status of Up, then SQL Server is running in the container and listening on the port specified in the PORTS column. If the STATUS column for your SQL Server container shows Exited, see the Troubleshooting section of the configuration guide.

The -h (host name) parameter is also useful, but it is not used in this tutorial for simplicity. This changes the internal name of the container to a custom value. This is the name you'll see returned in the following Transact-SQL query:

Setting -h and --name to the same value is a good way to easily identify the target container.

Change the SA password

The SA account is a system administrator on the SQL Server instance that gets created during setup. After creating your SQL Server container, the SA_PASSWORD environment variable you specified is discoverable by running echo $SA_PASSWORD in the container. For security purposes, change your SA password.

  1. Choose a strong password to use for the SA user.

  2. Use docker exec to run sqlcmd to change the password using Transact-SQL. In the following example, replace the old password, <YourStrong!Passw0rd>, and the new password, <YourNewStrong!Passw0rd>, with your own password values.

Connect to SQL Server

The following steps use the SQL Server command-line tool, sqlcmd, inside the container to connect to SQL Server.

  1. Use the docker exec -it command to start an interactive bash shell inside your running container. In the following example sql1 is name specified by the --name parameter when you created the container.

  2. Once inside the container, connect locally with sqlcmd. Sqlcmd is not in the path by default, so you have to specify the full path.

    Tip

    You can omit the password on the command-line to be prompted to enter it.

  3. If successful, you should get to a sqlcmd command prompt: 1>.

Create and query data

The following sections walk you through using sqlcmd and Transact-SQL to create a new database, add data, and run a simple query.

Microsoft 2011 For Mac Reporting Unable Locate Server List

Create a new database

The following steps create a new database named TestDB.

Microsoft 2011 For Mac Reporting Unable Locate Server Download

  1. From the sqlcmd command prompt, paste the following Transact-SQL command to create a test database:

  2. On the next line, write a query to return the name of all of the databases on your server:

  3. The previous two commands were not executed immediately. You must type GO on a new line to execute the previous commands:

Insert data

Next create a new table, Inventory, and insert two new rows.

  1. From the sqlcmd command prompt, switch context to the new TestDB database:

  2. Create new table named Inventory:

  3. Insert data into the new table:

  4. Type GO to execute the previous commands:

Microsoft 2011 For Mac Reporting Unable Locate Server Windows 7

Select data

Now, run a query to return data from the Inventory table.

  1. From the sqlcmd command prompt, enter a query that returns rows from the Inventory table where the quantity is greater than 152:

  2. Execute the command:

Exit the sqlcmd command prompt

  1. To end your sqlcmd session, type QUIT:

  2. To exit the interactive command-prompt in your container, type exit. Your container continues to run after you exit the interactive bash shell.

Connect from outside the container

You can also connect to the SQL Server instance on your Docker machine from any external Linux, Windows, or macOS tool that supports SQL connections.

The following steps use sqlcmd outside of your container to connect to SQL Server running in the container. These steps assume that you already have the SQL Server command-line tools installed outside of your container. The same principles apply when using other tools, but the process of connecting is unique to each tool.

  1. Find the IP address for the machine that hosts your container. On Linux, use ifconfig or ip addr. On Windows, use ipconfig.

  2. For this example, install the sqlcmd tool on your client machine. For more information, see Install sqlcmd on Windows or Install sqlcmd on Linux.

  3. Run sqlcmd specifying the IP address and the port mapped to port 1433 in your container. In this example, that is the same port, 1433, on the host machine. If you specified a different mapped port on the host machine, you would use it here.

  4. Run Transact-SQL commands. When finished, type QUIT.

Other common tools to connect to SQL Server include:

Remove your container

If you want to remove the SQL Server container used in this tutorial, run the following commands:

Warning

Stopping and removing a container permanently deletes any SQL Server data in the container. If you need to preserve your data, create and copy a backup file out of the container or use a container data persistence technique.

Docker demo

After you have tried using the SQL Server container image for Docker, you might want to know how Docker is used to improve development and testing. The following video shows how Docker can be used in a continuous integration and deployment scenario.

Next steps

For a tutorial on how to restore database backup files into a container, see Restore a SQL Server database in a Linux Docker container. To explore other scenarios, such as running multiple containers, data persistence, and troubleshooting, see Configure SQL Server container images on Docker.

Also, check out the mssql-docker GitHub repository for resources, feedback, and known issues.