Article ID: 127005, created on Sep 25, 2015, last review on Sep 25, 2015

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5


Drop database user task failed with the error:

Provisioning request failed. IDispatch error #3092 [<response><errorContext description="Object 'xxxxx' does not exist or is not a valid object for this operation." code="0x80040e14" executeSeqNo="2"><errorSource namespace="SQL Provider" procedure="ExecSQL"/></errorContext></response>]


The drop database user task was initiated by deprovisioning of APS application instance.

The issue caused sometimes because APS application creates database schema by itself, on uninstallation configuration script does nothing, issue can be caused, for example, by temporary objects.


  1. Cancel the task 'Drop database user xxx', this allows the next task 'Drop database xxx' to process.

  2. After successfull deletion of the database manually create database with the same name in MSSQL server (for example using Microsoft SQL Management Studio utility) and re-ran the task 'Drop database user xxx'.

  3. Delete manually created database

Search Words

drop database user *

etFileFolderFunc' does not exist or is not a valid object for this operation.


Provisioning request failed. IDispatch error #3092

is not a valid object for this operation

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF