Dynamics Community Forum Thread Details

Error on Report Server - rsReportServerDatabaseError

After reinstalling Dynamics 365 on prem and migrating over my databases I am experiencing the following error/issue when attempting to access the reporting services. Note: this is in DEV.

Reporting Services Error
--------------------------------------------------------------------------------

An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError) Get Online Help
Cannot convert to text/ntext or collate to '.......???.???.???.?N¥.???.???....?N¥.???.......' because these legacy LOB types do not support the Unicode supplementary characters whose codepoints are U+10000 or greater. Use types varchar(max), nvarchar(max), or a collation which does not have the _SC flag. Cannot convert to text/ntext or collate to '.......???.???.???.?N¥.???.???....?N¥.???.......' because these legacy LOB types do not support the Unicode supplementary characters whose codepoints are U+10000 or greater. Use types varchar(max), nvarchar(max), or a collation which does not have the _SC flag. Cannot convert to text/ntext or collate to '.......???.???.???.?N¥.???.???....?N¥.???.......' because these legacy LOB types do not support the Unicode supplementary characters whose codepoints are U+10000 or greater. Use types varchar(max), nvarchar(max), or a collation which does not have the _SC flag. Cannot convert to text/ntext or collate to '.......???.???.???.?N¥.???.???....?N¥.???.......' because these legacy LOB types do not support the Unicode supplementary characters whose codepoints are U+10000 or greater. Use types varchar(max), nvarchar(max), or a collation which does not have the _SC flag. Could not use view or function 'ExtendedCatalog' because of binding errors.

--------------------------------------------------------------------------------

I've tried so many things I can't recall what I have all tried so I am open to any and all suggestions. I've migrated over a new copy from the 2016 server, used what I thought was the correct keys, deleted the database and restored from production with new key etc. Any thoughts on what I did to cause this issue?

Quick Links