• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 787
  • Last Modified:

Report won't run in CRM 4.0

Experts,

I have a report that has worked in the past but I needed to make a change to it...it works in SSRS 2005.  After editing the report, I saved it and uploaded to CRM.  Then I went to run the report and I got an error that the report could not be displayed.

Any ideas on why that might have happened and how to fix it?

Thanks,
Kelly
0
mschmidt14
Asked:
mschmidt14
  • 2
  • 2
1 Solution
 
cubaman_24Commented:
Hello:
Is there any error message with more detailed information? Look at eventviewer..
Also, if your report has credentials, check that their are not expired.
Best regards.
0
 
mschmidt14Author Commented:
So we checked the errors in the event viewer and found the reason why...it has to do with an update statement I put in the query.  I wanted the table to update on whether another field contained a 1 or not.   The only way I knew to do this was to create a seperate dataset with this query.

update filteredcsisurvey
set status =
  CASE  WHEN recommend > 1
 THEN 'Resolved'
  ELSE 'Active'
  END

Select distinct status
From filteredcsisurvey
Where recommend >= 1

The error we get is as follows.

Event Type: Error

Event Source:     MSCRMReportingDataConnector

Event Category:   None

Event ID:   19972

Date:       12/21/2011

Time:       3:42:42 PM

User:       N/A

Computer:   XXXXXX

Description:

Report data set execution failure. Error: The UPDATE permission was denied on the object 'Filteredcsisurvey', database 'MyCompany_MSCRM', schema 'dbo'.

Do you know of another way I can do this?
Thanks,
Kelly



0
 
cubaman_24Commented:
Hello:
With such information I'm unable to recommend another path to achieve it..
But even if datasets are worse than Sadam and Osama together, your method seems to be OK, except that you need more permissions on DDBB. Check that current user has the proper rights on dbo schema to trigger the update.
Best regards
0
 
mschmidt14Author Commented:
It was the update statement that was killing it.  CRM didn't want to handle that piece for some reason.  I removed the update portion and it ran just fine.

Thanks for trying.
Kelly
0
 
mlmccCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now