Community
Showing results for 
Search instead for 
Do you mean 
Reply

The SQL Database instance is unavailable. Contact your administrator for assistance.

Astute Commentator
Posts: 78
Country: USA

The SQL Database instance is unavailable. Contact your administrator for assistance.

[ Edited ]

One of my remote users is getting "The SQL Database instance is unavailable. Contact your administrator for assistance." when she tried to initiate a sync via Hamachi. The last time we synced successfully was April 9.  My other 2 users are syncing OK (one is XP the other is Vista).


We are using ACT 2008 Standard with the latest patch installed. She has a Vista machine. I had her shut down and restart but she got the same message.  We tried turning off our Firewalls - same message.  Help?

 

Here is the most recent SQL error log from the user who is unable to sync:


2009-04-28 21:19:08.06 Server Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
Nov 24 2008 13:01:59
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.0 (Build 6001: Service Pack 1)
2009-04-28 21:19:08.09 Server (c) 2005 Microsoft Corporation.
2009-04-28 21:19:08.09 Server All rights reserved.
2009-04-28 21:19:08.09 Server Server process ID is 3144.
2009-04-28 21:19:08.09 Server Authentication mode is MIXED.
2009-04-28 21:19:08.09 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-04-28 21:19:08.09 Server This instance of SQL Server last reported using a process ID of 3344 at 4/28/2009 9:17:35 PM (local) 4/29/2009 2:17:35 AM (UTC). This is an informational message only; no user action is required.
2009-04-28 21:19:08.09 Server Registry startup parameters:
2009-04-28 21:19:08.11 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-04-28 21:19:08.11 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-04-28 21:19:08.11 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-04-28 21:19:08.14 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-04-28 21:19:08.14 Server Detected 2 CPUs. This is an informational message; no user action is required.
2009-04-28 21:19:12.73 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-04-28 21:19:17.32 Server Database mirroring has been enabled on this instance of SQL Server.
2009-04-28 21:19:22.35 spid5s Starting up database 'master'.
2009-04-28 21:19:22.92 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-04-28 21:19:23.23 spid5s SQL Trace ID 1 was started by login "sa".
2009-04-28 21:19:23.23 spid5s Starting up database 'mssqlsystemresource'.
2009-04-28 21:19:23.24 spid5s The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2009-04-28 21:19:25.61 spid5s Server name is 'SONNETHARRIS\ACT7'. This is an informational message only. No user action is required.
2009-04-28 21:19:25.62 spid8s Starting up database 'model'.
2009-04-28 21:19:25.62 spid5s Starting up database 'msdb'.
2009-04-28 21:19:26.02 Server A self-generated certificate was successfully loaded for encryption.
2009-04-28 21:19:26.03 Server Server is listening on [ 'any' <ipv6> 65304].
2009-04-28 21:19:26.03 Server Server is listening on [ 'any' <ipv4> 65304].
2009-04-28 21:19:26.03 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\ACT7 ].
2009-04-28 21:19:26.04 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$ACT7\sql\query ].
2009-04-28 21:19:26.05 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2009-04-28 21:19:26.06 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2009-04-28 21:19:26.06 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-04-28 21:19:26.13 spid8s Clearing tempdb database.
2009-04-28 21:19:26.63 spid8s Starting up database 'tempdb'.
2009-04-28 21:19:26.70 spid5s Recovery is complete. This is an informational message only. No user action is required.
2009-04-28 21:19:26.71 spid11s The Service Broker protocol transport is disabled or not configured.
2009-04-28 21:19:26.71 spid11s The Database Mirroring protocol transport is disabled or not configured.
2009-04-28 21:19:26.71 spid11s Service Broker manager has started.
2009-04-28 21:19:44.13 spid55 Starting up database 'Reverence06'.
2009-04-28 22:05:00.28 spid1s Server resumed execution after being idle 1794 seconds. Reason: timer event.
2009-04-28 22:50:03.80 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-28 23:35:07.35 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 00:20:10.90 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 01:00:26.70 spid1s Server resumed execution after being idle 1503 seconds. Reason: timer event.
2009-04-29 01:45:30.26 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 02:30:33.85 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 03:15:37.39 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 04:00:40.94 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 04:45:44.47 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 05:30:48.12 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 06:15:51.70 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 07:00:55.22 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 07:45:58.76 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 08:31:02.30 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 09:16:05.86 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 10:01:09.44 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 10:46:13.00 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 11:16:50.55 Server Server resumed execution after being idle 925 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2009-04-29 11:16:52.51 spid55 Starting up database 'Reverence06'.
2009-04-29 11:17:18.74 spid22s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 11:17:18.74 spid22s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 11:17:18.74 spid22s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 11:19:20.63 spid51 Starting up database 'ACT10Demo'.
2009-04-29 11:19:21.36 spid51 Starting up database 'ActEmailMessageStore'.
2009-04-29 11:19:21.76 spid51 Starting up database 'Reverence06'.
2009-04-29 11:22:14.95 spid51 Starting up database 'ACT10Demo'.
2009-04-29 11:22:15.58 spid51 Starting up database 'Reverence06'.
2009-04-29 12:13:43.04 spid1s Server resumed execution after being idle 1793 seconds. Reason: timer event.
2009-04-29 12:58:46.66 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 13:26:27.73 Server Server resumed execution after being idle 748 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2009-04-29 13:26:29.15 spid55 Starting up database 'Reverence06'.
2009-04-29 13:27:07.88 spid20s SQL Server has encountered 5 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 13:27:07.88 spid20s SQL Server has encountered 5 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 13:27:07.88 spid20s SQL Server has encountered 5 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 13:27:41.50 spid51 Starting up database 'ACT10Demo'.
2009-04-29 13:27:42.17 spid51 Starting up database 'Reverence06'.
2009-04-29 14:14:26.09 spid1s Server resumed execution after being idle 1793 seconds. Reason: timer event.
2009-04-29 14:38:35.43 Server Server resumed execution after being idle 537 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2009-04-29 14:38:37.11 spid55 Starting up database 'Reverence06'.
2009-04-29 14:39:10.38 spid21s SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 14:39:10.40 spid21s SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 14:39:10.40 spid21s SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 14:39:10.66 spid54 Starting up database 'Reverence06'.
2009-04-29 15:27:18.55 spid1s Server resumed execution after being idle 1793 seconds. Reason: timer event.
2009-04-29 16:12:22.13 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 16:57:25.67 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 17:42:29.21 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 18:27:32.77 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 19:12:36.31 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 19:57:39.86 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 20:42:43.41 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 20:51:47.40 spid51 Starting up database 'ACT10Demo'.
2009-04-29 20:51:48.40 spid51 Starting up database 'Reverence06'.
2009-04-29 20:51:48.78 spid8s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 20:51:48.78 spid8s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 20:51:48.78 spid8s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 21:37:46.07 spid1s Server resumed execution after being idle 1790 seconds. Reason: timer event.
2009-04-29 21:42:35.85 spid51 Starting up database 'ACT10Demo'.
2009-04-29 21:42:36.56 spid51 Starting up database 'Reverence06'.
2009-04-29 21:42:36.99 spid17s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 21:42:36.99 spid17s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 21:42:36.99 spid17s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-29 22:28:44.16 spid1s Server resumed execution after being idle 1792 seconds. Reason: timer event.
2009-04-29 23:13:47.70 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-29 23:58:51.24 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 00:43:54.82 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 01:00:31.69 spid1s Server resumed execution after being idle 84 seconds. Reason: timer event.
2009-04-30 01:45:35.23 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 02:30:38.77 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 03:15:42.33 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 04:00:45.86 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 04:45:49.44 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 05:30:52.98 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 06:15:56.56 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 07:01:00.10 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 07:46:03.69 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 08:31:07.24 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 09:16:10.79 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 10:01:14.37 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-04-30 10:02:23.17 spid55 Starting up database 'Reverence06'.
2009-04-30 10:04:03.34 spid18s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-30 10:04:03.36 spid18s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-04-30 10:04:03.36 spid18s SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.

Message Edited by rab5649 on 05-04-2009 04:56 PM
Astute Commentator
Posts: 78
Country: USA

Re: The SQL Database instance is unavailable. Contact your administrator for assistance.

Anyone?  This error message makes no sense.   Her database is obviously "available" because she uses it every day.  My database is available because the other 2 users are able to sync via Hamachi evey day.
Moderator
Posts: 4,395
Country: USA

Re: The SQL Database instance is unavailable. Contact your administrator for assistance.

Has this user been about to sync through the VPN before?  Try changing the server name to the server's internal IP address in Synchronization Panel > Manage Connection Information.
Astute Commentator
Posts: 78
Country: USA

Re: The SQL Database instance is unavailable. Contact your administrator for assistance.

Yes, she was able to sync a couple of times before she started getting this error.  I will try your suggestion.
Astute Commentator
Posts: 78
Country: USA

Re: The SQL Database instance is unavailable. Contact your administrator for assistance.

How do I find the server's internal IP address?
Moderator
Posts: 4,395
Country: USA

Re: The SQL Database instance is unavailable. Contact your administrator for assistance.

Follow the steps below.

 

- On the server, go to Start and select Run.

- Type in cmd and click Ok.

- In the cmd prompt window, type ipconfig and press enter.

Astute Commentator
Posts: 78
Country: USA

Re: The SQL Database instance is unavailable. Contact your administrator for assistance.

OK, she changed it from the computer name to the IP address but still got the same error.

 

We are using Hamachi to connect.  The network is fine because 2 other remote users are syncing OK.  Her connection shows up "active" (green star next to her highlighted name).  She is able to ping me but when I ping her it times out.  I am running Windows XP, she is Vista.

Moderator
Posts: 4,395
Country: USA

Re: The SQL Database instance is unavailable. Contact your administrator for assistance.

Have her disable the Windows Firewall and UAC.

 

How to Disable User Account Control (UAC) in Windows Vista®

Astute Commentator
Posts: 78
Country: USA

Re: The SQL Database instance is unavailable. Contact your administrator for assistance.

Still getting the same message: "The SQL Database instance is unavailable. Contact your administrator for assistance."

 

It has been almost 2 months since our last successful sync.  I'm considering an uninstall/reinstall on her machine.  Any danger in this?

Copper Super Contributor
Posts: 28
Country: India

Re: The SQL Database instance is unavailable. Contact your administrator for assistance.

Hi,

On the Remote machine, try change the server name to the hamachi ip address of the main (server) machine under Tools-> Synchronization Panel-> Manage connection information, and then try to sync.