That's just it - the boss swears he properly removed the share using Failover Clustering, as you're supposed to. That's why he was confused.
Thanks, I figured it was probably in a registry key somewhere. I just don't know if the cluster service needs to be restarted to re-read the registry key, or if just failing to the other node will be enough. On Tue, Jun 23, 2015 at 8:30 AM, Michael B. Smith <[email protected]> wrote: > This is what happens when you remove physical folders, without removing the > shares first... > > This (ancient) KB article tells you what to look for and where to remove the > entries: > > https://support.microsoft.com/en-us/kb/125996 > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Michael Leone > Sent: Tuesday, June 23, 2015 8:23 AM > To: [email protected] > Subject: [NTSysADM] Failover Clustering Event 1588 > > Our main file server is a Win2008 R2 cluster. This morning, I had to move the > resource with most of the shares to the other node (we are rebuilding the > cluster as a multisite Win2012 cluster). Anyway, I failover to the other > node, and get 3 errors. Event ID 1588, resource failed to create file share > "xxx". > > Here's the thing - we have no shares defined with any of those 3 names. We > may have had some in the past, but now, no share exists with that name; I > don't see it in Failover Cluster Manager anywhere, nor in Share and Storage > Management. > > So I'm not sure where Windows is getting the name from. The shares were > removed (apparently), and that's correct, we don't need them anymore. So I > don't want Windows to try and bring them online anymore. > But where can I find out where the definition still exists, if I don't see it > in Failover Cluster or Shares and Storage Management? > >
