Macola ES new server transition

[JDMiller]

We are upgrading our server and need to reload Macola ES and transfer existing data. Macola ES came with a new business unit we acquired. I am not familiar with the install. We run Macola Progression in our existing business.

Is there anything unexpected I should be aware of when I install SQL server and Macola ES on the new server?

I have the "Installing Macola ES in a Network Environment" instructions from the Macola website. I also have the "Welcome to Macola ES" manual.

 

[abaldwin]

To quote

I have the "Installing Macola ES in a Network Environment" instructions from the Macola website. I also have the "Welcome to Macola ES" manual.

I would suggest that you also get a Macola VAR.

Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[JDMiller]

Incredibly helpful Andy. Wow, hadn't even thought of that.

This would be sarcasm here.

 

[abaldwin]

Mine was supposed to be somewhat sarcastic. ES implementations are bad enough with a VAR. I can only imagine how bad it would be without support.

What is your intention with the data. Will you continue to use it or are you going to try and suck out the data to integrate to your current Progression (i.e. an upgrade in reverse?)



Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[JDMiller]

No, Macola Progression is not part of the server upgrade.

Macola ES exists on a current server. This server is separate from our Macola Progression server. We are replacing the Macola ES server. Hence, we need to load SQL and Macola ES on the new server. We will then backup/copy the database from the existing server and restore it on the new server.

I have never installed Macola ES and I was looking for advice on any unexpected issues I may encounter.

I am quite familiar with Macola Progression installs but that is irrelevant for this project.

This business unit is separate server from my other business units on Macola Progression.

 

[dgillz]

You would not be talking about Denver Biomedical would you?

To update ES on a server you need 2 files:

ProductUpdater_T6_AE.exe
License.elc

Run the product updater from the server - make sure you have fast internet access - and follow the instructions. ES does not ship or update via a CD, it is all downloads. You will need a valid username and password to the Exact customer portal to do this.

Be sure that you update to the same batch that the existing install of ES is set to. This is where a VAR's help would come in handy.

If you are running ES and eSynergy, you need to also run another product updater, which is ProductUpdater_T8_AE.exe if I recall. Perhaps one of the eSynergy gurus will chime in here to confirm this.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

"making predictions is tough, especially about the future" - Yogi Berra

 

[canimp]

Don hit it on the nail again, yes the e-Synergy updater is ProductUpdater_T8_AE.exe, located in the c:\synergy\bin directory on the IIS box of a default installation.

ALWAYS update ES, Globe first before updating e-Synergy.

 

[pronet74]

Then once that is done, go into the enterprise manager on the existing server, back up the database. Goto the new server and create a new company. Then do a restore in the new enterprise manager.

The reason why you should create a new company on the new server is that I had a problem restore to a new server. The database would restore but screens would give me weird errors while opening. Creating a new company creates the correct msllockdb database.

 

[JDMiller]

This will all be very helpful. Thanks to all of you.

The msllock.db is exactly the type of thing that I figured would come up to bite me.

No DG I am not talking about Denver Biomedical.

Thanks again. If anyone thinks of anything else, please post it.