It looks correct from the SQL Server side of things. When it comes to Sage... I'm not familiar with Sage, and you would have to inquire in a Sage forum.
Do you have a command-line application that is able to connect to Sage? If so, copy it to the SQL Server machine and run it from xp_cmdshell. That may work - or you may get a better error message.