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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Dynamics SL VBA errors...
Microsoft Dynamics SL (Archived)

Dynamics SL VBA errors (System Message 20406)

(0) ShareShare
ReportReport
Posted on by Mark Fineman 420

Hi,

For the past week we have  been getting a strange error message in Dynamics SL 2011.  Suddenly after years of working fine, users can open the Journal Transactions window fine.  So after being able to open the window fine many times in a day, one user changes to Initialize Mode and then opens the same window and System Message 20406 Appears (Error Loading VBA project. HRESULT = 0x8007000e.)   I looked up a KB article about it and none of the resolutions worked. We rebooted the app and sql server and the situation randomly persists.   But once one user gets the message on the Journal Transaction entry window - all users get it afterwards regardless if they are in Initialize Mode or not.

I've exhausted my research - any one with ideas?

Thanks!

Mark

*This post is locked for comments

I have the same question (0)
  • Mark Fineman Profile Picture
    Mark Fineman 420 on at

    Oh- the KB article I used was this  support.microsoft.com/.../873686 (none of these resolutions worked)....

  • Ram Peru Profile Picture
    Ram Peru 2,830 on at

    Hello Mark F,

    You can do the following steps that may resolve your issues.

    1.Log off from Microsoft Dynamics SL.

    2.Browse to the Microsoft Dynamics SL program files directory. (Example Path   C:\Program Files\Microsoft Dynamics\SL\Applications\)

    3.take a backup of Solomon.Ini file

    4.Locate the Solomon.ini file, and then open the file by using Notepad.

    5.Add the below lines into the Solomon.ini file  

    [Customization]                                
    VBASourceCompile = Yes

    6.Save and close the Ini file.

    7.Relaunch the Dynamics SL 

    Hope this explains.

  • Mark Fineman Profile Picture
    Mark Fineman 420 on at

    Hi, I checked on your suggestion and our Solomon.ini already is set with that configuration:

    [Customization]

    VBASourceCompile=Yes

    VBASourceSave=Yes

    Thanks for your suggestion!  We're open to more if you have any!

    Mark

  • Suggested answer
    Ram Peru Profile Picture
    Ram Peru 2,830 on at

    Good morning Mark F,

    How have you configured the Dynamics SL?

    If you have configured the Server & Work station Type, please do the following

    1.Place the server Solomon.ini file into Work station machine under the path

       C:\Users\xxxxxxxx\AppData\Roaming\Microsoft Dynamics SL

       Here xxxxxxx is the windows user name

    If you have configured the Dynamics SL in Terminal Server, you have to place the Solomon.Ini file against the each user login under the path

       C:\Users\xxxxxxxx\AppData\Roaming\Microsoft Dynamics SL

       Here xxxxxxx is the windows user name

    Please try this and let me know how it goes.

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    It worked!

  • ALeonard Profile Picture
    ALeonard 25 on at

    ... wrong thread

  • Suggested answer
    CFROTON Profile Picture
    CFROTON 4,710 on at

    Mark,

    Thank you for posting your issue to the forum. I wonder if the following will help. It was added a post yesterday originally referencing a different error, but about a 20406 like you are seeing:

        I just had a case that started with a System Message 20406 but when we renamed the APC folder in the user profile, the      

        error in the first post of this thread appeared (system message 20222).

        Instead of reinstalling the entire SL client, we just reinstalled the VBA components on the machine to alleviate the issue.      

        Steps:

        •Browse out to C:\Program Files (x86)\Common Files\Microsoft Shared\VBA

        •Rename any VBAXX Folders within

        •Browse out to your SL root directory > Prerequisites folder

        •Run the VBA71.msi (and then VBA71_1033.msi if applicable)

        •Browse back out to C:\Program Files (x86)\Common Files\Microsoft Shared\VBA

        •Any folder that did NOT get replaced, rename back to its original state.

        •Try the screen again.

        -Adam

    I hope this helps.

    Carolyn

    MSDSL Technical Support

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans