Table of Contents |
---|
Summary
Tip |
---|
The Docu Performer connects to SAP via ERPConnect, we do not directly use any specific hard-coded ports.
How is the Docu Performer connecting to its DB? We use a third party ORM (Object-Relational Mapping) framework from DevExpress: XPO. We do not use any specific technology for the connection to the DB directly. |
Error
Docu Performer logfile writes an error:
Code Block |
---|
T:3524 Error in program 'BI Docu Performer': ======> SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
...
LOCATION CPIC (TCP/IP) on local host
ERROR internal error
...
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -1
MODULE nixxi.cpp
LINE 825
DETAIL NiIInitSocket
SYSTEM CALL WSASocket, socket
ERRNO 10022
ERRNO TEXT WSAEINVAL: Invalid argument
COUNTER 2 |
Solution
SAP Logon through RFC ports:
SAP-Router used: 3299 + 3399
No SAP-Router used: 32<NN> + 33<NN>
(NN = your Instance Number /System Number)
Summary 2
...
Tip |
---|
Are you looking for Know-How "Technology used for the connection to SAP and its DB"? |
Table of Contents |
---|
...
Summary
The connection to your SAP-System fails.
1- Error (service '?' unknown)
Note |
---|
ERROR service '?' unknown |
Solution
...
SAP Message Server Ports (SAPMS):
(Admin rights needed) Paste the complete content complete content of the following text file ( services.txt ) into your services file located at: "..C:\Windows\System32\drivers\etc"
Make sure to add a single line break at the very end of your service file.
...
2- Error (service sapms<SID> unknown)
Note |
---|
ERROR "service sapms<SID> unknown" |
...
service name cached as unknown |
Solution
(Admin rights needed) Paste the following line to your services file located at: "..C:\Windows\System32\drivers\etc"
Code Block | ||
---|---|---|
| ||
sapms<SID> 3600 36<InstanceNumber>/tcp |
Example: if your SID is ECC and your Instance number is 00 - the line looks like the following one:
Code Block | ||
---|---|---|
| ||
sapmsECC 3600/tcp |
(NN = your Instance Number /System Number)
Old:
Note |
---|
Be advised, the Docu Performer (DPthe Performer Suite (PS) needs to be restarted to load in any system changes you did. Example: You adjusted your services file or pasted new LIB RFC files into your System32 folder -> Restart your DP. If you don't restart the DP, it could happen to fail to connect successfully, even if your system parameter is now correct. |
BO ports
6400 (Central Management Server)
6405 (Connection server Business Objects)
HANA ports
80<instance number>
...
...
3- Error (Connect to SAP gateway failed)
Performer Suite log file writes an error:
Code Block | ||
---|---|---|
| ||
T:3524 Error in program 'BI Docu Performer': ======> SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed
...
LOCATION CPIC (TCP/IP) on local host
ERROR internal error
...
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -1
MODULE nixxi.cpp
LINE 825
DETAIL NiIInitSocket
SYSTEM CALL WSASocket, socket
ERRNO 10022
ERRNO TEXT WSAEINVAL: Invalid argument
COUNTER 2 |
Solution
SAP Logon through RFC ports:
- SAP-Router used: 3299 + 3399
- No SAP-Router used: 32<NN> + 33<NN>
(NN = your Instance Number /System Number)
Further information
https://help.sap.com/viewer/ports
...
Tip |
---|
Are you looking for Know-How "Technology used for the connection to SAP and its DB"? |