I want to install Ax 2012 in my local machine. Does anyone know the steps involved in installing Ax2012
Highlights are you need 64 bit for the AOS, Help Server and EP (if you want it). I agree with the previous answer, 8GB memory is minimum. We tried on 4GB but it just won't work.
Our developers all have 2012 installed on their windows 7 (64 bit) machines. Remember you need SQL reporting installed to run ANY reports. You can run AX 2012 without SQL reporting just fine, but you won't have any reports at all (no invoice and packing slip etc).
Some of our guys have reporting and EP all running on their win7 machines. Remember that that is officially not supported though.
Follow the instructions in the Installation Guide.
For testing purposes you may use a preinstalled image. Requires PartnerSource or CustomerSource login.
Either option require lots of memory, 8 GB should be a bearable minimum.
Related
I need to migrate an enterprise production database from a Windows source machine running Postgres 9.5 to an Ubuntu destination machine running Postgres 11.6 with < 15 mins downtime. I plan to do this with pglogical, which requires the extension being loaded on both source and destination. I am having trouble with the source side because it is Windows.
I have very little Postgres-Windows experience and can neither find any helpful literature on the specific situation nor can I figure out for myself how to presumably install from source.
I've dug and dug and so far the only answer I've been able to find is "ugh... Windows". It seems like the only way to build from source is using Visual Studio, which I don't have or know how to use.
Sources:
https://www.2ndquadrant.com/en/blog/compiling-postgresql-extensions-visual-studio-windows/
https://postgrespro.ru/list/thread-id/1835275
Alex, the 2ndQuadrant article you link to in your own comment solves this. A few of the project or build options noted there have moved a little bit in the newer VisualStudio Community editions, so I can see where you got hung-up.
Just for kicks I compiled 32-bit DLL on my oldest Windows instance. I included the /Release path so you can grab my DLL & see if it works for you. It's (a) 32-bit because I'm assuming worst-case for an old v9.5 install, and (b) targets Postgres 9.6 because that's what I had installed. Unless there were major API changes though, it should connect to v9.5 without any issues:
https://github.com/mbijon/winpglogical/tree/master
If you find you need a version that entirely matches Postgres 9.5, grab my solution files & VS Community 20xx. Load the project & update the Additional Include Directories in Project Config to target your v9.5 paths. That should be all that's needed to link v9.5 Postgres libs.
Platform: Windows server 2012 R2 Datacenter
Version: mpich2-1.3
Problem: I have installed mpich2 on my windows server before and I could start mpiexec quickly. However, recently I added a domain for my windows server. After I shifted to my new domain and account, mpiexec seems to start too slow. I tried re-install MPICH2, but it still takes about 2 minutes to start the example cpi.exe. My intent is to use MPICH2 to run another program, which is much bigger than cpi.exe, and even if an hour passes, the calculation seems not start. I am quite confused. If you know any solution/guidance, please tell me.
I finally solved this question by migrating MPICH2 to MS-MPI. The codes are the same, but some configures of Visual Studio Project should be changed. A good article for how to compile MS-MPI program in Visual Studio: https://blogs.technet.microsoft.com/windowshpc/2015/02/02/how-to-compile-and-run-a-simple-ms-mpi-program/
I'm having problems installing BI Publisher for Desktop 11.1.1.9.0 32bit(11g) on Win7 64 bit system (Office 2013). Previously I successfully installed it but there was no add-on visible in Office, so tried with 64 bit version but with no luck. After that I've uninstalled it but now it keeps giving me these errors, "INSTALL DIR get falied!" and "TBMenusSetup.msi!"
Any idea hoe to solve this?
Br
This is what I did on Windows 7 (64-bit) and Office 2013 (32-bit):
Download: Oracle BI Publisher Desktop 11.1.1.7.0 for 32 bit Office on Windows (244 MB) - http://www.oracle.com/technetwork/middleware/bi-publisher/downloads/index.html
Run BIPublisherDesktop32.exe
If Add-In doesn't show up at this point, run step 4
Run setup.exe from here: C:\Program Files (x86)\Oracle\BI Publisher\BI Publisher Desktop\DotNetInstallFiles\setup.exe
Done
I also check the following conditions if I have trouble with installing BIP (which I often have)
Make sure that the versions on your system are matching
(JRE,Office,BIP). That means: If you have Office in 64bit you need
JRE(64bit) and BIP(64bit).
Check if the addon is deactivated by word and activate it in case.
Use "Run as Administrator" with the BIP Installer.
Hope this helps :)
download bi publisher desktop and do a fresh install.
if you are not getting the add on then go to Microsoft office icon-->word option-->add ins-->then check in manage drop down(disabled items).If its Bi Publisher then click on that.You will get this in MS word.
https://carsandcode.com/2014/05/12/oracle-bi-publisher-desktop-on-64-bit-windows-with-32-bit-office/
Personally, until next time, not sure what worked, as above step I did earlier with no resolution.
But, I have been installing, troubleshooting BIP Desktop for few years and each time it is broken, fix do not exist and there are threads which leads to absolutely nothing. This time around, O365 was rolled out to Pilot Users and yes BIP toolbar gone. Uninstalled O365, re-installed Office 2010, repair/remove/reinstall - none worked. Ran MS Debug/ Sysinternals - Procmon/ProcessXP - found leak threads but nothing to suggest which components is missing or corrupted. Finally, I started running all msi and pre-req sw in BIP dir and DotNetInstallFiles, and it did come back the elusive toolbar, which MS Word fails to load or kept in Inactive add-ins.
We are running an AS400 v5r2 and I have iSeries Client access installed. Since v5r2 does not support a x64 ODBC driver does anyone know how I can either install two versions (v5r4 supports x64) of iSeries Client Access on the same box or just install the x64 odbc driver from the more recent version without uninstalling all of v5r2 components.
Installing two versions of Client Access is probably not going to work, since both register their ODBC drivers with the same name, so only one would be available at a given time.
OTOH the PC side of V5R4 Client Access would probably work without problem with a V5R2 OS/400; perhaps even 6.1 iSeries Access, too. So you can upgrade the x64 box and check whether everything is working. FYI, I had problems with the first versions of 6.1 iSeries Access when running on x64 boxes, later versions were a bit better; also, I do not remember that V5R4 Client Access had a 64-bit variant at all.
Do not forget that on a x64 PC, there are two different ODBC drivers, one for 32-bit applications (stored on C:\WINDOWS\SysWOW64\cwbodbc.dll and that you can manage with the 32-bit administradorC:\WINDOWS\SysWOW64\odbcad32.exe), and another one for 64-bit applications (stored on C:\WINDOWS\System32\cwbodbc.dll and that you can manage with the 64-bit administrador C:\WINDOWS\System32\odbcad32.exe.) Unless your application is recompiled for 64-bit, what you are interested in is the former one, and if V5R2 Client Access runs flawlessly on that PC, everything is fine. Some applications like Office 2010 come in two flavours, but precisely for compatibility reasons like ODBC, it is still recommended to run the 32-bit variant even on 64-bit workstations.
1) V5R2 is very dead. You aren't going to get a lot of help when it comes to supporting an OS this old.
2) V5R4 is also dead.
3) Generally speaking, IBM intends that Client Access will work for operating systems two levels back and two levels ahead, so you could try using a V5R4 ODBC driver against a V5R2 DB2. The issue is going to be getting a V5R4 version of Client Access.
4) If you have questions about admin issues like this, Server Fault is probably the better choice.
EDIT: Add details of Client Access installation
Client Access has two logical pieces, a server side component and a client side component. Both pieces are available in the IFS, in the QIBM directory tree. If you have an already-working setup of Client Access on the server side, you can install the client side one of two ways:
1) Map a network drive to the IFS and run setup from there. This obviously won't be helpful to you because the V5R2 software doesn't support x64. If you are still under software maintenance, you could order a newer version of Client Access and install it on the server, and then use the newer version to install the needed ODBC driver.
2) Use the IBM-supplied CD to install the client component directly on the client. This allows you to install a different client version than the one on the server. Not generally recommended but in the case where you're migrating away from an unsupported machine, it's probably not a big worry. If your company ordered V5R4 at any time, you have the Client Access CDs.
The key thing for you is that you don't need to install the full Access product if all you need is the ODBC driver.
The biggest problem facing you is the age of the software. IBM stopped supporting V5R4 in Sep 2013. You aren't going to be able to place an order for it with IBM. You might be able to order V6R1 but the ODBC driver may not work with V5R2 - you'd have to try it. See the IBM i Access web site for details, but it's not downloadable.
If you can use OLEDB, try IBM's FTP site.
I'm using sqlAnywhere 5.0 to create ODBC with third parties software house
I'm running it on windows XP without any error / problem
but 8/4/2014 Microsoft announce to stop service for windows XP
then our company migrate all client PC to windows 7x64
Now the application always hang and closed itself
I would like you suggest what can I do, I'm trying to test under SQL Anywhere 12.0 but I cannot config ODBC to open application
I also attached a picture (ODBC from rtdsh50.exe)
Start command is "C:\Starlims8\SqlAny50\Win32\rtdsk50.exe -d -c4000"
Please advise, Thank you in advance.
According to the image, you are using the version 5 runtime engine. This software is almost 20 years old... I am not surprised you are having trouble getting it to run on Windows 7.
It doesn't look like you are providing a database file on the startline in the ODBC configuration. Are you providing this somewhere else? What does your actual connect string look like in the application?
Version 12 will probably not work, since your application was written for version 5. However, to even have a chance, you have to rebuild the version 5 database in version 12 format and then replace the SQLA version 5 ODBC data source with a version 12 one with the same name.
Is this an application that you/your company wrote or is it a third party app. you purchased? Is it a 16 or 32 bit application?
Also, I would suggest setting the application up to run in compatibility mode as well as running it as an administrator.