Windows Server 2012下Alfresco Community 4.0.d安装SQL Server 2012报错求助

Hey there, let's tackle this Alfresco 4.0.d + SQL Server 2012 installation issue step by step. I've worked through similar legacy setups before, so here are the most likely fixes to try:

First, let's break down the common pain points for this specific stack and walk through actionable checks:

1. Verify JTDS Driver Compatibility #

Alfresco 4.0.d is an older version, so it’s picky about the JTDS driver version it works with:

• Stick to JTDS 1.2.5 or 1.3.0 (avoid 1.4.x+—these introduce compatibility breaks with older Alfresco code).
• Make sure the correct jtds-<version>.jar is placed in your Alfresco installation’s tomcat/lib folder. Remove any other JTDS or SQL Server driver jars from this directory to avoid conflicts.

2. Fix Database Configuration Parameters #

Let’s tweak your config to align with SQL Server 2012’s requirements:

• Update your db.url to include encoding settings (critical for character handling) and confirm the format:

  db.url=jdbc:jtds:sqlserver://localhost:1433/alfresco;useUnicode=true;characterEncoding=UTF-8
  

• Adjust the transaction isolation level: The value 4096 (SERIALIZABLE) is overly strict and can cause locking issues with SQL Server. Switch to the more standard 2 (READ_COMMITTED):

  db.txn.isolation=2
  

• Double-check user permissions: Ensure the alfresco database user has db_owner privileges on the alfresco database. Alfresco needs full access to create tables, indexes, and stored procedures during installation—even if you pre-created the database manually.

3. Configure SQL Server Instance Correctly #

SQL Server often hides gotchas that block connections:

• Open SQL Server Configuration Manager:
  • Enable the TCP/IP protocol under SQL Server Network Configuration > Protocols for
  • In TCP/IP properties (IP Addresses tab), set the TCP port to 1433 in the IPAll section
  • Restart the SQL Server service to apply changes
• Enable snapshot isolation on the Alfresco database (this fixes concurrency issues that plague older Alfresco versions):
  Run this query in SQL Server Management Studio:

  ALTER DATABASE alfresco SET READ_COMMITTED_SNAPSHOT ON WITH ROLLBACK IMMEDIATE;
  

4. Get the Full Error Log #

The truncated log snippet you shared only shows the start of the error. Look for the full stack trace in:

• alfresco.log (in your Alfresco installation’s logs folder)
• tomcat/logs/catalina.out

The full exception message will tell us exactly what’s failing—whether it’s a connection timeout, authentication error, or schema creation failure. For example, a Cannot create PoolableConnectionFactory error points directly to a driver or connection string issue.

内容的提问来源于stack exchange，提问作者Georges Amichia