Error Id 5079 Cluster Administrator
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error 5079 - Cluster Administrator Want to Advertise Here? Solved Error 5079 - Cluster Administrator Posted on 2008-08-27 MS Server OS Windows Server 2003 1 Verified Solution 5 Comments 2,054 Views Last Modified: 2008-08-29 Greetings: Any idea how to fix this? Appears when I launch cluster administrator. Error ID 5079 (000013d7) An error occured attempting to read properties for the "Symentac mail Security for Microsoft Exchange" resource type. The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node. Windows 2003 Server (without R2) Exchange 2003 Cluster Administrator 5.2 0 Question by:kjanicke Facebook Twitter LinkedIn Google LVL 82 Active today Best Solution byoBdA At first glance, that error looks pretty self-explanatory: on at least one cluster node, "Symantec Mail Security for Microsoft Exchange" isn't installed (correctly). Start here: Installing Symantec Go to Solution 5 Comments LVL 82 Overall: Level 82 Windows Server 2003 52 MS Server OS 24 Message Active today Accepted Solution by:oBdA2008-08-27 At first glance, that error looks pretty self-explanatory: on at least one cluster node, "Symantec Mail Security for Microsoft Exchange" isn't installed (correctly). Start here: Installing Symantec Information Foundation Mail Security 6.x for Microsoft Exchange on an Exchange 2000 Server or an Exchange Server 2003 Cluster http://service1.symantec.com/SUPPORT/ent-gate.nsf/docid/2007357269197798 0 LVL 18 Overall: Level 18 Windows Server 2003 5 MS Server OS 2 Message Author Comment by:kjanicke2008-08-27 Thought we looked at that one already. We reinstalled Symantec on all nodes ... same version ... same license ... and all servers are reporting in properly to the main management station. Odd thing is .. on one of the four clusters, one node reports the error and the other does not. There are some good points in the article that i thought we checked but should review. I've only been working with these exchange servers for a couple of weeks, and every day is something new. Logs and binaries on a limited C drive was the first configuration bite. Thanks. I'll let you know how things go tomorrow. 0 LVL 18 Overall: L
my clustered servers. The primary server is a Windows 2000 serverand the backup is Windows 2003. The three errors state "An erroroccured while attempting to read properties for the 'Generic Script'resource type:The specified node does not support a resource of this type. This maybe due to version inconsistencies or due to the absence of the resourceDLL on this node. Error ID:5079 (000013d7).It does the same thing for the Majority Node Set and the Volume ShadowCopy Service Task. These items are https://www.experts-exchange.com/questions/23682450/Error-5079-Cluster-Administrator.html located under the ClusterConfiguration > Resource Types. Here are the dll's for each file.Generic Script: clusres.dllMajority Node Set: clusres.dllVolume Shadow Copy Service Task: VSSTask.dllI thought this could be an issue due to the differences in Windows 2000cluster and Windows 2003, but this error comes up even on the 2003server. This cluster is used strictly as http://microsoft.public.windows.server.clustering.narkive.com/KYOY6vmE/error-5079-on-cluster-admin-startup a print cluster.Should I worry about these error messages or just not bother with themuntil we upgrade our Windows 2000 system?Thanks,Tina Gerald Aigenbauer 2005-06-24 20:57:13 UTC PermalinkRaw Message hi tina!thatŽs ok during mixed usage of windows 2000 and windows 2003 nodes in onecluster. after updating the last windows 2000 node in the cluster, theerrors will remove.gerald aigenbauer.Post by TinaHello,I am getting an error 5079 when I start Cluster Administrator on eitherof my clustered servers. The primary server is a Windows 2000 serverand the backup is Windows 2003. The three errors state "An erroroccured while attempting to read properties for the 'Generic Script'The specified node does not support a resource of this type. This maybe due to version inconsistencies or due to the absence of the resourceDLL on this node. Error ID:5079 (000013d7).It does the same thing for the Majority Node Set and the Volume ShadowCopy Service Task. These items are located under the ClusterConfiguration > Resource Types. Here are the dll's for each file.Gene
may receive the following error message when starting Cluster Administrator. An error occurred attempting to read properties for the http://windowstechissues.blogspot.com/2008/06/you-may-receive-error-id-5079-000013d7.html 'Double-Take Source Connection' resource type. Error ID: 5079 (000013d7) You can http://www.verycomputer.com/156_c8c94a1809a0320d_1.htm alway safely ignore this error message. However to get rid of it completely just remove the Double Take Resource type from the registry. Open registry editor and take the backup of current registry. Delete the following key: HKEY_LOCAL_MACHINE\Cluster\ResourceTypes\Double-Take Source Connection ------------End Of Document error id ----------------- Tags: Clustering, Windows Server 2003 Published Date: 20080609 Posted by Mukul Agarwal at 12:48 PM Labels: Clustering, Windows Server 2003 1 comment: Mukul Agarwal said... Test Comment June 10, 2008 at 1:22 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Editor Mukul Agarwal India IT Consultant for error id 5079 Windows and Exchange Server environment since 1997 and working as a regular full-time employee now. Still learning new things every day. View my complete profile Registry Problems??? Best Registry Cleaner Custom Search Labels Active Directory (7) Autodiscover (1) CGI (1) Clustering (2) Exchange 2010 (1) Exchange Server (14) Group Policy (1) Hardware (1) Helpdesk (2) IIS (4) Outlook (1) Outlook Anywhere (1) Perl (1) Power Shell (4) PST (1) VB Script (1) Windows Server 2000 (14) Windows Server 2003 (25) Windows Server 2008 (6) Windows Vista (1) Windows XP (18) Website Tracker Blog Archive March 2011 (5) August 2010 (2) July 2010 (1) January 2010 (2) December 2009 (1) November 2009 (1) March 2009 (1) January 2009 (2) September 2008 (1) July 2008 (2) June 2008 (6) May 2008 (7) April 2008 (3) March 2008 (1) December 2007 (1) November 2007 (3) October 2007 (2) September 2007 (3) August 2007 (6) Toner Cartridge / Inkjet Problems Simple template. Powered by Blogger.
trying to install SQL enterprise 2000 on windows 64bit .net 2003 2node server cluster. Installing from node 1, the installation hangs on node 1, while it appears to be a complete install on node 2. Can start SQL service on node 2, but stops right after. Node 1 cannot be restarted or shutdown using the operating system. After a manual hardware reset on node 1, opening the cluster administrator I get this message: An error occured attempting to read properties for the 'Microsoft Search Service Instance' resource type. The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node. Error ID: 5079 (000013d7), Do you want to ignore this error and continue? gathercl.dll is right were it is supposed to be. Version 9.107.5512.0 I need to have SQL server runing on that cluster. No matter how. I'm already 6 weeks behind on the project. Any ideas? Top Error ID: 5079 (000013d7), ms search service on windows 64bit .net enterprise by John Kan » Wed, 29 Jan 2003 00:35:49 Olaf, First of all, you are installing the 64bit version of SQL Server 2000 (codename Liberty) on your Windows 64bit .net 2003 2node server cluster. Correct? If not, then you should obtain this version and re-install. The "error occurred attempting to read properties for the 'Microsoft Search Service Instance' resource type" relates to the MSSearch search engine. Are you planning to use FTS on this cluster? As for "This may be due to version inconsistencies or due to the absence of the resource DLL on this node. Error ID: 5079 (000013d7)", how do you know that this links to gathercl.dll and it's version? Note, you can also post FTS questions to the newsgroup: microsoft.public.sqlserver.fulltext. Regards, John Quote:> trying to install SQL enterprise 2000 on windows > 64bit .net 2003 2node server cluster. > Installing from node 1, the installation hangs on node 1, > while it appears to be a complete install on node 2. Can > start SQL service on node 2, but stops right after. > Node 1 cannot be restarted or shutdown using the > operating system. > After a manual hardware reset on node 1, opening the > cluster administrator I get this message: > An error occured attempting to read properties for > the 'Microsoft Search Service Instance' resource type. > The specified node does not support a resource of this > type. This may be due to version inconsistencies or due > to the absence of the resource DLL on this node. > Error ID: 5079 (000013d7), > Do you want to ignore this error and continue? > gat