Visual Studio Upgrade from VS2019 --> VS2022 causes Reporting Services Project to Fail with this message: "Project item ‘4294967294′ does not represent a file"

Question

Hi All,

I recently upgraded Visual Studio 2019 Professional to VS2022 Professional. The installation completed with no errors.

Our environment hosts a number of different Solution Types: C#, SQL Server, and Reporting Services.

We use TFS (Team Foundation Server) as our Source Control system.

Since the upgrade, all project types are working except Reporting Services. The Reporting Services projects receive this error message:

• Project item ‘4294967294′ does not represent a file

I have read previous articles regarding this error message, but they are quite old. The primary blog which offers a fix is no longer available.

This particular solution has over 1000+ SSRS reports defined, with 66 projects within the solution. The problem appears to be a strange interaction between TFS and SSRS.

How do I get around this error?

VS2019 works with no problems.

Thanks for your help.

--Dan

Answer 1

Hi @DJAdan ,

Thank you for taking time to post this issue in Microsoft Q&A forum.

I notice that this may be a known issue which reported here: Error message when click on the .sln reporting solution "project item 4294967294 does not represent a file". The fix has been internally implemented and is being prepared for release.

I think the solution for this issue is to wait for the newly VS update to be released. You can follow up that thread and VS Product Team will inform you once the update becomes available for download.

Thanks for your understanding, have a nice day.

Best Regards,
Tianyu

• If the answer is the right solution, please click "Accept Answer" and kindly 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.

Answer 2

Hi Tianyu,

Thank you for the update.

Is there an expected release-date for the bug-fix?

--Dan