It would be much appreciated if any expert would have any suggestion.
I use reporting service with SP2 and integrated with MOSS 2007 platform.
I found I couldn't jump to a URL while the URL contains my MOSS server name on it.
For example, I simplely put http://mymoss/mysite on the "Jump to URL" property on my report, and it works fine while I read it on BI Development Studio, but it failed after I deploye it on my MOSS server.
I cannot click the item contains this hyperlink.
Although I could use below java script to open the same URL. ( Type below script on the Jump to URL property "javascript:void(window.open( 'http://mymoss/mysite', '_blank'))")
But the problem is that the URL I used is the link to MOSS's list with a very long path, so the jave script will be truncated after about 128 character length.
It's really strange that I couldn't open the URL contains the MOSS server name directly from the report on this MOSS server.
Your suggetion or solution will be very important to me.
I have created a web part in ASP.Net. this web part is extracting data from the sql server database and displaying it on the web part page. This web part is working fine with asp.net application, but when i deploy it with MOSS. it is reaising security exception error like.
Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
I have made the entry under the safe control list of web.config file. but still i am getting error any suggestion wud be highly appreciable..
I am stuck on this and its happening no matter what I do. I have a huge project that holds tons of reports. Most are sub-reports.
I have 5 sections I will just use one for example
communictions (totals)
jump to report - summary data
Jump to report - detail data.
The when I get to the detail data I always get the error:
The path of the item '(null)' 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. (rsInvalidItemPath)
I have tried to do all sorts of things and no matter what I do I cant get it to work.
This is a web application using the ReportViewer for the web, SQL Server 2005 SP2
I have searched high and low for an answer to this and nothing works, not even the get instead of the post.
I have a report that uses report parameters and navigation in the textbox. When I click in the textbox, it jumps to the same report, but I cannot see the report parameters any more(hidden ). I cannot change the report parameters. When I use only the report paramenters (no navigation option), they appear always during the run time. How can I do to keep the report parameters visible all the time using "jump to the same report"??
Can some participants in this forum provide ideas on suggested training for somebody with a basic knowledge of SQL (started working in this field 6 months ago and still feel like a newbie beginner).
I assume I should focus on getting T-SQL nailed down before delving into the SSIS piece of SQL Server 2005?
Maybe there are a few companies that seem to give good practical knowledge and are located in the greater Los Angeles metro area?
Is it better to get certified through a 1 week or 2 week course via companies like Trainingcamp - does that really give you the practical skills to jump up several levels at one does at work?
Hope I can get some suggestions or direction on where I could best post this question for answers.
I am upgrading my application's SQL Server from 2008 R2 to 2012.
As discussed in the below URL I am able to see the Identity jump after I upgrade and the server is restarted.
Now since I cannot afford this and at this moment I do not have the time to create a sequence with NOCACHE and test it again I have to go ahead and add trace flag 272 in the start up parameter as this is the only solution which I can implement and even rollback without much hassles.
[URL] ....
What I got to know, this flag will disable the new feature of IDENTITY property that has been implemented as part of SQL Server 2012 and will make it work like it was doing in SQL Server 2008 R2.
But I want to know implementing this flag would impact any other feature or performance (except the performance of IDENTITY) of SQL Server.
Hi there- I want to see the reports developed in SQL reporting Services from Share point Server 2007. I see two methods to do this and would like to know the advantages / disadvantages between these two methods. 1) Configure Report Server to run in Share Point Integration mode and deploy the SQL reporting services reports directly in the Share point site. 2) Configure Report Server to run in Native mode and deploy the SQL reporting services reports in a web site. Just add the link for these reports in the Share point Site. Thanks in Advance.
Hey guys, I am working on the database side of an upgrade for our Sharepoint site to MOSS 2007. The current environment is SQL Server 2005 (SP2) clustered (8 dual core CPUs, 32GB RAM) with about 0.75 TB of data (about 10 different dbs). I noticed that the collation on the sharepoint databases are not the same as the system databases and other user databases.
The collation setting for our current Sharepoint is: Latin1_General_CI_AS_KS_WS
The collation setting for MOSS is: Latin1_General_CI_AS_KS_WS
The collation setting for our system databases is: SQL_Latin1_General_CP1_CI_AS
The collation setting for the server is: SQL_Latin1_General_CP1_CI_AS
I am aware of the following issues with having different collation settings between user databases and system databases. http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/07/12/883.aspx
http://support.microsoft.com/kb/843578
Currently nothing is broken, everything is working fine; So my question is: What does best practices suggest I do in this situation? Do I leave everything as is? Do I change the server collation and system databases?
Any suggestions and feedback will help. Thanks, Reghardt
Is anyone attempting or has anyone successfully deployed MOSS2007 with a SQL 2005 Database Mirror on the backend? We are doing it in our lab with the automatic failover (principal, mirror & witness) and the SQL portion works great. The only issue is we have is that we have to manually switch MOSS over (via Sharepoint 3.0 Central Admin or stsadm) to the new content database on the other server. Thank you
We have reviewed the White Paper that Microsoft offered with no help to our issue.
We have 64 bit MOSS with integrated SRS. This works quite well. You lose data-driven subscriptions until the release of SQL 2008. We want to build a custom subscription/workflow solution that renders reports and pops them into SharePoint lists. What we want to do is render thousands of reports into SharePoint document libraries and use workflow rules to route them to file shares, emails, approvals, etc.
This can be done manaully by right clicking the RDL in a report library and selecting Manage Subscriptions. This brings up a web page listing existing subscriptions (_layouts/ReportServer/ManageSubscriptions.aspx). This page does not write to a SharePoint list, but a set of tables in the ReportServerIntegrated database. I can see the tables and stored procedures that do the work. I cannot find a programming interface to create the subscriptions in code. I guess I can just call these stored procedures.
I also posted in the SharePoint forum, but maybe someone here can shed some light on this frustrating issue:
We have Reporting Services integrated with our MOSS environment. Several reports were set up for autmatic delivery via subscription. This was pre SP1 times and the reports ran just fine (they are not data driven reports). Whether it is related or not I don't know, but two weeks ago we upgraded to SP1 without any problems. Shortly after that, our users stopped getting their reports via email. When I go to the reports and click on "Manage Subscriptions", the history of subscriptions shows that the report ran, but then there is an error message under last results saying
"The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)"
I tried recreating reports, setting up new data connections, re-subscribing... nothing works. Checked SQL server logs - they seem to be OK; checked SharePoint logs - they show error with few minutes off the scheduled report, so I don't know if this is related, but here it is nevertheless:
"Unexpected query execution failure, error code 282. Additional error information from SQL Server is included below. "The 'proc_GetTpWebMetaDataAndListMetaData' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead." Query text (if available): "{?=call proc_GetTpWebMetaDataAndListMetaData(?,'1F57DB6C-AF94-4557-866D-4214D9EC8313',?,NULL,1,?,?,6187)}" "
Any ideas what went wrong or how to fix this? Does this have anything to do with .Net service packs that we installed about the same time as SP1 implementation?
We're currently having a great deal of difficulty getting our MOSS/SSRS integration configured. In short, we're getting "A connection to the computer cannot be established." message in the Grant Database Access page of the Reporting Services Integration settings.
A few more points:
We have two servers:
Server A: Win2K3 EE SP2, MOSS 2007, SSRS Integration Components
Server B: Win2K3 EE SP2, SQL Server 2005 SP2, MOSS database, SSRS, WSS 3.0, SSRS Integration Components A user in IE on Server A can successfully browse to the ReportServer virtual directory on Server B.
Another "test" MOSS server has been configured separately and successfully against Server B, so it seems like there's something amiss with Server A. The report server configuation tool shows all green. There are no entries in the App or System log that appear related to this issue. We've looked at KB's 871179 and 896861; no luck there.
We've tried both Windows Authentication and Trusted Connection with a number of different accounts, including a domain admin. No luck.
The error is really irritating, considering it gives no additional information, logging, or context.
I wonder if anyone can help me save the few remaining hairs on my head? I am trying to deploy reports created in SQL Server Business Intelligence Development Studio to SharePoint running SQL Server 2005 Reporting Services in SharePoint integrated mode. Whenever I try to deploy a report, the Reporting Services Login window pops up no matter which user/password I provide it won't accept any. I have the Reporting Services database set up to use Windows credentials and my Domain adminstrator account so I presume that this is user that I should be providing when prompted when deploying.
We are reporting from a custom list in MOSS 2007 using SSRS. When we try to report on a set of data from the list we receive 1;# in front of the returned data in SQL. How do i get rid of this or stop it from showing?
I am trying to use a reportviewer control (processing mode = remote) to view a rdl that is hosted on a server running MOSS, the reporting services are run in "sharepoint integrated mode". When i try to set the path to the RDL on the control like i usually do for an ASP.NET ReportViewer control, i get the error message posted below. I cant find anything on google, Please HELP
I'm running MOSS 2007 Enterprise, SQL 2005 SP2, RS integrated with MOSS and have a number of reports deployed to a Reports Library in MOSS. 3 out of 10 times I run a report I get a error message stating that 'An internal error occured on the report server.' Just hitting Apply on the parameter panel will fix the problem and render the report as expected.
Previous entries to the forum about this error hints at an error that supposedly was fixed in SP2; since I'm running SP2 something else must be the problem.
Any insight to what might cause the problem ?
Regards,
Trond
Relevant content from the RS error log included below:
w3wp!library!1!4/26/2007-11:42:21:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., un-named assertion fired for component processing; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details.
Like many others, I am have trouble getting this to work, and none of the solutions I have found on the inter-tubes seems to work for me:
"An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> The request failed with HTTP status 401: Unauthorized."
The Setup:
MOSS/SSRS (Integration Mode) running on a server farm on a single server: myserver.mydomain.org
Service Account for all Services: mydomainmyaccount (trusted for delegation, member of IIS_WPG) myserver trusted for delegation SSAS running under Local System on ssas.mydomain.org.
SETSPN -L mydomainmyaccount results:
HTTP/myserver.mydomain.org
HTTP/myserver
MOSS Authentication Settings
Authentication Type = Windows Default Authentication Provider = Negotiate (Kerberos) Anonymous access not enabled
IIS Settings
SSRS on Default Web Site: Port 8080
Application Pool Identity mydomainmyaccount
NTAuthenticationProviders="Negotiate,NTLM"
Security: Windows Authentication
MOSS on Sharepoint-80 Site: Port 80
Application Pool Identity mydomainmyaccount NTAuthenticationProviders="Negotiate,NTLM" Security: Basic Authentication except _vti_bin/ReportServer is Windows Authentication The idea is to use kerberos to pass credentials from SSRS reports running on myserver.mydomain.org to SSAS on ssas.mydomain.org.
hello when i try to view reports in reports manage i get the following error
The type Microsoft.SharePoint.Portal.Analytics.UI.ReportViewerMessages, Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c does not implement IReportViewerMessages or could not be found Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Reporting.WebForms.InvalidConfigFileTypeException: The type Microsoft.SharePoint.Portal.Analytics.UI.ReportViewerMessages, Microsoft.SharePoint.Portal, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c does not implement IReportViewerMessages or could not be found
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. Stack Trace:
I'm using Reporting Services Integration Mode and I have a page that has a number of report viewer webparts on it to display reports. Is there a way that I can add another webpart to pass parameters to all the reports at once instead of individually? I am trying to build a dashboard and this is one of the requirements. I see on the Report Viewer web part, that there is an option in Connections to 'Get report parameters from' , but it is greyed out. Any ideas on how to do this?
I am experiencing a problem integrating Reporting Services in MOSS 2007.
I tell you:
When i am in Reporting Services -> Aplications Administration, i click to set the default server settings and this error appears (it's in spanish, i try to translate below)
Error inesperado durante la conexión al servidor de informes. Compruebe que el servidor de informes está disponible y configurado para el modo integrado de SharePoint. --> El servidor no puede procesar la solicitud. ---> El cliente encontró el tipo de contenido de respuesta 'text/html; charset=utf-8', pero se esperaba 'text/xml'. Error de la solicitud con el mensaje de error:
Unexpected error while conecting to the report server. Check that the server is online and configured for the integrated Sharepoint mode. --> Server can precess the request ---> The client found the content response type 'text/html; charset=utf-8', but expected 'text/xml'.
I have watched into the report server, and it appears as integrated in Sharepoint.
If someone knows how to fix this, it would be very helpful.
I am having multiple URL in multiple zones for my site.I am not able to view SSRS reports on Internet which is in Internet zone where as i can view the same reports on Intranet site having URL in default zone. I m getting the following Error while accessing reports over internet:
" Unable to connect to the remote server.No connection to be made because target machine actively refused."
It would be great help if any one can solve this problem.
I have a masterpage that has no doctype, because I want to have a table with some fixed height TDs and some variable height TDs (this kind of table only seems to be possible in quirks mode, with no doctype). My problem is the SSRS web part, it has the web part title, but the actual report is not there! as soon as i put in the doctype, it renders normally.
Is there any way to have a reporting services web part render a report without a doctype?
does anyone know, when will the functionality of linked reports, my reports, data-driven subscriptions in MOSS integrated mode be enabled? Now it is according to Microsoft not supported. Will this be supported in the future ?Thanks.
we have Reporting services and Office Sharepoint on the same server, but the reporting services website is on default website and won't start because MOSS is already using the port. can i just change SSRS website port ?
I have configured Reporting services to use MOSS integrated mode. I have two servers, one for MOSS and the other for SQL database and reporting server.
Since I am using NTLM for IIS authentication, I can only use "Trusted Account" for Reporting Service Integration.
Then I created a report in SQL Server BI development studio and deployed to a MOSS document library. The deployment was successful. However, when I tried to open the report, I got the following error message:
An error has occurred during report processing. This data source is configured to use Windows integrated security. Windows integrated security is either disabled for this report server or your report server is using Trusted Account mode.
I have tried to switch to "Windows Authentication" for Reporting Service Integration, but this will give error for "Set Server Defaults" screen. Also the deployment from BI studio to MOSS will fail with authentication error. So I think I have to stay with "Trusted Account" option there.
What should I do to make the report accessible while using "Trusted Account"? Is there any configuration which has to be done for this purpose? Any input is appreciated.
Many a times see the below error in SQL Error log.
Login failed for user 'NT AUTHORITYANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: ]
Is this something to do here?
Note: If I run the below statement I know that the SQL Error log entry will go off, but wanted to know the real significance of this error?
CREATE LOGIN [NT AUTHORITYANONYMOUS LOGON] FROM WINDOWS
I am administering several SQL Servers running SQL Server 2005 SP2 Build 3042. I have a common maintenance plan that runs on each of the servers. The maintenance plan runs fine on all the servers except for one. On the one server the Database Integrity check fails with the following error:
Check Database integrity on Local server connection Databases: <list of databases> Include indexes Task start: 2008-02-21T00:05:42. Task end: 2008-02-21T00:05:46. Failed0) Alter failed for Server €˜XYZ€™
I created a test maintenance plan to just do the integrity check and selected one database only and this also failed with the same error message. I ran this test maintenance plan and configured it for each of the databases in question and it failed each time. If I run the DBCC manually against the databases they all report fine.
I read some of the post that talked about the €œAllow Updates€? being set incorrectly but that does not apply to my problem since my configured and run values are set to 0.
I have just installed RS and SP2 on a server running a MOSS 2007 (with SSL using an internal certificate) and configured RS to work on Sharepoint Integrated Mode. Then I went to Sharepoint to configure RS options, but when I tried to set up the Set Servers Defaults I receive the following error:
An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> Server was unable to process request. ---> The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> The remote certificate is invalid according to the validation procedure.
Also, when I try to deploy a report from SQL BI Development Studio to Sharepoint, I receive the error:
A connection could not be made to the report server https://myserver.mycompany.com.br/Reports/Site. (Microsoft Report Designer)
Server was unable to process request. ---> The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> The remote certificate is invalid according to the validation procedure. (System.Web.Services)
I have a report where I use Globals!ReportName in the header of the report for the report title. In Development and on SSRS stand alone the value for Globals!ReportName is in mixed case and the file extension is omitted. When the report is published to a MOSS server integrated with SSRS the value for Globals!ReportName is all in lower case and the file extension is included.
Is there any reason for this change in behavior and is there a way I can put back the mixed case and omit the file extension?
I use the "jump to url" in a report that links out to a page on our company intranet. Our internal users have to use http and an external user needs to be routed to the site w/ https. How can I account for this in a report?
I want to add two link(navigation) buttons in SINGLE CELL ... if i click on 1st it should navigate to xyz page and if i click on second then it should navigate to abc page...can u pls help me...
Hi, I am trying to link to a page outside of reporting services from a report. I am using SQL Server 2005 Reporting Services [Standard Edition]. The hyperlink works if it is a straight URL, however, nothing happens if I modify it to use Javascript so I can open the link in a new window. I have found many posts on the web from others indicating it should be really easy, but I can not get the link to recognize ANY Javascript (also tried a basic alert with no luck).
The Javascript I am using is well formatted. I can place it into a test page and it runs fine. I can also RC and View Source on my report, grab the entire link, put it in a test page and it works fine. It just doesn't work from the report - ?
