The remote server returned an error 409 conflict

Hello,

We’re trying to upload a lot of data (350+GB) to our on premises instance of SharePoint 2013.

This data is currently on a shared drive and consists of 1M+ documents on probably 10000+ different folders.

I’ve written a simple multithreaded tool that uploads the files to SP.

The his uses Parallel.ForEach. and works ok with small amounts of data, but when we try it in anger we tart getting this exception

Net.WebException: The remote server returned an error: (409) Conflict.
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()
   at Microsoft.SharePoint.Client.File.SaveBinary(ClientContext context, String serverRelativeUrl, Stream stream, String etag, Boolean overwriteIfExists, SaveBinaryCheckMode checkMode)
   at Migrator.Program.UploadFile(ClientContext context, String filePath, Boolean exception) in c

Interestingly, if I ramp up the number of threads, I get a lot more of these exceptions.

Perhaps, more interestingly we seem to get the error always for the same files, at least after two tries.

I can’t really see anything on the SP log, at least anything I can make sense out of.

The below seems to happen after the issue occurrs but not sure if this is the case or just an unrelated exception.

Set EventFiringDisabled to [False].  Stack trace: [   at Microsoft.Office.Server.Utilities.EventReceiverUtility.DisabledEventFiringScope.Dispose()     
at Microsoft.Office.Server.Utilities.EventReceiverUtility.RunItemEventReceiverExProps(Boolean handleVersionConflicts, MonitoredScopeWrapper monitoredScopeWrapper, Boolean disableEventFiring, SPItemEventProperties properties, ItemEventReceiverCodeToRunProps
codeToRun)     at Microsoft.Office.Server.Utilities.EventReceiverUtility.RunAndHandleVersionConflictsExProps(MonitoredScopeWrapper monitoredScopeWrapper, Boolean disableEventFiring, SPItemEventProperties properties, ItemEventReceiverCodeToRunProps
codeToRun)     at Microsoft.Office.DocumentManagement.DocumentId.ItemChangedInternal(SPItemEventProperties properties, Boolean fOverwrite)     a…
7f311d9d-2565-e02b-95fa-1ca09f0d4749
…t Microsoft.Office.DocumentManagement.Internal.DocIdHandler.ItemChangedInternal(SPItemEventProperties properties, Boolean fOverwrite)     at Microsoft.Office.DocumentManagement.Internal.DocIdHandler.ItemAdded(SPItemEventProperties properties)  
  at Microsoft.SharePoint.SPEventManager.RunItemEventReceiver(SPItemEventReceiver receiver, SPUserCodeInfo userCodeInfo, SPItemEventProperties properties, SPEventContext context, String receiverData)     at Microsoft.SharePoint.SPEventManager.RunItemEventReceiverHelper(Object
receiver, SPUserCodeInfo userCodeInfo, Object properties, SPEventContext context, String receiverData)     at Microsoft.SharePoint.SPEventManager.<>c__DisplayClassa`1.<InvokeEventReceiver>b__7()     at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken
userToken, Boolean bRe… 7f311d9d-2565-e02b-95fa-1ca09f0d4749
…setContext, WaitCallback code, Object param)     at Microsoft.SharePoint.SPEventManager.InvokeEventReceiver[ReceiverType](SPUserToken userToken, Guid tranLockerId, RunEventReceiver runEventReceiver, Object receivers, Int32 n, Object properties,
SPEventReceiverOperationsType operationsType, Boolean& canceled, String& error)     at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](SPRemoteEventReceiverCallType remoteCallType, SPUserToken userToken, Guid tranLockerId,
RunEventReceiver runEventReceiver, RunRemoteEventReceiver runRemoteEventReceiver, Object receivers, Object properties, Boolean checkCancel, SPEventReceiverOperationsType operationsType)     at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](SPRemoteEventReceiverCallType
remoteCallType,… 7f311d9d-2565-e02b-95fa-1ca09f0d4749
… Byte[] userTokenBytes, Guid tranLockerId, RunEventReceiver runEventReceiver, RunRemoteEventReceiver runRemoteEventReceiver, Object receivers, Object properties, Boolean checkCancel, SPEventReceiverOperationsType operationsType)     at Microsoft.SharePoint.SPEventManager.ExecuteItemEventReceivers(Byte[]&
userToken, Guid& tranLockerId, Object& receivers, ItemEventReceiverParams& itemEventParams, Object& changedFields, EventReceiverResult& eventResult, String& errorMessage)     at Microsoft.SharePoint.Library.SPRequestInternalClass.AddOrDeleteUrl(String
bstrUrl, String bstrDirName, Boolean bAdd, UInt32 dwDeleteOp, Int32 iUserId, Guid& pgDeleteTransactionId)     at Microsoft.SharePoint.Library.SPRequestInternalClass.AddOrDeleteUrl(String bstrUrl, String bstrDirName, Boolean bAdd, UInt32 dwDel…
7f311d9d-2565-e02b-95fa-1ca09f0d4749
…eteOp, Int32 iUserId, Guid& pgDeleteTransactionId)     at Microsoft.SharePoint.Library.SPRequest.AddOrDeleteUrl(String bstrUrl, String bstrDirName, Boolean bAdd, UInt32 dwDeleteOp, Int32 iUserId, Guid& pgDeleteTransactionId)    
at Microsoft.SharePoint.SPFolderCollection.AddInternal(String strUrl, Int32 userId)     at LD_FolderStructure.Events.Events.CreateFolderStructure(SPItemEventProperties properties)     at Microsoft.SharePoint.SPEventManager.RunItemEventReceiver(SPItemEventReceiver
receiver, SPUserCodeInfo userCodeInfo, SPItemEventProperties properties, SPEventContext context, String receiverData)     at Microsoft.SharePoint.SPEventManager.RunItemEventReceiverHelper(Object receiver, SPUserCodeInfo userCodeInfo, Object properties,
SPEventContext context, String receiverData)     at Mi…
7f311d9d-2565-e02b-95fa-1ca09f0d4749
…crosoft.SharePoint.SPEventManager.<>c__DisplayClassa`1.<InvokeEventReceiver>b__7()     at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param)     at Microsoft.SharePoint.SPEventManager.InvokeEventReceiver[ReceiverType](SPUserToken
userToken, Guid tranLockerId, RunEventReceiver runEventReceiver, Object receivers, Int32 n, Object properties, SPEventReceiverOperationsType operationsType, Boolean& canceled, String& error)     at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](SPRemoteEventReceiverCallType
remoteCallType, SPUserToken userToken, Guid tranLockerId, RunEventReceiver runEventReceiver, RunRemoteEventReceiver runRemoteEventReceiver, Object receivers, Object properties, Boolean checkCancel, SPE…
7f311d9d-2565-e02b-95fa-1ca09f0d4749
…ventReceiverOperationsType operationsType)     at Microsoft.SharePoint.SPEventManager.InvokeEventReceivers[ReceiverType](SPRemoteEventReceiverCallType remoteCallType, Byte[] userTokenBytes, Guid tranLockerId, RunEventReceiver runEventReceiver,
RunRemoteEventReceiver runRemoteEventReceiver, Object receivers, Object properties, Boolean checkCancel, SPEventReceiverOperationsType operationsType)     at Microsoft.SharePoint.SPEventManager.HandleEventCallback[ReceiverType,PropertiesType](Object
callbackData)     at Microsoft.SharePoint.Utilities.SPThreadPool.WaitCallbackWrapper(Object state)     at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
    at System.Threading.ExecutionContext.Run(Execution…
7f311d9d-2565-e02b-95fa-1ca09f0d4749
…Context executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)     at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()     at System.Threading.ThreadPoolWorkQueue.Dispatch()
 ] 7f311d9d-2565-e02b-95fa-1ca09f0d4749

Any ideas?

Thanks

Ошибка HTTP 409 Conflicting Request: что значит, как появилась, как исправить?

Ошибка HTTP 409 Conflicting Request – это конфликт между запросом пользователя и сервером, к которому он обращается. Например, есть сайт, с которого пользователь хочет скачать файл с названием «файл1», но этот файл раньше был на сервере и его упоминание сохранилось в кеше. Однако, теперь файл называется “файл01» и сервер не понимает, что пользователь хочет от него. Это очень образный пример для того, чтобы максимально понятно определить значение ошибки.

Ситуации при которых возникает ошибка 409 HTTP сильно разнятся, но сводятся к конфликту между запросами. Иногда, задавая запрос, браузер сам уходит в цикличную обработку, и он либо закрывается, либо виснет так, что пользователю ничего не остается, как просто перезагрузить компьютер. Это явление часто замечают пользователи браузера Mozilla и Opera.

Как и где появляется ошибка 409?

Выше упоминалось, что природа происхождения ошибки 409 кроется в конфликте запросов. Не всегда эти запросы относятся к пользовательским. Например, такая ошибка может возникнуть при конфликте файлов сайта, если они обращаются к разным данным в одном файле. В результате этого, сервер возвращает ошибку, которая на самом деле не имеет отношения к запросам пользователей.

Основные причины возникновения ошибки 409:

• Пользователь обращается к данным, имеющим отличное значение или более новую версию. В итоге, сервер выдает ошибку 409, т.к. существует обновленная версия файла, страницы или скрипта.
• Ошибка 409 появилась в результате конфликтующих запросов внутри файлов на сервере. Решить проблему может программист.
• Использование прокси, которое конфликтует с определенными адресами или форматами запрашиваемых данных. Не путайте эту ошибку с ошибкой 407.
• Более распространенная причина – троян или вирус, который блокирует запросы к определенным сайтам или подгружает файл, который имеет конфликт с конфигурацией браузера.

Ошибка 409 Conflicting Request в большинстве случае решается системным администратором или программистом, если это не касается заражения компьютера вирусом или трояном. Как проверить и какой программой расскажем ниже.

Как исправить ошибку 409 (Conflicting Request – Конфликт запросов)?

На некоторых сайтах приведен целый список шагов для устранения ошибки 409. Вот только проблема в том, что это не имеет смысла, т.к. эта ошибка касается программистов или разработчиков сайта / приложения. Конечный пользователь не сможет исправить ошибку 409, если только это не касается вируса или трояна.

1. Чистим от вируса или трояна, чтобы убрать ошибку 409

Определить вирус/троян у вас или нет просто – установите программу Cureit от Dr.Web и просканируйте систему этой программой. Она бесплатная и не требует установки. Скачиваем только с официального сайта. В программе отмечаем все пункты для проверки и шагаем спать/на работу, т.к. сама проверка займет длительное время. На скриншоте ниже вы можете рассмотреть, как и что отмечать в программе. Свой антивирус лучше отключить перед проверкой.

Чистим от вируса или трояна, чтобы убрать ошибку 409

Можно также использовать бесплатную утилиту от Касперского, но она довольно сложная и нужно понимать, какие скрипты вводить в консоль. Остальные программы – платные, поэтому не пишу о них. Кстати, не рекомендую скачивать бесплатные ключи, т.к. такие генераторы могут с собой принести тот самый вирус или троян. Не пожалейте 30$ в год за нормальную защиту.

1. Исправляем ошибку 409 в конкретном браузере

В случае, если ошибка 409 Conflicting Request появляется буквально на каждом сайте, чтобы вы ни нажимали – это точно троян или вирус. Причем это должно происходить в любом браузере. Если нет – можете сразу удалить и заново установить браузер. Возможно произошел сбой конфигурации браузера.

Перед удалением браузера сохраните закладки!

Заранее нужно сохранить закладки, т.к. можно потерять все нажитое непосильным трудом. Делается это просто. На скриншоте выше вы видите пример сохранения настроек в браузере Mozilla. Аналогично делается и в остальных браузерах.

1. Ошибка 409 в результате правок на сайте

Если вы являетесь администратором сайта или программистом… Вы знаете, что такое бэкап и как им пользоваться. Если не знаете – спросите в комментариях. Что с ним делать? Думаю, ответ знаете сами.

Последнее слово про ошибку

Ошибка 409 HTTP Conflicting Request редко относится к пользователю, если только это не вирус или троян. Почти 80% случаев с этой ошибкой касается разработчиков, поэтому разбираться в этом нужно точно не обычному пользователю. Все советы про чистку реестра и прочее – не актуальны. Это не относится к этой ошибке.

Если уж сильно хочется – установите программу CCleaner и пройдитесь по реестру с помощью этой программы. Во всяком случае это безопаснее, чем делать что-то лично ручками. Манипуляции с компьютером в случае с ошибкой 409 делать не стоит.

Источник

KB4511868 — FIX: Error 409 occurs when you back up databases by using BackuptoURL

Symptoms

When you back up your databases to Azure Page Blobs by using BackuptoURL statements, you may receive an error message that resembles the following:

Date and time: DateTime
Command: BACKUP LOG [SAMPLEDB] TO URL = N’UrlPath’ WITH CHECKSUM, NO_COMPRESSION, CREDENTIAL = N’ CredentialName‘
Msg 3271, Level 16, State 1, Server ServerName, Line LineNumber
A nonrecoverable I/O error occurred on file FilePath Backup to URL received an exception from the remote endpoint. Exception Message: The remote server returned an error: (409) Conflict..
Msg 3013, Level 16, State 1, Server ServerName, Line LineNumber
BACKUP LOG is terminating abnormally.
Outcome: Failed
Duration: DurationTime

Date and time: DateTime

Note The issue affects Microsoft SQL Server2014, 2016 and 2017 versions. When the fix becomes available for these versions ,this KB will be updated with the relevant information.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the «Applies to» section.

Resolution

This issue is fixed in the following cumulative updates for SQL Server:

About cumulative updates for SQL Server:

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

References

Learn about the terminology that Microsoft uses to describe software updates.

Источник

How To Fix HTTP Error 409 (Conflicting Request)

Most Conflicting Request errors are the result of a missing or corrupt version of the file installed by Edge . A large percentage of these file issues can be resolved with downloading and installing the latest version of your Windows 10 file. In addition, if your Conflicting Request error was due to a removed malware infection, we recommend running a registry scan to clean up any invalid file path references created by the malicious program.

Classic Conflicting Request Problems

The most common Conflicting Request errors that can appear on a Windows-based computer are:

• «Conflicting Request error.»
• «Conflicting Request moved or missing.»
• «Conflicting Request is missing.»
• «Conflicting Request failed to load.»
• «Registration failure: Conflicting Request.»
• «Conflicting Request Runtime Error.»
• «Loading error: Conflicting Request.»

Ordinarily, Conflicting Request-related Blue Screen errors happen when a Microsoft Corporation-related device driver is loaded, during the install of Edge or related program, or while Windows is starting or shutting down. Tracking Conflicting Request errors associated with Edge is critical to locating faults and relaying back to Microsoft Corporation for repair options.

Conflicting Request Problem Causes

Malware infestation, invalid Edge registry entries, or missing / corrupt Conflicting Request files can create these Conflicting Request errors.

Primarily, issues with Conflicting Request produced by:

• Conflicting Request registry key corrupted.
• Virus has infected Conflicting Request, creating corruption.
• Malicious deletion (or mistaken) of Conflicting Request by another application (not Edge ).
• Another program is in conflict with Edge and its shared referenced files.
• Corrupted installation or download of Edge (Conflicting Request).

Compatible with Windows 11, 10, 8, 7, Vista, XP and 2000

Источник

«409 Conflict» causes Runner to not run any jobs, and give up checking for new jobs for half an hour

Status update: 2022-12-04

@stanhu spent quite a bit of time analyzing this issue. As a result we are proposing closing this issue in 14.6 pending any customer or community member feedback that they are still begin negatively impacted by the 409 conflict error.

Here are our findings to date:

409 Conflict errors are normal and expected in cases where you have multiple runners configured and trying to pick up the same job. If a 409 conflict occurs for this use case, then in our testing to date, we have not been able to reproduce the situation where the execution of jobs in the queue is delayed or not picked up for execution.

Note as stated in the detailed analysis below, the more concurrent Runners that are configured and that can request a job, the greater the probability of generating the 409 conflict error.

Workaround

In the extreme case where you’re ALWAYS getting 409’s once your runner is up and running, this could be caused by a «bad» advertise_address value for your [session_server] section in the config.toml. If you’re experiencing this and you have a [session_server] settings configured (other than the default session_timeout) please comment them out and see if that allows the runner to pick up jobs.

What do I do I am still being impacted by these errors?

If you are noticing 409 conflict errors and the resultant behavior is that the the Runner is not reporting new jobs received, then this could be expected if there are no jobs pending in the queue for the runner.

If you are noticing 409 conflict errors and the resultant behavior is that there are pending jobs in the queue and the runner is not asking for them, then this is in fact a problem and will require further investigation.

For number 2, we will need data from your environment in order to debug your specific issue.

Original problem statement:

1. A random 409 Conflict for no good reason. It just stopped working.
2. After 4 tries, GitLab Runner totally gave up checking for new jobs for half an hour.
3. During that «downtime», the runner was reported as active in GitLab UI — «Last contact» read 1/2 minutes all the time.

Environment description

Used GitLab Runner version

I don’t have the log output indicating this is the version currently running but given the build date (2019-06-03T10:57:49+0000), and process age (Jun03), we can conclude it’s the version currently running.

Possible fixes

1. Don’t throw 409 Conflict at me.
2. Don’t give up for half an hour when faced with 409 Conflict.

The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Источник

Solving the conflict of using the HTTP status 409

I’ve probably seen this status code for the first time today, in an assignment submitted by a student. It’s defined as 409 conflict. The corresponding RFC indicates that

. the request could not be completed due to a conflict with the current state of the target resource

However, a bunch of questions in Stackoverflow there’s no real consensus on when to actually use as opposed to the other options indicated in the answers: 403, 412 or even 422.

Let’s see first to which verb it should respond to. The RFC says:

. Conflicts are most likely to occur in response to a PUT request.

But, PUT should be used when we want to modify a resource under the supplied URI. So where’s the conflict? Here’s the state I want, take it, whatever was there before, just forget it. If there’s a conflict with existing state (whatever that is), we’re explicitly telling the system to solve that conflict by adopting this new state.

Things are never so simple, however. My point here is that PUT is rather imperative. If you want the system to create a resource out of what you’re supplying, POST is quite possibly a better match, since you’re submitting some data and telling the system to create a resource out of it. The system might say: well, not possible, here’s your 409 status (with an informative message, of course, as the spec says).

And yet, 409 is used all the time with PUT requests. WebDAV returns 409 when you’re trying to upload a file that’s older than the one it’s trying to substitute or there’s no collection properly set up for it.

It might be questionable the use of PUT here, since idempotency is not really guaranteed: the state of the directory is going to be changed. But that’s what’s used.

In some other cases, it’s returned when something is not recognized. In both cases (and some other you might think of), there’s no real conflict anywhere. You’re trying to upload a file to somewhere you shouldn’t, well, unauthorized 403 might be it. There’s some error in the way you put the data together, that’s no doubt a bad request. Where’s the conflict?

There might be an actual use case for 409, right?

Proposed best practice for 409 conflict

When you use PUT, you create a resource with the data that’s in the URI or in the body. But there’s some metadata you should take into account, too. The one that goes in the header, which goes from MIME Types to ETags to custom headers.

And here’s the thing: those custom headers might be in conflict with the actual data that’s contained there. That’s actually one of the things that WebDAV does: there’s a custom version header, and that version has to increase if you don’t want the new state to be in conflict with the state it substitutes. The spec for 409 also indicates that the user should be able to do something about the data: in the case of a custom header, the client needs to have a good representation of the state; if it does not, there will be a conflict.

But a header is, in general, a meta-state, that is, not exactly part of the metadata, but rather part of the data we have about that data. What we’re proposing here is actually to use 409, then, when there’s a conflict between the desired or existing state and their metadata. That’s a more precise definition (and use case) than simply «a conflict in the state».

Источник

Description

Executing the following commands used to work fine just few weeks ago:

$containerName = "$Usage-$Stamp-$azureRegionAbbreviation-$Environment-$dt".ToLowerInvariant()
New-AzureRmStorageContainer `
        -ContainerName $containerName `
        -StorageAccount $storageAccount `
        -PublicAccess Container `
        -Verbose

Set-AzureRmStorageContainerImmutabilityPolicy `
        -ResourceGroupName $resourceGroupName `
        -StorageAccountName $storageAccountName `
        -ContainerName $containerName `
        -ImmutabilityPeriod 3 `
        -ErrorAction Continue `
        -Verbose

Set-AzureStorageBlobContent `
        -File $file `
        -Blob $blob `
        -Container $containerName `
        -Context $storageAccount.Context `
        -Force

And now it always fails with this error:

Set-AzureStorageBlobContent : The remote server returned an error: (409) Conflict. HTTP Status Code: 409 — HTTP Error Message: This operation is not
permitted as the blob is immutable due to a policy.

Steps to reproduce

Module versions

ModuleType Version    Name                                ExportedCommands            
---------- -------    ----                                ----------------            
Script     5.8.2      AzureRM.profile
Script     6.7.3      AzureRM.Resources
Script     5.2.0      AzureRM.Storage
Script     4.6.1      Azure.Storage

Debug output

DEBUG: 17:51:41 - Init Operation Context for 'SetAzureBlobContentCommand' with client request id
Azure-Storage-PowerShell-ee76c923-2482-4007-be43-13df225be153. If you want to get more details, please add "-Debug" to your command.
DEBUG: 17:51:41 - SetAzureBlobContentCommand begin processing with ParameterSet 'SendManual'.
DEBUG: 17:51:41 - Use storage account 'xxx' from storage context.
DEBUG: 17:51:41 - SetAzureBlobContentCommand end processing, Start 212 remote calls. Finish 212 remote calls. Elapsed time 618285596.19 ms. Client operation
id: Azure-Storage-PowerShell-ee76c923-2482-4007-be43-13df225be153.
DEBUG: 17:51:41 - SetAzureBlobContentCommand end processing.
DEBUG: 17:51:41 - Init Operation Context for 'SetAzureBlobContentCommand' with client request id
Azure-Storage-PowerShell-ee76c923-2482-4007-be43-13df225be153. If you want to get more details, please add "-Debug" to your command.
DEBUG: 17:51:41 - SetAzureBlobContentCommand begin processing with ParameterSet 'SendManual'.
DEBUG: 17:51:41 - Use storage account 'xxx' from storage context.
Set-AzureStorageBlobContent : The remote server returned an error: (409) Conflict. HTTP Status Code: 409 - HTTP Error Message: This operation is not
permitted as the blob is immutable due to a policy.
At srcresourcesscriptsNew-DataCenter.ps1:164 char:2
+     Set-AzureStorageBlobContent -File $file `
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Set-AzureStorageBlobContent], StorageException
    + FullyQualifiedErrorId : StorageException,Microsoft.WindowsAzure.Commands.Storage.Blob.SetAzureBlobContentCommand

DEBUG: 17:51:41 - SetAzureBlobContentCommand end processing, Start 212 remote calls. Finish 212 remote calls. Elapsed time 618285661.16 ms. Client operation
id: Azure-Storage-PowerShell-ee76c923-2482-4007-be43-13df225be153.
DEBUG: 17:51:41 - SetAzureBlobContentCommand end processing.

Error output

Message        : The remote server returned an error: (409) Conflict. HTTP Status Code: 409 - HTTP Error Message: This operation is not permitted as the
                 blob is immutable due to a policy.
StackTrace     :
Exception      : Microsoft.WindowsAzure.Storage.StorageException
InvocationInfo : {Set-AzureStorageBlobContent}
Line           :        Set-AzureStorageBlobContent -File $file `

Position       : At srcresourcesscriptsNew-DataCenter.ps1:164 char:2
                 +     Set-AzureStorageBlobContent -File $file `
                 +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HistoryId      : 31

Message        : The remote server returned an error: (409) Conflict.
StackTrace     :    at Microsoft.WindowsAzure.Commands.Storage.Common.DataMovementTransferHelper.<DoTransfer>d__0.MoveNext()
                 --- End of stack trace from previous location where exception was thrown ---
                    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
                    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
                    at Microsoft.WindowsAzure.Commands.Storage.Blob.SetAzureBlobContentCommand.<Upload2Blob>d__45.MoveNext()
                 --- End of stack trace from previous location where exception was thrown ---
                    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
                    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
                    at Microsoft.WindowsAzure.Commands.Storage.Common.LimitedConcurrencyTaskScheduler.<RunConcurrentTask>d__26.MoveNext()
Exception      : Microsoft.WindowsAzure.Storage.StorageException
InvocationInfo : {Set-AzureStorageBlobContent}
Line           :        Set-AzureStorageBlobContent -File $file `

Position       : At srcresourcesscriptsNew-DataCenter.ps1:164 char:2
                 +     Set-AzureStorageBlobContent -File $file `
                 +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HistoryId      : 31

Message        : The remote server returned an error: (409) Conflict.
StackTrace     :    at Microsoft.WindowsAzure.Storage.Shared.Protocol.HttpResponseParsers.ProcessExpectedStatusCodeNoException[T](HttpStatusCode
                 expectedStatusCode, HttpStatusCode actualStatusCode, T retVal, StorageCommandBase`1 cmd, Exception ex)
                    at Microsoft.WindowsAzure.Storage.Blob.CloudBlockBlob.<>c__DisplayClass57.<PutBlobImpl>b__56(RESTCommand`1 cmd, HttpWebResponse resp,
                 Exception ex, OperationContext ctx)
                    at Microsoft.WindowsAzure.Storage.Core.Executor.Executor.EndGetResponse[T](IAsyncResult getResponseResult)
Exception      : System.Net.WebException
InvocationInfo : {Set-AzureStorageBlobContent}
Line           :        Set-AzureStorageBlobContent -File $file `

Position       : At srcresourcesscriptsNew-DataCenter.ps1:164 char:2
                 +     Set-AzureStorageBlobContent -File $file `
                 +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
HistoryId      : 31

[{«Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Product»:{«code»:»SSMKJE»,»label»:»IBM Incentive Compensation Management»},»Component»:»»,»Platform»:[{«code»:»PF025″,»label»:»Platform Independent»}],»Version»:»All Versions»,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

Ошибка HTTP 409 Conflicting Request – это конфликт между запросом пользователя и сервером, к которому он обращается. Например, есть сайт, с которого пользователь хочет скачать файл с названием «файл1», но этот файл раньше был на сервере и его упоминание сохранилось в кеше. Однако, теперь файл называется “файл01» и сервер не понимает, что пользователь хочет от него. Это очень образный пример для того, чтобы максимально понятно определить значение ошибки.

Ситуации при которых возникает ошибка 409 HTTP сильно разнятся, но сводятся к конфликту между запросами. Иногда, задавая запрос, браузер сам уходит в цикличную обработку, и он либо закрывается, либо виснет так, что пользователю ничего не остается, как просто перезагрузить компьютер. Это явление часто замечают пользователи браузера Mozilla и Opera.

Выше упоминалось, что природа происхождения ошибки 409 кроется в конфликте запросов. Не всегда эти запросы относятся к пользовательским. Например, такая ошибка может возникнуть при конфликте файлов сайта, если они обращаются к разным данным в одном файле. В результате этого, сервер возвращает ошибку, которая на самом деле не имеет отношения к запросам пользователей.

Основные причины возникновения ошибки 409:

• Пользователь обращается к данным, имеющим отличное значение или более новую версию. В итоге, сервер выдает ошибку 409, т.к. существует обновленная версия файла, страницы или скрипта.
• Ошибка 409 появилась в результате конфликтующих запросов внутри файлов на сервере. Решить проблему может программист.
• Использование прокси, которое конфликтует с определенными адресами или форматами запрашиваемых данных. Не путайте эту ошибку с ошибкой 407.
• Более распространенная причина – троян или вирус, который блокирует запросы к определенным сайтам или подгружает файл, который имеет конфликт с конфигурацией браузера.

Ошибка 409 Conflicting Request в большинстве случае решается системным администратором или программистом, если это не касается заражения компьютера вирусом или трояном. Как проверить и какой программой расскажем ниже.

Как исправить ошибку 409 (Conflicting Request – Конфликт запросов)?

На некоторых сайтах приведен целый список шагов для устранения ошибки 409. Вот только проблема в том, что это не имеет смысла, т.к. эта ошибка касается программистов или разработчиков сайта / приложения. Конечный пользователь не сможет исправить ошибку 409, если только это не касается вируса или трояна.

1. Чистим от вируса или трояна, чтобы убрать ошибку 409

Определить вирус/троян у вас или нет просто – установите программу Cureit от Dr.Web и просканируйте систему этой программой. Она бесплатная и не требует установки. Скачиваем только с официального сайта. В программе отмечаем все пункты для проверки и шагаем спать/на работу, т.к. сама проверка займет длительное время. На скриншоте ниже вы можете рассмотреть, как и что отмечать в программе. Свой антивирус лучше отключить перед проверкой.

Можно также использовать бесплатную утилиту от Касперского, но она довольно сложная и нужно понимать, какие скрипты вводить в консоль. Остальные программы – платные, поэтому не пишу о них. Кстати, не рекомендую скачивать бесплатные ключи, т.к. такие генераторы могут с собой принести тот самый вирус или троян. Не пожалейте 30$ в год за нормальную защиту.

1. Исправляем ошибку 409 в конкретном браузере

В случае, если ошибка 409 Conflicting Request появляется буквально на каждом сайте, чтобы вы ни нажимали – это точно троян или вирус. Причем это должно происходить в любом браузере. Если нет – можете сразу удалить и заново установить браузер. Возможно произошел сбой конфигурации браузера.

Заранее нужно сохранить закладки, т.к. можно потерять все нажитое непосильным трудом. Делается это просто. На скриншоте выше вы видите пример сохранения настроек в браузере Mozilla. Аналогично делается и в остальных браузерах.

1. Ошибка 409 в результате правок на сайте

Если вы являетесь администратором сайта или программистом… Вы знаете, что такое бэкап и как им пользоваться. Если не знаете – спросите в комментариях. Что с ним делать? Думаю, ответ знаете сами.

Последнее слово про ошибку

Ошибка 409 HTTP Conflicting Request редко относится к пользователю, если только это не вирус или троян. Почти 80% случаев с этой ошибкой касается разработчиков, поэтому разбираться в этом нужно точно не обычному пользователю. Все советы про чистку реестра и прочее – не актуальны. Это не относится к этой ошибке.

Если уж сильно хочется – установите программу CCleaner и пройдитесь по реестру с помощью этой программы. Во всяком случае это безопаснее, чем делать что-то лично ручками. Манипуляции с компьютером в случае с ошибкой 409 делать не стоит.

When you attempt to view a website, you may see an error message that prevents you from accessing the page. If the server notices a conflict between the HTTP request and the resource, it will display a “409 Conflict” error.

Although this scenario can be frustrating, you can easily fix the 409 error. On the client side, you can fix typos in the requested URL, clear your browser cache, and uninstall browser extensions. Alternatively, you can solve this conflict as a website administrator by uninstalling core software and plugins or reviewing your server configuration.

In this post, we’ll give you an overview of the 409 error and its causes. Then, we’ll show you how to check your website for this issue and fix it if necessary. Let’s get started!

Check Out Our Video Guide to Fixing the “409 Conflict” Error

What Is the “409 Conflict” Error?

After making an HTTP request (such as loading a page), you may see an error message informing you that the request couldn’t be completed. In most cases, your browser will tell you what went wrong.

For example, a 400 Bad Request error will occur after a client-side error, like incorrect request syntax, corrupted browser cache, or large file sizes:

However, there are many other HTTP status codes. They belong to five different classes:

• 100s: Informational status codes that indicate continuing requests.
• 200s: Success codes for well-functioning requests.
• 300s: Redirection messages explaining a redirect to another resource.
• 400s: Error codes for client-side problems.
• 500s: Error codes for server-side issues.

If you see a “409 Conflict” error, this is a 400 HTTP status code. In short, the request wasn’t completed because of a conflict with the resource’s current state.

Although this issue might seem complicated, you can usually resolve the conflict and try the request again. Fortunately, unlike server-side errors, the “409 Conflict” error code has some simple solutions.

Don’t worry- fixing the 409 error is easier than it may seem! 🚀 Keep reading to see exactly how to get it sorted… 💪Click to Tweet

What Causes the “409 Conflict” Error?

As its name suggests, the “409 Conflict” error results from some conflict in the HTTP request. It may happen because the requested resource is not in its expected state. Alternatively, the request itself could create a conflict if completed.

A 409 error usually occurs in response to a PUT request. This request updates the target resource. You can use a PUT request to make a new resource or replace an existing one.

However, if there are conflicting values in the PUT payload, they can cause a 409 error. For example, if you mistype certain fields, the server can notice these inconsistencies and reject the request.

You might also see a 409 response if you try to upload a file to your site that’s older than the existing one. Doing this will create a version control conflict that can result in a 409 error.

How To Locate the “409 Conflict” Error

To identify any 409 errors on your website, you can evaluate your HTTP requests and start troubleshooting them. This process will depend on the web hosting company for your site.

With a Kinsta hosting plan, you can manage your site logs in the MyKinsta dashboard. First, log in to your account and select the Sites tab. Then, choose the website you want to evaluate:

This will open a page with basic information about your website. On the left-hand side, click on the Logs option:

After opening the Log viewer, you can see a record of specific errors on your website. If you don’t see a 409 error here, switch to access.log, which contains all of the requests processed by DevKinsta:

Here is the basic information you’ll see in each request:

• Date and time
• Request (method and URI)
• HTTP error code or “200 OK” for successful requests
• Bytes sent
• HTTP referer
• User-agent
• HTTP X Forwarded for

You can look through the list of server requests to find any 409 HTTP status codes. Be sure to look for PUT requests since these can also contribute to conflict errors.

If needed, you can use the search bar to filter your results. Once you locate a “409 Conflict” error, you can proceed with the following solutions.

How To Fix the “409 Conflict” Error (5 Methods)

Even after you experience a 409 error, there are a few ways to resolve it. If you’re unsure what’s causing the issue, you may have to try a combination of different methods. Here are five of the most common fixes!

1. Check the Requested URL

As we mentioned earlier, the “409 Conflict” error can arise from incorrect information in a PUT request. When updating a resource, you’ll want to make sure that you entered its destination correctly.

Before you try more complex solutions, it’s a good idea to review the requested URL. If you manually entered this information, you may have accidentally made a typo that caused an error in the request.

If you made a mistake in this data, you can correct it and try the request again. Sometimes, this will enable you to continue with the request without causing a 409 error.

You can also try simply refreshing the page. Sometimes, old errors can disappear given enough time. Plus, the website owner could have already resolved the issue.

2. Clear Your Browser Cache

When you first view a website, your browser stores that page’s data in a cache. This way, you can easily reaccess those resources. Once you visit the site a second time, your browser will pull the cached data instead of requesting the resources from the server.

After you’ve recently fixed an error in your request, like a mistyped URL, you may still see the 409 error. Although the issue could already be resolved, the error message might still display because of your browser cache. In this case, you can clear your cache to remove the HTTP status code.

The method you use to do this will depend on your browser type. For Google Chrome users, you can start by clicking the three-dot icon in the top-right corner of the page. Then select More Tools > Clear Browsing Data:

In the new pop-up, select Cached images and files. If needed, you can also clear your browsing history, cookies, and other site data. Then, click on Clear data:

Although this will clear most of your cache, your browser will likely keep additional data that most users don’t want to be deleted. However, if you want to remove your full cache, navigate to the Advanced tab:

Here, you can select the data you want to delete from your cache. You can choose from these options:

• Browsing history
• Download history
• Cookies and other site data
• Cached images and files
• Passwords and other sign-in data
• Autofill form data
• Site settings
• Hosted app data

Once you specify the information to remove, click on Clear data. Now you can try the request again to see if the 409 error has been resolved!

3. Roll Back Recent Updates

Sometimes, HTTP error codes can be caused by conflicting software. To troubleshoot a “409 Conflict” error, consider downgrading your WordPress website. This downgrade can help you evaluate whether the core software conflicted with other tools on your site.

However, you’ll need to back up your website before starting this process. If not, you risk losing important changes you made with this new software update. After troubleshooting the issue, you can quickly restore your site to its former state.

Since Kinsta performs daily automatic backups, you can downgrade WordPress by restoring a previous backup. To do this, click on the Backups tab in your MyKinsta dashboard:

Then, select the backup you want to restore. Click on Restore to and choose whether to implement these changes in your staging environment or live site:

Finally, confirm the restoration by entering the given text:

If you updated your website long ago, you’ll likely need to use another method of downgrading your site. Since Kinsta only saves your daily backups for 14 days, you may not be able to restore an older version.

As an alternative, you can install the WP Downgrade plugin. This tool will enable you to easily reinstall an older version of WordPress:

First, install and activate the plugin. Then go to Settings > WP Downgrade:

Enter the exact number for the previous WordPress version to downgrade your software. When you’re finished, save your changes.

You may want to consider rolling back your computer update as well. For Windows users, you can do this in the update history settings. You can also downgrade a Mac computer by reverting to a Time Machine backup.

4. Uninstall Plugins and Extensions

If you don’t want to downgrade your website completely, you can deactivate your plugins and third-party tools. By removing this software, you’ll likely eliminate any conflicts.

To deactivate your plugins, go to the Plugins page on your WordPress dashboard. Then, select all of your plugins:

Click on the Bulk actions menu and select the Deactivate option. To finalize these changes, hit Apply:

Now you can try the request to see if you receive the 409 error. If the request is successful, you’ll know there was a conflict with one of your plugins.

To identify which plugin is causing the issue, activate each plugin one at a time. After each activation, check to see if the error happens again.

Once you locate the problematic plugin, you can delete it. If it performs a necessary task on your website, consider browsing the WordPress Plugin Directory for an alternative. Usually, you can find a different tool with similar functionality.

Alternatively, there could be an issue on the client-side of the request. To solve a 409 error, you can disable your browser extensions. On Chrome, go to More Tools > Extensions:

This will open a list of your enabled extensions. To disable them, make sure the switch next to each one is turned off:

You can also delete the extensions completely. This should eliminate any software conflicts. However, you should only do this with unnecessary tools.

5. Review Your Server Configuration

As a last resort, you can check your server configuration for errors. In MyKinsta, you can use the built-in Application Performance Monitoring (APM). With this APM tool, you can identify any long external requests, unoptimized plugin code, and slow database queries:

To open the Kinsta APM, sign in to MyKinsta. Next, head to Sites > Kinsta APM:

Then, you’ll have to enable performance monitoring for a certain period. At the top of the page, click on Enable:

In the pop-up window, select the amount of time you want Kinsta to evaluate. You can enable a monitoring time window between 2 hours and 24 hours:

After you enable performance monitoring, you can use your results to troubleshoot the 409 error. You’ll be able to view all your requests and analyze your server’s response time:

Alternatively, you can use the Query Monitor plugin. This free tool enables you to see the performance level of your database queries, scripts, hooks and actions, block editor blocks, and more:

First, install and activate Query Monitor. Then, click on the new tab at the top of your WordPress dashboard:

Here, you can view reports for your site’s queries, requests, scripts, and other data. Under HTTP API Calls, you can see a list of any request errors:

With either of these tools, you can easily find 409 errors and discover the root cause of the issue. Then you don’t have to waste time troubleshooting other areas of your website.

There are several options to fix this error- and they’re all covered in this helpful guide 🚀Click to Tweet

Summary

When a conflict occurs during a request, you’ll likely see a 409 error. In this case, the server can’t send the relevant information because of a problem with the state of the requested resource. After identifying the conflicting requested values, you can try the request again.

To review, here’s how you can fix the “409 Conflict” error in WordPress:

1. Check the requested URL.
2. Clear your browser cache.
3. Roll back recent updates.
4. Uninstall plugins and extensions.
5. Review your server configuration.

With Kinsta web hosting, we provide all the tools you need to troubleshoot performance errors as soon as they occur. Using our APM, you can review your external requests and fix conflicts to keep your website functioning properly!