BorderManager abends with EIP in PROXY.NLM

Here's the problem.
Any ideas?
I have BM 3.9 SP1
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.08
Server MCFW01 halted Monday, 16 March 2009 1:50:07.245 pm
Abend 28 on P00: Server-5.70.08: Page Fault Processor Exception (Error code 00000000)
Registers:
CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
EAX = DFA2F6B3 EBX = 05B4B5A4 ECX = DFA2F5B7 EDX = 05B4B5A4
ESI = 00040000 EDI = 05B4B5B8 EBP = 00000000 ESP = B3F739C4
EIP = 9BBBD35D FLAGS = 00010086
9BBBD35D 8B08 MOV ECX, [EAX]=?
EIP in PROXY.NLM at code start +0003735Dh
Access Location: 0xDFA2F6B3
The violation occurred while processing the following instruction:
9BBBD35D 8B08 MOV ECX, [EAX]
9BBBD35F 39CA CMP EDX, ECX
9BBBD361 741A JZ 9BBBD37D
9BBBD363 85C9 TEST ECX, ECX
9BBBD365 7408 JZ 9BBBD36F
9BBBD367 8D81FC000000 LEA EAX, [ECX+000000FC]
9BBBD36D EBEE JMP 9BBBD35D
9BBBD36F 6877506F9E PUSH 9E6F5077
9BBBD374 E877B5FCFF CALL PROXY.NLM|InternalConsistencyError
9BBBD379 83C404 ADD ESP, 00000004
Running process: Server 00:78 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: B3F73F80
OS Stack limit: B3F6C040
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: 9BB95204 (PROXY.NLM|IdleClientSendFIN+44)
--05B4B5A4 ?
--05B4B5A4 ?
9BB8FC08 (PROXY.NLM|TCPCtlCallBack+1DC)
--05B4B5A4 ?
--00783B5A ?
--94E4D388 ?
--00040000 (LOADER.NLM|PSD_LibraryErrno+1FF0)
--94E4D2BC ?
8E296FA5 (TCP.NLM|TCPAnyAddrCheck+270D)
--00000004 (LOADER.NLM|KernelAddressSpace+4)
--05B4B5B8 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00783B5A ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--B3F73A8C ?
--94E4D2BC ?
8E29733E (TCP.NLM|TCPAnyAddrCheck+2AA6)
--94E4D2BC ?
--00000046 (LOADER.NLM|KernelAddressSpace+46)
--00783B5A ?
--00781B5C ?
--94E4D2BC ?
--B3F73A8C ?
8E296453 (TCP.NLM|TCPAnyAddrCheck+1BBB)
--94E4D2BC ?
--B3F73A8C ?
--00783B5A ?
--00000028 (LOADER.NLM|KernelAddressSpace+28)
--3FFFFFFF ?
--94E4D2BC ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--B3F73A8C ?
8E296078 (TCP.NLM|TCPAnyAddrCheck+17E0)
--94E4D2BC ?
--B3F73A8C ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--94E4D2BC ?
--B3F73A8C ?
8E295A80 (TCP.NLM|TCPAnyAddrCheck+11E8)
--94E4D2BC ?
--B3F73A8C ?
8E29EE64 (TCP.NLM|TCPMPUnsafeConnectionLookup+5C0)
--8753AF42 ?
--94E4D2BC ?
--94E4D2BC ?
--B3F73A8C ?
8E294CE1 (TCP.NLM|TCPAnyAddrCheck+449)
--94E4D2BC ?
--B3F73A8C ?
--8753AEE4 ?
--B3F73AB8 ?
--B3F73AC8 ?
--CC0F1879 ?
--00781B5C ?
--CC0F1879 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000014 (LOADER.NLM|KernelAddressSpace+14)
--1FFE0011 ?
--0000FFFF (LOADER.NLM|KernelAddressSpace+FFFF)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--B0AF0210 ?
--B2805ADB ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--50000210 ?
--C89E3FD3 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--10BC2188 ?
90A0869C (MSM.NLM|CMSMValidateAuxDataBuffer+DC)
--8F52D3AC ?
--871275FC ?
--903DA630 ?
--10BC2188 ?
90A089BB (MSM.NLM|CMSMValidateAuxDataBuffer+3FB)
--8F5273DC ?
90A1180E (ETHERTSM.NLM|EtherTSMRegisterHSM+11A)
--00000297 (LOADER.NLM|KernelAddressSpace+297)
8DD72D68 (TCPIP.NLM|IPInboundIF+679)
--00000297 (LOADER.NLM|KernelAddressSpace+297)
8DD720D8 (TCPIP.NLM|?IPSend_pushed+BE)
--007B5511 ?
--87127604 ?
00365802 (SERVER.NLM|FunnelingWrapperReturnsHere+25)
--C8C279D4 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000246 (LOADER.NLM|KernelAddressSpace+246)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
8E299D40 (TCP.NLM|TCPAnyAddrCheck+54A8)
--87127604 ?
--7C8C0850 ?
--7C8C0850 ?
--7C8C07AC ?
--00000450 (LOADER.NLM|KernelAddressSpace+450)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--871276C0 ?
--00000450 (LOADER.NLM|KernelAddressSpace+450)
--87127604 ?
--7C8C06E0 ?
Additional Information:
The CPU encountered a problem executing code in PROXY.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.

Cheers
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.08
Server MCFW01 halted Tuesday, 10 March 2009 1:09:37.852 pm
Abend 1 on P00: Server-5.70.08: Page Fault Processor Exception (Error code 00000000)
Registers:
CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
EAX = 000283A0 EBX = 176EA214 ECX = 9F6A38E4 EDX = 9F6A38E4
ESI = 00000000 EDI = 00000002 EBP = 025ED004 ESP = 885DBEA4
EIP = 9F1BFE72 FLAGS = 00010086
9F1BFE72 8B02 MOV EAX, [EDX]=?
EIP in PROXY.NLM at code start +00044E72h
Access Location: 0x9F6A38E4
The violation occurred while processing the following instruction:
9F1BFE72 8B02 MOV EAX, [EDX]
9F1BFE74 39D8 CMP EAX, EBX
9F1BFE76 7436 JZ 9F1BFEAE
9F1BFE78 39C8 CMP EAX, ECX
9F1BFE7A 7436 JZ 9F1BFEB2
9F1BFE7C 89C2 MOV EDX, EAX
9F1BFE7E EBF2 JMP 9F1BFE72
9F1BFE80 8D51FF LEA EDX, [ECX-01]
9F1BFE83 891530E1539F MOV [PROXY.NLM|cntModuleInUse]=00000001, EDX
9F1BFE89 83C404 ADD ESP, 00000004
Running process: Server 12 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 885DBF7C
OS Stack limit: 885D4040
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: -9F4D8604 (PROXY.NLM|(Data Start)+3604)
--025ED004 ?
-9F4D8630 (PROXY.NLM|(Data Start)+3630)
-9F4F5438 (PROXY.NLM|status500Description+0)
--176EA214 ?
9F1BFE18 (PROXY.NLM|oc_removeHot+A8)
--176EA214 ?
--176EA214 ?
--00000002 (LOADER.NLM|KernelAddressSpace+2)
9F182BB4 (PROXY.NLM|HTTPClientError+C0)
--176EA214 ?
-9F4F5438 (PROXY.NLM|status500Description+0)
-9F4D8630 (PROXY.NLM|(Data Start)+3630)
--176EA214 ?
--02E56004 ?
--870C4C86 ?
--02E56004 ?
--00000007 (LOADER.NLM|KernelAddressSpace+7)
9F182AA5 (PROXY.NLM|ClientCacheError+25)
--02E56004 ?
--00000003 (LOADER.NLM|KernelAddressSpace+3)
-9F4F5438 (PROXY.NLM|status500Description+0)
-9F4D8630 (PROXY.NLM|(Data Start)+3630)
9F18427E (PROXY.NLM|oc_writeHeadersToCache+13E)
--02E56004 ?
--00000006 (LOADER.NLM|KernelAddressSpace+6)
--00000006 (LOADER.NLM|KernelAddressSpace+6)
--000005B0 (LOADER.NLM|KernelAddressSpace+5B0)
--02E56004 ?
--0000970B (LOADER.NLM|KernelAddressSpace+970B)
--02E56004 ?
--02E56004 ?
9F183E28 (PROXY.NLM|WriteHTTPResponseHeaders+58)
--02E56004 ?
--02E56004 ?
--02E56004 ?
9F1832E0 (PROXY.NLM|ProcessReplyBody+320)
--02E56004 ?
--02E56004 ?
--02E56004 ?
9F1A6C7E (PROXY.NLM|ProcessHTTPReplyHeaders+7E)
--02E56004 ?
--0000970B (LOADER.NLM|KernelAddressSpace+970B)
--870C4D94 ?
--870C4C7E ?
9F182A1C (PROXY.NLM|ClientReplyHandler+BC)
--02E56004 ?
--870C4C7A ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
9F1E0240 (PROXY.NLM|CallrsCallBacks+0)
9F1E0294 (PROXY.NLM|CallrsCallBacks+54)
--02E56004 ?
00365AA2 (SERVER.NLM|StartWorkToDo+23)
--02E56004 ?
--0000970B (LOADER.NLM|KernelAddressSpace+970B)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--9E7C6440 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
002152C2 (SERVER.NLM|WorkerThread+50E)
--02E56004 ?
--18B9914A ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--886D4080 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--886D4080 ?
002228C8 (SERVER.NLM|TcoNewSystemThreadEntryPoint+40)
--886D4080 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--34343434 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
--65657246 ?
Stack dump exceeded the valid memory limit
Additional Information:
The CPU encountered a problem executing code in PROXY.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.
Originally Posted by Mysterious
asabadin wrote:
> Here's the problem.
>
> Any ideas?
>
> I have BM 3.9 SP1
>
> Novell Open Enterprise Server, NetWare 6.5
> PVER: 6.50.08
>
> Server MCFW01 halted Monday, 16 March 2009 1:50:07.245 pm
> Abend 28 on P00: Server-5.70.08: Page Fault Processor Exception (Error
> code 00000000)
Can you post abend 1 please?

Similar Messages

PROXY.NLM Abend & Memory Leak issues

Issue:
1. BM39SP2 abends frequently
2. Memory Leak issue.
3. During the restart, it has Short Term memory issues
Environment:
Netware 6.5 SP6
BorderManager 3.9 SP2 (with latest proxy.nlm)
Server has 4 GB memory
Additional Info: The server is patched with the latest TCP & Winsock patch for SP6.
Latest Abend information
Novell Netware, V6.5 Support Pack 6 - Internal Release
PVER: 6.50.06
Server BMMH01 halted Tuesday, 23 March 2010 10:57:37.119 am
Abend 1 on P00: Server-5.70.06: Page Fault Processor Exception (Error code 00000000)
Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = 1B8A5FFA EBX = 222E40A8 ECX = FFFFB5F6 EDX = 1B8A440A
ESI = 1B8A4EB2 EDI = FFFFC73E EBP = 1B8A15E4 ESP = 8AE58E14
EIP = 1195093C FLAGS = 00010012
1195093C 385006 CMP [EAX+06]=?, DL
EIP in PROXY.NLM at code start +000CC93Ch
Access Location: 0x1B8A6000
The violation occurred while processing the following instruction:
1195093C 385006 CMP [EAX+06], DL
1195093F 744C JZ 1195098D
11950941 385007 CMP [EAX+07], DL
11950944 7451 JZ 11950997
11950946 83E908 SUB ECX, 00000008
11950949 0508000000 ADD EAX, 00000008
1195094E 83F908 CMP ECX, 00000008
11950951 73CC JNB 1195091F
11950953 0BC9 OR ECX, ECX
11950955 7408 JZ 1195095F
Running process: Server 11 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 8AE58F60
OS Stack limit: 8AE51020
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: 118CD415 (PROXY.NLM|PLD_ParseHTTPHeaders+435)
--1B8A4EB2 ?
--FFFFC73E ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000A6A (LOADER.NLM|KernelAddressSpace+A6A)
--1327FA48 ?
--0000000C (LOADER.NLM|KernelAddressSpace+C)
--1B8A15E4 ?
--222E40A8 ?
1191031B (PROXY.NLM|SSLLoginWithFormDataCallback+36B)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--222E40A8 ?
--1B8A15E4 ?
--0000000C (LOADER.NLM|KernelAddressSpace+C)
--8AE58E78 ?
--8AE58EE4 ?
1191DF79 (PROXY.NLM|tsw_ssl3_ReadRecord+239)
--98994F6E ?
--1560BD04 ?
--1B8A15F0 ?
1191DFD4 (PROXY.NLM|tsw_ssl3_ReadRecord+294)
--1B8A15F0 ?
--8AE58E78 ?
--00000014 (LOADER.NLM|KernelAddressSpace+14)
--0000000C (LOADER.NLM|KernelAddressSpace+C)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--3935A2FF ?
--097478C7 ?
--A1C483D4 ?
--00000008 (LOADER.NLM|KernelAddressSpace+8)
--00000014 (LOADER.NLM|KernelAddressSpace+14)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--1B8A15F0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000028 (LOADER.NLM|KernelAddressSpace+28)
--222E40A8 ?
--00000028 (LOADER.NLM|KernelAddressSpace+28)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--0000000C (LOADER.NLM|KernelAddressSpace+C)
--1327FA48 ?
--222E40A8 ?
11910D85 (PROXY.NLM|SSLRedirectDataCallback+235)
--222E40A8 ?
--00000028 (LOADER.NLM|KernelAddressSpace+28)
--8AE58EE4 ?
--00000003 (LOADER.NLM|KernelAddressSpace+3)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--898E039B ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000028 (LOADER.NLM|KernelAddressSpace+28)
--0000000C (LOADER.NLM|KernelAddressSpace+C)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--222E40A8 ?
--00000017 (LOADER.NLM|KernelAddressSpace+17)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--1B8A15E4 ?
--00004800 (LOADER.NLM|KernelAddressSpace+4800)
--222E40A8 ?
119078CD (PROXY.NLM|TSW_SSL_Read+2D)
--1560BD04 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--1B8A15E4 ?
--1B8A15F0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--0000000C (LOADER.NLM|KernelAddressSpace+C)
--0000000C (LOADER.NLM|KernelAddressSpace+C)
--1B8A15E4 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--222E40A8 ?
1190EF88 (PROXY.NLM|SSL_V3_ServerDataReplyHandler+158)
--222E40A8 ?
-1197D604 (PROXY.NLM|rsSSL_V3_ServerWaitingForRequest+0)
--1560BD04 ?
--222E40A8 ?
--0347E701 ?
--0F78E700 ?
118E9400 (PROXY.NLM|CallrsCallBacks+0)
118E9454 (PROXY.NLM|CallrsCallBacks+54)
--222E40A8 ?
00362862 (SERVER.NLM|StartWorkToDo+23)
--222E40A8 ?
--0347E701 ?
--0F78E700 ?
--8AE18E30 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
0021459A (SERVER.NLM|WorkerThread+4F6)
--222E40A8 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8ADA5400 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8ADA5400 ?
00221528 (SERVER.NLM|TcoNewSystemThreadEntryPoint+40)
--8ADA5400 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
Additional Information:
The CPU encountered a problem executing code in PROXY.NLM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.
Kindly suggest.

In article <[email protected]>, Dkeyur wrote:
> Netware 6.5 SP6
> BorderManager 3.9 SP2 (with latest proxy.nlm)
> Server has 4 GB memory
>
> Additional Info: The server is patched with the latest TCP & Winsock
>
Is the above correct? If so, you are not even close to having the
latest patches. (NW65SP8, not SP6). Adding late tcp and winsock
patched to SP6 would probably cause problems.
If you look over the abend messages, and some of them refer to an LSL
component, it's very likely you need the wsock6o patch. (Check tip #1
at the URL below).
If you just typo'd the patch, and you are at sp8, at least try clearing
the cache. Unload proxy, load proxy -cc.
Craig Johnson
Novell Knowledge Partner
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

How to configure SharePoint HNSC with a reverse proxy server so that HNSC Share Point URLs are not exposed to end users.

Could you please let me know how SharePoint HNSC can be configured with a reverse proxy server so that HNSC Share Point URLs are not exposed to end users.
In normal path based site collections/web applications, reverse proxy configuration can be done using alternate access mappings with Public URL = "proxy URL", internal = "HNSC Share Point URL" so that share point sends response back
to Public URL = "proxy URL".
In Host Named Site Collections, alternate access mappings are not supported. Each HNSC is designed to have only one URL in each zone. Zone is one of the five zones(Default,Intranet,Internet,Custom,Extranet) with each of which only one alternate
URL is associated. This is what we are able to get using power shell command "Set-SPSiteUrl", but this will not help us to get the response back to proxy URL after a request sent to share point because we could not find any mechanism in share
point HNSC to respond to a different URL(proxy URL). Consequently, Share Point URLs are exposed to external users.
Below share point article in MSDN blog is symmetrical to what we are observing with Share Point 2013 and Proxy Server. It mentions that internal HNSC URLs can’t be hidden using any proxy server. If hiding the internal Share Point URLS is a requirement,
it suggests to use a web application instead of host named site collections.
Though I’m also observing the same behavior with Share Point 2013 HNSC, Could you please confirm my understanding is correct.
http://blogs.msdn.com/b/kaevans/archive/2012/03/27/what-every-sharepoint-admin-needs-to-know-about-host-named-site-collections.aspx
Excerpt from above article-
"Host Named Site Collections Only Use One Host Name
Continuing on the discussion on AAMs and host named site collections, you cannot use multiple host names to address a site collection in SharePoint 2010. Because host-named site collections have a single URL, they do not support alternate access mappings and
are always considered to be in the Default zone. This is important if you are using a reverse proxy to provide access to external users. Products like Unified Access Gateway 2010 allow external users to authenticate to your gateway and access a site
as http://uag.sharepoint.com and forward the call to http://portal.sharepoint.com. Remember that URL rewriting is not permitted. Further, a site collection can only respond to one host name. This means if you are using a reverse proxy, it must forward the
calls to the same URL. If your networking team has a policy against exposing internal URLs externally, you must instead use web applications and extend the web application using an alternate access mapping."<u5:p></u5:p>

Hi Satish,
You are right that only one URL is allowed for each zone of the host-name site collections in both SharePoint 2010 and SharePoint 2013.
It is by design that each host-name site collection only support one URL for each zone.
The article below is about RTM version of SharePoint, and it is the same for SharePoint 2013 with the latest CU.
https://support.microsoft.com/en-us/kb/2826457
So to make the URL of HNSC not exposed to external users is not supported, you need to use path-based sites instead.
Best regards.
Thanks
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Safari cannot open the page ~ The error was: "There was a problem communicating with the web proxy server (HTTP)

Help! I was cruzing along just fine and went out tonight only to receive the message above:
Cannot open Page
Safari cannot open the page
The error was: "There was a problem communicating with the web proxy server (HTTP)."
I have had all the Apple iPhone phone. Have never encountered anything like this.
All systems are GO as soon as I log on to wifi.
Can anyone help, please.

I am also fixed. I also loaded Onavo, but that was the other day ... this is what I did with the help of online chat with AT&T ...
I went to:
Settings
Wifi
I selected the network I was working on by hitting the blue arrow located on right side
At the detail page of that network I scolled down to the bottom to find HTTP Proxy boxes
I was on Off and changed it to Auto and it worked!
I was soo jazzed!!
Instructions said if it was already on AUTO, to change it to Manual and make your Port = 80 but I didn't have to do that!
YIPPIE!! I'm a new man!!
Go to settings -----> WI-FI -----> select the network you're using ------> hit the blue arrow located on the right-side of the network name (ie: show details of that network), this takes you to another page.
--------> at the bottom of the page you'll see "HTTP Proxy" boxes (located below the "renew lease" button) ---------------> change the proxy to AUTO. Note: if you're already at AUTO, change it to "Manual" and make your Port = 80.

Remote Resources: "A problem with the system proxy caused the connection to fail: End of file"

Hi, I am trying to use "Remote Resources" on the current version of the Microsoft Remote Desktop for Android app, I can input the webfeed and it even shows the apps that I have configured on the server for "Remote App", sadly whenever
I try to load any of the RemoteApps, I receive an error stating " A problem with the system proxy caused the connection to fail. End of File".
I don't know what I can do to fix this, I've tried many things to no avail, also, normal Remote Desktop connections from the Microsoft Android app work flawlessly to the server.
The relevant log is the following:
[2014-Jan-09 04:40:54] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Jan-09 04:40:54] RDP (0): Final rdp configuration used: memory bookmark [
label
hostname DIAZSERVER
port 3389
loadbalanceinfo
ui.swapmousebutton false
remote.program ||ZWaveUtil
remote.workingdirectory
remote.name ZWave Adapter Utility
remote.args
rail true
soundmode 0
connect_to_console false
redirectsdcard true
performance_flags 134
arc.sessionid 0
anonymous_username
authentication_level 2
use_redirection_server_name false
username administrator
gateway [
host = DIAZSERVER
port = 443
bypass = false
connect info[
hostnames = [localhost]
gatewayHost = DIAZSERVER
gatewayPort = 443
routingToken = Cookie: mstshash=administrator
redirectionGUID =
proxyHost = 200.5.68.10
proxyPort = 8080
sessionId = -1
[2014-Jan-09 04:40:54] RDP (0): Using HttpConnect proxy at 200.5.68.10:8080
[2014-Jan-09 04:40:54] RDP (0): Using Basic Authentication with username ''
[2014-Jan-09 04:40:54] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
AsioEndpointContext (0): startup(): starting up down context
[2014-Jan-09 04:40:54] RDP (0): Resolved '200.5.68.10' to '200.5.68.10' using NameResolveMethod_DNS(1)
[2014-Jan-09 04:40:54] RDP (0): Resolved '200.5.68.10' to '200.5.68.10' using NameResolveMethod_DNS(1)
ASIOSocketAdapter (9): readSomething error. message: End of file. instance: 0x5d39d5c0
RpcOverHttp (9): Stream error in endpoint 0x5abbc170 : A problem with the system proxy caused the connection to fail: End of file
[2014-Jan-09 04:40:55] RDP (0): Error message: A problem with the system proxy caused the connection to fail: End of file
[2014-Jan-09 04:40:55] RDP (0): Error message: A problem with the system proxy caused the connection to fail: End of file
[2014-Jan-09 04:40:55] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
ASIOSocketAdapter (9): handleRead(): exception: Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
    User Message : Failed to read from channel: -1. instance: 0x5d39d5c0
[2014-Jan-09 04:40:55] RDP (0): Disconnect initiated by client
RpcOverHttp (9): Exception in endpoint 0x5abbc170 : Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
    User Message : A problem with the system proxy caused the connection to fail: Failed to read from channel: -1
[2014-Jan-09 04:40:55] RDP (0): Exception caught: Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
    User Message : A problem with the system proxy caused the connection to fail: Failed to read from channel: -1
[2014-Jan-09 04:40:55] RDP (0): Exception caught: Exception in file '/var/lib/jenkins/jobs/rc-android-app/workspace/rdp-layer/library/jni/librdp/private/httpendpoint.cpp' at line 489
    User Message : A problem with the system proxy caused the connection to fail: Failed to read from channel: -1
AsioEndpointContext (0): shutdown(): shutting down context
AsioEndpointContext (0): shutdown(): context shut down
AsioEndpointContext (0): shutdown(): shutting down context
AsioEndpointContext (0): shutdown(): context shut down
[2014-Jan-09 04:40:57] RDP (0): ------ END ACTIVE CONNECTION ------

My problem is that the "proxy" is the proxy set up by my 3G configuration so, I tried connecting to the remote resources through my work wifi and I get the following:
[2014-Jan-14 16:58:13] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Jan-14 16:58:13] RDP (0): Final rdp configuration used: memory bookmark [
label
hostname DIAZSERVER
port 3389
loadbalanceinfo
ui.swapmousebutton false
remote.program ||chrome
remote.workingdirectory
remote.name Google Chrome
remote.args
rail true
soundmode 0
connect_to_console false
redirectsdcard true
performance_flags 134
arc.sessionid 0
anonymous_username
authentication_level 2
use_redirection_server_name false
username Administrator
gateway [
host = DIAZSERVER
port = 443
bypass = false
connect info[
hostnames = [localhost]
gatewayHost = DIAZSERVER
gatewayPort = 443
routingToken = Cookie: mstshash=Administrator
redirectionGUID =
proxyHost =
proxyPort = 0
sessionId = -1
[2014-Jan-14 16:58:13] RDP (0): Not using any proxy
[2014-Jan-14 16:58:13] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
AsioEndpointContext (0): startup(): starting up down context
ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d474090
RpcOverHttp (9): Stream error in endpoint 0x5d46b678 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 16:58:17] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d445158
RpcOverHttp (9): Stream error in endpoint 0x5d49fa30 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 16:58:17] RDP (0): Disconnect initiated by client
[2014-Jan-14 16:58:17] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
AsioEndpointContext (0): shutdown(): shutting down context
AsioEndpointContext (0): shutdown(): context shut down
AsioEndpointContext (0): shutdown(): shutting down context
AsioEndpointContext (0): shutdown(): context shut down
[2014-Jan-14 16:58:17] RDP (0): ------ END ACTIVE CONNECTION ------
Now, I know the host can be resolved because: if I connect to the same host but on a full remote desktop (as opposed to just RemoteApp on it) I have no trouble either through 3G OR through my work connection.
Moreover, I also tried directly inputting the IP as opposed to the web address of my server, I get the same error, that is the Remote Resources tab is able to access the feed (because it shows the available RemoteApps) but when I click an app it says it can't
find the Host, here's the log for the connection directly to the IP address/rdweb/feed/webfeed.aspx :
[2014-Jan-14 17:09:27] RDP (0): ----- BEGIN ACTIVE CONNECTION -----
[2014-Jan-14 17:09:27] RDP (0): Final rdp configuration used: memory bookmark [
label
hostname DIAZSERVER
port 3389
loadbalanceinfo
ui.swapmousebutton false
remote.program ||chrome
remote.workingdirectory
remote.name Google Chrome
remote.args
rail true
soundmode 0
connect_to_console false
redirectsdcard true
performance_flags 134
arc.sessionid 0
anonymous_username
authentication_level 2
use_redirection_server_name false
username administrator
gateway [
host = DIAZSERVER
port = 443
bypass = false
connect info[
hostnames = [localhost]
gatewayHost = DIAZSERVER
gatewayPort = 443
routingToken = Cookie: mstshash=administrator
redirectionGUID =
proxyHost =
proxyPort = 0
sessionId = -1
[2014-Jan-14 17:09:27] RDP (0): Not using any proxy
[2014-Jan-14 17:09:27] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
AsioEndpointContext (0): startup(): starting up down context
ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d372f28
RpcOverHttp (9): Stream error in endpoint 0x5dd6b168 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 17:09:31] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
ASIOSocketAdapter (9): handleResolve(): boost error: Host not found. Please provide the fully-qualified name or the IP address of the host.. instance: 0x5d378de0
RpcOverHttp (9): Stream error in endpoint 0x5e9cc1f0 : Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
[2014-Jan-14 17:09:31] RDP (0): Disconnect initiated by client
[2014-Jan-14 17:09:31] RDP (0): Error message: Unable to connect to remote PC. Please provide the fully-qualified name or the IP address of the remote PC, and then try again.
AsioEndpointContext (0): shutdown(): shutting down context
AsioEndpointContext (0): shutdown(): context shut down
AsioEndpointContext (0): shutdown(): shutting down context
AsioEndpointContext (0): shutdown(): context shut down
[2014-Jan-14 17:09:31] RDP (0): ------ END ACTIVE CONNECTION ------
I'm really puzzled here, I've tried checking if ports where open, and ports 443 and 3389 are wide open, I don't know what else it could be.

Help with Apache Reverse Proxy configuration with SAP Portal and SAP Webgui

Dear Experts,
I have an issue configuring Apache to work with SAP Portal and ERP webgui. Accessing Portal through Reverse Proxy is working fine. But the problem arises when we try to open an iView ERP webgui transaction page from Portal with the Reverse Proxy. Have anyone implemented similar requirements and could advice on the configuration required on the Apache side? Thank you

hi,
pls check the below links for reference:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/24396589-0a01-0010-3c8c-ab2e3acf6fe2
searchsap.techtarget.com/searchSAP/downloads/chapter-december.pdf
1)Learn to implement the reverse proxy filter and portal gateway in SAP Enterprise Portal 6.0 on Web Application Server 6.40.
https:/.../irj/sdn/nw-portalandcollaboration?rid=/webcontent/uuid/006efe7b-1b73-2910-c4ae-f45aa408da5b
.2 )Configuring the Portal for Your Reverse Proxy Filter Solution . ... This document describes the reverse proxy filter mechanism in SAP Enterprise ...
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/32ad9b90-0201-0010-3c8a-c900cd685f8f
3)have full reverse proxy functionality. Possibly. filter. requests. Internet ... Reverse proxy (optionally with authentication etc.) ...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c066c390-0201-0010-3cba-cd42dfbcc8be
Note:please reward points if solution found helpfull
Regards
Chandrakanth.k

CANNOT_READ_PALOAD error with SOAP to PROXY Synchronous interface

Hi,
Problem with SOAP to PROXY Synchronous interface.
In Production client, some times we are getting the below shown error in SXMB_MONI. There is no Inbound payload also.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">CANNOT_READ_PAYLOAD</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Unable to read payload from the message object</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Please suggest me to resolve this.
Thanks in advance,
Hari.

Hi Hari,
In your case, check SAP Notes: 1082111 and 1060723.
Regards,
P.Rajesh

Can XI /PI be configured with a web proxy for outbound communication.

We have a business to business scenario. There is a firewall and web dispatcher for inbound from the partner.
I want to know if the XI system can be configured with a web proxy for any communication that is outbound from the XI system to the partner (outside the company).
Your help will not only be appreciated, but also be rewarded.
Thanks.
Param.

2 cases for the configuration of HTTP Proxy:
1) If you use an adapter type running on the ABAP Stack (table PPROXY_C) and the RFC destination SAPHTTPA must to work.
Refere to this: Simple connection to a remote HTTP Server using Port, Server, Username & Pw
2) If you use adapter running in the Adapter Engine then you have to configure the proxy for the JAVA Stack:
Refere to this: http://help.sap.com/saphelp_erp2005/helpdata/en/7c/f257422d095542e10000000a1550b0/frameset.htm
Regards,
Sandro

Error with JPR(Java Proxy Runtime) in Adapter Monitor of RWB

Dear Experts,
             I am implementing scenario with Client Java Proxy(Outbound) and Server ABAP Proxy(Inbound). We have done all the designing in IR and configurations in ID. We have deployed the EAR successfully. But when we go to RWB(Runtime Work Bench) to monitor the inital status of JPR in RWB->Adapter Monitor. It shows the following error.
Status     Name                                Text
Error        SLD Access                     SLD host:port = yhsapi01.yashsap.com:50000
Error getting JPR configuration from SLD. Exception: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=yhsapi01 SYSNR=00 GWHOST=yhsapi01 GWSERV=sapgw00 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR max no of 100 conversations exceeded
TIME Wed Jun 03 19:42:45 200
RELEASE 700
COMPONENT CPIC (TCP/IP) with Unicode
VERSION 3
RC 466
MODULE r3cpic.c
LINE 10713
COUNTER 5521
No access to get JPR configuration

Hi!
Obviously there are more than 100 connections opened in your system.
ERROR max no of 100 conversations exceeded
Please check your gateway settings (in ABAP you can check the parameters using transaction SMGW).
Regards,
Volker

JRE with an external proxy

I'm hoping there is someone who can give some information on using JRE (with IE plugin) with an external proxy server.
We use a web proxy service that is hosted externally and only receives web requests on port 8080. Our IE browser is configured with a PAC (automatic configuration script) file that lists two external addressses and one internal proxy address all on port 8080.
I am trying to access an externally hosted web site (with lots of Java applets) from our corporate network and this fails when using an external proxy service.
Using JRE 1.4.2 we did a network trace and can see a request going to the external proxy on port 8080 but whatever the response is or what the JRE receives back, it doesn't like it and tries the next proxy address in the list and fails to connect.
In the JRE console, I see the following text when the connection fails (real addresses replaced)
Ping the proxy server <external proxy IP #1> on port 8,080
Proxy server <external proxy IP #1> on port 8,080 can not be reached
Ping the proxy server <external proxy IP #2> on port 8,080
Proxy server <external proxy IP #2> on port 8,080 can not be reached
Ping the proxy server <internal proxy IP > on port -1
Proxy server <internal proxy IP > on port -1 can not be reached
Does anyone know what the 'Ping the proxy server' is trying to do to detect the external proxy server? Whatever it is, it doesn't like the external ones and only works with the internal one. I'm assuming this is not a simple ICMP ping as the network trace shows a TCP request on port 8080 going to the external proxy and nothing coming back. I would like to know if it could be something the external proxy is blocking (so I could ask the supplier to change). I've looked at a good trace just using the internal proxy but can't see what type of response JRE accepts.
Later versions of JRE have the same issue except they resolve the last proxy (the internal one) correctly and still won't use the external proxies.
If there is anyone who can advise me on this or point me in the direction of some documention I would be very grateful.
-Steve

aseemfromnyc wrote:
is it possible to stream the contents of the hard drive to the hdtv witht the hard drive
Yes, add them to iTunes. The fact that they are on an external doesn't stop them from being in iTunes.
If necessary, create a separate library which you just use when you have the external connected.
Alternatively, if you have an iPhone or iPad you could check out an App like Air Video, which displays video that isn't in iTunes on your device. I think you can then use Airplay to get it onto your ATV.

Hasn't anyone out here worked with cut-through proxy

hasn't enyone out here worked with cut-through proxy with acs. is there no one out here to help me out with cut-through proxy.
sebastan

Hi Sebastan,
For your case, what's the scenario looks like?
Rgds,
AK

Repicat Parrallelized group abending with Errors

We recently paralleled our replicats using the RANGE function, Since then we have been seeing the replicat process getting abended with the following WARNINGS:
OGG01004 - Oracle GoldenGate Delivery for Oracle, XXXX.prm: Aborted grouped transaction on 'SCHEMA.TABLE123', Database error 54 (ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired, SQL TRUNCATE TABLE "SCHEMA"."TABLE123").
OGG01668 - Oracle GoldenGate Delivery for Oracle, XXXX.prm: PROCESS ABENDING.
OGG01296 - Oracle GoldenGate Delivery for Oracle, XXXX.prm: Error mapping from SCHEMA.TABLE123 TO SCHEMA.TABLE123.
On restarting the abended process, it starts without any issue and the lag is being caught up pretty quick. The truncate operation is performed on the source and we have the GETTRUNCATES parameter inside the parameter file. We never had this issue when the replicat was not parallelized. This started only after the parallelization is done.
Any idea or some one who have seen similar scenarios earlier?
Thank You.

We recently paralleled our replicats using the RANGE function, Since then we have been seeing the replicat process getting abended with the following WARNINGS:
OGG01004 - Oracle GoldenGate Delivery for Oracle, XXXX.prm: Aborted grouped transaction on 'SCHEMA.TABLE123', Database error 54 (ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired, SQL TRUNCATE TABLE "SCHEMA"."TABLE123").
OGG01668 - Oracle GoldenGate Delivery for Oracle, XXXX.prm: PROCESS ABENDING.
OGG01296 - Oracle GoldenGate Delivery for Oracle, XXXX.prm: Error mapping from SCHEMA.TABLE123 TO SCHEMA.TABLE123.
On restarting the abended process, it starts without any issue and the lag is being caught up pretty quick. The truncate operation is performed on the source and we have the GETTRUNCATES parameter inside the parameter file. We never had this issue when the replicat was not parallelized. This started only after the parallelization is done.
Any idea or some one who have seen similar scenarios earlier?
Thank You.

Replacing MS ISA proxy with IronPort WSA proxy - ISA firewall client?

Replacing MS ISA proxy with IronPort WSA proxy - what about the ISA firewall client?
Does Cisco have an equivalent of the Microsoft ISA Firewall Client?
How does WSA handle complex protocols (such as ftp) through the proxy server?

We are replacing MS ISA proxy servers with IronPort WSA S370 proxy servers.
We have several apps that make use the MS firewall client.
The MS firewall client enables HTTP-tunneling of TCP & UDP through the ISA proxy servers instead of going through firewalls.
These apps use various ports - and there are rules setup on the ISAs specifially for these apps and their ports.
Also we have serveral uses of RPD, telnet, and SSH using the firewall client to HTTP-tunnel through the proxy servers -- and these have specific ISA rules setup for them too.
I can find HTTP-tunneling software - commercial and freeware - but can't find any that I think will work through the IronPort WSA S370 proxy servers.
Would like to find someone who has implemented HTTP-tunneling using IronPort WSA 370 proxy servers.
Thanks again for your input.

Lync answer with SIP 491 - Proxy Side Reinvite Failed, pass result to GW when we try to make a RE-INVITE.

Hello,
In some cases, the gateway I'm using try to make a Reinvite (to update media Info) but Lync always reject this with SIP 491 Proxy side reinvite failed, pass result to GW.
Did anyone had this error before?
After this message should we try to send again the Reinvite? I'm using Lync without REFER Support.

Hello Sean,
Thank you for the answer, when you say settings "type=friend" and "canreinvite=yes" on gateway trunk you are telling in the Lync Side configurartion using powershell command or in the device i'm using to connect to the PSTN?
At Lync Powershell commands we have the Set-CsPstnGateway with the option "Routable"
http://technet.microsoft.com/en-us/library/gg398408.aspx
Should we activate this to true? Does this influence the external call transfers made by this PSTN Gateway?

Image Upload fails with Error 407: Proxy Authentication Required

Hello,
I am trying to upload Custom Template Image, however it fails with error :(407) Proxy Authentication Required message. i would have to admit that i am trying this behind a Proxy Firewall. So i do really need to know how to make this work and
what is that i need to request from the Proxy team to make this working.
Thanks
TSANA

Hello TP,
Your Suggestion really helped and the upload is working. However because of the bandwidth being low, its showing 2 days. Is there any other approach to get around with this? I have also observed that, if we leave the upload over night , then it will
show that the Image upload failed with exception. I have managed to rerun the script(same script) in same window, and luckily it continues from where it had failed. This is somehow not a good thing that Microsoft did not provide an option of using Azure VM
as a template.
Thanks
Sundesh

BorderManager abends with EIP in PROXY.NLM

Similar Messages

Maybe you are looking for