Report Builder 2016 freezes, SQL Server 2016 RC 3.3 and VS 2015 installed - report

Using Report Builder 2016 after creating the Data source the program freezes.
On my computer I have installed SQL Server 2016 RC 3.3 and VS Community 2015 w/ SSDT
Tried to create a blank report adding in the Data source and query, when trying to preview the report I get an error.
The definition of this report is not valid or supported by this version of Reporting Services. The report definition may have been created with a later version of Reporting Services, or contain content that is not well-formed or not valid based on Reporting Services schemas. Details: The report definition has an invalid target namespace 'http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition' which cannot be upgraded.

Related

Does IBM Database Add-Ins for Visual Studio support VS2019?

After scouting numerous articles and stack overflow for hours it seems that the IBM Database Add-Ins are not supported for Visual Studio 2019. Do correct me if I'm wrong.
Reasons for installing the Add Ins was to create entity classes in asp.net using web forms.
IBM Database Version : DB2 LUW 10.5
Reasons for the conclusions:
Installed the same fix packs for the IBM Data Server Driver Package as well as IBM Database Add-Ins for Visual Studio (Fix Pack 11) https://www.ibm.com/support/pages/node/3501195
Log Error Message : MSI (c) (98:58) [17:45:41:129]: Windows Installer installed the product. Product Name: IBM Database Add-Ins for Visual Studio, Product Version: 10.5.1100.2866, Product Language: 1041, Manufacturer: Company Name, Installation Success or Error Status: 1603
If the add in does not support Visual Studio 2019 , what would be the best replacement for Entity Framework 6.0 in order to use with IBM Db2?
If the add in does support Visual Studio 2019 is there a workaround to the following problem?
To get paid support (from IBM) for Visual-Studio 2019 in Db2, you need to have the visual studio add in that comes with Db2 v11.5.
For Db2 V10.5, it supports up to Visual Studio 2013.
It does not mean it will not work with older Db2 versions, but when you have issues (which is very likely), you won't get much help from IBM unless you have the right versions. You might be able to devise workarounds in some cases, but why bother?
If you are paying for a licence for Db2, pay for the current version and get the relevant paid support included. If you are not paying (for example, you are using a community edition) then get the latest version anyway. There seems no genuine reason for using the (out of support) Db2 v10.5 build if you are trying to use it with Microsoft software that was developed long after Db2 v10.5 was created.
Here is the link to the page that shows Db2 v11.5 supports Visual Studio 2019.
https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.swg.vs.addins.doc/html/ibmdevtsk-MigratingDB2Projects.htm

BizTalk 2013 R2 connect to Sybase Database through ODBC (Two connect & CDATA)

I have a requirement in BizTalk to connect to sybase database.
we are using BizTalk 2013 R2. I tried all ways to connect but not successful.
ODBC(Twoconnect)
Its showing up in admin console and when using add generated items in visual studio but the mysql option is not showing up in visual studio.I did install the older 5.3 my sql connector versions as the new 8 series throws an error when installing.
https://downloads.mysql.com/archives/c-odbc/
https://social.technet.microsoft.com/wiki/contents/articles/12824.biztalk-server-list-of-custom-adapters.aspx#hhh
In the technet link the ODBC is supported till BizTalk 2013.
CDATA
I have also tried to connect using CDATA
https://www.cdata.com/drivers/sybase/biztalk/
but it looks like the connection string is invalid when i try.
I am trying to provide servername,DB name,UserID,password and port number.It says specified connecting string in Invalid.
Not sure how to proceed further.

An attempt has been made to use a data extension that is either not registered for this report server or is not supported in this edition

I am trying to implement Custom Data Extension for the SSRS reports to get data from an assembly code as DataSet and display them.
I am able to fetch data and create DataSet in RDL report but on preview it is displayin g the below error:-
It seems like some mismatched version used.
Let you know my configurations as follows:-
Visual Studio 2013 with Data Tools 2014
SQL Server 2014 with MSDTBI tools and BI Services
Tried a lot but not getting any clue which all versions shall i use for VS and reporting services combination?
Any help would be of great help.
Regards,
Smruti Ranjan
I had a similar error to this. My issue was that I was using the wrong version of the Microsoft.ReportingServices.Interfaces dependency in my data processing extension. I was retrieving it via NuGet rather than using the version that was included with my BI install located in C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\PrivateAssemblies\Microsoft.ReportingServices.Interfaces.dll

Microsoft Dynamics AX 2012 Installation notes

Needs help with Microsoft Dynamics Ax 2012, installation and configuration.
Any info will be helpful, totally new to this technology.
My Personal notes:
You need to download the Dynamics ax on a Windows server 2008 r2 or windows server 2012.
While checking requisites, if you have an error with a configure check box enabled, use this check box to let the system automatically solve the issue for you.
When installing SQL server, note to enable the following features:
-Data Base engine services
-Full text search
-Analysis services
-Reporting services
-Business Intelligence
-Management tools basic
-Management tools Complete
-SQL client connectivity SDK
-Microsoft Sync features
Installing Core System:
A core Microsoft Dynamics AX system consists of
-an instance of an Application Object Server (AOS),
-an application file server,
-a database,
-and at least one client.
These components can be installed on computers arranged in a variety of topologies, but without all elements your system will not run.
For more info http://msdn.microsoft.com/en-us/library/aa548645(v=ax.10).aspx
In order to install Dynamics ax 2012 you need to have:
Database: DB server can be on a dedicated box or on the same machine. For production purposes recommended to have a dedicated machine.
I installed Microsoft SQL server 2008 r2 as the database engine.
Prerequisites check:
When checking the prerequisites, the SQL Full text search service is required.
If not installed on your SQL server, you have to add this feature to the existing SQL instance, to do so, please follow the steps in the link below:
http://www.techrepublic.com/blog/data-center/adding-sql-full-text-search-to-an-existing-sql-server/
Install the Microsoft Dynamics AX databases [AX 2012]:
http://technet.microsoft.com/en-us/library/ee355075.aspx
Server Components
-Application Object Server (AOS)
-Web server components
-Enterprise Portal (EP)
-Enterprise Search
-Helper Server
You need to have the server components; you can have one AOS or multiple AOSs, which will speed up the operation, and allows you to have more clustered environment.
EP gives you similar functionality to the client application over the web
Enterprise Search gives you the capability to find different info in your environment using a client utility or enterprise portal
Help server to get the latest info from Microsoft
Prerequisites check:
Download: Microsoft Search Server 2010 Express
http://www.microsoft.com/en-us/download/details.aspx?id=18914
http://msdn.microsoft.com/en-us/library/aa497037(v=ax.10).aspx
Business intelligence components
-Reporting Services extensions
-Analysis Services configuration
Reporting Services extensions: to create reports using visual studio or report builder, modify the existing reports, package them and upload to Dynamics ax
Analysis Services configuration: to use AOL app and AOL TP, Dynamics ax automatically creates OAL app cubes to analyze the business data.
Client components
-Client
-Office add-ins
-Remote desktop services integration
Client components very important to Dynamics ax users to be able to access Dynamics ax features.
You can add to the client app the office add-ins such as excel. Fully integrated with Dynamics ax 2012
you can also add remote connection to the client app.
Developer tools
-Debugger
-Visual studio tools: Note, You need VS2010 (Only 2010 will work) with Dynamics 2012
-Trace Parser
Integration components
-Web services on IIS: Based on WCF
-NET Business Connector: Gate way between Dynamics ax and Visual studio or any other 3ed party languages
-Synchronization proxy for Microsoft Project Server
-Synchronization service for Microsoft Project Server : these 2 components necessary to update info project server 2010 and dynamics as
Management utilities: uses windows power shell
 
Microsoft Dynamics ax 2012
Flowchart: Installation processes
http://msdn.microsoft.com/en-us/library/aa496434(v=ax.10).aspx
Hardware and software requirements
http://msdn.microsoft.com/en-us/library/aa548679(v=ax.10).aspx
Installing a core system – Very important link
http://msdn.microsoft.com/en-us/library/aa548645(v=ax.10).aspx

microsoft.office.interop.word dll (2007/2010)issues/ c#.net

issue: populating values for word document is not happening.object reference error in production server.
development server( working fine)
i am trying to populate the values for the word document using c#.am using microsoft.office.interop.word dll (version 12.0 related to word 2007) as a reference in my project. in my development server office 2007 is installed. am able to populate the values and save the document properly without any error.
Production Environment
getting object reference error. the one difference i see in this server is microsoft word 2010 is installed. i tried my level best but no luck.
*is this because word 2010 is installed in the production server?
*when i hosted the application in the other production server where word 2007 is installed.the application is working fine.
That could be the issue, it looks like Office 2010 uses Version 14 of the dlls:
http://www.microsoft.com/en-us/download/details.aspx?id=3508
Maybe try to use the 14 version in your dev server and see if that works, if so should be ok with production as well. otherwise see if the 2007 dll was copied into you bin, if not try to drop the 2007 version (v 12) into you application's bin and see if that works, could be the production application can't locate the dll in your bin and is then looking in the GAC, GAC would have 2010 version installed. If it's in your bin it might use that one first.

Resources