I have an SSIS package that has a single OData source (sharepoint site source). The package runs fine from Visual Studio. Once deployed to a SQL instance I try to run the package via an Agent Job (uses the Agent service account to execute), and I get the following:
SharePoint List to Stage:Error: System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.SqlServer.IntegrationServices.DataFeedClient.Http.HttpWebRequestWrapper.GetResponse()
at Microsoft.SqlServer.IntegrationServices.DataFeedClient.Http.WebRequestHelper.GetResponseWithThreadSafeRetry(IWebRequest& request,
Func`1 createWebRequest, Int32 retryCount, Int32 retrySleepInMilliseconds, Boolean isOAuth, Func`2 refreshRequestWithNewAccessToken, Func`2
getStatusCode)
at
Microsoft.SqlServer.IntegrationServices.DataFeedClient.Http.WebRequestHelper.GetResponseWithThreadSafeRetryAndImpersonation(IWebRequest&
request, DataFeedConnection connection, Func`1 createWebRequest)
at Microsoft.SqlServer.IntegrationServices.DataFeedClient.DataFeedCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.SqlServer.IntegrationServices.OData.ODataSource.GetSchemaTable()
at Microsoft.SqlServer.IntegrationServices.OData.ODataSource.PreExecute()
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPreExecute(IDTSManagedComponentWrapper100 wrapper)
The service account running the package has Full Control permissions on the SharePoint list in question. I have several other packages on the same server that use OData feed from the same SharePoint farm with the same service account without issue.
Turned out that the error was on the SharePoint server... the lookup column threshold in Central Admin was set to 8 (the default), but the number of lookup columns in the list exceeds that. Since I'm a farm admin, I bypass the restriction. I just wish that the error that goes through to SSIS was a little more explanatory than just (500).
Related
I have a problem connecting the SSRS to Sharepoint Online List. I can connect it through Microsoft Excel (asking for credentials, auth) and can read from the list but when I use the same URL to SSRS it doesnt work and message appears saying that "E_ACCESSDENIED".
I search over the internet a lots of threads but without success. I tried all of the auth methods but without success. My thoughts are that my connection string in the SSRS should be different. I really done know and need your help! Thanks!
Here is the error:
===================================
Server was unable to process request. ---> Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
(Microsoft Visual Studio)
------------------------------
Program Location:
at Microsoft.ReportingServices.DataExtensions.SharePointList.SPRemoteConnection.ExecuteServiceRequest(ServiceRequest request)
at Microsoft.ReportingServices.DataExtensions.SharePointList.SPRemoteConnection.GetLists()
at Microsoft.ReportingServices.QueryDesigners.SharePoint.SharePointTables.Refresh()
at Microsoft.ReportingServices.QueryDesigners.SharePoint.QueryDesigner.Presenter.ValidateConnection()
at Microsoft.ReportingServices.QueryDesigners.SharePoint.SharePointQueryDesigner.InitializeQueryDesigner()
at Microsoft.ReportingServices.QueryDesigners.InternalQueryDesignerWrapper.InitializeDesigner()
at Microsoft.ReportingServices.QueryDesigners.InternalQueryDesignerWithGenericModeWrapper.Initialize()
===================================
Server was unable to process request. ---> Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (System.Web.Services)
------------------------------
Program Location:
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.ReportingServices.DataExtensions.SharePointList.SPListService.GetListCollection()
at Microsoft.ReportingServices.DataExtensions.SharePointList.SPRemoteConnection.<>c__DisplayClass5_0.<GetLists>b__0(SPListService listSvc)
at Microsoft.ReportingServices.DataExtensions.SharePointList.SPRemoteConnection.ExecuteServiceRequest(ServiceRequest request)
Best regards.
I believe that option is only for on-premises versions, not for SharePoint Online. I do not believe you can directly connect SharePoint Online to SSRS.
We set up an SSIS package that pulls list data from SharePoint online into our on-premises database, and then query that within the SSRS report. It works pretty well for our needs.
I install SQL Server Connector for Power Query for SQL server 2017. Create SSDT SSIS package with power query connector. It works perfect in SSDT! But when I deploy project to SSIS catalog, I get an error:
Credentials are required to connect web source.
Package:Error: The data protection operation was unsuccessful. This may have been caused by not having the user profile loaded for the current thread's user context, which may be the case when the thread is impersonating.
Moreover, when I import this package from SSIS catalog to new project, power query connection manager go away from project with error:
The connection "{EFC6889A-D312-4A9E-B251-877C7A67B8DF}" is not found.
This error is thrown by Connections collection when the specific connection element is not found.
Solved!!! In SSDT I used my own login. But in SSIS catalog used SSIS proxy account that don't have access to web.
After granting access to web to SSIS proxy account it works!
If you met same error just try to run SSDT under proxy account and check web access in data source manager :)
Thank you in advance for your help on this issue.
Here is the situation:
I have a SSIS package that essentially take data from a excel file ( using a Excel Connection) and upload it to a SQL table through a OLE DB Connection. This package runs completely fine in Visual Studio but I keep having this error once it is deployed on SSMS:
Failed to configure a connection property that has the following path: \Package.Connections[Excel Connection Manager].Properties[ConnectByProxy]. Element "ConnectByProxy" does not exist in collection "Properties".
; at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ConnectionParametersManager.ConfigureProperty(String parameterName, Object parameterValue)
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ConnectionParametersManager.ConfigureProperties()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.ValidatePackageWithReference(Int64 validationId, Int64 infoId, Int64 projectId, String packageName, Int64 versionId, Nullable`1 referenceId, Project isserverProject, Boolean offlineMode)>
And I have the same error when it comes to the OLE DB ( SQL Server Native Client 11.0) connection.
Both Connections are at the project level and I deploy the hole project in SSMS. I also have the Microsoft.ACE.OLEDB.16.0 provider installed in SSMS.
To fix that error I have made some changes in the project configuration in SSMS like setting the ConnectByPoxy value to TRUE or adding my UserName but still failed. The package is pretty simple, has no parameters, no variables.
Also tried checking the 32 bit runtime..
Sometimes SSIS can throw strange errors when working with deployments to remote servers that you never encounter when executing the package locally. This implies there is likely something wrong with the compatibility of the server's version of SQL Server and your local copy (of SQL Server or Visual Studio). Perhaps verifying the deployed version of SQL Server your remote server uses and comparing it to your local copy would be worthwhile.
If they do match, next I would check the project's target SQL Server version by following the instructions at this site, and ensure it is correct. I would also confirm that the server has access to the directory in which the Excel files are being received, just to be safe.
This article specifically addresses the "ConnectByProxy" element issue you are encountering, and may prove helpful in resolving the issue or at least in giving more insight into possible issues.
Our cubes were working fine and were processed daily in SSMS until some Microsoft security updates were installed & the server was restarted. We receive the error message above when processing the cubes and dimensions. We already deleted the security updates but we still get the same error.
In the windows services -> SQL Server Analysis we have a service account with all the rights in SQL server (read, write, process, admin). We are working on SQL Server 2014.
We tried to:
restart the SQL Server Analysis
set up new accounts with read,process and admin rights on the SQL server and analysis server.
we tried to put in the "SQL Server Analysis" to put the Local account
create a new cube but Dimension can still not be processed.
change the provider from "SQL Server Native Client 11.0" to "Microsoft OLE DB Provider for SQL server" and we also checked the "allow inprocess" checkbox in SSMS in Server Objects -> Linked Servers -> Providers.
Nothing worked of the points above. I hope someone can help us.
Error message:
OLE DB error: OLE DB or ODBC error: Incorrect syntax near the keyword
'JOIN'.; 42000. Errors in the OLAP storage engine: An error occurred
while the dimension, with the ID of
'd4b8c9a6-7692-4d64-bb9c-f4ac7d7d62d1', Name of 'Customer' was being
processed. Errors in the OLAP storage engine: An error occurred while
the 'Type' attribute of the 'Customer' dimension from the 'TestCube'
database was being processed. Server: The current operation was
cancelled because another operation in the transaction failed.
Details:
Internal error: The operation terminated unsuccessfully. ... Module:
Microsoft.AnalysisServices
Microsoft.AnalysisServices.OperationException
at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection
impacts, Boolean expectEmptyResults, Boolean throwIfError)
at Microsoft.AnalysisServices.Server.Process(IMajorObject obj, ProcessType processType, Binding source, ErrorConfiguration
errorConfig, WriteBackTableCreation writebackOption,
XmlaWarningCollection warnings, ImpactDetailCollection impactResult,
Boolean analyzeImpactOnly)
at Microsoft.AnalysisServices.Server.SendProcess(IMajorObject obj, ProcessType processType, Binding source, ErrorConfiguration
errorConfig, WriteBackTableCreation writebackOption,
XmlaWarningCollection warnings, ImpactDetailCollection impactResult,
Boolean analyzeImpactOnly)
at Microsoft.AnalysisServices.ProcessableMajorObject.Process(ProcessType
processType, ErrorConfiguration errorConfiguration,
XmlaWarningCollection warnings)
at TimeXtender.DataManager.CubeEngine_2005.ProcessDimension(Dimension
dimension)
FYI:
We finally managed to fix the problem.
When running the SQL server repair it failed on SSAS with an error that indicates that the installation of SSAS was never successful so we think the files were corrupted.
Then we installed another instance of SSAS only to have 2 SSAS services. The new one was working so we deleted the old one and replaced it with a new SSAS installation. So no need reinstall the complete SQL Server.
We did backups just in case we would need them but all the cubes were automatically found by the new SSAS instance in that folder that we indicated in the installation process.
Everything was immediately working.
I'm getting this error when trying to view my data flow tab in Visual Studio. FWIW, this is a package that I've copied from a different server and am trying to get it to execute on the new server. I've changed the definition of the SQL Server related connection manager, but I think that this problem is related to the portion of the data flow which pertains to the ODBC data source, which is selecting data from a PostgreSQL database. A prior step, which truncates the SQL Server target tables executes without problem.
I have validated that the (32 bit) ODBC connection seems to work. It passes the connection test, anyway.
FWIW, I'm new to the SQLServer world. I've spent a bit of time building this package on a Virtual Server, but am trying to move it to a larger production server. Point being, I don't necessarily know all the details of the environment.
ps--All this is on SQL Server BI 2012 on Windows 2012 server (the newest version, whatever it's called).
UPDATE: Here is the full text (or more full, anyway) of the error:
OLE has sent a request and is waiting for a reply.
(Microsoft Visual Studio Debugger)
Program Location:
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode)
at Microsoft.DataTransformationServices.Project.DataTransformationsPackageDebugger.LaunchVsDebugger(IVsDebugger iVsDebugger, DataTransformationsProjectConfigurationOptions options)