on 02-12-2011 9:49 AM
We need to access SAPMNT hosted on CI node name R3-FFHK-CLS01 of the
PRD NT cluster
(CI and DB node) from another SAP QAS server name SAENUS.
The SAPLOC and SAPMNT was created during SAP installation and have been
granted everyone full control permission on both CI and DB node of PRD
NT cluster and SAP QAS server.
Despite the above, when we logon to Windows 2003 on SAP QAS server name
SAENUS to access the SAPMNT hosted on CI node name R3-FFHK-CLS01 of PRD
NT cluster, we received the following error :
R3-FFHK-CLS01\sapmnt\ is not accessible. You might not have
permission to use this network resource. Contact the administrator to
find out if you have access permissions. Access is denied.
We can connect and see the shares inside
R3-FFHK-CLS01 but cannot
access
R3-FFHK-CLS01\sapmnt. Strange.
On the other hand, if we logon to Windows 2003 on either node of PRD NT
cluster we can access the SAPMNT share hosted on SAP QAS server name
SAENUS without permission problem.
Regards, Johne.
We're running 4.7 Enterpise and SAPMNT is hosted on clustered (SAN storage) drive S:\usr\sap of the cluster.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Sapinst is supposed to remove the samloc and in most cases it does.
Since 700 CI and DI are installed on the local disk and ASCS is
installed on the shared disk
Is this true in your situation?
regards,
John Feely
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We logon to the cluster with domaina\prdadm.
We logon to the QAS with domaina\qasadm.
We can access SAPMNT hosted on QAS from cluster when logged onto cluster using domaina\prdadm.
We can't access SAPMNT hosted on cluster from QAS when logged onto QAS using domaina\qasadm.
Both SAPMNT has been granted everyone full control permission.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Be aware that the user who connects needs to be known on the target system, just giving "everyone" will not allow the system to connect.
Since this seems to be for transporting you need to create the user "qasadm" and "SAPServiceQAS" on the cluster.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.