Standalone Reports Server 12.2.1.3 Fails With REP-51002 Error When Start NodeManager as a Windows Service
(Doc ID 2551565.1)
Last updated on MAY 25, 2023
Applies to:
Oracle Reports Developer - Version 12.2.1.3.0 and laterOracle Forms for OCI - Version 12.2.1.4.0 and later
Information in this document applies to any platform.
Symptoms
You are running Reports 12.2.1.3 on Windows, and encountering issue similar to symptoms described in:
Document 2136727.1 Cannot Start Standalone Reports Server 12c When Node Manager Is Started From A Windows Service
However, the bug mentioned in Document 2136727.1 was supposed to be fixed in 12.2.1.2:
BUG 22566394 - CANNOT START S/A REP SERVER USING NMSTART WHEN NM INSTALLED AS A WIN SERVICE
When attempt to start the standalone Reports Server, it does say it "started successfully"; however, the "rwdiag.bat -findAll" is not returning the standalone Reports Server when using Windows Service for Node Manager. Also, attempting to access standalone Reports Server fails with:
REP-51002: Bind to Reports Server <standalone_rep_server> failed.
6. However, the Reports Server will work if you start the Node Manager as a Non-Service; that is, directly from command line using startNodeManager.cmd.
Changes
New installation of 12.2.1.3 on Windows platform.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |