Installing Call Quality Dashboard 2019 problems

Question

Installing Call Quality Dashboard 2019 problems

Viewing 3 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Jo Pattyn SSC-Dedicated Points: 32571 More actions · Answer 1

Hmm, contact microsoft support? Assuming the product is https://docs.microsoft.com/en-us/microsoftteams/turning-on-and-using-call-quality-dashboard

Mr. Brian Gale SSC-Insane Points: 24976 More actions · Answer 2

Did a quick google of the error message and found this forum post:

https://social.msdn.microsoft.com/Forums/en-US/531cc114-ffb5-4bad-9ac0-b1d6f0a1d9af/the-current-transaction-cannot-be-committed-and-cannot-support-operations-that-write-to-the-log

Here, the problem was with permissions.

I also found this post:

https://kb.blackbaud.com/articles/Article/53466

which to me sounds like a space issue. Are any of your databases, logs or disks full?

The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

garryha SSC-Addicted Points: 435 More actions · Answer 3

I thought it may be permissions, but I gave the install domain account sysadmin over the SQL Server and admin on the server so it should be able to do practically whatever it wants.

There is plenty of space on all drives on the Server.

I did have concerns about CQD 2019 being compatible with SQL Server 2016, as per The Microsoft website -

https://docs.microsoft.com/en-us/skypeforbusiness/management-tools/call-quality-dashboard/plan#infrastructure-requirements-for-cqd

But I have spent a couple of hours working with a Microsoft expert and asked and he said 2016 would be fine, but I have my doubts going by the documentation. Despite spending a couple of hours with the expert we were unable to fix the problem.

This reply was modified 5 years, 11 months ago by garryha.