Error Id 5019 Cluster
if you don’t see your drive in SQL management studio (console), you should know that you need to add the new physical disk as dependency to the SQL service. When you get this error message upon adding the disk as dependency, this blog solution is for you. The error message means you have to make SQL service offline and add the dependency. Follow the steps below to make that happen: Open the Cluster Administrator in Windows Administrative Tools. Locate the group that contains the applicable SQL Server resource that you would like to make dependent. If the resource for the disk is already in this group, go to step 4. Otherwise, locate the group that contains the disk. If that group and the group that contains SQL Server are not owned by the same node, move the group containing the resource for the disk to the node that owns the SQL Server group. Bring the the SQL Server resource offline. Select the SQL Server resource, open the Properties dialog box, and use the Dependencies tab to add the disk to the set of SQL Server dependencies. Keywords: An Error occurred attempting to add ‘drive’ as dependency of ‘SQL Server’. The operation could not be completed because the cluster resource is online. Error ID: 5019 (0000139b)
Share this:TumblrRedditPinterestMoreEmailGoogleFacebookPrintTwitterLinkedInPocketLike this:Like Loading... Related This entry was posted in Uncategorized. Post navigation ← 0x80094801 - the request contains no certificate templateinformation Exchange 2003: Logon Failure after MailboxMove → One comment on “How to add a Physical Disk Resource to the SQL ClusterGroup?” Carlos Garcia says: February 29, 2012 at 2:51 pm This will bring the SQL server down? Do I need to do this OOH? Whats the effect of bringing the sql server resource offline? Reply Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. Search DisplayFusion http://tinyurl.coup Stay up to date: Daily newsletters with brand new articles, scripts, editorials and a Question of the Day help you keep on top of SQL Server. Sign up No thanks Want more great articles like this? Sign up for fresh SQL Server knowledge delivered daily. Sign up Thank this author by sharing: Rate this Join the discussion Add to briefcase Add Dependencies to a SQL Server Resource in Windows 2003 By Ganapathi varma Chekuri, 2015/11/10 In my "last post ReadHere"we have talked about adding the new disk or drive to windows 2003 failover cluster. This time I’m going to talk an issue that I found related with Windows Server 2003 Failover Clustering. After https://anandthearchitect.com/2009/05/08/how-to-add-a-physical-disk-resource-to-the-sql-cluster-group/ we added a physical disk resource to the SQL cluster group as shown in my last post, I have tried to create new database placing log file (.ldf) in new drive J. I don’t see the J drive in Management Studio when browsing file location, we should know that we have to add new physical Disk J as dependency to the SQL service. You will get this error message upon adding the disk as dependency. An Error occurred attempting http://www.sqlservercentral.com/articles/Windows+2003/131584/ to add ‘drive’ as dependency of ‘SQL Server’. The operation could not be completed because the cluster resource is online. Error ID: 5019 (0000139b) In the below screenshot, J drive is used to add as dependency. Add Dependencies to a SQL Server Resource Since the resource for the disk is already in this group, locate the group that contains the disk. If that group and the group that contains SQL Server are not owned by the same node, move the group containing the resource for the disk to the node that owns the SQL Server group. In Windows Server 2003, we have to bring the SQL Cluster service offline to add the dependencies. Right click the SQL Service Resource and take offline. In the below screenshot, the SQL Server service resouce is brought offline. Next we need to select the SQL Server resource. Open thePropertiesdialog box, and use theDependenciestab to add the disk to the set of SQL Server dependencies. In the below screenshot, we have added the resource dependencies. Now bring the SQL Server resource online. We can now test by creating the database files on new drive. In the below screenshot, the log file is created on the J drive for testing purposes. Conclusion You have to take the SQL Service offlineand add the dependency in a Windows Server 2003 cluster for the drive to be available. Ganapathi varma Senior SQL Engineer, MCP https://msdn.microsoft.com/en-us/library/windows/desktop/ms681387(v=vs.85).aspx Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft error id Search Windows Dev Center Windows Dev Center Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design error id 5019 Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Explore What’s new for Windows 10 Intro to Universal Windows Platform Coding challenges Develop for accessibility Build for enterprise Windows Store opportunities Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Why Windows Dashboard Error Handling Error Handling Reference System Error Codes System Error Codes System Error Codes (4000-5999) System Error Codes (4000-5999) System Error Codes (4000-5999) System Error Codes (0-499) System Error Codes (500-999) System Error Codes (1000-1299) System Error Codes (1300-1699) System Error Codes (1700-3999) System Error Codes (4000-5999) System Error Codes (6000-819