Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

'AppeonAppPool' suffered a fatal communication error

2 posts in Appeon (partner product) Last posting was on 2012-05-03 09:35:10.0Z
sa Posted on 2012-04-26 09:11:19.0Z
From: SA
Newsgroups: sybase.public.appeon
Subject: 'AppeonAppPool' suffered a fatal communication error
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <>
Date: 26 Apr 2012 02:11:19 -0700
X-Trace: forums-1-dub 1335431479 (26 Apr 2012 02:11:19 -0700)
X-Original-Trace: 26 Apr 2012 02:11:19 -0700,
Lines: 17
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:2960
Article PK: 21972

I've installed installed 64-bit Appeon on Windows 2008. I'm
getting following error when I access AEM:

Encounter Unexpected Error
Error Message:
Error occurred when loading
C:\inetpub\wwwroot\Appeon\AEM\config\server.config file!
A process serving application pool 'AppeonAppPool' suffered
a fatal communication error with the Windows Process
Activation Service. The process id was '5812'. The data
field contains the error number.

How can I solve this problem?

Steven Posted on 2012-05-03 09:35:10.0Z
From: steven
Newsgroups: sybase.public.appeon
Subject: Re: 'AppeonAppPool' suffered a fatal communication error
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <>
References: <>
Date: 3 May 2012 02:35:10 -0700
X-Trace: forums-1-dub 1336037710 (3 May 2012 02:35:10 -0700)
X-Original-Trace: 3 May 2012 02:35:10 -0700,
Lines: 13
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:2961
Article PK: 13675


Please try to use the following solution to solve this
1. Right click the C:\Inetpub\wwwroot folder, select the
Properties items and select the Security tab page;
2. Add Everyone group if it is not listed in the box "Group
or user names";
3. Grant Full Control permission to the everyone group.
4. restart the IIS