Hi there, We are upgrating our report server from sql 2008 to sql 2008 R2. After updating the Report web service, I couldn't find a proper method to create/upload report via report service 2010; I used to use CreateReport() with reportingService2005. Could anyone give me a guidance on how to create a report to Report Server via Reporting Service 2010? Thanks, Ron

I meant to create/upload report programatically. I got reprot name, path, and the byte[] of report RDL, but couldn't find a way to create it on report server. The service works fine, I can manually upload the report to the server. Any idea?

Hi all, I found this is the method used to create report in ReportingService2010. Although the naming is not very abvious. ReportingService2010.CreateCatalogItem Description: Adds a new item to a report server database or SharePoint library. This method applies to the Report, Model, Dataset, Component, Resource, and DataSource item types.

Sorry to jump in but I was also in the same boat that's why this article came handy to me. Thanks anyway. Though I am using Rs2010.CreateCatalogItem and have supplied the required parameters also but still getting the same error as below. It says path is not valid but only on this server it creates itself these two folders successfully and while creating the report it throws the error only. Code: rs.CreateCatalogItem("Report", name, reportsFolder, overwrite, definition, new Property[] {myprop}, out warnings); Error: The path of the item '/TaGsReports/vsempsyshst01/' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item '/TaGsReports/vsempsyshst01/' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. Would highly highly apreciate your help in this matter. Cheers, Sandy.

I'm using SSRS for 2012 and I'm also getting the following error on the CreateCatalogItem. System.Web.Services.Protocols.SoapException: The path of the item 'https://nleininger-pc.ppi.ppitech.net:5430/ReportServer_SQL12/Objects/' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item 'https://nleininger-pc.ppi.ppitech.net:5430/ReportServer_SQL12/Objects/' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash. at Microsoft.ReportingServices.Library.ReportingService2010Impl.CreateReport(String Report, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, ItemType ItemType, CatalogItem& ItemInfo, Warning[]& Warnings) at Microsoft.ReportingServices.Library.ReportingService2010Impl.CreateCatalogItem(String ItemType, String Name, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, CatalogItem& ItemInfo, Warning[]& Warnings) at Microsoft.ReportingServices.WebServer.ReportingService2010.CreateCatalogItem(String ItemType, String Name, String Parent, Boolean Overwrite, Byte[] Definition, Property[] Properties, CatalogItem& ItemInfo, Warning[]& Warnings) private static void CreateReports(string reportName, string definitionPath) { ReportingService2010 rsc = new ReportingService2010(); rsc.Credentials = System.Net.CredentialCache.DefaultCredentials; rsc.Url = localReportServerWSUrl; Byte[] definition = null; Warning[] warnings = null; try { FileStream stream = File.OpenRead(definitionPath); definition = new Byte[stream.Length]; stream.Read(definition, 0, (int)stream.Length); stream.Close(); } catch (IOException e) { logger.log(e.Message); } try { string parentFolder = localReportServerUrl + "Objects/"; rsc.CreateCatalogItem("Report", reportName, parentFolder, true, definition, null, out warnings); Anyone have an idea on how to move past the error?