BO Enterprise - unable to connect:incorrect log on parameters

[twmyu]

Hi,
Having issues with BO Enterprise.

I have deployed a report on our new BO Enterprise Report server. I am able to schedule the report (which contains some subreports) in CRXI and do not have any issues. When the report is scheduled on the InfoView (BO Enterprise Report server) it completes with the status of success however am unable to view it. Gives me the following error:

Error in File ASummary: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 1005 ]
Unable to retrieve Object.
Error in File ASummary: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 1005 ]


One of the threads I've read suggested that I schedule the report in the CMC. I did and it worked and was to able to successfully view the report using the CMC too. Then I went into the InfoView and attempted to view the same report and it gives me the same error. In addition, I was able to find the location of the report instance that was generated and successfully open up the report and view it in CRXI. Note: it did ask me for the password which has been save in CMC.

Does anyone know why this happens?

Any help would be appreciated.

Thanks,
T

 

[synapsevampire]

You posted "I am able to schedule the report (which contains some subreports) in CRXI and do not have any issues.", but CR XI doesn't have scheduling.

Once the report was scheduled and successfuly ran, you should be able to just click on the name of the report within Infoview->History and view it.

Clicking on the report itself attempts to run it again, not view a successful instance.

-k

 

[twmyu]

When I say schedule the report I mean previewing it in CRXI.

The problem is that the report's status is success but when I click on the "instance time" it fails to display the report and comes up with the error message.

T

 

[synapsevampire]

An unable to retrieve object is ominous.

Is the scheduling done to default location?

Try scheduling it to a location first to make sure that it works.

Then try clicking on the last instance time of that.

If those work, then it sounds like a configuration of BOE problem to me.

-k

 

[twmyu]

Hi,

Yes, scheduling is done in the default location. BOE is running on a seperate server.

How do I schedule it to a location? If this is a config issue. Know how to fix it? BOE was not installed on the C: drive but on the D: drive, could the installation of BOE on the D: drive cause these issues?

I have been also having issues with .dll files too. We have a vendor that supplies us with some crystal report objects but they use their own .dll files. Some reports seem to be having an issue with finding the .dll files and as a result fails.

Thanks,
T

 

[TheStriker]

In the process tab click on the Database link, choose the Use original database logon information from the report' option which should be the first option.

Then scroll down to the 'When viewing report' section and select 'Use same database logon as when report is run' and click Update.

This should fix your logon errors as it uses the credentials specified in the first option everytime the report is run. Also note that you must do this for all of your subreports as well.