79499328

Date: 2025-03-10 23:04:44
Score: 0.5
Natty:
Report link

i know this late response but it could help someone
I don't know the real cause of your problem, but I recommend testing the SQL Server name first using the SQLCMD command in PowerShell. If it connects successfully, then the SQL Server name is correct, and there may be other issues to address:

  1. You might need to create the SSIS catalog (SSISDB) if it doesn't exist

  2. You may need to create the appropriate folder structure within the SSISDB

  3. Check the permissions of the user account you're using to ensure it has sufficient access rights

Reasons:
  • Long answer (-0.5):
  • No code block (0.5):
  • Low reputation (0.5):
Posted by: Yahya mlaouhi