Configured source directory .... does not exist was suppressed

Hi,
Below log is from PI 7.1 EHP1 system. I have tried to execute simple use cases from SDN but got below exception. The folder actually is there and there is not typing error. What could be the problem and any solution?
Kind regards,
Altug
#2.0 #2010 05 11 01:57:10:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124200000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4767#Plain##
Channel XiPatternChannel_FileSender: Directory C:
work
XIPattern1 does not exist#
#2.0 #2010 05 11 01:57:10:002#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124300000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@67c2a0d6_4768#Java##
Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
work
XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
#2.0 #2010 05 11 01:57:20:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124400000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4769#Plain##
Channel XiPatternChannel_FileSender: Directory C:
work
XIPattern1 does not exist#
#2.0 #2010 05 11 01:57:20:017#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124500000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@1cfe7a5d_4770#Java##
Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
work
XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
#2.0 #2010 05 11 01:57:30:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124600000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4771#Plain##
Channel XiPatternChannel_FileSender: Directory C:
work
XIPattern1 does not exist#
#2.0 #2010 05 11 01:57:30:017#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124700000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@d023a80_4772#Java##
Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
work
XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
#2.0 #2010 05 11 01:57:40:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124800000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4773#Plain##
Channel XiPatternChannel_FileSender: Directory C:
work
XIPattern1 does not exist#
#2.0 #2010 05 11 01:57:40:002#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124900000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@76395415_4774#Java##
Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
work
XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#
#2.0 #2010 05 11 01:57:50:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124A00000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4775#Plain##
Channel XiPatternChannel_FileSender: Directory C:
work
XIPattern1 does not exist#
#2.0 #2010 05 11 01:58:00:002#+0300#Error#com.sap.aii.adapter.file.File2XI#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124B00000000000007B0#9722350000001755##com.sap.aii.adapter.file.File2XI.getFileList(File2XIConfiguration.FileSource[])#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI File2XI[XiPatternChannel_FileSender/PI7_FileSystem_XIPattern1/]_4777#Plain##
Channel XiPatternChannel_FileSender: Directory C:
work
XIPattern1 does not exist#
#2.0 #2010 05 11 01:58:00:002#+0300#Error#com.sap.aii.af.service.administration.impl.AlertingStatusListener#
#BC-XI-CON-AFW#com.sap.aii.af.lib#000C293D9117124C00000000000007B0#9722350000001755##com.sap.aii.af.service.administration.impl.AlertingStatusListener.run()#J2EE_GUEST#0##488CE8105C4F11DF9D42000C293D9117#488ce8105c4f11df9d42000c293d9117#488ce8105c4f11df9d42000c293d9117#0#XI AF AAM AlertingStatusListener$AsyncAlerter@37d6d40_4778#Java##
Unable to raise alert for fatal process status (adapter :, channel ): com.sap.aii.af.service.alerting.AlertingException: An alert with suppress information:  Error Code:  Error Category:  Error text: Configured source directory 'C:
work
XIPattern1' does not exist was suppressed!Host:w2k3x64_PI7_00|AdapterType:File|Sender::PI7_FileSystem_XIPattern1|Receiver::|Interface:XiPatternInterface1:http://sap.com/xi/XI/System/Patterns|MsgID:null#3#http://sap.com/xi/XI/System#File#7be7f5b9e06c30cc97f90f55a21e150e#

Hi,
Use this as a source directory mention the \ at last "C:
work
XIPattern1\"
This doesn't help me. But later I give a permisson to the directory for everyone group. This time PI process worked and processed file.
Thanks.
Altug

Similar Messages

  • File Adapter to iSeries IFS "Configured source directory does not exist"

    Good day, All
    We are using PI 7.1
    I need the PI file adapter to pull a file off of an iSeries(AS400) IFS folder directory.
    I'm able to configure the file adapter to pull off files from the PI server C and D drives.
    I'm able to configure the file adapter to pull off files from other network drives.
    But the iSeries IFS folder keeps coming back "does not exist".
    I've configured the Source Directory with / and with \ and it doesn't help.
    I am able to navigate to the folder while logged into the PI server as the server admin.
    I've tried mapping a drive on the server to the IFS folder but that doesn't work either.
    Please help!!!
    I've wasted too much time trying different settings on this already.
    Any assistance would be greatly appreciated.
    Thanks,
    Chad

    Dear Chad,
    Please go through the following SDN link :
    - Configured source directory .... does not exist was suppressed
    give the write permisson to the directory for everyone group and check if that helps.
    Also, kindly go through the following links :
    1) http://wiki.sdn.sap.com/wiki/display/XI/TroubleshootingtheFile+Adapter (point 2)
    2) Not able to read files from Windows directory to Unix Server using NFS
    which might give some hints in solving your issue.
    Best Regards
    Nishwanth

  • Configured source directory does not exist

    Hi Guys,
    I had configured a sender file adapter and when i check the CC monitoring it gives the message : Configured source directory '/usr/sap/NRD/SYS/global' does not exist. But the directory is in the AL11 of R/3 application server. Iam using the NFS in the File Adapter Communication channel.
    Can anyone throw some light reagrding the error.
    Thanks,
    Kittu.

    Kittu,
    1. With NFS , XI server can acccess only folders available on its OWN local path. It cannot access the Path of your R3 machine. The XI server is looking for the path on its own directories and it is not finding the same.
    One option is to mount your Drive on the XI server to some folder. Not something I
    would recommend thought.
    2. The better thing to do would be,
    a) place the file on the XI 's some folder ( you would need a local directory access to the server) or some program to upload the file to the server.
    b ) Use FTP. Look into this blog by Shabrish for how to set up a FTP ion your Local Desktop and make XI access the same,
    /people/shabarish.vijayakumar/blog/2006/08/01/along-came-a-file-adapter-mr-ftp-and-rest-of-the-gang
    Regards
    Bhavesh

  • Error in sender file adapter: source directory does not exist

    Hi,
    The PI system is 7.11
    I've created sender file adapter with following details:
    Transport Protocol : File System
    Source directory: /interfaces/In
    I checked in AL11 that this path really exists and it does. (I can even see the .txt file that should be processed.)
    But still i get in Communication Channel Monitoring the following error:
    "Configured Source directory "/interfaces/In" does not exist.
    (i also tried to give the source directory as "interfaces/In" and as "//interfaces/In" but still the same error.
    Any suggestions as to what is wrong?
    kr
    Robert

    Actually, Need to use forward slash (/) to separate directory names in accordance with the Java specification.
    But wanted to try if that works..
    Also check directory name , path again as this is case sensitive...
    --Divyesh

  • Distribution manager failed to process package - the source directory does not exist

    Hi,
    I have the following behaviour:
    A Software Update Deployment Package is not distributing because of the following error:
    I have found the following query (http://blogs.technet.com/b/ken_brumfield/archive/2013/01/10/troubleshooting-sccm-software-update-deployment-package-distribution-due-to-missing-directories.aspx) to
    determine which update is missing.
    It is about update KB978601. If we search this update in the console, we see this:
    The update is not required, not downloaded, not deployed and superseeded.
    If we look into the members of the Update deployment package, we can't find this update.
    When I was digging into the database, I found this:
    SELECT
    distinct cp.Content_ID,
    cp.ContentSubFolder,cp.PkgID,
    con.ContentProvisioned
    FROM
    [dbo].[vCI_ContentPackages] cp
    INNER
    JOIN [dbo].[CI_ConfigurationItemContents]cic
    ON cp.Content_ID
    = cic.Content_ID
    inner
    join dbo.v_CIContents_All
    con on con.Content_ID
    = cp.Content_ID
    where cp.PkgID
    =
    'XXX002BA'
    and cp.ContentSubFolder
    =
    '39b46f0a-7244-48a6-b795-119ac74009f9'
    which resulted in:
    Content_ID ContentSubFolder PkgID ContentProvisioned
    16828355 39b46f0a-7244-48a6-b795-119ac74009f9 BP1002BA 1
    I found the "ContentProvisioned = 1 " a little bit strange.
    So, my question is:
    Why SCCM is thinking of distributing the content although it is not downloaded or deployed and how can we fix this?
    Has it something todo with the "ContentProvisioned" or is it something else?
    Thanks,
    Sem

    I can tell you why CM wants to distribute it, but the easiest way would be downloading that patch thus adding it to the package (so that it can be distributed) and remove it afterwards.
    Torsten Meringer | http://www.mssccmfaq.de

  • ERROR: Cannot start mail services, configuration directory does not exist

    I'm running an Xserve G5 with one internal boot drive and one RAID using the other two internal drives. I used Apple's Disk Utility to set-up the RAID.
    Back in early December, I moved my mail database and mail store to the RAID. Ever since, when I restart the server, the mailaccess.log generates the following error:
    Jan 23 18:51:33 mail master[47]: ERROR: Cannot start mail services, configuration directory does not exist: /Volumes/RAID/mail.data/db
    I'm speculating this is a timing error that gets created when Postfix initially can't find the RAID. Then, it must try again and find it because the error message does not repeat and mail starts running.
    Is this something to worry about?

    Hi Joel,
    You're right, it's a timing issues. The mail system is ready for work before the file system is mounted. It's benign.
    Jeff

  • File adapter : Do not poll if directory does not exist

    Hi people !
    I have a BPEL process that takes files as Input messages.
    I use a file adapter to do that.
    It works well but I would like to avoid polling the directory if it does not exist, do you know how to control if the directory actually exists ?
    Here is the File Adapter configuration :
    <jca:operation
    PhysicalDirectory="PhysDir"
    ActivationSpec="oracle.tip.adapter.file.inbound.FileActivationSpec"
    PhysicalArchiveDirectory="ArchiveDirl"
    DeleteFile="true"
    IncludeFiles=".*\.xml"
    PollingFrequency="30"
    MinimumAge="0"
    OpaqueSchema="false" >
    </jca:operation>
    Even if the directory does not exist, the process endlessly tries to poll that directory.
    Thanks in advance,
    Romain.

    I do agree with you that the directory should exist because the adapter was configured to poll on that directory !!
    Nevertheless, I would like to know how to control its existence before polling...
    Romain.

  • Source system restore - Source system does not exist

    Hello friends,
    We have a problem. Now we have a new test system QA2. From BW system source system connection was configured for older test source system QA1.
    We needed to route this source system to new system. I tried with changing RFC of QA1 to QA2 details.
    Now, when i check RSA1 source system Check for QA1, i get this error :
    Port 'A000000103 ' of type 'ALE ' does not exist
    No destination exists to source system QA1
    I can see this source system in RSA1 in BW. However, in WE21 port is not available now.
    Please suggest.
    I do not have to lose transfer rules/PSA tables..etc.
    thanks
    ashish

    I get this when i try to restor connection :
    Source system does not exist
    Message no. RSAR175
    Diagnosis
    You have specified that you want to restore source system QA2. This source system is not known in BI.
    System Response
    The source system is not restored.
    Procedure
    Recreate the source system.
    If the source system should be known to BI, the name of source system QA2 may be incorrect. Rename the source system and try the function again.

  • Error in file receiver adapter (Directory does not exist / cannot be create

    I have a NFS reiceiver file NFS adapter with target directory:
    10.128.68.38\arbo2000\UploadPinfos\arbodev
    if I run this line in windows, windows access to this folder.
    Full Error log:
    Receiver Adapter v2123 for Party '', Service 'BS_0000_ARBO_DEV':
    Configured at 2006-04-06 18:08:26 CEST
    History:
    - 2006-04-06 18:08:35 CEST: Error: Message processing failed: Exception: Message processing failed - configuration error in file receiver adapter (Directory does not exist / cannot be created)
    Can somebody help me please??

    Hi Alvaro,
            If your XI server is running on Unix platform then you'll get the access only after mounting 10.128.68.38 this system as a drive. This is equivalent to the windows network mapping.
    Next thing is that once that is done then you can access the path /arbo2000/UploadPinfos/arbodev by mentioning it in your directory path.
    To check whether the above mentioned is the problem then pls do try by doing it with FTP protocol. If it works then for acting as a local directory for NFS you need to mount the drive.
    Cheers
    JK

  • Transporting Process Chain - error  Source system does not exist

    Hi,
    I tried to transport a local PC by itself (not including its main meta chain) since I have only done modifications in the local PC only. In the PC, there are PSA Processing, ODS Processing, ODS Activation, ABAP Program w/ variants and Infocube Rollup.
    However, I got the following transport error: Source system does not exist
    =======
    Diagnosis
    Source system  is not known.
    System Response
    The imported data for DataSource  was deleted again because the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP on an existing productive source system.
    Procedure
    Create the referenced source system in the Data Warehousing Workbench or define mapping to a known source system in table RSLOGSYSMAP.
    You get to maintenance using Tools -> Conversion of the logical system names.
    ============
    I have checked at the table RSLOGSYSMAP and all source system mappings are in order.
    And the weird thing is, upon checking the PC itself in the transport-to box, I can activate it without any error.
    FYI, we are currently upgrading to BI Accelerator. Am not sure if this could be one of the reasons.
    Any inputs and tips are highly appreciated and will be rewarded with points accordingly.
    Thanks

    Hi,
    This error is due to the fact that the
    mapping table for the after import (RSLOGSYSMAP) is not correct maintained in PB7 system.
    You need to maintain table RSLOGSYSMAP in each system
    You can find the steps to do it in the attached note 127326:
    o  Maintain table 'RSLOGSYSMAP' in the target BW with view
       'V_RSLOGSYSMAP' and enter as 'original source system' the logical name of the source system in the source BW and as 'target source system' the logical name of the source system in the target BW.
       This maintenance is required since it allows the correct source system reference of the InfoSources to be transported.
    This source system reference in turn is absolutely necessary to activate the transfer structure.
       Example:
       Source BW with source system AAA.
       Target BW with source system BBB where the source system AAA
       corresponds to the source system BBB.
       Entry in RSLOGSYSMAP in the target BW:
       Original source system: AAA, target source system: BBB.
       Give the DDIC user in the source BW in client 000 the
       authorization profile S_RS_ALL to create BW objects.
    Cheers
    Rajesh

  • Input File repository server Error: The requested directory does not exist.

    Hi,
    Getting following error "The requested directory does not exist." for Input and Out put file repository server.
    The specfied directory exists and the user has local administrative privelges with full control of the IFRS and OFRS location.
    The location was earlier working and after trying to implement Windows AD the things stopped. Have tried reverting the things but the following issue still persists.
    Thanks,
    Manpreet

    @Siva,
    I am not using the defacult FRS, I have specfied a specfic location on which the user has full control.
    this was working prior to the Windows AD setup tried by me.

  • ELoad Message Webpage Dialog - Repository root directory does not exist ...

    I get the following eLoad Message Webpage Dialog message:
    Repository root directory does not exist or is inaccessible:
    Repository:QC Scripts
    Directory:\\kocfs01\Collaborate\Ingenium Imp Study\PRIDE\QA\QC Phase II - Client Fraternal\e-Tester Scripts
    (messag id=repos.missingRootDir)
    Everything was fine a few dys ago.
    How do I fix this?

    The problem was due to a 'canceled' user id in the 'Services" Log On As field. Once a valid user id was entered and the services restarted, eLoad opened without the Repository root directory Warning message

  • ~/oradiag_$USER/.. and "Directory does not exist for read/write" issue

    Hi.
    Recently I've discovered that ADR was creating a folder in one of ours Oracle 11.2.0.1 server, in the users home like ~/oradiag_$USER/.. The problem is that this logging files dont stop growning, and they are filled only with this lines:
    Wed Apr 11 13:40:06 2012
    Directory does not exist for read/write [usr/oracle/product/11.2.0/log] [usr/oracle/product/11.2.0/log/diag/clients]
    Wed Apr 11 13:40:06 2012
    Directory does not exist for read/write [usr/oracle/product/11.2.0/log] [usr/oracle/product/11.2.0/log/diag/clients]
    Wed Apr 11 13:40:06 2012
    Directory does not exist for read/write [usr/oracle/product/11.2.0/log] [usr/oracle/product/11.2.0/log/diag/clients]
    Wed Apr 11 13:40:06 2012
    Directory does not exist for read/write [usr/oracle/product/11.2.0/log] [usr/oracle/product/11.2.0/log/diag/clients]
    Wed Apr 11 13:41:06 2012
    Directory does not exist for read/write [usr/oracle/product/11.2.0/log] [usr/oracle/product/11.2.0/log/diag/clients]
    etc
    I've searched around internet about this issue all that I've found is a "workaround" by creating those folders. And yep, it works, it stops growning.
    Then I checked the others servers that we have, and the problem replicates in some servers with the same Oracle version.
    My question is: Why this? Why in some servers ADR is looking for that folder? That folder didnt exist in any of them, but only some servers tries to read/write on it (or, at least, log it) What parameter relies on it?
    Regards.

    Metalink note
    11g Sqlnet Log Shows Error "Directory does not exist for read/write" [ID 797678.1]
    Errors Filling log.xml and sqlnet.log: Directory does not exist for read/write [opt/oracle/oemagent/agent11g/log] [ID 1291286.1]

  • Src/wwu directory does not exist

    Chapter 3 of three of the Single Sign-on Administrator's Guide (Rel. 3.0.9) refers to 'ssoexp.csh' in the "src/wwu directory in
    which Portal is installed". What are they talking about?
    I found an "ssoexp.csh" in ".../Portal30/admin/plsql/wwu" that I am going to use.
    Does this mean my Portal install was done wrong? Or is the documentation off?
    TIA

    Hi,
    I tried to change the directory for DIR_TRANS but I encountered the error directory does not exist. The directory is something like that
    switest\sapmnt\trans. Anything went wrong?
    Ideally the share
    switest\sapmnt points to the location <drive>:/usr/sap/
    Taking your case , sapmnt should point to
    switest\<Drivename>\usr\sap.
    So will be need to ensure that this location is shared as sapmnt and you have created a folder trans under this location.
    Hope this helps.
    Regards,
    Deepak Kori

  • Specified directory does not exist

    Hi there,
    I'm having a wierd problem, and can't seem to find a way around it.
    I'm logging into my clients' version 5 SP10 application, and the "Finance" app works fine: all dimensions downloaded, all folders created locally, etc (today is the first day I've used my PC with this appset so I didn't have these locally previously).
    However, when I switch to my "interco" app, or any other, I get this error (NOTE: my user profile folder is on D not C):
    "The Specified directory does not exists: D:\Jason\Documents\Outlooksoft\<Server Name>\<User>\App Info\<Appset>\<Application>\eExcel"
    Sorry, not very easy to read!
    It doesn't seem to create these folders. But if I do it manually (through My Computer), the next time I log in I don't get the error - presumably because the folder has been created.
    My colleague has the exact same problem from the exact same application set, and we are using different Windows OSs (he is on XP and I'm on Vista) so it can't be that.
    Any ideas? I have worked at this client many times, but not since SP10 was applied - could that be the cause of the problem?
    Thanks as always!
    Jason

    Jason,
    I had the same issue with a few applications. SAP tech advised me to copy an application and it should re-create folder structure. Another approach is to process application without selecting any options - should also re-create folder structure, but I can't confirm this one.
    And 3rd way is to copy folder structure from a good (working) version of the same application into the "broken" one.
    Hope that helps,
    Akim

Maybe you are looking for