PERMISSION DENIED IN FTP SERVER

Hi all,
i have XML to XML scenario. i have put xi_input.xml in my system and made delete mode in sender communication channel. but its not picking and deleting the data, its giving error in FTP serve as "permission denied" and in runtime work bench error is "Failed to delete file 'xi_input.txt' after processing. The FTP server returned the following error message: 'com.sap.aii.adapter.file.ftp.FTPEx: 550 Permission denied'. For details, contact your FTP server vendor.". please help me
thanks and regards

>
pawan kumar wrote:
i m getting output XML file in my system.but i tried with directly one to one mapping in message mapping, now i did some modification in Message mapping like i concatenate name by X in message mapping and in description i passed ZSUBHODIP as constant then in output i am not getting concatenateed value and constant ZSUBHODIP in name and description.
Hi,
Did you activate the message mapping after modification ??
If yes, test the mapping in test tab and let us know the exact error.
Regards,
Chandra

Similar Messages

Scp works sftp permission denied - debug sftp-server process ?

We have a number of servers where we can scp a file on to the server, but when we try and sftp onto the server and put a file we get permission denied. The sftp connection works and we can cd arround just not put a file.
Its not a file/folder permissions problem.
Any ideas?
Is there any way under solaris 10 to put debug on the sftp-server process? you could under solaris 8 but according to the man pages under 10 the options have gone.

Try turning on logging.
I typically edit /etc/syslog.conf and add an entry
local7.info;local7.debug /var/log/sshd
ensuring the entries are tab delimited.
Then
touch /var/log/sshd
Edit /etc/ssh/sshd_config and change
SyslogFacility auth
LogLevel info
to
SyslogFacility LOCAL7
LogLevel debug
Restart everything:
svcadm restart system-log
svcadm restart ssh

DNS permission denied for vpn clients?

I have an x-serve setup to allow a client access remotely to a local network via VPN. I'm currently having an issue with the DNS server however, which is not allowing me to do lookups when connected via the VPN:
client 10.0.0.130#59551: view com.apple.ServerAdmin.DNS.public: error sending response: permission denied
The DNS server resolves perfectly fine for physical machines on the local network.

Have you added the range of VPN-assigned addresses to the list of clients the DNS server will respond to?
Server Admin -> (server) -> DNS -> Settings -> Accept recursive queries from the following networks
This will have to include the VPN client address range in order for the DNS server to respond to their queries.

FTP exception: Can't open passive connection: Permission Denied

I have a File sender adapter, with FTP as transport protocol.
The adapter polls a directory each 60 seconds.
All works perfectly but <b>sometimes</b> I get the following error :
Channel CC_GBL_FlatFileSender: Error connecting to ftp server ...: com.sap.aii.adapter.file.ftp.FTPEx: 425 Can't open passive connection: Permission denied.
And 60 seconds after, no more error.
Any idee of why I get this error occasionally ?
In the sender file adapte, data connection is set to Passive. Do I have to set it to Active ?
Thanks in advance,
Laurence

Hi
Data Connection
- Active
In active mode, the server establishes a data connection from its data port, port 20, to an end point chosen by the client.
- Passive
In passive mode, the client establishes a data connection to the port required by the server.
The default setting is a passive data connection. Only change this setting if you have a specific reason. This is what is recommended by SAP.
It is possible that Passive FTP mode may terminate session.
In this mode the server "listen" on a data port (which is not its default data port) and to wait for a connection rather than initiate one upon receipt of a transfer command. The response to this command includes the host and port address this server is listening on.
In the FTP protocol two ports are normally used, 20 and 21.
Port 21 is the control channel in which requests such as PUT, GET, and PWD are sent to the server.
Port 20 is the data channel in which actual files, folders and directory
listings are sent.
Normally, when you connect to an FTP site, the site establishes the data
connection to your PC (the client) on Port 20. However, if the site allows
passive transfers, you can have your PC establish the data connection. It is
recommended that you use passive mode for most transfers.
Regards
Sumit Jain
**Reward with points if you find it useful.

Permission Denied on Solaris 10 NFS share, shared trough Windows Server 2008R2

Hello,
We have a NFS share on Windows Server 2008 R2 setup the following way,
NTFS permissions for ANONYMOUS LOGON and Everyone groups are set to Full control.
When mounting this share on our Solaris workstation, it mounts and we can view files in that mount but cannot edit or write to it.
mount -f nfs 10.0.0.2:/Folder/ /test
permissions are set as:
drwxrwxrwx 2 nobody nobody 4096 Mar 4 08:57 test/
when in test direcorie, trying to copy a file gives this error:
cp gp.txt gp_1.txt
cp: cannot create gp_1.txt: Permission denied
Please help,
Thanks

Hi,
Is there any error message in the Event Log on Windows Server 2008 R2? Please try to install the hotfix in the KB article below.
"Permission Denied" error when a UNIX user accesses files on an NFS share in Windows Server 2008 R2
http://support.microsoft.com/kb/2485529
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

"Error Starting OMI-Server. Unable to bind socket.Permission denied. Listen

Hi All,
I Installed Forms 1o-g successfully on my mishon ( Version windows vista), when i try to connect Forms i got error
like this *"Error Starting OMI-Server. Unable to bind socket.Permission denied. Listen*
Plz Anyone help....
Thanks
sa.....

Which version of Windows Vista? Bear in mind that Vista home edition is not supported by Oracle (I think for all products). If that is the case, you should be upgrading your OS to business or ultimate edition.
If that is not the case, please get in touch with Oracle support. Not much is available on internet or in forums (as you seem to have posted this in Forms forum as well).

Mount: failed reason given by server: Permission denied

Hi,
I am getting this error when tried to mount
# mount sfxdb01:/db01/u20/oracle/prodarch /db01/u20/oracle/prodarch
mount: sfxdb01:/db01/u20/oracle/prodarch failed, reason given by server: Permission denied
What is the reason?
Thanks,
Kavitha

kavi wrote:
Thank you chad.
How can check the remote server is denying the permissions?
Which file shows the error message in /var/log?
If it is denying permissions, how can I give the permissions?
Regards,
KavithaYou'll need access to the remote server to do this - I'm going to assume that this server (to you) really is 'remote', so the best thing to do is to contact the system administrator; this isn't an error you can solve if you don't have administrative rights to the remote server.

BEA-002606: Weblogic server runs on port 80 - permission denied.

Hi,
I am new to weblogic, just started to playing around with it. I setup weblogic server with a cluster consisting of 2 servers, all running locally. I was trying to configure the web server functionality on weblogic 10.3. I followed the exact steps described at http://edocs.bea.com/wls/docs103/config_wls/web_server.html, but I keep on getting a permission denied error:
<Dec 2, 2008 3:00:10 PM> <Info> <NodeManager> <Working directory is "/opt/bea/user_projects/domains/firstDomain">
<Dec 2, 2008 3:00:10 PM> <Info> <NodeManager> <Server output log file is "/opt/bea/user_projects/domains/firstDomain/servers/server03/logs/server03.out">
<Dec 2, 2008 3:00:12 PM MYT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 10.0-b19 from Sun Microsystems Inc.>
<Dec 2, 2008 3:00:13 PM MYT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
<Dec 2, 2008 3:00:16 PM MYT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 2, 2008 3:00:16 PM MYT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Dec 2, 2008 3:00:16 PM MYT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/bea/user_projects/domains/firstDomain/servers/server03/logs/server03.log is opened. All server side log events will be written to this file.>
<Dec 2, 2008 3:00:26 PM MYT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Dec 2, 2008 3:00:41 PM MYT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Dec 2, 2008 3:00:41 PM MYT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Dec 2, 2008 3:00:44 PM MYT> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
<Dec 2, 2008 3:00:44 PM MYT> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 2, 2008 3:00:44 PM MYT> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of Cluster-00.>
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <Cluster> <BEA-000162> <Starting "man" replication service with remote cluster address "null">
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <Cluster> <BEA-000162> <Starting "man-async" replication service with remote cluster address "null">
<Dec 2, 2008 3:01:14 PM MYT> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address 172.16.141.1 might be incorrect or another process is using port 80: java.net.BindException: Permission denied.>
<Dec 2, 2008 3:01:14 PM MYT> <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
<Dec 2, 2008 3:01:14 PM MYT> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[3]". The address 127.0.0.1 might be incorrect or another process is using port 80: java.net.BindException: Permission denied.>
<Dec 2, 2008 3:01:14 PM MYT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceeding log message for details.>
<Dec 2, 2008 3:01:14 PM MYT> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[2]". The address 10.8.8.31 might be incorrect or another process is using port 80: java.net.BindException: Permission denied.>
<Dec 2, 2008 3:01:14 PM MYT> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[1]". The address 192.168.140.1 might be incorrect or another process is using port 80: java.net.BindException: Permission denied.>
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 2, 2008 3:01:14 PM MYT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <Cluster> <BEA-000163> <Stopping "man" replication service>
<Dec 2, 2008 3:01:14 PM MYT> <Notice> <Cluster> <BEA-000163> <Stopping "man-async" replication service>
<Dec 2, 2008 3:01:15 PM> <Debug> <NodeManager> <Waiting for the process to die: 19768>
<Dec 2, 2008 3:01:15 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
<Dec 2, 2008 3:01:15 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Netstat shows:
netstat -an | grep 172.16.141.1
tcp6 0 0 172.16.141.1:7001 :::* LISTEN
tcp6 0 0 172.16.141.1:7005 :::* LISTEN
tcp6 0 0 172.16.141.1:43991 172.16.141.1:7001 ESTABLISHED
tcp6 0 0 172.16.141.1:7005 172.16.141.1:46728 ESTABLISHED
tcp6 0 0 172.16.141.1:7001 172.16.141.1:43991 ESTABLISHED
tcp6 0 0 172.16.141.1:46728 172.16.141.1:7005 ESTABLISHED
tcp6 1 0 172.16.141.1:43999 172.16.141.1:7001 CLOSE_WAIT
udp 0 0 172.16.141.1:137 0.0.0.0:*
udp 0 0 172.16.141.1:138 0.0.0.0:*
Port 80 is not being used by the IP. Am quite lost at the moment on how to troubleshoot this problem.
Appreciate any advice offered. Thanks in advance.

There's not much benefit to having 2 instances on the same machines vs having one instance on that machine. Putting a load balancer in front of a machine with 2 hosts only helps you when you lose a mgd server - but not when you lose an entire machine ( since both mgd servers go away too )
Consider:
Mgd Server A on machine myHost1 with java memory 512m/512m
Mgd Server B on machine myHost1 with java memory512m/512m
vs
Mgd Server A on machine myHost1 with java memory 1024m/1024m
vs
Mgd Server A on machine myHost1 with java memory1024m/1024m
Mgd Server B on machine myHost2 with java memory 1024m/1024m
The first config is your current situation. Your two mgd servers are fighting each other for processing time & memory on that machine. They can't use the same ports, so how does a user decide which port to use when they access your application?
The second config combines their resources into one mgd server
The third gives you load balancing ability - you can survive the loss of a machine. Also note that since the 2 instances are on DIFFERENT machines, they CAN use the same non-SSL and SSL ports.

Server Debug Permission denied

I upgraded to CF8 and now when using the "Server Debug"
feture in Dreamweaver 8 I get an error. I can skip the error and
everything seems ok. It is just such a pain to get the error
message each time I start a debug session.
The error is:
The following error has occured while connecting to the
ColdFusion Server:
Permission denied for the requested operation.
Each time I make the error occure an entry is placed in the
ColdFusion Runtime log:
user RDSServlet: Permission denied for the requested
operation
I am running on MS IIS on a windows XP pro

Try turning on logging.
I typically edit /etc/syslog.conf and add an entry
local7.info;local7.debug /var/log/sshd
ensuring the entries are tab delimited.
Then
touch /var/log/sshd
Edit /etc/ssh/sshd_config and change
SyslogFacility auth
LogLevel info
to
SyslogFacility LOCAL7
LogLevel debug
Restart everything:
svcadm restart system-log
svcadm restart ssh

FTP - Permission Denied

Can anyone help. I have recently set up file sharing on a Mac server. I have set both my internal hard drive and external hard drive as share points. I can navigate the external one fine but when I try and navigate the internal one I get the error:
NOOP
200 NOOP command successful.
CWD /OS X/Applications
550 /OS X/Applications: Permission denied.
Can anyone help?

>
pawan kumar wrote:
i m getting output XML file in my system.but i tried with directly one to one mapping in message mapping, now i did some modification in Message mapping like i concatenate name by X in message mapping and in description i passed ZSUBHODIP as constant then in output i am not getting concatenateed value and constant ZSUBHODIP in name and description.
Hi,
Did you activate the message mapping after modification ??
If yes, test the mapping in test tab and let us know the exact error.
Regards,
Chandra

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

Some files never getting transferred to our FTP Server

We are moving configuration changes from one instance to another using 'Manage Implementation Projects' functionality. This PeopleTools functionality creates DM scripts to transfer functionality like Billing, Contracts, etc to another instance when you click 'Export'
It is supposed to send the scripts to 'FTP Server > psdata > PSFILEDIR' on a Windows system in Financials 9.1 using PT 8.53.04. We constantly get a 'Permission Denied' from this process when trying to do this.
This problem happens in all DEV instances, yet the process works fine in the Prod instance. I have examined the permissions in the PSFILEDIR and compared them in DEV and PROD and find no differences

I guess you didn't like my last answer. So I'll try again. First off, forget FTP. We don't even care about FTP and adding it to the Title of the question just confuses things and maybe gets you less responses. In production, does this open a Dialog box/Save window when the export finishes?
My assumption is that you have the variable PS_FILEDIR set to \\s-wpstbftp1\s$\psdata\PSFILEDIR for the app server. Is that true?
You are failing on line 10 which is
&PROJECT_FILE = GetFile(&FILENAME, "W", %FilePath_Relative);
The PSAPPSRV process is trying to open a file in write mode. It's using Relative Path which appends &FILENAME to the path which is determined by either PS_FILEDIR or PS_SERVDIR. This part of the code is not even the part where the file is supposed to be placed at a final destination. This is very initial step in creating the file, nothing is being written yet. The PSAPPSRV process at this point knows nothing about FTP or other network transfer protocols, it simply knows that it should use \\s-wpstbftp1\s$\psdata\PSFILEDIR as the path. To the PSAPPSRV process this is a path that is locally available on the server,wWhen the system call comes through to the OS to attempt to open this file, the operating system is what allows this to seamlessly connect to a network resource.
There are two potential points where for this and they both relate to the user running the PSAPPSRV process.
You are using the Admin share for the S: drive on s-wpstbftp1. This means any connection to this PATH must be made as a user that is an Administrator on server s-wpstbftp1.
The PSAPPSRV processes must be running as a user that is an Administrator on the other server. This requires configuring the Oracle ProcMGR Windows service to run as a user that has access to the resources in question.
So to fix this you need to look at the ProcMGR service and set it to run as an Administrator user from s-wpstbftp1. This may require additional tasks such as setting up that user on the PeopleSoft server. Use task manager to look at what user is running the PSAPPSRV processes and make sure it's the user you need it to be.
In my humble opinion though, this is bad configuration:
You shouldn't be using Admin shares
I don't like relying on remote server paths that aren't redundant storage devices (NAS or SAN). What if this server is down and other processes need to use this path?
You appear to be expecting this file at a location where it is created for further processing by the code, not the final destination. The file is intended to be downloaded by the user. I don't know why the developer decided to leave the file on the file system, but they may decide to clean up after themselves or change how this works in the future. The file is created, inserted into the database, then read from the database, sent to the user, and deleted from the database. The code calls DetachAttachment which the PeopleCode Language Reference book says:
Use the DetachAttachment function to download a file from its source storage location and save it locally on the end-user machine. The file is sent to the browser with appropriate HTTP headers to cause the browser to display a save dialog box to the user.

SAP ROUTE PERMISSION DENIED

Hi Experts,
When i try to logon SAPNET from T/Code OSS1 its througing error as
"sapsrv2a: route permission denied(12.34.23.5 to oss1 sapdp01)
Location SAPoruter 37.15 on sapserv2a
Component NI
Release 640
Version 37
Return Code -93
Counter 5
Kindly suggest any solution for this problem
Thanks in Advance,
Ramamurthy

HI
I have this error too if I try to logon to sapnet with OSS1 transaction.
you must logon to sapnet trought internet explorer http://service.sap.com
Note 33135 - Guidelines for OSS1
Note Language:      Version: 15     Validity: valid since 30.06.2006
PDF     Download Corrections     Compare Versions     SSCR
     Go to SAP Note: Display
Content: Summary | Header Data | Releases | Related Notes
Summary
Symptom
You are using transaction OSS1 to establish a remote connection.
Other terms
OSS1, RFC connections to SAPNet - R/3 Frontend, SAPOSS, OSS_RFC, SAProuter
Reason and Prerequisites
Remote connection to SAP, R/3 system
Solution
On April 03, 2006, SAPNet - R/3 Frontend was deactivated as a user interface. SAPNet - R/3 Frontend, which was introduced in 1995 as SAP's Online Service System (OSS), was SAP's first and, for a long time, its only support system, which customers worldwide accessed using transaction OSS1.
Today, the SAProuter connection via transaction OSS1 continues to be used for the following RFC connections:
- Transfer of EarlyWatch Alert data
- Exchange of data using the SAP Notes Assistant
To install and configure this transaction, proceed exactly as follows:
1. Making the technical settings for OSS1
You must configure transaction OSS1 before you can use it. Choose "Parameter" from the menu bar (-> Techn. Settings) and choose "Change".
The technical settings for transaction OSS1 are set by default to Walldorf (sapserv3) with the IP address 147.204.2.5. If this address does not correspond with the entry in your host file, choose the sapserv3 IP address that is valid for you by choosing the menu option "SAPRouter at SAP -> Walldorf".
Furthermore, enter your local SAPRouter information in the "SAPRouter 1" fields. Now save the settings.
After making these changes, the screen for the technical settings should be as follows:
Router data for the logon to SAPNet - R/3 Frontend
-Customer SAPRouters----
-SAPRouter 1----    -SAPRouter 2----
Name         my_saprouter
Name
IP Address   x.x.x.x
IP Address
Instanc No. 99
Instance No.
-SAPRouter and OSS Message Server at SAP----
-SAPRouter at SAP----    -OSS Message Server----
Name          sapservX
Name          oss001
IP Address    x.x.x.x
DB Name       O01
Instance No. 99
Instance No. 01
NOTE:
Replace sapservX with the following values:
sapserv1 (194.117.106.129) connection via Internet VPN
sapserv2 (194.39.131.34) connection via Internet SNC
sapserv3 (147.204.2.5)    for customers with connection to Germany
sapserv4 (204.79.199.2)    for customers in America
sapserv5 (194.39.138.2)    for customers with connection to Japan
sapserv6 (194.39.139.16) for customers in Australia and New Zealand
sapserv7 (194.39.134.35)   for customers in Asia
Choose "Start Logon to SAPNet - R/3 Frontend". If the system issues message S1 452, there are errors in the operating system configuration. In this case, see appendix A.
When you install an access authorization file "saprouttab", you should ensure that all of your front ends and R/3 servers can establish a connection to sapserv3, service sapdp99. Appendix E contains examples of saprouttabs. For more information on the SAPRouter, refer to the SAPRouter documentation (Note 30289).
Try it again until the dialog box "Please select a group" appears. If the dialog box "Please select a group" is displayed, the configuration for transaction OSS1 is correct. You can then proceed with the next section.
NOTE:
When you try to log on to SAPNet - R/3 Frontend, the system issues an error message indicating that you are no longer allowed to log on to SAPNet - R/3 Frontend.
2. Further questions?
As soon as you have carried out the steps described above, transaction OSS1 should connect you to the most efficient SAPNet - R/3 Frontend application server.
If you have further questions or problems, the file entitled "OSS1. TroubleShooting" contains additional information. If you have a problem that you cannot solve, contact our hotline: 0180/5 34 34 3-3.
Appendix A
If message S1 452 appears when you try to log on to SAPNet - R/3
Frontend with transaction OSS1, there is an incorrect setting somewhere (either in the technical settings for OSS1 or at operating system level).
To find out why the connection to the message server was unsuccessful, choose Tools (Case, Test ( Developer trace (transaction ST11). The trace contains an entry for dev_lg. This file contains the error log. The LOCATION line, if available, contains the host on which the error occurred. The problem description is found in the ERROR line. If you cannot find the entry dev_lg, check whether the program "lgtst" exists (see appendix B).
Examples of the contents of dev_lg:
ERROR       partner not reached (host abc.def.gh.i, service sapdp99)
TIME        Thu Aug 10 09:17:57 1995
RELEASE    21J
COMPONENT   NI (network interface)
VERSION    15
RC          -10
MODULE      niuxi.c
LINE        773
DETAIL      NiPConnect
SYSTEM CALL connect
ERRNO      239
ERRNO TEXT Connection refused
COUNTER    1
Here, the system could not reach the SAPRouter. For example, no SAProuter could be found under service 99 (port 3299) on the host with the IP address abc.def.gh.i. The SAPRouter process does not work or the IP address was not configured correctly in OSS1.
ERROR      service 'sapdp99' unknown
TIME        Thu Aug 10 09:22:00 1995
RELEASE    30A
COMPONENT   NI (network interface)
VERSION    17
RC          -3
MODULE      niuxi.c
LINE        404
DETAIL      NiPServToNo
SYSTEM CALL getservbyname
COUNTER    1
This message indicates that the service sapdp99 was not entered in /etc/services. Add the entry in /etc/services. This must be available on all R/3 servers and front ends.
LOCATION    SapRouter on abc.def.gh.i
ERROR      route permission denied (XXXXXXXX to sapservX, sapdp99)
TIME        Thu Aug 10 09:37:44 1995
RELEASE    30A
COMPONENT   NI (network interface)
VERSION    17
RC          -94
MODULE      nixxrout.c
LINE        1426
COUNTER    1
The file saprouttab, which contains the valid connections, is not correct. The SAPRouter on the host abc.def.gh.i does not set up the connection to sapservX. Check the SAPRouter file saprouttab. This should contain every R/3 server and frontend (see also appendix E).
LOCATION    SapRouter on abc.def.gh.i
ERROR      internal error
TIME        Thu Aug 10 10:50:18 1995
RELEASE    21J
COMPONENT   NI (network interface)
VERSION    15
RC          -93
MODULE      niuxi.c
LINE        773
DETAIL      NiPConnect
SYSTEM CALL connect
ERRNO      242
ERRNO TEXT No route to host
COUNTER    1
This error message indicates that the host abc.def.gh.i cannot process the IP address of the next host configured in OSS1. If the SAPRouter error message appears and the next host is sapservX, check the address for sapservX. OSS1 is delivered with the default settings sapserv3 and IP address 147.204.2.5. Customers in the U.S.A. are normally connected to sapserv4, IP address 204.79.199.2. If required, change the technical settings of OSS1 accordingly.
ERROR      internal error
TIME        Thu Nov 23 00:11:20 1995
RELEASE    21J
COMPONENT   NI (network interface)
VERSION    15
RC          -1
COUNTER    1
This message shows that the instance number entered does not agree with at least one of the technical settings for the SAPRouter defined in OSS1. The default for the instance number of the SAPRouter is 99. Under no circumstances should you enter the instance number of your R/3 system for the SAPRouter. You need to specify instance number 99 for sapservX. Otherwise, it is not possible to log on to SAPNet - R/3 Frontend.
LOCATION    SapRouter on sapservX
ERROR       route permission denied (XXXXXX to oss002, sapmsO01)
TIME        Mon Nov 27 19:25:54 1995
RELEASE    30A
COMPONENT   NI (network interface)
VERSION    15
RC          -94
MODULE      nixxrout.c
LINE        1390
COUNTER    1
An incorrect server was entered as message server 001, in this example, the server oss002. The message server for O01 is oss001. Change the technical settings for transaction OSS1 accordingly.
Appendix B (for Windows NT only)
Change to the directory "\usr\sap\<SID>\SYS\exe\run" and search for the program "lgtst.exe". If you cannot find it, or if the length of this file is not exactly 640216 bytes, import the program "lgtst.exe" from sapservX via ftp:
> ftp sapservX
Connected to sapservX.
220 sapservX FTP server (Version 1.7.194.2 Wed Sep 8 17:23:04 GMT 1993) ready.
Name: ftp
331 Guest login ok, send ident as password.
Password: <Your_customer_number>
ftp> cd dist/permanent/OSS1/lgtst.exe
250 CWD command successful.
ftp> binary
200 Type set to I.
ftp> get lgtst.exe
150 Opening BINARY mode data connection for lgtst.exe (640216 bytes).
226 Transfer complete.
640216 bytes received.
ftp> bye
Copy this file into the aforementioned directory.
Appendix C
The messages from transaction OSS1 (error messages and information) are given in the following list. Each message is described briefly.
|No.| Message Text
|450| Maintain technical settings first.
|452| Unable to connect to SAPNet - R/3 Frontend message server.
|454| E: Unable to start SAPGUI.
|455| SAPGUI was started.
|456| Specify a server name.
|457| Specify an IP address.
|458| Specify an instance number.
|459| Specify a database name.
|460| No authorization to log on to SAPNet - R/3 Frontend.
|461| No authorization to maintain technical settings.
|462| E: RFC destination could not be generated
Number 450: Maintain technical settings first
You can only log on to SAPNet - R/3 Frontend if the technical settings
are maintained. The technical settings determine the network path from the customer R/3 system to the online service system.
Number 452: Unable to connect to SAPNet - R/3 Frontend message server.
This message appears if the connection to the SAPNet - R/3 Frontend message server was not possible (system name O01, server oss001). There can be different reasons for this (see appendix A).
Number 454: E: Unable to start SAPGUI.
Transaction OSS1 could start the SAPGUI (not SAPTEMU), either because the program does not exist in the path given, or because the execute permission is not set correctly. Check whether the SAPGUI exists; SAPTEMU alone is not sufficient.
Number 455: SAPGUI was started.
This is not an error message. It merely informs you that an additional SAPGUI was started to establish a connection to SAPNet - R/3 Frontend.
Number 456: Specify a server name.
The server name was omitted from the technical settings.
Number 457: Specify an IP address.
The IP address was omitted from the technical settings.
Number 458: Specify an instance number.
The instance number was omitted from the technical settings.
Number 459: Specify a database name.
The database name for the Online Service System (001) was omitted from the technical settings.
Number 460: No authorization to log on to Online Service System
You do not have authorization to call transaction OSS1. Up to Release 2.2F: The authorization S_TSKH_ADM is checked for value 1. After Release 2.2F: For transaction OSS1, there are two special authorization profiles (see appendix D).
Number 461: No authorization to maintain technical settings.
You do not have the authorization to maintain the technical settings (see appendix D).
Number 462: E: RFC destination could not be generated.
In Releases 2.2, you can ignore this message. When saving the technical settings, an attempt is made to generate the RFC destination SAPOSS. The length of an RFC destination is limited in 2.2, and the maximum length was exceeded by the parameters of the technical settings.
Appendix D
As of Release 2.2F, there are two different authorization profiles for transaction OSS1: S_OSS1_START and S_OSS1_ADMIN.
S_OSS1_START authorizes you to call transaction OSS1 and to log on to the Online Service System. In addition, S_OSS1_ADMIN contains the
authorization to maintain the technical settings for the transaction.
The technical settings of OSS1 must be made at least once. Therefore, add S_OSS1_ADMIN to your user profile, log off, and then log on again afterwards.
Appendix E
Prerequisites:
(A TCP/IP connection can be established between the SAProuter on
the customer system and the SAProuter on sapserv3 in Walldorf.
(The SAProuter process must be started on the server that is registered
with SAP:
saprouter -r -R saprouttab &
Example of the "saprouttab" file with minimum configuration:
saprouttab - Example
Allows connections from the entire customer network to sapservX
and therefore to the Online Service System via SAProuter port 3299.
P      *      sapservX    sapdp99         *
Allows connections from sapserv3 to the entire customer network,
for example for EarlyWatch or First Level Support.
P   sapservX      *          *            *
Header Data
Release Status:     Released for Customer
Released on:     30.06.2006 09:13:57
Priority:     Correction with high priority
Category:     Consulting
Primary Component:     XX-SER-NET Network connection
Antonio.
Edited by: Antonio Voce on May 22, 2008 5:07 PM

"Access Denied" Error After Server Change

I have a number of hosting clients that use Contribute. Since
I upgraded my hosting server, they are unable to connect - or more
accurately, they can connect, but if they try to edit a page they
get a "Access Denied. The file may not exist, or there may be a
permission problem." error. This did not occur during my last
server upgrade - all Contribute connections worked just fine.
All settings such as username, password and server addresses
remain the same including the FTP server settings. I can create a
new connection from scratch, but anyone with a key generated by
their web developer is out of luck. I can send out these new keys
I've created and they seem to work just fine.
What could possibly cause this error, and is there any other
way to correct the issue beyond regenerating keys and sending them
to everybody?

Do u mean Contrinute? Captivate is not being used. It is not
possible to rename the file because these files are in production
and it would take a lot of work to go through renaming files for a
whole website.

Unable to copy current-config from IPS 4240 to FTP server

I am in the process of upgrading our Signature File at a client site where there is a 4240 installed.
The readme file for Signature S353 indicates that a copy of the running configuration should be saved away.
I have FTP running on my desktop.
I am entering the following command on the IPS at CLI:
bhiips# copy current-config ftp://192.168.5.189
where I am then prompted for my username, then filename, then password.
I watch as the IPS indicates "Generating current config".
The log output of the FTP (Filezilla) shows my FTP connection successful, but then it bombs. Here is an excerpt:
00151) 08/27/2008 15:45:47 PM - (not logged in) (192.168.10.53)> Connected, sending welcome message...
(000151) 08/27/2008 15:45:47 PM - (not logged in) (192.168.10.53)> 220-FileZilla Server version 0.9.24 beta
(000151) 08/27/2008 15:45:47 PM - (not logged in) (192.168.10.53)> 220-written by Tim Kosse ([email protected])
(000151) 08/27/2008 15:45:47 PM - (not logged in) (192.168.10.53)> 220 Please visit http://sourceforge.net/projects/filezilla/
(000151) 08/27/2008 15:45:47 PM - (not logged in) (192.168.10.53)> USER Kevin
(000151) 08/27/2008 15:45:47 PM - (not logged in) (192.168.10.53)> 331 Password required for kevin
(000151) 08/27/2008 15:45:47 PM - (not logged in) (192.168.10.53)> PASS ***
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> 230 Logged on
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> PWD
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> 257 "/" is current directory.
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> EPSV
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> 229 Entering Extended Passive Mode (|||2125|)
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> TYPE I
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> 200 Type set to I
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> STOR current
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> 550 Permission denied
(000151) 08/27/2008 15:45:47 PM - kevin (192.168.10.53)> disconnected.
What could be the problem here? I checked the Windows Firewall on my workstation at 192.168.5.189,but it is turned off. I am not sure why I cant save the config away.
It is holding me up from moving forward with the upgrade to Sig 353.
thx

Have you checked permissions on your FTP server to see if a client is able to PUT a file onto your FTP server.
Try connecting from a separate windows PC to your FTP server and login with the userid and password you are using in your copy command. And then try to push a file with a similar name on to your FTP server.
It could be that the FTP server is not configured to allow that userid to put a file on the server.
When you try the above test try and use an FTP client that supports Passive mode. There might be a problem with passive mode on your FTP server.
You might also try running another test from the sensor, but this time instead of copying the configuration try copying the license file from the sensor to your ftp server.

PERMISSION DENIED IN FTP SERVER

Similar Messages

Maybe you are looking for