ABAP proxy Connection not working in ECC60

Hi All,
We have created the proxies in SPROXY and using it in the report..
All the proxy related configuration are done in LPCONFIG, since SOAMANAGER is not available in this version.
My issue is when I try to establish a connection with a non-sap application through this report, I get HTTP 503, Service unavailable....
When I debugged the report, I see this exception from the proxy "no extended message(SOAP_ESERVER)"....
The report in higher versions works, but the connection is intermittent, which means if I try to execute report first time. I get HTTP 200 OK response.
In this system, I have made the configuration in SOAMANAGER. If I try to execute the same report second time, I get service unavailable, and this is weird. I have
checked with the non-sap application and its up and running. The non-sap application is a Java application. I have imported the SSL certificates, created the Logical port
for the consumer proxy created with the necessary transport settings..
I have done all the configurations in both the systems(lower and higher). Is there anything that I am missing here?
Could anyone suggest me why the connection is intermittent and why its not working in lower version?
Thanks in advance

Hi ,
Please try with this link.
http://ecohub.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0dec9f5-e9a0-2b10-c1a8-e355d01af932&overridelayout=true

Similar Messages

ABAP Proxy connection Between PI and SRM for XMLs

Hello Experts,
We are trying to set up ABAP proxy connection between PI 7.1 and SRM so we can send XML from SRM into PI.
Our SRM developer is getting an SLD error (below) and seems like something is not set up right in the SLD. Could you help me out with any kind of blog/documention on setting up an ABAP proxy connection between PI and an ABAP system. Something that talks about what steps we need to take in PI and SRM.
error ...
*We saw the error during debugging. This error is preventing XML output
to be sent to PI.
BBP_BD 002 An SLD system has not been assigned to logical system
Thanks,
Mayur

Thanks all for a quick reply. I also had to take following step to achieve the task.
adding the XI system to the SRM config - SRM Server -->
Technical basic Settings --> Define System Landscape? (also please
associated documentation in that link for XI)
Thanks,
Mayur

Server proxy is not working

Hi Experts,
I have a scenario from jdbc to SAP.I have made serverproxy.The proxy was not working.I have test the proxy backend it is working fine,but i am staring jdbc channel the data was not insert in to the database table in sap.I have checked in sxmb_moni in sap r/3 system is showing scuessfully,but data was not sent to proxy.I have put one break point in the code for debugging the proxy.But data was not comming to breakpoint.Kindly help me.
Thanks
Ravi

Hi,
Make sure that you have not done any changes in your XI structure recently otherwise regenerate the proxy and then try agin.
Secondly if you have not done any changes then it's ok. Just one thing, have you used Commit Work just after modifying/inseting the value into database table. If not use this and then try again.
It seems that smoethig went wrong at R3 side because you said data is successful in R3 MONI, so data is reaching to R3 but not going into proxy.
When you kept the break point then were you able to see the debugger screen in R3?
Regards,
Sarvesh

Proxy was not working in sap r/3

Hi All,
I have a scenario from jdbc to SAP.I have made serverproxy.The proxy was not working.I have test the proxy backend it is working fine,but i am staring jdbc channel the data was not insert in to the database table in sap.I have checked in sxmb_moni in sap r/3 system is showing scuessfully,but data was not sent to proxy.I have put one break point in the code for debugging the proxy.But data was not comming to breakpoint.Kindly help me.
Thanks
Ravi

Hi ,
Please try with this link.
http://ecohub.sdn.sap.com/irj/scn/index?rid=/library/uuid/b0dec9f5-e9a0-2b10-c1a8-e355d01af932&overridelayout=true

Camera connection not working with my camera

Camera connect not working with my Sony boggie camera

The Bloggie will not work because it draws too much power from the USB port on the iPad. The solution is to interpose a powered USB hub between the Bloggie and the iPad - connect the Bloggie to the powered hub, then connect the hub to the ipad accessory. Works fine with my 3D Bloggie.

X-Fi Titanium PCI Express front pannel connection not working

<font face="verdana,geneva" size="3">I can not get any signal to or from the front pannel connector of my X-Fi Titanium PCI Express. (The rear jacks are working fine.)
<font face="verdana,geneva" size="3">The front header cable from my Antec P-80B worked perfectly with my onboard motherboard sound. Now that I have it connected to my X-Fi I get nothing from the jacks on the front of my case. (The onboard sound is disabled in my BIOS.)? I've double and tripple checked the connection and it is properly keyed and fitted. Is there a step or a setting that I'm missing somewhere to get this working? Can anyone confirm that the front pannel connection is acti've on the X-Fi Titanium PCI Express?

Re: X-Fi Titanium PCI Express front pannel connection not working? I was truly hoping that would help and I wanted to give you some additional hope. I have a coolermaster case, and it has the AC97 jack on the inside with all my other other front panel connectors for hard dri've activity light, reset, and power on. Three inches down from the AC97 jack, the INTEL HD *which works beautifully with the X-FI, only differs by three wires in different locations and the two pinouts configurations match those of the INTEL site identically.
Please tell me what happens as I would like to post a step by step guide for the others here in the forum. You will know when you have successfully adapted the connector because in VISTA and Windows 7, your sound applet in control panel will have a display of the connectors "lit up" when they are successfully connected. Mine shows FP microphone in the applet when its plugged in, and grayed out when its not. Its great for telling if I am connected on the rear of the soundcard of the front.
Best of luck and .......
Message Edited by jmacguire on 07-06-2009 :09 PM

ABAP Proxy does not send data to XI system.

I have a very simple program to test an ABAP Proxy:
REPORT Z_TEST_PERSON_OB.
DATA prxy TYPE REF TO Z996CO_PERSON_OB2.
CREATE OBJECT prxy.
DATA person TYPE Z996PERSON_MT .
*TRY.
person-person_mt-first_name = 'Ken and Kenneth'.
person-person_mt-Series = 'The Fast Show'.
person-person_mt-motto = 'Ooh, suit you Sir!'.
CALL METHOD prxy->execute_asynchronous
EXPORTING
output = person.
commit work.
I removed any exception handling to see if it would dump. Nothing. Seems to work fine, but no data appears in the XI Integration Engine monitor. I checked the scenario in XI and tested it; again, seems to work fine.
Could I have missed something in setting up the system? Any pointers highly appreciated.
BR,
Tony.

Try the Message Monitoring -> Messages from component 'Proxy Runtime <...>'.
That's where I found my Messages back (Status: To Be Delivered...)
If this is the case, probably your Proxy Runtime does send the messages to the Integration Engine.
Check the queues:
Transaction SXMB_ADM on the Business system (the system that sends the Proxy)
Integration Engine > Administration > Manage Queues
All queues should be checked
Click Register Queues. Status bar should display a Success message.
Click Activate Queues. Status bar should display a Success message.
If it still does not work, maybe the is no connection between Integration Builder and Runtime Workbench.
Check SM59 on your ECC-business system (the system that sends the Proxy). It should have the Connection INTEGRATION_DIRECTORY_HMI (type H). If not, this is the problem.
Create a new connection INTEGRATION_DIRECTORY_HMI, type H.
Tab Technical settings:
Target Host is your XI-host
Service No. 5xx00 (xx is the instance number of your XI-system)
Path Prefix is "/dir/hmi_cache_refresh_service/ext" (without quotes)
Tab Logon & Security
Logon Procedure is "Basic Authentication"
Logon using XIISUSER (or PIISUSER)
Tab special Options
Specify timeout: set to 900 msec.
Compression Status should be 'inactive'
Compressed response: No
Accept Cookies: Yes (all)
Save configuration and test connection. Popup about cookies appears. Check the "Accept All Further Cookies"option.
The response should have HTTP/1.1 200 OK in the first line of the response header.
Now your Proxy Runtime should be able to connect the Integration Engine.
Greetings, Frank

Corporate connectivity not working for some users

Hi,
I'm having an issue that started about a month ago but is getting worse. A select group of users are no longer able to connect using DirectAccess, even though these users have been using their computers for a few months without issue.
BACKGROUND:
-Windows 2008 R2 DirectAccess server
-Windows 7 x64 enterprise clients
-Most clients experiencing the issue have a newer laptop (Lenovo T440 with Intel 7260AC wireless), but the issue is not limited to this model. Also, I have 25+ other Lenovo T440 units that connect without issue to this day.
TROUBLESHOOTING STEPS:
I have tried disabling the various interfaces used for directaccess on these problem machines and have not been able to narrow it down. Essentially- I've noticed the IP-HTTPS interface shows deactivated, so I'll disable Teredo. This
usually allows the IP-HTTPS to show activated, and connectivity is restored. However, after 30 seconds to a few minutes, connectivity will once again drop. So I'll re-enable teredo (default,client, or enterprise client) and connectivity will kick
on for another brief period, but drops again shortly after.
I have confirmed that during these short periods of connectivity working, the wf.msc shows connectivity using NTLM and Kerberos, but the clients just can't seem to stay connected on any interface.
However, in the wf.msc when the clients are not functioning, I only ever see one NTLM entry.

LOGS:
Below is a directaccess client log pulled from a non-functioning client before making any changes or any testing. Feel free to ask for the rest of the log if needed-- I have put in place holders for information that may be sensitive. Thank you!!
RED: Corporate connectivity is not working.
Windows is unable to relocationve corporate network names. Please contact your administrator if this problem persists.
24/3/2015 18:21:43 (UTC)
Probes List
FAIL PING: location-dc.domain.local
FAIL PING: location-file.domain.local
DTE List
PASS PING: 2002:'mac':5a1c::'mac':5a1c
PASS PING: 2002:'mac':5a1d::'mac':5a1d
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : c2075
Primary Dns Suffix . . . . . . . : domain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.local
domain2.ad
System Quarantine State . . . . . : Not Restricted
Wireless LAN adapter Wireless Network Connection 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter #2
Physical Address. . . . . . . . . : 2A-B2-BD-'mac2'-E5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Virtual WiFi Miniport Adapter
Physical Address. . . . . . . . . : 2A-B2-BD-'mac2'-E6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 28-B2-BD-'mac2'-E9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 7260
Physical Address. . . . . . . . . : 28-B2-BD-'mac2'-E5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2602:304:'mac3':d370:5a1:c77:834:86a9(Preferred)
Temporary IPv6 Address. . . . . . : 2602:304:'mac3':d370:f9ce:db89:87ad:'mac4'(Preferred)
Link-local IPv6 Address . . . . . : fe80::5a1:c77:834:86a9%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.86(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, March 24, 2015 1:48:21 PM
Lease Expires . . . . . . . . . . : Wednesday, March 25, 2015 1:48:21 PM
Default Gateway . . . . . . . . . : fe80::21b:5bff:febf:4f21%12
192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : domain.local
Description . . . . . . . . . . . : Intel(R) Ethernet Connection I218-LM
Physical Address. . . . . . . . . : 28-D2-44-C5-24-59
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.attlocal.net:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter iphttpsinterface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : iphttpsinterface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{FD31098B-E475-49A1-9AFA-8C43FF928F97}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.domain.local:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:'mac':5a1c:342d:25dd:b4e1:12c8(Preferred)
Link-local IPv6 Address . . . . . : fe80::342d:25dd:b4e1:12c8%18(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{E1BE09BA-B38B-4F87-8893-E3D32A88EDFC}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{0C04B587-7861-4D8D-9DA9-6326AB71D701}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #5
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh int teredo show state
Teredo Parameters
Type : client
Server Name : 204.16.90.28 (Group Policy)
Client Refresh Interval : 30 seconds
Client Port : unspecified
State : qualified
Client Type : teredo host-specific relay
Network : unmanaged
NAT : restricted
NAT Special Behaviour : UPNP: No, PortPreserving: Yes
Local Mapping : 192.168.1.86:55842
External NAT Mapping : 75.30.237.55:55842
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh int httpstunnel show interfaces
Interface IPHTTPSInterface (Group Policy) Parameters
Role : client
URL : https://uag.webdomain.com:443/IPHTTPS
Last Error Code : 0x0
Interface Status : IPHTTPS interface deactivated
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh dns show state
Name Relocationution Policy Table Options
Query Failure Behavior : Always fall back to LLMNR and NetBIOS
if the name does not exist in DNS or
if the DNS servers are unreachable
when on a private network
Query Relocationution Behavior : Relocationve only IPv6 addresses for names
Network Location Behavior : Let Network ID determine when Direct
Access settings are to be used
Machine Location : Outside corporate network
Direct Access Settings : Configured and Enabled
DNSSEC Settings : Not Configured
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh name show policy
DNS Name Relocationution Policy Table Settings
(ENTRIES OMITTED TO SAVE SPACE)
Settings for .domain.local
Certification authority : DC=local, DC=domain, CN=HDT CA
DNSSEC (Validation) : disabled
DNSSEC (IPsec) : disabled
DirectAccess (DNS Servers) : 2002:'mac':5a1d::'mac':5a1d
DirectAccess (IPsec) : disabled
DirectAccess (Proxy Settings) : Bypass proxy
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh name show effective
DNS Effective Name Relocationution Policy Table Settings
(ENTRIES OMITTED TO SAVE SPACE)
Settings for .domain.local
Certification authority : DC=local, DC=domain, CN=HDT CA
DNSSEC (Validation) : disabled
IPsec settings : disabled
DirectAccess (DNS Servers) : 2002:'mac':5a1d::'mac':5a1d
DirectAccess (Proxy Settings) : Bypass proxy
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh int ipv6 show int level=verbose
Interface Loopback Pseudo-Interface 1 Parameters
IfLuid : loopback_0
IfIndex : 1
State : connected
Metric : 50
Link MTU : 4294967295 bytes
Reachable Time : 40000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : disabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Wireless Network Connection Parameters
IfLuid : wireless_0
IfIndex : 12
State : connected
Metric : 25
Link MTU : 1472 bytes
Reachable Time : 1101000 ms
Base Reachable Time : 1805000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 64
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.attlocal.net Parameters
IfLuid : tunnel_4
IfIndex : 22
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 27500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Wireless Network Connection 2 Parameters
IfLuid : wireless_5
IfIndex : 15
State : disconnected
Metric : 5
Link MTU : 1500 bytes
Reachable Time : 24000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface iphttpsinterface Parameters
IfLuid : tunnel_5
IfIndex : 17
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 31500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : enabled
Other Stateful Configuration : enabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Local Area Connection Parameters
IfLuid : ethernet_6
IfIndex : 11
State : disconnected
Metric : 5
Link MTU : 1500 bytes
Reachable Time : 31500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface 6TO4 Adapter Parameters
IfLuid : tunnel_6
IfIndex : 19
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 39500 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : disabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.{FD31098B-E475-49A1-9AFA-8C43FF928F97} Parameters
IfLuid : tunnel_7
IfIndex : 21
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 33000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.domain.local Parameters
IfLuid : tunnel_8
IfIndex : 39
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 36000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Bluetooth Network Connection Parameters
IfLuid : ethernet_9
IfIndex : 14
State : disconnected
Metric : 50
Link MTU : 1500 bytes
Reachable Time : 17000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Wireless Network Connection 3 Parameters
IfLuid : wireless_9
IfIndex : 16
State : disconnected
Metric : 5
Link MTU : 1500 bytes
Reachable Time : 17000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 1
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface Teredo Tunneling Pseudo-Interface Parameters
IfLuid : tunnel_9
IfIndex : 18
State : connected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 14500 ms
Base Reachable Time : 15000 ms
Retransmission Interval : 2000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : enabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : enabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.{E1BE09BA-B38B-4F87-8893-E3D32A88EDFC} Parameters
IfLuid : tunnel_10
IfIndex : 20
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 41000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
Interface isatap.{0C04B587-7861-4D8D-9DA9-6326AB71D701} Parameters
IfLuid : tunnel_11
IfIndex : 23
State : disconnected
Metric : 50
Link MTU : 1280 bytes
Reachable Time : 40000 ms
Base Reachable Time : 30000 ms
Retransmission Interval : 1000 ms
DAD Transmits : 0
Site Prefix Length : 64
Site Id : 1
Forwarding : disabled
Advertising : disabled
Neighbor Discovery : enabled
Neighbor Unreachability Detection : disabled
Router Discovery : enabled
Managed Address Configuration : disabled
Other Stateful Configuration : disabled
Weak Host Sends : enabled
Weak Host Receives : disabled
Use Automatic Metric : enabled
Ignore Default Routes : disabled
Advertised Router Lifetime : 1800 seconds
Advertise Default Route : disabled
Current Hop Limit : 0
Force ARPND Wake up patterns : disabled
Directed MAC Wake up patterns : disabled
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh advf show currentprofile
Private Profile Settings:
State ON
Firewall Policy BlockInbound,AllowOutbound
LocalFirewallRules N/A (GPO-store only)
LocalConSecRules N/A (GPO-store only)
InboundUserNotification Enable
RemoteManagement Disable
UnicastResponseToMulticast Enable
Logging:
LogAllowedConnections Disable
LogDroppedConnections Disable
FileName %systemroot%\system32\LogFiles\Firewall\pfirewall.log
MaxFileSize 4096
Ok.
C:\WINDOWS\system32\LogSpace\{05471C14-7140-4651-84C2-230EC7D70628}>netsh advfirewall monitor show consec
Global Settings:
IPsec:
StrongCRLCheck 0:Disabled
SAIdleTimeMin 5min
DefaultExemptions ICMP
IPsecThroughNAT Never
AuthzUserGrp None
AuthzComputerGrp None
StatefulFTP Enable
StatefulPPTP Enable
Main Mode:
KeyLifetime 60min,0sess
SecMethods DHGroup2-AES128-SHA256,DHGroup2-AES128-SHA1,DHGroup2-3DES-SHA1
ForceDH No
Categories:
BootTimeRuleCategory Windows Firewall
FirewallRuleCategory Windows Firewall
StealthRuleCategory Windows Firewall
ConSecRuleRuleCategory Windows Firewall
Quick Mode:
QuickModeSecMethods ESP:SHA1-None+60min+100000kb,ESP:SHA1-AES128+60min+100000kb,ESP:SHA1-3DES+60min+100000kb,AH:SHA1+60min+100000kb
QuickModePFS None
Security Associations:
Main Mode SA at 03/24/2015 14:21:44
Local IP Address: 2602:304:'mac3':d370:f9ce:db89:87ad:'mac4'
Remote IP Address: 2002:'mac':5a1d::'mac':5a1d
Auth1: ComputerCert
Auth2: UserNTLM
MM Offer: None-AES128-SHA256
Cookie Pair: 9398e38420480425:51071d5bae9eb503
Health Cert: No
Quick Mode SA at 03/24/2015 14:21:44
Local IP Address: 2602:304:'mac3':d370:f9ce:db89:87ad:'mac4'
Remote IP Address: 2002:'mac':5a1d::'mac':5a1d
Local Port: Any
Remote Port: Any
Protocol: Any
Direction: Both
QM Offer: ESP:SHA1-AES192+60min+100000kb
PFS: None
Thanks again,

ABAP PROXY CONNECTION TO SAP/XI

Hi,
I have the following scenery: Abap Proxy -> XI->RFC.
This abap proxy is installed in the enviroment R/3 in the client 041 and client 210.
In the client 041 it is executed with success. In the customer 210 when I execute the program abap a login screen appears in SAP/XI. Typing the login works.
The subject is: why in the enviroment cliente 210 does the login screen appear when I execute the program abap and in the client 041 not?
I enter in the sxmb_moni and appears the following in the client 210
<? xml version = "1.0" encoding = "UTF-8" standalone = "yes"?>
- 
- <SAP:ErrorHeader xmlns:SAP = "http://sap.com/exchange/MessageFormat">
<SAP:Context />
<SAP:Code p1 = "401" p2 = "Unauthorized" p3 = "" p4 = ""> HTTP.HTTP_STATUS_CODE_NEQ_OK </ SAP:Code>
<SAP:Text language = "EN">HTTP status code 401: Unauthorized </ SAP:Text>
</ SAP:ErrorHeader>

Hi Sergio,
When you execute the program abap a login screen appears in SAP/XI. Typing the login works. But It gives error
HTTP status code 401: Unauthorized
Because it is using your userID and trying to execute it,
But it is not having enough authorization.
Go and check the entry for Integration server in
Go to SXMB_ADM
Go to Integration engine Configuration
Check the Integration server Entry -
It must be
http://server:port/sap/xi/engine?type=entry
The solution is make a RFC destination of type HTTP for XI Integration server
with Target host - host
service - http port (like 8000)
Path prefix - /sap/xi/engine/?type=entry
And in the logon/security Tab, enter the user name and password for user XIAPPLUSER,
And again Go to SXMB_ADM
Go to Integration engine Configuration
Check the Integration server Entry -
change it to
dest://<RFCDESTNAME that you have created>
This way it will not ask for login and XIAPPLUSER will
have enough permission to execute it.
Regards,
Vijay

ABAP Proxy outbound not showing in sxmb_moni

Hi All,
All my ABAP proxy scenarios are inbound, however I need to do a outbound ABAP Proxy scenario.
So, I created a Assyn interface in Integration Builder and created a proxy on outbound message interface in SPROXY. (ZCO_ITF_FILE_***).
R/3 --> SQL server
In my simple example I created a program in se38 as shown below
DATA prxy TYPE REF TO ZCO_ITF_FILE_***.
CREATE OBJECT prxy.
DATA it TYPE ZMTP_FILE_***.
TRY.
    it-MTP_FILE_***-id = '12'.
    CALL METHOD prxy->execute_asynchronous
      EXPORTING
        output = it.
commit work.
CATCH cx_ai_system_fault .
    DATA fault TYPE REF TO cx_ai_system_fault .
    CREATE OBJECT fault.
    WRITE :/ fault->errortext.
ENDTRY.
I want to send just one field called ID.
The program works fine, the "commit work" is called but It doesn´t reach the XI. It doesn´t appear in SXMB_MONI.
As I said before I have Inbound Abap Proxies interfaces, so, I got the sxmb_admin configured.
What am I missing ?
Thanks
Diego

Hi
Thare are no error in SMQ2. The message shwon is
Cl     | User      | Func. Module             | Queue       | Date          | Time      | Status Text
310    ABAP01 SXMS_ASYNC_EXEC   XBTS0005     26.05.2009 11:23:59 Transaction recorded
When I press F6 the message goes to XI. the message reach the sxmb_moni in XI.
But in XI I am facing with another error (the receiver could not be determined).
Thanks
Diego

R/3 Proxy is not working

Hi XI Gurus,
Scenario:
The overview of the scenario is as follows.
1.legacy system will send file to XI which will send it to SAP via a ABAP Proxy.
2.The data is then validated in a control program(r/3) as per the various validation rules.
3.The validated data is then send back to XI via ABAP Proxy.
4.XI creates and posts the IDocs in SAP using the validated data.
Problem:
The file is coming successfully to ABAP proxy.
But, it is not returning back to XI(step 3).
This whole configuration was working successfully earlier.
Suddenly , now it is not working.
Even we are not able to Debug these XML Messages.
Any help in this matter will be very usefull.
Regards.
Santosh.

Hi Santosh,
1. Pls do check whether your o/b proxy to XI is holding all the settings for sending the data in source system(R/3).
2. Have you provided the explicit 'Commit Work' statement after the outbound proxy?
3. Check in the debugging of the outbound proxy triggering program to see there is enough data to get into the place where the proxy is triggered.
4. Also check whether the queues for the outbound proxy is registered.
5. Check in the SXMB_MONI of your R/3 system which acts as a sender to see whats happening to your messages if step 3 mentioned was successful.
6. Check whether your RFC destination to the XI system is not changed recently like the service/CPIC user and its password.
Cheers
JK

ICM_HTTP_CONNECTION_FAILED message in SM59 (ABAP Proxy Connection)

Hi All,
Recently, i got a problem with our XI server, suddently the ABAP proxy connectiont to XI from another SAP server was failed. i was check from sm59 the HTTP connection return me ICM_HTTP_CONNECTION_FAILED.
i already check the port and calling this link http://demokl:8001/sap/XI/engine?type=entry from the other server it is working fine. but still got problem from SM59.
Please help.
Regards
Fernand

Hi jagadish,
These are my parameters :
Connection Type = (H) HTTP Connection to ABAP System
Target host = demokl (hostname)
Path Prefix = /sap/XI/engine?type=entry
Service       = 8001
Language   = EN
Client        = 300
User          = PIAPPLUSER
Previously was working fine, but suddently go problem. but i was trying to create HTTP connection from XI Box itself it is working fine but from others box didn't work.
i have check the port it is open.
Please help
Regards
Fernand

T500 Ethernet Connection Not working, but wireless is working

Hi
In my laptop, when I try to connect to internet using the Ethernet card, it is not working.
My laptop has the following configuration.
T500; Windows Vista 64
Ethernet card: Intel(R) 82567LM Gigabit Network Connection
Following are what I observed.
1. From command prompt, when I executed the command ipconfig, it is not listing the ethernet adapter connection.
C:\Windows\system32>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : Palasseri-Mana
   Primary Dns Suffix . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
Wireless LAN adapter Wireless Network Connection 3:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : My WiFi PAN
   Physical Address. . . . . . . . . : 00-21-6A-1A-24-B3
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wireless Network Connection 2:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : WiFi STA
   Physical Address. . . . . . . . . : 00-21-6A-1A-24-B2
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::42a:c2e2:cf9f:7b87%13(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.12(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, February 21, 2010 6:12:15 PM
   Lease Expires . . . . . . . . . . : Sunday, February 28, 2010 6:12:14 PM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 234889578
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-11-88-93-46-00-24-7E-13-AE-17
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 6:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : isatap.{7DB78E75-7547-408D-97D2-C347AF27F
5F9}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : isatap.{5D3FE014-FD4D-40E1-AB3A-94B48F4A9
392}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 14:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
2. Control Panel\Network and Internet\Network Connections : Under this, when I list all the connection, the Ethernet connection is showing it as Enable.
3. When I unplug the network cable, at Control Panel\Network and Internet\Network Connections, I see the status as Cable Unplugged..
4. I downloaded the latest driver and installed, but didnt change this behavior.
How can I fix this ethernet issue. Any help is deeply appreciated.
Thanks,
NP

palasseri wrote:
Thank you for your reply.
Yeah, it is listed under the Device Manager.
I see one potential error under the event viewer. Thank you for that pointer.
The IP address lease 192.168.0.11 for the Network Card with network address 00216A1A24B2 has been denied by the DHCP server 192.168.0.1 (The DHCP Server sent a DHCPNACK message).
Any idea why this is coming???
I get that exact same error when I change my MAC address and my computer is trying to connect to my router.
This message is probably just the result of your computer not recognizing your Ethernet Adapter.
I have never had this problem and am just shooting in the dark, but I would say you either have a bad Ethernet card, or your Adapter is not configured correctly.
I keep wanting to go back to your adapter in the Device Manager.
Is the Device Status "This Device is working Properly"?
Under Power Management, is the "Allow the computer to turn off this device to save power" unchecked?
Are you downloading the drivers from Lenovo's website?
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-70199
Have your tried Uninstalling the adapter, and reboot.
Your system may automatically reinstall the adapter. If not, you can manually reinstall it.
T500 ~ T9400 2.53GHz 1066MHz 6MBL2 ~ Vista 32bit Home ~ WXGA 15.4 LED ~ ATI Mobility Radeon 3650 ~ 4GB ram ~ Camera ~ 160GB 7200rpm HD ~ Intel Turbo Memory 2GB ~ CD-RW/DVD ~ Intel WiFi 5300

Http connection not working on phone

Hi i am trying to connect to a http server using the new nokia n95 phone with T-mobile web and walk(Unlimited 3g internet access)
on the emulaor and on the phones wifi connection, it works. But when i try connecting to the server using gprs/3g it doesnt. The response code never equals to OK . here is my code below:
I know it is not working because has soon as the program makes an attempted to connect, the root.notifyDestroy() closes the application as i expect it too
server = (HttpConnection) Connector.open(url);
            server.setRequestMethod(HttpConnection.POST);
            int rc = server.getResponseCode();
            if (rc == HttpConnection.HTTP_OK)
               is = server.openInputStream();
            else
                root.notifyDestroyed();
                 Alert alert = new Alert ("Error");
                alert.setString("Error, server is down");
                alert.setTimeout (5000);
                Display.getDisplay(root).setCurrent(alert);
                throw new IOException("HTTP response code: " + rc);
            }

I had all sorts of strange problems getting http connect to work from phones. Most of my problems were resolved by adding every single header I could find that tells the carrier's gateway to leave it alone. Try adding these headers to the connection from the phone, and the response from the server:
                    connection.setRequestProperty( "User-Agent","Profile/MIDP-1.0 Configuration/CLDC-1.0");
                    connection.setRequestProperty( "Content-Type", "application/octet-stream");
                    connection.setRequestProperty( "Content-Length", ""+(allContentToSend.length));
                    connection.setRequestProperty( "Cache-Control","no-store");
                    connection.setRequestProperty( "Cache-Control", "no-cache");
          connection.setRequestProperty( "Pragma","no-cache");
          connection.setRequestProperty( "Cache-Control", "no-transform");
          connection.setRequestProperty( "Connection", "Keep-Alive");
          connection.setRequestProperty( "Proxy-Connection", "Keep-Alive");
The content-type will depend on what you are sending. octet-stream is for binary data. If you are just encoding parameters in your POST you may need something else like "application/x-www-form-urlencoded".
The content-length is obviously dependant on what you are sending. The rest of the properties simply tell whoever is transporting the request to leave it alone.
TEMP_MOVED sounds like a redirect or some odd thing. Maybe the carrier is caching the response, and you are actually getting something unnexpected.
Hope this helps.

Excite PRO 3G connection not work after Android v4.3 update

Hello,
I live in Italy and on last Sunday (january 26th) my Excite PRO tablet (model AT10LE-A-10H) got the Android version 4.3.201121220.35.
After restart my wifi works fine, all other app work fine, but my 3g connection doesn't work, mobile network bar is empty and it says "no service".
My sim card is ok. I used this sim card before the system update and I didn't get any problem with Android 4.2.2.
Please help me.
Thank you

>After restart my wifi works fine, all other app work fine, but my 3g connection doesn't work, mobile network bar is empty and it says "no service".
Go to the mobile network settings and search again for the 3G network.
I had similar problem with my Android Smartphone and my o2 provider
I started new search, then I chosen the O2 again and then I could solve the problem.
In case this does not work for you, recommend you to reset the tablet back to default (factory settings)

ABAP proxy Connection not working in ECC60

Similar Messages

Maybe you are looking for