500 error when save the Microsoft SQL Resources

When i try to save mssql resource always raise error 500. Test connection is successful. trying to save rest api resource is successful. only this one have errror.
Can you help me?

Hi @sakir.altinmakas, welcome to the Retool community!

To help with the saving error, perhaps try using a unique description, different from the name (e.g., 'Test DB Connection'). It's also worth checking if that database name is already in use within the app."

5 Likes

hi @WidleStudioLLP thanks for answer. i try another name but i cannot success. when i try another type like rest-api i can save resource. i have a problem just with sql server source type

Hi @sakir.altinmakas, thanks for the update. Since other resources work, the issue is likely SQL Server specific. Could you share what version of SQL Server you're using and if you're using the default port (1433)? Also, are there any special characters in your connection details?

5 Likes

@WidleStudioLLP server version Number Microsoft SQL Server 2019 (RTM-CU26) (KB5035123) - 15.0.4365.2 (X64) Mar 29 2024 23:02:47 Copyright (C) 2019 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 (Build 17763: ) (Hypervisor)

only @ and ! characters in password and i can connect to server with Management Studio.

Is there any think i can control?

Hey @sakir.altinmakas

  1. Check Permissions: Ensure that your user account has sufficient permissions to create resources in Retool. For Free or Team plans, users should have global Edit permissions.
  2. Verify Connection String: Double-check your connection settings, including the server address, database name (e.g., retooltestdb), and credentials. Make sure there are no typos or incorrect configurations.
  3. Firewall Settings: If your Microsoft SQL Server is behind a firewall, ensure that Retool can access it. Check if you've allowed the appropriate IP addresses for Retool to connect.
  4. Authentication Issues: Since your password contains only @ and !, verify that you’re using the correct method of authentication (e.g., SQL Server Authentication) and that the password is valid.
  5. Examine Logs: If possible, review the logs for any additional error messages that might give more detail about the source of the error.
  6. Retry Connection Test: After making changes, use the Test Connection button to verify that Retool can indeed connect to the database before attempting to create the resource again.

If the issue persists after these checks, you might want to reach out to Retool support for further assistance.

5 Likes

I would assume this is something related to Retool's backend DB instead of Microsoft SQL.

Can you try restarting your postgres container, wait 2 mins and test again?

I agree, @zelterNN. :+1: If this is still an issue, @sakir.altinmakas, can you try escaping the special characters in your connection details? I've seen that cause an issue in the past.