SAP mapping network drive without downtime. Wrong order of calls <- CALL opendir

[Former Member]

During a windows patchday we lost some of our mapped network drives. All of the permissions were set correct as of note 117395.

The access on operating system level was working perfectly fine.

I know that the SAP System works with the SAPService<SID> user. Due to this i logged on to the server and checked the mapped network drive:

The access to the folder was possible.

I checked ( and recreated ) the mapped network drive in the SAP System:

The error wrong order of calls <- CALL opendir was normally resolved after a system restart. In this special case i had no chance.

I also implemented a small application server and mapped the network drive to the new server.

The access was still not possible. Althou the UNC Connection worked!

During the resarch i came across Report RSBDCOS0. This report allows to acces the operating system level directly.

From here i could also check what setting are active in the SAP system.

The access to directory I: was not possible. ( I also had one Applikation Server where the Status was "ok" but i still could not logon to directory I: via transaction al11 )

After deleteing the the mapped drive both in the sap system and on os level with the command:

net use I: /delete

i created the link again with Report RSBDCOS0

The access was possible inside the report.

Double checking inside transaction al11 also working:

I did not manage to find out why the restart was not working. At the end i found a nice solution to map those network drives without any downtime.

Rainer