You receive an "Application has generated an exception that could not be handled" error message when you start FRx Report Manager

This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft Business Solutions-Axapta 3.0 is now part of Microsoft Dynamics AX 3.0. All references to Microsoft Business Solutions-Axapta and Microsoft Axapta pertain to Microsoft Dynamics AX.
When you start FRx Report Manager on a computer that is running Microsoft Windows Server 2003, you receive the following error message:
FRxReportManager.exe - Common Language Runtime Debugging Services.Application has generated an exception that could not be handled.Process id=0xb4c (2892), Thread id=0x9ac (2476)
This problem occurs when FRx Report Manager is installed on a computer that is running Windows Server 2003 and UNC (Universal Naming Convention) paths were specified. This problem is caused by a known issue in the Microsoft .NET Framework. A problem with zone security in the .NET Framework on Windows Server 2003 does not allow for installations that use UNC paths and that use the same installation as a client.
To resolve this problem, reinstall FRx Report Manager. Specify drive mapping instead of UNC paths. You must map a drive from each workstation to the server whether you are performing a local client installation or a custom installation.

Artikelnummer: 893260 – Letzte Überarbeitung: 01/15/2015 08:45:18 – Revision: 4.0

Microsoft Business Solutions for Analytics–FRx 6.7 Desktop, Microsoft Dynamics GP 9.0, Microsoft Business Solutions–Great Plains 8.0, Microsoft Business Solutions–Great Plains 7.5, Microsoft Dynamics SL 6.5, Microsoft Business Solutions–Solomon 6.0, Microsoft Dynamics AX 4.0, Microsoft Dynamics AX 3.0, Microsoft Dynamics NAV 4.0, Microsoft Business Solutions–Navision 3.70, FRx Financial Reporter 6.5

  • kbnosurvey kbarchive kbnavisionfrx kbsolomonfrx kbgreatplainsfrx kbaxaptafrx kberrmsg kbmbsmigrate kbprb KB893260