Source of Bex Browser SAP system entries (not saplogon.ini?)

Question

I hope someone could help to clarify what I presume is a fairly simple query.
I will run through the steps I take to reach my point of confusion:
1. I navigate to "Start Menu\Programs\Business Explorer\Business Explorer (SAP BW 3.x)" and open the Browser (SAP BW 3.x).
2. A "SAP Logon" window (similar to a cut-down version of SAP GUI's SAP Logon program) opens, I select the appropriate BW system from the list and logon. I have just ticked the box for "Use Selected System  as Default" at this stage.
3. The BW Browser opens, I navigate to ANY report and double-click to open.
4. Microsoft Excel 2003 opens in the background, I can see the Business Explorer add-on as well.
Now this is the problem stage at step 5 and a complete oddity at step 6....
5. Another "SAP Logon at SID" window opens, but if I enter my logon details again I get an RFC_ERROR_PROGRAM error.
6. At this point I repeat step 3 above but instead of typing in my password at step 5, I click the "System" button which opens the mini "SAP Logon" windows for BW Browser. It is here I notice that all the SAP system entries which I presumed were populated from saplogon.ini at C:\Windows, are in fact from a much older version of the saplogon.ini I previously had.
So my real question is about step 6, why/how are the SAP system entries being populated from an older version of saplogon.ini? Does the BW Browser cache these entries somewhere else locally?
For reference, I am running SAP GUI 710 at Patch Level 12 & BW Add-on Patch Level 4 for 710. I have tried updating everything to the latest version/patch levels but with the exact same result. I've done a complete rebuild before a new 710 install and still can't figure this out.
Thank you.

Answer 1

Hi David,
Thank you for providing details of those SAP Notes, unfortunately they haven't helped to resolve the issue.
We do not use an Environment Variable to make another SAPLOGON.ini file known to the SAP Logon Control.
On running the trace, it appears quite apparent that SAPLOGON.ini in C:\Windows is being utilised. My first thought on seeing the trace file was that a SAPLOGON.ini file might be present in the "current directory" identified as N:\My Documents, but this wasn't the case.
Steps 1 and 2 are void, the standard .ini file should be getting picked up in step 3:
Wed Aug 05 15:09:45 2009 0001  DpaPersPar::BasicInitialization()  current directory N:\My Documents
Wed Aug 05 15:09:45 2009 0001  DpaPersPar::BasicInitialization()  SAPLOGON_INI_FILE not set; use SAPLOGON.INI
Any other thoughts?
Thanks.
Simon