IDCS2 on INTEL crashes while placing apicture from a AFP server volume

[macandweb@adobeforums.com]

INTEL MacPro 2.66GHz, 2GB RAM, OS X 10.4.7, IDCS2 4.0.4, OSX Server 10.3.9 (AFP)

When I place a picture (jpg or smthng else) from an AFP server volume ID will crash. Sometimes the crash will occur in the dialog box where I choose the file to place, sometime it crashes after I click the ok-button.

I reproduces this crash on several machines, also with ID2.

Yes I know, Rosetta ..., but I think this is a major bug which should be fixed.

If you also have this problem, then please send a bug report to:
<http://www.adobe.com/misc/bugreport.html>

Thierry

[Richard_Sohanchyk@adobeforums.com]

See big QA above feature request.

[Peter_Truskier@adobeforums.com]

Yes I know, Rosetta ..., but I think this is a major bug which should
be fixed.




Actually it is not Rosetta - at least not in and of itself - and it may or may not be a bug.

I have a nearly identical environment to yours - Intel Mac with 10.4.7, InDesign 4.0.4, and a Panther 10.3.9 Mac OS X Server sharing AFP volumes. The only difference is that my client machine is a MacBook Pro. I am able to reliably place every type of image I have tried - JPEG, PSD, TIFF, EPS, PSD without a crash or any other sort of problem.

Can we assume that you are able to place the same images from the network mount in an InDesign document on a PPC Mac? Can we also assume that you are able to place the same images using your Mac Pro after you have copied them to your local drive?

Perhaps there is a hardware-related issue at play. It does seem that the people on this forum experiencing crashes with ID and Intel Macs are using either MacPros or iMacs, and not Mac Minis or MacBooks/MacBook Pros.

[macandweb@adobeforums.com]

Both your "can we assume ..." questions I can answer with yes. I tested that.

Tomorrow I'll give it a try on my colleagues MacBook Pro

Thierry

[Peter_Truskier@adobeforums.com]

Thierry,

Please post the outcome. It would be very interesting to know whether the crashes that some folks are having are related to the machine type.

[Eric_@_MCA@adobeforums.com]

Are you using the Adobe dialog or the Apple dialog? Probably wouldn't hurt to try switching to see if that clears the issue...

[Peter_Truskier@adobeforums.com]

Are you using the Adobe dialog or the Apple dialog? Probably wouldn't
hurt to try switching to see if that clears the issue...




I had the same thought, Eric, and tried both on my machine. I could not get it to crash either way.

However, your suggestion brings up another possibility too. There are known incompatibilities with Version Cue and Intel Macs - it simply will not work. If you ever installed it on this machine, Thierry, it may be that there are left over bits of Version Cue that are causing the problem.

[chris@adsrus.com]

Just out of curiosity...
Can you connect w/ SMB, and place files successfully?
what version of AFP are you actually running & what OS on the server?

Chris

[Peter_Truskier@adobeforums.com]

what version of AFP are you actually running & what OS on the server?




From the original post:

... OSX Server 10.3.9 (AFP)

[macandweb@adobeforums.com]

Chris, using SMB was a good idea, unexpectedly it works!

I tried several other things:

- On the MacBook Pro I don't have problems, looks like it only happens to the MacPro (I didn't check MacMini and iMac, maybe someone else can check this ... ?)

- I allways used th Apple dialog, but Adobe dialog crashes as well.

- Another MacPro is connected with an INTEL Imac, which has the normal OS 10.4.7 installed (the iMac shares a directory). This MacPro crashes also.

- The crash occurs when an images that lies on an AFP server is placed in an ID document. It doesn't matter if the ID document is on the server or on the local HD.

The solution for me is, using SMB for placing images.

So far, thanks for all your input.

Thierry

[chris@adsrus.com]

Peter,
Thanks..... I should have looked more carefully :-)

Thierry,
Be aware that your path to the image may have changed using an smb mount. It did on mine. I asked about the AFP versus SMB because just recently I had a hard drive on my server crash, and somehow corrupted my AFP. My server is Linux, however.
We re-installed a newer version of AFP & all seems to be well now.
I know Peter has said there was a problem w/ a certain version of AFP, but I think that was when running on a Windows server. It may have something to do w/ your problems, but then again it may not apply at all.
Glad you got somewhere w/ it!
:-)
Chris

[Peter_Truskier@adobeforums.com]

I know Peter has said there was a problem w/ a certain version of AFP,
but I think that was when running on a Windows server.




Right, Chris. The problems I know about have to do with newer Mac OS X clients (Tiger and, to a lesser extent, Panther) connecting to AFP 2.x servers (like Microsoft Services for Macintosh). Panther Server, though, implements AFP 3, and I'm not aware of any problems with Tiger clients connecting to a Panther server.

I can't explain why SMB works and AFP doesn't, Thierry. Not knowing how big your company is, do you have an Apple service engineer or other rep you can ask?

Do you have similar problems in any other application?

[macandweb@adobeforums.com]

Chris,
The thing with the paths I checked out with my MacBook Pro. I placed an image using SMB, saved and closes the ID doc. Then I unmounted and remounted it with AFP an reopend the ID document - the path to the image was still ok.

Peter,
Our company is small ... 6 macs, one OS X Server.

But actually we're not working a lot with ID, our business is selling macs, software and support ...
So the first time I got aware of this bug was, when a client told me that he's got this problems. Except that he's also using a MacPro 2.66GHz, his environment is different than ours.

My client also uses ID2 which has the same problems as IDCS2.

By now I'm not aware of similar probs in other apps than Adobes.

Thierry

[Laura_Kneppel@adobeforums.com]

We have had the same problem with G5 Macs running Tiger. It seems to be a bug with Tiger Clients and happens when image files are copied to the AFP server volumes. Our workaround has been to save the images to the server volumes rather than copying them to the server volumes. Then when images are placed into ID from the server volumes, it doesn't crash. I have been told it is an Apple bug and that it happens to Tiger clients with all third party AFP servers and also with Apple AFP servers. I can't test the latter, as we are running Xinet FullPress 15 on the server and have to shut off OS X Server AFP services or they conflict. For the record our Panther Mac clients do not have the problem. All Tiger Macs are on 10.4.7, as we keep hoping each update might fix the problem. :-)

Our server is a G5 Xserve running OS X Server 10.4.7 and Xinet FullPress 15.02. Xinet keeps trying to fix the bug from their end, but so far nothing we have tried truly fixes it, only our save-to workaround is 100%. Actually I was starting to get hopeful that the MacPros did not have the problem, but they soon began to report it, too.