Pulse 5.8.0 SQL Server Backend TM1 10.2.2 & Planning Analytics MSServer2016 Error


We currently have 3 Pulse monitored TM1 10.2.2 (MS Server 2012 R2) environments writing to a SQL Server 2014 database successfully.
I am trying to add 2 Planning Analytics servers (MS Server 2016) to write to the same database.
All are running Pulse 5.8.0

Pulse is operational using the default database on the two new servers.

But after adding the same line in the config file as the current running servers to point the two new servers to the same database
JDBCURL = DBDEVDWH01:1433;databaseName=TM1Pulse;integratedSecurity=true
I get an error.

When going to the pulse through #removed#:8099 i get a white overlay window stating the following.
ā€œErrors when initalizing the Pulse Repository! Refer to ā€˜Pulse For TM1/Logs/pulse.logā€™ for more detailsā€

The pulse log error is as follows

2019-01-15 13:47:26 INFO InitContextListener Pulse Version is: 5.8.0
2019-01-15 13:47:26 INFO InitContextListener Pulse Listener configured on port 8093(https)
2019-01-15 13:47:26 INFO ServerHelper Server name is: #removed#
2019-01-15 13:47:26 INFO ServerHelper Working Directory is: d:\Program Files\Pulse for TM1
2019-01-15 13:47:26 INFO InitContextListener Setting SSL certificate trust
2019-01-15 13:47:26 INFO InitContextListener Using SQL Server database #removed#:1433;databaseName=#removed#;integratedSecurity=true
2019-01-15 13:47:26 INFO com.zaxxer.hikari.HikariDataSource HikariPool-1 - Startingā€¦
2019-01-15 13:47:26 INFO com.zaxxer.hikari.pool.PoolBase HikariPool-1 - Driver does not support get/set network timeout for connections. (This operation is not supported.)
2019-01-15 13:47:26 INFO com.zaxxer.hikari.HikariDataSource HikariPool-1 - Start completed.
2019-01-15 13:47:26 INFO InitContextListener Connection pool created: #removed#:1433;databaseName=#removed#;integratedSecurity=true
2019-01-15 13:47:26 INFO InitContextListener Docs database is version: 64
2019-01-15 13:47:27 INFO InitContextListener Updating docs database to version: 65 statement: 1
2019-01-15 13:47:27 INFO InitContextListener Updated docs database to version: 65 statement: 1
2019-01-15 13:47:27 INFO InitContextListener Updating docs database to version: 65 statement: 2
2019-01-15 13:47:27 INFO InitContextListener Updated docs database to version: 65 statement: 2
2019-01-15 13:47:27 INFO InitContextListener Updating docs database to version: 65 statement: 3
2019-01-15 13:47:27 FATAL InitContextListener Unable to update docs database to version: 65 statement: 3
com.microsoft.sqlserver.jdbc.SQLServerException: Cannot find the object ā€œProcessLog.uidx_ProcessLogā€ because it does not exist or you do not have permissions.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:217)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1655)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:885)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:778)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7505)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2445)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:191)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:166)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeUpdate(SQLServerStatement.java:703)
at com.zaxxer.hikari.pool.ProxyStatement.executeUpdate(ProxyStatement.java:117)
at com.zaxxer.hikari.pool.HikariProxyStatement.executeUpdate(HikariProxyStatement.java)
at com.cubewise.servlets.InitContextListener.initialiseDocsDB(SourceFile:749)
at com.cubewise.servlets.InitContextListener.contextInitialized(SourceFile:505)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5157)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5680)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1018)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:994)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1296)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:2039)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2019-01-15 13:47:27 WARN InitContextListener There were errors when Initalising the DB
2019-01-15 13:47:27 WARN InitContextListener Db Users will not be createdā€¦
2019-01-15 13:47:27 WARN InitContextListener Db Admin settings will not be appliedā€¦
2019-01-15 13:47:27 FATAL InitContextListener Errors when configuring Pulse Database
2019-01-15 13:47:27 INFO InitContextListener Source Controls remote scripts deployed.
2019-01-15 13:47:27 WARN InitContextListener Jobs will not be scheduled
2019-01-15 13:47:27 WARN InitContextListener Windows Authentication will not be set
2019-01-15 13:47:27 WARN InitContextListener VCS optimisations will not be CACHED
2019-01-15 13:47:27 INFO ro.isdc.wro.http.WroFilter wro4j version: 1.7.7
2019-01-15 13:47:27 INFO ro.isdc.wro.http.WroFilter wro4j configuration: ro.isdc.wro.config.jmx.WroConfiguration@6df9d92a[

The server service account users have been added to MS SQL server and given write and read access on the database.

I have added the same sqljdbc_Auth.dll file to the system32 directory as the original servers as well as trying the new version 7 file. Both still result in the above errors.

Therefore my questions are as follows.

  1. Had any one else come across this error and know a fix or work around?
  2. Can Pulse monitor 10.2.2 and PA using the same MS Sql Server DB ?


Hi @Dou4242,

By the error, it seems that the account is not able to perform Drop index operation, such index must exist as it was introduced in the earliest versions of Pulse 5.6. Perhaps the account is able to read and write but not able to alter/drop objects in database, Could you check if this account is the DB owner of the Pulse database?

Now, regarding your question " Can Pulse monitor 10.2.2 and PA using the same MS Sql Server DB ?", The answer is Yes, if by PA you are referring to Planing Analytics Local (PAL); Pulse is able can write to an unique SQL server from diverse Pulse installations, [1] gives more details on this. However, it is important to remark that, for this scenario to work properly, the same version of Pulse should be installed across in all the TM1 hosting severs. But, If you are referring to PA as the IBM Cloud Planning Analytics, Pule 5.x cannot track cloud installations, We are working towards the next major release of Pulse which will be cloud compatible.

[1] https://code.cubewise.com/docs/pulse-database-migration-into-sql-server?rq=sql%20server (Last time browsed, Jan 2019)

Best Regards,


1 Like

Thanks Erik.

Granted both service accounts ddl access and its now working and migrating the db.

Also the setup is PAL.

Thanks again