USR0061 error while loading BusinessQuery

When trying load BusinessQuery from Excel, I get an USR0061 error message (The key file name given in the command line does not exist in the data folder). I have no problem loading BusinessObjects. What is this error caused by? And how can I fix it?

I’m using:
Windows 2000 SP4
BusinessObjects 5.1.5
Office 2000 Professional

Thanks in advance!


proteo2000 (BOB member since 2004-06-29)

Hi, proteo2000, and welcome to BOB! :mrgreen:

What is the name of the key file in your LocData subdirectory of BusinessObjects? Is it the standard BOMain.key name?


Anita Craig :us: (BOB member since 2002-06-17)

Hi Anita:

The .key file had a name different from the standard bomain.key. I’ve already changed it to bomain.key but the problem stills. The .key file is in the LocData folder.


proteo2000 (BOB member since 2004-06-29)

I’m sorry – since we don’t have BusinessQuery (we only did an evaluation of it a few years ago) – I am out of ideas.

If no one else has a thought, I’d suggest you contact tech support.


Anita Craig :us: (BOB member since 2002-06-17)

Are you starting Excel with command line parameters?


KSG :us: (BOB member since 2002-07-17)

No, I start excel thru the default shortcut. Even calling excel from the command “excel.exe” I have the same result.


proteo2000 (BOB member since 2004-06-29)

Do you have BusinessObjects in your path? BusinessQuery requires that BusinessObjects be in the environment path, perhaps that is something to check next…


Dave Rathbun :us: (BOB member since 2002-06-06)

I knew BusinessQuery 5.1 doesn’t requires to be in the path, but I made the test anyway. I tried with both “BusinessObjects 5.0” and “LocData” paths but BusinessQuery is still crashing.


proteo2000 (BOB member since 2004-06-29)

Is your Security File “Security Domain (*.key)” setting “Local” or “Shared”?

-If Local, is the BOMAIN.KEY in the “Local Data” file location?
-If Shared, is the BOMAIN.KEY in the “Shared Data” file location?

If Local or Shared, does the user have the proper permissions to the appropriate file location? I thnk they only need read.


KSG :us: (BOB member since 2002-07-17)

The security domain is Local.

The .key file is in the LocData folder, and the user has Admin rights on it, but the .key file has a name different from BOMAIN.key.

Is it neccesary for BusinessQuery that the name of the .key file is BOMAIN? I have no problem with the other BusinessObjects products.

Should I rename the .key file to BOMAIN or I must regenerate it with this name?


proteo2000 (BOB member since 2004-06-29)

I don’t know if the key file has to be BOMAIN.KEY with BusQuery. I’ve never used another name.

What happens if you regenerate it, using BOMAIN.KEY? Does it work?


KSG :us: (BOB member since 2002-07-17)

I thought it had to be BOMain.key. That’s why I asked you above – and I thought you said you’d tried renaming it that.

So did you already try the rename to BOMain.key or not?


Anita Craig :us: (BOB member since 2002-06-17)

Finally, I’m back… Sorry by the delay, I had to reformat my PC. In the process, I installed Windows XP. Since then, I have no problem with the BusinessQuery.

As far as I can see, BusinessQuery works fine with XP users, and there is no problem if the .key file has a name other than bomain.key (at least with the 5.1.x versions of BusinesObjects).

I think BQ works fine because of Windows XP, and not because I reformated my PC. The problem with BQ was present in the PCs with Windows2000, and was originated by a migration of the BusinessObjects repository, and the regeneration of the .key file (with a different name for avoiding users connecting to the old server). Only the users with BusinessQuery under Win2K (a few), had problems. So, the BQ reports were mostly redone, and the BO supervisor didn’t make a new version of the .key file under the name of “bomain” for “version integrity” reasons.

Anyway, I’ll try to convince the supervisor to recreate the same .key file, but now under the “bomain.key” name.

Thanks for your help!


proteo2000 (BOB member since 2004-06-29)