Adobe Drive & Version Que

Thanks Laurel for your info! I have so much to do, that a direct link to the solution would have been helpful. I have no interest in reading trough the whole Adobe site, who would want that for the next thousand years.
I also have absolutelly no interest in having any provider of any service that wants to control or maintain my data. It was just great when I was in control of my data and I was defining who has access to my data, I guess you could rightfully so assume that there is a lack of trust toward a company that just randomly disposes of products that worked well for people like me.
I probably have to go through a lot a hassle to get my data back and I have purchased Version 5 a long time ago and never until yeasterday installed it just because of Version Que. Stupid of me to not resist the temptation to want to get something for my cash.
I say to Adobe which was for many years one of my favorite companies, keep disappointing customers like you do, and soon nobody is supporting you any longer.
If you have a solution to the problem, please let me know. I have no interest anymore to spend more then a half hour to solve this problem, otherwise I will have to find another solution without Adobe.
Thanks again for your interest in helping a bad situation, it is bad enough that one can't even get customer support anymore and no warning during the installation that you mess up all my data, well done Adobe. I hope you get my distinct sense of frustration, trying to stay "politically correct" which in this case is rather hard to do.

Here is the link: http://www.adobe.com/products/versioncue/downloads/index.html
A search for 'Adobe Drive' returned this as 3rd in the list.
Adobe Drive 2 supports connectivity to Version Cue server CS4 (not earlier versions).

Similar Messages

Versioning in Adobe Drive 3.0

Hello,
Have some problems with versioning in Adobe Drive 3.0
'View Versions' in Bridge display icon only for current version. 'Open' version returns corrupted file.
The same code works fine with Adobe Drive 2.6
Did not found any differences for version handling in sdk docs 3.0
Any suggestions?

Hi
Could you please share more detail information?
Which connector are you using? the built-in ADEP, CMIS connector or a custom connector?
What is the icon for the current version? a file system icon representing those files with the same file extension or a bitmap thumbnail? how about other versions?
What does you mean "'Open' version returns corrupted file"? you openned the current version or the previous version? Did the application openning the version crash or you could still open the version, however the file content is incomplete?
for your information, We never released Adobe Drive 2.6, only 2.0, 2.1, 3.0.
Furthermore, you can create a Environment variable named "AdobeDriveLogLevel" and set its value to "DEBUG", reproduce this issue and post the logs under <userdata>\Adobe\Adobe Drive CS5\logs and \Adobe\CS5ServiceManager\logs here or send them to [email protected]
Thanks

I confirm that the Canoscan driver versions are indeed by Canon and not Adobe. Any Solution pl.?

I confirm that the Canoscan driver versions referred to, by me are indeed from Canon and not Adobe. Solution to
problem for images rotation during scanning itself is good and sincerely appreciated. Thanks for the same. My other problems remain. Any solutions please?

Please keep the discussion in your original topic http://forums.adobe.com/thread/1328718

We are using CS 5.5. If I update to OS 10.9 can I download the latest version of Adobe Drive and have it work with CS 5.5?

We are using CS 5.5. If I update to OS 10.9 can I download the latest version of Adobe Drive and have it work with CS 5.5?

For older Macs that aren't supported in Firefox 4.0, try TenFourFox for PowerPC's running Mac 10.4.11 & 10.5.8 . <br />
http://www.floodgap.com/software/tenfourfox/
Or you can revert to 3.6.16. <br />
http://www.mozilla.com/en-US/firefox/all-older.html

I am running Photoshop CC 2014 on Windows 8.1 with an AMD quad core processor and AMD E1-2100 APU with AMD Radeon HD 8210 Graphics Card. I have installed the latest driver version 13.152.0.0. When I activate puppet warp, the mesh appears over the image an

I am running Photoshop CC 2014 on Windows 8.1 with an AMD quad core processor and AMD E1-2100 APU with AMD Radeon HD 8210 Graphics Card. I have installed the latest driver version 13.152.0.0. When I activate puppet warp, the mesh appears over the image and I can place the first pin. However, when I go to add the second pin, Photoshop crashes. I have tried with on a new, blank file, with just a few lines on it, but, as soon as I place the first pin, the image disappears, and then, as soon as I click anywhere else in the image, Photoshop crashes. I have followed all the online advice about settings under the Preferences/Performance interface, but nothing fixes the problem. Can anyone please help?

BOILERPLATE TEXT:
If you give complete and detailed information about your setup and the issue at hand, such as your platform (Mac or Win), exact versions of your OS, of Photoshop and of Bridge, machine specs, such as total installed RAM, scratch file HDs, video card specs, what troubleshooting steps you have taken so far, what error message(s) you receive, if having issues opening raw files also the exact camera make and model that generated them, etc., someone may be able to help you.
A screen shot could be very helpful too.
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks!

Under Windows 8.1, Adobe Drive crashes on File- Check In... when invoked from an Adobe creative application.

I am testing my drive connector on Windows 8.1 (64-bit) using Adobe Drive (5.0.2) with Photoshop CC (15.1.0.148) and Bridge CC (6.1.0.116), and I find that if I use File->Check In... from the creative apps (I checked InDesign too), the application crashes inside of AdobeDriveUI.dll. The crash happens as it attempts to display the dialog that solicits a Check In comment.
I have tried using both the 32-bit and the 64-bit version of Adobe Drive, but both exhibit the same issue. I am quite certain that my connector is not involved, as the crash happens in native code that collects the version comment *before* my ICheckInHandler instance gets called.
I am interested in any insight or work-arounds that might exist. Thanks for any help!
Here are details in the Windows Event Viewer's XML format:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-10-02T15:36:38.000000000Z" />
<EventRecordID>5226</EventRecordID>
<Channel>Application</Channel>
<Computer>Win8VM</Computer>
<Security />
</System>
- <EventData>
<Data>Photoshop.exe</Data>
<Data>15.1.0.148</Data>
<Data>53d97a8f</Data>
<Data>AdobeDriveUI.dll</Data>
<Data>5.0.2.16</Data>
<Data>532b518c</Data>
<Data>c0000005</Data>
<Data>0000000000008ca8</Data>
<Data>dec</Data>
<Data>01cfde5650e17527</Data>
<Data>C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe</Data>
<Data>C:\Program Files\Common Files\Adobe\Adobe Drive 4\Client\AdobeDriveUI.dll</Data>
<Data>e5865b18-4a49-11e4-8271-000c29022208</Data>
<Data />
<Data />
</EventData>
</Event>

Thank you for the Replay,
I performed steps provided by you , but it did not help.
on other hand, i have collected some more data regarding
this issue.
1. went to SAFE Mode and tried to run the application from USB
2. got Exception "The instruction at 0x00407038 referenced memory at 0x00000078. The memory could not be read"
some more info on setup :
we have a micro controller on board, some part of memory (present on board) is used to keep application and server. we can open this memory via USB connection to PC. then we can see all files present at this memory on PC (behaves like externally connected
USB Drive) .
When we start this application . it will start the server . server will send 'request file' to controller soft. (this part is working fine), and controller will send back response , as soon as response file(RSP.txt) will appear in USB drive it will get corrupted
.(here RSP.txt file is present in controller USB decided memory but to open this we are using PC RAM). crashing of RSP.txt file will crash whole application. This RSP File is of FAT Type.
i have copied application in another external drive and tried to RUN application. it will not crash . but USB can not receive the "RSP.txt" (as it is not in communication with controller soft). and problem is in response file.
BR,
sanjyot

Adobe Drive 5 Install Failed on Mac

When installing Adobe Drive 5 on a Mac and get Installation Failed with the fallowing error Summary:
Exit Code: 7
Please see specific errors below for troubleshooting. For example, ERROR:
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 2 error(s)
ERROR:
Adobe Drive 5 is used together with these Adobe products: Photoshop, InDesign, InCopy, Illustrator, and Adobe Bridge.
You must have previously installed one of these CS6 or CC products in order to install Adobe Drive 5.
For localized versions of this error message go here:
http://www.adobe.com/go/adobedrive5_install_faq
ERROR: System check returned with error : 6
My system info:
OS X 10.9.5
3.66 Ghz Quad- Core Intel
8GB Memory
1.2 TB free space out of 1.3 TB HD
Currently Installed and up to date:
Creative Cloud
InDesign CC
Illustrator CC
Photoshop CC
Adobe Air (installed by recommendation of Adobe Phone Support)
Would like to know to get past this error and complete the installation.
Thank you
Adrian :-)

mike.buckhout is right, i had the same issue and had to install Adobe Bridge first.
Greetings
Robert

Adobe Drive not connecting to hello world sample launched via Eclipse

I'm trying to get the hello world sample running with Drive SDK 5. I got:
Adobe Drive 5.0.1
AdobeDriveSDK-5.0.0.398770.zip
latest Java JRE 1.6
Eclipes 4.3.1 (Kepler SR 1)
Windows 7 64bit
I configured the hello world project as described in the getting started guide. I double checked that AD4ServiceManager.exe is not running. After starting the project in Eclipse and waiting about 15 seconds, all bundles are active:
osgi> ss
Framework is launched.
id     State       Bundle
0     ACTIVE      org.eclipse.osgi_3.5.0.v20090520
1     ACTIVE      com.adobe.csi.ncomm_2.0.0.28
2     ACTIVE      com.adobe.drive.core_2.0.0.28
3     ACTIVE      org.eclipse.equinox.cm_1.0.100.v20090520-1800
4     ACTIVE      org.eclipse.equinox.preferences_3.2.300.v20090520-1800
5     ACTIVE      org.eclipse.equinox.app_1.2.0.v20090520-1800
6     ACTIVE      com.adobe.drive.biz.filesystem_2.0.0.28
7     ACTIVE      javax.servlet_2.5.0.v200806031605
8     ACTIVE      org.eclipse.equinox.launcher_1.0.200.v20090520
9     ACTIVE      com.adobe.drive.manager.executor_1.0.0.28
10     ACTIVE      com.adobe.drive.connector.cmis_2.0.0.28
11     ACTIVE      com.adobe.drive.ui_2.0.0.28
                 Fragments=27
12     ACTIVE      org.hsqldb_2.2.9
13     ACTIVE      com.adobe.drive.model.synchronization_2.0.0.28
14     ACTIVE      com.adobe.drive.data.persistence.api_2.0.0.28
15     ACTIVE      org.eclipse.equinox.ds_1.1.0.v20090601
16     ACTIVE      org.eclipse.update.configurator_3.3.0.v20090312
17     ACTIVE      org.hibernate_3.2.5
18     ACTIVE      com.adobe.csi.core_2.0.0.28
19     ACTIVE      com.adobe.drive.connector.service_2.0.0.28
20     ACTIVE      com.adobe.drive.model_2.0.0.28
21     ACTIVE      com.adobe.drive.data.provider_2.0.0.28
22     ACTIVE      com.adobe.csi.auth.keystore_2.0.0.28
23     ACTIVE      com.adobe.drive.connector.api_2.0.0.28
24     ACTIVE      com.adobe.drive.data.persistence.hsqldb_2.0.0.28
25     ACTIVE      com.adobe.drive.data.cache_2.0.0.28
26     ACTIVE      org.apache.commons.codec_1.0.0.28
27     RESOLVED    com.adobe.drive.ui.scripting_2.0.0.28
                 Master=11
28     ACTIVE      org.apache.commons.net_1.4.1
29     ACTIVE      sample.helloworld_2.0.0
30     ACTIVE      com.adobe.csi.bootstrap_2.0.0.28
31     ACTIVE      com.adobe.drive.data.manager_2.0.0.28
32     ACTIVE      org.apache.commons.logging_1.0.4
33     ACTIVE      com.adobe.versioncue.nativecomm_4.0.1.28
34     ACTIVE      com.adobe.drive.biz.versioncue.api_2.0.0.28
35     ACTIVE      org.eclipse.equinox.common_3.5.0.v20090520-1800
36     ACTIVE      com.adobe.csi.pipes_2.0.0
37     ACTIVE      com.adobe.drive.data.model_2.0.0.28
38     ACTIVE      com.adobe.drive.data.persistence_2.0.0.28
39     ACTIVE      com.adobe.drive.processinfo_2.0.0.28
40     ACTIVE      com.adobe.drive.connector.cmis.client_2.0.0.28
41     ACTIVE      com.adobe.drive.ncomm.filesystem_2.0.0.28
42     ACTIVE      org.eclipse.equinox.registry_3.4.100.v20090520-1800
43     ACTIVE      org.apache.commons.httpclient_3.1.0
44     ACTIVE      com.adobe.drive.vcdetector_2.0.0
45     ACTIVE      com.adobe.drive.ncomm.versioncue_2.0.0.28
46     ACTIVE      com.adobe.drive.connector.cqdam_4.0.0.28
47     ACTIVE      com.adobe.csi.core.preferences_2.0.0.28
48     ACTIVE      org.eclipse.equinox.util_1.0.100.v20090520-1800
49     ACTIVE      com.adobe.csi.utils_2.0.0.28
50     ACTIVE      com.adobe.drive.biz.automount_2.0.0.28
51     ACTIVE      com.adobe.csi.core.logging_2.0.0.28
52     ACTIVE      com.adobe.drive.manager.interests_2.0.0.28
53     ACTIVE      org.apache.log4j_1.2.15
54     ACTIVE      com.adobe.drive.ifs_2.0.0.28
55     ACTIVE      com.adobe.drive.core.jobs_2.0.0.28
56     ACTIVE      org.eclipse.osgi.services_3.2.0.v20090520-1800
57     ACTIVE      com.adobe.drive.biz.versioncue_2.0.0.28
58     ACTIVE      com.adobe.csi.auth_2.0.0.28
Also, the output of csstat looks fine:
osgi> csstat
Registered connector factories (schema : reference):
cmis : {org.osgi.service.component.ComponentFactory}={component.factory=com.adobe.drive.connector.handlerfactory, component.name=com.adobe.drive.connector.cmis#cmis, service.id=48}
cq : {org.osgi.service.component.ComponentFactory}={component.factory=com.adobe.drive.connector.handlerfactory, component.name=cq#cq, service.id=75}
helloworld : {org.osgi.service.component.ComponentFactory}={component.factory=com.adobe.drive.connector.handlerfactory, component.name=sample.helloworld#helloworld, service.id=70}
Instantiated connector factories (uuid : factory):
Afterwards, I start Adobe Drive (32bit version). The UI hangs with the message "Adobe Drive is starting. Please wait.". From task manager I can see that not just Adobe Drive was started, but also AD4ServiceManager.exe. I guess, this should not happen, because Adobe Drive should discover the one launched via Eclipse.
So what's going wrong here? How does Adobe Drive discover the one launched via Eclipse? What could block discovery?
Here more details in case that helps debugging the problem. MANIFEST.MF:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: HelloWorld Plug-in
Bundle-SymbolicName: sample.helloworld
Bundle-Version: 2.0.0
Bundle-Vendor: Adobe Systems
Adobe-AutoStart: true
Require-Bundle: com.adobe.drive.connector.api,
com.adobe.drive.core,
com.adobe.drive.model,
com.adobe.csi.utils
Service-Component: OSGI-INF/HelloWorldHandlerFactory.xml
build.properties
source.. = src/
output.. = bin/
bin.includes = META-INF/,\
               OSGI-INF/
HelloWorldHandlerFactory.xml:
<?xml version="1.0"?>
     <component name="sample.helloworld#helloworld"
     factory="com.adobe.drive.connector.handlerfactory">
     <implementation class="sample.helloworld.HelloWorldHandlerFactory"/>
</component>
Here the Eclipse run configuration settings:

Wow, this seems to help even though it is still a bit shaky. Here the steps I have to do to get it working:
manually launch 64bit version of AD4ServiceManager.exe with parameter -launchedbydrive
launch Eclipse project and wait till ss shows everything as registered (much faster now)
start 64bit version of Drive -> my adapter doesn't show up
shutdown drive
start 64bit version of Drive again -> my adapter now shows up and works as expected
I find a few things confusing here:
In Eclipse, should I configure the 32bit or 64bit version of AD4ServiceManager as plugin execution environment? Currently, I'm using the 32bit version.
Why isn't the step of manually launching AD4ServiceManager.exe not mentioned in the getting started guide?
I will reboot my machine to see if it is still working or just some special sun radiation making it work currently :-)

How to uninstall Adobe Drive 4 for CS6 for Mac

I have Adobe CC on my system and also Adobe Drive 4.2 from CS6 time for some reason. adobe Drive was not removed when I removed CS6. The Adobe Drive 4.2 run fine at this time.
Now I want to uninstall Adobe Drive 4 from my Mac (running OSX 10.8.4), so I got to /Utiliies/Adobe Installer/Uninstall Adobe 4 and click to run it. The uninstaller won't run
I tried to go to /Library/Application Support/Adpbe/Adobe Drive 4 folder then click Uninstall Adobe Drive 4 from there. It won't run either.
So I'm stuck with Adobe Drive 4 and is there a method or way to remove it from my system manually?
I have tried Adobe Clean Tool but Adobe Drive 4 is not list there.
I tried to reinstall Adobe Drive 4 but it fail due to
Payload: Adobe Drive 4 4.0.0.0 {C3BC3DF1-83AB-4808-A672-474E15340D4B} -----------
ERROR: DW030: Custom Action for payload Adobe Drive 4 4.0.0.0 {C3BC3DF1-83AB-4808-A672-474E15340D4B} returned error. Failing this payload.
The {C3BC3DF1-83AB-4808-A672-474E15340D4B}.app is not available in /Library/APplication Support/Adobe/Uninstall folder
Can any expert here help me get Adobe Drive 4 out of my system MANUALLY please. So that I can reinstall Adobe Drive 5. It fail to install and ask me to remove Adobe Drive 4 first.
Help please

Hi, and sorry that the uninstaller is having this problem there.
We haven't seen this problem internally, and would like to learn more about it so we can provide you with the best workaround.
Have you already tried using Apple's Disk Utility to repair permissions on that disk? If you haven't already, that's worth doing first before trying the steps below.
Here's one possible solution that could be faster than manual steps:
(1) install at least one qualifying CS6 app, if you have already replaced them all with CC versions. I believe not having a qualifying CS6 app is why your re-install of 4.2 failed earlier.
(2) re-install Adobe Drive 4.2
(3) reboot, and then uninstall Adobe Drive 4.2
In step 1, the qualifying CS6 app (Photoshop, Illustrator, InDesign) can be in trial mode, but you shouldn't even need to launch it after installing it.
Did AD 4.2 uninstall successfully in step 3? If not, we'll dig deeper.

Check in dialog with Adobe Drive 4.2 doesn't work

Hi,
we are currently implementing a custom check-in dialog using Adobe Drive 4.2.
The dialog looks like the example given in discussion "Custom check in dialog".
To build the SWF, I use Flash Builder 4.5 with Adobe Flex SDK 4.0.0 (flex_sdk_4.0.0.14159A).
I have created a new Flex Project with Application type "Web" and added a MXML Modul with name "CustomUI" and option "Do not optimize (module can be loaded by multiple applications)".
After compiling the project I extract the "CustomUI.swf" and copy the file in the "resources" folder of my Custom Adobe Drive adapter.
I implement the "IGetCustomCheckInUIHandler", "ICanEnableCustomCheckInUIHandler" and "IGetCustomCheckInUIContextInfoHandler":
"IGetCustomCheckInUIHandler" sets the module url like
response.setModuleURL(Thread.currentThread().getContextClassLoader().getResource("resource s/CustomUI.swf"));
"ICanEnableCustomCheckInUIHandler" enables the custom ui dialog with
response.setCanEnable(true);
"IGetCustomCheckInUIContextInfoHandler" adds some context data like
Map<String, Object> contextInfo = new HashMap<String, Object>();
contextInfo.put("key1", "test1");
response.setContextInfo(contextInfo);
(Also hidding the "IGetCustomCheckInUIContextInfoHandler" in "IRemoteHandlerFactory" doesn't work.)
Right click on an checked out asset in Windows Explorer and click on "Adobe Drive 4/Check in..." does following:
1. "IGetCustomCheckInUIHandler" called
2. "ICanEnableCustomCheckInUIHandler" called
3. "IGetCustomCheckInUIHandler" once more called
4. "IGetCustomCheckInUIContextInfoHandler" called
5. The default check in dialog is shown (with no custom ui extension), the default dialog hangs (OK/Cancel doesn't react on click, the dialog is freezed). Only the close button (X in the right upper corner) works.
How is it possible to provide a custom ui check in dialog?
Thanks

Hi again.
I found where the problem was (at least in my case).
To go to the point: go in the "properties" of your flex project. In the menu, go in "Flex Build Path" and then in "Library Path". Then, the option "Framework linkage" is with the default value in a new flex project.
So here is the trick : with Flex 3 (so Adobe Drive 3), the default value is "merged into code". Bug in the Flex 4 (so Adobe Drive 5), the default value is "Runtime Shared Library".
And because the module is ran independently (with no link with the flex code that load your module), the flash player crashes because it doesn't find your libraries (like ICustomCheckinUI).
I discovered this problem running the Custom UI from the windows explorer (not with Bridge) and using the Flash Player Debug version, and watching the error log files of the Flash Player.
So in the end, when I checked "merged into code" in the Framework Linkage option, all my dependencies of my flex module were merged into my final module swf, and no more flash crash.
Sorry for my bad english and hope it helped.
Guillaume
(edit : screenshot at http://www.hostingpics.net/viewer.php?id=276932flexbuildpath.png )

How can I get Adobe Bridge to show XMP metadata using Adobe Drive 4 CMIS Connector?

I have successfully connected to an Alfresco Enterprise Edition 4.1.0 repository, using the Adobe Drive 4, created a test folder and uploaded a jpeg file containing XMP metadata into it.
When I view the image's metadata (using Adobe Bridge), I observe that only part the standard file properties are displayed.
When I view a local copy of the image using the same, I see all fields of the standard file properties plus available metadata.
My question: what should I do in Adobe Bridge to be able to see all available XMP metadata?
Kind Regards and Appreciation
Don Greenwood
Pixelboxx GmbH
Dortmund

How did you get through to customer service? They've changed the website and I can't even find phone numbers or a chat button any more.
Here's my story that I posted on discussion yesterday, but no one has replied:
I am screaming and pulling my hair out right now! The last six months with Adobe has been a nightmare.
Once again I am completely locked out of Creative Cloud and cannot use the apps even though my automatic monthly deduction for payment was just made a couple of days ago. Creative Cloud continues to reset itself to the trial version which runs out in 30 days and after that I am locked out once again.
Now it looks like it is harder to access support than before. Where are chat and the phone numbers now? This was a nightmare with countless hours spent on chat and the phone over the last six months, and now I don't even know how to access support in order to spend even more time that does not solve the problem. What am I to do?
I cannot use the product I have paid for!
Please help!

How to enable Adobe Drive in CS5

How can I enable Adobe Drive in PSCS5?
its disabled (gray) under Preferences -> File Handling
I want to use my CS4 Version Cue Server.
Thx

function(){return A.apply(null,[this].concat($A(arguments)))}
KenToole wrote:
I didn't suggest that this was a separate 'payed for' application
I'm sure that's a relief to folks hoping for CS5 support of it.
And thanks especially for the update on Subversion integration into the CS products.
I run my own Subversion server for my team of developers. It's pretty straightforward to set up and very much "set it and forget it" trouble-free to run.
-Noel

No previews in Bridge with Adobe Drive 3?

We are using a custom connector for Adobe Drive. Windows Explorer shows the correct thumbnails and previews for asset versions (in the Show Versions UI). However in Bridge we cannot see any thumbnails or previews. Clearing or purging the cache does not help. It turns out that the execute method in the GetPreviewIconHandler class is never called when browsing assets in Bridge. This used to work fine with Adobe Drive 2 (at least for jpg previews, png previews never seemed to work in Bridge). We tried different Bridge versions (4.0.4.2, 4.0.5.11, 4.1.054) but they all have the same problem. Did anything change regarding this behavior in Adobe Drive 3? Thanks in advance for any advice.

Indeed, adding the READ_XMP_METADATA capability seems to do the trick.
Thanks for the quick help.

I need information on how Adobe Drive works and how to set it up

Hey folks,
believe it or not, but I have been searching a lot on the web already on how to find information how Adobe Drive works and how to set it up.
Most information that I found is old and seems to be valid only for older versions of Creative suite. Here in the company we use CS5.5 and will switch to CS6 soon.
I already downloaded Adobe Drive 3 and installed it on my Mac. Unfortunately I don't know what to do next? Do I need Adobe CQ to make it work? Or can I use it with an existing SVN infrastructure, that we have here? Actually I would like to access the SVN via Adobe Bridge. But after the installation of Adobe Drive my Bridge CS5.5 is crashing while starting up, and I didn't find out how to fix this again.
Actually I just found the manual for Adobe Drive 3 and read it. Seems to be easy in case its working. But it's not in my case, as mentioned above.
Any idea what could be the problem?

Thanks,
in the meantime I managed to re-setup Adobe Drive 3 again. Bridge CS5.1 is still crashing (i have a log-file with a detailed error-report, if somebody knows how to extract information from this.
At least now I can start Drive as a standalone application.
So now my main question is how to connect Drive 3 to our subversion infrastructure in the company. Does anybody have information on this?

Adobe Drive 3 not starting on Mac OS X 10.7.2

I have a computer with Mac OS X 10.7.2 installed. On this computer there is the Creative Suite CS 5.5 (with the latest updates applied to every single piece), a component of the Creative Suite CS5 (InDesign CS5, updated as well). It is impossible to have Adobe Drive 3 running on this computer.
Every time the Adobe Drive 3 application is launched, the CS5ServiceManager crashes.
Not only, when Adobe Drive 3 is installed on that computer, Photoshop CS 5.1 and Illustrator CS 5.1 take 2 minutes to open a file that normally takes 2/3 seconds to be opened.
Is this a known bug?
Best,
Luca

Hi Luca,
We comparing the Service Manager load lib, find there are some difference:
Following are piece of Service Manager load library when Service Manager launched successfully:
/Users/labuser/Library/Application Support/Adobe/CS5ServiceManager
/Library/Application Support/Adobe/CS5ServiceManager/CS5ServiceManager.app/Contents/MacOS/CS5ServiceManager
/System/Library/Frameworks/JavaVM.framework/Versions/A/JavaVM
/System/Library/PrivateFrameworks/JavaLaunching.framework/Versions/A/JavaLaunching
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries/libjvmlinkage.dylib
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home/lib/jce.jar
/System/Library/Java/Extensions/AppleScriptEngine.jar
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries/libverify.dylib
/System/Library/Frameworks/JavaVM.framework/Versions/A/Frameworks/JavaNativeFoundation.fra mework/Versions/A/JavaNativeFoundation
/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries/libjava.jnilib
Follwoing are from your logs:
    0x1000 -    0x3bfe7 +com.adobe.csi.CS5ServiceManager (??? - 5.0.0.743) <72D5CE97-C76C-E56A-4F97-FA1C27EF3179> /Library/Application Support/Adobe/*/CS5ServiceManager.app/Contents/MacOS/CS5ServiceManager
   0x76000 - 0x7affd com.apple.JavaVM (14.1.0 - 14.1.0) <1163556C-5C1D-3C5A-8767-682DAE7D3174> /System/Library/Frameworks/JavaVM.framework/Versions/A/JavaVM
0x82000 -    0x86fff JavaLaunching (??? - ???) <54FA100F-1C60-33D1-97C0-3B0704FE97BC> /System/Library/PrivateFrameworks/JavaLaunching.framework/Versions/A/JavaLaunching
0x70f000 -   0x716fff libverify.dylib (1.0 - 1.0) <C4F30112-1D8E-31D8-8E38-F6A10194E21F> /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/libverify.dylib
0x71b000 -   0x723fff JavaNativeFoundation (??? - ???) <066553E2-055F-3D16-AD97-8F715D63CC61> /System/Library/Frameworks/JavaVM.framework/Versions/A/Frameworks/JavaNativeFoundation.fr amework/Versions/A/JavaNativeFoundation
0x72c000 -   0x733ffb libjvmlinkage.dylib (??? - ???) <6A77EDD1-D1B2-39A9-A637-67BC1D7349F9> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Libraries/libjvmlinkage.dylib
0x73a000 -   0x757fff libjava.jnilib (??? - ???) <A84706D2-237E-37E9-A7B5-F1079935107D> /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Libraries/libjava.jnilib
0x5000000 - 0x536dfe3 libjvm.dylib (??? - ???) <E873F28F-C5E1-DAA6-2B07-7C1A50044B06> /System/Library/Java/JavaVirtualMachines/1.5.0/Contents/Home/bundle/Libraries/libjvm.dylib
0x8fe06000 - 0x8fe389c7 dyld (195.5 - ???) <134323A7-49DC-3A9D-ACFD-32FAD0FD6BA2> /usr/lib/dyld
Highlighted are difference.
My concern is :there are two JavaVM framework 1.5.0 and 1.6.0 involved. it should be only 1.6.0.jdk in the /System/Library/Java/JavaVirtualMachines if all the java updated from Mac website.
So can you just keep 1.6.0 jdk and try it again? Thanks for your patience.
Thanks,
Jianfeng

Adobe Drive & Version Que

Similar Messages

Maybe you are looking for