Logon to SAPNet

Hello,
I installed SAP NW 7.0 Trial Version. I want to get the access key for developer user to create the new programs. But after click the button "logon to SAPNet" always "unable to connect to SAPNet message Server" display.
Please help me, how to get the access key for developer user? Otherwise how can new programs be created?
thanks a lot
Lei
Edited by: Lei Meng on Jul 6, 2008 12:38 AM

Hello,
Thankyou for giving me your precious time.
When i have try to check the registration of my public IP with SAP in the servive market place.
It will show the authorisation error.
1.Please tell me how can i overcome by this authorisation error.
2. Please suggest me if there is any other way to check my public key registration to SAP.
3. I want to configure the maintainance optimiser in the solman but SAPOSS,SAPOSS,SDCC_OSS RFC is fail.please tell me its solution.
Regards
Abha Sood

Similar Messages

Problem to Logon to SAPNet

Hello Experts,
I am facing the problem in logon to SAPNet in solution manager.
I have set the parameter for tha sapserv2 with the ip 194.39.131.34.
But When I try to logon to the SAPNet,I will shwo the massage.
Unable to connect with SAPNet logon message server.
sapserv2a:-route permission denied.
Return code is -93.
Please suggest me its solution.
Regards,
Abha Sood

Hello,
Thankyou for giving me your precious time.
When i have try to check the registration of my public IP with SAP in the servive market place.
It will show the authorisation error.
1.Please tell me how can i overcome by this authorisation error.
2. Please suggest me if there is any other way to check my public key registration to SAP.
3. I want to configure the maintainance optimiser in the solman but SAPOSS,SAPOSS,SDCC_OSS RFC is fail.please tell me its solution.
Regards
Abha Sood

Solution manager Remote Connection issues

Hi
I'm currently in the process of setting up Solution Manager 7.1 on windows Server 2008r2 using central system.
I did the prerequisite check & the Solman installation and i'm actuallly working on the post-installation steps.
I'm experiencing difficulty with the step : "Configure Remote Connection to SAP".
I followed the informations provided on :   http://service.sap.com/remoteconnection
In the technical prerequesite you have to set up a connection to sap support.
So i have to choose a connection type : I selected Internet connection so my first question is : do we need "VPN with SNC" or "VPN OR SNC" ?
I personnaly understood VPN or SNC.
So from here i decided to use SNC.
The first step was to set up & configure the SAProuter. I decided to do it on an another computer on the same domain ( not on the same computer where Solution Manager is installed ) but i'm not sure it is necesary
I assume I can install Saprouter on the same location as the Solution manager? do you recommend it ?
The Basic Functions testing with niping is working.
The next step is : "establish Internet Connections"
So now i can choose between SNC or VPN : my goal is to establish the connection as fast as possible.
I actually don't have a switch available ( i can get one if necesary but time is running ... ) so i'm opting for the SNC solution.
I tryed to get the certificate for the saprouter but i don't have a register SAProuter, but when i opened a customer messager for component XX-SER-NET, SAP answered about the impossibility to access SAP service Backbone with an SNC , saying that i will need to register a VPN site to site connection to SAP => i don't get it .... Can someone explain it to me ?
So please can one of you guru's tell me how to set this remote connection :
-which materials ( server / switch / firewalls ) ?
-where to get the right documentation ?
-What about DMZ ?
-I have a single IP Address is that enough ? ( setting up nat for port 3299 )
- do i have to contact a service provider ?
My idea was initially to set up the SAProuter on the same computer as the SOLMAN setup & use SNC communication to communicate with SAP but it doesn't seems that easy. Do i need separate installation for Saprouter <=> Solution Manager. ?
What's the minimal infrastructure to establish this connection ?
In addition to that, after configuring the SAProuter, i had trouble with the SAPMMC : on my system , on the instance 0 , the process disp+work.EXE won't run ( yellow light )and i can't find where i made a mistake if you have suggestions ...
Really need your help, i'm on a short deadline ... Any help, even incomplete, would be appreciated.
Thanks a lot.

Thx for the answer.
I actually managed to register my saprouter with SAP and was granted with CN/OU & connection informations.
I followed this guide : http://service.sap.com/saprouter-sncdoc with the addition of this guide : http://wiki.sdn.sap.com/wiki/display/Basis/SAProuterviaSNC.
My first issue : I'm running with a Windows server 2008 r2 enterprise edition 64 bits with a processor Intel Xeon 2.4ghz ( dualcore). so i decided to use the crypto folder "nt-x86_64"
For the environment variable i set as System variables SECUDIR = C:\usr\sap\saprouter and SNC_LIB = C:\usr\sap\saprouter\nt-x86_64\sapcrypto.dll
The generation/install of the certificate is alright ( sapgenpse get_my_name -v -n Issuer is OK )
using the command :saprouter -r -K "p:CN=mycn, OU=myOUnbr, OU=SAProuter, O=SAP, C=DE" i have
I get the following message : trc file     dev_rout
                                                no ligging active
Its strange cause it looks like its running but when i check the services running on windows saprouter isn't started .... How to know if SAProuter is running right ?
If i folow the SAP procedure : Step 3 : test of the ip connection by the customer : SAP Remote Services : technical preparation ( see SAP Note 812386 ) : it's ask in the note to implement note 766505 via SNOTE : i get the following error msg : Error in remote connection to destination SAPOSS : Error when opening an RFC connection ( LB: Hostname or service of the message server unknown#DEST = SA
What's wrong ?
If i use T oss1 in parameter => technical setting => i set my saprouter info in SAProuter 1 ( at customer site ) with instance no. 99 and if SAProuter and SAPNet Message Server at SAP i put the following : Name : sapserv2 / IP Address 194.39.131.34 intance no. 99 and message server name oss001/ DB Name 001/ Instance no.01.
When trying to "Logon to SAPNet" i have an error Unable to connect to SAPNet message server ( default connection will be used ... )
and followed by the error screen : "partner '80.15.173.168:sapdp99' not reached WSAECONNREFUSED : Connection refused. do you want to see the detailed error description ? "
Details : module nixxi.cpp / line 3286 / Method : NipConnect2:80.15.173.168:3299 / Return code : -10 / System call : connect / Error No : 10061 / Error Text WSAECONNREFUSED: Connection refused / Counter : 10
Any idea ?
when doing niping.exe -c -H /H/mylocalSR/H/194.39.131.34/H/194/39.131.34 i obtain :
Wed Dec 07 21:20:09 2011
connect to server o.k
Wed Dec 07 21:20:09 2011
send and receive 10 messages (len 1000)
times -
avg   122.148 ms
max   193.731 ms
min   81.564 ms
tr 15.990 kB/s
excluding max and min :
av2   118.273 ms
tr2   16.514 kB/s
Is it the expected output ?
I've maintained system data in service.sap.com/system-data ( selecting the sap router ) then i tryed to use the SAP service connection, downloaded the .exe but i can't find the stfk.oez. I realized that in my maintain connection screen i have no space for entering any routestring. Seems wrong ?
Do i have to use the SAO?
i've made nat redirection from my router as this : from my public ip to my lan ip ( 192.168.x.x) what should i enter in the routestring : /H/public or lan or hostname ?/S/3299 ?
Hoping you can help me ! ( the goal of all this is to set up RFC connection for postinst step of Solution manager ).
Edited by: BLANCHARD Guillaume on Dec 7, 2011 10:47 PM

TMS configuration

Hi,
I'm in the process of installing solution manager. I've managed to run saprouter & to logon to sapnet. Now i'm having a hard time configurating the TMS.
My conf is the following Solution manager & SAProuter are both installed on the same machine. I want my solution manager to be the transport system.
I use STMS, then i get prompted for Description, transport domain name & description.
After fulfilling i can either save or do "other configuration" => there i'm asked a
-Target host :
-System number :
-User : TMSADM
Can i have some info about target host & system number : target host would be my solman installation so should i enter SOLUTIONMAN-SRV as target host & system number 00?
If i don't enter those information & continue with the basic entries, i
- Check the RFC connection : working fine
-In overview=>system when checking the Communication tab, in transport domain my controler is my solman system, but there is no backup or workflow engine : what should i enter?
In RFC Adress i have the user TMSADM , but no snc name : somehting to do here ? The snc active is unclickable : but i'm actually using SNC so should i change something ?
How to check if the TMS configuration is stored in the transport directory?
How to check the transport profile tp is generated ?
Can't access the worklist saying "Workflow not active" : some insights ?
In overview=> transport routes => Configuration => Standard configuration : i can't select "single system" but if i follow the SAP documentation i'm supposed to have a Single system configuration.
Hope you can help me !:

Hi Blanchard,
As per your requirement you have to enter the following entries in the TMS Conf.
-Target host :<HOSTNAME of the TARGET SYSTEM>
-System number :<SYSTEM NUMBER OF THE TARGET SYSTEM>
-User : TMSADM<STANDARD USER>
Target Host and the System Number should be the System which you want to target,
i.e As you are Configuring TMS in Solman so your Target Host and the System number should be your ECC or SRM or whatever
Systems which are in Landscape.
The Path of the Transport Profile which is being generated is in E:\usr\sap\trans\bin--> TP_DOMAIN_SID.PFL
And If Any Doubts regarding this kindly go through the link.
[http://help.sap.com/printdocu/core/print40b/EN/pdf/bcctstms/bcctstms.pdf]
Hope this will help you out
Thanks & Regards
Ajitabh

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

Sapserv1:route permission denied (216.53.212.149 to 147.204.100.55, sapdp01

Hi,
We are having issue with our sapnet connection. When ever I am trying to connect to sapNet im getting this error. The following is the procedure i m doing
1. t-code oss1
2. logon to SAPNet
3. selecting the group PUBLIC
then I m getting thid error
sapserv1:route permission denied (216.53.212.149 to 147.204.100.55, sapdp01)
Please reply me back ASAP as this is urgent issue. I will appriciate ur help n sugsestions.

Hi,
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.
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.
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.
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.
I hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

SAPROUTER - route permission denied

Hello.
I'm trying to connect my ERP to SAPNet but i'm getting troubles.
This is the error.
[Thr 4812] * LOCATION    SapRouter on sapserv2a
[Thr 4812] * ERROR       sapserv2a: route permission denied (80.37.122.205 to oss001,
             sapmsO01)
[Thr 4812] *
TIME        Mon Jun 25 10:24:43 2007
[Thr 4812] * RELEASE     620
[Thr 4812] * COMPONENT   NI (network interface)
[Thr 4812] * VERSION     36
[Thr 4812] * RC          -93
[Thr 4812] * COUNTER     19
[Thr 4812] *
[Thr 4812] *****************************************************************************
I have the 3299 port open for the saprouter host.
My saprouter is registered in SAP, i have my certificated and i applied correctly on my saprouter.
My routerttab permits all traffic. P * * * *
I'm configuring my connection on the SM59 transaction.
Target system: OSS
Msg. Server: /H/194.39.131.34/H/OSS001
Language: EN
Client: 001
User: My SSO number
PWD: My sso password.
Any idea?
Thanks in advance.

Hi,
As of April 3rd, 2006 the SAPNet R/3 Frontend will be not available for
Support applications anylonger. It will be substituted by both supports Platforms,
SAP Support Portal and SAP Solution Manager
So OSS1 -->Logon to SapNet (Does not work).
You can maintain the IP's and Other Information in OSS1 -->Paramter ->Technical Settings. which will modify the "SAPOSS" RFC destination.
Thanks,
Tanuj

Profiles for Basis Admins

Does anyone have a list of transactions that would be considered adequate for a basis administrator on a production system, which would allow them to do all the work they may need to without logging in with a sap_all id?
What is the best practice for access for basis in production?
Lee

Hi Lee-
I can understand where are you coming from :). You needed the list of all possible basis tcodes in production environment rather adopting strenuous task of deriving and identifying all required functionality from SAP Standard role template for basis. Not an issue
You can refer the tcodes listed below in production environment. It includes all required for regular support, monitoring & performance analysis.
SSO2      Workplace Single Sign-On Admin.
STRUSTSSO2      Trust Manager for Logon Ticket
BD82      Generate Partner Profiles
SMT2      Trusting systems (Display <->Maint.)
SPAU      Display Modified DE Objects
SDCCN      Service Data Control Center
SLG1      Application Log: Display Logs
SGEN      SAP Load Generator
STMS_MONI      TMS Import Monitor
STMS      Transport Management System
SCOOL      COOL Repository
PFUD      User Master Data Reconciliation
SMMS      Message Server Monitor
SICK      Installation Check
SMICM      ICM Monitor
SE38      ABAP Editor
AL04      Monitor call distribution
AL08      Users Logged On
AL11      Display SAP Directories
AL12      Display table buffer (Exp. session)
AL13      Display Shared Memory (Expert mode)
AL15      Customize SAPOSCOL destination
AL16      Local Alert Monitor for Operat.Syst.
BD21      Select change pointer
BD50      Activate Change Ptrs for Mess. Type
BD51      Maintain function modules (inbound)
BD52      Activ.change pointer per chng.doc.it
BD54      Maintaining Logical Systems
BD64      Maintenance of Distribution Model
BD97      Assign RFC dest. to Logical Systems
CK11      Create Product Cost Estimate
DB01      Analyze exclusive lockwaits
DB02      Tables and Indexes Monitor
DB03      Parameter changes in database
DB12      DBA Backup Logs
DB6BACKHIST      DB6: DBA Planning Calendar
DB6CLP      DB6: Command Line Processor
DB6COCKPIT      DB6: DBA Cockpit
DB6EXL      DB6: Analyze Exclusive Lock Waits
DB6PERF      DB6: DB2 UDB Cockpit Performance
DB6SPACE      DB6: Space Analysis
FTXP      Maintain Tax Code
KOSRLIST_PR      Projects/Nets: Coll. Displ.SettRules
LBWE      LO Data Ext.: Customizing Cockpit
LSMW      Legacy System Migration Workbench
OS01      LAN check with ping
OS03      O/S Parameter changes
OS04      Local System Configuration
OS05      Remote System Cconfiguration
OS06      Local Operating System Activity
OS07      Remote Operating System Activity
OSS1      Logon to SAPNet
OY05      Factory calendar
RBDMIDOC      Variant for RBDMIDOC
RSA7      BW Delta Queue Monitor
RZ01      Job Scheduling Monitor
RZ03      Presentation, Control SAP Instances
RZ04      Maintain SAP Instances
RZ10      Maintain Profile Parameters
RZ11      Profile Parameter Maintenance
RZ12      Maintain RFC Server Group Assignment
RZ20      CCMS Monitoring
SA38      ABAP Reporting
SAINT      Add-On Installation Tool
SALE      Display ALE Customizing
SASAPIMG      Call Up Project IMG
SBIW      BIW in IMG for OLTP
SCON      SAPconnect - Administration
SCOOLTOOL      COOL Tools
SCOT      SAPconnect - Administration
SCU0      Customizing Cross-System Viewer
SCU3      Table History
SE03      Transport Organizer Tools
SE06      Set Up Transport Organizer
SE12      ABAP/4 Dictionary Display
SE13      Maintain Technical Settings (Tables)
SE15      ABAP/4 Repository Information System
SE18      Business Add-Ins: Definitions
SE37      ABAP Function Modules
S_TABU_DIS Display Tables (customize it to ztcode)
SCC4 (customize it to ztcode)
SE63      Translation: Initial Screen
SE11      ABAP Dictionary
SE11_OLD      ABAP/4 Dictionary Maintenance
SE80      Object Navigator
SE81      Application Hierarchy
SE82      Application Hierarchy
SE84      R/3 Repository Information System
SE93      Maintain Transaction Codes
SESSION_MANAGER      Session Manager Menu Tree Display
SICF      HTTP Service Hierarchy Maintenance
SM01      Lock Transactions
SM02      System Messages
SM04      User List
SM12      Display and Delete Locks
SM13      Administrate Update Records
SM14      Update Program Administration
SM20      Security Audit Log Assessment
SM21      Online System Log Analysis
SM28      Installation Check
SM35      Batch Input Monitoring
SM36      Schedule Background Job
SM37      Overview of job selection
SM37C      Flexible version of job selection
SM38      Queue Maintenance Transaction
SM49      Execute external OS commands
SM50      Work Process Overview
SM51      List of SAP Systems
SM56      Number Range Buffer
SM58      Asynchronous RFC Error Log
SM59      RFC Destinations (Display/Maintain)
SM61      Backgroup control objects monitor
SM62
SM63      Display/Maintain Operating Mode Sets
SM64      Trigger an Event
SM65      Background Processing Analysis Tool
SM66      Systemwide Work Process Overview
SM69      Maintain External OS Commands
SMEN      Session Manager Menu Tree Display
SMGW      Gateway Monitor
SMLG      Maint.Assign. Logon Grp to Instance
SMLT      Language Management
SMQ1      qRFC Monitor (Outbound Queue)
SMQ2      qRFC Monitor (Inbound Queue)
SMQR      Registration of Inbound Queues
SMQS      Registration of Destinations
SMT1      Trusted Systems (Display <-> Maint.)
SMX      Display Own Jobs
SNL1      Display NLS (character set, lang.)
SNOTE      Note Assistant
SNRO      Number Range Objects
SNUM      Number Range Driver
SO00      SAPoffice: Short Message
SO01      SAPoffice: Inbox
SO02      SAPoffice: Outbox
SO03      SAPoffice: Private Folders
SO04      SAPoffice: Shared Folders
SO05      SAPoffice: Private Trash
SO07      SAPoffice: Resubmission
SO23      SAPoffice: Distribution Lists
SO50      Rules for inbound distribution
SO99      Put Information System
SOST      Overview transmission requests
SP01      Output Controller
SP12      TemSe Administration
SPAD      Spool Administration
SPAM      Support Package Manager
ST01      System Trace
ST02      Setups/Tune Buffers
ST03      Performance,SAP Statistics, Workload
ST03N      R/3 Workload and Perf. Statistics
ST04      DB Performance Monitor
ST05      Performance trace
ST06      Operating System Monitor
ST07      Application monitor
ST10      Table Call Statistics
ST11      Display Developer Traces
ST14      Application Analysis
ST22      ABAP dump analysis
STAD      Statistics display for all systems
STAT      Local Transaction Statistics
SU01D      User Display
SU03      Maintain Authorizations
SU51      Maintain Own User Address
SU52      Maintain Own User Parameters
SU53      Evaluate Authorization Check
SU55      Call the Session Manager menus
SU56      Analyze User Buffer
SUIM      User Information System
S_BCE_68001285      Transaction S_BCE_68001285
S_BCE_68001402      With Unsuccessful Logons
S_BCE_68001418      Act. Grps According to Complex Crit.
S_BCE_68001420      Act. Grps According to Complex Crit.
S_BCE_68001429      Transactions for User
TU02      Parameter changes
USMM      Customer measurement
WE02      Display IDoc
WE05      IDoc Lists
WE07      IDoc statistics
WE08      Status File Interface
WE09      Search for IDoc in Database
WE20      Partner Profiles
WE21      Port definition
WE30      Development IDoc Type
WE46      IDoc administration
WE60      Documentation for IDoc types
WE61      Documentation for IDoc record types
WE63      Documentation
Cheers!
Ashok

SAP Trial version installation/Licensing

Hello there,
I have installed trial version of SAP on my laptop computer and sent the information to SAP at www.sap.com/minisap for extending the license. But I have received very long key back from [email protected] It believe it has to be 24 charaters.
Has anyone seen this problem?
Thanks,
Manoj

Hi,
Just don't change anything, first save that file in your desktop as a notepad. And
To get an SAP License you have to complete the
following steps:
1) Find out the machine on which the SAP message server is running.
2) Get your hardware key by running "saplicense -get"
     on the machine where the SAP message server is running.
3) Logon to SAPnet and send a license request to SAP.
4) On receipt of your license key from SAP, install it
     using "saplicense -install".
     As a more convenient way to install the license please
     use the transaction SLIC in the SAP system.
And
Refer also,
license renewal procedure please
Note: Points always encourage me to reply!!

OSS1 connection failed ,the message means local saprouter timeout

When we testing connection by OSS1, we didn't logon the SAPNet. the error detail means my local saprouter is timeout. But I don't what wrong with my saprouter. becasue we use SM59 to test SAPOSS or SDCC_OSS,the connetion test are all ok.

hello,
pls check if the process saprouter is started on operating system level. If not
you can start it from operating system level. Please use saprouter -help to find
out the syntax. You can see as well in your saprouttab if you specified
the proper connection settings / permits.
Hope this helps.
KR,
andreas

Netmessage server

hi guys,
i am trying to logon to sapnet.Through oss1,in that its telling unable to connect to message server.
for this what i want to do?? anyone can help me??
regards
vijay

Hi Vijay,
Login to OS level goto --> C:\WINNT\system32\drivers\etc\services, open services file with notepad and enter
<b>sapms<SID> 36<INstance no>/tcp # SAP System Message Port</b>
then login to SAP --> oss1 --> parameter --> technical settings --> specify ip adress on user side and SAP side. then try to connect.
Regrds,
suraj

Unbale to conncet oss1

Hi Experts.. when I tried to logon to SAPnet error message popup as below.
Hostname:router permission denied( 192.168.10.24 to 194.39.131.34,sapdp99)
location:sap router 39.1(SP3) on Hostname
component:NI (network interface)
Release :710
version:39
Return Code: -94
Counter:10902
I have checked saposs/sapnet_rfc and sdcc_oss but all connection tests faild.
I have selected in SM59 target host as '/H/172.20.1.100/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001' and
save database as '/H/172.20.1.100/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001'
I have checked all parameters in oss1 also SAP router at sap name:sapserv2/IP:194.39.131.34/instance:99
SAP net message server -name:OSS001/DBname:O01/INSTANCE:01.is it correct? please give me as soon as possible to over come this.
Thanks

I have followed snote-33135 and i got this error message in st11
dev_lg Log:
Display Developer Traces                                                    1
trc file: "dev_lg", trc level: 1, release: "700"
Thu Mar 12 09:05:46 2009
ERROR => NiBufIProcMsg: hdl 0 received rc=-104 (NIEROUT_SNC_FAILURE) from peer [nibuf.cpp    2125]
ERROR => MsINiWrite: NiBufSend (rc=NIEROUT_SNC_FAILURE) [msxxi.c      2480]
ERROR => MsIAttachEx: MsINiWrite (rc=NIEROUT_SNC_FAILURE) [msxxi.c      734]
ERROR => LgIAttach: MsAttach (rc=NIEROUT_SNC_FAILURE) [lgxx.c       3980]
ERROR => LgApplSrvInfo: LgIAttach(rc=LGEMSLAYER) [lgxx.c       1272]
LOCATION    SAProuter 39.1 (SP3) on 'sgbwep01'
ERROR       SNC processing failed:
             SncProcessOutput
TIME        Thu Mar 12 09:02:43 2009
RELEASE     710
COMPONENT   NI (network interface)
VERSION     39
RC          -104
MODULE      nisnc.c
LINE        1108
DETAIL      NiSncIInitHdlSecurity: sncrc=-4;1101694d0
COUNTER     273
please give ur suggestion
Best regards

Setting for SAPNet Logon

dear guru,
can anyone pls let me know the default settings/values for SAPNet Logon... I am trying to connect it through my IDES. but its not working. the default settings maintained here are .....
SAP Router at SAP
Name: sapserv3
IP: 147.204.2.5
Instance no.: 99
SAP Net Message Server
Name: oss001
DB Name: 001
Instance no.: 01

Abishek,
the R/3 logon to the SAP backend system is gone for years so it's not your fault, it's simply not possible.
Markus

SAP GUI Logon

HI,
We are supporting a 2 clients where one has sandboxes and other production system.
Is it possible to keep Sandboxes in one gui and production systems in another logon pad.
I mean i need 2 SAP GUI-logon pad on my desktop where one logon pad must contain only productions systems and another should contain only sand-box systems.
Is it possible? What setting has to be made?
Sugessions and Help is appreciated
Regards,
Magham.

Hi,
Pls check things like
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000659894&_OBJECT=011000358700005431522005E
service.sap.com/sapgui
Eddy
PS. Reward the useful answers and you will get <a href="/people/baris.buyuktanir2/blog/2007/04/04/point-for-points-reward-yourself">one point</a> yourself!

"Logon Not Possible (Error in License Check)" at DR Site

Hi,
I am doing DR ( Disaster Recovery ) Site. I used Tivoli Storage Manager ( TSM ) to take FS Backup & DB Backup.
On the DR site I restore the same backup successfully and the resultant is I am able to run my SAP server.
When I try to connect through SAP Logon. it gives me first screen.
Problem none of the user is permitted to enter except sap*. for other user following message come.
"Logon Not Possible (Error in License Check)".
i know how to apply new license but in requesting permanent license the SAPnet is not asking hardware key.
Best Regards,
Syed Saifuddin
Software Architect ( JEE 5 )
SAP BASIS Administrator

Hi Syed,
Please check the SAP Note
Note 94998 - Requesting license keys and deleting systems.
Also check the sapms<sid> port.
Thanks,
Prabhat

Logon to SAPNet

Similar Messages

Maybe you are looking for