Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The RoleTailored client crashes when you run a page and then execute an action that uses the COMMIT statement and then the PAGE.RUNMODAL statement in Microsoft Dynamics NAV 2009 SP1

The RoleTailored client crashes when you run a page and then execute an action that uses the COMMIT statement and then the PAGE.RUNMODAL statement in Microsoft Dynamics NAV 2009 SP1

View products that this article applies to.

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

↑ Back to the top

Symptoms

When you run a custom page and then execute an action that uses the COMMIT statement then the PAGE.RUNMODAL statement in the RoleTailored client of Microsoft Dynamics NAV 2009 with Service Pack 1 (SP1), you receive the following error message: 
The connection to the server has been lost. The application will close.

Additionally, the RoleTailored client crashes.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft Web site:
https://mbs.microsoft.com/support/newstart.aspx
You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft Web sites:

Partners
https://mbs.microsoft.com/partnersource/resources/support/supportinformation/Global+Support+Contacts
Customers
https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htm
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 any additional support questions and issues that do not qualify for the specific update in question.

↑ Back to the top



How to obtain the Microsoft Dynamics NAV hotfix or update files

After you request a Microsoft Dynamics NAV hotfix, a hyperlink will be sent to you in an e-mail.


The e-mail will contain a hyperlink and a password. You can use the hyperlink to download the Microsoft Dynamics NAV hotfix or the update files. When you click the hyperlink, the File Download – Security Warning dialog box opens. Then, you are prompted to run, to save, or to cancel the download.


If you click Run, the files start the download and the extraction process. You must specify a folder for the new files, and then provide the password.


If you click Save, you must specify a path for saving the compressed file. When you open the file that you saved, you are prompted to specify a path for the files. Then, you must provide the password provided in the e-mail.


If you click Cancel, the download process stops.



How to install a Microsoft Dynamics NAV hotfix or an update file

The Microsoft Dynamics NAV platform hotfixes and updates are made available as single files. To install a Microsoft Dynamics NAV hotfix or an update, you must replace the existing Microsoft Dynamics NAV installation files with the hotfix or the update files. To do this, follow these steps.

Step 1: Replace the files in the Microsoft Dynamics NAV Classic Client installation

In the Microsoft Dynamics NAV Classic Client installation, replace the following files by using the hotfix or the update file.
File nameFile versionFile sizeDateTimePlatform
Dbm.dll6.0.31143.0427,84804-Jun-201015:34x86
Fin.exe6.0.31143.012,630,34404-Jun-201015:39x86
Finhlink.exe6.0.31143.0452,43204-Jun-201015:39x86
Finsql.exe6.0.31143.012,752,20804-Jun-201015:39x86
Nc_netb.dll6.0.31143.096,59204-Jun-201015:34x86
Nc_tcp.dll6.0.31143.098,64004-Jun-201015:34x86
Nc_tcps.dll6.0.31143.0141,13604-Jun-201015:34x86
Ndbcs.dll6.0.31143.01,350,48004-Jun-201015:33x86
Slave.exe6.0.31143.0152,40004-Jun-201015:34x86
To replace the existing Microsoft Dynamics NAV files, follow these steps:
  1. Close the Microsoft Dynamics NAV Classic Client.
  2. Locate the Microsoft Dynamics NAV Classic Client installation directory. The Microsoft Dynamics NAV Classic Client is usually installed in the following directory:
    C:\Program Files\Microsoft Dynamics NAV\60\Classic
  3. Copy the files that you downloaded.
  4. Paste the files that you downloaded into the Microsoft Dynamics NAV Classic Client installation directory.
  5. Click Yes to overwrite the files in the directory.

Step 2: Replace the files in the Microsoft Dynamics NAV RoleTailored client installation

In the Microsoft Dynamics NAV RoleTailored client installation, replace the following files by using the hotfix or the update file.
File nameFile versionFile sizeDateTimePlatform
Microsoft.dynamics.framework.patterns.dll1.3.10803.22471,65604-Jun-201006:30x86
Microsoft.dynamics.framework.ui.dll1.3.10803.224698,32804-Jun-201006:30x86
Microsoft.dynamics.framework.ui.mapping.dll1.3.10803.224104,42404-Jun-201006:30x86
Microsoft.dynamics.framework.ui.navigation.dll1.3.10803.22434,80004-Jun-201006:30x86
Microsoft.dynamics.framework.ui.ux2006.dll1.3.10803.22488,04004-Jun-201006:30x86
Microsoft.dynamics.framework.ui.ux2006.winforms.dll1.3.10803.22463,48004-Jun-201006:30x86
Microsoft.dynamics.framework.ui.windows.dll1.3.10803.22483,94404-Jun-201006:30x86
Microsoft.dynamics.framework.ui.winforms.controls.dll1.3.10803.2242,115,58404-Jun-201006:30x86
Microsoft.dynamics.framework.ui.winforms.dll1.3.10803.224690,15204-Jun-201006:30x86
Microsoft.dynamics.nav.client.builder.dll6.0.31143.0198,54404-Jun-201015:23x86
Microsoft.dynamics.nav.client.exe6.0.31143.0149,37604-Jun-201015:23x86
Microsoft.dynamics.nav.client.interop.communicator.dll1.0.559.18375,68804-Jun-201015:23x86
Microsoft.dynamics.nav.client.serviceconnection.dll6.0.31143.0104,35204-Jun-201015:23x86
Microsoft.dynamics.nav.client.ui.dll6.0.31143.0509,82404-Jun-201015:23x86
Microsoft.dynamics.nav.client.winforms.dll6.0.31143.0337,80804-Jun-201015:23x86
Microsoft.dynamics.nav.client.winforms.tlbNot applicable2,64404-Jun-201012:06Not applicable
Microsoft.dynamics.nav.language.dll6.0.31143.01,992,57604-Jun-201015:23x86
Microsoft.dynamics.nav.types.dll6.0.31143.0567,16004-Jun-201015:23x86
Microsoft.dynamics.nav.watson.dll6.0.31143.042,88004-Jun-201015:23x86
Microsoft.office.interop.outlook.dll10.0.4504.0395,13604-Jun-201015:34x86
To replace these files, follow these steps:
  1. Close the Microsoft Dynamics NAV RoleTailored client.
  2. Locate the Microsoft Dynamics NAV RoleTailored client installation directory. The Microsoft Dynamics NAV RoleTailored client is usually installed in the following directory:
    C:\Program Files\Microsoft Dynamics NAV\60\RoleTailored Client
  3. Copy the files that you downloaded.
  4. Paste the files that you downloaded into the Microsoft Dynamics NAV RoleTailored client installation directory.
  5. Click Yes to overwrite the files in the directory.

Step 3: Replace the files in the Microsoft Dynamics NAV Server installation

In the Microsoft Dynamics NAV Server installation, replace the following files by using the hotfix or the update file.
File nameFile versionFile sizeDateTimePlatform
Httpcfg.exe5.2.3790.022,35204-Jun-201015:34x86
Microsoft.dynamics.nav.language.dll6.0.31143.01,992,57604-Jun-201015:23x86
Microsoft.dynamics.nav.ncl.dll6.0.31143.0608,12004-Jun-201015:23x86
Microsoft.dynamics.nav.server.exe6.0.31143.0141,18404-Jun-201015:23x86
Microsoft.dynamics.nav.service.dll6.0.31143.0145,28004-Jun-201015:23x86
Microsoft.dynamics.nav.service.runtime.dll6.0.31143.075,66404-Jun-201015:23x86
Microsoft.dynamics.nav.service.webservices.dll6.0.31143.0145,30404-Jun-201015:23x86
Microsoft.dynamics.nav.types.dll6.0.31143.0567,16004-Jun-201015:23x86
Microsoft.dynamics.nav.watson.dll6.0.31143.042,88004-Jun-201015:23x86
Nclcsrt.etxNot applicable89,52504-Jun-201008:28Not applicable
Nclcsrt.stxNot applicable91,72404-Jun-201008:28Not applicable
Nclcsrts.dll6.0.31143.01,485,13604-Jun-201015:34x86
Ndbcs.dll6.0.31143.01,350,48004-Jun-201015:34x86

To replace these files, follow these steps:
  1. Stop the Microsoft Dynamics NAV Server.
  2. Locate the Microsoft Dynamics NAV Server installation directory. The Microsoft Dynamics NAV Server is usually installed in the following directory:
    C:\Program Files\Microsoft Dynamics NAV\60\Service
  3. Copy the files that you downloaded.
  4. Paste the files that you downloaded into the Microsoft Dynamics NAV Server installation directory.
  5. Click Yes to overwrite the files in the directory.
  6. Start the Microsoft Dynamics NAV Server.

Step 4: Replace the files in the Microsoft Dynamics NAV Application Server installation

If you have Microsoft Dynamics NAV Application Server installed, replace the following files in the Microsoft Dynamics NAV Application Server installation by using the hotfix or the update files.
File nameFile versionFile sizeDateTimePlatform
Dbm.dll6.0.31143.0427,84804-Jun-201015:33x86
Nas.exe6.0.31143.02,270,53604-Jun-201015:34x86
Nassql.exe6.0.31143.02,368,84804-Jun-201015:34x86
Ndbcs.dll6.0.31143.01,350,48004-Jun-201015:34x86
Slave.exe6.0.31143.0152,40004-Jun-201015:33x86
To replace the files, follow these steps.
  1. Stop the Microsoft Dynamics NAV Application Server.
  2. Locate the Microsoft Dynamics NAV Application Server installation directory. The Microsoft Dynamics NAV Application Server is usually installed in the following directory:
    C:\Program Files\Microsoft Dynamics NAV\60\Application Server
  3. Copy the files that you downloaded.
  4. Paste the files that you downloaded into the Microsoft Dynamics NAV Application Server installation directory.
  5. Click Yes to overwrite the files in the directory.
  6. Start the Microsoft Dynamics NAV Application Server.

Prerequisites

You must have Microsoft Dynamics NAV 2009 Service Pack 1 installed to apply this hotfix.

↑ Back to the top

Status

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

When this problem occurs, the Application log contains the following error message:
Type: Microsoft.Dynamics.Nav.Client.NavClientClosingException Message: The connection to the server has been lost. The application will close. StackTrace: at Microsoft.Dynamics.Nav.Client.ExceptionHandler.DoExecute(Func`1 execute) at Microsoft.Dynamics.Nav.Client.ExceptionHandler.DoRethrowWithCatchException(Exception exception) at Microsoft.Dynamics.Nav.Client.ExceptionHandler.Application_ThreadException(Object sender, ThreadExceptionEventArgs e) at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t) at System.Windows.Forms.Control.WndProcException(Exception e) at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.Run(ApplicationContext context) at Microsoft.Dynamics.Nav.Client.WinClient.RunCore() at Microsoft.Dynamics.Nav.Client.ExceptionHandler.ExecuteAndCatchExceptions(Func`1 execute) at Microsoft.Dynamics.Nav.Client.ExceptionHandler.DoExecute(Func`1 execute) at Microsoft.Dynamics.Nav.Client.WinClient.Run() Source: Microsoft.Dynamics.Nav.Client

---------------------
Type: Microsoft.Dynamics.Nav.Types.NavConnectionLostException Message: The connection to the server has been lost. The application will close. StackTrace: at
Microsoft.Dynamics.Nav.Client.ExceptionHandler.<>c_DisplayClass2.<DoRethrowWithCatchException>b_0()
at Microsoft.Dynamics.Nav.Client.ExceptionHandler.ExecuteAndCatchExceptions(Func`1 execute)
Source: Microsoft.Dynamics.Nav.Client
----------------------
Type: Microsoft.Dynamics.Nav.Types.NavConnectionLostException Message: The connection to the server has been lost. The application will close. StackTrace: at Microsoft.Dynamics.Nav.Client.ConnectionStateManager.HandleCommunicationFailure[T](CallServerMethod`1 callServerMethod, Exception e, Int32 messageNumber, String sessionId) at Microsoft.Dynamics.Nav.Client.ConnectionStateManager.CallServer[T](CallServerMethod`1 callServerMethod) at Microsoft.Dynamics.Nav.Client.ServerInvocationHandler.CallServer[T](CallServerMethod`1 callServerMethod) at Microsoft.Dynamics.Nav.Client.ServiceConnectionBase.CallServer[T](CallServerMethod`1 callServerMethod) at Microsoft.Dynamics.Nav.Client.ServiceConnection.ActionField(NavRecordState& state, NavDataSet recDataSet, String controlTriggerMethodName) at Microsoft.Dynamics.Nav.Client.DataBinder.NstDataAccess.ActionMethod(String triggerName) at Microsoft.Dynamics.Nav.Client.Actions.InvokePageTriggerAction.InvokeTrigger(LogicalControl logicalControl, UISession uiSession) at Microsoft.Dynamics.Nav.Client.Actions.InvokePageTriggerAction.InvokeCore(Boolean async, LogicalControl logicalControl, Object state, UISession uiSession) at Microsoft.Dynamics.Framework.UI.Action.InvokeCoreWithErrorHandling(Boolean async, LogicalControl logicalControl, Object state, UISession uiSession) at Microsoft.Dynamics.Framework.UI.Action.DoInvoke(LogicalControl logicalControl, UISession uiSession) at Microsoft.Dynamics.Framework.UI.ActionControl.Invoke() at Microsoft.Dynamics.Framework.UI.Windows.ActionControlAdapterBase.DefaultInvokeAction(LogicalControlAdapter adapter, ActionControl actionControl) at Microsoft.Dynamics.Framework.UI.Windows.ActionControlAdapterBase.DefaultInvokeAction(LogicalControlAdapter adapter) at Microsoft.Dynamics.Framework.UI.Windows.ActionControlAdapterBase.OnInvoke() at
Microsoft.Dynamics.Framework.UI.WinForms.ActionPaneActionControlAdapter.<InitializeNativeControl>b_0(Object sender, EventArgs e)
at Microsoft.Dynamics.Framework.UI.WinForms.Controls.ActionItem.OnButtonClick() at Microsoft.Dynamics.Framework.UI.WinForms.Controls.ActionButton.OnMouseUp(MouseEventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) Source: Microsoft.Dynamics.Nav.Client.ServiceConnection

-----------------------
Type: System.ServiceModel.FaultException
Action:
http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher/fault
Message: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
StackTrace: Server stack trace: at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter) at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)


Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.Dynamics.Nav.Types.INavService.ActionField(FieldRequest fieldRequest, NavRecordState dataSetState) at Microsoft.Dynamics.Nav.Client.ServiceConnection. <>c_DisplayClass46.<ActionField>b_45()
at Microsoft.Dynamics.Nav.Client.ServerCallContext`1.InvokeCall(Object instance) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[]args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
Exception rethrown at [1]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase) at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData) at System.Threading.WaitCallback.EndInvoke(IAsyncResult result) at Microsoft.Dynamics.Nav.Client.ServerInvocationManager.CallServer[T](CallServerMethod`1 callServerMethod) at Microsoft.Dynamics.Nav.Client.ServerInvocationHandler.CallServer[T](CallServerMethod`1 callServerMethod) at Microsoft.Dynamics.Nav.Client.ConnectionStateManager.CallServer[T](CallServerMethod`1 callServerMethod) Source: mscorlib


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

↑ Back to the top

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.

↑ Back to the top

Keywords: kberrmsg, kbnoloc, kbsurveynew, kbexpertiseinter, kbexpertisebeginner, kbexpertiseadvanced, kbhotfixserver, kbmbsmigrate, kbmbsquickpub, kb, kbqfe, kbautohotfix, kbmbspartner

↑ Back to the top

Article Info
Article ID : 2188923
Revision : 3
Created on : 1/31/2017
Published on : 1/31/2017
Exists online : False
Views : 251