This is a question related to non-prod testing and evaluation
I know it's technically possible to have the Ax 2012 R2 client installed locally and have a copy of the R3 Client installation folder copied locally to allow a user to access both Ax 2012 R2 and R3 environments using the same machine
However, is it possible to do some kind of workaround like this to get the DIXF client tools for R3 working on the same local machine where the R2 DIXF client tools are already installed?
I can't just install the DIXF tools for R3 on the same machine as the installer complains about the older version of the DIXF client tools
Related
I'm unable to find anywhere online where it states that BizTalk Server 2010 is supported/not supported fully by Windows 10.
No, not even BizTalk 2013 R2 is supported on Windows 10 as can be seen at Summary of 64-bit support, operating systems and SQL Server versions supported by BizTalk Server and also
Hardware and Software Requirements for BizTalk Server 2013 and 2013 R2 as it is not listed on either page as a supported operating system.
There is a related question about BizTalk 2013 R2 and windows 10 called BizTalk Server Configuration failing to create group. The conclusion for that is, yes you can run BizTalk 2013 R2 on Windows 10, but as per a answer and comments there it probably will not be supported by Microsoft for a Production environment and could break with updates and patches applied to the operating system.
No, not directly but that shouldn't matter because running BizTalk Server on any client OS is never the best option.
Yes, you can run BizTalk Server 2010 in a Windows Server 2008 R2 VM using Client Hyper-V. You need Windows 10 Professional or Enterprise but this would be the best way to do it even if the client OS supported it directly.
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
I have a website which will use OleDB.12.0 to read data from an Excel worksheet upon upload. It works fine on my local PC. But when hosted in my production server I get the following error.
microsoft.ace.oledb.12.0 is not registered on the local machine
How can I correct this?
My production server configuration:
MS Office 2007.
IIS 7
VS 2010
Windows 2008 R2
SQL Server2008
Does your production server have Access installed?
In any event, try installing/reinstalling Microsoft Access Database Engine 2010 Redistributable to the production server.
Update
Another point: is your production server running 32-bit or 64-bit Windows? Choose the download appropriately.
Update 2
From this link it appears that using the 64-bit version will cause trouble on a 32-bit system, but the 32-bit version will work.
I have a database in my App_Data folder that was created using SQL Server 2008 R2.
When I try to view a page, I get this error message:
The database 'C:\My Projects\NCPA\APP_DATA\NCPA.MDF' cannot be opened
because it is version 661. This server supports version 655 and
earlier. A downgrade path is not supported.
Could not open new database 'C:\My Projects\NCPA\APP_DATA\NCPA.MDF'.
CREATE DATABASE is aborted.
An attempt to attach an auto-named database for file C:\My
Projects\NCPA\APP_DATA\NCPA.MDF failed. A database with the same name
exists, or specified file cannot be opened, or it is located on UNC
share.
Here's my connection string:
<add name="NCPA" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\NCPA.mdf;Integrated Security=True;User Instance=True;MultipleActiveResultSets=True" providerName="System.Data.SqlClient" />
I have SQL Server 2008 R2 and Visual Studio 2010 installed on my computer. I've searched this problem all over, and everything says "You need R2", but I already have it.
I've also seen that I need to check the SQL Server instance name by going to Tools > Options > Database Tools > Data Connections, mine just says SQLEXPRESS. Is that right? Should it be something else?
What do I need to do here? Is there something that I might not have installed? Is there a setting in Visual Studio that I need to change? I feel like every solution I've found is so vague, or the solution is something I've already done.
EDIT: Here's what I have if I start up SQL Server, and go to Help > About:
Microsoft SQL Server Management Studio - 10.50.1617.0
Microsoft Analysis Services Client Tools - 10.50.1617.0
Microsoft Data Access Components (MDAC) - 6.1.7600.16385
Microsoft MSXML - 3.0 4.0 6.0
Microsoft Internet Explorer - 9.0.8112.16421
Microsoft .NET Framework - 2.0.50727.4961
Operating System - 6.1.7600
While you may have installed SQL Server 2008 R2, are you sure you upgraded the instance you're using to R2?
Use the SQL Server Installation Center from your R2 media and the "Upgrade from SQL Server 2000, SQL Server 2005, or SQL Server 2008" option to upgrade your SQLEXPRESS instance to R2.
My guess is that your code is trying to connect to the database instance that was install with Visual Studio 2010 instead of the SQL Server 2008 R2 instance that you have installed.
Are you really, really sure that the SQL Server you are trying to attach the database to is SQL Server 2008 R2?
Your error message says that your SQL Server only supports version 655, and everything I found concerning these version numbers said that version 655 is SQL Server 2008 (non-R2):
SQL Server: Attach incorrect version 661
SQL Server 2008 R2 bumps the database version
Cannot read SQL Server 2008 database - version increased to 661 from 655
If you really have SQL Server 2008 R2 and it still doesn't work, you'll probably have to re-install the server, like raym0nd said in the comment to his answer.
EDIT:
Steven, none of the numbers you posted is the "real" version number of your SQL Server.
You can find out the actual version number by running select ##version in a query window in Management Studio.
On my machine, Help --> About says Microsoft SQL Server Management Studio - 10.50.1617.0 like on your machine, but when I run select ##version I get this:
Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (X64) Mar 29 2009 10:11:52
Copyright (c) 1988-2008 Microsoft Corporation Express Edition (64-bit)
on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
And here comes the weird part:
I am 100% sure that I installed SQL Server 2008 R2 on my machine.
In fact, the SQL Server stuff in my start menu says "SQL Server 2008 R2" everywhere, and the Help --> About window that you mentioned has a huge SQL Server 2008 R2 logo as well.
But according to several lists that I just found, 10.0.2531.0 is SQL Server 2008 SP1.
So my installation seems somehow messed up as well.
Strange, very strange...
I encountered the similar issue, when trying to attache an .mdf files that was created on another machine running SQL Server 2008 R2 Express, to the SQL Server 2008 R2 Express on my machine..
I did install 2008 (non-R2) and then 2008 R2 on my machine.
After spending hours googling to find a solution, eventually unsuccessful, I simply decided to download the installer SQLEXPR_x64_ENU.exe from here and run it again, hoping it would solve (Windows 7 64 bit)
On the installation Wizard under Installation, I selected Upgrade from SQL Server 2000, SQL Server 2005 or SQL Server 2008 and continued to press Next until it disappeared (Obviously you will have to wait until it finish processiong each step).
That's it. I was able to attach the same file..
Download and reinstall the new MS R2 SQL SERVER , When Microsoft updates something, it doenst support older versions most of the time.
Here what worked for me without trying any updates!
From Visual Studio --> Server Explorer --> Add New Connection
Change the data source to Microsoft SQL server
Server name : My computer's name or localhost
At the drop down list choose the database you want
Everything works fine! No updates and no 661 problems!
We are attempting to install BizTalk Server 2006 R2 on a fresh server with x64 Windows 2008. The basic configuration is complaining that the “Default Web Site” we select for the BAM Portal installation is not validated due to “IIS is not 32-bit enabled.” Despite setting the appPool (Classic mode) 32-bit property to True, BizTalk configuration wizard is still complaining.
Has anybody successfully installed BAM Portal in 64-bit IIS 7.0?
It looks like Microsoft’s official statement is Biztalk Server 2006 R2 with Windows 2008 is “not supported”. BizTalk Server 2009 is the one that is meant to be married to Windows 2008.
UPDATE, MOFE INFO
I should additionally comment that the process of setting up a multiple servers for a BizTalk Group requires configuration of network COM+ and DTC access, of which Windows 2008 interface of doing so differs from Windows 2003. In fact, I haven't found how to configure MSDTC in Windows 2008 as required by BizTalk 2006. Failing to properly configure this will prevent some of the databases from being created properly in a remote SQL Server due to transactional failure.
BizTalk 2006 R2 will not be supported on Windows 2008 and this will not change going forward, if you wish to get this configuration working you will need BizTalk 2009.
I've managed to install/configure BAM with no problems in W2008/x64.
What I can't seem to do is getting the BAM portal to work, however. Without x32 compat enabled in the app pool, I get an expected assembly loading error. With x32 app compat enabled, I just get blank pages in the web, even when adding a static .html page to the site.