a database error occurred the database error text is ORA-01017;invalid username/password;logon denied(wis 10901)

[Former Member]

when user tries to run webi report he gets this error

"a database error occurred the database error text is ORA-01017;invalid username/password;logon denied(wis 10901)"

as a administrator if i try to run report it executes

he as access to report

he as access to universe and connection

don't know what the problem is?

can anyone help me in this issue?

thanks in advance

[Former Member]

now report is running but its just going on running.

i get no output

dont know y?

Thankyou in advance

[former_member188911]

what version and patch level are you on?

get traces from the Web Intelligence processing server and trace the database they should give some hints on what is going on

thanks

[Former Member]

You got this resolved ever?

[Former Member]

Hi Pavan,

-Check the connection configuration of connection in that universe,

-Edit the connection and see the connection properties, see whether there is predefined username and password.

or businessobjects credentials or SSO.

-If it is using other than predefiend username and password, then you need to test with user account who is having problem and try to login to database using his BO credentials or credentials specified in user account properties in CMC>>USERS depend on the option specified in universe connection.

-I am sure the problem lies here.

thanks,

Niranjan

[former_member188911]

Check that the user settings in the CMC, there is an option for using the user credentials which would override the ones hardcoded in the universe

[Former Member]

Hi Pavan,

Please try the solution provided by Sakthipriya. In case you face the same problem on client machine then go to Documents and Settings\<windows user id>\Application Data\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Universes (please enable to show hidden folders on windows as "Application Data" is hidden folder) and delete all the folders and universe.

To summarize, when you change the password to reporting database in universe connection, sometimes the universe with new password does not replace old universe on client machine. So if they are using client tools like deski/webi, they get this error.

[Former Member]

Hi Pavan,

BO reports are developed with the full client report designer have the connection strings imbedded in the report itself. Those "strings" point to the reference used by the repository. Therefore, when you update the repository with the new access information (in my case new passwords) it automatically follows with the reports when they are opened.

In the case when a report is developed with the Webi interface that connection information is specifically attached to the universe connection information. This is not automatically updated.

>>The fix was to import each universe from the repository on the server, and

when opened >>click tools

>> connections

>> and click on test for your connection used by the universe.

If the test doesn't come back as successful you will need to make the necessary changes through the edit screen. Save the universe to the local sever and then export the universe back to the repository. Do this to each universe. This refreshes the connection in the universe.

[Former Member]

HI,

Solution -1

These error messages indicate a failure to connect to the database or a failure to authenticate.

The BusinessObjects Universe connection that defines how to connect to the reporting database may be configured incorrectly. This happens if there a data entry error occurred when running InstallUniverse.bat.

Verify the Universe connection configuration details:

1. Start the BusinessObjects Designer.
2. Under Tools, Connections, edit the  connection. Amend any details that are incorrect,
3. Test the connection to verify that the details are now correct
4. Save the connection.

If you cannot connect to the Universe successfully, use a database native client to verify independently that you can access the database using the correct address and login credentials of a BusinessObjects user account.

Solution -2

Close all the browsers completely and try again to run the report