Active - Active clustering -Second instance

Trying to install a second named instance of SQL Server 2005 on a
Windows Server 2003 Enterprise two node cluster. I am installing on the
node which the cluster group is currently on. The first named instance I
installed went in like a champ - I have a Cluster Resource group, a SQL
Server(Instance) Group (contains disks, services, ip address, net name, etc)
and a SQL Server (NewInstance) resource group which contains only the shared
disks for the second instance.
Run through setup - everything goes as planned, until the actual
installation is to take place, and then it fails on the 'Remote' server,
because the Scheduled task can't be run - I get this in the Scheduled Task
log file:
"SQL Server Remote Setup .job" (setup.exe) 10/4/2006 3:27:10 PM ** ERROR **
Unable to start task.
The specific error is:
0x80070005: Access is denied.
Try using the Task page Browse button to locate the application.
This seems to indicate that the remote machine cannot access the install
files on the local machine - Has anyone experienced this, and how did you
solve it ?
thanks !
RJ wrote:
> Trying to install a second named instance of SQL Server 2005 on a
> Windows Server 2003 Enterprise two node cluster. I am installing on the
> node which the cluster group is currently on. The first named instance I
> installed went in like a champ - I have a Cluster Resource group, a SQL
> Server(Instance) Group (contains disks, services, ip address, net name, etc)
> and a SQL Server (NewInstance) resource group which contains only the shared
> disks for the second instance.
> Run through setup - everything goes as planned, until the actual
> installation is to take place, and then it fails on the 'Remote' server,
> because the Scheduled task can't be run - I get this in the Scheduled Task
> log file:
> "SQL Server Remote Setup .job" (setup.exe) 10/4/2006 3:27:10 PM ** ERROR **
> Unable to start task.
> The specific error is:
> 0x80070005: Access is denied.
> Try using the Task page Browse button to locate the application.
> This seems to indicate that the remote machine cannot access the install
> files on the local machine - Has anyone experienced this, and how did you
> solve it ?
> thanks !
I am not sure about this specific problem, however from my experience
it is quite easier to first install SQL Server on both machines, then
create the cluster.
Other suggestions while you are in the setup stage:
-Make sure you have different ports and names for your instances if you
want to have them both running on the same server in a failover
scenario.
-If possible, try using the default instance on one of your servers.
Some software can't connect to named instances, like Microsoft CRM.
-Be careful about SSIS, which can be painful in an active-active
cluster. The easier way to go it is to use Filesystem packages, and
store the packages on a cluster resource.
Regards,
lucm
|||Actually, this was mysteriously resolved -
I started looking through the installation log files, and decided I wanted a
'clean' set of files for analysis. I deleted ALL the files in the c:\program
files\Microsoft SQL Server\90\Setup Bootstrap\LOG folder, and proceeded to
try another doomed installation. To my complete amazement, it succeeded.
So - I don't know that I learned anything here... but it got me working.
"lucm@.iqato.com" wrote:

> RJ wrote:
> I am not sure about this specific problem, however from my experience
> it is quite easier to first install SQL Server on both machines, then
> create the cluster.
> Other suggestions while you are in the setup stage:
> -Make sure you have different ports and names for your instances if you
> want to have them both running on the same server in a failover
> scenario.
> -If possible, try using the default instance on one of your servers.
> Some software can't connect to named instances, like Microsoft CRM.
> -Be careful about SSIS, which can be painful in an active-active
> cluster. The easier way to go it is to use Filesystem packages, and
> store the packages on a cluster resource.
> Regards,
> lucm
>
|||Take a look at this KB article see whether it's relevant:
http://support.microsoft.com/?id=910851
Linchi
"RJ" wrote:

> Trying to install a second named instance of SQL Server 2005 on a
> Windows Server 2003 Enterprise two node cluster. I am installing on the
> node which the cluster group is currently on. The first named instance I
> installed went in like a champ - I have a Cluster Resource group, a SQL
> Server(Instance) Group (contains disks, services, ip address, net name, etc)
> and a SQL Server (NewInstance) resource group which contains only the shared
> disks for the second instance.
> Run through setup - everything goes as planned, until the actual
> installation is to take place, and then it fails on the 'Remote' server,
> because the Scheduled task can't be run - I get this in the Scheduled Task
> log file:
> "SQL Server Remote Setup .job" (setup.exe) 10/4/2006 3:27:10 PM ** ERROR **
> Unable to start task.
> The specific error is:
> 0x80070005: Access is denied.
> Try using the Task page Browse button to locate the application.
> This seems to indicate that the remote machine cannot access the install
> files on the local machine - Has anyone experienced this, and how did you
> solve it ?
> thanks !