Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
the runbook throws this error, it looks like for axdeployuser
i did a small test, on the db, created a test table, with axdeployuser, and then tried dropping it and i got the same error message.
as far as the permissions are concerned, axdeployuser has dbo role
An error occurred when deploying database. Deployment will continue for other databases, but this deployment will be marked as failed.8/20/2018 8:28:02 PM: ############### Error occurred: ###############8/20/2018 8:28:02 PM: PSMessageDetails : Exception : System.Management.Automation.MethodInvocationException: Exception calling "ExecuteSqlText" with "1" argument(s): "The transaction ended in the trigger. The batch has been aborted. ICM:#71360017: Tables cannot be dropped Near statement: BEGIN TRANSACTION; SET TRANSACTION ISOLATION LEVEL SERIALIZABLE; SET XACT_ABORT ON; CREATE TABLE [ax].[tmp_ms_xx_RETAILTRANSACTIONTAXTRANSGTE] ( [CHANNEL] BIGINT ... " ---> System.Exception: The transaction ended in the trigger. The batch has been aborted. ICM:#71360017: Tables cannot be dropped Near statement: BEGIN TRANSACTION;
this probably need more information. What environment we are talking about? DEV, SBX? Did you do somethink with database before applying binary package? Did you install it from machine or thru LCS? Is this only error in logs?
Thank you Marek, this was SBX, i found the root cause , there was a database level trigger, that stopped dropping of tables for the axdeploy user , am not sure, how this was created but may be during one of the refresh activities the MS engineer created it ,and left it out there, thats my best guess right now.
dropping this trigger, all went fine.
/****** Object: DdlTrigger [PreventDropTable_Trg1] Script Date: 8/22/2018 9:12:53 PM ******/
SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
CREATE TRIGGER [PreventDropTable_Trg1]
DECLARE @USER VARCHAR(256)
SELECT @USER = current_user
IF ( @USER = 'axdeployuser' or @USER = 'axdeployextuser')
PRINT 'ICM:#71360017: Tables cannot be dropped'
DISABLE TRIGGER [PreventDropTable_Trg1] ON DATABASE
Business Applications communities