One of our clients recently had an issue where a user got an error message when trying to create a new appointment. Upon saving, a dialog pops up “The record you are requesting is currently unavailable. Either the record was not found or you don’t have sufficient permissions to view it.” When getting that message, I thought it was a permission issue, but that was quickly ruled out. After much searching, I ran across a post on Ronald Lehman’s blog. He posted the solution to this, but I wanted to reference this as well because our client received it a few times. Also, it took me quite some time to find this post, so hopefully we can give it more exposure. The url for Ronald’s blog post is: http://ronaldlemmen.blogspot.com/2007/05/error-when-creating-new-appointment.html.
Basically he goes on saying that this is caused by an “orphan” record in CRM. The SystemUserBase table in CRM should have a one to one correlation with the Resource table. That is if a record exists in the Resource table, but not in the SystemUserBase table (as was our case), then this error would be received.
After running the query he suggested and “cleaning” up the data, that resolved the issue.
Posts
No comments:
Post a Comment