Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

...

Summary1

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.
Through this framework, we can connect to SQL Server, Oracle DB, and SQLite as a black box without knowing and caring about the lower-level details.

SAP Logon through RFC ports

SAP-Router used: 3299 + 3399

No SAP-Router used: 32<NN> + 33<NN>

Image Removed

(NN = your Instance Number /System Number)

Possible connection symptoms

Error1

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

Solution1

SAP Logon through RFC ports

SAP-Router used: 3299 + 3399

No SAP-Router used: 32<NN> + 33<NN>

Image Added

(NN = your Instance Number /System Number)

...

Summary

SAP Message Server Ports (SAPMS)

...

Error2

Note
ERROR service '?' unknown

...

Solution2

(Admin rights needed) Paste the complete content of the following text file ( services.txt ) into your services file located at: "..\Windows\System32\drivers\etc" 

...

Make sure to add a single line break at the very end of your service file.

...

Error3

Note

ERROR "service sapms<SID> unknown"

...

Solution3

(Admin rights needed) Paste the following line to your services file located at: "..\Windows\System32\drivers\etc"

...

Code Block
sapmsECC  3600/tcp


(NN = your Instance Number /System Number)

Note

Be advised, the Docu Performer (DP) 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.

...

6400 (Central Management Server)

6405 (Connection server Business Objects)

...

HANA ports

80<instance number>

(NN = your Instance Number /System Number)

...

Further information