Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics SL (Archived)

Customization corrupted all the time

Posted on by 310

Hi, 

I'm working on Dynamicvs SL 2011 FP1 (version 8.13.60522.00) installed on Windows server 2008 64bits. 

Most of the time (not always), when I'm doiing changes to my customization in VBA, the program crash and after that, I can't open it, I get a Windows crashed application screen. Export don't work neither, what I'm ending up is working in text editor, import my changes, test and loop back in the text editor. Adding new fields this way is a pain. 

Hopefully someone will be able to help me to fix this issue. 

Thanks.

Description:
Stopped working

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: 0425000.exe
Problem Signature 02: 8.0.0.0
Problem Signature 03: 555f5276
Problem Signature 04: Solomon.Kernel
Problem Signature 05: 8.0.0.0
Problem Signature 06: 5057a202
Problem Signature 07: 1bf
Problem Signature 08: 0
Problem Signature 09: RML5K4UDBMA5NI04CIYRWVDHKEWFDHCV
OS Version: 6.1.7601.2.1.0.16.7
Locale ID: 1033

*This post is locked for comments

  • AlexDupuis Profile Picture
    AlexDupuis 310 on at
    RE: Customization corrupted all the time

    Hi Erich, thank you for you time, hopefully someone will have an idea of what that could be.

    Someone told me that it could be because I imported cst files with VBA insted of the binary. I may try something related to that, just delete everything and recreate the whole thing, I'll see if it fix the issue.

  • Erich Strelow F Profile Picture
    Erich Strelow F 1,642 on at
    RE: Customization corrupted all the time

    I think you are right, the hotfix doesn't apply to you.

    There's little more help I can give you.

    Not being even able to export the customization is weird. Do you get to see the export customization list?

    The VBA customizations are kept in the SYS.CustomVBA table using a storage model which I find annoying. Those records might have got corrupted in your case.

    The customization data (the VBA source code, the control properties and positioning, along with any binary design data) is stored in the CustomVBA table using a binary serialization. Because of the so called 30500 bytes per record limit, each customization data might get partitioned so it can expand across several records. The RecordIndex field is used to sort out the separated sections. The export screen (9150000) just dumps the contents of the customization, it doesn't really compile any code. In theory the export is a no-fail operation.

    Having said so, this storage model has been successful for many years. I don't trust it because I'm picky. That's why I never get too greedy in the customization: if you have to code too much inside the customization, better move out the code.

    Check if there's anything fishy in the CustomVBA records. The first two bytes of the PropData field are the size header with a little endian order. 0x2C75 means 29,996 bytes, a full customization data section. A normal customization might expand across a few 0x2C75 full sections and end with the Max RecordIndex of a smaller size. The other CustomVBA fields control the loading access rules and order, they also might have issues.

  • AlexDupuis Profile Picture
    AlexDupuis 310 on at
    RE: Customization corrupted all the time

    I looked at the HotFix, it says to update "solomonwrapper.dll" to version 8.10.31015.00 (2012-10-15) but I'm already to version 8.13.60522.00 (2015-05-22) for this file.

  • AlexDupuis Profile Picture
    AlexDupuis 310 on at
    RE: Customization corrupted all the time

    I will get a look on that hot fix. Sometime, it crash when I try to save, other times, I save my changes, I'm able to close the form but not to open it back, from this point, I can't export it neither, the only thing I can do is import my lastest backup.

    What I'm changing doesn't seem to impact that, sometime it happen when moving a control, sometime when a change things in VBA. But either way, I redo the same change and it work so, it's not a particular change that cause the problem.

    I'll try the hotfix and let you know.

    Thanks.

  • Erich Strelow F Profile Picture
    Erich Strelow F 1,642 on at
    RE: Customization corrupted all the time

    Does it crash while you are editing or run-time?

    There is a hotfix for this version about a crash while inserting controls in the forms. Check out article 2773029.

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,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,214 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans