The transaction log (Servicedesk_log.ldf) for database 'servicedesk' is full
There are two methods to fix this issue.
Method 1
To fix this issue, we have to detach ServiceDesk database, after detaching we can delete the transaction log ( .LDF log)
and attach the ServiceDesk database back.
The important part in this process of attaching database will be removing the log path.The attaching database configuration window will show the path of the log (.LDF log), we have to remove the log path only then we will be able to attach the database.
Following steps are given below, explains in detail about the process of attaching and detaching the database.
# Stop the ServiceDesk Plus service.
# Connect to the SQL database, take a SQL backup and detach service desk database.
# After detaching the database, goto the location where the .LDF log file is located.
Follow the screenshots given below to delete the .LDF log
Eg:-
C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA
Delete the "mike_log.LDF" log file
# Import and add the detached Servicedesk database as per the screenshot is given below.
# In order to complete ServiceDesk database attaching process, remove the .LDF log file path .
The important part in this process of attaching database will be removing the log path.The attaching database configuration window will show the path of the log (.LDF log), we have to remove the log path only then we will be able to attach the database.
# Restart the ServiceDesk Plus service.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Method 2
Shrinking the transaction logs is an alternate method to resolve the issue.We could use the below query to bring down the size of those logs.
==========================
USE Database_Name
GO
DBCC SHRINKFILE (File_Name, Target_Size)
GO
==========================
Database_Name -->> the database on which we are going to execute the query.
File_Name -->> The file which needs to be shrinked.
Target_Size -->> To what size the file needs to be shrinked.(size is mentioned in MB)
Find below few screenshots which can help you understand things in detail:
Screenshot 1: The database JamesWilcox with log file name JamesWilcox_log with initial log size 1744 MB is going to be shrinked to size 1MB .
New to ADSelfService Plus?
Related Articles
Transaction log full
Logs: Depends On Me: com.adventnet.persistence.DataAccessException: [TierComponent] The transaction log for database 'supportcenter' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases ...Failed to start the database
For the error "Failed to start the database", Check what database being used and, execute changeDBServer.bat. For Pgsql, Start PGSQL from the command link, execute StartDB.bat 65432 under C:\Manageengine\ServiceDesk\bin 65432 is the default port ...To Change the application log directory
Environment: Windows Notes: This kb is not recommended. The support file (Community -> Troubleshoot -> Support File) will be generated with log files which are generated using the bat files. The new logs, generated in changed log directory won't be ...How to take console log ?
This article is common for Servicedesk plus MSP and Supportcenter plus applications. To troubleshoot certain UI issues , JS errors , we need console log (output) from the browser. Steps to follow : 1. Login to the application. 2. Right click on the ...How to resolve Connectivity issues with Postgresql Database from our product?
Log Traces Feb 20, 2024 6:40:00 PM [SYSERR] [INFO] : java.sql.SQLException: java.lang.Exception: Exception during getConnection from pool Exception occurred during get connection from datasource Nov 15, 2023 1:29:10 PM [SYSERR] [INFO] : Caused by: ...