SSRS 2016 DeviceInfo Name already exists Parameter name: deviceInfoName

Ravishanker Maduri 1 Reputation point
2022-03-23T21:42:49.577+00:00

DeviceInfo Name already exists Parameter name: deviceInfoName error cooming here and there in production.

is there fix for this issue, i see the error is coming since older version. But not yet had a fix from Microsoft?

Hope to get a fix for this issue.

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,807 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Isabellaz-1451 3,616 Reputation points
    2022-03-24T02:03:08.51+00:00

    Hi @Ravishanker Maduri

    Did you encounter this error when you view report in Report Viewer?

    If so, based on my research, this issue may be caused by an internal recycle job running on the Reporting Service web service. If the time interval of refreshing report coincides with recycle, then they will clash, the report refresh will fail. You can consider to increase the recycle time to decrease the possibility to encounter it. Try to change it in the config file which locates at xx:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config.

    Another option to help in this scenario is to specify the URL to the report via the reportserver and set rc:toolbar=false. This forces SSRS to use the meta refresh tag. Instead, we use HTNL meta tag in web page to support AutoRefresh for reports.

    I refer to this thread,hope this will help you:https://social.msdn.microsoft.com/Forums/sqlserver/en-US/5b4acc6d-058b-4c40-b916-cc634bb35f61/ssrs-2012-deviceinfo-name-already-exists-parmeter-namedeviceinfoname

    Best Regards,
    Isabella


    If the answer is the right solution, please click "Accept Answer" and upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments