Trying to update from 10.2.600.3 to 10.2.700.10 but I am getting the message that 10.2.700 is not detected. Do I need to install the full package for 700, or is there an update from 600 to 700 I am missing to get to 700.10?
Sorry for the stupid question, just don’t to ruin everything.
Yep - full installation on the Appserver. You really need to follow the steps in the Installation/upgrade PDF for the server side stuff, and then it points you to the client side install.
Ok, I think I did it, but the conversion workbench fails at Import GL Transaction Types, I can’t login as myself only as manager, I am so worried I deleted everything
ok, thank god… hahah, I just logged in as manager and didn’t see any jobs, or anything, so I am dying but I am still going through this, I have done this before, a few times actually, but I dont remember it being this heart pounding
yeah, the workbench is still open, i am so confused, I am getting this now, I am looking on here for how to fix it, just trying to sort through it, unless you already know what it is
Errors:
Company ‘JA’ GL Transaction Type ‘AP Invoice’ Revision ‘Base Std’:
Cannot convert Segment ‘Chart’ for Book MAIN Package Standard: mapping is not defined. Please correct Segments Mapping setup on GL Book Entry and run conversion program again or import Revision for this GL Transaction Type manually. Revision ‘Base Std’ of transaction type ‘AP Invoice’ company ‘JA’ could not be upgraded automatically. Please see Change Log.
Company ‘JA’ GL Transaction Type ‘AR Invoice’ Revision ‘Base Std’:
Cannot convert Segment ‘Chart’ for Book MAIN Package Standard: mapping is not defined. Please correct Segments Mapping setup on GL Book Entry and run conversion program again or import Revision for this GL Transaction Type manually. Revision ‘Base Std’ of transaction type ‘AR Invoice’ company ‘JA’ could not be upgraded automatically. Please see Change Log.
Company ‘JA’ GL Transaction Type ‘COSAndWIP’ Revision ‘Base Std’:
Cannot convert Segment ‘Chart’ for Book MAIN Package Standard: mapping is not defined. Please correct Segments Mapping setup on GL Book Entry and run conversion program again or import Revision for this GL Transaction Type manually. Revision ‘Base Std’ of transaction type ‘COSAndWIP’ company ‘JA’ could not be upgraded automatically. Please see Change Log.
Company ‘JA’ GL Transaction Type ‘Epicor FSA’ Revision ‘Base Std’:
Cannot convert Segment ‘Chart’ for Book MAIN Package Standard: mapping is not defined. Please correct Segments Mapping setup on GL Book Entry and run conversion program again or import Revision for this GL Transaction Type manually. Revision ‘Base Std’ of transaction type ‘Epicor FSA’ company ‘JA’ could not be upgraded automatically. Please see Change Log.
Company ‘JA’ GL Transaction Type ‘Fixed Asset’ Revision ‘Base Std’:
Cannot convert Segment ‘Chart’ for Book MAIN Package Standard: mapping is not defined. Please correct Segments Mapping setup on GL Book Entry and run conversion program again or import Revision for this GL Transaction Type manually. Revision ‘Base Std’ of transaction type ‘Fixed Asset’ company ‘JA’ could not be upgraded automatically. Please see Change Log.
Company ‘JA’ GL Transaction Type ‘Payroll Check’ Revision ‘Base Std’:
Cannot convert Segment ‘Chart’ for Book MAIN Package Standard: mapping is not defined. Please correct Segments Mapping setup on GL Book Entry and run conversion program again or import Revision for this GL Transaction Type manually. Revision ‘Base Std’ of transaction type ‘Payroll Check’ company ‘JA’ could not be upgraded automatically. Please see Change Log.
Company ‘JA’ GL Transaction Type ‘PO Release’ Revision ‘Base Std’:
Cannot convert Segment ‘Chart’ for Book MAIN Package Standard: mapping is not defined. Please correct Segments Mapping setup on GL Book Entry and run conversion program again or import Revision for this GL Transaction Type manually. Revision ‘Base Std’ of transaction type ‘PO Release’ company ‘JA’ could not be upgraded automatically. Please see Change Log.
Company ‘JA’ GL Transaction Type ‘Revenue Recognition’ Revision ‘Base Std’:
Cannot convert Segment ‘Chart’ for Book MAIN Package Standard: mapping is not defined. Please correct Segments Mapping setup on GL Book Entry and run conversion program again or import Revision for this GL Transaction Type manually. Revision ‘Base Std’ of transaction type ‘Revenue Recognition’ company ‘JA’ could not be upgraded automatically. Please see Change Log.
Are you sure there is not another conversion program that failed? Unless I am wrong, if the posting rules program don’t succeed, it should not prevent you from opening Epicor.
I STRONGLY recommend that you install the latest patch. I’ve done tons of upgrades and never ran into this… but I never, never performed an upgrade on the base version.
These error suggest the mapping of the segments is not right. I am sure this is mentioned in the upgrade guide somewhere (I don’t have it at hand right now to check).
Yeah, I had checked that, but at the end, I just kept making the server worse. I was prepping my pink slip, to make the exit quicker and I finally just restored the server and thankfully, the backup worked hahah. Thankfully, I do a pretty good job taking care of the network so my backup worked fine, so I need to double down today.
We do not utilize Chart, Division or Departments and I could not find a conversionparams after the update, now that I have a clean slate, I will whip out my magnifying lens and focus more on the document. I must have missed something, I have updated a few times before successfully, but something changed along the way.
Thank you so much for your time, I will update once successfully, If I don’t reply, chances are I was fired and it would be hard to reply from my new job at McDonalds, cuz the wi-fi is no good. Thanks again
Yes and no, but out of frustration, I just restored the server, starting again this morning, I need to study the document closer. I have upgraded a few times before, the first time I blew things up, but the 3 times afterwards was smooth, but something changed. Thanks for your help and I will come back once i am done to let you go, unless I a get fired or something haha.
Never, never, neeeever upgrade your production system without having tested the upgrade on a separate VM first, and have the end users doing some testing! Good luck.
Before you try an upgrade again, I would reload the posting rules in the JA company. Then if you get an error, it will be easier to troubleshoot since you still have access to the system.
yeah, you definitely want to do a test run of the upgrade before touching production. I spin up a new VM, install the same version of Epicor as production and then copy the database over and upgrade that. We then give key users access to this system for testing. I repeat the process until I can do it smoothly.
well, I came into this company 3 years ago, and have been fixing what the previous person did… it wasn’t easy. One of the short comings is lack of space, we still have this issue, but earlier this week I found a rogue VM, that has no use, so I might reclaim that space and use it for a copy. You brought up posting rules, One of the few things I don’t fully grasp about Epicor, since it has never been my thing, the GL, it was done for it, can you clue me in or point me in the direction were I can learn about posting rules?
I have been a Product Development Engineer for Alienware, later Dell when they bought us and then Velocity Micro, so I love to tinker and they took a chance on me 3 years ago to hire me as the IT Manager since I really haven’t done it before and I have done great here, after AW, D and VM, I worked at AMC Technology as a Solutions Engineer, so I got to learn the ins and outs of Salesforce, Desk.com, Siebel, Dynamix, Siebel, SAP so they though I would be a great fit here for Epicor, but Epicor is sooooooooo different. Also, my focus was Salesforce and its not as deep as the rest.