SQL Server Error Msg 49973 – Cannot remove tempdb remote file to local tempdb filegroup in transition to primary

In this blog post, let’s learn about the error message “49973 – Cannot remove tempdb remote file to local tempdb filegroup in transition to primary.” in Microsoft SQL Server, the reason why it appears and the solution to fix it.

SQL Server Error Message

49973 – Cannot remove tempdb remote file to local tempdb filegroup in transition to primary.

Reason for the Error

The SQL Server error 49973 occurs during the transition of a database to primary, and it indicates that SQL Server is unable to remove a tempdb remote file to the local tempdb filegroup. Here are some of the possible causes of this error:

1. Insufficient disk space: SQL Server may not be able to remove the tempdb remote file to the local tempdb filegroup due to insufficient disk space on the server.
2. Lack of permissions: The SQL Server service account may not have the necessary permissions to remove the tempdb remote file to the local tempdb filegroup.
3. Connectivity issues: There may be connectivity issues between the server where the tempdb remote file is located and the server where the local tempdb filegroup is located.
4. Corruption of the tempdb file: The tempdb remote file or the local tempdb filegroup may be corrupted, preventing SQL Server from completing the transition to primary.

Solution

To fix the SQL Server error 49973 , try one of the below steps.

1. Ensure that there is sufficient disk space on the server where the local tempdb filegroup is located. You can try removing unnecessary files from the server to free up space.
2. Verify the connectivity between the server where the tempdb remote file is located and the server where the local tempdb filegroup is located. Check for any network issues that may be causing the connectivity problems.
3. Check the permissions of the SQL Server service account to ensure that it has the necessary permissions to remove the tempdb remote file to the local tempdb filegroup.
4. Check for any corruption of the tempdb file. You can use DBCC CHECKDB to verify the integrity of the tempdb file and the local tempdb filegroup.
5. Restart the SQL Server service: Sometimes, restarting the SQL Server service can fix the issue. Restarting the service can free up any resources being used by SQL Server and may resolve the issue.
6. Use SQL Server Configuration Manager: Use the SQL Server Configuration Manager to verify the SQL Server service account and that it has the appropriate permissions.
7. Rebuild the system databases: In some cases, rebuilding the system databases can resolve the issue. This should only be done as a last resort after ensuring that you have a recent backup.