Currently I am working on Migrating BT2006 R2 (VS2005) to BT2013 R2 (VS2013).
I tried below twp approaches.
Approach I:
First, Open the BT2006 R2 Project in (VS2010)[BT2010] [Intermediate]
then Upgrade BT2010 Project to BT2013 R2 (opening in VS2013 Project). It's work fine. there is no issue on that.
Approach II:
Directly open the BT2006R2 Project Solution file in VS2013 (without Intermediate version)
Getting the below error
Error migrating project user file. The element BIZTALK beneath element VisualStudioProject is unrecognized.
I tried to remove project user file and then migrate to BT2013 R2. but still same error occurred.
So it means, we can't we do direct migration from BT2006 R2 to BT2013 R2?
Do we always need to do the first approach above?
Put it this way, if the direct upgrade does not work, you have to use the intermediate step. That's it.
So, yes, you must follow Approach 1.
Related
I cannot get VS 2015 to create my EDMX file for an Oracle Connection.
I am using Visual Studio 2015 Update 3
I have installed the Oracle Developer Tools 12.1.0.2.4
I have installed Oracle Data Access and the following DLLs exist under \ client[user]\product\12.1.0\client\odp.net\bin
2.x\Oracle.DataAccess.dll version: 2.121.2.0 ODAC Release 4
4\Oracle.DataAccess.dll version: 4.121.2.0 ODAC Release 4
I am using the following assemblies
Oracle.ManagedDataAccess Version: 4.122.1.0
Oracle.ManagedDataAccess.EntityFramework Version: 6.122.1.0
* I believe both of these are version 12.2.1100 based on the folders in which they reside in the packages folder.
There are no connections defined in the Server Explorer
My steps are as follows:
Within the Solutions Explorer, Right click on project and select "Add" | "New Item..."
Select Data | ADO.NET Entity Data Model | Add
Select EF Designer from Database | Press Next
In the Entity Data Model Wizard:
Press New Connection... (I get an warning "Failed to find the default tnsnames.ora file." I ignore and press "OK"
With the Datasource as "Oracle Database (ODP.NET, Managed Driver)" I enter the credentials and specify the the other
connection parameters and press "Test Connection" which SUCCEEDS.
I press OK and am taken to the next page in the Entity Data Model Wizard
I include sensitive data in connection string and Press Next....
WIZARD SHUTS DOWN (crashes) - NO EDMX CREATED
Any assistance in helping me troubleshoot this would be greatly appreciated.
TIA - Xavier
Thanks to #Hong-vit pointing me in the right direction. I found the answer.
When you visit the download page for ODAC you're given a selection of version numbers.
In my case the top two were:
ODAC 12.2c Release 1 and Oracle Developer Tools for Visual Studio (12.2.0.1.0)
ODAC 12c Release 4 and Oracle Developer Tools for Visual Studio (12.1.0.2.4)
For me the top one wouldn't install. It would cut out during the installation process (thanks Oracle!) so I settled with the second one (12.1.0.2.4).
This meant that when I installed Oracle.ManagedDataAccess and Oracle.ManagedDataAccess.EntityFramework I had to select the correct version.
Not for me:
The one I needed
As you can see the version numbers (almost!) match up:
ODAC 12.2.0.1.0 = Oracle.ManagedDataAccess 12.2.1100
ODAC 12.1.0.2.4 = Oracle.ManagedDataAccess 12.1.24160719 (yay!)
I believe this is a failing on oracles behalf as it's not made clear despite their inclusion on a page long readme on which this doesn't feature. In additon the version numbers not quite being the same...but that's a rant for the blog.
I have the same bug. I fixed it successfully by follow this step:
On your project Right click -> Select Manage NuGet packages on Browse tab input oracle. You will see Oracle.ManagedDataAccess.EntityFramework. Select version of oracle you have installed. This should be 12.1.2400. Install it, you are done
I had the same issue - I hope I can help fellow Googlers having the unfortunate task of connecting Oracle and Visual Studio.
I followed the steps and still got crashes - because I was using VS2017 (I understand that the questions is tagged VS2015). You'll need to install the VS2017 ODAC Client. Thankfully, this one actually does something when you begin the installation. The installer in the link on the accepted answer will only work for VS2015.
The most recent version (as of this time of writing) of ODP.NET is 18.3, which can be installed through NuGet (Oracle.ManagedDataAccess.EntityFramework). Follow these steps on Oracle's website and you'll be setup.
...Or so you think. I got the same error as in this stack overflow question, where it won't go past the Entity Data Model Wizard.
I applied every configuration in the selected answer, but it still wouldn't work. When I downgraded my Oracle.ManagedDataAccess.EntityFramework from 18.3.0 to 12.2.1100, I could finally create my models!
I have had the same problem when I was trying to connect Oracle Entity Framework with Visual Studio 2017.
After install and unistall several times differents version. The build that better works for me is:
Oracle Developer Tools for Visual Studio 2017 (ODTv2017) v12.2.1200
Oracle.ManagedDataAccess v12.2.1100
Oracle.ManagedDataAccess.EntityFramework v12.2.20190115
EntityFramework .NET v6.3.0
I think that having similar versions in Oracle packages is very important for good performance.
It looks like someone here had similar issue: He add to change implementation somehow.
[in this ]case a View (valid and worked) caused the crashes. After changing the implementation without using that view it worked (more or less).
What I advise is you proceed step by step, only importing one object for the first time you test the wizard, then only simple table, then add procedures, views...
We are running Microsoft Dynamics AX 2012 R3 CU8.
Our customer wants to start using the rolecenter, but we found problems around importing Web URI into the AOT. There is a hofix for this (KB2894068), but it is for R2. The Microsoft LCS titles it: 'Error message is displayed when importing web URL page in AOT ”The parameter PageUrl is missing or invalid”'
I was wondering if there are 'Best Practices' on how to install an R2 hotfix in R3...
If it is code only, meaning it isn't a kernel hotfix, then you only need to be concerned about merging the code into your environment. You don't want to overwrite R3 code if it isn't necessary for your fix.
There should be an impact analysis tool or a way to use the compare tool to see what code will change. Or, sometimes LCS will show you what the code changes are before you download the hotfix.
I am building a substantial ASP.Net MVC app using the latest EF and MVC. Suddenly nothing works, every one of my index views now produces the following error when its generates the data to send to the index view:
System.InvalidOperationException {"Sequence contains no matching element"}
This is happening in code that was generated when I added a controller with views. It now effects ALL my index views and there are about 40 of them which all worked previously and now none of them work. The only thing I can think of is that I hit some limit as I am just adding very similar controllers.
I have found the cause of my problem. None of my previous work on this machine will work anymore. They haven't been changed and they were all working. The problem is that anything I run in Visual Studio (VWD 2013 and VS Community 2015) will NOT talk to SQL Express.
I became suspicious and removed the connection string from the problem App and got exactly the same message. I then thought I would try it with Apps that I know worked, but I ran them first before I made any changes and they (five different apps) all produced the same error.
Yet If I look at Server Explorer it still works and it is using the same Web.Config connection string, because when I remark it Server Explorer will not access the database.
As I said from the start this is some internal problem as all the code was generated by Visual Studio and then it all failed, and all my other working Apps fail as well.
I will now test it on a different machine.
I manually rebuilt it all and the problem appeared again when I added the last few Models. So that was not the solution. I got assisatnce on the ASP.Net forum from Krunal who provided a solution that worked and fixed both versions which had the problem.
I was working with Code First from the database. Krunal thought I was using Database first with Designer and suggested I use the Model Browser to refresh my model. You don't get a Model Browser if you used Code First so I added a Database First Design Model which created a EDMX file, I then right clicked on that and opened the Model Browser.
I then rebuilt it and it all worked. I then went back to the original version added an EDMX opened the Model Browser and it all worked fine. As I said from the start it was not a code issue it was an Internal problem with Visual Studio and SQL Express. No code was changed.
Our web application used the old Crystal Reports XI Rel 2 activeX to render the reports called from classic ASP. We would like now to have it run alongside the new Crystal Reports 13 run time to render reports called from ASP.NET.
We installed the exe found in http://scn.sap.com/docs/DOC-7824 (support pack 3). On our dev machines (windows XP) everything went alright, and we were able to design and render reports in both technologies. We tried to deploy it today to a client's server (Windows Server 2008 64 bit) and it obviously didn't work.
If we first try to open the new report then the old one, they both fail, but with completely generic and therefore useless error messages ones like "Error while creating report". the new one is OK, but the old one fails with message "Invalid TLV record".
Inversely, if, after restarting iis, we first try to open an old report (CR XI R2 from classic ASP), it shows correctly, but the new one (CR 13) gives this error:
Retrieving the COM class factory for component with CLSID
{F734A321-8381-4FFD-A614-139E8906DC83} failed due to the following
error: 80000003 One or more arguments are invalid (Exception from
HRESULT: 0x80000003).
We tried to google this error; the only meaningful result was this thread but it didn't help us.
Thank you
EDIT: ok, the first error was simply that the .rpt files were being left out of the deployed folder. So it really boils down to an incompatibility of the CR runtimes, maybe?
EDIT 2: Yes, it is definitely it. We moved the new report in another virtual directory running under another application pool and now they both work, regardless of what is instantiated first. So is there any way we can gradually migrate our existing records, ie have a period where both run times coexist and are used by the same virtual directory?
I had this problem. As I had just installed CR 13 without a reboot, I thought I'd try a reboot of the server. After the reboot, the problem went away.
I have the same error - reboot didn´t help.
Installed SAP Crystal Reports runtime 13.0.0.99 on Win7 but got several errors registering components during installation - think that is the cause of the problem.
Downloaded and installed CR Runtime 13.0.21.2533 (32bit)
from
https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads
http://downloads.businessobjects.com/akdlm/crnetruntime/clickonce/CRRuntime_32bit_13_0_21.msi
That installed without errors but didn´t work either :-(
Background:
We are hosting a .NET 4.0 Windows Workflow activity inside a WCF service on IIS. The server is a Windows 2008 R2 machine.
Problem:
The ‘Activity’ fails inside the constructor’s InitializeComponent() call with the following stack trace (XamlObjectWriterException). This problem appears to be machine related – i.e. it works on some machines, but fails on others.
Stack Trace :
at System.Xaml.XamlObjectWriter.WriteEndObject()
at System.Xaml.XamlObjectWriter.Dispose(Boolean disposing)
at System.Xaml.XamlWriter.System.IDisposable.Dispose()
at MyActivity.InitializeComponent() in \MyActivityLib\obj\Debug\MyActivity.g.cs:line 81
Has anybody found a similar problem and/or know the cause? I found this Microsoft Connect bug, which gives the same error, but they don't seem to have been able to reproduce it reliably, and it was closed before RTM.)
One of our developers could induce this error when hosting on IIS (Windows XP), while the activity ran flawlessly out of a test console app on his machine. He then deleted his source tree and rechecked it out, and the IIS problem appears to have gone away for him. However, trying the same approach (delete source & re-checkout) hasn't fixed our build server / test environment combination.
Thanks
It turns out that our server was still running .NET 4 Beta 2. Still doesn't explain the problems we had on the developers local machine (definitely running RTM), but oh well - at least it's fixed.