We are using Buisness Objects to report on our HP Openview Service Desk. Our company has decided to move our current Service Desk database to a new server. Now, I am unable to report on the Service Desk database. How do I repoint BO to the new database location? I thought it would be as simple as repointing the DSN in OBDC to the new SQL Server but when I do that, I get an error message when trying to login that my account has been disabled.
The BO username is disabled while logging into the application or the DB username
If its BO userid and the repository DB has been moved then read the below suggestion else ignore it.
And check the SQL server DB for the disabled user for which reports are not working.
You need to recreate the BOMAIN.key file from Supervisor->Admin by running Safe Recovery and pointing to the new database string.
The initial post was referring to changing the location of a source database used for reporting (accessed via a universe connection) and not the database(s) hosting the Business Objects repository, I believe.
Yes, I am getting the disabled error message when trying to login to BO. I will was thinking about heading in the direction of doing that safe recovery but now I know that is the answer. I will try that and let you knoe. Thanks.
Ok, I recreated the BOMAIN key. After I changed the ODBC to the new server on my client machine to point to the new SQL Server, I still get the “your login has been disabled by your supervisor.” error message.
Here are the steps I followed,
Changed ODBC on the Server where supervisor is loaded to the new SQL Server.
Logged into Admin portion of Supervisor.
Did a safe Recovery and created a new bomain key.
Copied new bomain key into locdata folder on client machine.
Changed odbc on client machine to new server
This is the part I where I get stuck when trying to login in BO from client or server machine.
Update- I also check the security on the SQL Database and the account I am connecting to has DBO on all the databases I am trying to hit.
-Check the repository schema in the new database. Ensure that all the repository tables are present.
-Safe recovery showed no errors/warnings.
-What is the version of SQL server DB where the old schema was moved (SQL 2005 not supported by BO 6.5.1 unless SP4 is installed).
Login to Supervisor with a reserve General Supervisor account if any. Also try to login to Designer or Reporter.
See that the correct domain is used while logging to Supervisor/Designer/Reporter, if there are more than one .key files in locdata folder.
(BOB member since 2005-07-18)
(BOB member since 2002-06-20)
(BOB member since 2005-07-18)