IIS Application Pool fatal error when building Live Report in BPC NW 7.5

[Former Member]

We just installed BPC 7.5 NW. Repord building and some reporting features always crashes (both in Web and Excel interface), causing ASP .NET app.pool shutdown. Please help, we already checked the OSS Notes and SDN forums with no success. Thanks is advance.

Details:

When I'm building a new Live Report in BPC the editor apprears

correctly,but when I finish with the row/column settings and press OK,

the IIS .NET pool crashes. The same happens when trying to create reports using

the Excel interface.

Checking the IIS server log, found the following warnings and errors

"A process serving application pool 'ASP .NET 2.0' suffered a fatal

communication error with the Windows Process Activation Service"

And finally:

"Application pool 'ASP .NET 2.0' is being automatically disabled due to

a

series of failures in the process(es) serving that application pool."

As the application pool become disabled, the whole BPC application gets

unusable. We need to restrat the app.pool or the entire server to get

back the to the BPC.

We have Windows2008R2 64bit Server for the MS components.

Tried to apply the Note 1531023 but did not help.

Steps to reproduce:

1. Start BPC client, (default AppSet)

2. Start Interface for the Web

3. Start Live reporting

4. Build a report drag&drop

5. Set row and column dimensions

6. Press OK.

(No response from this point on)

[Former Member]

Has the problem been solved?

We are from this thread and have the same problems.

Yet, previous post from Rizwan was helpful and with this we appeared to be able to run application pool (because it hasn't been working - now it's ok). But IIS doesn't - IIS throws two errors when BPC client try to download dimension from server:

1) A process serving application pool 'ASP .NET 2.0' terminated unexpectedly. The process id was '2056'. The process exit code was '0xc0000374'

2) A process serving application pool 'ASP .NET 2.0' suffered a fatal communication error with the Windows Process Activation Service. The process id was '3948'. The data field contains the error number.

We would highly appreciate if author provide a bit information about the problem

[Former Member]

This issue has not been resolved, but we managed to overcome it.

To help others facing such issue here are the details:

- We analyzed and found the .NET infrastructure is OK.

- We realized, that every time such error pops up an ABAP short dump happens, referring to a missing table error. We debugged the ABAP side without any reasonable outcome.

- We realized, that we bump into this error only if we use the standard (default) dimensions.

At the end of day we decided not to use any standard dimension in our Appset despite the fact we copied it from AppShell. This was the only way we could eliminate the issue.

[Former Member]

Balázs Kovács,

You could have followed the instructions taken from note 1574106. i.e.

Alter the error tolerence level of related IIS application pool by the following steps:

1. Open IIS manager and navigate to "Application Pools"

2. Select the application pool "ASP .NET 2.0" (which hosted BPC web site), and click the "Advanced Settings..."

3. Change the setting of "Maximum Failures" from "5" to a larger number, for instance, "500".

Hope this will help.

Award points.

Regards,

Rizwan