Updated on October 9, 2026
Ubyquo does not perform the direct export to Sage
Check the connection path, the Named Pipes protocol and the state of Sage, then export again.
If Ubyquo does not perform the direct export to Sage, check the database connection settings and the state of Sage. This helps you spot problems with the connection path, the protocol used or a pending Sage update.
- 1
Check the server name
Open the connection settings in Ubyquo and check that the Nombre del servidor (Server name) field matches the actual SQL server of the Sage database. Avoid IP paths or incorrect aliases.

- 2
Use Named Pipes
To connect to Sage, Named Pipes is recommended, with a path made up of the server and the instance, for example:
\\servidor\nombre_instanciaUsing TCP/IP with a port can cause errors in the direct export, even when the connection test says the connection is fine.
- 3
With TCP/IP, remove the port
If the protocol is TCP/IP, do not specify a port number in the connection string: if there is one, remove it.
- 4
Check that Sage has no pending update
Sage must start properly and without update warnings. If an update is pending or did not complete properly, the database may be locked, Ubyquo may not be able to access it and the direct export may fail.
- 5
Export again
Check the connection settings in Ubyquo again (server and protocol) and repeat the direct export.
Done! If the settings are correct, Ubyquo will be able to communicate with the Sage database and perform the direct export.
