Skip to main content

Error - 'Logon failed for table xxx' when multiple tasks are failing following a server migration

Updated over a week ago

This issue will occur when a crystal report used in the task has been configured to use an ODBC connection and the ODBC connection does not exist on the new server.

The resolution is to create a new ODBC connection on the server using the same name as the connection used in the crystal report.

If Access carried out the migration for you, please raise a new case online and reference the title of this article and please include the text of the error message.

Did this answer your question?