Sage 100

We are adding a module (CRM) to an existing MAS 200 EES 4.40 installation. Not sure why the CRM module was not installed on their last upgrade....but anyhow...We are running the installation and it gets all the way to the end and comes up with: Error 107 in program SY_EMBEDDEDIOCOMMON at line 0268 Error #107: Keyed file error (wrong key block address) There are no files referenced. I have seen the posts about using UFAR for error 107's but not sure what file would be the offender or if UFAR is even appropriate. Has anyone seen something like this before? Thank you for any input!

I found this in the old KB, might be an easy thing to check. http://infosource.sagesoftwareonline.com/infasp/kdb.asp?isresolutionconceptid=502988

Not sure why the CRM module was not installed on their last upgrade...."" Maybe "" We are running the installation and it gets all the way to the end and comes up with: Error 107 in program SY_EMBEDDEDIOCOMMON at line 0268"" Just a WAG.

Thanks for the input Debbie, but not the issue. We rolled the install back and I am now on hold with Sage support...loving the new on hold music...not... Going to try to isolate the keyed file that has the issue, crossing my fingers and will update the post as soon as we have meaningful info

SY0DD2.soa file is being accessed there.

1. Restore the SY0DD2.SOA from an older backup 2. Repair the file using UFAR.BAT or SVXBLD.

Thanks Lee and Jim. We will give that a try!

I typically start with running the script to replace the embedded IO's first. Least evasive approach. That's the File / Run , Program = syzcon At the prompt type the following: o=new(""sy_activation_bus"",%sys_ss) Hit enter and type on the second line: print o'activate(""y/y"",""xxx"") And hit enter, you should get a 1 returned to show the script ran successfully. The y/y represents the module code and the xxx represents the company code. Run the script for each module in the company beginning with C/I

More good information. Thank you Joan. To clarify, you mention that you ""typically start"" with this utility...can you briefly describe the circumstances where you typically apply this solution? Thanks much!

It seems to me that the bigger picture is why (or even how) you would add the CRM module to an EES system. The EES systems contained the CRM module, that's what made them EES. I am thinking you have bigger fish to fry than either Joan's embedded IO or SY0DD2 issues, although I could be wrong. How did the CRM module get removed in the first place? I would think you would want to answer that question first. I would think a complete reinstall of the original EES system might be in order.

I'm not sure - I think it required you install EES with the EES keys but I don't think you had to install CRM only the Integration Engine. I know if you purchased EES just to get the bundle of modules the keys would not work on regular Sage -- they forced a re-install using EES.

Update - I LOVE 90Minds! Turns out the sy0dd2.soa WAS the problem. We grabbed one from a clean 4.4 installation and put in place of the bad one. The installation to add the CRM module progressed without error. We went forth and re installed the other 3rd party applications without error as well. My prelim testing suggests that we are in good shape...of course tomorrow morning when the users start up will be the real test. Keeping my fingers crossed! On a different note - we activated the CRM module and connected it too the CRM installation and the integration seems to work EXCEPT if a customer is linked to CRM (via a successful push from MAS to CRM...each time we access the customer and click the ACCEPT button we get the following errors: Record is missing from .....\CUHPI\CU_Address.M4T Info says Error 11 program CI_CUConvertData.pvc line 1350 If END on Error get: SY_ActivityLog does not have correct permissions IF END from the INFO screen get: CM_ScriptLink does not have correct permissions Could this be still related to the Sy0dd2.sao file issue or something new?? Many many thanks you to all who commented!! @CullenLowe - I did not personally perform the last upgrade for this client, but I suspect the CRM module was manually de-selected during the upgrade or removed since the customer was not using the CRM Application.....hoping you are wrong about the big fish...

@RebekahVeuger, hoping I'm wrong, too :-) It's been a while, and of course those errors are not in the new KnowledgeBase, but do you know how to look for those dreaded ""N Records"" in the CU_Address table? If you have a failed sync you will get those records and the only way to remove them is to run the Rebuild CRM utility. That will repopulate the CU tables based on the mirror tables. Before doing that, though, you probably want to look at the CRM Activity Log to see if there any errors indicating SQL communication problems, etc.