Ye olde 0x80041010 error

#31

It works because the client tools installer is not cluster-aware. The SP
installer works the exact same way as the RTM installer and has the same
limitations. So, you ahve to install the SP to each node in order to update
all the client tools. And I agree, it is somewhat frustrating and
definitely not intuitive.

Look for changes in the next edition (SQL 2008). Cluster install and setup
gets a lot better. SQL Clustering install and config starts to look a lot
like the underlying Windows clustering and config.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP

"Offeral" <Offeral (AT) discussions (DOT) microsoft.com> wrote

Quote:

Geoff Hiten was able to fix the issue of this happening in the post below
this one on the forums (I double posted because the first post took 30
minutes to appear and I thought I'd accidentally hit the wrong button).
At
any rate the solution was to install SP2 on the client machine that was
causing the error, not the cluster machines. I felt it was
counterintuitive,
but if it works, I don't care

. Hope this is helpful

O.

"heidendal" wrote:

We have the same problem.

We have recently built a 2 instance dual node cluster SQL 2005.
We have used Windows 2003 EE SP2 and SQL 2005 EE SP2.

I get the same error when someone connects with SSMS and open the object
explorer. We did a clean install towards SP2, so you can rule out that
something went wrong in the update process.

url:http://www.ureader.com/msg/11421083.aspx

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Ye olde 0x80041010 error

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering

Re: Re:Ye olde 0x80041010 error - 02-06-2008 , 08:41 AM