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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics SL (Archived)

Vendor Banking Entry stopped working CLR20r3 error

(0) ShareShare
ReportReport
Posted on by

Testing an upgrade of Dynamics SL 7 FP1 to 2011SP1 and receive a "stopped working" message for any ebanking module launched.  All other areas are working.

Example of problem details with ebanking - Vendor Banking Entry has stopped working message

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: dd25100.exe
Problem Signature 02: 6.0.3279.15314
Problem Signature 03: 4950e7f4
Problem Signature 04: Microsoft.VisualBasic
Problem Signature 05: 8.0.0.0
Problem Signature 06: 4ca2d138
Problem Signature 07: 5b
Problem Signature 08: 2c
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.1.7601.2.1.0.18.10
Locale ID: 1033

any ideas?

*This post is locked for comments

I have the same question (0)
  • Carolyn Kolpien Profile Picture
    on at

    Hi Support Mgr,

    If you aren't using a standard SL module, support can't assist.  If another customer doesn't offer any help, you most likely will need to contact the person that sold you the eBanking module.

  • Jwalsh Profile Picture
    5 on at

    Carolyn,

    I have (essentially) the same error.  

    I understand that you cannot answer technical questions about custom screens that have been created.  I am a developer, so I know that trying to answer technical questions about something not included in the original application would be almost impossible.  

    That being said... What is different about SL 2011 FP 1 that would throw a "System.IO.FileNotFoundException" where SL 7 did not?  I have read through the SL 2011 documentation and I cannot find anything that might have changed between versions that would cause an error like this.

    In MY custom screen, the end result is some data being written to a txt file.  If the stored procedures that write to the file have the correct file path to which it will write data to, then what is going in in SL 2011 that would make the application think that the file cannot be found?  

    Thank you (in advance)!

  • Community Member Profile Picture
    on at

    Did you solved?

    I'm facing the same problem in a migration.

    Thanks in advance.

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…

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans