{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "error",
  "home_page_url": "https://evotec.xyz/fr/tags/error",
  "feed_url": "https://evotec.xyz/fr/tags/error/index.feed.json",
  "description": "Evotec Main Website",
  "items": [
    {
      "id": "https://evotec.xyz/fr/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error",
      "url": "https://evotec.xyz/fr/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error",
      "title": "Upgrade Azure Active Directory Connect fails with unexpected error",
      "summary": "Today, I made the decision to upgrade my test environment and update the version of Azure AD Connect to the latest one. The process is usually simple: download a new MSI, run it, click next a few times, enter the credentials for your Global Admin, and you\u2019re finished. However, this time, I encountered an error.",
      "date_published": "2024-10-02T12:17:34.0000000Z",
      "tags": [
        "azure ad",
        "azure adconnect",
        "error",
        "errors",
        "Office 365",
        "office365"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/active-directory-the-directory-service-was-unable-to-allocate-a-relative-identifier",
      "url": "https://evotec.xyz/fr/blog/active-directory-the-directory-service-was-unable-to-allocate-a-relative-identifier",
      "title": "Active Directory \u2013 The directory service was unable to allocate a relative identifier",
      "summary": "I\u2019ve been testing Disaster Recovery scenario restoring Active Directory. One of the servers was restored, and it worked for a moment after restore. If you can regain your Primary DC, it\u2019s best to do so. If you can\u2019t, a standard thing to do during DR is to move all FSMO roles to the restored server so that it can become a master server. You can find out your FSMO holders by using those commands below:",
      "date_published": "2019-03-27T20:39:25.0000000Z",
      "tags": [
        "active directory",
        "ad",
        "error",
        "powershell"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/hyper-v-cant-start-virtual-machine-because-its-backing-up",
      "url": "https://evotec.xyz/fr/blog/hyper-v-cant-start-virtual-machine-because-its-backing-up",
      "title": "Hyper-V \u2013 Can\u2019t start Virtual Machine because it\u2019s backing up",
      "summary": "Working as a small business often brings you little tasks here and there. Today I\u2019ve decided to shut down the Hyper-V machine to expand its disks. Unfortunately for me, while extending of HDD went great, I couldn\u2019t start Virtual Machine any longer.",
      "date_published": "2019-02-25T21:29:14.0000000Z",
      "tags": [
        "backup",
        "error",
        "hyper-v",
        "powershell"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/outlook-the-primary-account-cannot-be-removed-unless-it-is-the-only-account-in-the-profile",
      "url": "https://evotec.xyz/fr/blog/outlook-the-primary-account-cannot-be-removed-unless-it-is-the-only-account-in-the-profile",
      "title": "Outlook \u2013 The primary account cannot be removed unless it is the only account in the profile",
      "summary": "Last few months I\u2019m responsible for the migration of Office 365 to Office 365. While doing so, we came into a situation where users have their old mailbox as Primary Account and new Mailbox as their secondary account. This is a quite common scenario that people are running into and something that is expected. Usually, my recommendation is: Please create a new profile for user and topic is closed. It\u2019s also quite easy to achieve this in an automated way where you delete all profiles and Outlook just goes with autodiscovery adding new account as required. That\u2019s how I have always done this till now. My Client has gone thru setting up 1000\u002B users with their second account in Outlook and deleting a whole profile, recreating would cause lots of downloading of emails from Office 365 that my Client wanted to avoid.",
      "date_published": "2018-11-23T22:39:44.0000000Z",
      "tags": [
        "error",
        "exchange",
        "outlook",
        "PowerShell",
        "windows"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/azure-adconnect-export-failed-permission-issue-error",
      "url": "https://evotec.xyz/fr/blog/azure-adconnect-export-failed-permission-issue-error",
      "title": "Azure ADConnect Export Failed \u2013 Permission-issue error",
      "summary": "During our recent setup of Azure ADConnect for one of our Clients we\u2019ve been getting permission-issue \u2013 Insufficient access rights\u2026",
      "date_published": "2017-10-08T19:23:20.0000000Z",
      "tags": [
        "active directory",
        "adconnect",
        "azure ad",
        "azure adconnect",
        "error",
        "errors",
        "export failed",
        "office 365",
        "permission-issue",
        "permissions",
        "powershell",
        "windows 2012R2",
        "windows 2016",
        "windows server 2016"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/unifi-controller-upgrade-ubuntu-fails-package-installation",
      "url": "https://evotec.xyz/fr/blog/unifi-controller-upgrade-ubuntu-fails-package-installation",
      "title": "UniFi Controller upgrade on Ubuntu fails during package installation",
      "summary": "We\u2019re a huge fan of Ubiquity hardware, especially it\u2019s UniFi products line. It\u2019s nice, modern hardware with lots of functionalities\u2026",
      "date_published": "2017-08-06T10:18:10.0000000Z",
      "tags": [
        "5.5.19",
        "5.5.20",
        "apt update",
        "apt upgrade",
        "debian",
        "error",
        "errors",
        "hardware",
        "ubiquiti",
        "ubuntu",
        "unifi"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/hyper-v-error-move-operation",
      "url": "https://evotec.xyz/fr/blog/hyper-v-error-move-operation",
      "title": "Hyper-V \u2013 There was an error during move operation",
      "summary": "Windows Hyper-V with it\u2019s live migration is a great feature\u2026 when it works! Unfortunately after setting it up things weren\u2019t\u2026",
      "date_published": "2017-06-11T16:31:03.0000000Z",
      "tags": [
        "Active Directory",
        "error",
        "hyper-v",
        "microsoft",
        "microsoft windows",
        "windows 2012",
        "windows 2012R2",
        "windows 2016",
        "windows hyper-v"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/the-shadow-copy-provider-had-an-unexpected-error-while-trying-to-process-the-specified-command",
      "url": "https://evotec.xyz/fr/blog/the-shadow-copy-provider-had-an-unexpected-error-while-trying-to-process-the-specified-command",
      "title": "The shadow copy provider had an unexpected error while trying to process the specified command.",
      "summary": "Recently we had a case where an offsite backup in Altaro VM Backup was supposed to be written to Western\u2026",
      "date_published": "2017-02-02T19:48:44.0000000Z",
      "tags": [
        "altaro",
        "error",
        "errors",
        "shadow copy provider",
        "vss",
        "vss error",
        "vssadmin",
        "Windows"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/microsoft-exchange-ou-picker-empty-creating-new-user",
      "url": "https://evotec.xyz/fr/blog/microsoft-exchange-ou-picker-empty-creating-new-user",
      "title": "Microsoft Exchange \u2013 OU picker is empty when creating new user",
      "summary": "We\u2019ve migrated one of our Clients fairly early but recently we got complain that when new user is created from\u2026",
      "date_published": "2016-11-01T11:24:27.0000000Z",
      "tags": [
        "error",
        "exchange",
        "exchange 2013",
        "microsoft exchange",
        "microsoft exchange server"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/hyper-v-incorrect-function-when-trying-to-move-files",
      "url": "https://evotec.xyz/fr/blog/hyper-v-incorrect-function-when-trying-to-move-files",
      "title": "Hyper-V \u2013 Incorrect function when trying to move files",
      "summary": "When we are asked by our Clients to setup their servers we usually go with virtualization. We usually choose Hyper-V\u2026",
      "date_published": "2016-10-30T17:46:27.0000000Z",
      "tags": [
        "altaro",
        "altaro hyper-v",
        "error",
        "errors",
        "hyper-v",
        "microsoft hyper-v",
        "microsoft hyper-v 2012"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/suggestions-are-not-provided-because-most-attendees-are-not-available-during-your-working-hours",
      "url": "https://evotec.xyz/fr/blog/suggestions-are-not-provided-because-most-attendees-are-not-available-during-your-working-hours",
      "title": "Suggestions are not provided because most attendees are not available during your working hours",
      "summary": "\u201CSuggestions are not provided because most attendees are not available during your working hours.\u201D \u2013 is one of those messages you\u2026",
      "date_published": "2016-10-22T10:22:31.0000000Z",
      "tags": [
        "error",
        "Exchange",
        "exchange 2010",
        "exchange 2013",
        "exchange 2016",
        "outlook 2010",
        "outlook 2013",
        "outlook 2016",
        "room finder"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/get-adpermission-the-operation-couldnt-be-performed-because-object",
      "url": "https://evotec.xyz/fr/blog/get-adpermission-the-operation-couldnt-be-performed-because-object",
      "title": "Get-AdPermission \u2013 The operation couldn\u2019t be performed because object couldn\u2019t be found",
      "summary": "During our recent creation of Relay Receive Connector on Exchange 2013 we\u2019ve encountered an error: The operation couldn\u2019t be performed because object. Since time\u2026",
      "date_published": "2016-02-25T19:50:34.0000000Z",
      "tags": [
        "error",
        "exchange",
        "exchange 2013",
        "powershell"
      ]
    },
    {
      "id": "https://evotec.xyz/fr/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message",
      "url": "https://evotec.xyz/fr/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message",
      "title": "Microsoft Exchange \u2013 Connecting to remote server failed with the following error message",
      "summary": "Connecting to Microsoft Exchange via PowerShell is a standard administrative tasks since Exchange 2007 was released. It\u2019s available in all\u2026",
      "date_published": "2015-11-26T17:47:09.0000000Z",
      "tags": [
        "error",
        "exchange",
        "microsoft exchange",
        "microsoft exchange 2007",
        "microsoft exchange 2010",
        "microsoft exchange 2013",
        "microsoft exchange 2016",
        "microsoft exchange server",
        "powershell",
        "ssl certificate"
      ]
    }
  ]
}