"The Service Header does not exist" error message and Microsoft Dynamics NAV crashes when you press ESC to close a form in Microsoft Dynamics NAV 2009

Applies to: Dynamics NAV 2009 Service Pack 1

This article applies to Microsoft Dynamics NAV for all countries and all language locales.

Symptoms



Consider the following scenario in Microsoft Dynamics NAV 2009 with Service Pack 1 (SP1):
  • You maximize the Service Contract form.
  • You post a service invoice in a service invoice card that is opend from a service contract through the No of Unposted Invoices field on the Invoice Details tab in the Service Contract form.
  • You press ESC to close the service invoice card.
In this scenario, you receive the following error message: 
The Service Header does not exist.

Additionally, Microsoft Dynamics NAV crashes.

Resolution


Hotfix information

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV service pack or the next version that contains this hotfix.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.




Installation information

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:
  • The Modify permission for the object that you will be changing.
  • The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.


Note You do not have to have rights to the data stores unless you have to perform data repair.

Code changes

Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.

To work around this problem, change the code in the OnAfterGetRecord trigger of the Service Document Registers form (5968) as follows: 
Existing code
CASE "Destination Document Type" OF
"Destination Document Type"::Invoice:
BEGIN
ServHeader.GET(ServHeader."Document Type"::Invoice,"Destination Document No.");
CustNo := ServHeader."Bill-to Customer No.";
CustName := ServHeader."Bill-to Name";
END;
"Destination Document Type"::"Credit Memo":
BEGIN
ServHeader.GET(ServHeader."Document Type"::"Credit Memo","Destination Document No.");
CustNo := ServHeader."Bill-to Customer No.";
CustName := ServHeader."Bill-to Name";
END;
"Destination Document Type"::"Posted Invoice":
BEGIN
ServInvHeader.GET("Destination Document No.");
CustNo := ServInvHeader."Bill-to Customer No.";
CustName := ServInvHeader."Bill-to Name";
END;
"Destination Document Type"::"Posted Credit Memo":
BEGIN
ServCrMemoHeader.GET("Destination Document No.");
CustNo := ServCrMemoHeader."Bill-to Customer No.";
CustName := ServCrMemoHeader."Bill-to Name";
END;
END;
END;
Replacement code
CASE "Destination Document Type" OF
"Destination Document Type"::Invoice:
BEGIN
IF ServHeader.GET(ServHeader."Document Type"::Invoice,"Destination Document No.") THEN BEGIN
CustNo := ServHeader."Bill-to Customer No.";
CustName := ServHeader."Bill-to Name";
END;
END;
"Destination Document Type"::"Credit Memo":
BEGIN
IF ServHeader.GET(ServHeader."Document Type"::"Credit Memo","Destination Document No.") THEN BEGIN
CustNo := ServHeader."Bill-to Customer No.";
CustName := ServHeader."Bill-to Name";
END;
END;
"Destination Document Type"::"Posted Invoice":
BEGIN
IF ServInvHeader.GET("Destination Document No.") THEN BEGIN
CustNo := ServInvHeader."Bill-to Customer No.";
CustName := ServInvHeader."Bill-to Name";
END;
END;
"Destination Document Type"::"Posted Credit Memo":
BEGIN
IF ServCrMemoHeader.GET("Destination Document No.") THEN BEGIN
CustNo := ServCrMemoHeader."Bill-to Customer No.";
CustName := ServCrMemoHeader."Bill-to Name";
END;
END;
END;
END;

Prerequisites

You must have Microsoft Dynamics NAV 2009 SP1 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

More Information


Steps to reproduce this problem
  1. Open the Service Contract form.
  2. Maximize the Service Contract form.
  3. Click the Invoice Details tab for the contract record with contract No. of "SC00007".
  4. Look up the No. of Unposted Invoices field, the Service Document Registers lookup form opens.
  5. Click Document, and then click Card to open the "Service invoice" form.

  6. Post the service invoice.
  7.   Press ESC.  
 

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.