SAP Note

Header Data

Symptom

Authorization problems occur for the file I/O on network drives from the R/3. Such a problem typically occurs after you successfully set up a central transport directory. The R/3 Systems belonging to the group do not belong to the same NT domain. The participants of the transport group which are informed about the modified transport directory via the DIR_TRANS parameter in the instance profile are not able to access this directory via Transaction AL11. The following error message is displayed: Wrong order of calls HOST B(shared resource) | domain user : ABCadm | \______________________/ The domain user account is valid in the whole domain.

2. All participating R/3 instances are members of an NT work group or standalone server

In this case, the respective operating system users are only locally valid on the servers, and the conditions for the above error are given. A possible solution is to include the server in a domain and to exchange the local users with domain users. Since this is quite an effort (the startup users for every SAP service must be changed), you must decide whether the following method is more useful. The disadvantage of local validity can be avoided by creating the respective users who need access to the remote resource (for example the server with the central transport directory) with the same name and the same password on the target computer. Work group or standalone server: No Access HOST A------/-----> HOST B (shared resource user: A* pwd : ABC Access HOST A------------> HOST B (shared resource) user: Auser: A pwd : ABCpwd : ABC * the SAP System uses users adm and SAPService

3. The participating R/3 instances are member of several NT domains

If a what is known as 'trust relationship' exists between the domains, the users of a domain can also access resources of foreign

117395 - Authorization problems for file I/O on Windows NT

Version 6 Validity: 12.04.2002 - active Language Ingls

Released On 12.04.2002 10:34:04 Release Status Released for Customer Component BC-OP-NT Windows Priority Recommendations / Additional Info Category Help for error analysis

domains. A 'trust relationship' is only unidirectional by default. That means that only users of the one domain may access the resources of the other. However, mutual accesses are also possible by setting up a mutual status of confidence. Without 'trust relationship' the precondition for the above problem is given because the domain users are only valid locally in their own domain. However, you an also solve the problem with a workaround with a second user of same name and same password. Domain ADomain B ____________ \No Trust/ |Relationship| HOST A ----------------> HOST B (shared resource) |No Access ! | _____ /\ _______ Domain ADomain B ___________ \No Trust/ | Relationship | HOST A ----------------> HOST B (shared resource) |Access !| ______ /\ _______ user: A*user: A pwd : ABCpwd : ABC * the SAP System uses users adm and SAPService You must check which method is most appropriate for your individual case.

Other Attributes

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (4)

AL11

FILE

HIER

NT/ALPHA

NT/INTEL

556734 FAQ Transport: Setup and further information 99155 DATASET_WRITE_ERROR / DATASET_CANT_OPEN on NT 48486 R/3 server in different NT domains

48486 R/3 server in different NT domains 99155 DATASET_WRITE_ERROR / DATASET_CANT_OPEN on NT 1172252 CTS+, 'attach file': Troubleshooting Guide 556734 FAQ Transport: Setup and further information