web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / The transaction log fo...
Small and medium business | Business Central, N...
Suggested Answer

The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'

(7) ShareShare
ReportReport
Posted on by Aman Kakkar 3,502 Super User 2026 Season 1
Hi Experts,
 
I am encountering the below issue while publishing my extension -
 
The request for path /v2.0/DevEnv/dev/apps?tenant=ec0959f8-3171-48d7-XXXXXXXXXXX&SchemaUpdateMode=synchronize&DependencyPublishingOption=default failed with code UnprocessableEntity.
 
Reason: Publishing failed due to 'The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION' and the holdup lsn is (495:11416:88).'.
 
The original extensions have been restored.
 
What could be the possible reasons for this error?
 
Categories:
Dynamics 365 Business Central
Dynamics 365 Business Central migration
Microsoft Dynamics NAV
I have the same question (0)
  • Abdel DAHMANI Profile Picture
    Abdel DAHMANI 84 on at
    indicates that the SQL Server tempdb (temporary database used by Business Central / AL extension publishing) has run out of space in its transaction log while trying to publish or synchronize your extension schema.
  • Suggested answer
    YUN ZHU Profile Picture
    YUN ZHU 100,974 Super User 2026 Season 1 on at
    Hi, It appears to be a problem with the local database. Hopefully, the following information will give you some hints.
     
    Thanks
    ZHU
  • Suggested answer
    OussamaSabbouh Profile Picture
    OussamaSabbouh 16,074 Super User 2026 Season 1 on at
    Hello,
     
    This error simply means SQL tempdb ran out of log space during schema sync while publishing your extension. It isn’t caused by your AL code.
    Why it happens
    tempdb log too small or cannot grow
    Disk is full
    Another long SQL transaction is blocking log cleanup
    Your schema update is large and fills the log
    Fix
    SaaS: try again later; if it repeats, open a Microsoft support ticket.
    On-prem: increase tempdb log size, enable autogrowth, free disk space, or stop long-running SQL transactions.
     
    Regards,
    Oussama Sabbouh

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,086 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,290 Super User 2026 Season 1

#3
AndrewThomas81 Profile Picture

AndrewThomas81 1,218

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans