topic Re: aCC runtime: ERROR: _main() not called. in Operating System - HP-UX

aCC runtime: ERROR: _main() not called.

Joydeep_1 — Wed, 16 Jan 2002 07:15:32 GMT

Hi Gurus,

I was trying to install Netscape Application Server in one of our HP-UX 11 Server. During installation I am getting follwoing error message.
aCC runtime: ERROR: _main() not called.

I am attaching screenshot also.

Proceeding with installation of Netscape Application Server (NAS)...

Reading userinput log file ..... done
aCC runtime: ERROR: _main() not called.

1. Register NAS Deployment Manager
2. Make Database Access Parameter registry entries
3. Register NAS, Java & C++ engines 4. Register NAS dynamically loadable modules
5. Update Application Server startup scripts 6. Register NAS DLM
7. Extract Java JDK 1.1.8 into /opt/java 8. Register NAS sample applications 9. Register Transaction Manager 10. Register NAS in the Directory Server 11. Configure Administrative Assistant (NASA) 12. Application Server ACL registration
-----------------------------------------------------
0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
| | | | | | | | | | |
2. aCC runtime: ERROR: _main() not called. aCC runtime: ERROR: _main() not called.

What could be problem ?

Regds
Sandip

Re: aCC runtime: ERROR: _main() not called.

Steve Steel — Wed, 16 Jan 2002 07:33:05 GMT

Hi

Indicates a problem in the application,talk to the supplier.

The change in behavior is a result of tighter error checking by the aC++
support libarary by a direct request of a strategic partner , and
indicates a defect in the application.
The support library function _main() must be called by all C++
applications to assure that static constructors and destructors are
called. If main() [ie, the user-defined function main()] is
compiled by aCC, this is done automatically. However, if main() is
compiled by the C compiler, user code must call _main() explicitly.

Your a.out indicates there are destructors to execute and it may abort
anyway since the constructors were never called.

This error did
not occur prior to patch PHSS_20055

Steve Steel

Re: aCC runtime: ERROR: _main() not called.

Animesh Chakraborty — Wed, 16 Jan 2002 07:56:16 GMT

Hi Sandip,
See the link
http://us-support3.external.hp.com/cki/bin/doc.pl/sid=cf0f1cf605e4ebc6f4/screen=ckiDisplayDocument?docId=200000054317188

Netscape has discontinued development and support for the Netscape Application Server 1.5 product. For details, please see the Netscape Application Server 1.5 End of Life Statement located at:

http://help.netscape.com/products/eol/server/nas15eol.html

Re: aCC runtime: ERROR: _main() not called.

Anoop_2 — Fri, 08 Feb 2002 10:53:30 GMT

Hi Animesh,

This link you have provided mentions 2 things:

1. The functionality of the cryptoki.sh is not impacted.
While this is certainly true, the original error message
comes while configuring the Web Server plug-in (at the
same point as mentioned by Sandip) . This functionality
is certainly impacted, because after the install the iAS
gives an error. I have appended the WebServer logs at the
end.

2. Support for iAS1.5 has been withdrawn. But the same
problem also exists in iAS 6.0 SP1.

Also, while installing on HP an error message of 'nawk not
found' is generated. The only option seems to be to create
a nawk file and link it to /usr/sbin/awk, since nawk is not
supported on HP-UX.

We are working on HP11 800, iWS 4.1SP3, iAS6.0SP1

Thanks,
Anoop

[07/Feb/2002:18:01:16] info ( 1061): gxrequest reports: ve
[THDR]EHTTP_HOST=192.168.100.44:12080
[THDR]EHTTP_USER_AGENT=Mozilla/4.72 [en] (X11; I; HP-UX B.11.00 9000/800)
[THDR]EHTTP_ACCEPT_LANGUAGE=en
[THDR]EHTTP_ACCEPT_ENCODING=gzip
[THDR]EHTTP_ACCEPT_CHARSET=iso-8859-1,*,utf-8
[THDR]ECOOKIE_ENABLED=0

[07/Feb/2002:18:01:16] warning ( 1061): gxrequest reports: Try MakeServerConnection(192.168.100.44, 10818)
[07/Feb/2002:18:01:16] info ( 1061): conn reports: new connection (conn 0x4078e2b0, sock 34, host 0xc0a8642c, port 10818)
[07/Feb/2002:18:01:16] info ( 1061): MakeServerConnection reports: Spawning listener for connection 1081664176
[07/Feb/2002:18:01:16] info ( 1061): GetNext reports: Return connection at 0
[07/Feb/2002:18:01:16] warning ( 1061): for host 192.168.100.44 trying to GET /NASApp/fortune/fortune, gxrequest reports: retry on alternative server[0xc0a8642c,10818]
[07/Feb/2002:18:01:16] warning ( 1061): gxrequest reports: Try MakeServerConnection(192.168.100.44, 10818)
[07/Feb/2002:18:01:16] info ( 1061): GetNext reports: Return connection at 0
[07/Feb/2002:18:01:16] warning ( 1061): gxrequest reports: MakeServerConnection succeeded
[07/Feb/2002:18:01:16] info ( 1061): for host 192.168.100.44 trying to GET /NASApp/fortune/fortune, gxrequest reports: request start [0xc0a8642c:10818]
[07/Feb/2002:18:01:16] info ( 1061): gxrequest reports: Sending req 0 to kxs
[07/Feb/2002:18:01:16] info ( 1061): conn reports: sent 1186 bytes
[07/Feb/2002:18:01:16] info ( 1061): conn reports: sent 1186 bytes (GXConn::SendBuffer) (conn 0x4078e2b0, sock 34, host 0xc0a8642c, port 10818)