Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics SL (Archived)

Unable to locate the message file \messages.csv

Posted on by Microsoft Employee

I have a client that is sporadically seeing the error message pop up 'unable to locate the message file ..\messages.csv'. If a user waits a minute and tries their entry again they don't get the message. At first I thought it might be connectivity but they have their SQL server on the same machine as their SL applications. I would assume I would see assertion errors if they were losing connection to the server.

Is there any process that locks the messages.csv file for any reason?

*This post is locked for comments

  • Suggested answer
    CFROTON Profile Picture
    CFROTON 4,710 on at
    RE: Unable to locate the message file \messages.csv

    Hello FXF

    Back when 2015 was released they added the following to the installation guide

    1. Map a drive to the shared folder containing the Dynamics SL parent directory.

    2. Before running the ClientSetup.exe, open a command prompt with "Run as Administrator".  Map a drive to the shared folder using the same drive letter as indicated in Step 1.

    3.  Execute ClientSetup.exe as the current user - and not a "Run as Administrator".

    The other workaround was to Edit the following registry keys:  

    HKEY_LOCAL_MACHINE\Software\WOW6432Node\Microsoft\DynamicsSL---> Change the INSTALLDIR and ParentDirectory entries from the UNC path to the mapped drive path

    HKEY_LOCAL_MACHINE\Software\WOW6432Node\Solomon\SolomonIV Tools for Visual Basic -->Parent Directory change the UNC path to the mapped drive path

    This is Microsoft Dynamics bug 35852

  • FXF-CLCC Profile Picture
    FXF-CLCC 5 on at
    RE: Unable to locate the message file \messages.csv

    Seeing this behavior on a fresh Dynamics 2018 install.

    Solved it by editing the registry.

    Should this still be necessary 2 years later?

    SL 2018 CU1 Client 10.1.21108, CU2 Client 10.02.30430.00.

    Installed 'as administrator' using domain admin account, Y: drive mapped to \\<servername>\Dynamics where Dynamics is the share name for the folder C:\SLInstall, so Y:\ = C:\SLInstall, in other words the root of Y is the install folder on the server containing the Dynamics software.

    Wondering if the programmers expectation was that C:\ would be the shared folder so that \\<servername>\<sharename>\<folder with install> would be the Parent Directory.

    Or if in Windows 10 the drive mapping lookup for the drive letter isn't working the way the Dynamics programmers anticipated. In any event, I popped open Explorer, navigated to Y:\, right clicked the exe and selected "run as administrator."

    I would have thought that Y:\ would have been picked up as the Parent directory, not \\<servername>\Dynamics.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Unable to locate the message file \messages.csv

    Today I had a new variation on this.  The client had a new workstation so we installed the SL 2015 client.  We checked the registry settings indicated in this thread and they were good.  We then installed CU1 on the workstation and it emptied those registry settings so we had to manually edit them back to the mapped drive and folder.  We did not have this issue on another new workstation installed a couple of weeks ago.  Both were Windows 10 workstations.

  • Laura Profile Picture
    Laura 450 on at
    RE: Unable to locate the message file \messages.csv

    The change to the Solomon.ini for the messages.csv file and copying the file locally to that users directory got me past one error and on to the next!

    Now I am getting System Message 9867 The client components on this machine are not up to date. This situation can result when a Service Pack is installed on the server but not the client. Please apply updates to this client computer.

    I reapplied the hotfixes, they all said they were successful but one of them did not show the right version on the dll. I copied the Swimapi.dll to 2 places and SL finally launched but the menu was blank. The user did not have a Solomon.ini in their AppData\Roaming\Microsoft Dynamics SL directory.  I copied the Solomon.ini from another workstation but then SL would not launch.

    I am going to start from scratch and uninstall and reinstall.

    Thanks for the initial assistance.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Unable to locate the message file \messages.csv

    Aloha Laura,

    Not sure if this is the same issue, but we followed the Installation Guide (page 18. changes needed for UAC) and we no longer receive these errors.  Basically, updated the Solomon.ini file to look for the message file in the users Public Documents folder.  Then copied the messages.csv file to the folder.

    Hope this helps.

    Aloha,

    -Scott

  • Laura Profile Picture
    Laura 450 on at
    RE: Unable to locate the message file \messages.csv

    Thanks Mark, but checked that already. This is a 64 bit machine so we looked at the WOW6432Nod entry and it is using the mapped drive.

  • Suggested answer
    Mark E Profile Picture
    Mark E 6,405 on at
    RE: Unable to locate the message file \messages.csv

    Try this workaround, works for a client of mine today with a new SL 2015 CU1 install on Win7 PC...

    www.dynamictechservices.com/sl-2015-cu1-unable-to-locate-message-file-and-system-message-5004

  • Laura Profile Picture
    Laura 450 on at
    RE: Unable to locate the message file \messages.csv

    Any other ideas on this topic? SL 2015 CU1 with hotfixes; Windows 7 machine; using Webroot for antivirus

    Install done by a Domain Admin, Registry entries are correct and mapped to a drive letter;

    Even as an Domain Admin getting the System Message "Unable to locate the message file T:\Applications\MESSAGES.CSV"  and then System Message 9867 "Message was not found in message file".

    Share on the server seems right the AD group on the SL directory has full control.

    Have uninstalled and reinstalled.

    Not sure on next steps to resolve.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Unable to locate the message file \messages.csv

    Totally borked, see Elaine's reply and make the registry changes. Anytime you re-install or when you apply CU1 it appears to rebork.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Unable to locate the message file \messages.csv

    Still no joy here. New installation of SL 2015 CU1. Works fine on the Terminal Server but not on a workstation. I have tried:

    1. Installing from a share. (Logged in as admin *and* run as Administrator).

    2. Installing from a mapped drive and changing the registry entries. (Logged in as admin *and* run as Administrator).

    3. Changing the permissions on the share and files to include read/write (although I would not be happy if this was the fix!)

    Is this just borked?

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans