Hello, I am trying to deploy a report model on a report server, my model has only one table and I get this error: The item '/Models' already exists. Can you help me please?

Hi, It seems the model that you deployed has already existed in the target folder on the report server. You can rename the model or change the target folder where you want to deploy the model on the report server. If there are any more questions, please let me know.Thanks.

Hi, To rename your target folder go to the following url http://localhost/Reports/Pages/Folder.aspx Select Show Details (right hand side of screen). Then select Edit on the folder you wish to change. Rename the folder and select apply. If you wish to change to another target folder: In BIDS go to Properties and click on "<<ProjectName>> Properties.." and change the TargetReportFolder. Please let us know if this helped in your question.

I'm deploying a set of new reports.I created the folder manually called: localhost/reports/OperationsI then created one report in BIDS and change the deployment properties to point to this /Operations folderwhen I try to deploy, it gives me an error saying: '/Operations' target item already existsWhy can't BIDS just replace it? I have set the "OverWrite" flag to true? let's say, i delete the folder I created and go back to BIDS and deploy it? Would it then give me the same error next time I go to deploy my BIDS project?

I'm having the same exact problem. I didn't have this problem until I upgraded 2005 to 2008. Is there a Overwrite = true property for report items? I see the property for DataSet but not for report items.

I have had this problem with data sources and the issue came down to permissions in Reporting Services.We had a "Data Sources" folder with the data sources in them and when I deploy everything works fine but when a developer deployed he got the "The item Data Sources already exists" error.The problem was that although he had permission to deploy a report, he did not have permission to deploy a data source. I did not think this would matter as the project setting is to never overwrite data sources and the shared data source already existed so would not need to be deployed but it seems the deploy option still compares the data sources so the user needs to have access to teh folder. I tried browser access and this was not enough so I added a ne role to the system to allow view data sources and then added the developer to that role and this has worked for me.So this issue not just that it cannot overwrite the folder as it isn't even trying to do that. It just wants to verify that it is there or create a new one and it cannot evn check the existence of the folder.I hope this helps with your issue. Have a look at the permissions of the folder that RS is complaining about for the user that is deploying and remember that even if the user is a content manager at the root, they still may need additional access if you have restricted access to the folder.Hope this helpsDaveWeb dev and DBA

I'm deploying a set of new reports. I created the folder manually called: localhost/reports/Operations I then created one report in BIDS and change the deployment properties to point to this /Operations folder when I try to deploy, it gives me an error saying: '/Operations' target item already exists Why can't BIDS just replace it? I have set the "OverWrite" flag to true? let's say, i delete the folder I created and go back to BIDS and deploy it? Would it then give me the same error next time I go to deploy my BIDS project? Don't set that to "true" unless that's what you want. What you need to do is run BIDS as administrator. That was my problem.

Edit role assignment to this folder in localhost/reports and assign the all the roles listed.

I copied all my models to the new user and was getting the same error. However, what I did is right click on the shortcut or the actual file and then properties, then the compatibility tab and checked the "Run this porgram as an administrator" check box. Even though my log in for this computer is a domain admin and placed in the Local Administrators group, I still had to do this and I have had to do this for SEVERAL other programs. Always seems to be a quick first try for me now days and usually it works.