[ 
https://issues.apache.org/jira/browse/SYNCOPE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-401:
-------------------------------------------

      Component/s:     (was: core)
                   documentation
         Priority: Trivial  (was: Blocker)
    Fix Version/s: 1.2.0
                   1.1.3
         Assignee: Francesco Chicchiriccò

I have just updated the mentioned wiki page.

Please write in mailing list for support before opening "Blocker" issues, 
thanks.
                
> Deploying syncope.war with MSSQL server settings to Tomcat on Windows results 
> in Error listenerStart
> ----------------------------------------------------------------------------------------------------
>
>                 Key: SYNCOPE-401
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-401
>             Project: Syncope
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 1.1.2
>         Environment: Microsoft Windows 2008 R2, Microsoft SQL Server 2008 and 
> 2012
>            Reporter: Mathias Holdt
>            Assignee: Francesco Chicchiriccò
>            Priority: Trivial
>             Fix For: 1.1.3, 1.2.0
>
>
> Following the installation guide "Run Syncope in real environments" results 
> in a generic error when deploying syncope.war to a Tomcat container (7.0.41) 
> on Windows 2008 R2 + MS SQL Server 2008/2012. 
> I tried a few times on different combinations of Windows and SQL Server 
> (2008/2012), all resulted in the same error (non descriptive Error 
> listenerStart). I then added a logging.properties to the deployed web 
> archive. This gave me a terrible long exception. One of the nested exceptions 
> (CannotReadScriptException) told me that the file 
> [quartz\tables_sqlserver.sql] was not found. I noticed that the file was 
> actually named tables_sqlServer.sql (with uppercase S).
> I renamed the file to tables_sqlserver.sql (all lowercase) and successfully 
> deployed to all my installations afterwards.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to