[DCMEE-1814] problem with column type on sql server prevents dcm4chee from starting up Created: 07/Mar/12 Updated: 28/Nov/18 Resolved: 28/Nov/18 |
|
Status: | Closed |
Project: | dcm4chee |
Components: | None |
Affects versions: | None |
Fix versions: | None |
Type: | Bug | Priority: | Minor |
Reporter: | Marc Durand | Assignee: | Gunter Zeilinger |
Resolution: | Won't Fix | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original estimate: | Not Specified |
Testing Assignee: | Peter Heiles |
Tracking Status: |
Risk Analysis - Todo, Test Spec - ToReview, Test State - Not tested
|
Sprint: |
Description |
If you check out dcm4chee from trunk, build and deploy it for SQL Server, you will get this error in the log file when JBoss starts up: 09:15:55,031 WARN [ServiceController] Problem starting service persistence.units:ear=dcm4chee-web-ear-3.0.1-mssql.ear,unitName=dcm4chee-arc This error prevents many EJBs from starting up. A workaround is to change the column type in SQL Server to int: drop index sps_status on mwl_item While I am sure this is not the real fix, this will at least allow JBoss to start up error-free and allow dcm4chee to receive images... |
Comments |
Comment by Ruben Perez [ 25/Apr/13 ] |
This is also happening to me with dcm4chee-2.17.1-mssql and MSSQL 2012 Express... What the description of the issue says fixes the problem to me as well |
Comment by Rubin Webb [ 05/May/14 ] |
Same issue for me, the workaround fixed it though. Got stuck for a day or so before I found this, thank you. |