Upgrading 6.1 to 7.0.2 Issues - Windows 2003 Server SP-1

Forum|Forum|18 years ago
July 16, 2007
6 replies
702 views

Last night I attempted to upgrade our Standard version CFMX6.1 to MX7.0.2 on our Windows Server 2003, SP-1, and I encountered errors consistent with those described in TechNote 228c3aaa -- http://kb.adobe.com/selfservice/viewContent.do?externalId=228c3aaa&sliceId=1. So far, the first 3 solutions suggested by the TechNote didn't work. During on installation attempt, I didn't have option to install MX7 as "Server Configuration" because it was grayed out), so I uninstalled MX7 (wanting to just get back to a working version of 6.1). Well, that really screwed things up. My website could no longer process .cfm files, and the CFIDE directory was complete gone.

So, I installed MX7 twice more...the first time with 4 errors, the second with 2. I then used the Web Server Configuration Tool (the one included in MX7) and now my sites seem to be working, but as 6.1...which is better than not at all.

Here are my questions:
1) Does the 4th solution (copying the CFusionMX7 directory from another working server) really have a chance at working correctly?
2) If it does, will MX7 know the first time I open the admin page that this is a new upgrade, and thus walk me through the Migration Wizard (which I really want)?
3) What do I need to do to get my websites to run with the MX7 extensions, rather than the MX61 like they are now --assuming I get questions 1 and 2 answered?

I know this is a lot to read. Thanks for taking time to consider helping me out.

This topic has been closed for replies.

A

Anonymous

I haven't made the upgrade yet, and now I am considering upgrading to MX8. Should I expect to encounter the same problem going to MX8, or is there a chance this issue was resolved?

A

Anonymous

The ODBC's may have been working, but I kept getting some kind of "mapping" issue when just trying to go to non-db-calling pages. The admin pages seemed to come up ok, though.

I'd try the uninstall, delete, and reinstall option, but I am afraid I'd be right back where I was before the start of all this where CF wouldn't install properly.

A

Anonymous

If ODBC is working, my first choice would be to simply manually recreate the ODBC datasources in cfmx7. If you have 100s of DSNs, then I guess you could uninstall, delete cfmx7 dirs and reinstall.

A

Anonymous

Hi Ken,
I just attempted the upgrade again. I got further than last time, but still can't switch things over to CF7 yet because the migration wizard didn't seem to do its job. I had set the adminConfig.xml as we talked about above, but it still didn't import any of the old ODBC or other settings from the CFMX6 installation. Instead, it had all the configurations from the similar server that I copied the CFusionMX7 directory from. Since that server is just a backup server for just one of my websites, it is not configured with everything I need on my production server.

I even tried to install CFMX7 from the .exe again, thinking that maybe since all the directories/files are there, it would install properly and do the migration properly. But, it sees that MX7 is already there and won't let me install it over top.

Any thoughts? Is there some place in the CFusionMX7 directory I can flush out the backup server configurations?

A

Anonymous

Hi Ken,
Thanks for the response. Couple follow up questions:

As far as the migration/configuration wizard goes, here is what I am looking to migrate:
- Data Sources
- custom tags
- email server setup
- missing template settings
- Java and JVM -- Server Settings

I think that's it. So, given that, what would the below adminConfig.xml need to look like? Again, I am upgrading from MX6.1 to MX7.0.2. Let me take a stab at it:

<setupconfig>
<runsetupwizard>true</runsetupwizard>
<runmigrationwizard>false</runmigrationwizard>
<runmxmigrationwizard>true</runmxmigrationwizard>
<migratecf5>false</migratecf5>
<migratecf6>true</migratecf6>
<setupoptions>
<sampleapps>false</sampleapps>
<odbc>true</odbc>
<enablerds>false</enablerds>
</setupoptions>
</setupconfig>

My second question might be irrelevant, but I am curious. The way it is setup now, I can't get into the CF Admin page (since the uninstall of CFMX7 removed it), but I know I am running 6.1 because I tried to hit a test page with a <CFDOCUMENT> tag, and CF said it didn't know what that tag was. But, when I go into IIS and look a the Application Configuration for .cfm extensions, it has a mapping to C:\CFusionMX7\runtime\lib\wsconfig\jrun_iis6.dll. Any ideas?

Thanks so much for your help.
-tom

A

Anonymous

Your adminconfig looks good, except you should probably enable RDS during configuration. Disable it after the config is done if you want to.

Remember the config wizard will not move or copy files. So customtags etc will not get moved under cfusionmx7 if they live under the cfmx6 program root now. Only pathing info etc. is copied in. JVM settings from CFMX6 will not make sense under cfmx7 probably. Update them as needed for settings that do need update, like classpath additions, etc.

2) Dunno

A

Anonymous

Sorry for all the problems with your installation. There is free installation support for licensed CFMX7 owners at www.adobe.com/support/coldfusion. You may want to use it.

However:
1) Solution 4 definitely can work. CFMX is a java application with only installation information entered into the windows registry. All files and settings are in cfusionmx7 and its sub-folders (except CFIDE which may be under a separate webroot.)
2) The configuration wizard will not open automatically if it has already been run on the prior machine. Open cfusionmx7\lib\adminconfig.xml and update to have the config wizard run. Update the migrationwizard, setupwizard and others to true as needed.
3) Run wsconfig from cfmx7 and setup the connector from cfmx7. What connector is currently running and is it really from cfmx6.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded