[
https://issues.apache.org/jira/browse/ROL-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Mazza closed ROL-1960.
---------------------------
Resolution: Incomplete
As stated twice before, user needs to turn on SQL server logging to determine
which SQL statement failed, so we would need to know where to look. User
apparently feels volunteer developers should spend 100+ hours trying to figure
out which SQL statement failed for him so he can save 20 minutes not activating
database logging.
The user should also run Roller on either Derby or MySQL to determine it is
indeed a database problem with MS SQL Server and not some other configuration
error that would happen with any database.
If he is unwilling to put in this effort and just reopens the JIRA again, I'll
unfortunately have to delete it (and all other subsequently created JIRAs
reporting the same problem) as spam. We can't keep unsolvable JIRAs endlessly
open.
> Roller not working with user's MSSQL instance.
> ----------------------------------------------
>
> Key: ROL-1960
> URL: https://issues.apache.org/jira/browse/ROL-1960
> Project: Roller
> Issue Type: Bug
> Components: Database Access & Data Model
> Affects Versions: 5.0.1
> Environment: Windows7,Tomcat7,SQL SERVER 2008
> Reporter: 杨勐
> Assignee: Roller Unassigned
> Priority: Critical
>
> I've define database in roller-custom.properties,and Tomcat started
> correctly,The first blog creation failed after first user Account created.
--
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
