I have sharepoint 2013. I have one SQL instance in sharepoint integrated mode and another instance in SSRS native mode on my server.
I get the login failure error.
I am dealing with this failure that is explained in the following solutions. But non of them solved my problem:
I did this solution:
https://stackoverflow.com/a/1445068/779408
and this:
http://ybbest.wordpress.com/2011/08/04/how-to-fix-%E2%80%9Cnot-able-to-deploy-report-to-sharepoint-2010-in-integrated-mode%E2%80%9D/
then I tested this solution:
http://www.thorntontechnical.com/tech/sharepoint/sharepoint-2010-ssrs-integrated-mode-deploy-login-prompt#.U5vQj7EmFKb
and implemented the solution in this:
https://sharepoint.stackexchange.com/questions/16656/not-able-to-deploy-report-to-sharepoint-2010-in-integrated-mode
Now I have the following web application and its Document library
http://test.local:44444/sites/sc1/Reports
But I can not deploy my reports on it.
What should I do now??
This issue normally occurs due to incomplete installation. Ensure that SQL Server Reporting services Add-in for sharepoint is installed. If not, run SQL Server setup again to install the missing add-in. If SharePoint 2013 is missing service pack 1, it may cause errors during configuration.
I would suggest you make use of the release configuration manager. You can create releases such as
LOCAL
REPORT_TESTING
REPORT_STAGING
PRODUCTION
SOME_SHAREPOINT_DEPLOYMENT
Each release type contains it's own instance of configuration values. This would allow the release type to control the deployment. If you are not using SharePoint locally then you can set the LOCAL release configuration to the standard SSRS values on your local machine.
this issue happening when you deployment the SSRS reports on SharePoint mode and configure FBA on the SP server
To solve this issue you must extend the Web Application that include BI Center
I have been facing the same issue,
When creating a new service application in SharePoint using SQL Server Reporting Services Service Application, I forgot to check the Web Application to be Associated.
Solution:
After I checked the Web Application & updated the service application properties, its Working.
Hope it helps someone...
Related
I'm trying to understand what the "Deployed" tab is used for in TFS 2013 Team Web Access. There's another similar question here: What is the "deployed" tab for in TFS 2012 Web Access
Some of the information there seems to suggest that TFS Deployer is setting a build quality, but what is it? Another post indicates that it might be for Azure deployments.
Just trying to understand how it works.
When you use the built in Continious Build to Azure build template it will automatically set this for successfully deployments.
You may be able to set this through the API.
When attempting to use hashtags in SharePoint 2013 users see "the tagging service is currently unavailable". I've googled this issue and have tried or validated the following without success:
The application pool for Managed Metadata Service is running with the correct credentials
The Managed Metadata Web Service is running on all WFE's and app servers
In Central Admin the Managed Metadata web service is the default location for keywords
In general this (test) farm looks identical to my production farm. The only difference is that I've applied the new service pack 1 to this test farm, and now this service appears to have broken.
Any help would be greatly appreciated.
Generally after installing a service pack, you are required to run the SharePoint Products Configuration Wizard on each of the servers in the farm (http://technet.microsoft.com/en-us/library/ff806338(v=office.15).aspx). Also, sometimes a reboot may be required after running the configuration wizard. Have you done both/either of those things?
I enabled the Web Deploy feature for my Web Role and deployed it.
But how can I get hold of the .publishsettings file so I can create a Publishing Profile for it?
This 2 year old article states that it should have been created automatically, but I haven't got that in my profile manager.
Any ideas?
If you are using Visual Studio 2012 or greater, the server explorer to the left will have several Azure items.
Specifically the Windows Azure Compute is what we are looking for, right click on that and say 'add deployment environment'. You will then be prompted with a dialog that allows you to sign in and download publish settings file:
You can get publishsettings file from the following link: https://windows.azure.com/download/publishprofile.aspx
Well, the problem was really behind the keyboard.
So the publishing profile is actually provisioned correctly and automatically to the Web project as the documentation states.
The problem and confusion was that I have a secondary web application in my Solution that I also publish to the same Web Role (referenced as an additional Site in the ServiceDefinition.csdef file).
That Web Project does not get the Publishing Profile, and when I try to create a profile manually, it doesn't work since that (secondary) IIs instance is not configured for Web Deployment.
Oh well, back to the tedious Cloud Service deployment it is...
Good day all,
We recently migrated from TFS2008 to TFS2010. We migrated our TFS_name databases and our WSS databases. We followed the migration steps and our upgrade was successful, except for a single piece regarding the project sites.
Whenever I go into a team project portal, I receive the following error when trying to access the "Reports" site.
TF250016: No access rights have been granted for the following site: http://<tfsserver>/Sites/<project portal site>. You must grant access rights between the SharePoint Web application and Team Foundation Server. You must also associate this site with reports and dashboards for a specific project in Team Foundation Server. For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=147580).
I have gone through the TFS upgrade steps and made sure we followed every step and we are running of ideas. Can anyone point me in the right direction? We didn't notice this error as we are not using reports at this time, but it's something we would like to implement in the future.
Thank you
Edit
(to read in the comments)
You did a move from one server to another and upgrade your TFS Server.
It's most likely you didn't follow the "how to move a TFS from one hardware configuration to another" procedure, then you'r SQL Report Server is down or incorrectly configured (the SQL Connection strings in the Data Sources configuration are incorrect).
Follow the procedure I gave you for the SQS Server Resport Service part and you should be fine.
How can i package rdl reports inside SharePoint package files (wsp), And be able to change connection string later so i can deploy that package to different servers?
In addition to deploying the files, you need to register them with SSRS using ReportingService2006.CreateReport and ReportingService2006.CreateDataSource.
Once the Data Sources has been deployed to your Data Connections library and registered with Reporting Services, you can change it either manually or programmatically.
For details, see:
Automating Report Deployment with Reporting Services in SharePoint Integration Mode
Deploying Reports in Integrated Mode