Can't get mirroring working for all DBs?

I'm getting the following errors when trying to set up mirroring for a DB.
[PRINCIPAL]
Date 3/2/2007 2:52:06 PM
Log SQL Server (Current - 3/5/2007 8:44:00 AM)
Source spid99
Message
Communications to the remote server instance 'TCP://SQL2:5022' failed before
database mirroring was fully started. The ALTER DATABASE command failed.
Retry the command when the remote database is started.
Date 3/2/2007 2:52:06 PM
Log SQL Server (Current - 3/5/2007 8:44:00 AM)
Source spid99
Message
Error: 1413, Severity: 16, State: 1.
Date 3/2/2007 2:52:06 PM
Log SQL Server (Current - 3/5/2007 8:44:00 AM)
Source spid37s
Message
The mirroring connection to "TCP://SQL2:5022" has timed out for database
"DB1" after 10 seconds without a response. Check the service and network
connections.
Date 3/2/2007 2:52:06 PM
Log SQL Server (Current - 3/5/2007 8:44:00 AM)
Source spid37s
Message
Error: 1479, Severity: 16, State: 1.
[MIRROR]
Date 3/2/2007 2:52:49 PM
Log SQL Server (Current - 3/5/2007 8:46:00 AM)
Source spid35s
Message
The mirroring connection to "TCP://SQL1:5022" has timed out for database
"DB1" after 5 seconds without a response. Check the service and network
connections.
Date 3/2/2007 2:52:49 PM
Log SQL Server (Current - 3/5/2007 8:46:00 AM)
Source spid35s
Message
Error: 1479, Severity: 16, State: 1.
This only occurs for this particular DB. I have mirroring running
successfully for 4 other DBs. The only difference I can see is that the
problematic DB is significantly larger than the other mirrored DBs... it's
~70GB.
I'm running SQL 2005 Enterprise x64 for both principal and mirror SQL
instances.
Please help...interesting. cant say I've seen this before but trying running consistancy
check DBCC CHECKDB (refer to BOL) perhaps a corruption in the db is causing
the timeout.
M.
"slin" <slin@.discussions.microsoft.com> wrote in message
news:E52523C6-0B5C-4507-B6FA-9439EFD1C02E@.microsoft.com...
> I'm getting the following errors when trying to set up mirroring for a DB.
> [PRINCIPAL]
> Date 3/2/2007 2:52:06 PM
> Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> Source spid99
> Message
> Communications to the remote server instance 'TCP://SQL2:5022' failed
> before
> database mirroring was fully started. The ALTER DATABASE command failed.
> Retry the command when the remote database is started.
> Date 3/2/2007 2:52:06 PM
> Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> Source spid99
> Message
> Error: 1413, Severity: 16, State: 1.
> Date 3/2/2007 2:52:06 PM
> Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> Source spid37s
> Message
> The mirroring connection to "TCP://SQL2:5022" has timed out for database
> "DB1" after 10 seconds without a response. Check the service and network
> connections.
> Date 3/2/2007 2:52:06 PM
> Log SQL Server (Current - 3/5/2007 8:44:00 AM)
> Source spid37s
> Message
> Error: 1479, Severity: 16, State: 1.
>
> [MIRROR]
> Date 3/2/2007 2:52:49 PM
> Log SQL Server (Current - 3/5/2007 8:46:00 AM)
> Source spid35s
> Message
> The mirroring connection to "TCP://SQL1:5022" has timed out for database
> "DB1" after 5 seconds without a response. Check the service and network
> connections.
>
> Date 3/2/2007 2:52:49 PM
> Log SQL Server (Current - 3/5/2007 8:46:00 AM)
> Source spid35s
> Message
> Error: 1479, Severity: 16, State: 1.
>
> This only occurs for this particular DB. I have mirroring running
> successfully for 4 other DBs. The only difference I can see is that the
> problematic DB is significantly larger than the other mirrored DBs... it's
> ~70GB.
> I'm running SQL 2005 Enterprise x64 for both principal and mirror SQL
> instances.
> Please help...|||Already did a DBCC CHECKDB... No errors. I'm using Profiler to see if it'll
show me what's failing, but not having any luck so far...
-S
"Mark Broadbent" wrote:

> interesting. cant say I've seen this before but trying running consistancy
> check DBCC CHECKDB (refer to BOL) perhaps a corruption in the db is causin
g
> the timeout.
> M.
>
> "slin" <slin@.discussions.microsoft.com> wrote in message
> news:E52523C6-0B5C-4507-B6FA-9439EFD1C02E@.microsoft.com...
>
>|||Well... I finally got it working. It seemed like the large physical size of
the transaction log file was causing the problem. The log file was 200GB,
but it was only 1% used. I shrunk the log file size back down to 1GB and di
d
the whole restore/backup process and mirroring started right up.
"slin" wrote:
[vbcol=seagreen]
> Already did a DBCC CHECKDB... No errors. I'm using Profiler to see if it'
ll
> show me what's failing, but not having any luck so far...
> -S
> "Mark Broadbent" wrote:
>