🚀 go-pugleaf

Hi Macophil,
please try to follow these steps:
- first make sure you have updated the server to version 4.0.1 via AdobeUpdateManger (or via downloads from <http://www.adobe.com/downloads/updates/> > popUp > Version Cue - Macintosh)

- turn off both server CS3 and CS4
- go to
- /Library/Application Support/Adobe/Adobe Version Cue CS4
- navigate to the folder named "cs3-migration-plugin"
- enter it
- copy the complete folder inside named "com.adobe.versioncue.migration_3.1.2"
- paste it into /Library/Application Support/Adobe/Adobe Version Cue CS3/plugins
- now start the servers again
- go to the CS4 administration page > "Advanced" tab
- on that page there should be an entry "Import Version Cue CS3 Data"
- click it
- the login for the CS3 server now should be available.
- after login you can select projects and import them.

If that will still not work, please provide some data here:
- MAC OS version (Tiger / Leo and version of the system...10.4.11/10.5.5)
-the exact steps you did to migrate.

Thanks and regards

Markus

Hi Markus,

thank you for your help, but it still not work. I followed exact your steps.
System Mac OS X Leopard 10.5.5. I remember that I had a problem with the CS3 Server (before I tried this all), I coudn't stop the Server, after several minutes I shut down the server.
But after that it works fine again. Otherwise I have no idea why the CS3 Server don't detect the new plugin.

Maco

Hi Maco,
mmh, sounds strange.
You sure you follow my steps?
The CS3 server will not show the plug in, only the CS4 server will at the advanced tab.

If you have problems to shut down a server just use Activity Monitor and force quit "mysql" runned by "nobody" should work.

Markus

I think I'm having the same problem as Maco� I copy the plugin folder from the Version Cue CS4 folder into CS3's plugins folder while both servers are off, then turn them back on and try to access the migration feature. In my case, I don't get an error indicating that the plugin isn't found, but I get an error indicating that the CS3 server is not running.

OSX 10.5.5 here.

�Phillip

I'm having the same issue. I was at VC CS2, followed the instructions to upgrade to VC CS3 which was flawless, now want to go to VC CS4, but I'm getting the "CS3 server is not running" error even though it clearly is. I've tried this a few times with no luck. Is there a resolution to this?

Mac OSX server 10.4.11 (ppc)
VC CS3 server version 3.1.0
VC CS4 server version 4.0.1

I was able to get mine going by doing a couple things ,most of which probably have almost nothing to do with the issue.

I wanted to add a new user, so I adjusted the workgroup size for VC CS4 in System Prefs. I used a Mac admin account to log into my VC CS4 panel as a VC admin. I then created a new VC CS4 user account for one of the other users on this computer. I gave them a group and sorted out the sort of permissions I wanted them to have, then logged into the other user's account on the Mac and launched Adobe Drive to connect.

I set up a few more preferences and logged into the VC CS4 panel with this other user's account to make sure everything looked alright. For some reason at this point I decided to launch VC CS3 from this other users account, and I set it to the same workgroup size as my VC CS4 server.

When I logged back into my Mac admin account and visited the VC CS4 panel, the VC CS3 migration option worked fine. I've migrated all my projects and I haven't noticed any major problems.

I had opened a support case, and when all this happened I updated my case with this new information, and they suggested that I had a permissions issue initially. However, I think they also thought this other user account was an admin- it isn't.

So basically, I set up a new VC CS4 account fully, then logged into it using the other Mac user (not admin) account. From this other account, I connected to my VC CS4 server and launched the VC CS3 server. When I logged back into my account, the migration worked fine.

I am sure a lot of those steps are unnecessary, and there's a good chance that none of it had anything to do with resolving my issue; but it worked for me and I hope it works for someone else.