I am using the Web Intelligence Rich Client 4.2 SP3 Patch 3, I created a report and save it on WEBI. After I open the report in WEBI, when I click Refresh, it gives me the following error:
The following database error occurred: [DataDirect][ODBC lib] System information file not found. Please check the ODBCINI environment variable.. For information about this error, please refer to SAP Knowledge Base Article 2054721 on the SAP Support Portal. (IES 10901) (Error: INF )
What is the problem and how do I fix it? Thanks a lot!
I believe the WebI Rich Client needs both 32-bit and 64-bit ODBC data sources with the same name on the machine on which it is running. Then you will need a 64-bit ODBC data source with the same name on the server in order to be able to run the WebI report via the BI Launchpad.
This link discusses how to get to the 32-bit and 64-bit ODBC Administrator Tools.
Related
I've got this error when I tried to deploy SSRS report in Visual Studio.
(DAX 2012 kernel 6.0.1108.6510 app 6.0.1108.670 solution 6.1.1108.670)
Error 1 A call to the Microsoft Dynamics AX SRSFrameworkService service failed. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.43.6.57:8201. C:\Program Files (x86)\MSBuild\Microsoft\DynamicsTools\Microsoft.Dynamics.Framework.Design.Reporting.Modeling.targets 466
10.43.6.57:8201 is old address new should be 10.43.6.91:8201
Where I can change it?
In AX form SSRSServerFarm address is new:(NLDDAXDBS02TR, http://NLDDAXDBS02TR/Reports, 01#NLDDAXDBS02TR)
I run Visual Studio like this "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /AxConfig "c:\Users\Username\Desktop\DEV.axc" with correct config file
in axc file I don't have 10.43.6.57 or old dns NLDDAXDBS01T
I scanned and replaced values in registry on client and server machine, checked all files on client and server machine, checked all values in database.
Also restarted AOSes, SSRS service, and client RDP session.
Microsoft Dynamics AX 2012 Configuration and perform a Refresh Configuration didn't help
Full CIL Compilation, Deactivate BIServices, Activate BIServices also didn't help
Running Visual Studio as Admin - same result
nslookup says: NLDDAXDBS01T - 10.43.6.57 NLDDAXDBS02TR - 10.43.6.91
System Administration > Setup > Business intelligence > Report Servers is correct because i tried to deploy from another rdp server and it works fine
Are you certain the default report server is setup correctly in Ax?
Found under:
System Administration > Setup > Business intelligence > Report
Servers
Check your business connector configuration to make sure it's connecting to the right environment, see https://technet.microsoft.com/en-us/library/aa569654.aspx
I think Visual Studio deploys to AX based on that business connector AXC, so if that's pointed to an incorrect environment that has the "old" SSRS setup, it would explain your issue.
I got this problem one time due to multiple AOS and SSRS instance, or you might stop AOS service while user still using.
First, you need to make sure Report servers configuration point correctly to SSRS instance.
Then, stop all AOS service, go to reporting service login with correct instance and check everything again.
Then, perform full compilation using AXbuild.exe , Full CIL.
Start AOS service and check.
Let us know result.
SSIS SP Connection using OData connector.
I was able to connect to Sharepoint site fine and was able to see the data thru preview and all.. but when i execute the task i get below error.
[OData Source [2]] Error: The OData Source was unable to process the data. Object reference not set to an instance of an object.
Note: Visual Studio 2012 with BI template not sure how different is that from SSDT 2012. When i go try to open SSDT 2012, i get VS 2010 shell, that's why i use VS 2012 with Business Intelligence template thinking that maybe same as SSDT 2012. If this has to do something with error message i get above.
Task:
OData Source with SP connection information
OLE DB Destination.
Let me know your thoughts!!
I would try setting the Project Properties / Debugging / Run64BitRuntime to False.
This will run your debug executions (e.g. Execute Task, Execute Package using Visual Studio) using the 32-bit version of the OData connector. Visual Studio (which you have used to design the task and preview the data) is a 32-bit app, so it will be using the 32-bit versions of the OData connector.
The same challenge applies to almost every connector or driver that has to be separately installed for SSIS. Typically they come in 32-bit and 64-bit flavors, with independent setup, configuration and sometimes bugs.
While I recognize that 64-bit components will generally deliver higher throughput, I have resigned to always install and use the 32-bit connectors and drivers. I find this minimizes wasted time and frustration trying to debug and resolve these issues on multiple developer machines and servers.
I'm unable to generate a report from the web based interface (Report Manager). The same report in my Visual Studio project works perfectly.
The error which appear when trying to generate the report from the web is
"Cannot create a connection to data source"
The log file error is the fallowing
Cannot get edition information from catalog server.
The report data is retreived from an SQL Azure database.
How come the report can work inside my Visual Studio project but no more once deployed?
I've tried both SQL Server 2012 and SQL Server 2008 on fresh machines and both gives the same result.
Thanks,
After a half day of troubleshooting this issue, I discovered it was because the edition of SSRS I am using does not support Azure SQL Databases as a data source.
I am using 2008 Express Advanced Edition. It appears Standard or above is required for this.
See this article for more information:
http://www.sqlservercentral.com/blogs/sqltact/2016/09/25/sql-ssrs-express-edition-cannot-connect-to-azure-sql-databases/
We've got a a series of SQL Server Integration Services packages that copy data from a few MS Access databases into a SQL Server 2008 database. There is one parent package that calls the various sub-packages, and that parent package is initiated by a user that runs a .bat file that executes the package like so:
dtexec /f "\\networkshare\package.dtsx" /CHECKPOINTING OFF /REPORTING EWCDI
This has worked fine for several years. Our IT department has begun upgrading our 32-bit Windows XP workstations to 64-bit Windows 7 and since they've upgraded the workstations of these users, the package has been failing, giving the error
-1071607037,0x,SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR. The requested OLE DB provider MICROSOFT.JET.OLEDB.4.0 is not registered -- perhaps no 64-bit provider is available. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
My workstation has not yet been upgraded from Windows XP and I'm still able to run the packages but my ability to postpone the upgrade is running out and I need to figure out a solution as soon as possible. I've found many articles and posts related to this in my efforts to resolve the issue. Among the things I've tried are:
After ensuring that the users had the Client Tools and Business Intelligence Development Studio installed and that the path is valid, changing the contents of the .bat file to specifically reference “C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\dtexec.exe” in the hope that the 32-bit JET provider would be used
Researched the Run64BitRuntime setting but this appears to only have an effect while debugging and won't help me
Researched adding the /X86 flag to the command line but according to the MSDN article on dtexec, this only has an effect if the SQL Server Agent is running the task
The last thing I've tried was to install the Microsoft Access Database Engine 2010 Redistributable and change the connection string from "Provider=Microsoft.Jet.OLEDB.4.0;" to "Provider=Microsoft.ACE.OLEDB.12.0;". I can't seem to get off the ground with this one. If I try to create a new connection in BIDS and set the provider to "Microsoft Office 12.0 Access Database Engine OLE DB Provider" and test the connection, I get the error "Test connection failed because of an error in initializing provider. Unspecified error".
I'm just about at a loss for what else I can try and looking for any help at all, even if it's trying the things I've already tried, maybe I've configured something wrong while trying them originally, not sure.
Any help would be immensely appreciated!
In SQL Agent job or by just executing the package by itself there is a tab called "Execution options", you can select "Use 32 bit runtime" option
By default, SQL Server puts the 64-bit version of DTEXEC in the path. The 32-bit version should be located somewhere like C:\Program Files(x86)\Microsoft SQL Server\100\DTS\Binn and would need to be called directly. I had the same issue with the ACE drivers and Excel files.
See this for more information.
I was able to run it successfully by changing debugging setting in project property page. Property to change is Run64BitRuntime -> set this to false.
I'm trying to add a third party reporting chart control in to my project. I'm using visual studio 2005 and i've installed SQL Server 2005 along with the Reporting Services. When i try to add the third party dll to the tool box, i get the error message
'Could not load file or assembly 'Microsoft.ReportingServices.ProcessingCore, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.'
I checked out the assembly and i was not able to find any dlls starting with Microsoft.ReportingServices.
Any ideas?
Thank you
NLV
I see this is a bit late, but I wanted to share something I learned for future possibilities of this error for others. I experienced a similar issue after some software was installed that appears to have updated SQL for VS and/or SQL assemblies in general. It appears this caused a mismatch of what assembly SSRS was trying to use vs what it could find.
I found the following workaround:
You can go to the appropriate reportserver bin and add/replace the Microsoft.ReportingServices.ProcessingCore.dll with the appropriate version one. The location for this bin is
Drive(ex. C):\Program Files\Microsoft SQL Server\MSRS__.MSSQLSERVER(or
whatever report server name is)\Reporting Services\ReportServer\bin.
I just copied the .dll here and then went to Reporting Services Configuration and stopped and re-started the report server.
If there is enough disk space on the DB server but this message still appears, restart the SQL Server Reporting Services (MSSQLSERVER) service