It's hanging because your BCP job is running in a different process and creating its own connection to SQL Server.

You are therefore blocking yourself... run sp_who2 and you should see...

If the service starts using services.msc, can't you log on to the cluster node, fire up SSMS, connect to the instance and add the account that way?

Yes, the service needs to be running in order to add the login.

If the service starts successfully from services.msc, then it is definitely an issue with the cluster service being able to connect to SQL Server.

Where did you read that the Local...

Before looking at ports etc, are you sure that the Cluster Services account has the relevant permissions to allow it to connect to SQL Server. These are the lines that...

That error log looks as though SQL Server has started up successfully, but for some reason the Cluster software thinks it hasn't.

The cluster software continually connects to the SQL Instance...

What does the SQL Server error log show when you try to start the instance?

Use the dateadd function instead... that works for both datetime and datetime2, e.g.:-

SELECT @result = DATEADD(minute,20,@toincrease)

The reason that your default constraint works is because you are adding 20 minutes to...

Just put single quotes round dbo.ContentExport, i.e.

EXEC sp_addextendedproperty

@name = N'Caption', @value = 'This column contains email for contacts.',

@level0type = N'Schema', @level0name = dbo,

@level1type = N'Table', @level1name = 'dbo.ContentExport',

@level2type...

There seems to be a parallel thread running which may answer your question.

http://www.sqlservercentral.com/Forums/Topic407783-146-1.aspx

As an example, the old syle outer joins using *= won't work in SQL2005 compatibilty.

Look up "compatibility level" in SQL2005 BOL for the official list.

It won't stop you making changes at the subscriber... but they won't be replicated back to the publisher.

Use Transactional Replication... that's unidirectional

You already have data in the employee table that breaks the FK constraint. i.e. there is an Employee.AddIdOffice that doesn't exist in Address.AddressId

A bilt late now, but... although the actual...