Failure with Aperture Upgrade form 3.2.2 to 3,2,4

I need to upgrade Aperture 3.2.2 on a MacBook Pro (OSX 10.7.4) in order to share Aperture libraries with an iMac (OSX 10.6.8).
The Download of 3.2.4 on the MacBook was long, but without any problems. However, when unpacking, a message is poping up, telling that this update must be done by Mac App Store und notihing is working any more.
Is Aperture 3.2.4 not compatible with OSX 10.7.4 ?
When looking for for help, there is mostly Aperture Version 3.3 shown (= very anoying), which is not compatible with my iMac. For several reasons I will not yet upgrage my iMac to OSX 10.7... but use the MacBook when travelling.
Who can help?
Thanks so much,
Felix

Thanks a lot Ernie
At least, I must no longer feel a "dump"..... Thus, there is no way to bring Aperture 3.2.4 on my MacBook (OSX 10.7.4) ?
Greetings, Felix

Similar Messages

How can I install after a hard drive failure with only upgrade disk?

I've been using Photoshop since 1998 but my HDD recently suffered a complete failure and I've had to change the drive. Unfortunately, I don't have my original Photoshop disk, only a CS2 and CS5 upgrade disk (with both serial numbers). Is there any way round this problem? Many thanks in advance for any replies.

Welcome to the forum.
My upgrade path started with Ps version 2.5. That was the last full version, that I had. All the rest were upgrades from there, though to CS 2.
When I went to install CS 2, I was asked for the CS version. I had both the upgrade disc and the S/N (my S/N's went through a couple of iterations, over the decades). In my case, the CS version disc was inserted, found and the installation went smoothly.
Now, while I have CS 5 (and 5.5 and 6), I never installed CS 5, it was just part of the upgrade path, to get me to CS 6 at the end. With my CS 5 S/N, CS 6 installed fine.
That was what worked for me, and I hope will work for you too. Keep that CS 2 disc handy, as you might need to insert that into the multi-drive, at a point in the CS 5 installation.
The one worry that I would have, with an HDD failure, would be Activation, as you probably did not Deactivate Ps, before that failure. For that, should you be up against your allowed Activations, you will likely want to call Adobe Customer Support, and explain your problem. They should be able to reset the Activations, and help you.
Good luck,
Hunt

Another Win7 Bootcamp failure with Yosemite upgrade (missing 34 GB)

I've been reading what others have been doing per Loner T's instructions, but I'm a bit unclear on the ultimate goal, particularly when using testdisk and looking for "familiar files." I'm hoping for some instructions on how to recover my Win7 partition. I'm running a testdisk deeper search, but again I'm not sure what I'm looking for in that program or if I've followed the correct selections. Here are the outputs from the 4 commands that Loner T has said to provide...
Huge thanks in advance for any help.

So here's the results of a Quick Search:
Inside the MS Data selection:
The top MS Data and the bottom one both show "Can't open filesystem" when I use P: list files, but the middle one (size = 191678457) has that System Volume Information file you mentioned in the thread, along with some other recognizable file names, though there are a few key programs I had installed that I don't see, but I'm hoping they'll still be there when we recover the partition. Here's that file highlighted, and I put red boxes around what I think are the "start" and "end," are those correct?
In the other thread, you go on to say "If this is the only MS data entry..." but I have 3 I think, so will I need to do something different than fhornedo?

Aperture upgrade won't open with serial number

I have a retail license for aperture version 2.1 with the serial numbers on the jacket for the cd. Several times after upgrades the new version will ask for my name and serial number. The latest upgrade to 3.4.5 tells me that my serial number is invalid. Any suggestions?

Thank you so much for your reply but I want to apologize for wasting your time with this question. I was making a "rookie" mistake by using my cd jacket information from version 2.1. After reading your reply I looked further into my cd's and found the version 3.0 cd with the info I needed on the jacket. The correct serial number works fine with the upgrade.

IPhoto to Aperture upgrade failure

Hello, I have upgraded to the latest iPhoto 9.3 in order to upgrade the picture library to work with Aperture, but the upgrade of the picture library stops at step 5 of 9 at 96%. I have tried a several times and in safe mode as well. Any tips?
At the moment I can´t use the pictures at all, beacuse the library looks like an Aperture library, but needs an upgrade by starting iPhoto.
Can I remove iPhoto and install it again without remove the existing picture library?
Thank´s
Magnus

Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild.
If that fails:
Restore from your back up. Repair the Library (as above) and then upgrade again.

Form 6.0/6i with database Upgrade to Oracle 8i

Hi all,
I am planning to update our database from Oracle 7.3.4 to Oracle 8i (8.1.6).
Do you know that whether i need to recomplile all report (rep) and form (fmx) after grade?
For my past experience, all reports need to recomplile in REPORT 3.0 for change of table any table structure/move tablespace.
Best Regards
Chris Sung
null

Hi Himanshu,
oracle forms6i and reports6i is not certified for Oracle 10g relese2 database,its only certified for oracle10g release1 with Patch17.
We ran in to same problem recently..
We got errors when we are compiling Forms and reports against Oracle10g release2.database
Error 00600: database internal error.
This is only happened with the few Forms and Reports which are having Database links(For those remote databases which were lower version than 10g relese2) in it.

Too late to start up with Aperture?

I'm aware of both Aperture and iPhoto being trashed by Apple in the near future. I have been using iPhoto on my MacBook Pro since it was introduced and usually do some additional editing as required using Adobe Photoshop Elements. But now I'm starting to shoot in RAW, and iPhoto won't even take RAW files into it's library without converting them to Jpegs. I think the best bet for me would be to upgrade to Aerture but I also know it's no longer going to be supported. In fact, I've read that Apple is no longer interested in the entire advanced enthusiast and pro photography spaces. Thoughts and advice for me? I have been spoiled by the wonderful Apple apps that work so nicely. By the way, I haven't upgraded to Yosemite, nor do I intend to. I think in my case it will take me in the wrong direction.

Reasons for migrating to Aperture of course depend upon your intended use. As pointed out here, development for Aperture has ceased. Apple has decided to migrate to another application, using cloud based back end for image storage. There has been more than one or two posts of disappointment on this course of action. In the end it's Apples decision however right or wrong the users believe that decision to be. Your best bet is to look at the features, determine if those are of use to you, scan the threads here for comments, then determine if the cost is worth it.
As opined Aperture probably has about a year of life left. After that you may be able to use it so long as you do not upgrade your operating system. But make no mistake - there will not be an Aperture 4.x. Nor, in my opinion will there be any significant (or heroic) efforts to fix what are now significant issues with Aperture.
The trade off, in my opinion is not worth it. Especially when you can get Lightroom now for a modest price. That is if you don't mind paying a monthly usage fee and really don't need facial recognition. The former being the pricing plan Adobe is moving to and the latter being completely absent from Lightroom. I don't know of any other viable professional package on the market right now. On the upside, Adobe products do support IPTC extended metadata which Apple never adopted. Understandable, it was an Adobe push - but the data stored is pretty nice. Mostly dealing with model and release information (and others, read the IPTC specs if you are interested) - if you deal with that kind of thing.
As for my experiences - Aperture use to be an incredible product. Especially with the introduction of Facial Recognition - which is now horribly broke. Here are some of my experiences.
FACES:
- Aperture now scans my entire photo library for new faces in every image every time the application fires up. This isn't a problem if you have a few hundred images. Once you start hitting about ten thousand (10,000) it becomes a nuisance. It takes about 45 seconds. Multiply that time out based on your library size.
- Aperture now rescans every identified face for a match, every time you identify a new face. Ok, I get this process. You have marked this guy as John Smith, now we are going to look for possible matches for John Smith. The only problem is that it appears to being in every face which it cannot justify as someone else.
- Aperture often double tags a face. To explain this you have to understand what the software is (probably) doing and how it records facial locations. First it applies some order of facial recognition. It looks for things which appear to be faces. Eyes, nose, mouth. It then draws a box around that area. You have the option to select that boxed area and in the upper left hand corner click on the "x" to close the box. Except when two boxes are exactly on top of each other. It's maddening. You cannot get rid of either box. Nor, can you identify the name of the person in both iterations of the box. If you understand all the places where you can name people (every software package has multiple places to do the same task) then you can select one of the boxes and tell Aperture that this area "is not a face". But since you are now telling the AI that the information contained within the defined area is not a face (when in fact it is) you are setting yourself up for a real HAL9000 moment. And if you don't get that reference, you are simply confusing the system. Especially when you leave box 2 in place and give that person a name. So is it a face or isn't it? Aperture appears to be using both decisions (is and isn't a face) in future iterations of facial identification (finding faces in an image) and facial recognition (is this face Johnny Smith or Jane Smith).
PLACES:
- A number of folks have reported problems with the geolocation of images. With the upgrade to the latest OS I have also begun to experience this problem. Images which I shot in my home studio were correctly mapped within a few feet of my home. With Aperture 3.6 many of them are not even on the same block. I actually have photographs which were previously (properly) mapped in central Maryland, that with the 3.6 upgrade are now tagged in the middle of the Pacific Ocean. Yes you can manually move them to their correct location - but again, thats great with a few hundred images. Thousands becomes a real nightmare.
This same geomapping problem has reared its head in faces as well with some users reporting the placement of the facial identification box in the wrong location on the image. Far be it from me to disparage software developers but it's almost as if the crew forgot that the image coordinates (whether for dropping a box on a photo or a pin on a map) start at 0,0 being the upper left corner of the display. /snark
STORAGE:
- A couple "upgrades" back Aperture migrated a reasonable and easily understandable storage methodology in which photos were filed (on your hard disk) in a directory architecture based on the date/time of image. So, if something horrible happened a savvy user could open the Aperture package, navigate through the directory and recover lost or damaged data. Not anymore. I defy anyone to explain the system now. It appears to have something to do with the ingest date, solar or lunar cycle and a hashed algorithm of some programmers mothers birthdate which is then translated into an XML filename. All that to say - good luck finding your photo IF you need to AND you are storing images internal to the Aperture database. But lets get serious about filing images under a directory system based on import date/time. This is great - if you import your photos on the date of the shoot. But, if you go on a two week trip of Europe and ingest all your photos the day you get home, well that's not too bad. A year later when you have to recover all your photos from a significant system failure and end up ingesting 10,000 photos on 15 May 2014 that is another story entirely. Now, good luck finding your photos on the hard disk (if you need to that is).
SECURITY:
- Apple applied the "sandbox" theory to image security. Basically in a nutshell all your photos are locked from editing by only approved applications. So don't even think you are going to download some awesome script to do some wonderful task and have it work. Sorry. It took me months of phone calls with apple support before one of those on the line even thought to walk me through my editing process and determined the script/app I was using was not apple approved and this was causing my problem. I get it, new risks in computer data and all. But there comes a point when you have taken security so far as to lock the user out of the loop.
CRASHES:
- We all have them, and they all happen at the worst possible moments. In the past 2 days I have been working in Aperture with my data and experience Aperture crashes about every 45 minutes or so. Yes, I have repaired my permissions, yes I have repaired the database and Yes I have rebuilt the database. It just appears to be another nuisance of Aperture that wasn't there a couple years ago. I have even gone so far as to completely uninstall Aperture, reload it from scratch and re-ingest all my images (that is how I discovered the whole ingest date/time versus shoot date/time storage della described above). My entire library now (in the Aperture Package) falls under a single year (2014) when previously it was spread across 40 years (from the 70's to current date). Yes, I have images from the 70's in aperture. I scanned a lot of film over the years. Regardless, I could never track down exactly why the crashes were happening. Some feedback from Apple would be nice - I have after all must have sent them a few hundred crash reports by now. My RAM is good (yup, I have tested it), drive space is fine and I have plenty of it so ..... Im left scratching my head.
Aside from all of that - I loved Aperture, while it lasted. I will be saddened by it's loss and to date I haven't heard anything yet which gives me hope about Photos. As someone who is occasionally paid, and who occasionally pays to shoot (read into that what you will) I refuse to store my image library on anyone else cloud. I have my own storage architecture which has worked fine for me. I haven't lost an image now in the many many years I have been using it. If you shoot a lot I recommend you look into Drobo. I was an early adopter and have never looked back. I have two 16TB units on my desk - one for live data, one for TimeMachine.
Cloud storage is simply too risky.
1. You are reliant on too many factors which are (a) out of your control and (b) are run by people who really don't care about your data or your business. Not to mention the constant finger pointing. If a switch goes out somewhere in Nebraska I hope you had a local copy of your data because now you can't work. But then again, that defeats the whole purpose of cloud storage doesn't it? How many Apple users signed up and put up web pages in what is now the cloud? You remember those days? You data is your data and will always be there? Until we change our ToS and now longer support personal websites.
2. Pricing. Seriously look at the pricing. The cloud tops out at 1TB for $20/month. Not bad. What do I do with the other 15TB of data I have? Oh, and after 3 months I could have purchased a Western Digital portable USB 1TB. If Moore was right (and so far he has been pretty close) that 1TB next year will only cost me $30 at the local Best Buy. If you can find it. You know 6TB drives come out this fall? Only a couple hundred dollars each. About 1 years payments on the cloud. Now I realize I might get slammed there - not everyone has $60 extra dollars for a portable 1TB drive. But I am assuming you do since you are tinkling about spending $70 for an app which is only viable for another year.
3. Cloud storage really? I don't know about you but the last time I ran an all day shoot I used up about 128GB of card space which took me a couple hours of transfer time (card to local disk). Now, how long would it take me to run that up to the cloud before I can use it. And that was on an older camera which was half the megapixels of what I am shooting now. So, 1/4 of my storage maximum being transferred up to the cloud after only one shoot. Awesome. Ill get a coffee, take a road trip, and in a couple days my images will be ready for first draft editing. Meanwhile my client will be ..... strumming his fingers? Don't worry though sir - a couple more days and your proofs will be available online. For everyone with any mad skillz to hack into. The only secure computer is one not online.
So, there are the down sides from my perspective. Yup, it's one sided. If you want to know the good stuff (and there is a lot of good stuff) just read the sales brochures. It's fine product - so long as you understand the limitations. And overall I am happy with it. And I will, again, be saddened when it leaves the market.
Aperture's days are numbered. I am past denial and isolation. I guess this places me in the anger stage. There is no use in bargaining. It is Apples decision and they have made it. Depression is next. I doubt I will make it to acceptance - unless there are some significant changes to Photos and I don't see that in the works. Apple appears to be dropping their professional line of products and pushing to the general market.

Few 5DmkII RAW files do not open with Aperture, but OK with other software

Hi, I have two RAW files which I cannot import with Apple Aperture. The files open fine with Canon Digital Photo Professional, Raw Photo Processor and dcraw (and with various programs on my Windows 7 laptop) and I'm able to create TIFF files from the RAW files with every other software.
Detail about the files:
A. they are two first frames of burst (used auto bracketing, which takes 3 images in burst mode, to create HDR image)
B. there is nothing strange in the files, they are normal RAW files and file size is normal as well (other 28.4MB and 32.7MB)
C. both files process OK in above mentioned softwares and there are no blocks missing from created TIFF images, also preview JPG in the RAW file is OK
D. Mac OS X Quick view (press spacebar in Finder) and Preview do show these two RAW images well (I assume they use the embedded JPG image)
I have installed all the updates available in "Apple icon" -> "Software update..." function. Therefore I have Apple Aperture version 3.0.2. Computer is MacPro:
Model Name: Mac Pro
Model Identifier: MacPro3,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 2.8 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 12 MB
Memory: 12 GB
Bus Speed: 1.6 GHz
Boot ROM Version: MP31.006C.B05
SMC Version (system): 1.25f4
How I can submit the files for Apple to create fix? I searched for Apple Aperture support but there is only this forum, no email address or anything. Do they read this forum?

Some clarifications and answers to your questions:
First to Tony Gay:
I try the feedback later today even they claim "Please know that while we do read these submissions, we cannot guarantee a personalized response.", which is original reason why I'm why I wrote this question here. The url you provided did not work but this should:
http://www.apple.com/support/feedback
This is not relevant to sRAW files, I did not change the between camera taking automated bracketed shots the image format for 2 shots to sRAW and took 3rd with RAW, that is not even possible.
I have copied the images from card to hard drive, not trying to read from the card itself. However now you mention tried also from card = exactly same result. Tried desktop (different HD) and external USB and external eSata, all same result.
Get info doesn't show anything wierd for the images. All other 192 RAWs from same shoot were imported with exact same methodology (as well as 60000 images before that).
Then to gosuk2:
There is no HDR setting in camera, I took the images FOR HDR, but did not use any specific setting, just used 1 1/3 stop bracketing and 2 second times when camera automatically takes 1 1/3 underexposed, correct exposure and 1 1/3 overexposed image (the order of images can naturally be changed via custom function in camera). All this is unrelevant since I shoot quite often HDR with this method (=more than 500 images each month) this way and they have always been fine before these two images.
I see the files in import panel and I the don't use import dublicates setting so that doesn't affect the situation (why it would, Aperture things files are broken).
Again HDR cannot be combined in 5DmkII, it's just automatically shoot 3 bracketed shots.
No I don't get same result no matter what I do, it's just these two files. My other ~5000 HDR bracketed RAWs are importing fine as well as all burst/shots taken in continous shooting mode.
I'm very aware how stacking of images works, but I do not understand relevance to this issue. I can not import the images at all to Apple Aperture, after importing all images Aperture displays dialog saying that following files could not be imported to Aperture, then displays list with both of these files in the list and gives possibility to locate the files in Finder.
I have used Aperture since version 1 and I have 70000 images imported successfully to Aperture. Earlier I have seen this dialog "Aperture could not import image" only after hard drive/card failure. However then images cannot be used in Canon's DPP (Digital Photo Professional) or any other RAW software - now the problem ONLY EXISTS in Aperture all other RAW converters are able to open and process SUCCESSFULLY these images.
So I'm not whining that Aperture is not good, but if it starts to work only part of the images in future and I have to process rest of the images with Canon DPP (that program is really lousy on usability standpoint) then I'm not so happy with Aperture anymore.
Will report here if I get any comments back from Apple through the Feebback tool.
Message was edited by: vahonen (due to forum software replacing words like s u c k s etc. with ***)
Message was edited by: vahonen

Imac (10.6.8) and Macbook Pro R (10.8) with Aperture??s

I have an Imac with Aperture 3.2.4 that works fine on the current system (10.6.8).
I just got a new Macbook Pro Retina for travel that has 10.8 on it that I installed Aperture on, updated it to the current version, and added a few photos onto it to experiment with. However, now it says I have to rebuild the Library for my old photos which "can't be undone." Glad it did it with just a few photos.
My dilemma...IF I use this laptop on my trip for editing photos and return, am I going to be able to import them back to my Imac with the "old Aperture 3.2.4" or not? Or, am I soon going to be forced to upgrade my Imac to the more current OS system. I hate updating when everything works great!

You will not be able to go backward.
Once the library is updated (or you have a new library made with the new version of Aperture) that library will not open in the old version of Aperture.

I have Aperture 3 now and can't use my iPhoto library with Aperture.

My version of iPhoto is 8.1.2. Aperture says I need iPhoto 9.1 or somewhere around there. How do I do this. Is this another purchase I will have to make? I downloaded the upgrade for iPhoto 9.4.2 and it told me that I need iPhoto 9.1 or later for the upgrade to 9.4.2. Come on man!!!
I just spent $100 for mountain lion and aperture. What is the oldest upgrade I can make to iPhoto 8.1.2 so it will work with aperture 3? Or am I just stuck with having to purchase iPhoto 9.1?
Thanks

As documented you must have iPhoto 9.3 and Aperture 3.3 or later - if you do not meet the minimum requirements then you must upgrade to meet them - in your case purchasing iPhoto '11 in the App store
http://support.apple.com/kb/HT5260?viewlocale=en_US&locale=en_US
With Aperture 3.3 you can directly open and work with libraries from iPhoto 9.3 or later.
LN

My repaired macbook now has Yosemite. I have my photo library on an external drive loaded with Aperture 2. Now unable to do anything.

My "photo management macbook" crashed and when it was repaired it was upgraded to Yosemite. This macbook is used exclusively for photos using Aperture 2 (I also have a new Pro retina and an older macbook as well, with Yosemite and Lion loaded respectively). I have my photo library on an external drive and it was loaded using Aperture 2. Now I cannot use Aperture, cannot see photos, cannot upgrade to Aperture 3.6 and so cannot migrate photos to another software package, which I am going to have to do this year sometime.
What can I do to get Aperture working and migrate my photos?

On Yosemite you can only run Aperture 3.6, but that will not run on Lion.
If you want to get Aperture running on your photo management macbook, restore it to the previous system from the last backup you made before the crash occurred, if you have a full Time Machine backup. If you want to keep the Mac on Yosemite, try to restore the older system to an external drive and boot the Mac from that drive, when you want to work with Aperture 2.
Otherwise your only option would be to buy the upgrade to Aperture 3.6.

Extend SAP R/3 4.x with Interactive PDF Forms

Hi there,
In this blog of Matthias Zeller <a href="http:///people/matthias.zeller2/blog/2004/06/22/the-hidden-secret-of-adobe-reader hidden secret of Adobe Reader</a> there is the following paragraph:
<i>While mySAP ERP 2004 provides many business scenarios using Interactive Forms out-of-the-box, a lot of customers have asked me how they can use the new Interactive Forms with existing R/3 applications. Therefore, I would like to encourage you to vote for my SAP TechEd presentation proposal ("Extend your SAP R/3 4.x applications with interactive PDF forms"). I plan to discuss how you can connect your existing SAP R/3 applications with SAP Web AS 6.40 to enable interactive form workflows.</i>
Can somebody tell me if this presentation is somewhere on SDN? Or can somebody tell me where i can find more information about this subject?
Thx in advance.
Regards Maarten.

Hi Maarten,
Here's a brief run-down on how you could make use of SAP/Adobe Interactive Forms and Workflow:
1) Remember that a form is really just a UI for collecting data. A PDF form can be used to collect data online (connected to your SAP system) or offline, e.g. you could send it as a mail attachment, fill it in, and email it to a central point for uploading into the system.
2) The main requirements for using SAP Interactive Forms are:
a) A NW04 (6.40) or NW04s (7.00) WebAs (Java Stack) to run Adobe Document Services. This is the critical component that assigns ReaderRights to the document, e.g. so that the user can change the data and save it on the document. You could run a WebAs like this alongside your R/3 4.7 - e.g. if you have an XI system or Enterprise Portal you could use that system to run Adobe Document Services. Every form you create must be generated via the Adobe Document Services to get the Reader Rights. Note: Get a NW04s environment if you can - as this release has usefuul new features such as loading attachments to the PDF, using digital signatures, etc.
b) A WebDynpro application to generate the Adobe form via Adobe Document Services, and to execute the Adobe Form when using online mode, and to upload offline forms. Tutorials on how to do this are available in SDN - have a look at the Adobe section within WebDynpro. Note: From ECC 5.0 there are some standard WebDynpros apps provided, but in R/3 4.7 you will need to write your own.
c) There's also a licensing requirement for any production custom forms (SAP provided forms and cosmetic changes to those forms are free) so make sure you get your SAP account manager involved to help sort out how your intended usage will fit in with your current license agreement and any discounts that may apply.
3) To use the "form" with workflow has some additional requirements:
a) You need to store the data entered via the form somewhere that is accessible by Workflow. The easiest approach here is to use the standard form handling technique Internet Service Requests. Transaction QISRSCENARIO will let you define all of the form fields, give you BADIs for doing validation, raising workflow events, etc. Also from ECC 5.0 onwards using Adobe forms as the form entry is a standard option for this technique, so this will help reduce the upgrade impact when you eventually do upgrade.
b) Assuming you use ISRs, have your WebDynpro App call the function module ISR_PROCESS_EVENT to pass the data to R/3 and do the validation checks.
c) Assuming you use ISRs, you use the BOR object for notification such as BUS2078, as your main object for the workflow. The form data is attached to the notification and can be retrieved using function module ISR_SPECIAL_DATA_GET.
d) If you want to call your WebDynpro App from SBWP (I take you don't have Enterprise Portal?) then use transaction WF_EXTSRV to define the web service to call your WebDynpro app and generate a workflow task for it. Also you must configure transaction WF_HANDCUST to enable R/3 to handle web services. Note: If you do have the Enterprise Portal, you can use transaction SWFVISU instead.
I'd strongly recommend you read the ISR cookbook at http://service.sap.com/isr as well. ISRs aren't the only way to use Adobe forms with R/3 but they are extremely handy if you want to use your Adobe form with Workflow.
As for Lotus Notes, you can use your WebDynpro app to generate and send/receive a form to/from an email address. You can also put a hyperlink in your workflow task to call your WebDynpro app and use RSWUWFML2 (swap to Enhanced Notifications when you upgrade) to send out a mail with the hyperlink attached as per usual.
You'll also find some useful threads on Adobe forms and Workflow in the SDN BPM Forum. So if you have workflow specific questions try raising them in the BPM forum.
Enjoy!
Regards,
Jocelyn

Failure with EWS via WWSAPI (native code)

Failure with EWS via WWSAPI (native code)
I'm trying to make a request against Exchange(*) EWS
using WWSAPI (native code).
Exchange replies with the error:
"Cannot process the message because the content type
'application/soap+xml; charset=utf-8;
action="http://schemas.microsoft.com/exchange/services/2006/messages/ResolveNames"'
was not the expected type 'text/xml; charset=utf-8'."
It seems the SOAP envelope is ill-formed.
If I manually create the envelope (without WWSAPI) EWS gives no error.
Is WWSAPI supported for EWS?
I can provide all the code for testing.
Thanks & regards
josue
On WebServices tracing I see the following events:
Sending message - bin (id: 1):
3C 73 3A 45 6E 76 65 6C 6F 70 65 20 78 6D 6C 6E 73
3A 73 3D 22 68 74 74 70 3A 2F 2F 77 77 77 2E 77 33
2E 6F 72 67 2F 32 30 30 33 2F 30 35 2F 73 6F 61 70
2D 65 6E 76 65 6C 6F 70 65 22 3E 3C 73 3A 48 65 61
64 65 72 3E 3C 52 65 71 75 65 73 74 53 65 72 76 65
72 56 65 72 73 69 6F 6E 20 56 65 72 73 69 6F 6E 3D
22 45 78 63 68 61 6E 67 65 32 30 31 30 5F 53 50 31
22 20 78 6D 6C 6E 73 3D 22 68 74 74 70 3A 2F 2F 73
63 68 65 6D 61 73 2E 6D 69 63 72 6F 73 6F 66 74 2E
63 6F 6D 2F 65 78 63 68 61 6E 67 65 2F 73 65 72 76
69 63 65 73 2F 32 30 30 36 2F 74 79 70 65 73 22 2F
3E 3C 2F 73 3A 48 65 61 64 65 72 3E 3C 73 3A 42 6F
64 79 3E 3C 52 65 73 6F 6C 76 65 4E 61 6D 65 73 20
52 65 74 75 72 6E 46 75 6C 6C 43 6F 6E 74 61 63 74
44 61 74 61 3D 22 74 72 75 65 22 20 43 6F 6E 74 61
63 74 44 61 74 61 53 68 61 70 65 3D 22 49 64 4F 6E
6C 79 22 20 78 6D 6C 6E 73 3D 22 68 74 74 70 3A 2F
2F 73 63 68 65 6D 61 73 2E 6D 69 63 72 6F 73 6F 66
74 2E 63 6F 6D 2F 65 78 63 68 61 6E 67 65 2F 73 65
72 76 69 63 65 73 2F 32 30 30 36 2F 6D 65 73 73 61
67 65 73 22 3E 3C 55 6E 72 65 73 6F 6C 76 65 64 45
6E 74 72 79 3E 43 6C 65 62 65 72 3C 2F 55 6E 72 65
73 6F 6C 76 65 64 45 6E 74 72 79 3E 3C 2F 52 65 73
6F 6C 76 65 4E 61 6D 65 73 3E 3C 2F 73 3A 42 6F 64
79 3E 3C 2F 73 3A 45 6E 76 65 6C 6F 70 65 3E
Sending message (id: 1):
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope">
<s:Header>
<RequestServerVersion Version="Exchange2010_SP1" xmlns="http://schemas.microsoft.com/exchange/services/2006/types"/>
</s:Header>
<s:Body>
<ResolveNames ReturnFullContactData="true" ContactDataShape="IdOnly" xmlns="http://schemas.microsoft.com/exchange/services/2006/messages">
<UnresolvedEntry>Cleber</UnresolvedEntry>
</ResolveNames>
</s:Body>
</s:Envelope>
Error occurred: 0x803D0000 - The input data was not in the expected format or did not have the expected value.
Error occurred: 0x0 - The format of the HTTP request was not supported by the server.
Error occurred: 0x0 - The server returned HTTP status code '415 (0x19F)' with text
'Cannot process the message because the content type 'application/soap+xml;
charset=utf-8; action="http://schemas.microsoft.com/exchange/services/2006/messages/ResolveNames"'
was not the expecte
Error occurred: 0x0 - There was an error communicating with the endpoint at 'https://gpe-exc2k10/EWS/Exchange.asmx'.
WsCall API failed by 0x803D0000
(*) Microsoft Exchange 2010 SP3 with Update Rollup 7

Thank you for the tip. I was using SOAP 1.2. After changing to SOAP 1.1 it worked fine.
WS_ENVELOPE_VERSION soapVersion = WS_ENVELOPE_VERSION_SOAP_1_1;
Thanks and regards,
Josue

Iphoto needs update after working with aperture

I recently opened my iphoto library with aperture (v3.5.1). Now iphoto '09 won't open the library and prompts me to update to the latest version of iphoto.
Why does Apple force me to update / buy iphoto '11 this way?
Is there a way around?
Greetings and Thanx in advance!
Stephan

There is noway around updating to a compatible iPhoto version, if you upgraded your iPhoto library to an Aperture 3.5 library. Either restore the last version of your iPhoto library that you could use with your iPhoto version from your backup, or update to iPhoto '11 (version 9.5).
You could try to downgrade a copy of the upgraded library to iPhoto '09 with iPhoto Library Manager, but you would need the paid version, so you could rather upgrade iPhoto.

Syncing photos with Aperture 2.0

After upgrading to Aperture 2.0, I no longer have the option to select which projects I want to sync my photos from. It is now all photos or none (with Aperture 1.5, you could select one or more projects). Has anyone else experienced this problem? Is there any known workaround?

I have been running the Aperture 2.0.1 upgrade for some time now and still can't import Aperture albums. It's all or nothing.
Does anyone else continue to have the problem after upgrading to 2.0.1?
Thanks

Failure with Aperture Upgrade form 3.2.2 to 3,2,4

Similar Messages

Maybe you are looking for