How can we help you today? How can we help you today?

Two issues introduced in 6.x release

ISSUE #1

I am getting a lot of CE Database corruption errors that I didn't get in the previous release from multiple instances on our development PolyServe matrix.

6/24/2009 1:45:03 PM:
6/24/2009 1:45:06 PM: Warning 402: Failed to open local data store: The database file may be corrupted. Run the repair utility to check the database file. [Database name=E:\software\Red Gate\SQL Backup\Data\InstnaceName\data.sdf]

The data.sdf files are stored on a shared PolyServe volume with multiple nodes running the service, so that might have something to do with it, but it's a new problem that didn't exist with 5.4.

ISSUE #2

I was getting errors connecting SQL 2000 instances using the PolyServe IA Browser that contains features that the Microsoft SQL browser does not. Switching back to the Microsoft SQL Browser, resolved it. Note this problem only exists for SQL 2000 instances, 2005 instances have no problem SQLBackup 6.x and the PolyServe IA Browser. While you might see that as a PolyServe IA Browser issue (and it partially is), I again point out that 5.4 does not have this problem.

Here is the error I get for ISSUE #2:

SQL error -2147467259: Login timeout expired
SQL error -2147467259: Login timeout expired
SQL error -1: SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
Server : PhysicalHostName\SQL2000InstanceName
Windows authentication
6/23/2009 9:29:46 PM: Failed to connect to SQL Server instance: PhysicalHostName\SQL2000InstanceName

Creating client side aliases for the Physical host to the correct virtual host and port did not resolve it. Changing to Microsoft SQL Browser did.
DonFerguson
0

Comments

2 comments

Sort by
  • Andrew Hodge
    Another PolyServe user, wow...

    I had a similar issue to the one you describe with SQL Backup v5 reporting that it couldnt open the database. This occurred with multiple nodes running the sql backup service at the same time and accessing the same sdf. I had to create scripts to perform the startup / shutdown of the sql backup service during a rehost / failover.

    I didn't think the PolyServe IA was a replacement for the SQL Browser? It just does a NAT type port redirection from one to ip:port to another ip:port. Dont have a test polyserve setup to install SQL Backup v6 onto however so cant really comment.
    Andrew Hodge
    0
  • DonFerguson
    I may need to go the route of generating start/stop scripts for instances, but this problem ceratainly became significant with 6.x and wasn't much of an issue with 5.4. Of course if the data were recorded in the msdb database instead of CE, that problem would completely go away.

    PolyServe does have the option to replace the SQL Browser with the IA Browser, it's under advanced options of Instance Aliasing.
    DonFerguson
    0

Add comment

Please sign in to leave a comment.