Failed to initialize local data store: Invalid class string

laurencerooks · June 1, 2007 2:23PM

SQL Backup Professional v5.0 and v5.1 just won't play nice with me. Okay. I have a Windows 2003 Server with Service Pack 2 and a proper installation of the .NET 2.0 Framework. I have successfully installed SQL Backup Professional v5.1. I have successfully launched the application. I can't get a connection to the server due to the following error:

Failed to initialize local data store: Invalid class string

I've done a search for this and come back with nothing. Can someone please help?

Laurence

petey · June 1, 2007 11:54PM

When you run a test backup manually e.g.

EXEC master..sqlbackup '-sql "BACKUP DATABASE model TO DISK = [<AUTO>]"'

does the backup complete successfully? Thanks.

laurencerooks · June 4, 2007 9:04AM

I was able to successfully create a SQL Backup of the model database with the command given. Why am I not able to connect via the GUI console so I can activate the license and manage it?

Laurence

petey · June 4, 2007 10:43PM

The error message 'Failed to initialize local data store: Invalid class string' indicates that the SQL Server Compact Edition (SSCE) files have not been copied/registered on the server. However, the test backup that you created seems to indicate the opposite. If the SSCE files were not available, you would have received a warning similar to the following:

Warning 402: Failed to open local data store: Invalid class string

The backup would have still succeeded, but information regarding the backup would not have been stored in SQL Backups' local database.

Could you pls confirm that the test backup succeeded without any warnings or errors? Thanks.

laurencerooks · June 5, 2007 9:02AM

Petey,

We are using SQL Server 2000 Standard Edition with SP4 on Windows Server 2003 with SP2. We are not using SQL Server Compact Edition. I did not receive any warning or error message during the test backup.

petey · June 5, 2007 9:16AM

What I meant to say was that SQL Backup 5 stores its own data on backups and restores that it performs. It stores this in a SQL Server Compact database. The runtime files for the Compact database is usually installed together with the server components. It is this database that is referred to as the 'local data store' in the error messages. I apologise for not making this clear.

When you register a server in the version 5 GUI, it checks if the SQL Backup extended stored procedure are installed. If so, then then calls the sqbdata extended stored procedure to retrieve data from the 'local data store'. I am assuming that it is at this point that the error message you mentioned should have been raised, if the Compact files have not been property copied/registered.

Perhaps I am making the wrong assumptions about your scenario. Could you provide a screenshot of the error that is happenning in the SQL Backup GUI? You can send it to me via email. Thanks.

petey · June 5, 2007 9:30PM

The cause of the error was because the SQL Server Compact Edition COM interface was not registered. While the files were installed on Laurences' server, they were not registered for some reason. Manually registering the interface allowed the GUI to connect to the server successfully. The file to register is named sqlceoledb30.dll.

Failed to initialize local data store: Invalid class string

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk