I am attempting to install BI 2025 Patch 3 on a new Window Server 2025 Standard server. I had one of my DBAs create blank CMS and Audit databases on a SQL Server 2019 server. My 64-bit ODBC connections (CMS and Audit) using the Microsoft ODBC Driver 18 for SQL Server test out just fine.
When I try to connect within the install program…
I get this error…
I do see this in the installation documentation…
During installation process, the following character usage is not supported for password creation:
- For a BI Administrator, you cannot have: “ ‘, space tab, and a trailing backspace ().
- For cluster key, you cannot have: “ ‘, $, #, and a space tab.
- For SQL Anywhere, you cannot have: "&`', <>, @, , |, (), , {}, ^, $, *, +, ?, ., ;, and space tab.
We are using SQL Server, not SQL Anywhere, so that password restriction should not apply, right? I do have two asterisks and a comma in my password. We are using that same password for the BOBJ CMS and Audit databases in our existing 4.3 SP04 Patch 7 system, but that we recently changed and was not used during the install.
Interestingly, it is making a successful connection at some level because it is able to populate the list of databases on that server.
But I get the error above when I hit the Next button.
Do I need to adhere to those SQL Anywhere rules for my SQL Server password? Is there an installation log file some where that will tell me what is actually the problem?
Thanks
I have tried a very simple password, 7 characters and an exclamation point. Same error.
I have already reached out to our BOBJ support provider on this issue and they are investigating.
Check C:\Program Files (x86)\SAP BusinessObjects\InstallData\logs then a date named folder for your installation date for install log files. There should be an ErrorsAndWarnings.log file that can be helpful.
If the files aren’t there yet, they will be in the User’s documents for the account running the installation.
1 Like
I found the ErrorsAndWarnings.log file in…
C:\Users\MyUser\AppData\Local\Temp\2025.08.19.12.28.00
All that is there are 19 instances of this message…
Error: Identifier not found in lookup: [INS00104]
You are going to love this.
I did reach out to our BOBJ support provider. They reviewed all the details…
- Windows Server 2025
- Microsoft Visual C++ 2015-2022 Redistributable (x64) - ver. 14.44.35211
- Microsoft ODBC Driver 18 for SQL Server (downgraded to 17 with no effect)
Here is an excerpt from the Product Availability Matrix for BI 2025…
To me that says Window Server 2025 is good to go, right?
If I click on the link toward the bottom of that screenshot…
Please check supported Operating System details on Common Cryptographic Library (CCL / SAPJCE) PAM Link
It takes me here. And if I filter on WINDOWS FOR X86_64 I get this…
Which makes no mention of Windows Server 2025. Is that meaningful? I have no idea.
The recommendations from support were…
- Download the latest patch which is BI 2025 Patch 4. I was trying to install Patch 3.
- If that doesn’t work, spin up a Windows Server 2022.
- In the meantime, they would escalate the issue to SAP.
I did download Patch 4 and get it installed successfully.
Did I read the PAM incorrectly and try to jump to Windows Server 2025 too soon? But then it again it seems to be working for me know with Patch 4.
I did request that a KB be published on this issue. I am not going to hold my breath on that.
Noel
Seems typical SAP documentation. 
They may have updated the PAM for patch 4 but didn’t indicate that it was only available with that patch.
1 Like
As far as I know, the OS compatibility is always at the SP or major release level, not the patch level (unless specifically noted). So I don’t think it’s intentional that Patch 4 is the first version to support Win25, but rather the issue you had was a bug in Patch 3. I think you’re reading the PAM correctly, that BI 2025 supports Win25.
