How much of an effort does it take to upgrade from 32bit client to 64bit? Any concerns or anything we should be aware of that could cause issues?
I believe it is just a matter of creating a Shortcut to the MfgSys64.exe Application from the \Epicor905\Client\ folder.
Here is the Warning when using it:
Once in a while our Finance users would run the 64-bit Client if they had a Dashboard with a Lot of data that they were running. And I think I remember they would get a red ‘X’ on a grid view or something to that effect every so often but running the 64-bit version of the Client helped.
1 Like
How would this impact our custom codes that may have been developed on 32bit .dlls?
Can you expand on the problem are you trying to solve by going to the 64bit client?
1 Like
We upgraded FAS and now our Crystal Runtime no longer runs on 32bit in Epicor. FAS will only work on 64bit CR. When we went to uninstall and reinstall 32bit CR, it works for Epicor but broke FAS. So in order to get both to work, we need to run on 64bit client. Not sure why having both the 32bit and 64bit CR installed doesn’t resolve the issue.
Not sure what FAS stands for, but, something not working with the 32bit client is a good reason to use 64bit IMO (there aren’t very many good reasons to use the 64bit client, so I was concerned). Carry on 
1 Like
FAS is the Sage Fixed Assets software we use in Finance. It required installing the ODBC driver for 64bit so not sure if that might be a contributor to the issue.
What is all involved in going from 32bit to 64bit? Is it as simple as updating the shortcut link to mfgsys64.exe and then testing with your custom codes and processes? Would we request SCR fixes in 32bit or 64bit going forward?
need to change the shortcuts to point to mfgsys64.exe and install the 64bit Crystal Runtime on everyone’s workstation. You wouldn’t request one-offs any differently than you do now. Just provide Support the DB type, the Epicor Server OS, and whether 32/64 OE is used.
Can mfgsys64.exe work with 32bit Crystal Runtime?
I don’t think that would be too hard to test on your own. Just open up the 64bit client on a system with the 32bit Crystal Runtime installed and see if a Crystal Report runs for you. Sometimes seeing is believing!
2 Likes
I think the bigger issue is having multiple versions of Crystal Runtime running on the same local PC client. Heard that CR 2016 won’t run with E9’s CR 2013 at the same time.