Cannot run report on the report server with ssis as a datasource
Helo All,
I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:
An error has occurred during report processing.
- Cannot create a connection to data source 'DataSource1'.
- is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)
I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.
My connection string looks something like this:
="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"
Could any please help me out of this?
Note: SSIS is parameterized here!
Regards,
Raju
Does it work if you remove the parameter?
Also, enable logging in the package so you can tell if SSRS is actually executing it.
Hi,
I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.
The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.
Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.
Thanks for your help...
I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .
Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.
