Sql Backup And FTP

hi there

i've been using SSME for years to connect to databases at my host with no problems.

using SB&FTP i can also connect fine. however when i try and run a backup i get the following error log:


Database scripting failed: An error occured while getting database information. >> System.Data.SqlClient.SqlException: Invalid object name 'sys.databases'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at b.x.i(Stream A_0)


version of SQL Server is 8.00.2055

can you help please?

thanks

dave

thanks mike... but i'm confused:

the version showing for SQL Server is 8.00.2055... is that not sql server 2008? that is also what the hosting company say they are providing.

ok so at last we have migrated our database to sql server 2008.

sadly we are still getting errors with SBF - this time the message was 'an error occured while getting tables information'.

here is the log:


>>> run 01/11/2010 14:08:32 by user

SqlBackupAndFtp 5.2.2.15553 (Free)

SUMMARY:
Database 2qute: Backup - Failure

DETAILED LOG:
01/11/2010 14:08:23 Creating backup of 2qute to C:\temp (using scripting)
01/11/2010 14:08:23 Creating 2qute001.sql
01/11/2010 14:08:23 Scripting database creation
01/11/2010 14:08:25 Scripting users
01/11/2010 14:08:26 Scripting roles
01/11/2010 14:08:26 Scripting users in roles
01/11/2010 14:08:27 Scripting schemas
01/11/2010 14:08:28 Scripting user defiend types
01/11/2010 14:08:29 Scripting table structures
01/11/2010 14:08:32 ERROR: Database scripting failed: An error occured while getting tables information. >> System.ApplicationException: An error occured while getting tables information. ---> System.Data.SqlClient.SqlException: Incorrect syntax near '2'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at b.p.c(String A_0)
--- End of inner exception stack trace ---
at b.p.c(String A_0)
at b.x.a(Stream A_0, List`1& A_1)
01/11/2010 14:08:32 ERROR: Backup of 2qute failed: Job failed
01/11/2010 14:08:32 Cleaning C:\sqlbackup
01/11/2010 14:08:32 ERROR: Job finished (With Errors)


any help much appreciated :)

so basically there's not a fix for this?

shame.... is there likely to be?

i'm sure that there are many other developers like me that are working on shared hosting, and we just don't have the access to the server that others might, and so have to use scripting. if i could get this to go on this database then we'd probably buy the full product, as we have quite a few other databases to support.

anyway: i note that the detail in the error i am receiving is:



and that in the other thread, the error was:



as our database is called 2qute and the error specified a problem near a 2, and the other user's error also involved a number (0100494), i'm wondering if this might be something to do with it?

just an idea....

i do appreciate your work and efforts, and can sympathise. you (appear!) to have a great product and it's a drag i can't harness its power.

this might be a bit cheeky - but can you recommend another solution that might enable me to safeguard our clients' data - which after all is our priority, as we (and they) do feel quite exposed should our hosting provider vanish into the ether.

keep up the good work - thanks for your input - i'll try again soon.... :)

i have already tried this but the best they could suggest was a DTS routine. however as i undertstand it, to save and schedule that requires a proper copy of sql server, which we don't have... SSME only....

i've tried looking for a 3 party solution, ie a company that will do backups as a service, but without success.

oh well, i'll keep my eye on your site and in the future try newer versions to see if they work.

thanks again for your assistance.

fairly likely it's the number at the start then :)

i'll try renaming our database.