B1i (2005) installation failedSo far: windows XP, MS-SQL 2005 express: ok

[Former Member]

Dear All,

I try to install B1i for NW 2005 on a SBO 2005B installation. I have installed all prerequisites like JDK, MSXML, Tomcat (no blanks in path). When running the setup program and after all information gathered, the connection to the MS-SQL 2005 database succeeds and the final installation step starts but returns the message:

"Initail database failed, make sure Tomcat or mini-http is shut down and please check your database's status and try again"

Looking into MS-SQL shows a database beeing created named localhost/B1i. Tomcat and mini-http are definately shut down. When starting Tomcat, it is accessible via http://localhost:8080.

System Parameters:

windows server 2003

SBO 2005B

java: 1.4.2.19

tomcat 5.5.27 including compat package for 1.4.2.19)

sql jdbc 1.2.2828.100

msxml 4.0 SP 2

I can not find an error in the system. Is there a way to diagnose what is happening and does anyone have an idea where the problem lies?

Ciao, Mathias

[Update]

I have tried JDBC 2.0.1008 and JDBC 2.0.1607 - both lead to a fatal error when trying to connect to the database. I assume this is due to Java JDK 1.4.2 as JDBC requires Java 5.0 (1.5.0)

Does anybody know if I can use JDK 1.5.0_17 instead of 1.4.2_19?

[Update 2]

I have tried to install the B1i on two other servers with identical setup and it worked. However, this will not help me with this machine... On the other side, it shows, that there is nothing wrong with the procedure I am using

I found by the way: B1i works fine with MSSQL 2005 Express, it works with jdk 1.5.0.17 (and then JDBC 2.0)

[Update 3]

So far:

windows XP, MS-SQL 2005 express: ok

windows XP, MS-SQL 2005 express, SBO2005A: ok

windows 2003, MS-SQL 2005 SBO2005A: fail

windows 2003, MS-SQL 2005 SBO2005B: fail

windows 2003, MS-SQL 2005 SBO2007A: ok

windows 2003, MS-SQL 2005 Netweaver 2004S: fail

Unfortunately the three servers where it fails are the ones I need to use for production

The precise error state is that the install routine creates the database in SQL 2005 and then reports that it can not create the database. Is there something I should check in SQL 2005?

Edited by: Mathias Wilhelm on Feb 11, 2009 5:17 PM

[Eneveux · Accepted solution]

Mathias,

When you try the install, does the B1i database exist in SQL Server? If it does ... remove it and then re-install.

HTH,

Eddy

[Former Member · Accepted solution]

Salut Eddy,

I have read this in one of the notes and tried it, but it does not resolve the issue. The error appears also on a clean system where I try to install the first time. So far I can only determine that the error shows up on MS-SQL with SBO2005x or NW2004S on it but not on empty MS-SQL or with SBO2007 on it.

But thanks for the reply, after 4 days on it you go nuts

Ciao, Mathias

[Eneveux · Accepted solution]

Mathias,

Something you can check is that B1i 2005 requires the version of Tomcat and the JRE for B1i 2005 is JRE 1.4.2 + Tomcat 5.0.

Eddy

[Former Member · Accepted solution]

Salut Eddy,

I tried it with tomcat 5.0.30 - no success. JDK is 1.4.2.19

I tried it with tomcat 5.5.27 - no success. JDK was 1.4.2.19 and 1.5.17

I checked the database: The structure is created but the tables are not created. As the user 'sa' has full admin rights it must be with the access path to the database that is wrong. What I do not understand is, why the installation routine is able to connect to the database to create B1i and then unable to create the tables. I checked in the log files of the db and found no error messages. I tested this as well by using a wrong password for sa or a wrong user. In both cases, the installation routine fails already when checing the existence of B1i database

[Update]

In the meantime:

Checked permissions on database

Checked that administrator is member of local admin group

Checked JAVA_HOME environment variable

Found collation SQL_Latin1_General_CP1_CI_AS for working setup and SQL_Latin1_General_CP1_CS_AS in failing setup

Checked all security settings by comparing to working setup

Checked event viewer and found no errors

Checked all log files and found no errors

Checked that sa can create tables manually in localhost\B1i

Ciao, Mathias

Edited by: Mathias Wilhelm on Feb 12, 2009 2:36 PM

[Eneveux · Accepted solution]

This issue has been moved to SAP Support.

[Former Member · Accepted solution]

For those reading this threat:

The problem lies with the collation of the MS-SQL database. It was set to case sensitive. The installation routine issues a SQL statement that uses different cases. The solution is to change the default collation of the MS-SQL database to case insensitive. This implies a reinstallation of MS-SQL and rebuild of the master database as described by Microsoft. Take a backup before doing it!

Many thanks to the superb support by Eddy and his colleagues from SAP

Mathias