Jeffrey's advice works, I did it sometime ago. By giving the permissions to the domain account it will be able to create the SPN.

Could you execute "select @@version" on both nodes and send the results. As for the msdb error, on which node was the sql instance running when you got it?

Yes! Are there no differences on the nodes?

I agree on the fact...

What kind of cluster do you have? active/pasive or active/active. Are you doing a failover when you before you try to connect to the Integration Services?

Maybe you can try replication.

Do you have more sql 2005 sp 2 server from which you can connect? If the answer is "yes", you can try to create a maintenance plan from one of...

Nicholas, in this case the data is being copied to dev server. I don't think restoring from a network path will be an issue. Sometimes (depending on how the...

Javier, just to be sure, Are you able to connect to Integration Services from the first node?

Perry, thanks for your reply. You are right, I can use the setspn command to create the SPN manually. It is a good way to do it, but to give...

Hi Brian,

After testing giving the "Write Service PrincipalName" permission to a normal domain user (the account that starts the MSSQL service), I found out that it generates the SPN dynamically....

Thanks for your reply. I thought that giving the domain account the "write service principalname" permission will allow that account to create an SPN.

Hi Brian,

We start the SQL service with a domain account. This account does not have the "write service principalname" permission. That is why there is no SPN created in the...

I connected with the SQL account, I think that the SPN is still an issue. I will check it tomorrow first thing in the morning (It is 00:33!). You save...

It works! Thanks! The problem is solved!