Migrating Progression to a new server???

[toomes1]

Hi,

I'm looking for the document from exact that describes in detail how to move a macola install from one box to another. In my instance I'm moving progression 7.6 running on a win 2000 SQL server (SQL 2000), to a win 2k3 server running sql 2000 as well. Also I was wondering if orpan users could be a problem and if sp_help_revlogin is the appropriate way to deal with it in this instance.

 

[toomes1]

Also if anyone has any advice or knows of any bumps in the road I should be aware of that would be great.

 

[TardisInc]

It's a long process to explain, but there are a LOT of caveats to moving the server, depending on how you're doing it. I've move 6 Macolas in the past year. If you want some help, and if it's worth money, you're welcome to contract with me. Results are guaranteed; no results - you don't owe a nickle.

Whatever you do, I would put all of your Macola CDs onto a USB drive and use that. Just make sure all of the directory names you use are DOS compliant (8.3). Makes the installation go a LOT faster.

Lastly, if you want to practice moving the server, put Virtual PC on your computer, then you can install, and if it doesn't work, just copy back the saved VHD and VMC files to get right back to where you started. I install, save a version, install, save a version, etc. Works great (less filling).

 

[toomes1]

Well, I have to SQL database moved over and installed a fresh install of Progression 7.6. I had to run some scripts to get rid of supervisor_sql and recreate it so I could logon and sych up with the database.

The problems I'm having now are, I need to update to 76100a and I don't have the exe to do so.
I'm not sure if i need to install the flexibility suite on the server, what is the purpose of the F9 installation and last but not least when I rn an install on a client machine i get an access denied error New MDAC 2.5 1 nad install fails.

 

[kscheeler]

What version of Macola are you on. I thought you were already running 7.6. I would skip 100a and go to 7.6.200 then to 300 and then to spa.

As for MDAC. I'm a fan of downloading and installing 2.8 from Microsoft's web site. I've found it to solve alot of issues. Are you logging in as an Administrator of the client? Verify the permissions on the hkey_local_machine\software\odbc folder as well as the macola folder and btrieve folder (if it's present)

Another possibility is from the infomine below:

Question:

When trying to install the progression client I get
"Component transfer error: New MDAC 2.51 – Catastrophic Failure"
How can I correct this?

Answer:

1. Check Drive mapping.
2. Shut down all running apps, including anti-virus. Verify Temp directory is empty.
3. Run the standalone MDAC install. This file is mdac_t25.exe. It is on the CD \pwe\msredist\ OR located in the X:\Macsql\Install\msredist\ directory.
4. Reinstall the client by deleting the Macola7.ini in the windows directory, deleting the Macola shared in C:\Program Files\common files\ and deleting the Macola Key in the registry under HKEY_LOCAL_MACHINE\Software. Then install the client by browsing to the Macsql directory and double-clicking on the PWE.EXE.
5. If this is a Native Windows 2000 environment using Active Directory and Disk Quotas, verfiy that the user's quota on the server is not full or almost full. If necessary, clear space on the user's quota or increase the user's quota to allow for the installation.
6. Verify that you are logged in as the adminstrator. A user with administrative rights may not have sufficient permissions to install these components to the workstation.
7. On Windows 2000 and 2003 servers it is imperative that you are logged into the workstation as administrator. The install routine tries to access disk space and resources on the server, so if the user does not have access to the server, the install will fail with errors such as access is denied or not enough diskspace.



Kevin Scheeler

 

[NEmacGuy]

This was a my reply to a similar question:
In your case watch for "YOUR SQL SERVER NAME" and the
Supervisor script.

---------------------------------------------------
The first thing I would check is the mapped drive issue; if that is not the issue then I would check the following

macsql.cfg - what are they server names
[SQL_INFO]
Companies_Installed=2
[Company_000]
Name=Macola Electronics
Server="YOUR SQL SERVER NAME"
Database=Demodata
LOCKDB=MsllockDB
FRL=False
[Company_001]
Name="YOUR DATA COMPANY NAME"
Server="YOUR SQL SERVER NAME"
Database=DATA_01
Lockdb=MSLLockDB
FRL=False
[ENGLISH]
Server="YOUR SQL SERVER NAME"
Database=SCREENS
LockDB=msllockdb



pwe.tam
[DbInfo]
Server="YOUR SQL SERVER NAME"
Database=PWE

macola7.cfg
Last-Ver-Inst=7.6.100
PRIOR-VER-INST=7.6.100
Last-Instmac-inst=7.6.100

prosql7.cfg
If you changed the driver letter you used for mapping macola you will have to change this file.

If after all this then I would contact my support person (Reseller or Exact) and ask about dropping the Supervisor user in SQL and recreating it. Then run the SQL security sink from visual menu builder. There is a tech note on how to do this.

One other one got me once check your registration file, and make sure you used a SQL and not a btrieve reg disk.

 

[wwwedward]

Component transfer error: New MDAC 2.51 – Catastrophic Failure"


I have had some success after obtaining this error by starting the progression workflow explorer and this causes a series of installs to take place that corrected my issues on workstations. This was on 7.6.2.500 ..sql..

 

[toomes1]

Well the insatll problem is fixed, now when i run anything I get MSL File Load failed, error during file load for table [NT4].[data_100].dbo[compfile_sql] in path M:\macsql\msl
Detail error: the system can not find the path specified.
Pleae verify that the MSL file exists and is valid.

 

[dgillz]

Look at the prosql7.cfg file, in the 4th line, and make sure that is the proper path.

Also, silly question, but the workstation does have MS SQL server client connectivity installed correct?

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

http://www.gainfocus.biz

 

[toomes1]

Well, I got the new server working and the clients working but it's running soooo slow, it's strange because it's fast when I have the old server on and gets slow when I disconnect. What I did was I copied the Macsql dir over from the old machine to the new after renaming macsql on the new to macsql.old I did this because of custom apps I needed to bring over, I think there is something still looking for that old machine. Does anyone think it would be wise to rename the new machine to the old machines name and ofcourse update the appropriate config files at the same time, I think this would give me all my custom apps and hopefully anything in macsql looking for the old machine name wouldnt have to look to far.

 

[kscheeler]

You probably have flexibility. The registry entries that flexibility creates on the local clients has references back to the old server. When you take it off line, it has to search for the files needed.

One option (long way) is to search the registry and change the references from the old server to the new server.

Another option is to remove Macola from the workstations and reinstall it from the new server. To remove Macola from a workstation in order to reinstall it I do the following:

* Delete the folder c:\program files\common files\macola shared
* Delete the file c:\windows\macola7.ini
* Delete the registry key hkey_local_machine\software\macola
* Reboot

After it comes back up, install Macola and then flexibility. It should reset everthing to the new server.

Kevin Scheeler

 

[toomes1]

Thanks that worked perfect and everything is up and running =8^)