<feed xmlns="http://www.w3.org/2005/Atom"><title>error</title><id>https://evotec.xyz/de/tags/error/index.atom.xml</id><updated>2024-10-02T12:17:34.0000000Z</updated><subtitle>Evotec Main Website</subtitle><link href="https://evotec.xyz/de/tags/error" /><link href="https://evotec.xyz/de/tags/error/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>Upgrade Azure Active Directory Connect fails with unexpected error</title><id>https://evotec.xyz/de/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error</id><link href="https://evotec.xyz/de/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error" /><updated>2024-10-02T12:17:34.0000000Z</updated><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’re finished. However, this time, I encountered an error.</summary><category term="azure ad" /><category term="azure adconnect" /><category term="error" /><category term="errors" /><category term="Office 365" /><category term="office365" /></entry><entry><title>Active Directory – The directory service was unable to allocate a relative identifier</title><id>https://evotec.xyz/de/blog/active-directory-the-directory-service-was-unable-to-allocate-a-relative-identifier</id><link href="https://evotec.xyz/de/blog/active-directory-the-directory-service-was-unable-to-allocate-a-relative-identifier" /><updated>2019-03-27T20:39:25.0000000Z</updated><summary>I’ve 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’s best to do so. If you can’t, 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:</summary><category term="active directory" /><category term="ad" /><category term="error" /><category term="powershell" /></entry><entry><title>Hyper-V – Can’t start Virtual Machine because it’s backing up</title><id>https://evotec.xyz/de/blog/hyper-v-cant-start-virtual-machine-because-its-backing-up</id><link href="https://evotec.xyz/de/blog/hyper-v-cant-start-virtual-machine-because-its-backing-up" /><updated>2019-02-25T21:29:14.0000000Z</updated><summary>Working as a small business often brings you little tasks here and there. Today I’ve decided to shut down the Hyper-V machine to expand its disks. Unfortunately for me, while extending of HDD went great, I couldn’t start Virtual Machine any longer.</summary><category term="backup" /><category term="error" /><category term="hyper-v" /><category term="powershell" /></entry><entry><title>Outlook – The primary account cannot be removed unless it is the only account in the profile</title><id>https://evotec.xyz/de/blog/outlook-the-primary-account-cannot-be-removed-unless-it-is-the-only-account-in-the-profile</id><link href="https://evotec.xyz/de/blog/outlook-the-primary-account-cannot-be-removed-unless-it-is-the-only-account-in-the-profile" /><updated>2018-11-23T22:39:44.0000000Z</updated><summary>Last few months I’m 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’s 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’s how I have always done this till now. My Client has gone thru setting up 1000+ 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.</summary><category term="error" /><category term="exchange" /><category term="outlook" /><category term="PowerShell" /><category term="windows" /></entry><entry><title>Azure ADConnect Export Failed – Permission-issue error</title><id>https://evotec.xyz/de/blog/azure-adconnect-export-failed-permission-issue-error</id><link href="https://evotec.xyz/de/blog/azure-adconnect-export-failed-permission-issue-error" /><updated>2017-10-08T19:23:20.0000000Z</updated><summary>During our recent setup of Azure ADConnect for one of our Clients we’ve been getting permission-issue – Insufficient access rights…</summary><category term="active directory" /><category term="adconnect" /><category term="azure ad" /><category term="azure adconnect" /><category term="error" /><category term="errors" /><category term="export failed" /><category term="office 365" /><category term="permission-issue" /><category term="permissions" /><category term="powershell" /><category term="windows 2012R2" /><category term="windows 2016" /><category term="windows server 2016" /></entry><entry><title>UniFi Controller upgrade on Ubuntu fails during package installation</title><id>https://evotec.xyz/de/blog/unifi-controller-upgrade-ubuntu-fails-package-installation</id><link href="https://evotec.xyz/de/blog/unifi-controller-upgrade-ubuntu-fails-package-installation" /><updated>2017-08-06T10:18:10.0000000Z</updated><summary>We’re a huge fan of Ubiquity hardware, especially it’s UniFi products line. It’s nice, modern hardware with lots of functionalities…</summary><category term="5.5.19" /><category term="5.5.20" /><category term="apt update" /><category term="apt upgrade" /><category term="debian" /><category term="error" /><category term="errors" /><category term="hardware" /><category term="ubiquiti" /><category term="ubuntu" /><category term="unifi" /></entry><entry><title>Hyper-V – There was an error during move operation</title><id>https://evotec.xyz/de/blog/hyper-v-error-move-operation</id><link href="https://evotec.xyz/de/blog/hyper-v-error-move-operation" /><updated>2017-06-11T16:31:03.0000000Z</updated><summary>Windows Hyper-V with it’s live migration is a great feature… when it works! Unfortunately after setting it up things weren’t…</summary><category term="Active Directory" /><category term="error" /><category term="hyper-v" /><category term="microsoft" /><category term="microsoft windows" /><category term="windows 2012" /><category term="windows 2012R2" /><category term="windows 2016" /><category term="windows hyper-v" /></entry><entry><title>The shadow copy provider had an unexpected error while trying to process the specified command.</title><id>https://evotec.xyz/de/blog/the-shadow-copy-provider-had-an-unexpected-error-while-trying-to-process-the-specified-command</id><link href="https://evotec.xyz/de/blog/the-shadow-copy-provider-had-an-unexpected-error-while-trying-to-process-the-specified-command" /><updated>2017-02-02T19:48:44.0000000Z</updated><summary>Recently we had a case where an offsite backup in Altaro VM Backup was supposed to be written to Western…</summary><category term="altaro" /><category term="error" /><category term="errors" /><category term="shadow copy provider" /><category term="vss" /><category term="vss error" /><category term="vssadmin" /><category term="Windows" /></entry><entry><title>Microsoft Exchange – OU picker is empty when creating new user</title><id>https://evotec.xyz/de/blog/microsoft-exchange-ou-picker-empty-creating-new-user</id><link href="https://evotec.xyz/de/blog/microsoft-exchange-ou-picker-empty-creating-new-user" /><updated>2016-11-01T11:24:27.0000000Z</updated><summary>We’ve migrated one of our Clients fairly early but recently we got complain that when new user is created from…</summary><category term="error" /><category term="exchange" /><category term="exchange 2013" /><category term="microsoft exchange" /><category term="microsoft exchange server" /></entry><entry><title>Hyper-V – Incorrect function when trying to move files</title><id>https://evotec.xyz/de/blog/hyper-v-incorrect-function-when-trying-to-move-files</id><link href="https://evotec.xyz/de/blog/hyper-v-incorrect-function-when-trying-to-move-files" /><updated>2016-10-30T17:46:27.0000000Z</updated><summary>When we are asked by our Clients to setup their servers we usually go with virtualization. We usually choose Hyper-V…</summary><category term="altaro" /><category term="altaro hyper-v" /><category term="error" /><category term="errors" /><category term="hyper-v" /><category term="microsoft hyper-v" /><category term="microsoft hyper-v 2012" /></entry><entry><title>Suggestions are not provided because most attendees are not available during your working hours</title><id>https://evotec.xyz/de/blog/suggestions-are-not-provided-because-most-attendees-are-not-available-during-your-working-hours</id><link href="https://evotec.xyz/de/blog/suggestions-are-not-provided-because-most-attendees-are-not-available-during-your-working-hours" /><updated>2016-10-22T10:22:31.0000000Z</updated><summary>“Suggestions are not provided because most attendees are not available during your working hours.” – is one of those messages you…</summary><category term="error" /><category term="Exchange" /><category term="exchange 2010" /><category term="exchange 2013" /><category term="exchange 2016" /><category term="outlook 2010" /><category term="outlook 2013" /><category term="outlook 2016" /><category term="room finder" /></entry><entry><title>Get-AdPermission – The operation couldn’t be performed because object couldn’t be found</title><id>https://evotec.xyz/de/blog/get-adpermission-the-operation-couldnt-be-performed-because-object</id><link href="https://evotec.xyz/de/blog/get-adpermission-the-operation-couldnt-be-performed-because-object" /><updated>2016-02-25T19:50:34.0000000Z</updated><summary>During our recent creation of Relay Receive Connector on Exchange 2013 we’ve encountered an error: The operation couldn’t be performed because object. Since time…</summary><category term="error" /><category term="exchange" /><category term="exchange 2013" /><category term="powershell" /></entry><entry><title>Microsoft Exchange – Connecting to remote server failed with the following error message</title><id>https://evotec.xyz/de/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message</id><link href="https://evotec.xyz/de/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message" /><updated>2015-11-26T17:47:09.0000000Z</updated><summary>Connecting to Microsoft Exchange via PowerShell is a standard administrative tasks since Exchange 2007 was released. It’s available in all…</summary><category term="error" /><category term="exchange" /><category term="microsoft exchange" /><category term="microsoft exchange 2007" /><category term="microsoft exchange 2010" /><category term="microsoft exchange 2013" /><category term="microsoft exchange 2016" /><category term="microsoft exchange server" /><category term="powershell" /><category term="ssl certificate" /></entry></feed>