We are facing a weird issue after we migrated our database location from shared server to a dedicated Windows 2012 server. Database has just been migrated from SQL Server 2008 R2 to SQL Server 2014.
We are using SQL Server 2014 but unfortunately all our pocket queries giving the above error.
Is SQL Server 2014 supported by pocket query? I see all my queries working fine in SQL Server management studio.
Any suggestions on this please? If SQL Server 2014 is supported by pocket query, what can be a probable reason for this plugin not working in our Confluence instances?
Confluence does support SQL 2014 completely.
Configuration changes might be required in SQL 2014.
It will be more helpful if you share the exact issue.
Hi Ranganath, Thanks for your reply. I verified and understand that Confluence does support SQL Server 2014 as a database:- https://confluence.atlassian.com/display/DOC/Supported+Platforms However, I am facing the problem with the plugin that I had installed:- POCKET QUERY. POCKET QUERY plugin was working earlier when my database was SQL SERVER 2008. But may be after migration to SQL Server 2014, it seems to have stopped working with the rendering issue. This is the plugin that I am referring to:- https://marketplace.atlassian.com/plugins/de.scandio.confluence.plugins.pocketquery
My Pocket query version is the latest one available in Atlassian market place. Confluence version is 5.7.3. However, just an update that I was able to execute and show the pocket queries without any errors. I just deleted the previous pocket queries from the config and then again added them. Somehow, it was holding the previous database config even after changing the database config in pocket query. Thanks :)
Hi Felix, Thanks for your response. Yes it works now. I changed the database location and also upgraded the database. I also changed the pocket query database config and checked and it was able to connect properly. But somehow, I had to delete all the existing queries (though the queries were all the same with all their table names) and then again add new queries. Regards, Arya
That's strange. Always when a PocketQuery macro is run, the statement is fetched, then the database connection is created and then the statement is executed. I don't really understand why this happened at the moment. Well.. at least it works again now ;)
Two vulnerabilities have been published for Confluence Server and Data Center recently: March 20, 2019 CVE-2019-3395 / CVE-2019-3396 April 17, 2019 CVE-2019-3398 The goal of this article is...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events