SQL 2014 cluster installation on mounting point disks error: Updating permission setting for file

Dear all,
I am attempting to install SQL 2014 fail over cluster under a physical windows 2012 R2 server which have mounting point disks.
At the finish of setup I get the following error message.
Could you please help me on this?
Thanks
The following error has occurred:
Updating permission setting for file 'E:\Sysdata!System Volume Information\.....................................' failed. The file permission setting were supposed to be set to 'D:P(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;OICI;FA;;;CO)(A;OICI;FA;;;S-1-5-80-3880718306-3832830129-1677859214-2598158968-1052248003)'.
Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
For help, click: go.microsoft.com/fwlink
I am using an administrator account which have all security rights (cheched on secpol.msc mmc) needed for installation.

Hi Marco_Ben_IT,
Do not install SQL Server to the root directory of a mount point, setup fails when the root of a mounted volume is chosen for the data file directory, we must always specify
a subdirectory for all files. This has to do with how permissions are granted. If you must put files in the root of the mount point you must manually manage the ACLs/permissions. We need to create a subfolder under the root of the mount point, and install
there.
More related information:
Using Mount Points with SQL Server
http://blogs.msdn.com/b/cindygross/archive/2011/07/05/using-mount-points-with-sql-server.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

SQL 2014 cluster shared volume

Hi,
I have testing SQL 2014 cluster in my lab to see how it's performing. 2xserver 2012r2 (virtual machines). There are some weird issues that are putting me in dust.
1. If I try to backup/restore database, I cannot select data path from gui. (I cannot "browse")
2. I cannot connect applications to databases (sqlclustername\instance) - permissions denied on cluster shared volume.
Can you please give me a hand on this?
Thank you.

Please check Symantec Backup Exec 2014 it works with CSV.
remove the CSV from the failover cluster manager and then try to point the tool and see if it is able to see the volumes without CSV.
http://www.symantec.com/business/support/index?page=content&id=TECH205833
Hope this helps.
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

SQL 2014 Cluster to Cluster protection

Hi,
I got 2 physical servers in Cluster with SQL 2014 on source site and same environment of two physical servers on target site. I want target cluster to protect target source. The site are remote from each other. How can I do replication and FO & FB? Can
always on protect source cluster to target cluster? can it monitor and do FO to remote cluster. Both cluster on the same domain.
Thanks
Erez

Please check Symantec Backup Exec 2014 it works with CSV.
remove the CSV from the failover cluster manager and then try to point the tool and see if it is able to see the volumes without CSV.
http://www.symantec.com/business/support/index?page=content&id=TECH205833
Hope this helps.
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach

The dreaded: The network address is invalid error - SQL 2014 Cluster on Server 2012 R2

Trying to setup an SQL 2014 Failover cluster on Windows Server 2012 R2 (two nodes). Every time I get to the assign a SQL server Network Name piece of the setup I get the following error message:
The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'
This happens whether I use the Advanced cluster installation procedures or the normal installation. I have tried the following based on anything I can find on the web:
1) Removed the clustered MTDTC role.
2) Deleted the NIC Team (4 1GB NICs). Deleted all but 1 NIC from the server device manager.
3) Shutdown the second node.
4) Lanman Server registry change posted someplace on this forum that does not stick on reboot
None of the above, separately or in combination, has worked to allow SQL 2014 to be installed as a cluster role.
There is no virtual machines added to the cluster. This is not a VMware installation. It is straight Windows 2012 R2 with a two node cluster (setup identically).
Any ideas, suggestions, comments?
Thanks,
-Andrew

Hi Alberto and Lydia,
The cluster was verified, there are only warnings related to a lack of redundant network paths as the cluster verification doesn't recognize a team of 4 nics are redundant. I updated AD to include the permissions detailed in the link Lydia provided,
still no go.
I'm not sure how to attach the installation logs to this message forum other than as text in the message, so here you go:
Summary:
Overall summary:
Final result:                  User cancelled
Exit code (Decimal):           -2068380094
Exit facility code:            1207
Exit error code:               1602
Exit message:                  User has cancelled.
Start time:                    2015-03-24 09:55:25
End time:                      2015-03-24 10:01:04
Requested action:              CompleteFailoverCluster
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for ComponentUpdate: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
Cluster properties:
Machine name: SUN-PIE-CS-01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine name: SUN-PIE-CS-02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Data Quality Client                      1033                 Standard
Edition     12.0.2000.8     No         Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine Properties:
Machine name:                  SUN-PIE-CS-01
Machine processor count:       16
OS version:                    Windows Server 2012
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Package properties:
Description:                   Microsoft SQL Server 2014
ProductName:                   SQL Server 2014
Type:                          RTM
Version:                       12
SPLevel:                       0
Installation location:         \\sun-server2\data\Software\Microsoft\SQL 2014\x64\setup\
Installation edition:          Standard
User Input Settings:
ACTION:                        CompleteFailoverCluster
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASLOGDIR:                      Log
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
CONFIGURATIONFILE:
CONFIRMIPDEPENDENCYCHANGE:     false
ENU:                           true
FAILOVERCLUSTERDISKS:          <empty>
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    <empty>
FAILOVERCLUSTERNETWORKNAME:    sun-pie-mt-01
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS:              false
INSTALLSQLDATADIR:             <empty>
INSTANCENAME:                  MSSQLSERVER
QUIET:                         false
QUIETSIMPLE:                   false
SAPWD:                         <empty>
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Full-Text and Semantic Extractions for Search
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - Native
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Integration Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Setup Support Files
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity SDK
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Writer
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Documentation Components
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Browser
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
    Message:
        User has cancelled.
    HResult : 0x84b70642
        FacilityCode : 1207 (4b7)
        ErrorCode : 1602 (0642)
    Stack:
        at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
        at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
        at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)

SQL 2012 Cluster Installation AddNode

Hi All.
I am trying to do a clsuter installation and I get the error below, when I try to add the second node as part of the cluster.
Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$SQL_INSTANCE
Error result: -2061828095
Result facility code: 1307
Result error code: 1
Please review the summary.txt log for further details
Microsoft (R) SQL Server 2012 11.00.3000.00
Copyright (c) Microsoft Corporation. All rights reserved.
(01) 2015-01-28 13:24:49 SQLBrowser: This is a cluster-related scenario. IsCluster = 'True'.
(01) 2015-01-28 13:24:49 SQLBrowser: CalculateStartMode: bIsNamedInstance = 'True', bIsDbmsEngineInstall = 'True', bEngineNetworkProtocolsOn = 'True', bIsAsInstall = 'False',bIsCluster = 'True'.
(01) 2015-01-28 13:24:49 SQLBrowser: CalculateStartMode: Named instance needing SQL Server Browser: setting intended SQL Server Browser StartMode property to 'Automatic'.
(01) 2015-01-28 13:24:49 SQLBrowser: EndMethod Type='SqlBrowserPublicConfig' Method='CalculateStartMode'.
(01) 2015-01-28 13:24:49 SQLBrowser: EndMethod Type='SqlBrowserPublicConfig' Method='Calculate'.
(01) 2015-01-28 13:24:49 SQLEngine: Obtaining FDLauncher service account from active node
(01) 2015-01-28 13:24:49 SQLEngine: Active node is SERVERNAME
(01) 2015-01-28 13:24:49 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine SERVERNAME
(01) 2015-01-28 13:24:49 Slp: Sco: Attempting to open registry subkey System\CurrentControlSet\Services\MSSQLFDLauncher$SQLINSTANCE
(01) 2015-01-28 13:24:49 Slp: Error: Action "Microsoft.SqlServer.Configuration.SetupExtension.FinalCalculateSettingsAction" threw an exception during execution.
(01) 2015-01-28 13:24:50 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$SQLINSTANCE ---> Microsoft.SqlServer.Configuration.Fulltext.FulltextFeatureException: Could not find subkey System\CurrentControlSet\Services\MSSQLFDLauncher$SQLINSTANCE
(01) 2015-01-28 13:24:50 Slp: at Microsoft.SqlServer.Configuration.Fulltext.Util.GetFDLauncherAccountFromRegistry(ServiceContainer Context, SqlRegistryKey keyHKLM)
(01) 2015-01-28 13:24:50 Slp: at Microsoft.SqlServer.Configuration.Fulltext.FulltextConfigurationPublic.Calculate()
This is the detailed log section when I look in the folder of the cluster log.

Hi MrFlinstone,
As discussed in this similar
thread, it seems to be an known issue when adding a second node in a SQL Server failover cluster using option “
Integration Installation with Add Node ”.
To work around this issue, you can use the Advanced/Enterprise installation option to install SQL Server failover cluster.
SQL Server Advanced/Enterprise failover cluster installation consists of the following steps:
• On each node that is a possible owner of the new SQL Server failover cluster, follow the Prepare Failover Cluster setup steps that are listed in the
Prepare section. After running the Prepare Failover Cluster on one node, Setup creates the Configuration.ini file that lists all the settings that you specified. On the additional nodes to be prepared, you can supply the auto-generated Configuration.ini
file from first node as an input to the Setup command line.
• After the nodes are prepared for clustering, run Setup on one of the prepared nodes. This step configures and finishes the failover cluster instance.
Reference:
Create a New SQL Server Failover Cluster (Setup)
Installing a Two-node SQL Server 2008 Cluster - Advanced option
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Need to Increase mount point disk space

Hello,
I do not know whether this is the appropriate forum to post my question.
I need to increase the mount /u01 disk space . I would like to club two mounts and make one File system to a make a bigger one. I do have 2 filesystems mounted on 2 disks as following.
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c1t4d0s0 2012390 9 1952010 1% /u01
/dev/dsk/c1t14d0s0 2012390 9 1952010 1% /u09
Is there any way that I can merge these two into one filesystem to make a 4 GB filesystem of /u01 ?
Thanks

Hi
You have to install a package called Solaris DiskSuite where there is a utility called growfs which can grow your file systems that is it can add more space to your existing file system. Which OS do u have . If you have solaris 7 you have to install it from sun early access CD..If it is already installed , then you have to follow the procedure as given below.
The following example expands a nonmetadevice slice for the /u01 file system. In this example, the existing slice, /dev/dsk/c1t4d0s0, is converted to a metadevice so additional slices can be concatenated.
# metainit -f d1 2 1 c1t4d0s0 1 c1t4d0s1
# umount /u01
(Edit the /etc/vfstab file to change the entry for /u01
to the newly defined metadevice, d1.)
# mount /u01
# growfs -M /u01 /dev/md/rdsk/d1

CC 2014, the installation fails by the fatal error exit number: 7

Hey guys. Since 24 days Im trying to update my Cloud to the CC 2014 but when starting with PS, the installation fails by the fatal error exit number: 7. Whats to do?

Well John, first of all, thank you very much for helping me.
Yesterday I tried something, by deinstalling the Cloud App and PS, but still the same error remained.
What I also don't understand is the term: Reinstalling the product. Is it meant, to deinstall every app, just the Cloud app or only the app where the error occupies?
By Reinstalling I also understand: Uninstall the app and the install it again. Is this correct?
I am surprised anyway. Once everything is fine and then within one day, nothing runs anymore. I read about, using a disc clean app as Clean My Mac 2 can destroy the structure of adobe products some how... but hmmm... this sounds very strange.

SQL 2012 cluster installation fails with an IP address error

I am building an eight node cluster and have successfully installed two SQL instances on it. Now, I cannot install any additional instances because of the following error:
The resource with identifier 'Type='IP Address' NetworkName='Cluster Network 1' Group='SQL Server (WEBAPPS)' Resource='SQL IP Address 1 (ACHSQLWebapps)'' could not be found on the cluster. Please check if it exists.
I can verify that the installation builds the SQL Name and then adds the IP address. After the IP address comes online, the installation stops and that error pops up. It results in a failed install that must be removed by the "Remove Node"
wizard.
A search on the web comes up empty. Any ideas?

Hello,
To add a node to an existing SQL Server failover cluster, We should run SQL Server Setup on the node that is to be added to the SQL Server failover cluster instance.Please verify the account that you using has permission to log in as a service on all nodes
of the failover cluster.For local installations, you must run Setup as an administrator.
Reference:http://msdn.microsoft.com/en-us/library/ms191545(v=sql.110).aspx
Regards,
Fanny Liu
If you have any feedback on our support, please click
here.
Fanny Liu
TechNet Community Support

Queries on cluster installation with win2k3 & Oracle 10.2.0.4.0 for 640 rel

Dear All,
We are in a process installing sap clustered system for 640 basis release o win 2k3 with Oracle 10.2.0.4.0
However i have followed this steps as below..
Install windows on NODE-A & NODE- B, Update windows,
Install required hotfixes which controls high paging on windows as per sap note
#1009297 Windows Server 2003 Family: High Paging Rates
#1416152 Memory problems with Windows server 2003 and 2008
Tested connectivity to Storage area network as recommended in MSCS cluster guide for both NODES
Installed Java on both nodes & set variables , paging etc..
Configure widows cluster & tested the connectivity by moving the shared disks from NODE-A to NODE-B
Step 2
I have installed Oracle 10.2.0.4.0 with required bug fixes on Both the NODES by switching all the resources
After this step i am pretty confused that do i need to install OFS server & client.
or
Install CI + DB , Configure MSCS NODE-A,NODE-B
then install Oracle OFS server & client & configure & test the connectivity.
At what time my oracle cluster group to be created
At what time my SAP R/3 cluster group to be created
I am also referring to standard instguide & pretty confused on sequence to be followed
Using SAP R/3 Enterprise Core 4.70, SAP R/3 Enterprise Extension Set 2.00, Service Release 1
Please throw some light on the sequence to be followed , so much of time & effort can be saved for me.
Thanks,
Rahul..
Edited by: Rahul on Jul 12, 2010 3:21 PM

Hello all,
Thank you for the inputs provide, I have completed a first run .. with lot of issues..
Currently prparing for a cutover & i just wanted to share few inputs after installing.
The inst guide also suggest same sequence.. which i have followed...
Move all disk groups and cluster group to node A
- Install Oracle RDBMS on both nodes.
- Install OFS on both nodes.
- reboot.
- verify that all cluster groups are online (and on node A).
- Install Central Instance
- Install Database Instance.
- Configure Node A for MSCS
- Convert Database to OFS
- Configure Node B for MSCS
but i was wondering after installing CI + DB i& configured NODE A.
During Conversion of DB to OFS .. my verification failed many times & i found this is the reason..
The database must be cluster-enabled so that it can be switched between nodes as a group
of resources. To do this, you create an Oracle Fail Safe group and then add the database of
the SAP system to this group.
I have done this in the following process....using linkd.exe i have shared the oracle home & mapped to local drives on both the nodes as suggested in DB upgrade & my DB verification was successful..
However it was not provided in Instguide.. or did i missed to read some where..
Please also advice me am i doing it in correct process...for DB cluster enabling
thanks,
rahul..

Mount point won't allow read/write for non-root user

Any ideas why this particular fstab line leads to root user only read/write for any disk referenced in my fstab?
Example:
UUID=496E-7B5E /media/STORAGE vfat defaults 0 0
I have tried all variations of what "defaults" should be (rw,suid,dev,exec)
I had even added uid=0777, and no matter what options I add there, doing
sudo mount -a
or with the line in fstab commented out and
mount -t vfat -U 496E-7B5E /media/STORAGE -o defaults
causes the same issue.
Results in every filesystem there to be mounted as read only for me as a user, and I can only write to them as root.
Weird
I have run
sudo chmod -v -R a+rwx /media/STORAGE
and similarly
sudo chmod -v -R 0777 /media/STORAGE
Both were tried on the directory as mounted and unmounted. When mounted, the verbose output DOES NOT error out and shows property change of the files
Oddly, if no fstab reference is used, the disk shows up in the dolphin panel, and can be mounted in that manner and it is read write as a usual user.
Using a Chakra-live installed with Unetbootin, so perhaps that is the issue... so
How is mounting through dolphin handled and what might I use at the command line to accomplish this same routine, as I only need one partition to mount read write when the system starts, so maybe I can add the command to rc.local
Last edited by bwh1969 (2009-01-18 23:04:59)

# fstab generated by gen_fstab
#<file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
UUID=496E-7B5E /media/STORAGE vfat defaults,user,users,rw,exec,uid=777,gid=777 0 0
/dev/sr0 /mnt/sr0_cd auto user,noauto,exec,unhide 0 0
# This would do for a floppy
#/dev/fd0 /mnt/floppy vfat,ext2 rw,user,noauto 0 0
# + mkdir /mnt/floppy
# E.g. for USB storage:
#/dev/sdb1 /mnt/usb auto rw,user,noauto 0 0
# + mkdir /mnt/usb

UIM Installation in MS (VM 2) fails as it searches for files in AS (VM 1)

Dear Gurus,
Scenario:
For UIM installation, 2 Virtual Machines (VM 1 & VM 2) with no shared disk given.
VM 1 hosts Admin Server (AS) & Manage Server (MS).
After creation of domain, the directory structure is copied from VM 1 to VM 2.
Ran the UIM Installer on VM 2 with intentions to install UIM on MS running on VM 1.
Issue:
When UIM installer tries to deploy the application on MS (target server) it fails because it cannot find those files i.e. OracleCommunications and UIM folder in VM 1 which were created in VM 2 in the process of installing UIM. It still baffles me why it is not searching for the files which were created in the current VM (VM 2) but instead looking at VM 1 which were non-existent. With the same architecture, installation of OSM works perfectly with no similar issue. Basic intention behind this architecture is to segregate the Admin tasks related to Server & UIM app.
Do advise
AA
Edited by: AmosAw on Dec 2, 2012 8:48 PM

I"m sorry you're unhappy with Sun products. Many users will have different opinions.
Many of the issues we see often have had "technotes" published about them. However, many folk don't seem willing to look those up.
Many folk also don't seem interested in looking at the documentation, either.
Yes, our documentation can be confusing. Ours, and others, too.
You always have the option of moving to other vendors, anytime you wish.
In a direct comparison between Messaging Server and Exchange, however, our product looks pretty good. It's easier to maintain, handles far more users, at a lower cost per user, and is more stable.
How many Exchange servers would you need (and how many administrators) to handle 500,000 users? JES Messaging Server can do that all on one box, with very few admins.

Recovery Disk Error : cannot read from source file or disk HOW TO FIX ISSUE

I have had my satellite L655-S5096 for some time now.. I had to switch out hard-drives the other day and installed windows 7 home on it from my own disk. I tried to download all the drivers needed, but the graphics and wifi drivers never worked, so I pulled out the old toshiba disks to start from new with this harddrive.. It gets to asking me for the second disc, then the second disc gives me the the "cannot read from source file or disk PREINST8.SWM" This is from the "out of the box" setting, which is recommended. I do not know how to fix this issue besides reinstalling windows 7 from my disc and trying to get the drivers to work again.. however I shouldn't have to since I have the Toshiba recovery disks.. do I need new disks?
Yes, I also had the hard drive drivers and all of that installed.. my toshiba reads the HDD just fine.
~Drew

Satellite L655-S5096
Downloads here.
the second disc gives me the the "cannot read from source file or disk PREINST8.SWM"
My best guess is that the disc is not readable. Try copying it to another. Sometimes that works.
Otherwise, order new discs from Toshiba.
-Jerry

SQL 2008 R2 cluster installation failure - Failed to find shared disks

Hi,
The validation tests in the SQL 2008R2 cluster installation (running Windows 2008 R2) fails with the following error. The cluster has one root mount point with multiple mount points :
"The cluster on this computer does not have a shared disk available. To continue, at least one shared disk must be available'.
The "Detail.txt" log has alot of "access is denied" errors and here is just a sample. Any ideas what might be causing this issue?
2010-09-29 12:54:08 Slp: Initializing rule      : Cluster shared disk available check
2010-09-29 12:54:08 Slp: Rule applied features : ALL
2010-09-29 12:54:08 Slp: Rule is will be executed : True
2010-09-29 12:54:08 Slp: Init rule target object: Microsoft.SqlServer.Configuration.Cluster.Rules.ClusterSharedDiskFacet
2010-09-29 12:54:09 Slp: The disk resource 'QUORUM' cannot be used as a shared disk because it's a cluster quorum drive.
2010-09-29 12:54:09 Slp: Mount point status for disk 'QUORUM' could not be determined. Reason: 'The disk resource 'QUORUM' cannot be used because it is a cluster quorum drive.'
2010-09-29 12:54:09 Slp: System Error: 5 trying to find mount points at path
\\?\Volume{e1f5ca48-c798-11df-9401-0026b975df1a}\
2010-09-29 12:54:09 Slp:     Access is denied.
2010-09-29 12:54:09 Slp: Mount point status for disk 'SQL01_BAK01' could not be determined. Reason: 'The search for mount points failed. Error: Access is denied.'
2010-09-29 12:54:10 Slp: System Error: 5 trying to find mount points at path
\\?\Volume{e1f5ca4f-c798-11df-9401-0026b975df1a}\
2010-09-29 12:54:10 Slp:     Access is denied.
2010-09-29 12:54:10 Slp: Mount point status for disk 'SQL01_DAT01' could not be determined. Reason: 'The search for mount points failed. Error: Access is denied.'
2010-09-29 12:54:10 Slp: System Error: 5 trying to find mount points at path
\\?\Volume{e1f5ca56-c798-11df-9401-0026b975df1a}\
2010-09-29 12:54:10 Slp:     Access is denied.
Thanks,
PK

Hi,
We were asked by the PSS engineer to give the following privileges the account used to install SQL Server - i am referring to the user domain account as apposed to the SQL service account. These privileges were already applied to the
SQL service account prior to the SQL installation. Assigning these privileges to the user account resolved the issue.
Act as Part of the Operating Sywstem = SeTcbPrivileg
  Bypass Traverse Checking = SeChangeNotify
  Lock Pages In Memory = SeLockMemory
  Log on as a Batch Job = SeBatchLogonRight
  Log on as a Service = SeServiceLogonRight
  Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
Thanks for everyones assistance.
Cheers,
PK

DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location

Hello!
We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.
FACTS
- all servers are Windows Server 2012 R2
- all servers are Virtual (except Hyper-V hosts obviously:)
- that means virtualization is based on Windows Server 2012 R2 Hyper-V
- all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V
- SQL 2014
- DPM 2012 R2 CU4
- Primary and DR location
SETUP
SQL
- Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
- DR location: SQL 2014 Standalone using VHDX disks
- AlwaysOn Availability Group expands between the primary and DR location.
DPM
- Primary location: DPM 2012 R2 CU4
- DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.
SCENARIO
- DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
- As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.
DPM ERROR
Starting synchronization on SqlServerName\DatabaseName failed:
Error 104: An unexpected error occurred while the job was running.
Error details: The system cannot find the path specified (0x80070003)
Recommended action: Retry the operation.
TROUBLESHOOTING
- Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
> error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
> this looks like DPM is not aware that DPM is active on DR location to me
- Checked Technet, blogs and forums; no useful information
QUESTION
Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
Does anybody have a lab of that kind to try it out?
Thank you!
Best Regards,
Damjan Grimšič
Lpd

OK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.
In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.
Lpd

"Exception has been thrown by the target on an invocation" during installation of SQL 2014 CTP2

Hi.
I have this error during installation SqlEngineConfigAction_install_confignonrc_Cpu64 (component of SQL 2014 CTP2) on virtual machine (Windows Server 2012 Standart). Logs in Event Viewer are clean. And I have no idea, what can I do with such problem.
Maybe, you know and can help me?
Later in Event Viewer appears such message (maybe this message can help to resolve this problem):
Activation context generation failed for "c:\program files (x86)\microsoft sql server\120\Tools\Binn\managementstudio\CopyDatabaseWizard.exe".Error in manifest or policy file "c:\program files (x86)\microsoft sql server\120\Tools\Binn\managementstudio\CopyDatabaseWizard.exe"
on line 8. The value "1.0" of attribute "version" in element "assemblyIdentity" is invalid.
Source: SideBySide
Event ID: 63

Hi Max_Mikulik,
According to your error message, we need to verify if the Antivirus software or other application hinder installing SQL Server 2014
SQL Server 2014 CTP 2. When you install SQL Server 2014 CTP2, there are some notes.
1. You must install .NET Framework 4.0 as well as PowerShell 2.0 .
2. Copy Database Wizard has Limitations. I recommend you take a backup of the database in the instance of SQL Server running on a previous version and restore the database to SQL Server 2014 CTP 2. We can install SQL Server 2014 CTP 2 without
choosing the component about Copy Database Wizard.
For more information about SQL Server 2014 community technology preview 2 ( CTP 2) release notes, you can review the following article.
http://msdn.microsoft.com/en-us/library/dn169381(v=sql.15).aspx
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

SQL 2014 cluster installation on mounting point disks error: Updating permission setting for file

Similar Messages

Maybe you are looking for