That error is because of the SQL Server restriction on how wide a table can be - all those fields have exceeded the maximum width allowed. There are a few of ways to get around it depending on your version.

1) If there are some fields that you don't need to copy locally, you can remove your integration users' permissions to those fields, which will shorten the row length. In that message output, it doesn't look like it's very much over (8107  versus the maximum of 8060), so it shouldn't require much trimming.

2) SF_Replicate and SF_Mirror have ColumnSubset options that will bring down alphabetic subsets of the columns, which of course serves to shorten the rows in each piece. That would look like: EXEC SF_Replicate '<your linked server>','Account_ColumnSubsetAM' and EXEC SF_Replicate '<your linked server>','Account_ColumnSubsetNZ' to get all data down.

3) Similar to #1, but without needing to go to Salesforce to change permissions, you can use SF_BulkSOQL to bring down data based on a particular SOQL query you designed that only queries those fields that you need local copies of. You can find documentation here for v22: https://cdn.cdata.com/help/AFH/dbampd/SF_BulkSOQL.html  or in the “DBAmp Stored Procedure Reference” Chapter of your PDF documentation in older versions of DBAmp (<v5.1.9) if your version of DBAmp includes that stored procedure.