SQL Server 2005 upgrade fails and stops the server

• Type: Regression Bug
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 6.0.12 EE, 6.1.0 CE RC1, 5.2.X EE
• Fix Version/s: --Sprint 12/11, 6.1.0 CE RC1
• Component/s: Infrastructure > DBs, Upgrades
• Labels: None
• Environment: Tomcat 6.0 + SQL Server 2005. Firefox.4.0.0. 5.2.x. Revision 79750. ; Tomcat 6.0 + SQL Server 2005. Firefox.4.0.0. 6.0.x. Revision 79750. ; Tomcat 6.0 + SQL Server 2005. Firefox.4.0.0. Trunk. Revision 79750.
• Branch Version/s:
  5.2.x, 6.0.x
• Similar Issues: Show 3 results ; ;

  LPS-3911	SQL Server 2005 DB Upgrade Issue
  LPS-29903	NTEXT has been deprecated in SQL Server 2005
  LPS-22717	Kaleo deploys with errors in SQL Server 2005

1. Get a 6.0.6 Bundle
2. Get a SQL Server 2005 database up
3. In your portal-ext.properties, put:

jdbc.default.driverClassName=net.sourceforge.jtds.jdbc.Driver
jdbc.default.url=jdbc:jtds:sqlserver://localhost/lportal
jdbc.default.username=sa
jdbc.default.password=password

lucene.store.type=jdbc
lucene.store.jdbc.auto.clean.up=true
index.with.thread=true
index.on.startup=false
lucene.store.jdbc.auto.clean.up=true
lucene.store.jdbc.dialect.microsoft=org.apache.lucene.store.jdbc.dialect.SQLServerDialect

4. Start up 6.0.6 and make sure it runs ok.
If you want, you can check the Lucene table type to verify that it is varchar

5. Shutdown 6.0.6
6. Get a 6.0.x bundle and point it to the same database.
You should use the same portal-ext.properties.
7. Start up 6.0.x.

You well see the auto stopping in tomcat.
Can see the error message"Stopping the server due to unexpected startup errors".