Sharepoint and SSRS configuration continued...

So my next step is to deploy the reports in sharepoint. Great! Except now you might run into the following issue:
the full path must be less than 260 characters
how would you go about resolving this-->simple follow the steps below....
1. Create a document library with the document type being null.
2. Else go to the library section and select reports as the type of library.
3. The next step is to ensure that you give a valid name for the library (This is an easy one) so your format would be http:///SiteName/LibraryName
4. Go back to your SSRS project properties. Make sure that the Target Data source folder and the Target Report Folder are configured with the following value as mentioned in step 3 :- http:///SiteName/LibraryName
5. The TargetReportPartFolder need not be filled.... Its upto you. This foldercan be used to deploy to a sub library...
6. The TargetServerUrl would be http:///SiteName
7. Make sure you point the TargetServerUrl to the right version of SQL server.
Click deploy and your report should now be published onto your sharepoint site. Done ain't we?

Comments

Anonymous said…
Great it worked

But a suggestion dont need to create any folder in the sharepoint site.

do the follwing changes in SSRS project properties.

1. Make sure that the Target Data source folder and the Target Report Folder are configured with the following value as mentioned :- http://SiteName/FolderName
2. The TargetReportPartFolder need not be filled.... Its upto you. This foldercan be used to deploy to a sub library...
3 The TargetServerUrl would be http://SiteName
3:48 AM
Post a Comment

Popular posts from this blog

Rhino - ETL

Image
Using Rhino-ETL ( a C# based) framework for developing standard ETL's is pretty easy and one can do a lot of fun stuff with the underlying source data. I just wrote up a quick console app to generate data into a text file and push the same data into a table in SQL Server as well as an external file. Here are the following steps (for the external file push): 1. Create a new C# console application solution in Visual Studio. 2. Target the .Net framework as shown in the below screen shot in your project properties:- 3. Create 3 Sub Folders underneath your project as shown in the following screen shot DataObjects --> Contains the class files associated with each and every table/file in your environment. Example:- if your source file contains student data, then you would create a class file called Student with the individual properties (in relation to the properties) exposed (nouns). Operations --> This primarily contains the class files that contain the activities (a...
Read more

Redshift Experience

Image
Big Data - the keyword given to solutions that can handle massive amount of data usually in the petabyte or greater amount. There are several big data solutions out there and all of them have their unique characteristics which can be useful in different scenarios. I was looking into Cloudera's versions of Hadoop like Impala, Sentry and HBase. All these vary based on the use case. For some of my clients I have leveraged Amazon Redshift, Cassandra (and hopefully soon Apache Hadoop). The architecture of these systems differ but the end goal is the storage and processing of vast amounts of data down to second or milli second based result generation. Focusing on this aspect I am going to give a more detailed insight on Redshift which is a node based peta byte scaled database as well as a high level overview of what I recently implemented. Note: The above diagram is from the Redshift Warehousing article ( http://docs.aws.amazon.com/redshift/latest/dg/c_high_level_system_architecture....
Read more

An Agile process evaluation

In the recent past, I have been working as a scrum master for one of the projects. And since there were two folds to this project, a portion being handled onsite as well as a portion being handled offshore, there were initial hiccups that gradually deteriorated away. But here comes the crux of the problem and where an Agile process has to be evaluated.         We had weekly sprints where a subset of tasks were to be completed and we have a daily scrum between the offshore and onsite team. But the onsite team were persistent on a daily mail sent with the changes being addressed. Now the point of the scrum is to take into account who, what and where the changes have to be made based on the product backlog. Now having status mails as part of the Agile process is indeed a flaw in the fundamental flow. After pointing out this fact, I was counter attacked with several points (some of which were valid to have a status update email) and finally left to ...
Read more