<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>error</title><link>https://evotec.xyz/fr/tags/error</link><description>Evotec Main Website</description><atom:link href="https://evotec.xyz/fr/tags/error/index.xml" rel="self" type="application/rss+xml" /><item><title>Upgrade Azure Active Directory Connect fails with unexpected error</title><link>https://evotec.xyz/fr/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error</link><description>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.</description><pubDate>Wed, 02 Oct 2024 12:17:34 GMT</pubDate><guid>https://evotec.xyz/fr/blog/upgrade-azure-active-directory-connect-fails-with-unexpected-error</guid><category>azure ad</category><category>azure adconnect</category><category>error</category><category>errors</category><category>Office 365</category><category>office365</category></item><item><title>Active Directory – The directory service was unable to allocate a relative identifier</title><link>https://evotec.xyz/fr/blog/active-directory-the-directory-service-was-unable-to-allocate-a-relative-identifier</link><description>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:</description><pubDate>Wed, 27 Mar 2019 20:39:25 GMT</pubDate><guid>https://evotec.xyz/fr/blog/active-directory-the-directory-service-was-unable-to-allocate-a-relative-identifier</guid><category>active directory</category><category>ad</category><category>error</category><category>powershell</category></item><item><title>Hyper-V – Can’t start Virtual Machine because it’s backing up</title><link>https://evotec.xyz/fr/blog/hyper-v-cant-start-virtual-machine-because-its-backing-up</link><description>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.</description><pubDate>Mon, 25 Feb 2019 21:29:14 GMT</pubDate><guid>https://evotec.xyz/fr/blog/hyper-v-cant-start-virtual-machine-because-its-backing-up</guid><category>backup</category><category>error</category><category>hyper-v</category><category>powershell</category></item><item><title>Outlook – The primary account cannot be removed unless it is the only account in the profile</title><link>https://evotec.xyz/fr/blog/outlook-the-primary-account-cannot-be-removed-unless-it-is-the-only-account-in-the-profile</link><description>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.</description><pubDate>Fri, 23 Nov 2018 22:39:44 GMT</pubDate><guid>https://evotec.xyz/fr/blog/outlook-the-primary-account-cannot-be-removed-unless-it-is-the-only-account-in-the-profile</guid><category>error</category><category>exchange</category><category>outlook</category><category>PowerShell</category><category>windows</category></item><item><title>Azure ADConnect Export Failed – Permission-issue error</title><link>https://evotec.xyz/fr/blog/azure-adconnect-export-failed-permission-issue-error</link><description>During our recent setup of Azure ADConnect for one of our Clients we’ve been getting permission-issue – Insufficient access rights…</description><pubDate>Sun, 08 Oct 2017 19:23:20 GMT</pubDate><guid>https://evotec.xyz/fr/blog/azure-adconnect-export-failed-permission-issue-error</guid><category>active directory</category><category>adconnect</category><category>azure ad</category><category>azure adconnect</category><category>error</category><category>errors</category><category>export failed</category><category>office 365</category><category>permission-issue</category><category>permissions</category><category>powershell</category><category>windows 2012R2</category><category>windows 2016</category><category>windows server 2016</category></item><item><title>UniFi Controller upgrade on Ubuntu fails during package installation</title><link>https://evotec.xyz/fr/blog/unifi-controller-upgrade-ubuntu-fails-package-installation</link><description>We’re a huge fan of Ubiquity hardware, especially it’s UniFi products line. It’s nice, modern hardware with lots of functionalities…</description><pubDate>Sun, 06 Aug 2017 10:18:10 GMT</pubDate><guid>https://evotec.xyz/fr/blog/unifi-controller-upgrade-ubuntu-fails-package-installation</guid><category>5.5.19</category><category>5.5.20</category><category>apt update</category><category>apt upgrade</category><category>debian</category><category>error</category><category>errors</category><category>hardware</category><category>ubiquiti</category><category>ubuntu</category><category>unifi</category></item><item><title>Hyper-V – There was an error during move operation</title><link>https://evotec.xyz/fr/blog/hyper-v-error-move-operation</link><description>Windows Hyper-V with it’s live migration is a great feature… when it works! Unfortunately after setting it up things weren’t…</description><pubDate>Sun, 11 Jun 2017 16:31:03 GMT</pubDate><guid>https://evotec.xyz/fr/blog/hyper-v-error-move-operation</guid><category>Active Directory</category><category>error</category><category>hyper-v</category><category>microsoft</category><category>microsoft windows</category><category>windows 2012</category><category>windows 2012R2</category><category>windows 2016</category><category>windows hyper-v</category></item><item><title>The shadow copy provider had an unexpected error while trying to process the specified command.</title><link>https://evotec.xyz/fr/blog/the-shadow-copy-provider-had-an-unexpected-error-while-trying-to-process-the-specified-command</link><description>Recently we had a case where an offsite backup in Altaro VM Backup was supposed to be written to Western…</description><pubDate>Thu, 02 Feb 2017 19:48:44 GMT</pubDate><guid>https://evotec.xyz/fr/blog/the-shadow-copy-provider-had-an-unexpected-error-while-trying-to-process-the-specified-command</guid><category>altaro</category><category>error</category><category>errors</category><category>shadow copy provider</category><category>vss</category><category>vss error</category><category>vssadmin</category><category>Windows</category></item><item><title>Microsoft Exchange – OU picker is empty when creating new user</title><link>https://evotec.xyz/fr/blog/microsoft-exchange-ou-picker-empty-creating-new-user</link><description>We’ve migrated one of our Clients fairly early but recently we got complain that when new user is created from…</description><pubDate>Tue, 01 Nov 2016 11:24:27 GMT</pubDate><guid>https://evotec.xyz/fr/blog/microsoft-exchange-ou-picker-empty-creating-new-user</guid><category>error</category><category>exchange</category><category>exchange 2013</category><category>microsoft exchange</category><category>microsoft exchange server</category></item><item><title>Hyper-V – Incorrect function when trying to move files</title><link>https://evotec.xyz/fr/blog/hyper-v-incorrect-function-when-trying-to-move-files</link><description>When we are asked by our Clients to setup their servers we usually go with virtualization. We usually choose Hyper-V…</description><pubDate>Sun, 30 Oct 2016 17:46:27 GMT</pubDate><guid>https://evotec.xyz/fr/blog/hyper-v-incorrect-function-when-trying-to-move-files</guid><category>altaro</category><category>altaro hyper-v</category><category>error</category><category>errors</category><category>hyper-v</category><category>microsoft hyper-v</category><category>microsoft hyper-v 2012</category></item><item><title>Suggestions are not provided because most attendees are not available during your working hours</title><link>https://evotec.xyz/fr/blog/suggestions-are-not-provided-because-most-attendees-are-not-available-during-your-working-hours</link><description>“Suggestions are not provided because most attendees are not available during your working hours.” – is one of those messages you…</description><pubDate>Sat, 22 Oct 2016 10:22:31 GMT</pubDate><guid>https://evotec.xyz/fr/blog/suggestions-are-not-provided-because-most-attendees-are-not-available-during-your-working-hours</guid><category>error</category><category>Exchange</category><category>exchange 2010</category><category>exchange 2013</category><category>exchange 2016</category><category>outlook 2010</category><category>outlook 2013</category><category>outlook 2016</category><category>room finder</category></item><item><title>Get-AdPermission – The operation couldn’t be performed because object couldn’t be found</title><link>https://evotec.xyz/fr/blog/get-adpermission-the-operation-couldnt-be-performed-because-object</link><description>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…</description><pubDate>Thu, 25 Feb 2016 19:50:34 GMT</pubDate><guid>https://evotec.xyz/fr/blog/get-adpermission-the-operation-couldnt-be-performed-because-object</guid><category>error</category><category>exchange</category><category>exchange 2013</category><category>powershell</category></item><item><title>Microsoft Exchange – Connecting to remote server failed with the following error message</title><link>https://evotec.xyz/fr/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message</link><description>Connecting to Microsoft Exchange via PowerShell is a standard administrative tasks since Exchange 2007 was released. It’s available in all…</description><pubDate>Thu, 26 Nov 2015 17:47:09 GMT</pubDate><guid>https://evotec.xyz/fr/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message</guid><category>error</category><category>exchange</category><category>microsoft exchange</category><category>microsoft exchange 2007</category><category>microsoft exchange 2010</category><category>microsoft exchange 2013</category><category>microsoft exchange 2016</category><category>microsoft exchange server</category><category>powershell</category><category>ssl certificate</category></item></channel></rss>