Sage 100

@AlnoorCassim Do you know how the MAS 4.4 ""MAS_SETUP.exe"" knows that there is an existing MAS system? I need to reinstall the 4.4 system over an existing 4.4 system and it is saying that I need to input a new location and use the parallel migration.

Looking into it ..

I think that Jeff may have posted a solution to this. I've had to point out to support when they recommend that I ""reinstall"" 4.4 that this error message will pop up. I think Jeff S posted on this maybe 3 to 6 months ago --- another reason we need a way to build some type of KB centered around common issues and solutions not readily documented in SOSS

I guess I should of asked ;""How do you move a 4.4 system to a new location?

Well the answer from SAGE is to install at new system location and then migrate from the 4.4 to the new 4.4

Excuse me for a minute. BAWHAHASHAHAHAHA BAWAHAHAHAHAHAHA HAHAHAHAHAHHAHAHAHA (cough) bullshit BAWHAHAHAHAHAHAHAHAHAHAHAHHAHAHHAHAHHAHAHAHAHHHAHAHAH What a bunch of morons

I'm not engineer. I didn't even sleep at a Holiday Inn Express --- ever. But holy shit even I would have expected this issue and designed a way around it. And what is Sage's proposed resolution for adding modules? Shouldn't that be impacted in the same way. Do we go to the customer and have all 30 users log out so we can do a 4 hour parallel migration? Really?

Here's what I was thinking of: From: John Broadfoot <johnb@parseccomputer.com> Date: Tue, May 4, 2010 at 12:19 PM Subject: RE: [premier_partners] Adding a module to 4.40 To: premier_partners@yahoogroups.com Greg and David, Thanks for the response. The product was installed at the server and the attempt to add the module was done at the server as well. It does prompt for new or existing. I choose existing and it then informs me that I am installing over an existing installation and please choose another folder. Sage suggested renaming the uninstall info and doing a reinstall. I may have found why I am having the issue and David did not. This customer has their data on a network storage device which is not recommended. I get a warning message just before I get the choose another folder message. This must mess up the program logic at that point. I also found something that works for me. On the install screen, I went to Documentation, instead of install, just to check the instructions. When I came back to Installation, after I chose Maintain, it took me directly to the Add, Re-Install, De-install screen. Using that route, it never checked for the network drive. Thanks, John Broadfoot

Well I am going to try it. I'll let you know how it goes. WTF... not much else I can. Robert managed to find the article that you were referring to but it assumed the ""SAME"" location.

Looks like my refresh on Socialcast was slow. Anyway I looked at this article and it doesn;t seem to be working for me since MAS I have never had MAS200 in the new location.

Well the parallel migration actually worked pretty well. It looks like it brought everything over. The MAS200 service started right up and modules did not need any conversion. 1 Install new MAS200 at new location (unfortunatelu you do need to re-register in order to reinstall) 2. Start the ""Migrate"" program and point to the old 4.4 system and migrate system and all desired companies.

And we wonder why people are attracted to cloud computing ...

Sorry for the late response. Trying to get my feet under the socialcast thing. Honestly, I still like the idea of the resellers group on Yahoo, but then at one time I loved the System 36 hardware before moving to DOS. Oh well...... This reinstall issue was brought to Sage's attention back in the Beta testing day. I wrote several paragraphs about it because it made Beta testing difficult. I never received a satisfactory response (but come to think about it, I don't think they ever responded at all). Looks like you found a work around.