使用ERPConnect连接SAP时出现随机错误
本文关键字：随机 错误 ERPConnect 连接 SAP 使用 | 更新日期: 2023-09-27 18:14:43
我们在ASP中使用了ERPConnect。. NET应用程序，但有时当用户试图通过我们的应用程序连接到SAP时，我们会得到一些错误消息。
cpc - call: 'CMRCV: rc=19 LOCATION SAP-Gateway on host SERVERNAME/sapgw10 ERROR Conversation 53230591 not found TIME Wed Nov 16 13:49:58 2011 RELEASE 701 COMPONENT SAP-Gateway VERSION 2 rc 728 MODULE gwxxrdc LINE 6278 COUNTER 1277701
当通过ERPConnect打开与SAP的连接时，总是会发生这种情况。
R3Connection connection = Connection;
connection.Open(); // the error occurs here
这是相当随机的。有时候我们不会收到任何错误信息，有时候我们一天会收到20条信息。ERPConnect使用在system32文件夹中定义的librfc32.dll，其版本为7200.1.39.6461(这是最新版本)。
在我的本地开发机器(Windows 7 x86)上没有发生此问题。它总是发生在我们的生产服务器(Windows server 2008 R2)上。
你知道是什么导致了这个问题吗?
编辑(添加错误日志摘录):
* * LOCATION SAP-Gateway on host HERCULES / sapgw10 * ERROR partner 'hercules:sapgw01' not reached * * TIME Thu Nov 24 09:10:20 2011 * RELEASE 701 * COMPONENT NI (network interface) * VERSION 38 * RC -10 * MODULE nixxi.cpp * LINE 2835 * DETAIL NiPConnect2 * SYSTEM CALL connect * ERRNO 10061 * ERRNO TEXT WSAECONNREFUSED: Connection refused * COUNTER 1385122 * *****************************************************************************
GwTraceHdlInfo:
HANDLE = 137
TIME = Thu Nov 24 09:10:19 2011
SOCKET = 2108
STAT = NI_CONN_WAIT
TYPE = STREAM IPv4
OUT = 0 messages 0 bytes
IN = 0 messages 0 bytes
LOCAL = 0.0.0.0:1865
REMOTE = -
OPTIONS = BUFFERED
ni hdl = 137
type = CLIENT
net_stat = CONNECT_TO_REM_GW_PENDING
hostaddr = 100.100.103.15
accept_hostaddr = 100.100.103.15
opcode = NORMAL_CLIENT
conn opcode = REMOTE_GATEWAY
conn vers = 2
index = 10
data = 0000000000000000
ext_info = 000000000EF1D870
offset = 0
rest_len = 0
snc_forced = 0
remote gateway infos:
hostname =
hostaddr = 100.100.103.15
service = sapgw01
tpname = sapdp01
GwSelClear: clear RWC for hdl 137
NiICloseHandle: called for hdl 137 while waiting for connection
NiICloseHandle: shutdown and close hdl 137 / sock 2108
GwFreeHdlInfoMemory: free 000000000EF1D870 (ext info)
GwIFreeMemForLU_TP: freed memory for sys 10
GwListRemove: remove elem 10 from sys_r3_list
GwListRemove: 2 elems in sys_r3_list
GwListRemove: elem 10 not in sys_reg_list
GwListRemove: remove elem 10 from sys_inuse_list
GwListRemove: 104 elems in sys_inuse_list
GwUpdateClient: act_sys: 104
GwIDelR3Conn: send error message to client
GwSendRc3: send (appc_rc=CM_PRODUCT_SPECIFIC_ERROR / sap_rc=GW_CONNECT_FAILED) to client HERCULES / sapgw10 (0)
GwRqDpSendTo: (HERCULES / sapgw10, gw_id=0, appc_ca_blk=-1, len=335, comm_index=-1)
LOCK APPC ca_blk 3
DpGetCpicCommIdx: found index 3 via appc_hdr
found comm entry 3 (tid/uid/mode/conv_id/a_r: 158/13268/0/ /0)
GwIsAWaitingSWP: wp 1 waiting
GwSapWpWakeUp: send answer to sap wp 1
GwSapWpWakeUp: make wp 1 owner of appc_ca_blk 3
-OUT- tid -1 uid -1 mode 255
-OUT- appc_ca_blk 3 len 335 rq_id 43133
-OUT- wait_f_answ 0 cmd 0
NiIWrite: hdl 109 sent data (wrt=28,pac=1,MESG_IO)
GwIDelR3Conn: decrement conv_no of client 0: 5
GwFreeMemory: free 000000000EEF3480 (len=3700)
GwFreeMemory: act_overflow_size = 20352 (- 3700)
GwIDelR3Conn: idx/conv = ((-1/0) | (10/0)), delete conv 48 from conv-table
GwClearConn: conv_no/tcp_conv_no/sna_conv_no: 6/6/0
GwClearConn: free r3 conv info
GwClearConn: free buffer info
GwFiSearchConvId: deleted 27077110 local, conn=48
GwListInsert: insert elem 48 into conn_free_list (at begin)
GwListInsert: 494 elems in conn_free_list
GwListRemove: remove elem 48 from conn_search_list
GwListRemove: 0 elems in conn_search_list
GwListRemove: elem 48 not in conn_write_list
GwListRemove: remove elem 48 from conn_inuse_list
GwListRemove: 6 elems in conn_inuse_list
GwReadReqIndex: (process_id: -1)
GwReadReqIndex: no filled request-index-block
GwCheckClient: check clients
LOCK APPC ca_blk 4
GwCheckClient: raise timeout for conv 27059938 (intr/uid/mode/comm_idx=9/13261/0/90)
GwSendRcToDp: send appc_rc/sap_rc 10001/221 to dp
make DISP owner of appc_ca_blk 4
DpSemRq: key: 3, units: 1, timeout: -1
DpSemRel: key: 3, units: 1
DpRqPutIntoQueue: put request into queue (reqtype 0, prio LOW, rq_id 43134)
GwDispWakeUp: send wakeup with ni handle 2
NiIWrite: hdl 2 sent data (wrt=1,pac=1,MESG_IO)
-OUT- sender_id APPC_SERVER tid 165 wp_ca_blk -1 wp_id -1
-OUT- action SEND_TO_WP uid 13261 appc_ca_blk 4 type NOWP
-OUT- new_stat NO_CHANGE mode 0 len 80 rq_id 43134
GwListRemove: remove elem 90 from comm_wait_list
GwListRemove: 0 elems in comm_wait_list
GwListRemove: remove elem 90 from comm_wait_list
GwListRemove: 0 elems in comm_wait_list
我创建了一个小代码示例，如果注意到在最后一个连接保持打开状态。如果我再次启动示例，则在示例结束时仍有两个连接保持打开状态。一定是出了什么问题…
protected void SAP( object sender, EventArgs e ) {
ThreadStart threadStart1 = new ThreadStart( CreateSAP );
Thread thread = new Thread( threadStart1 );
Thread thread2 = new Thread( threadStart1 );
thread.Start();
Thread.Sleep( 2000 );
thread2.Start();
while ( thread2.IsAlive ) {
}
Response.Write( "done" );
}
private void CreateSAP() {
R3Connection conn = ERPConnection.Connection;
conn.MultithreadingEnvironment = true;
for ( int i = 0; i < 12; i++ ) {
try {
conn.Open();
Thread.Sleep( 1000 );
} finally {
conn.Close();
}
}
}
不幸的是，我在我的代码中做的事情不是很…恩……好了。ERPConnect有一个r3connection对象，我在整个应用程序中使用了一个单例。
如果一个用户正在使用一个连接，而另一个用户也请求一个连接，则r3connection -对象创建一个新连接(您可以通过使用SAP中的SM04-transaction来验证这一点)。如果两个用户都关闭了连接，两个连接中的一个仍然是打开的(我认为这是ERPConnect的一个错误，但是我们无法联系他们，因为我们的支持现在已经过期了)。在生产环境中，连接的限制(在SAP中定义)很快就会达到。
我现在为每个用户创建一个r3connection对象，这样我就可以确保在调用Close()方法(或使用语句)时在sap系统中正确关闭连接。
public static R3Connection Connection {
get {
ERPConnect.LIC.SetLic( "MyLicenseKey" );
R3Connection connection = new R3Connection(
[set connection settings]
);
connection.MultithreadingEnvironment = true;
return connection;
}
}
我正在寻找一个完全不同的问题的答案，但是看到我绊倒了你的，这看起来很像网络配置-确保你的SAP服务器"大神"有端口3210,3310和3610(我认为这些是正确的-可能是3201/3301/3601，很难从SMGW日志中分辨出来)在Windows防火墙中打开，没有任何其他防火墙阻止相关流量，并且"hercules"上的默认网关设置为可以成功将流量路由到100.100.103.15的设备(我假设，从您的日志中，这是运行. net应用程序的服务器的IP地址)，并且100.100.103.15上的默认网关设置为可以成功将流量路由到"hercules"的设备。此外，如果您使用完全限定的域名(例如hercules.sap.local)来连接SAP服务器，您将会有更好的运气，因为这样您就不再依赖于NetBIOS的史前变幻莫测来查找SAP服务器。