Who's On?

	Membership:
	Latest: Saef
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5226

	People Online:
	Visitors: 688
	Members: 0
	Total: 688

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

LBI 9 Reporting Issue

6 Replies

0 Subscribed to this topic

22 Subscribed to this forum

Sort:

Author

Messages

drhoades44

Advanced Member

Posts: 46

1/21/2009 2:03 PM

I created a report in development and published LBI Data Settings of a user and password we set up for all development reports. The report is in Crystal XI using a SQL Server stored procedure as the data source. This office is used to using tables as the data source. When I publish to LBI Dev the Data Settings are fine. When they publish in production, there is no user or password in the Data Settings area. How do I fix this?

Matthew Nye

Veteran Member

Posts: 514

1/21/2009 4:30 PM

thats typically an indication that the report is corrupt or there was an interruption during upload. i would republish the report, if you continue to have the problem, check youre report for special characters in formula or parameter names as well as special characters in default parameter values.

hth
matt

Ruma Malhotra

Veteran Member

Posts: 412

1/21/2009 4:44 PM

If you are publishing a report from the dev environment to the production environment you may also want to use the Override Datasource feature on the data settings screen and choose the datasource for the prod environment, put in a user-id and password that will refresh the report from the prod environment and click on save.

Next time when you click on view with data refresh it will refresh the report from the data in the prod environment.

Hth.
Ruma.

Chris Martin

Veteran Member

Posts: 277

1/21/2009 5:52 PM

This can also occur if RAS is not running when the report was published.

drhoades44

Advanced Member

Posts: 46

1/22/2009 2:54 PM

We re-published but now get this. See attachment.

drhoades44

Advanced Member

Posts: 46

1/22/2009 2:55 PM

Sorry, wrong file type. Here it's zipped.

Attachments

LBIError.zip

Matthew Nye

Veteran Member

Posts: 514

1/22/2009 3:07 PM

This is not an error, its a warning really. I means that you are using bursting options for this report but the user you are logged in as has no rights associated to data that is being returned in the report. First turn bursting options off o the report and validate that the reports run. Then check your rights management and make sure the user "administrator" has a right with the stucture that is being used for this report and that values are associated to that right are being returned in the report. The easiest way to do this is to assign the value of "*" to all elements in the right. This says the user can see all data in the report.

hth,
matt