Microsoft.Dynamics.Nav.Client has stopped working (2)

GoMaD
GoMaD Member Posts: 313
edited 2010-11-09 in NAV Three Tier
I had the same error message as in the following post: Microsoft.Dynamics.Nav.Client has stopped working

Scenario:
On windows server 2008 navision RTC is installed with hotfix 30806.
When we moved all the objects from our development server to the test server, after the restart of the middle tier server, nobody could open the RTC of the test server anymore.
It resulted in the error message mentioned below.

Description (XML Version):
<?xml version="1.0" encoding="UTF-16" ?>
- <WERReportMetadata>
- <OSVersionInformation>
<WindowsNTVersion>6.1</WindowsNTVersion>
<Build>7600</Build>
<Product>(0x4): Windows 7 Enterprise</Product>
<Edition>Enterprise</Edition>
<BuildString>7600.16617.amd64fre.win7_gdr.100618-1621</BuildString>
<Revision>1</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>1033</LCID>
</OSVersionInformation>
- <ProblemSignatures>
<EventType>CLR20r3</EventType>
<Parameter0>microsoft.dynamics.nav.client</Parameter0>
<Parameter1>6.0.0.0</Parameter1>
<Parameter2>4bad52df</Parameter2>
<Parameter3>Microsoft.Dynamics.Nav.Client.UI</Parameter3>
<Parameter4>6.0.0.0</Parameter4>
<Parameter5>4bad52d8</Parameter5>
<Parameter6>6f5</Parameter6>
<Parameter7>69</Parameter7>
<Parameter8>K0R55XEMOOBPB22DBJZDN4P0SFJO3U25</Parameter8>
</ProblemSignatures>
- <DynamicSignatures>
<Parameter1>6.1.7600.2.0.0.256.4</Parameter1>
<Parameter2>2057</Parameter2>
</DynamicSignatures>
- <SystemInformation>
<MID>8C5046C9-DA3F-40C8-8C8F-486E94218B2E</MID>
<SystemManufacturer>Acer</SystemManufacturer>
<SystemProductName>Aspire 8735</SystemProductName>
<BIOSVersion>V1.05</BIOSVersion>
</SystemInformation>
</WERReportMetadata>

We checked almost everything (like looking for a needle in a haystack)
and today we found the solution.

Solution:
In one of the parts of the Role Center a table was used which had code on its OnDelete trigger that referenced an "Unknown Automation" server.
And this "Unkown Automation" server variable was the reason for the error.
When we moved the code and all the needed variables (including the Automation Variable) to a separate CodeUnit and called that CodeUnit function on the OnDelete Trigger, the error disappeared.
Now, let's see what we can see.
...
Everybody on-line.
...
Looking good!

Answers

  • mihail_kolev
    mihail_kolev Member Posts: 379
    But you will get error when the OnDelete trigger is called. The Automation server must be installed on every machine. And how you compile a Codeunit (or anything) with Unknown Automation variable?
    -Mihail- [MCTS]
  • GoMaD
    GoMaD Member Posts: 313
    mihail_kolev wrote:
    But you will get error when the OnDelete trigger is called. The Automation server must be installed on every machine. And how you compile a Codeunit (or anything) with Unknown Automation variable?

    Off course, but this automation was still in development. And so it had a larger repercussions than first thought.

    I compile on the machine where we do the .NET development.
    Now, let's see what we can see.
    ...
    Everybody on-line.
    ...
    Looking good!
  • mihail_kolev
    mihail_kolev Member Posts: 379
    Now, this is reasonable :mrgreen:
    -Mihail- [MCTS]

Categories