FTPEx : 550 Unexpected reply code

Hi Experts
I am trying to connect one of the vendor's site and get the files by using the file adapter, I am able to access the file folders when i try from the https site , but this is secured site and I configured as  ftpssl
when I activate my CC i get the following error , my User Id has the access to the all folders abd files, It should not be an issue while accessing the directories and download the files
An error occurred while connecting to the FTP server 'ftpssl.rbm.com:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Unexpected reply codeAccess denied.'. For details, contact your FTP server vendor.
please suggest how can I resolve the issue
Thanks
PR

Hi PR,
This is a network issue please contact your network/Basis team they would be able to help you,,
Also you can check the discussion for the same issue in the link :Receiver File Adapter - FTPEx: 550 Access denied
Regards,
Naveen
Edited by: chichilin on Sep 20, 2011 9:15 PM

Similar Messages

  • FTPEx: 550 Unexpected reply codeAccess denied in FTPS in PI 7.11

    Hi All,
    We are having same issue with the FTPS in our SAP PI systems. On the Target FTP server side we are using the Proftpd software for the FTPS installed and configuration on port 990 and generated Certificate on FTP Server using Proftpd software.
    Error:
    An error occurred while connecting to the FTP server 'xxxxx:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Unexpected reply codeAccess denied.'. For details, contact your FTP server vendor.
    In SAP PI server Communication Channel Configuration we use below FTP configuration.
    FTP Connection Parameters.
    Server : xxxxx
    Port :21
    Data Connection : Passive
    Connection Security : FTPS (FTP Using SSL/TLS) for Control Connection
    Command Order : AUTH TLS,USER,PASS,PBSZ,PROT
    We are not using any [ ] X.509 Certificate for Clinet Authentication
    Thanks
    PR
    Edited by: PR on Nov 15, 2011 7:22 PM

    We are having same issue with the FTPS in our SAP PI systems.
    21 is the default port for FTP(S).....but you should check with the basis/ network team which port is enabled for FTPS.
    Also the ip-address of the target server should be the same as used when uploading the cert

  • FTP Error - 550 Unexpected reply code

    Hi Guys,
    I am encountering the following error in my QA Environment.
    Error Attempt to process file failed with com.sap.aii.adapter.file.ftp.FTPEx: 550 Unexpected reply codeThe filename, directory name, or volume label syntax is incorrect.
    In my receiver FTP channel, I have set the 'Temporary File Name Scheme' as '*.tmp'. I have the same setup in my Dev environment but no issue is encountered.
    When I tried to removed it, the error is not occurring.
    What do you think could be the issue?
    Also, what should be the File Type if the temp file name scheme is *.tmp? Binary or Text?
    Message Flow: IDOC -> File
    Thanks and Regards,
    Neil

    A file name should not contain "* "
    when you define the tempfilename scheme as "*.tmp" , PI is trying to create the file as *<timestamp>.tmp to place the file on FTP which is not allowed.
    refer : Configuring the Receiver File Adapter - Configuring the File/FTP Adapter in Integration Directory/PCK - SAP Library
    >>>Also, what should be the File Type if the temp file name scheme is *.tmp? Binary or Text?
    It can be anything.

  • File.ftp.FTPEx: 501 Unexpected reply codeUnknown extension in database file name

    Hi Folks,
    I am trying to place file in the iSeries library folder and for this I am using a receiver file adapter with the following config, FYI, I am not using any FCC
    Target Directory : /QSYS.LIB/XXXXX.LIB/
    File Name Scheme : FILENAME.FILE
    As I am doing this config for the first time I am using the following SCN discussion as my reference,
    File FTP to AS400 Library folder | SCN
    but i am still getting the error message at the receiver channel as below
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: An error occurred while connecting to the FTP server 'XXXXXX:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 501 Unexpected reply codeUnknown extension in database file name.'. For details, contact your FTP server vendor.
    Please let me know if anyone has anymore suggestions.

    Hi Kalyan,
    The File Name extension that you configured is incorrect I think.  Can you try to change the extension to .txt and try once.
    File Name Scheme : FILENAME.FILE
    Thanks,
    Satish.

  • Get SMTP reply code

    Hi,
    I am using destination mail server to send emails. For example to send an email to [email protected] , I do an MX lookup on mailservers for hotmail.com and use that to send mail to user fred. The reason for this is that
    I get better email validation. For example - if user fred does not exist then, I know it straight away as I get error 550.
    From what I can see, Javamail does not provide functionality to retreive SMTP reply code. It will be good if a method is added to Messaging Exception class that returns the SMTP reply code that caused the exception.
    From what I understand, the only method to get SMTP reply code is to parse the exception message for an int.
    Is there any alternative to get the SMTP reply code that caused the exception?
    Regards,
    Anmol

         public static int getSmtpErrorCode (Exception ex){
              String exceptionString = ex.toString();
              StringTokenizer tokens = new StringTokenizer(exceptionString);
              int code = 0;
              boolean flag = false;
              while(tokens.hasMoreTokens()){
                   if (flag == true) {
                        break;
                   try {
                        flag = true;
                        code = Integer.parseInt(tokens.nextToken());
                   } catch (Exception e){
                        flag = false;
              return code;
         }

  • TF270015 MSTest.exe returned an unexpected exit code when publishing results of test run

    Hello, I have a problem only with one of my three build servers.
    The build log is the follow:
    Publishing results of test run tfsbuild@HXCI07 2013-01-29 07:41:05_Any CPU_Release to
    http://server.domain.com:8080/tfs/Rivendell...
    .Value does not fall within the expected range.
    Publish failed or canceled.
    00:00
    Handle MSTest Exception
     TF270015: 'MSTest.exe' returned an unexpected exit code. Expected '0'; actual '1'.
    It's very strange because I have 3 build server with the same configuration and only this has the problem with publishing test results.
    My server: TFS 2010 SP1
    Can somebody help me?
    Thanks,
    EriC#

    Hi Eric, 
    Thanks for your reply.
    If you can run the same builds on another Build Service without this error, it seems that this issue relate to your current Build Service. So you can try to restart this Build Service(in TFS Admin Console), then compare if there’s
    some specific difference between the current build agent machine and another build agent machine(configured in another Build Service).
    To clean the TFS 2010 Cache and restart TFS Server, please refer to the following steps(delete the content of the folder only, not the cache folder itself):
    Clean the Cache folder on client computer. The folder path is: C:\Users\username(Team Explorer user name)\AppData\Local\Microsoft\Team Foundation\3.0\Cache. (os: Windows Server 2008 R2)
    Clean the Cache folder on Server machine. The folder path is:
    C:\ProgramData\Microsoft\Team Foundation\Web Access\Cache_v10.0.
    (os: Windows Server 2008 R2)
    After cleaned, on Server machine, click
    Start and select Run… to open the dialog box, then input
    iisreset.exe and click OK, wait it run completely.
    John Qiao [MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    YES!!!! Cleaning the build server
    cache solved the
    problem! Thanks John!
    EriC#

  • Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)

    Hi all,
    I have TFS2012 and run several projects.
    We encounterwed with such an error while using Build server.
    Overall Build Process
    Initial Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    00:00
    Get the Build
    00:00
    Update Build Number
    Initial Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Final Property Values
    BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
    Result = Ephone_DIT_Deploy_20150424.1
    01:56
    Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
    Initial Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    00:00
    Get the Build Directory
    Initial Property Values
    Result = d:\temp\217\CTI\Ephone_DIT_Deploy
    01:53
    If Not String.IsNullOrEmpty(ConfigurationFolderPath)
    Initial Property Values
    Condition = True
    01:53
    Run TfsBuild for Configuration Folder
    Initial Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp" 
    00:08
    Getting sources
    00:02
    Labeling sources
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
    00:19
    Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
    00:19
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:10
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:05
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
     CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:01
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
    00:02
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
    "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
    a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
    00:00
    Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
     CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
    MSBuild Log File
    00:08
    Generating list of changesets
    00:20
    Built Skins\SkinEPhone.cs for default targets.
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
     C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
    Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
       at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
       at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
       at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
       at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
       at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
       at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
    00:03
    Creating work item
     Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
    Exception Stack Trace:    at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
       at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
       at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
    Final Property Values
    BinariesSubdirectory = 
    BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
    CommandLineArguments = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MaxProcesses = 1
    NodeReuse = False
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TargetsNotLogged = 
    TestResultsSubdirectory = 
    ToolPath = 
    ToolPlatform = Auto
    Verbosity = Diagnostic
    Final Property Values
    Condition = True
    Final Property Values
    MaxExecutionTime = 00:00:00
    MaxWaitTime = 04:00:00
    ReservationSpec = Name=*, Tags=
    Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
    Final Property Values
    AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
    BinariesSubdirectory = 
    ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
    DoNotDownloadBuildType = False
    LogFilePerProject = False
    MSBuildArguments = 
    MSBuildPlatform = Auto
    RecursionType = OneLevel
    SourcesSubdirectory = 
    TestResultsSubdirectory = 
    Verbosity = Diagnostic
    Please have a look and guide where to find a problem
    Thanks ahead

    Hi Hooi,
    I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
    From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
    Best regards,

  • Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550

    Hi Experts,
    We have many File to EDI scenarios wherein XI System pick up the XML and sent to customers via EDI. Recently we faced a problem so created a Back-up System (Production copy) and tested successfully. After sometime the messages were routed to this back-up system and when we notice it and then stopped the back-up system. All the messages that were routed to back-up system, we try to send the same messages from the actually Production system to our customers. Now the problem is XI system (Production system) is unable to pick these files and I check the communication monitoring and encountered the below error message.
    Could not process due to error: com.sap.aii.adapter.file.ftp.FTPEx: 550.550
    Can anyone let me know how to fix the issue or what needs to be done?
    Your help is highly appreciated.
    Regards
    Faisal

    Hi,
    It seems to be problem with permission of files. Please ask your basis to do following:
    1. Set the permissions to FTP User you are using as 777 rights(full access to read , write and delete)
    2.If you have access to PI server, try to telnet /connect to ftp using command prompt (open ftp .....) the FTP server form there, you should see the same error there , inform this to your network guys.
    3.Clear all the files places already in the ftp (take backup) and test afresh after permissions are set by basis team.
    Regards
    Aashish Sinha

  • Receiver File adapter - FTPEx: 550 Permission denied

    Hi all,
    We are getting the following error from a File receiver comm. channel:
    Delivery of the message to the application using connection AFW failed, due to: com.sap.aii.adapter.file.ftp.FTPEx: 550 Permission denied to "inbound"..
    The FTP connection is anonymous so anyone (within our network) can login on this server, folder rights are also set to all i.e. anonymous user can create, read, delete files on the target folder.
    I have tested to the target folder using IE browser, I was able to logon the server, read, create and delete files.
    Has anyone of you an idea why the adapter engine still cannot create a file?
    Regards,
    Roberto

    > Hi Roberto,
    > 'Anonymous' is a default user that exists in Unix
    > nix layer. But for this user also you need to provide
    > the file write/read/delete permissions into the
    > folder. Then only you can write a file evenif you are
    > using 'Anonymous' User.
    >
    > Cheers
    > JK
    Hi there,
    As explained before; we have tested the same FTP connection (using the same anonymous account) via a DOS session and also via IE (from the XI server), both tests were successful and we were able to create/delete files without any problem.
    So again, the problem is only with the File/FTP adapter which for some unexplained reason cannot get access to this folder.
    Are there any special (not mentioned in the SAP documentation?) prerequisites to establish a FTP connection using the file adapter?
    Any help is highly appreciated!
    Thanks, Roberto
    BTW; we are on SP14 and the XI server runs under a Windows Server machine.
    Message was edited by: Roberto Viana

  • Receiver File Adapter - FTPEx: 550 Access denied

    Hi Experts,
    In my receiver file adapter scenario I'm getting 550 Access denied in RWB.
    I am a little confused here because I could access the FTP client from my desktop using the same User and Password informed in the Receiver CC. I also could drag and drop a file there.
    Here you have Detail Display in RWB, it seems that at least the user is working fine for PI also:
    Success: Connecting to FTP server "<FTP IP>"
    Success: Write to FTP server "192.168.10.85", directory "\Transportadoras\10326750000101\",   file "Nfe_teste.xml"
    Success: Transfer: "TXT" mode, size 8881 bytes, character encoding UTF-8
    Error: Attempt to process file failed with An error occurred while connecting to the FTP server '192.168.10.85:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Access denied.'. For details, contact your FTP server vendor.
    Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: An error occurred while connecting to the FTP server '192.168.10.85:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Access denied.'. For details, contact your FTP server vendor.
    Regards,
    Daniela
    Edited by: Daniela Machado on Aug 11, 2010 10:18 PM

    Hi Daneial,
    This is an issue due to any firewall or proxy between your Xi system and the FTP.In this case the direct logon
    works with same user but when XI tries to create file at runtime you get this error due to network issues.
    To resolve this contact your Basis/Network guys  and
    1. Set the permissions to FTP User you are using as 777 rights(full access to read , write and delete)
    2.If you have access to PI server, try to telnet /connect to ftp using command prompt (open ftp .....) the FTP server form there, you should see the same error there , inform this to your network guys.
    3.Clear all the files places already in the ftp (take backup) and test afresh after permissions are set by basis team.
    Regards,
    $rinivas

  • Application returned an unexpected return code 1632 - MDT 2012

    Hi,
    I am getting the following error while installing Adobe reader, office 2010 only in few PC's. 
    applicatio adobe reader x1 returned an unexpected return code 1632
    applicatio MS office 2010 returned an unexpected return code 1632
    can any help on this. 
    Please note that the above mentioned problem comes only in some PC's.
    D. Sendil Kumar

    http://support.microsoft.com/kb/290158/en-us
    ERROR_INSTALL_TEMP_
    UNWRITABLE              1632   The temp folder is either full or
                                    inaccessible. Verify that the temp folder
                                    exists and that you can write to it.
    Check the MSI installation logs. Whenever I install *.msi packages in MDT I turn on logging:
    Msiexec.exe /qb- /l*vx %LogPath%\<file>.log REBOOT=ReallySuppress UILevel=67 ALLUSERS=2 /i <File>.msi
    http://keithga.wordpress.com/2013/09/04/application-installation-and-packaging-via-mdt-and-sccm/
    Keith Garner - keithga.wordpress.com

  • Com.sap.aii.adapter.file.ftp.FTPEx: 550

    Hi,
    I have the below error in my sender file channel. I also read the following thread
    FTP Error
    Error:
    An error occurred while connecting to the FTP server '10.12.12.101:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 C:Inetpubftproot: The filename, directory name, or volume label syntax is incorrect. '. For details, contact your FTP server vendor.
    The above thread suggests me to change the setting in the IIS. Should do that settings in the PI server or the source FTP server.
    Also does anybody have any other solution to this problem.
    Rgds,
    Mithun

    HI,
    If you're using an FTP server you need to know the path to the file on the FTP.
    To do this I suggest to connect to the FTP using Internet Explorer and navigating the FTP folders until reaching the right one.
    Then on the url bar you should got something like this: "ftp://server:21/path/to/file/". Use "/path/to/file" as value for the file adapter configuration.
    Please refer below blogs:
    unable to send file to FTP server
    FTP to Windows Server
    thanks,

  • File to File-CC 'error com.sap.aii.adapter.file.ftp.FTPEx: 550 Access deni'

    Hi friend,
    I am doing file to file scenario in which i wan to move one file from input folder to output folder.
    I had created as FTP on one system that i am able to access and have full authorization to read and write.
    and created that two input and output folder in it,n kept an xml file in input folder.
    When i see sender communication channel in RWB it is showing error, "com.sap.aii.adapter.file.ftp.FTPEx: 550 Access denied'
    I checked password,it correct also I tried to test it using Anonymous Login, but the same things.
    SO i am not sure where i had done mistake.
    Plz give ur suggestions.
    Thanks

    Hi,
    Please Check below few steps:
    Check if the username and the Password is created to write the file in the desired directory.
    Check the username is provided the authorization to write the file in the desired directory. ... IS Guys will help you..
    Confirm if the directory created have all the authorization to write the file.
    ls - lrt
    chmod 777 Directory Name
    all the authorization will then be provided
    Confirm if the directory is created with the root id then it there might be some problem with the user name u r trying to create..
    Hope this will help.
    Assign points for helpful answer..
    Thanks
    JAY.

  • Com.sap.aii.adapter.file.ftp.FTPEx: 550 You are not allowed to issue this

    hi All,
    We are getting below error while connecting to an FTP location through File Adapter:
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: An error occurred while connecting to the FTP server XYZ. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 You are not allowed to issue this command'. For details, contact your FTP server vendor.
    Also when we tried to connect to this FTP location through PI server we able to connect, but when we connect to it through channel we are getting above error.
    Please Help!
    Thanks,
    Mayank

    hi All,
    The usedid we are using to connect to FTP location has appropriate access to write(we have an receiver file adapter) the files, when we connected to FTP location from PI server using same useid(as used in channel) we are able to connect to FTP location and also able to write the file there.
    Now error soming is:
    An error occurred while connecting to the FTP server XYZ. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Operation is not supported under Connect:Enterprise FTP server.'. For details, contact your FTP server vendor.
    Thanks,
    Mayank

  • FTPEx: 550  : Cannot create a file when that file already exists.

    Hi experts,
    I am working on idoc to file scenario and PI 7.1. The idoc is split into 3 files.
    In sxmb_moni , the message is successful , but in rwb( Message montoring) i am geeting the fllowing  Error message.
    ' Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: An error occurred while connecting to the FTP server '172.19.125.190:21'. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 /Storedata/Outbound/0000001802: Cannot create a file when that file already exists. '. For details, contact your FTP server vendor..'
    and this error message is not displayed for all the target files , some files are getting created succesfully.
    After some times , the file in error status , gets created automatically.
    What may be the reason.?
    Thanks in advance .
    Best Regards,
    Anil

    There seem to be already some files in your Target Directory with the same name as your new files (which the CC is trying to place) and the CC is not able to overwrite the existing files and hence the error...check this.
    Check: http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/69d7cfa4b633eae10000000a1553f6/content.htm
    14.      Select the File Construction Mode.
    u25CB       Create
    The file is created. The document received last is saved in each case.
    If you want the created file to be overwritten, select Overwrite Existing File. If you do not set the indicator, processing is stopped until the created file is processed.
    You can only set the indicator if you select Use Temporary File under Put File below.
    Regards,
    Abhishek.
    Edited by: abhishek salvi on Jul 28, 2009 6:59 PM

Maybe you are looking for