October 2, 2009 at 1:23 pm
I just discovered I'm missing SQL2005 folder and other stuff on a clustered system that is already in production. One node only has a Resource folder under C:\Program Files\Microsoft SQL Server\90\Tools\Binn. The second node has the VSShell folder but doesn't have SqlWb.exe in the IDE folder. Neither of the physical nodes have a Bin folder. Basically can only administer it from afar. I found this out troubleshooting a SSIS. I thought maybe since the package was written on a 32 bit... so I started Visual Studio on the 64 bit cluster and Integration Services Project is not an option when selecting New/Project. So SSIS is fouled up as well as SQL Server.
SQL Server is Standard Edition (64-bit) 9.00.4035 SP3. I thought I'd try and reapply SP3. But doesn't SQL Server stop you, saying "nothing to update" or something to that effect? If I can reapply SP3, how would you suggest I go about it? Apply to the virtual machine? Apply to each node (2 nodes). SSIS is not cluster aware so I would have to apply SP3 to each node for that. Should I reapply SP3 to each physical node? Will SQL Server allow me to do it? Any better ideas?
By the way, the database works just fine. Looks like SSIS and Administration stuff is what's fouled up.
Thanks all for your help.
October 2, 2009 at 1:38 pm
When installing you have the option of installing the client tools and SSIS, it looks like this wasn't installed, if not you need to install, these are not clustered, so you will need to do the install on both nodes, one at a time and then run SP 3 on each node and see if it wants to update the tools you just installed.
Andrew
October 2, 2009 at 1:54 pm
So it sounds like Client Tools are not cluster aware and got missed when SQL Server was installed on the virtual server. Excellent! Its always better when there's a good reason for something not working properly.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply