SAP GUI 7.1 not working
Hi
I installed SAP GUI 7.2 and I encountered some issues (another post on this forum). Because of that I decided do uninstall and install 7.1 again with patch 18
What happens is that now, when I install SAP GUI 7.1, and then patch 18 I enter saplogon.exe and it doesn't open!
I tried several times to uninstall and install again and none of the times i managed to open the saplogon
If i install the GUI 7.1 and open saplogon.exe before I install the patch it works ok, but I can't work properly, I keep getting SAP errors.
I also tried to install patch 17 (the version I had working before i installed 7.2) and it also doesn't work now
Is there a way to clean everything SAP related so I can do a fresh install? Could this be caused by remains from previous installations?
And if so, why does the unpatched version work (even if poorly)?
Thanks
Hello,
- deinstall the sapgui with following command line in START -> RUN
nwsapsetup /uninstall /all
*you need administrative user rights
( in WTS environment you must also change to installlation mode )
- uninstall the VCREDIST installation in the CONTROL PANEL -> ADD / REMOVE Software -> deinstall the
Microsoft redistributable runtime DLLs VS2005 SP1(x86)
- if exists, delete the folder
C:\Program Files\Common Files\Sap Shared
- delete all other folders where the sapgui was installed
c:\program files\sap\Frontend
C:\Program Files\SAP\Business Explorer
C:\Documents and Settings\All Users\Start Menu\Programs\SAP Front En
C:\Documents and Settings\All Users\Start Menu\Programs\Business
Explorer
- delete then all "SAP" entries in the windows registry in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs
( ONLY the SAP entries !!!! )
Now you have a CLEAN workstation.
Please if you have problems in Installation of the sapgui 720, please look at the NWSAPSETUP.log file
for a first analyse.
Best regards
Sven
Similar Messages
-
Iview (sap gui for windows) not in mode full screen
Hi all,
I was last week working in a performance problem with ITS. We discovered that ITS (sap gui for html) is not the best when you have to show a lot of cells in the same page.
So the custom decided to run this transaction thru the portal, using an iview.
The problem now is that we dont want to show the sap menu, the transaction menu. Also we want this screen integrated in the browser. I have checked the options and looks like correct.
Launch in New Window = Display in content portal area.
I know that with ITS we can modify the menu, with somethink like this:
~WEBGUI_SIMPLE_TOOLBAR = 34
Is this possible with SAP Transaction iView fo sapgui windows?
Thanks a lot.
Have a nice day experts.Hi,
In short, the answer is, yes.
There is however some additonal considerations you can make before creating hybrid roles with Web/Win Gui iviews.
When you start this scenario you don't have a standardised environment. You need to ensure all users accessing the iview have the Win Gui installed - again overhead, particularly when displaying inline of the webpage - even more of an issue when serving content to the outside world.
Have you tried to create a page (set the width to what you think can accomodate the requirements of the transaction you are calling), then assign the iView of the WebGui transaction you were having issues with to that? It should dynamically resize the iview to the page within the content area to allow your users to scroll to the right if need be. Just a thought.
Another scenario is to create a Z-App and enhance the screen of the SAP ABAP transaction to meet your needs, then call that transaction via the webgui. You can do much with webgui you can't do with WinGui e.g you can send users email that references the portal iView and send parameters via url query strings to prepopulate screen fields. You can control how users navigate within the portal.
Hope this helps. -
Sap adobe print preview not working
Hello,
I have installed Adobe Live Cycle Designer and developed a form. The form looks ok.
When I try doing a print preview of the form I get a message "initalization of font server module failed"(note: it is not a sap message but a windows system message) and i get kicked out of the SAP system.
I tried couple of things..Unstalling and Installing the SAP GUI 710 with patch level 11(latest). I checked with the basis team and seems like its working for them. Not sure what is the problem with my system.
Please let me know how to fix this issue.
Thanks,
RajeevHi,
It seems that the font you have used in form is not supported by the printer.
Please check it once.
Regards,
Raju. -
SAP GUI Logon does not have any anything to log on under systems
Hi everyone!
My friend installed SAP GUI 7.10 patched to 15 a few months back.
She was able to log in during that time since there were many servers/groups under the systems tab.
Right now, after her laptop has been recently cleared of a virus attack, she could no longer log on to any servers/groups because there were nothing there!!!
She is worried for a few questions:
FIRST: If she uninstall the program, will she lose her saved files that she worked on during those few months??
SECOND: Where can the saved files be located?? So that backup can be done when uninstalling SAP GUI 7.10
I really hope to get a reply soon!!! ( She needs to get her SAP up and running so she can continue on with her practicals since there is some kind of test related to SAP also... )
Thanks!!!!!!!!!!!!! Really grateful if there is a reply...Hello
Please also be aware that there is the option to re-install the latest SAP GUI with latest patch.
563161 - SAP GUI, SAP ITS & SAP IGS patches on Service Marketplace
If you would like to be notified when one of the patches is released please subscribe to the following thread in SAP Developer Network: Notification service for news about SAP GUI for Windows
1053737 - Expected release dates for SAP GUI for Windows & ITS patches
Regards. -
CTI - SAP CRM & SAP BCM: ANI does not work in SAP standard
Hello Experts,
our customer wants to work with a CTI in SAP CRM WebUI Role (Non IC; CEBP).
For the CTI the SAP CRM 7.0 (on HANA) and SAP BCM where itegrated.
We are using the Slim Communication Toolbar as recommended by SAP.
The Problem ist that the ANI (Automatic Number Identification) does not work.
The Callers Number is not identified. Function Module BUPA_SEARCH2 is not called.
No Changes were made in this area. We are completely using the SAP standard.
Has anybody experienced issues related to this one?
It would be great if somebody could give me some help and/or information!
Thank you!
Kind Regards
Martin GaschkHello Andrei,
the issue was solved by SAP.
The relevant startup component for ANI in the CMS integration profile (Tx CRM_IC_FW_PROF) was inactive:
Component:
BUSINESS PARTNER IDENTIFICATION
Class:
CL_CRM_IC_FW_BP_SEARCH_SRV
Thanks for your support!
Kind regards
Martin -
BBS BEX Query to R3 Transaction - Connect to SAP GUI for HTML not to R3 Backend-TA
Hi Experts,
I try to customize a report-report-interface from a bex query to R3 transaktion fs10n.
I configurated everything in TA RSBBS within BI.
When I start the BBS from the BEX Query a browser session opends, I have to enter the login data for the R3 system an SAP GUI for HTML is started.
Several years ago I tried the same and was connected directly to the Backend-Transaction within R3.
Was there a change within the last year?
Is it possible to configure somewhere in R3 or BW that I want to be tranferred to the Backend-TA and not to open a SAP GUI for HTML?
Can someone help?
Best regards
Mirjam
(SAP Netweaver 7.31 -> SAP ECC 6.0)Hi Stephen,
You should try running one of these transaction iViews using Firefox and have Firebug installed (or use HTTP watch in IE). This might show you why the styles are not being loaded, it could be that since the upgrade something has changed in the SICF configuration settings that is blocking the download of the CSS... that is just a guess, but if you use a tool that will show you the HTTP traffic (like Firebug) then you might get a better idea of what is going on.
Hope this helps,
Simon -
BI Precalculation Server for BI 7.0 (SAP GUI 710)? Not Available?
We recently upgraded from BW 3.5 to BI 7.0 SP 15. To support other SAP company initiatives, we also upgraded all SAP GUIs to 710.
Is there no updated BI Precalculation Server for BI 7.0 with SAP GUI 710? Can we use older precalculation software with BI 7.0? Or do we have to wait until SAP publishes the precalc server for GUI 710 (as indicated by note # 1013205)? Anyone know when that might be?I created opened a message with SAP and here is the response I got back:
Dear Customer,
Currently SAP GUI 7.10 is not supported with Precalulation service.
As per Note: 1013205 Pre-Requisite for BI Precalculation service 710
The program is believed to be shipped with the patch 400 of the 7.10
Frontned.
Patch release schedules are available in note 1085218.
Patch Delivery Schedule for BI 7.X Frontend on SAP GUI 7.10
Patch #400
o Current Status: Retest
o Planned delivery Date: first week of 2008 -
SAP NetWeaver BW Connection not working for SBOP4.0
Hello Experts,
Following are the steps & current patches:
SBOP 4.0
Dashboard Design , version: 6.0.0.0
SAP Logon
Release : 720
Patch: 5
1. SAP BW & NetWeaver Portal are not SSO(Single Sign-on)
2. I open the Dashboard Designer
3. Click on "Manage Connection"
4. Select 'SAP NetWeaver BW Connection'
5. It pops-up the Log-on screen
6. Pass on the required information
7. Use the query browser & selected the query
8. it takes the query with no error message
Issue:
1. It is not showing the Input values & Output values
Not able to display the BW Bex Query element using Dashboard Designer - SAP NetWeaver BW Connection.
Please let me know if we are missing any config. or step.
Thanks
MahendraThanks Amit for your suggestions. I tried the below steps & still it is not working:
1. re-installed Adobe version 10.1
2. Tried to connect the BW Bex query using SAP NetWeaver BW connection.
3. I am getting no error but Dashboard designer is not able to display the Input values & Output values of the BW BEx query
As I had mentioned you earlier that when I open the Bex report using the designer using the IE, it calls the portal window & I have to enter the LDAP password then the report opens in the portal.
So I think as our BW & portal are not configured as SSO so when the Dashboard designer tried to load the query from the xml file it fails. It may be because it required my LDAP login credentials.
Please let me know your suggestions.
Thanks
Mahendra -
OEM 12c: buttons in GUI page does not work
Hi,
I am using OEM12c, we just installed BI publisher last week and we have problem configure it to integrate with OEM12c. One day after the failed configuration, one of the target Authorization Policy Manager (oracle.security.apm) shows down, then we start seeing GUI problems on the console:
1. Under My Oracle Support, all links except for the Community link show blank pages.
2. Buttons in a lot of pages does not work. For example, view/edit/create on the administer page, nothing happen when click on these buttons. This is all overall the GUI, I think in general http post method is not working. Basically the GUI is un-workable.
Any suggestion to how to fix these problem?
Thanks for the help!Enterprise Manager Cloud Control Workbook for Applying Bundle Patch 1 (February 2012) and 12.1.0.2 Plugins [ID 1393173.1]
-
SAP FTP Binary Does not work after EHP 7 Upgrade
Hi All,
Since EHP 7, if I try to execute an external command through sm49, which has a shell script for ftp connection and fetching files, the 'binary' command after ftp connection is not working.
Result? I'm fetching corrupted files once in a while. The same was fine before the upgrade. The script runs fine at OS level. We are using AIX.
Did anyone see this issue before? Is there a solution?
Please help, it's quite urgent.
Thank you.
UdayHi Uday,
Since EHP 7, if I try to execute an external command through sm49, which has a shell script for ftp connection and fetching files, the 'binary' command after ftp connection is not working.
1) What is the exact error message you get ?
2) Did you check permission to the script . Ensure sidadm has full access to execute it.
3) Did you check Test Connection to TCP/IP RFC destinations SAPFTP and SAPFTPA are working fine in SM59 ?
Regards,
Deepak Kori -
SAP BeX WAD URL not working on Black Berry Emulator
Hi All,
I web report which is running successfully on Windows XP browsers. But when I am going to use same url for Black Berry emulator its not working for that. Can Some one please Help me on this?
I tried same url on Windows CE emulator also but was getting same error.
Regards,
Abhishek JainThe error that I was getting for above is "Something Didn't work quite right and we are unable to show the page you requested right now. Rest assured, Google Engineers are already springing into action to solve the problem."
Edited by: Abhi4SAP on Jan 12, 2010 8:06 AM -
Data Services XI3.1 function module files for SAP R/3 is not working
Hi guys,
Thank you for the quick response so far. I am very grateful to you all.
I got an issue and will try to explain as detail as I could and
hope ur guys won't mind. :P
I pass the functions module to SAP tech guy to install to SAP using CTS
method, and using 900086.R63 file type because my chinese client is
running SAP on unicode environment.
My DS installed on my laptop client; job server plus db2 is on HP
unix. SAP is on another HP Unix server. The function module I used is
supplied from Data Services XI3.1.
Anyway, the installation is successfully done with GUI wizard windows of
SAP Workbench instead of tp command line method.
1)However, I checked the ZAW0 function group, I opened and can't see any functions
listed under it, although the table structures ZACTA, ZTAB2048 and other items
were created.
2)So I tried to create SAP Datastore, Transport Target, etc and tried to
extract file. It failed and log said "can't open file ---
/db2/temp/curcode.txt". I checked and SAP working directory /db2/temp didn't have
curcode.txt, because the result file supposed to be extracted and stored there.
The SAP tech guy checked SAP and cant find generated ABAP program of
ZCURCD is running anyway, although my local CURCD ABAP program is
created.
3)Is it the 900086.R63 not complete? Is my function installation correct? I could view data
on datastore, but just cant run job to extract. Another non-unidcode 900200.S08 group
has larger file sizes. Should I try to install also this 900200.S08 files? Will it corrupt SAP
and cause system errors?
4)After that, I had tried to install the functions manually into ZAW0
one by one using cut and paste, however after that, I cant view the data view anymore with
error. Besides, I tried to run Check on the functions and they all returned
syntax errors, so I cant Activate any of them with SAP. Maybe dependency is missing??
Then, I deleted the manually installed functions and can view data again, but just cant extract
data by job.
5)Another side issue is all these SAP datastore creation and viewing is
through DI 11.5 old installation. The new Data Services X3.1 unable to
create datastore with database error, although the function module
installed is came from Data Services. Does anyone know the issue?
Thank you very much to read it patiently. :PHi,
Thank you for the informative link. It did help a lot in solving the problem.
(1) to (4) --- The Sap tech guy didnt install the function programs correctly, and he redo the transport again using CTS. Now I can see all the functions inside the function group ZAW0. While for the problem of cannot generate extracted file to SAP working directory for downloading, it is due to unix directory access permission setting. And also have to include the ftp username into SAPSYS user group as the help link suggested.
(5) For this problem, I reinstalled again the DS with all required components like Server Manager. The network technical guy helped me with the first installation, and the installation was not complete. So now the issue is solved, I can create R/3 Datastore with DS. -
SAP J2EE Engine : does not work !!!
Hi everyone,
I have installed SAP NW2004s Java SP9 Trial (on Windows XP and Sapdb as database). The installation finished without problems.
But when I start my SAP system, the SAP J2EE engine (process <b>jcontrol</b>) is still stopped
[... I have already searched in the forum, but I have not found a solution to my problem ...]
Here is the contents of files <b>dev_jcontrol</b> & <b>dev_sdm</b> :
File <b>dev_jcontrol</b> : *************************************
trc file: "D:\usr\sap\J2E\JC01\work\dev_jcontrol", trc level: 1, release: "700"
node name : jcontrol
pid : 1384
system name : J2E
system nr. : 01
started at : Mon Dec 03 15:23:56 2007
arguments :
arg[00] : D:\usr\sap\J2E\JC01\exe\jcontrol.EXE
arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
[Thr 2356] Mon Dec 03 15:23:56 2007
[Thr 2356] *** <b>ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] [jstartxx.c 725]
[Thr 2356] *** ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] </b>[jstartxx.c 1952]
[Thr 2356] *** ERROR => JStartupReadArgumentsEx: can't enumerate nodes [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties] (rc = -1) [jstartxx.c 524]
File <b>dev_sdm</b> : *************************************
trc file: "D:\usr\sap\J2E\JC01\work\dev_sdm", trc level: 1, release: "700"
node name : sdm
pid : 1360
system name : J2E
system nr. : 01
started at : Fri Nov 30 10:38:29 2007
arguments :
arg[00] : D:\usr\sap\J2E\JC01\exe\jlaunch.exe
arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
arg[02] : -DSAPINFO=J2E_01_sdm
arg[03] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
-> ms host : ahassaine
-> ms port : 3900
-> OS libs : D:\usr\sap\J2E\JC01\exe
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Used property files
-> files [00] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
Instance properties
-> ms host : ahassaine
-> ms port : 3900
-> os libs : D:\usr\sap\J2E\JC01\exe
-> admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
Bootstrap nodes
Worker nodes
-> [00] sdm : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
[Thr 3544] Fri Nov 30 10:38:29 2007
[Thr 3544] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 3544] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2240] JLaunchRequestFunc: Thread 2240 started as listener thread for np messages.
[Thr 3352] WaitSyncSemThread: Thread 3352 started as semaphore monitor thread.
[Thr 3544] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 3544] CPIC (version=700.2005.12.02)
[Thr 3544] INFO: Invalid property value [Debbugable=yes]
[Thr 3544] [Node: SDM] java home is set by profile parameter
Java Home: C:\Java\
[Thr 3544] <b>JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar</b>
JStartupIReadSection: read node properties [sdm]
-> node name : SDM
-> node type : sdm
-> node execute : yes
-> java path : C:\Java\
-> java parameters :
-> java vm version : 1.4.2_09-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> root path : D:\usr\sap\J2E\JC01\SDM\program
-> class path : D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
-> OS libs path : D:\usr\sap\J2E\JC01\exe
-> main class : SDMInternal
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
-> shutdown class : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters : server sdmhome=D:\usr\sap\J2E\JC01\SDM\program
-> debuggable : yes
-> debug mode : no
-> debug port : 50000
-> shutdown timeout : 120000
[Thr 3544] JLaunchISetDebugMode: set debug mode [no]
[Thr 2480] JLaunchIStartFunc: Thread 2480 started as Java VM thread.
JHVM_LoadJavaVM: VM Arguments of node [SDM]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Dsys.global.dir=D:\usr\sap\J2E\SYS\global
-> arg[ 4]: -Dapplication.home=D:\usr\sap\J2E\JC01\exe
-> arg[ 5]: -Djava.class.path=D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar;D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
-> arg[ 6]: -Djava.library.path=C:\Java
jre\bin\server;C:\Java
jre\bin;C:\Java
bin;D:\usr\sap\J2E\JC01\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;D:\usr\sap\J2E\SYS\exe\uc\NTI386
-> arg[ 7]: -Dmemory.manager=512M
-> arg[ 8]: -Xmx512M
-> arg[ 9]: -DLoadBalanceRestricted=no
-> arg[ 10]: -Djstartup.mode=JCONTROL
-> arg[ 11]: -Djstartup.ownProcessId=1360
-> arg[ 12]: -Djstartup.ownHardwareId=G1610100576
-> arg[ 13]: -Djstartup.whoami=sdm
-> arg[ 14]: -Djstartup.debuggable=yes
-> arg[ 15]: -DSAPINFO=J2E_01_sdm
-> arg[ 16]: -DSAPSTARTUP=1
-> arg[ 17]: -DSAPSYSTEM=01
-> arg[ 18]: -DSAPSYSTEMNAME=J2E
-> arg[ 19]: -DSAPMYNAME=ahassaine_J2E_01
-> arg[ 20]: -DSAPDBHOST=ahassaine
-> arg[ 21]: -Dj2ee.dbhost=ahassaine
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude iaik/security/md/SHA a
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
[Thr 2480] JHVM_LoadJavaVM: Java VM created OK.
JHVM_BuildArgumentList: main method arguments of node [SDM]
-> arg[ 0]: server
-> arg[ 1]: sdmhome=D:\usr\sap\J2E\JC01\SDM\program
[Thr 2240] Fri Nov 30 10:38:33 2007
[Thr 2240] JLaunchRequestFunc: receive command:17, argument:0 from pid:2600
[Thr 2240] JLaunchIShutdownInvoke: set shutdown interval (stop:1196419113/end:1196419233/TO:120)
[Thr 2240] JLaunchProcessCommand: Invoke VM Shutdown
[Thr 2240] JHVM_FrameworkShutdownDirect: invoke direct shutdown
[Thr 2240] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 2240] JLaunchISetState: change state from [Initial (0)] to [Stopping (5)]
[Thr 640] Fri Nov 30 10:38:34 2007
[Thr 640] JLaunchIExitJava: exit hook is called (rc = 0)
[Thr 640] JLaunchCloseProgram: good bye (exitcode = 0)
Thank you very much in advance for your help.
HassanHi!
If instance.properties is not there your installation has not finished correctly. This file is the central point of information for the bootstrap, which retrieves the info on how to connect to the database to collect the infos for the system startup (which will then overwrite your instance.properties file with the most recent values from the DB).
Please check if instance.properties has been deleted and can maybe be restored from tape or if there was an error in the installation.
Regards,
Jörg -
SAP Screen Personas: Restgui not working _ URGENT
Hi Expert,
I am having trouble configuring SAP Screen Personas, I have done all the configuration provided in the Personas Config Guide. Please see blew:
1. Activated all the following services in SICF
/sap/persos_app
/sap/bc/bsp/persos/mainapp
/sap/bc/bsp/sap/system
/sap/bc/bsp/sap/public/bc
/sap/public/bsp/sap/public/bc
/sap/public/bsp/sap/system
/sap/public/bsp/sap/htmlb
/sap/public/bc
/sap/public/bc/ur
2. Changed the restgui to CL_HTTP_EXT_ITS_BASIC
3. Setup the system in the IMG
Server.Url url to your system
Service.Uri /restgui
4. Under “Gui Configuration” button, you have the following parameters set:
Parameter
Value
~RESTGUI
1
~XSRFCHECK
0
~WEBGUI
1
But when testing the restgui service, it prompts for username & password but nothing happens.
URL: http://<system Id>:<port>/sap/restgui?sap-client=200
I also tried testing the service from default_host --> SAP --> BC --> BSP --> Persos --> mainapp, it gives me error:
500 Business Server Page (BSP) error.
I have checked the cache memory allocation; it is set to 512 mb.
Please help me, why I m not able to test the restgui services from my browser. What i'm missing and how to fix the BSP error.
Thanks in advance.
Regards
J SPlease help regarding issue attached image
1 restgui :
2 In Persuna home page not connect to server when already mentioned server but still same issue.
Please give advice and share authentic ways. -
SAP router connection is not working
Dear Experts,
I cannot connect my systems to SAP, getting the below error.My router is not expired and port 3299 is reachable.
SAPRouter "dev_rout" log as follows:
trc file: "dev_rout", trc level: 1, release: "720"
Wed Apr 09 15:55:51 2014
SAP Network Interface Router, Version 40.4
command line arg 0: C:\saprouter\saprouter.exe
command line arg 1: -r
command line arg 2: -W
command line arg 3: 60000
command line arg 4: -R
command line arg 5: C:\saprouter\saprouttab
command line arg 6: -K
command line arg 7: p: CN=SOLMAR, OU=0000881026, OU=SAProuter, O=SAP, C=DE
SncInit(): Initializing Secure Network Communication (SNC)
PC with Windows NT (mt,ascii,SAP_UC/size_t/void* = 8/64/64)
GetUserName()="Administrator" NetWkstaUser="Administrator"
SncInit(): Trying environment variable SNC_LIB as a
gssapi library name: "C:\saprouter\nt-x86_64\sapcrypto.dll".
File "C:\saprouter\nt-x86_64\sapcrypto.dll" dynamically loaded as GSS-API v2 library.
SECUDIR="C:\saprouter\" (from $SECUDIR)
The internal Adapter for the loaded GSS-API mechanism identifies as:
Internal SNC-Adapter (Rev 1.0) to SAPCRYPTOLIB
Product Version = SAPCRYPTOLIB 5.5.5C pl36 (Jul 3 2013) MT,[aesni],NB
main: pid = 3656, ppid = 0, port = 3299, parent port = 0 (0 = parent is not a saprouter)
reading routtab: 'C:\saprouter\saprouttab'
Wed Apr 09 16:00:49 2014
NiHLGetHostName: to get 192.168.4.69 succeeded in 4660ms (tl=2000ms)
Wed Apr 09 16:00:50 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:12 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:13 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:24 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:25 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:03:27 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:08:16 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:11:42 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 16:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:10 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:11 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 18:53:12 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 372
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 19:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:04 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 20:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 21:55:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 22:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Wed Apr 09 23:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 00:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 01:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 02:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 03:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 04:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 05:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 06:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 06:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:20:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:20:08 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 18/sock 384
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:05 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 19/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:06 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 20/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:28:07 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 21/sock 360
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:37 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 22/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:38 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 23/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:56:39 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 16/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
Thu Apr 10 08:58:15 2014
***LOG Q0I=> NiPConnect2: 194.117.106.129:3299: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3283]
*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 380
(SI_ECONN_REFUSE/10061; I4; ST; 194.117.106.129:3299) [nixxi.cpp 3283]
SAPRoutab:
P * * *
P 192.168.0.96 194.117.106.129 3299
P 192.168.0.96 194.117.106.129 *
# SNC-connection from and to SAP
#KT "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 194.117.106.129 *
# SNC-connection from SAP to local R/3-System for Support
#KP "p:CN=sapserv1, OU=SAProuter, O=SAP, C=DE" 192.168.* 32*
P * 194.117.106.129 *
P 127.0.0.1 194.117.106.129 3299
P * * *
P sapserv1 192.168.0.165 3389
P sapserv1 192.168.0.96 3389
P sapserv1 192.168.0.162 3389
SAPOSS Screens:Hi Philip
This looks fine. Just click on change and save again , it will automatically create SAPOSS RFC, u can see that in TX; SM59,
seems you Public IP : 192.168.0.96
The entry that you maintained in the sapsouttab was:
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" 192.168.0.96, 3200
you supposed to maintain the IP Address of the server that you opening the connection.not the router IP(192.168.0.96,)
make sure it looks like the below:
KP "p:CN=sapserv2, OU=SAProuter, O=SAP, C=DE" <IP Address of the server that you working with RFC>, 3200
Please follow this:
1.Maintain then correct entries in the saprouttab
2.restart the saprouter
3.Delete RFC: SAPOSS from TX:SM59
4. Recreate the RFC: SAPOSS from OSS1 after deleting that from SM59..
5.Go to TX: SM59 and open the RFC:SAPOSS and go to technical setting tab: and make sure that the string looks ok and make sence(if requied copy the string frm the anotherserver where the RFC:SAPOSS is workingalready) and go to log on security tab and reenter the password of the user:OSS_RFC as CPIC (all in Capital letters)
save it and test.
please send me the screen shots of saproutab and screen shot of the SAPOSS RFC from SM59 and error screen shot.
hope it clarifies the now.
Kind Regards,
Phaneendra kakani
Maybe you are looking for
-
Indesign Plug-ins How to upgrade and install?
I have CS 5.5 Master Collection for a year now, and now that I am ready to use InDesign for the first time I can't open my files. I get a message that tells me to "upgrade your plug-ins, or get the latest InDesign version". I'm not ready to shell out
-
Hi, I am having trouble understanding equivalent data types in my conversion from SQL Server to Oracle. Let's say I have this statement in SQL Server, where the string being "passed in" is a uniqueidentifier: select cast(substring('EFDA8997-63AA-4F33
-
9.3.4 export functionality results in APPCRASH
Item #1 might not be germaine to the issue, but... 1. App version discrepancy: Windows APPCRASH problem details dialog indicates version 9.3.3.177 Complete "Problem Detail" text: Problem signature: Problem Event Name: APPCRASH Application Name: Acrob
-
My iPhone 4S won't sync with my macbook pro version 10.9.1
I got my Macbook for christmas (2013) and my iphone 4s (2011). When I plug my iphone into my old macbook (2007) it works fine but when I try plugging it into my new macbook (2013) it keeps dinging until I unplug it from computer. Sometimes an error m
-
Communication Error with Epson R2400
I have an Intel Mac running Leopard and Photoshop CS3 and despite the latest driver from Epson my printer will start to print a photo and then stop due to a communication error. I checked the cables, tried printing different photos. Sometimes it will