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)

SL 2015 CU1 screen crash when choosing PV

(0) ShareShare
ReportReport
Posted on by 467

Hi Guys, I have seen this issue atleast twice, but don't know the actual fix. All screen crashes when choosing any possible value lookup field.

Any ideas?

*This post is locked for comments

I have the same question (0)
  • Community Member Profile Picture
    on at

    <BUMP>  We are having the same issue but only with the Invoice Print Screen, and only when I choose "FInal" Or "Preliminary" and then hit F3 in the DRAFT begin box and the screen crashes: BI.INV.00

  • Suggested answer
    Community Member Profile Picture
    on at

    For ANYONE that is having this problem, we figured out our solution last night and wanted to post it.  There was a corrupt PVREC record in the systems PVREC table.  We deleted ALL rows from it and re-imported "Import PV Lookup Values" under administrator tab in Dynamics and VOILA!  problem solved!  

    Hope that helps anyone with this issue in the future, the help on this stuff is very lacking.

  • Community Member Profile Picture
    on at

    Having the same issue with my SL2015 upgrade, any screen I hit f3 it crashes. No luck on my end so far.

  • Suggested answer
    DAN_F Profile Picture
    5 on at

    Hi Everyone,

    We were able to resolve this by:

    Delete/drop the user E8F575915A2E4897A517779C0DD7CE from all app and system databases

    Delete/drop the login E8F575915A2E4897A517779C0DD7CE from SQL Server security

    Run the Database Maintenance Update Scenario "Synchronize All Database Ownership & Security" which will put the login and user back

  • Verified answer
    Mark E Profile Picture
    6,451 on at

    FYI, I ran into this issue with a SL 2015 CU2 upgrade, turned out there was a custom proc using WITH EXECUTE AS 'E8F575915A2E4897A517779C0DD7CE', and it prevented the login from being dropped and re-added with the "Synchronize All Database Ownership & Security" DB Maintenance routine.  Changing the proc to use '07718158D19D4f5f9D23B55DBF5DF1' instead resolved the issue, and allowed the security sync process to run correctly.

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