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) / Fatal Database Error! ...
Microsoft Dynamics SL (Archived)

Fatal Database Error! Number = 5 on table PJPTDROL

(0) ShareShare
ReportReport
Posted on by Community Member

SL7 sp3

For some project if we run the Integrity rebuild we get the error in the title.  Thru SQL traces it seems to be an issue with Inserting records to the PJPENTEM table, that violate the primary index.

if I delete all the records from the PJPENTEM for that job and run the integrity check it runs successfully and rebuilds the records in PJPENTEM.

Does anyone know anything about PJPENTEM?  Am I causing any other issues by doing this?  If it is safe, I would like to delete all from PJPENTEM and rebuild all projects (over the weekend).

Thanks,

Ayrin

 

 

*This post is locked for comments

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

    The PJPENTEM stores the information that you see on the Resource Assignment screen, including your project/task/resource combinations (assignments), the actual hours for those assignments, and any budgets hours you entered for those assignments.  The integrity check may somewhat rebuild the table, but if a resource doesn’t have any actual work posted to a given assignment, the integrity check would have no way of knowing that the resource needs to be re-assigned to the task so it wouldn’t get re-added.   I would also suspect that your estimated/budgeted hours for the assignments would be lost as well.   So unless you don’t really use the resource assignment screen, I wouldn’t recommend just deleting from the table.

    Are you able to tell which project/task/employee combination might be duplicated?

  • Community Member Profile Picture
    Community Member on at

    This has to be very rar,e but just incase somebody else come accross this.  In my case it the PJPENTEM table did not have a pjpentem0 index.  When I tried to add it, it said it already existed.  so I droped the index and then added it back thru SQL.  Everything worked after that.

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