
- Forum
- ERP
- Microsoft CRM
- Error: "Information is needed before this report can be processed"
Error: "Information is needed before this report can be processed"
This is a discussion on Error: "Information is needed before this report can be processed" within the Microsoft CRM forums, part of the ERP category; Error: "Information is needed before this report can be processed" This is said to occur when you run MS CRM ...
-
09-01-2005, 11:12 AM #1David Carroll Guest
Error: "Information is needed before this report can be processed"
Error: "Information is needed before this report can be processed"
This is said to occur when you run MS CRM on a win 2003 and the Active
Directory on a win 2000 for all users except the ‘admin’ user which CRM was
installed with.
However...
I am using 2000 Active Directory and my MSCRM is also on a 2000 Server and
can only run reports using the inital account that was created in MSCRM
Any help would be great!
--
David Carroll MCSE, DBA
-
10-24-2005, 01:59 PM #2Reichert Guest
RE: Error: "Information is needed before this report can be processed"
David,
Any luck resolving this issue. I am receiving the same error message when
users try to run reports. CRM and AD are both on win 2003. I already
checked the PrivUserGroup and SQLAccessGroup in AD. Any help would be
appreciated.
Regards,
Mike
"David Carroll" wrote:
> Error: "Information is needed before this report can be processed"
>
> This is said to occur when you run MS CRM on a win 2003 and the Active
> Directory on a win 2000 for all users except the ‘admin’ user which CRM was
> installed with.
>
> However...
>
> I am using 2000 Active Directory and my MSCRM is also on a 2000 Server and
> can only run reports using the inital account that was created in MSCRM
>
> Any help would be great!
>
>
>
> --
> David Carroll MCSE, DBA
-
10-25-2005, 08:48 AM #3Julio Martus Guest
Re: Error: "Information is needed before this report can be processed"
Hi Sir.
This error may occur as the result of several different factors:
If the error only occurs when you run a custom report, the server address
may be saved in the report.
Your Active Directory domain controller is running Microsoft Windows 2000
Server and your Microsoft CRM server is running Microsoft Windows Server
2003.
Microsoft CRM is installed on a computer that has an underscore in its name.
The security account running the Crystal and Microsoft CRM services does not
have sufficient permissions.
RESOLUTION
Resolution 1 - Verify that the Save Server Address check box was not
selected on the custom report.
1. Make sure Crystal Designer 9.2.2 is closed and then reopen it.
2. Click Start, point to Programs, and then click Crystal Reports 9.
3. After Crystal Designer is open, click File and then click Open.
4. Click the Enterprise folder on the Open dialog box.
5. In the Logon to APS dialog box, enter Administrator for the User Name and
the Crystal Enterprise Administrator password. By default the Administrator
password for Crystal Enterprise is set to blank. If you have not changed the
Administrator password using the Microsoft.CRM.tools.crystaladmin.exe, the
password will be blank.
6. Locate the custom report and then click Open.
7. After the report is open, click the Report menu and then click Refresh
Report Data (F5).
8. Clear Connect to Local Computer in the Connection Info dialog box. .
9. If you have the Save Server Address check box selected, clear the check
box.
10. Make sure the Server field is set to
http://<YourCRMServer>/MSCRMServices.
11. Click Finish.
12. When you click the Database menu and then click Set Datasource Location,
the connection must appear as SSO. If the connection appears as
http://<YourCRMServer/MSCRMServices> or something other than SSO, the report
is not using the required SSO connection.
13. Click the File menu and then click Save.
14. You will have to close out of Crystal Designer 9.2.2 and follow steps 1
through 13 for each custom report that has this issue.
Resolution 2 - Obtain the Hotfix that corrects this error when the Microsoft
CRM server is running Windows Server 2003 and the Domain Controller is
running Windows Server 2000.
For more information about how to obtain this Hotfix, visit the following
Knowledge Base article:
https://mbs.microsoft.com/knowledgeb...b;en-us;862579
Resolution 3 - Rename the Microsoft CRM server if it contains an underscore
in the name.
If the CRM server has an underscore in the name, see the Verify and fix a
computer name containing an underscore section of the Microsoft Business
Solutions CRM Version 1.2 Reports FAQ. Click the following URL to download
the FAQ:
http://support.microsoft.com/default...b;en-us;834789
Resolution 4 - Provide the account running the Microsoft CRM and Crystal
services with sufficient permissions.
View the Identifying and fixing security problems that are preventing
reports from running section of the Microsoft Business Solutions CRM Version
1.2 Reports FAQ. This document can be downloaded from the URL specified in
Resolution 3.
This article was TechKnowledge Document ID: 35495
"Reichert" <Reichert@discussions.microsoft.com> wrote in message
news:725DB2BA-8AB2-4AB8-9522-6E3F68BF5BCC@microsoft.com...
> David,
>
> Any luck resolving this issue. I am receiving the same error message when
> users try to run reports. CRM and AD are both on win 2003. I already
> checked the PrivUserGroup and SQLAccessGroup in AD. Any help would be
> appreciated.
>
> Regards,
> Mike
>
> "David Carroll" wrote:
>
>> Error: "Information is needed before this report can be processed"
>>
>> This is said to occur when you run MS CRM on a win 2003 and the Active
>> Directory on a win 2000 for all users except the 'admin' user which CRM
>> was
>> installed with.
>>
>> However...
>>
>> I am using 2000 Active Directory and my MSCRM is also on a 2000 Server
>> and
>> can only run reports using the inital account that was created in MSCRM
>>
>> Any help would be great!
>>
>>
>>
>> --
>> David Carroll MCSE, DBA
-
Check the report Rights - On Demand Reports must have View On Demand right to execute on a Business
I had the above mentioned error for a user when they were trying to run a report I had deployed to their Reporting Server (a Business Objects report server - server details unknown).
After trying several things with the user I noted that they kept referring to clicking the schedule button for the report when running it on the server. This particular report required the user to select from a listbox of values before running the report i.e. it is designed as an on Demand report.
I noted that on the Server under the Central Management Server, the report properties showed that theuser group user was a member of, only had schedule rights. When ever they tried to schedule the report the above error occurred. the FIX: was to grant the user group View On Demand rights at report level. The following is a transcript of the resolution from our bug tracking system, with sensitive material removed.
NOTE
---------
As the CR report developer, I have Admin rights which meant the Removals Report runs successfully for me. However, <user> falls into the user class Everyone. This user class ONLY had Schedule rights. Meaning they could schedule the report only. As the report is Run "On Demand" because it requires user to select the runtime parameter Extract Type, user class Everyone needed the right "View On Demand".
Once this right was prescribed to the report via Report Maintenance on the Report Server, <user> was able to see a link to run the report on demand. When clicked she was challenged to select the Extract Type parameter and the report executed successfully.
REPORT MTC.
--------------------
1. Logon to report server Central Management Console:
2. Navigate the tree to the report link. Click the report to Maintain it
Path Details:
<removed>
3. Click the Rights tab. For the User Class Everyone, select the right "View On Demand". Click Update.
Hope this helps.
-
If the report uses runtime parameters, target user group must have server right "View on Demand". This is set in the report properties on the Business Objects Server via Central Management Console.
NOTE:
=====
Specifically if you can view the report OK, but others get the above error. This is probably the problem. The reason you can see the report but other can't is because you are the author and the person who deployed the report and you therefore have full control of the report. I others only have Schedule rights for the report, but the report requires user to enter / select a runtime parameter when report is executed, you'll get this symptom.
Hope this helps
-
Sponsored Ads

Reply With Quote





