Hi Pandiya,

It looks like this error isn’t related to your screen or module, but rather to the database environment.

The message: “The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'” means that SQL Server’s tempdb transaction log ran out of space while your publish operation was running. This usually happens when there’s a long-running or uncommitted transaction preventing the log from being cleared.

When publishing from OutSystems Service Studio, several database operations are triggered (like metadata updates and schema changes), and these can temporarily put pressure on tempdb.

Possible causes

• A long-running or stuck transaction

• tempdb log file size is too small

• Autogrowth settings are insufficient or disabled

• Disk space is low

• Another process is heavily using tempdb

Things you can try

1. Restart SQL Server (quickest fix in dev environments)This recreates tempdb and clears the log.

2. Check tempdb usageYou can run: DBCC SQLPERF(LOGSPACE);

3. Increase tempdb log sizeIn SQL Server Management Studio:

• Go to tempdb properties → Files

• Increase initial size

• Enable/adjust autogrowth

4. Look for active transactions

DBCC OPENTRAN;

If needed, you may have to terminate a blocking session.

5. Verify disk spaceEnsure the drive hosting tempdb isn’t full.

If you're using OutSystems Cloud

Since direct DB access isn’t available:

• Try restarting the environment (if you have permission)

• Otherwise, reach out to OutSystems support

Given that your module only has one screen, this is very unlikely to be caused by your application itself. It’s almost certainly an environment or database configuration issue.

After resolving the tempdb space problem, try publishing again, it should go through normally.

Regards,

Janakiraman JR

Hi @Pandiya rajan ,

Try the below forge component to evaluate your environment space utlization and do the clean up to free up some space.

https://www.outsystems.com/forge/component-overview/423/dbcleaner-o11

Regards,

Manish Jawla 

Hi @Pandiya rajan 

Adding one point to the suggestions above: Please check the complete error details in Service Center → Monitoring → Errors around the exact time the publish failed. Since the error specifically mentions ACTIVE_TRANSACTION, simply freeing database space or increasing the tempdb log may address the immediate symptom, but it would also be important to identify what transaction was active when the failure occurred.
If the problem is reproducible, try publishing again and note the exact timestamp. This will make it easier for your DBA or OutSystems Support to correlate the OutSystems error with the corresponding database activity.