I use reporting services integrated with SharePoint. All reports work fine. The thing is that as soon as I installed the Microsoft .NET Framework 2.0 Service Pack 2 (NetFx20SP2_x64.exe), I get an error page when accessing the reports saying the following:
An unexpected error occured while connecting to the report server. Verify that the report server is configured for SharePoint integrated mode. --> The request failed with HTTP status 401: Unauthorized.
Any ideas why installing the sp2 for .Net 2.0 is causing this error?
Edit:
I also get the following line in MOSS logs
AppDomainUnloadListener.RegisterSelf() entered lock(this=15368010).
please see the below links:
http://msdn.microsoft.com/en-us/library/ee384252%28SQL.100%29.aspx
http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/7e77fe54-74ee-437c-a985-03dd04e9f35c/
Related
I tried to integrate SSRS reportviewer in .net web application(v4.8). Solution is working in my local but after deployed in IIS server the controller not loading properly.
It seems like some service not installed properly in the server. i couldn't figure out what is the issue and spend more then 2 days to address this but no improvement.
Please help me to resolve this issue. Error and configuration details mentioned below.
IIS version: 8.5
OS: Windows server 2012 R2
Asp.net : 4.8
Error in browser console: "Uncaught ReferenceError: Sys is not defined"
enter image description here
I am having problem when running SSIS which extracts data from SharePoint list. SSIS Package was running fine till 2 weeks back and suddenly the package is failing with this error:
[OData Source [56]] Error: Cannot acquire a managed connection from the run-time connection manager.
[SSIS.Pipeline] Error: OData Source failed validation and returned error code 0xC020801F.
[SSIS.Pipeline] Error: One or more component failed validation.
Error: There were errors during task validation
Tried:
Changing 64bit debug option in package properties to false
http:// instead of https://
I expect SSIS package to extract data from SharePoint list without any issues but facing the above error message recently which was working fine for more than a year.
Server detail: Windows server 2012 R2.
Application details: Visual studio 2010, .NET framework - 4.5
Update # 2019-02-17
We are not using windows authentication and SSIS Passage is getting failed even after running SSDT as administrator. We are able to preview the Sharepoint list data in ODATA Source, but package is getting failed with the mentioned error message when triggered
Update 2 - ODATA connection properties
In the ODATA connection manager try setting the following properties as shown in the image:
Update 1 - TLS issue
While searching i found a the following related article:
TLS Issue with SSIS package while accessing OData Source like Dynamics AX Online
They mentioned the following solution:
We can resolve this using the below steps:
Install Microsoft .NET 4.6 and above on your computer (https://technet.microsoft.com/en-us/library/security/2960358.aspx).
Enforce TLS 1.2 on your machine through registry settings. In an elevated command prompt run the following commands:
reg add HKLM\SOFTWARE\Microsoft.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:64
reg add HKLM\SOFTWARE\Microsoft.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:32
Also based on the following article:
TLS 1.2 and .NET Support: How to Avoid Connection Errors
.NET 4.6 and above. You don’t need to do any additional work to support TLS 1.2, it’s supported by default.
.NET 4.5 TLS 1.2 is supported, but it’s not a default protocol. You need to opt-in to use it. The following code will make TLS 1.2 default, make sure to execute it before making a connection to secured resource:
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
Similar issue linke
(The link i mentioned are also mentioned in this question, also there are many helpful comments, this question is very related but the difference is that they are not connecting to Sharepoint list, they are connecting to a public data source)
OData Source Component in SSIS Not Connecting
Original Answer
Trying to figure out the issue
Based on the information you provided, it looks like the issue is not caused by SSIS, it is related to the environment you are working in or maybe the credentials you are using to access the Sharepoint List.
In the ODATA Connection Manager, there are many Authentication option you can use:
Authentication
Select one of the following options:
Windows Authentication. For anonymous access, select this option.
Basic Authentication
Microsoft Dynamics AX Online for Dynamics AX Online
Microsoft Dynamics CRM Online for Dynamics CRM Online
Microsoft Online Services for Microsoft Online Services
If you select an option other than Windows Authentication, enter the username and password.
If you are using Windows Authentication, try to run the Visual Studio as Administrator and run the package again, if you are using other authentication type check that this account still have access.
If you are running the package usin SQL job, check also that the user has necessary permissions to read data from Sharepoint list.
Some helpful links
In addition, i will provide some helpful links on how to connect to a Sharepoint list using ODATA Source, it may give you some insights:
How to configure OData SSIS Connection for SharePoint Online
Reading SharePoint Lists with Integration Services 2017
Using the SSIS OData Source Connector With SharePoint Online Authentication
We got this error since proxy was enabled in the server. SSIS Package is not able to access Sharepoint List during execution when the proxy is enabled. This is working fine after changing the connection to "automatically detect settings" in the internet options.
This solution helped but the command still has an issue. The \ is missing from the command (between Microsoft and .NETFramework)
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319 /v SchUseStrongCrypto /t REG_DWORD /d 1 /reg:64
If you are using a proxy, setting it for the .NET Framework in machine.config can help.
Open Notepad as administrator and open the following file(s):
C:\Windows\Microsoft.NET\framework\v4.0.30319\config\machine.config
C:\Windows\Microsoft.NET\framework64\v4.0.30319\config\machine.config
Search for <system.net>
If <system.net> is not found, add the following text as the second line from the end above and substitute the proxy address as appropriate for the environment:
<system.net>
<defaultProxy>
<proxy autoDetect="false" bypassonlocal="true" proxyaddress="http://proxy_host:8080" />
</defaultProxy>
</system.net>
I am trying to deploy a report from Visual Studio to a Reporting Server which is not running on my local computer and I am getting this error:
Error: The given key was not present in the dictionary
I can deploy the report to my local Reporting Server but when I tried to deploy the same report to another Reporting Server then is when I am getting that error message.
I am running Visual Studio 2017
I have installed Microsoft SQL Server Data Tools version (15.1.61707.200)
The Reporting Server where I tried to deploy the report is running Microsoft SQL Server 2012 Reporting Server.
Target SQL Server 2012
Please any advice or suggestion to fix this problem.
Regards;
Sergio
For those who are having the same problem as me, I have found the solution:
https://social.msdn.microsoft.com/Forums/en-US/68f09a17-23b6-4e2f-8dd2-f532e02eb563/unable-to-deploy-ssrs-report?forum=sqlreportingservices
Please install the latest package for Microsoft Reporting Services Projects.
https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio#overview
I created some SQL Server Reporting Services reports using Microsoft Visual Studio. Previewing the reports is working fine. But when i deploy the application, i get the following errors: The permissions granted to user 'PERSOLGH\SOMAD' are insufficient for performing this operation.
But the SQL Server Management Studio Reporting Services works fine.
What could cause the error or am I missing something?
Any help would be much appreciated.
Best Regards,
Somad
I got the error while uploading a package to Worklight using Worklight Console site.
Object
'com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-'
is not managed by this context
I just saw this error message using Browser Developer Tools to investigate Request and Response Network activity.
PS: There isn´t any JPA class in my project and package.
My environment:
IBM MobileFirst 6.3 (Worklight)
IBM WebSphere Liberty 8.5.5
MySQL
Windows Server 2008 R2
Hybrid App with Android Environment
Full error message:
{"id":147,"type":"UPLOAD_APPLICATION","status":"PENDING","project":{"name":"project1"},"timeCreated":"2015-02-05T19:37:08.000Z","userName":"user1","appServerId":"Liberty","description":{"appVersionsDeployed":[{"applicationName":"App1","environment":"android","version":"1.0"},{"applicationName":"App1","environment":"common","version":"1.0"}],"appVersionsAlreadyDeployed":[],"filename":"App1-all.wlapp"},"errors":[{"date":"2015-02-05T19:37:08.655Z","phase":"VALIDATE","code":"FAILURE","exception":"ArgumentException","details":"Object \"com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-com.ibm.worklight.dataaccess.jpa.entity.ProjectEntity-2\" is not managed by this context."}],"warnings":[],"productVersion":"6.3.0.00-20141127-1357"}
The problem is the file size (.wlapp).
I got the error when the file is bigger than 7MB.