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.
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...
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.
I recently installed CU9 to BizTalk 2010. Microsoft site (https://support.microsoft.com/en-us/kb/3136004) claims that all previously CU are included in latest CU.
BizTalk Server uses a cumulative update (CU) model for providing fixes and updates. Each cumulative update includes new updates in addition to all the updates that were included in previous cumulative updates
Now I have problem with deployment ("Error saving map. Stored procedure returned non-zero result." error message when you deploy the BizTalk Server 2010 applications in BizTalk Server 2010 Administration Console") supposed to be fixed in CU4.(https://support.microsoft.com/en-us/kb/2667310)
So do I need to install all CUs from 1 - latest (for BizTalk 2010) to be fully upgraded?
You do not need to install all of them, the latest is just fine. They are cumulative as is stated.
That being said: have you tried uninstalling the latest CU (CU9) and installing CU4 instead? I assume you had no CU's installed before?
Unfortunately, lately Microsofts track records in relation to BizTalk CU's is not something to be proud of... There were quite a few issues with CU's already. It is not unthinkable that some CU after CU4 reintroduced the issue.
Also: the specific issue you are mentioning is something that was supposedly being fixed in CU4. However, this is just one particular case that was solved. There are still other remaining cases which have not been fixed yet.
Problem solved. It turned out that this App is using resources from another app that was not fully upgraded and one schema was missing in it. After deploying/upgrading that shared application everything went well.
While trying to integrate R Studio with SQL Server 2016 I am getting following error:
Unable to launch runtime for 'R' script. Please check the configuration of the 'R' runtime.
As suggested on different sites it is advised to install "%programfiles%\RRO\RRO-3.2.2-for-RRE-7.5.0\R-3.2.2\library\RevoScaleR\rxLibs\x64\RegisterRExt.exe" /install.
But I have already installed R studio and not able to find the path specified.
R Services for SQL 2016 is a new offering from Microsoft - who purchased Revolution Analytics about a year ago. This is the first major result of that.
SQL Server 2016 is in (CTP - community technical preview), so not really finished (although you can download and use a version that will expire after about 6 months). Also a lot of the docs are incomplete and there are probably a fair amount of bugs. However it has been long announced that it will include "R Services for SQL 2016", which is based on the Revolution R Engine. In order to use that you have to
Install SQL Server 2016 CTP as usual.
Install the "Advanced Analytics Extensions" from the setup.exe program (see https://msdn.microsoft.com/en-us/library/mt590808.aspx)
Obtain the appropriate RevoScaleR packages (there are two) and install them, one your client, and one on the machine running SQL 2016. They are described here: https://msdn.microsoft.com/en-us/library/mt604883.aspx
Then to test it you can follow the instructions here: https://msdn.microsoft.com/en-us/library/mt590808.aspx
Good luck with it, but remember it is still in pre-release development and testing, so problems are to be expected.
I've managed to break Access on my laptop. I had Office 2010 installed, then decided to upgrade to Office 2013 after going to an MS presentation. This wasn't the best move for me.
I realised after installation that Access 2013 doesn't support ADP's. So ran the installer and removed Access and reinstalled it from Office 2010. At this point all is well.
This morning I decided to uninstall Office 2013 entirely and reinstall Office 2010. Most of the office apps are working fine, but when I try and run my ADP in Access 2010, it seems to be appending a 1 to the end of all of my database objects, then errors out saying it cannot find the object.
I'm getting the following error trying to type into a combo box on the opening form of the database. " cannot find the object 'Company1'".
The correct name for the table object it cannot find is Company, not Company1. It seems to be adding the one on for other objects as well.
I have checked the connection property for the database and it is testing okay. I can open up the table in design view, and it shows me all of the columns etc, but I cannot open it in datasheet view to see the rows. I get the same error as above.
I don't believe that the ADP file itself is corrupt, because I can open it fine from another PC.
I have tried uninstalling Office 2010 and reinstalling from scratch, but I can't seem to solve the issue.
Is there a registry setting or something that is playing with the object names?
I'm at my wits end, so any help is appreciated.
Thanks,
Mike.
I found your question when having a similar problem with my PC; in my case, I added Access 2010 to a PC with Access 2003 - when I did that, it caused problems when I tried to filter on forms. The solution was to downgrade a DLL
C:\Program Files\Common Files\Microsoft Shared\MSClientDataMgr\MSCDM.DLL
Version 14.0.4731.1000 had to be downgraded to 11.0.8204.0. Suddenly filtering worked again!
So last night I was testing one of my ADPs in Access 2010 (they want us to upgrade!) and I got the same problem you had - it was appending "1" to tables, views, stored procedures, etc. So on a whim, I changed back to the newer DLL. It did the trick and I have my tables/objects back! It appears that different versions of the DLL have problems with different versions of MS Access.
Although you may have uninstalled Access 2013, it wouldn't have changed all your DLLs to the old one. I'd suggest that you rename the MSCDM.DLL (right-click it and get the version number first) and see if you can get Version 14 installed in its place. It shouldn't require a registration or a reboot - mine worked when I replaced the DLL and opened my ADP again.
Good luck!
Kevin