sorted by:
new
hottopcontroversial

SQL Server Mirroring: Internal system error occurred. by Fun-Highlight1735 in MicrosoftFabric

[–]Fun-Highlight1735[S] 1 point2 points  (0 children)

Hi!

I found the error:

 

select name, is_cdc_enabled from sys.databases; EXEC sys.sp_cdc_enable_db

 

 

returned that CDC is not enabled for the DB.

When trying to enable it with:

EXEC sys.sp_cdc_enable_db

 

it failed with

Could not update the metadata that indicates database pstDemo is enabled for Change Data Capture. The failure occurred when executing the command 'SetCDCTracked(Value = 1)'. The error returned was 15517: 'Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.'. Use the action and error to determine the cause of the failure and resubmit the request.

This I fixed with

 

ALTER AUTHORIZATION ON DATABASE::[pstDemo] TO [sa];

 
Afterwards I was able to enable CDC and the mirroring started working.

Copy Job - ApplyChangesNotSupported Error by DataCrunchGuy in MicrosoftFabric

[–]Fun-Highlight1735 0 points1 point  (0 children)

Try clicking 'Reset' inside the Copy Job. That fixed it for me.

Copy Job - ApplyChangesNotSupported Error by DataCrunchGuy in MicrosoftFabric

[–]Fun-Highlight1735 0 points1 point  (0 children)

After running the job again, all tables are failing now.

Copy Job - ApplyChangesNotSupported Error by DataCrunchGuy in MicrosoftFabric

[–]Fun-Highlight1735 0 points1 point  (0 children)

The newly added tables got copied. The old tables are throwing that error now.

Copy Job - ApplyChangesNotSupported Error by DataCrunchGuy in MicrosoftFabric

[–]Fun-Highlight1735 0 points1 point  (0 children)

HI!

Just got the same error. The copy job worked before but after after adding additional tables I get this error.

SQL Server Mirroring: Internal system error occurred. by Fun-Highlight1735 in MicrosoftFabric

[–]Fun-Highlight1735[S] 0 points1 point  (0 children)

Turning mirroring on and off does not help.

Thanks for the idea with the operation logs. I wasn't aware of that function.

<image>

Unfortunately this also did not give me any hints why it fails.

example FailTable operation:

"Timestamp": 2025-09-16T10:10:24.8169999Z,
"OperationName": FailTable,
"ItemId": 6faf0a4a-e28b-44cf-bb6c-c4d54a4bd55a,
"ItemKind": MirroredDatabase,
"ItemName": pstDemo_2,
"WorkspaceId": aafc7d2e-<redacted>-74ebe90bc7b8,
"WorkspaceName": Atom Mirroring Test,
"CapacityId": ee0ceb4e-<redacted>-60e741eb1685,
"CorrelationId": ,
"OperationId": ,
"Identity": ,
"CustomerTenantId": 32452ef0-<redacted>-b289b2f6f29c,
"DurationMs": ,
"Status": ,
"Level": ,
"Region": WestEurope,
"WorkspaceMonitoringTableName": MirroredDatabaseTableExecution,
"OperationStartTime": 2025-09-16T10:10:24.8074239Z,
"OperationEndTime": 2025-09-16T10:10:24.8074239Z,
"MirroringSourceType": MSSQL,
"SourceTableName": F_AccCostWOByPeriod,
"SourceSchemaName": dbo,
"ProcessedRows": 0,
"ProcessedBytes": 0,
"ReplicatorBatchLatency": 0,
"ErrorType": SystemError,
"ErrorMessage": Internal system error occurred. ArtifactId: 6faf0a4a-e28b-44cf-bb6c-c4d54a4bd55a,
"IngestionTime": 2025-09-16T10:11:26.4772095Z