[resolved] Incorrect syntax near the keyword 'top' In TalendBPM.

[Anonymous]

Hi,
I have configured Talend Bpm runtime container Back end with SQL SERVER(2012). I have created tables successfully in the Databases. but while opening bpm portal we are getting an exception like "Unable get cases from server" in red colour and also in the log file we are getting an exception like below. please find the following attachmnet
07:08:55,744 | ERROR | tp1892124631-165 | rnate.util.JDBCExceptionReporter  234 | 246 - talend-bpm-server - 5.10.0 | Incorrect syntax near the keyword 'top'.
07:08:55,745 | ERROR | tp1892124631-165 | vices.impl.DefaultCommandService   48 | 246 - talend-bpm-server - 5.10.0 | exception while executing command org.ow2.bonita.facade.rest.RESTServerAPIInterceptorCommand@5ec13917: Unexpected Exception arrived in Bonita: could not execute query
07:08:55,996 | ERROR | qtp1892124631-99 | t.provider.GenericObjectProvider   95 | 215 - talend-bpm-deployer - 5.10.0 | Error while decoding <org.ow2.bonita.facade.exception.BonitaInternalException>
  <detailMessage>Unexpected Exception arrived in Bonita: could not execute query
</detailMessage>
  <cause class="org.hibernate.exception.SQLGrammarException">
    <detailMessage>could not execute query</detailMessage>
    <cause class="com.microsoft.sqlserver.jdbc.SQLServerException">
      <detailMessage>Incorrect syntax near the keyword &apos;top&apos;.</detailMessage>
      <stackTrace>
        <trace>com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:196)</trace>
        <trace>com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1454)</trace>
        <trace>com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:388)</trace>
        <trace>com.microsoft.sqlserver.jdbc.SQLServe
can any one please help me 
Thanks in advance.

[Anonymous]

Hi jillu, 
Talend BPM is only certified for MS SQL Server 2008 R2 (not SQL Server 2012 which you use). Any change to switch back to 2008 R2?
Dietmar 

[Anonymous]

Thanks dlenzen,
we Resolved the issue.