System Copy:Failure when starting export with SAPINST

[Adamrog00]

We are busy with a Unicode conversion and needs to start the export with sapinst. All pre unicode conversion steps are done, we upgraded from 4.6C to ECC6.0. It is a distrubuted system running on MSSQL. Started the export on the DB server and got the follwing error below.

Regards

Roger

INFO 2007-02-08 20:09:27

Execute step stepPreconditions of component |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|ind|ind|ind|ind|0|0.

INFO[E] 2007-02-08 20:09:27

FSL-02077 File system export (share) saploc does not exist.

INFO[E] 2007-02-08 20:09:27

FSL-02077 File system export (share) sapmnt does not exist.

ERROR 2007-02-08 20:09:27

CJS-00030 Assertion failed: in NW_ABAP_Export.stepPreconditions: Executable directory 'G:\usr\sap\HD3\SYS\exe\nuc\NTI386' must exist

ERROR 2007-02-08 20:09:27

MUT-03025 Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.

ERROR 2007-02-08 20:09:27

FCO-00011 The step stepPreconditions with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|stepPreconditions was executed with status ERROR .

INFO 2007-02-08 20:09:36

An error occured and the user decide to stop.\n Current step "|NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|stepPreconditions".

[Former Member]

Hi Roger,

You most likely have answered this by now, but in case you have not.

Remember that SAP installs 2 share defintions on the \usr\sap folder. Many sap programs call the share definition and not the explicit filepath. The easiest fix here is to drill down to the G:\usr\sap folder and add the saploc and sapmnt shares to that folder. No permissions or other config is needed to get this to work.

Addtionally, check to make sure the \nuc\I386 folder exists as well. If it does, the error message may be related to the missing shares.

Good luck.

Tim

[Adamrog00]

Hi Tim

The executable drive does not exist on th DB server, but looking for it locally, we tried mapping the shared drives of the central instance, but in the drop down of the export installation it only shows local drives. SAP in Germany is also battling to solve this problem, seems to be global as it only appears to be with the distributed method.We had a work around by doing a full SAP install on the DB server, detaching the original DB and attaching after install which allowed the export and import to go thru successful. We need to go forward with the distributed method which we are still stuck.

Regards

Roger