🚀 go-pugleaf

Hi,

just completed the install of CS4 Design Premium. Same experience here. The folder with the Bridge startup scripts is empty. No link in the Favorites anel to Version Cue.

There is a tech note that addresses this:
 <http://kb.adobe.com/selfservice/viewContent.do?externalId=kb407015&sliceId=1>

Basically - don't use Bridge and Drive until the patch is released. Best to use the mounted VC server directly in the OS and applications.

From the tech note...

As we were preparing to ship Creative Suite 4, we discovered serious issues that need to be addressed so that customers will have an optimal experience using Version Cue CS4. Because of these issues, we temporarily disabled access to Version Cue from Adobe Bridge CS4. In mid-November, we plan to release a patch for Version Cue CS4 that will fix those issues and re-enable Version Cue CS4 in Bridge.

We recommend evaluating and implementing Version Cue in production workflows when the patch becomes available. However, you can set up a managed workflow today using the new Adobe Drive. If you will be using Adobe Drive with Version Cue in a production workflow, be aware of some issues you may encounter, which are detailed on our Version Cue Support Center at www.adobe.com/support/versioncue.

Note: To check availability of the patch in mid November, please visit the Version Cue Support Center at www.adobe.com/support/versioncue or run Adobe Update Manager (choose Help > Updates in any CS4 application).

      Best to use the mounted VC server directly in the OS and applications.




What must I do (Windows)?

How can I mount VC server in Windows? I can only open VC server as web folder in Internet Explorer but it's wrong way.

Hi denis-gr,

- open the context menu on the desktop choose: Adobe Drive CS4...>Connect To... (You need to restart after installation to load up all neccessary files)
- Adobe Drive comes up
- Click on the VC logo in left lower corner
- Choose your VC server and double click it
- enter User credentials
- connect

The VC Server will appear as mounted network volume.

Adobe Drive is the new application to connect to the VC Server. There is no other way I can think of.

Best Arne

Aaa, Adobe Drive!
I though there is another standard system way to mount VC as WebDav server!

Thank you!

Whatever you do, do NOT enable Version Cue through the registry or anywhere else. The last 2 days, I have lost hours of work because of the bugs that exist currently.

It occured like this:

Create a new Flash file on the VC server. No matter how many times you save it, it will not PHYSICALLY save on the networked drive until you CHECK-IN. If you don't check it in, eventually, when you try to save it, your system will not respond. So much so that all your programs will not even respond to force quits. So, the logical thing is to reboot your computer, but it won't happen most likely, causing you to hard reboot. This is the break in the chain. When you reboot you will find that your latest SWF is saved but not your fla, and you have lost all of your work since you last (if ever) checked it in.

They disabled it for a reason it seems. But they really SHOULD have made it more clear that you SHOULD NOT use it. Lesson learned.

Hi Kevin,
you now use a network volume and only check in versions will keep versions.
I'm not sure what exactly you did, even though I read your post, but if you just save a file and and open it again, it is possible to check it in then. Should be checked in initially before....
You may check it in via context menu on the project in your filesystem "MyComputer > name of version Cue Server > name of project".
You do not need Bridge for that.

Manipulating via RegEdit is a bad idea, but this hack will have no impact on the way Drive behaves in your filesystem.
You should wait for a patch that will be delivered very soon, to get VC back in Bridge.
 <http://kb.adobe.com/selfservice/viewContent.do?externalId=kb407015&sliceId=1>

Have in mind that it is a very good workflow to create a file, check it in and than start editing.

Maybe this will help to understand the idea behind Drive:
 <http://help.adobe.com/en_US/Bridge/3.0/WS03F94DCA-00B1-4837-BC8E-97B8FD4D3235.html>

thanks

Markus

Another hint:

 <http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405502&sliceId=2>

is about Flash CS4 and Version Cue.

Markus

Jasker, thanks for the links. I have read through each of these at least 10 times trying to find out why Version Cue wasn't enabled by default. My complaint is that the technote explaining WHY it's not enabled by default and why it isn't a good idea to enable it yourself, didn't appear until after people are having serious issues.

I understand it's not the greatest idea to tell everyone you're shipping a not quite polished product, but at the same time, people need to be made aware so we can avoid these kinds of things. I know not everyone used Version Cue in CS3, but for those who did, it's absence from CS4 was especially curious, and the people who wanted it found a way to enable it.

My biggest concern/question was this though: If Drive is connecting to a PHYSICAL networked place in my studio, why is it not SAVING my file regardless of whether or not it's checked in? Even if I create a file, locally or actually inside of the server, it is considered checked out initially. Well, if I attempt to check in every time I save it, there will be 50 versions as much as I save (and I know I can speak for several others here). So, unless I wait to check it in until I am finished, (which is normally several hours later), as the workflow dictates, it is never actually saved.

This tech note:
 <http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405502&sliceId=2>

doesn't really apply here because I am not quitting Flash and the file is saved (well, I am saving via Ctrl-S, but that doesn't seem to actually be saving as it turns out.) Either way, I see why it wasn't enabled by default because of the bugs that exist, and I will not be using it until the patch is released. That said, once the patch IS released and fixes all the things I have noticed (such as labels and ratings not being transferred or even available once on the server, Bridge not being able to see networked drives that haven't been mapped through Drive, and things involving the entire discussion above) I will probably use it again.

Thanks Jasker for your time and attention. It is much appreciated.

Hi Kevin,
you're quite right with some of your statements.

I still try to figure out what happend in your case.
If you have initially checked in a file and saved it, the file should be available on the same machine after a reboot, since it is cached locally. That's what happend to your .swf files. They should be in state of "new file" (< .swf) or Checked out By me" (< the .fla).

Just a few more questions:

- did you enable Version Cue in Flash? In that case the first save must bring up a check in comment window in Flash, if you choose a mounted Version Cue server as target.
If not, Flash behaves like any third party application and versions can only be checked in via context menu in your local file system.

- could it be that the hang of your system was initiated by something totally else? Like Windows or so?

- was the server up and running all time?

We tried to reproduce your case and had sort of similar experiences, but I'm pretty sure that your workflow differs from ours.

Would you like to be contacted by me directly and maybe we will be able to find the issue here and shade some more light onto it?

How about that?

I'll be back tomorrow and see what you'll say.

have a nice dy

Markus

Hey Markus, to answer your questions:

- The system has never frozen to such a point until Version Cue was being used for the entire project management. The same thing has happened to co-workers Since I have disabled it, it has not happened again.

- The server was running at all times. I waited about 20 minutes or so after my system was freezing (this was still happening), and then I turned the server off. Nothing. I disconnected the shared drive through Adobe Drive. Still nothing.

I was creating a new file INSIDE of Flash directly on the Windows networked drive. I know this normally a bad idea for a workflow, but since Bridge does not recognize Windows networked places, we saw this as the solution. This drive was also connected through Adobe Drive, thus enabling Version Cue management. So, after the new file was created, it displayed "Checked Out" in Bridge. After hours of working and saving repeatedly, I would try to save at some point, and then it would crash, although nothing was really being saved. It would not save in Version Cue or on that networked drive. After I was forced to hard reboot by hitting the power button, I checked Version Cue and the networked drive Windows Explorer file directories. Some files were on the Version Cue Server that were not on the networked drive (even though, technically, they were the same thing). And the files that were there, had a 'date modified' property of the time when the file was created.

The whole point is really, that we shouldn't have enabled it. If we had known about Version Cue not being stable, we would have certainly avoided it. And in all of the time I spent researching before enabling it, I never once came across that tech note. That is where all these issues are coming from. But even more than that, I feel Adobe should have stepped up and told people from the get go WHY it wasn't enabled by default. That's all.

As far as calling or getting to the bottom of the issue, I don't feel any need to, although the offer is more than generous. Thank you. The one thing you could do is remind me of the string values of the 3 default DisabledScripts registry entries. I'm pretty sure of they were GallerySheet, VersionCue, and VersionCueSDKLoader. But I am not 100% sure, and I would like to get CS4 back to it's normal, un-modified state. That would help a ton.

Thank you again for your time and effort put into solving this. It is very much appreciated.

We installed a fresh version of CS4 and anyone who disabled those scripts and needs to know their registry values to RESTORE them, here they are.

HKEY_CURRENT_USER>Software>Adobe>Bridge CS4>Preferences>DisabledScripts

GallerySheet
VersionCue
VersionCueSDKLoader

I'm not aware of any problems caused by restoring these values. I'm sure it's better than what happened by removing them.

I have this problem, but I am on a mac so I don't understand all the registry hacks above. With bridge running and Version Cue, starting Adobe Drive just hangs the system hard when u try and connect. I have the latest updates for CS4 as of today. Is the fix just to wait? thx!!!
coocoo

It's not a problem of CS4 but a problem of network. Disable firewall, antivirus, proxy server usage in browser etc.

Hi forum hound,
just run the AdobeUpdateManager, download the "All CS4 Services Update" (and the server update too, if you have one on that machine!) , restart your Mac!!
After restart of your Mac start Bridge, go to preferences and there to Startup Scripts, enable the "Adobe Version Cue CS4" startup script.
restart Bridge.
Now Version Cue will be enabled in Bridge and you can browse, check in and out, view versions etc.

thanks
Markus

BTW, this works on WIN too!!!
The update will bring back the startup scripts that was disabled in CS4.0

Markus