Recently a report that's existed for a while stopped working and it gave the error message:
The viewer could not process the event. The database logon information
for this for this report is either incomplete or incorrect. [] ----
Error code:0 [CRWEB00000119]
The thing that's throwing me is that nothing about either the report or the database it's connected to changed and to "fix" it all I did was save a copy of the report and put in the same credentials and database settings. I tried the Verify Database option which is what a lot of the results said to do, and that said that the connection was fine, but it didn't fix the issue.
Most of the other instances I found usually happened when something was changed and Crystal got out of sync with the database for some reason.
Has anyone ever heard of or experienced this where Crystal just up and starts failing or have any idea of why this might have happened?
Related
When I deploy one of the reports I've made to the report server, a field that is shown when I preview in SSRS magically disappears. I've re-downloaded the report from the report server and opened it up in SSRS and the field reappears when I preview.
Has anyone encountered something like this?
I've tried searching for similar problems but nothing came up.
Please & thanks.
For a long time I have always deleted the report from the server prior to deployment when I change /Datasource/Parameters values---works for me. Then re-deploy and you should be set.
Some reports have been updated and work as before (can be viewed through a .net app and not prompt for credentials).
Other reports have started prompting for credentials since they've been changed. This happens even if the change is just moving something on the report.
I've tried deleting everything on the report apart from a label and this hasn't made any difference.
There's no difference in the .net code in how these reports are displayed.
All the reports are using the same DSN datasource.
If the credentials aren't stored in the report, I'm not sure how only changing the report can make this difference?
Update to add: Crystal reports v9.2.2.634
Came back to this today. Tried changing a report that I'd previously edited and was working OK, just to see if all reports edited after a certain point were going wrong, and this worked fine.
Tried altering one of the broken reports again (just adding a space to the end of a label), saved this and that report now works fine.
No idea what actually made this work, but if you get the same problem you could try editing a previously edited working report and trying again.
Confused.
I am new to SSRS, but have begun migrating our reports to that for my organization. I have 3 reports set up at this time, but have run into a problem. Viewing any of the reports in Report Builder works just fine, but viewing 2 of the 3 in IE (also tried Chrome, Firefox, Opera) is only sporadically successful. Report server is set up on database server, and nothing in the queries being run would tax the system.
I know the security settings are correct, as I can access everything without permissions errors; I know the reports work, as I can freely use them in Report Builder and sometimes from the browser; and I am able to always access one of my three reports through the browser. All have the same security, are in the same folder, and I have gone through the same steps to load each of them. The only difference is that the one that always loads is much simpler than the other two as far as volume of data.
Now, to explain what I actually see when this happens. I set my parameters, and click View Report, and the loading icon pops up for about 1/10th of a second, then disappears. The toolbar does not appear, no data appears, and no error message is present. Every once in a while, it all works perfectly. Most of the time, only 1 of the 3 reports works. I've tried without success to find this issue raised elsewhere -- my apologies if I missed it. Any help on this would be greatly appreciated, thanks in advance.
edit details: SQL Server 2008 R2, on Windows Server 2008 R2, IE9 from a Windows 7 desktop.
If you inspect the SSRS error log it may reveal more of the issue. Sounds like a processing error that was not gracefully handled. Inspect the file \SERVER\\MSRSXX.MSSQLSERVER\Reporting Services\LogFiles and find the current log file to view the exception. Depending on how the client is set up some errors may not show.
The following error message occurs with some reports of our Crystal Reports application, when you try to open them a second time.
"A Crystal Reports job failed because a free license could not be obtained
in the time allocated"
It seems to be a problem only with some reports (with a lot of data in particular). Other reports work without any problem. But once the error message appeared, all reports will fail.
Can anyone tell me how the licensing mechanism of Crystal Reports works?
Where is the "free license" obtained from?
Can this be a time issue due to the amount of data?
-- edit --
From what we learned in the meantime, it seems to be a problem only with reports that called a particular long running PL/SQL package in the report command. And Crystal somehow doesn't like calling that twice.
And i guess the error message is just a secondary symptom and not the cause.
Unsure if anyone on here could lend a hand, but I thought I'd give it a shot. Google wasn't too useful.
I have a report that I was working on all yesterday in Crystal Reports XI. I thought it was all good and working, so I closed the file (big mistake). Now, I try and open it again, and it's not letting me.
I get the following errors:
"An Ole object in this report could
not not be loaded. It has been
replaced with a blank object"
So then crystal tries to load my report with it's changes (I think), and then I get:
" This document could not
be opened. It does not appear to be a
Crystal Report document. This document
has the expected file extension
(.RPT), but it seems to be corrupted.
If this report used to work, try
opening it with a different version of
Crystal reports and if that still does
not work, please contact your
administrator".
I don't have another version of Crystal to check it with, and I'm pretty much the local admin for crystal, and I have no idea what to do.
Crystal wasn't letting me save over previous versions of this report yesterday, and now none of the 6+ versions I have are loading.
Can anyone suggest anything to help?
I got around this error by recreating the entire report.
I have no idea what the issue was, but after I spend 2 hours recreating it, it now works as intended.
I'm guessing that if anyone else receives the terminal Corruption error, they should just throw it away and start again.
You can try opening it in Visual Studio, which may or may not have the same version of Crystal. But it's a binary file, and if that gets munched, I'm not sure you have much recourse.