web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

Object Designer crash

(0) ShareShare
ReportReport
Posted on by

Hi,

I've got an error message when pressing design on table 77 Report Selections: "Internal error 2 occurred in module 11."

I am using release 6.00.32012 of the client, and it happens with the NAVW16.00,NAVE16.00.01,NAVRO6.00.01 version of the object, the W1 is ok. I tried it on several PCs and operating systems, SQL and Native, but the same error occurs.

Anyone seen this kind of error before?

Thanks.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Neville Foyn Profile Picture
    4,320 on at

    Hi

    Based on the fact that this only occurs on one table and the same error occurs from multiple clients i think it is as a result of a change to the structure of the SQL table

    We had something similar happen when there was changes made to a table directly through SQL management studio

    Please try replacing the object with a standard object from the Chronos demo database, then design on it and save compiled, if this resolves the issue try and find a backup of the system from before the problem started and restore the object from then

    If you cant find one you will need to  re-create the object customization in the new standard object

    Hope this helps

  • Community Member Profile Picture
    on at

    Hi,

    Thanks for the reply, but unfortunately it happens also with the object in the Cronus demo database (NAVW16.00,NAVE16.00.01,NAVRO6.00.01), both with the SQL Server and the native client. The NAVW16 version of the object is ok, I checked in a W1. I could create the modifications in the W1 version, but I don't want to lose any standard country specific customizations.

  • Neville Foyn Profile Picture
    4,320 on at

    Agreed, I suspect this should be logged with Microsoft directly, if it is happening on the Cronos database of your country localization is sounds like it may be a bug

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

#1
HoangNam Profile Picture

HoangNam 7

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans