I have this problem every once and a while. If you check the task scheduler log you'll see that the job is failing to start for some funky reason. Wait for the job to show up in the task scheduler. After it fails edit the job, reset the password for the account that the task runs as and manually restart the job.
The install should go fine. You have to move fast however. I've notices that the problem doesn't have anything to do with rights as I'm a domain admin when I'm installing SQL.
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)
--Anything is possible. All it takes is a little research. (Me)
Managed to get SQL installed. It turned out to the be media. After that, SQL install was able to do the "task" on the remote machine.
I now have a new issue, doesn't SQL server management studio supposed to be installed on both nodes? Do I have to install this on the passive node seperately?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.