No PDF Previews are appearing

I have tried this repeatedly on a Mac Pro quad-core Intel on
Safari 3 beta and Firefox 2. No matter what flavor of PDF files I
have uploaded so far, and most of them have been saved out of
Photoshop or directly from Acrobat Professional. There are no
previews that appear in my area of Share. Thought you would want
this feedback.
Look forward to future builds and also being able to upload
Photoshop, Flash, jpeg and other files and see a preview.
best wishes,
Mark

not sure what that means, I downloaded the program and when I try to open any file it only shows me folders

Similar Messages

Just installed mountain Lion. Viewing a pdf sent to me using preview and some colors are appearing BLACK, however when I view the same PDF in Acrobat they are perfect and what they are suppose to be. WHY would PREVIEW showing a different color?

Just installed mountain Lion. Viewing a pdf sent to me using preview and some colors are appearing BLACK, however when I view the same PDF in Acrobat they are perfect and what they are suppose to be. WHY would PREVIEW showing a different color?

Here's what I've found on the issue:
Pantone color definitions have changed (coinciding with CS6) — they are now "Pantone+" (I think that's what they're called). The "+" apparently means they're now LAB colors. Lab colors are not properly displayed in Preview (or in Finder previews) — they display as black (as far as I can tell, in all circumstances). I'm sure it's a tad more complicated than that, but that's the gist.
Now the bad news — nobody seems to know anything about a fix or workaround (unless you convert your PDFs to process — this might be a fix for sending to clients). It causes issues for me in AI files — being able to view them in the finder (with previews) is a HUGE time saver for my workflow... when they're all black, not so much.
In my chat with a director of product dev at Adobe, they placed the responsibility to fix on Apple (assuming Apple wants to support Pantone color definitions in their OS).

Pdfs and screenshots opened in Photoshop are appearing pixelated, or not displaying at all.

Hi. I'm on a new iMac system. (iMac 27" retina - Yosemite OS X 10.10).
Whenever I take a screenshot and open it up in Photoshop by using File/Open and locating the screenshot, it is appearing pixelated.
The same thing is occurring when I try to open a pdf, or the pdf doesn't appear at all.
Here is a saved photoshop file (jpg) of how a screenshot is appearing in Photoshop. I just took a screenshot of this page for the purposes of this exercise. Other screenshots appear even more pixelated.
The only reason I am opening screenshots in Photoshop is to crop them before posting anywhere or sending to anyone.
I'm selecting 'use the embedded profile (instead of the working space).
I'd attach the image of how a pdf is appearing in Photoshop but it is not displaying anything at the moment. A file does open to the right shape/size of the pdf but it appears blank.
I'm using File/Open locating the pdf file, I click OPEN, the specs I put in are: 300dpi, Select: Page1, Anti-aliased is ticked, Crop to Bounding Box, width: 19.8cm, height 8.8cm, contain proportions is ticked, 300dpi per inch, fit page, Bid depth: 8 bit, CMYK, Thumbnail size: Fit Page.
Which is everything I used to do on my old Mac, and which worked perfectly, but not working now. Wondering if it's a bug or if I'm missing something in Photoshop, due to it being an upgraded Photoshop version (CC2014).
This is how the pdf file of an advertisement I need to insert into a brochure appears in photoshop. If I open it again, it will again render differently.
Btw, the screenshot or the pdf file previews fine when about to open it (in the Finder/folder).

Correction for above: 'Bit depth' not ' Bid depth'

PDF's are blank in Preview

I hope this is an appropriate place to post this question...
I have come across some PDF files that when opened in Preview are blank. The number of pages will be correct, but each page is blank. I can open these PDF's just fine using Adobe's Acrobat Reader, however I prefer to use Preview for its speed and simplicity. Does anyone have any idea why some PDF's are blank when opened using Preview? I want to note that one of the PDF's that I tried to open recently did not have anything special about (no forms, no extra JavaScript), it was just a plain old PDF. Any ideas?

A form has to be saved in Preview in order for it to be corrupted, not merely opened. What OS is used when opening a corrupted PDF in Reader/Acrobat doesn't matter.

Urgent help needed with iPhoto/pdf preview for book order - mysterious pixelated areas show on PDF but not in iPhoto

Hello. I ordered an iPhoto book last week to give to my parents for their 50th wedding anniversary. Tonight, I just checked on the order status and found that my book is cancelled. I received no notification about it, and all I could do was fill out the online form, so customer service will get back to me on Monday via email (if I'm lucky...). There is no telephone number for me to call about this. I decided I'd best do some searching to try to figure out what had happened.
I had thought that the preview I saw in iPhoto was the preview of the book. I found out I was wrong. So I created a PDF preview of the book and found some craziness that I don't understand. In iPhoto (and any other program, i.e. PhotoShop), my photos are fine. They are mostly TIFF format and high resolution with a few high res JPEGs. However, when I view the PDF, there is a band of black and white pixelation about 1/2-inch across the bottom of some pages - not all. The photos in that area are messed up in that band zone. The other photos are totally unaffected. This affects both TIFF and JPEG photos, and both black and white and color.
Has anyone else had this problem, and what was your solution? I would be extremely grateful to anyone for advice or information about this! The anniversary party is less than a week away and I'm beyond my limit of stress right now...

Launch iPhoto with the Option key held down and create a new library. Import enough photos for a book (use some of those in the current book) create a new book and preview as a PDF. If you don't see the problem then it's limited to your library which may be damaged. If that's the case make a temporary, duplicate copy of the library and try the two fixes below in order as needed:
Fix #1
1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your Home/Library/Preferences folder.
2 - delete iPhoto's cache file, Cache.db, that is located in your Home/Library/Caches/com.apple.iPhoto folder.
3 - reboot, launch iPhoto and try again.
NOTE: If you're moved your library from its default location in your Home/Pictures folder you will have to point iPhoto to its new location when you next open iPhoto by holding the the Option key. You'll also have to reset the iPhoto's various preferences.
Fix #2
Launch iPhoto with the Command+Option keys depressed and follow the instructions to rebuild the library.
Select the options identified in the screenshot and the option to rebuild the small thumbnails.
Click to view full size
If you get the same problem in the test library then log into another user account on your Mac, create a test library and try it there. If the problem shows up there a reinstall of iPhoto is indicated. To do so you'll have to delete the current application and all files with "iPhoto" in the file name with either a .PKG or .BOM extension that reside in the HD/Library/Receipts folder and from the /var/db/receipts/ folder,
Click to view full size
If you don't encounter the problem in the other user account then it's something in your account that's the culprit. Post back with the results.
OT

Links (urls) inside a pdf document are not enabled by the New firefox pdf preview feature but are in Chrome & IE

The new pdf preview feature in firefox desktop does NOT seem to activate any links (urls) inside the pdf meaning they are no longer clickable.
Is anyone else experiencing this problem.
I send out product information using pdf's with clickable links inside (as do lots of businesses) and this loss of clickable links functionality is a problem.
I also tried the same pdf files in IE and Chrome and their inline pdf previews keep all links fully working.
I know the pdf preview in firefox can be deactivated and the adobe reader can be used instead but in reality lots of people won't know how to do this or won't be troubled to find out how and will just move on.
Does anyone know if this feature is going to be fixed or supported or is it a deliberate security feature.
Thanks.
JP.

Hey JPEdwards,
The PDF.js team is still hard at work on the built-in viewer. It looks like there is already a bug on file for this and they are aware of it:
https://bugzilla.mozilla.org/show_bug.cgi?id=821599
Please don't post in the bug if you are just confirming that you've seen the problem too. That clutters the tickets ;)

My photos looked great but when I made a book they all appeared to be corrupted in the pdf preview?

My photos looked great but when I made a book in iphoto 09 they all appeared to be corrupted in the pdf preview? There is a white triangular shape with random horizontal lines running through each photo in the ibook preview. Took it to the Genius bar, after a week of fooling with it including wiping it clean and resinstalling the OS the same thing happens.

A LOT of them dont appear.
What do you see in the window when you click on those? A blank, black window? An exclamation mark? What?

Arabic letters are displayed as junk character in PDF preview

When we try to view (HFR Financial reports in PDF preview Arabic letters are displayed as junk character. While the same is shown correctly in HTML view.
Oracle EPMA version we are using 11.1.1.3, please provide some solution on this issue

This could help if you are connecting to essbase or planning:
1.Set the ESSLANG environment variable on the Essbase server to
ESSLANG= Arabic - Saudi Arabia (ISO)@Binary
2. In Financial Reporting, you must use the Essbase APS ADM driver rather then the Essbase Native ADM driver. Set the driver in \Hyperion\products\biplus\lib\fr_global.properties by setting the parameter
UseEssbaseEDS=1
3. In \Hyperion\products\biplus\lib\fr.env, set the ESSLANG environment variable as follows:
ESSLANG= Arabic - Saudi Arabia (ISO)@Binary
4. Re-start the Essbase and Financial Reporting services.

LaTeX composition in (g)vim with live update-as-you-type PDF preview

Ever since I tried the gummi LaTeX editor, I've been intrigued by the idea of having a live-updating PDF preview--i.e., a PDF output panel which updated as I typed. This provides all the good things of WYSIWYG, but without taking away the control I have by editing the source directly. However, apart from its preview panel, I was thoroughly unimpressed with gummi as an editor. It had none of the advanced features I was used to.
Since then, I've been trying various techniques to make it work with my preferred editor, (g)vim. At first, I used latexmk with the -pvc option which recompiles whenever the file changes, along with a PDF editor that refreshes whenever the file changes (like evince); but found it slow and tended to get stuck.
My current method is to use mupdf as my viewer, with a custom LaTeX script which calls xdotool to update mupdf whenever I have a successful compilation. This seems to be working fairly well.
Here's an animated GIF screen capture showing it in action
There is typically still a 1-second delay between typing something and it showing on the PDF preview, but it's not really any worse than it seems to be wih gummi, and I get to use a world-class editor.
I should note that I'm not using the vim-latex suite plugin or anything similar, so I don't know whether or not any of this is compatible.
Anyway, I thought I'd post my method here just in case anyone thought it useful, or more importantly, anyone had any feedback for how it might be improved. I'm not a programmer (--my degrees are in philosophy!--) and don't really have that much experience with vim or bash scripting, so forgive my naive methods.
Anyway, in my ~/.vim/ftplugin/tex.vim I have:
" Function to save, check if already compiling and compile if not
function! KKLtxAction()
" go to right directory
lcd %:p:h
" save the file if need be and it's possible
if filewritable(bufname("%"))
silent update
endif
" see how many kkltx processes there are
" note that there are always 3 when the checking itself happens
" so we need there to be no more than that
let numrunning = system("ps ax | grep kkltx | wc -l")
if numrunning < 4
exec "silent !kkltx " . expand("%") . " &"
endif
endfunction
" Call this function whenever mupdf the cursor moves
" But only in gvim
if has("gui_running")
au CursorMoved *.tex call KKLtxAction()
au CursorMovedI *.tex call KKLtxAction()
endif
So whenever the cursor moves, the file saves and checks if the compilation script is running. If it is not, it runs it. Here's the script, named kkltx. (To make it work, create a ~/.config/kkltx folder. Sorry about the stupid name; I needed it to be uncommon.)
#!/bin/bash
file="$1"
logfile="${file%.tex}.log"
auxfile="${file%.tex}.aux"
# check to see when file was last saved and
# check see what version of file was last compiled
currmodified=$(stat -c %Y "$file")
oldmodified=$(cat $HOME/.config/kkltx/lastprocessedfile)
# if they're the same exit with no change
if [ "$currmodified" == "$oldmodified" ] ; then
echo "nochange"
exit 0
else
# if compilation is necessary, check what program to use
# 'xelatex' should appear in first 5 lines for xelatex docs
if head -n 5 "$file" | grep -i -q 'xelatex' > /dev/null 2>&1 ; then
execprog="xelatex"
else
execprog="pdflatex"
fi
# try to compile
if ${execprog} -interaction=batchmode -file-line-error -synctex=1 "$file" > /dev/null 2>&1 ; then
# if compiling worked check if bibtex needs to run
if cat "$logfile" | grep -i -q 'undefined citations' > /dev/null 2>&1 ; then
if bibtex "$auxfile" > /dev/null 2>&1 ; then
if ! ${execprog} -interaction=batchmode -file-line-error -synctex=1 "$file" > /dev/null 2>&1 ; then
echo "failure"
exit 1
fi
else
echo "bibfail"
exit 2
fi
fi
# check if a rerun is necessary to update cross-references
if cat "$logfile" | grep -i -q 'rerun to get' > /dev/null 2>&1 ; then
if ! ${execprog} -interaction=batchmode -file-line-error -synctex=1 "$file" > /dev/null 2>&1 ; then
echo "failure"
exit 1
fi
fi
# update mupdf by sending the r key to it
xdotool search --class mupdf key --window %@ r > /dev/null 2>&1
echo "success"
# save time of compilation
echo -n "$currmodified" > "$HOME/.config/kkltx/lastprocessedfile" 2>/dev/null
else
echo "failure"
exit 1
fi
fi
exit 0
One thing you miss out on with mupdf is the SyncTeX ability in, e.g., TeXworks that allows you jump from the source to the corresponding part of the PDF and vice-versa. Here's a kludge that at least gets to you to the right page by using xdotool to send the signal to move to a certain page matching the source, or to read what page mupdf is on, and move to the beginning of the source code for that page (or strictly, a couple inches over and down). Again, in my ~/.vim/ftplugin/tex.vim
" \v to open the viewer
nnoremap \v :exec "silent! !mupdf ".expand("%:r").".pdf &"
" forward search with mupdf
function! MuPDFForward()
" make sure I'm in the right directory
lcd %:p:h
let pageforward = 0
" find where I am now; adjust for starting with 0
let searchline = line(".") + 1
let searchcol = col(".") + 1
" use synctex to find the page to jump to
let pageforward = system("synctex view -i " . searchline . ":" . searchcol . ":\"" . expand("%") . "\" -o \"" . expand("%:r") . ".pdf\" | grep -m1 'Page:' | sed 's/Page://'")
" if a page other than 0 is found, send the page number to mupdf
if pageforward > 0
call system("xdotool search --class mupdf type --window %1 \"" . pageforward . "g\"")
endif
endfunction
" inverse search with mypdf
function! MuPDFReverse()
lcd %:p:h
let gotoline = 0
" call a script which returns the line number near start of page shown on mupdf
let gotoline = system("syncreverse-mupdf.sh " . expand("%:p:r"))
if gotoline > 0
exec ":" . gotopage
endif
endfunction
" mappings \f and \r for forward and reverse search
nnoremap <buffer> \f :call MuPDFForward()<CR>
nnoremap <buffer> \r :call MuPDFReverse()<CR>
Here is the script syncreverse-mupdf.sh called by the above:
#!/bin/bash
# syncreverse.sh full-path-of-PDF-minus-extension
pathfn="$1"
# reduce filename to base, add .pdf
pdffile="$(echo "$pathfn" | sed 's@.*/@@g').pdf"
# change to directory containing files
cd "$(echo "$pathfn" | sed 's@$.*$/[^/]*@\1@g')"
# read page number in mupdf window title
page=$(xdotool search --class mupdf getwindowname | sed 's:.* - $[0-9]*$/.*:\1:')
# synctex lookup; remove junk
line=$(synctex edit -o "$page:288:108:$pdffile" | grep -m1 'Line:' | sed 's/Line://' | head -n1)
line=$(echo "$line" | sed -n 's/$[0-9]*$.*/\1/p')
# return line for gvim
echo "$line"
exit 0
I also recommend putting mappings in vim to send keys to mupdf to move around, so you can move around in the preview but without making (g)vim lose focus. These are just examples.
nnoremap <silent> <buffer> <C-PageDown> :silent! call system("xdotool search --class mupdf key --window %@ Page_Down")<CR>
nnoremap <silent> <buffer> <C-PageUp> :silent! call system("xdotool search --class mupdf key --window %@ Page_Up")<CR>
Anyway, these could definitely be improved, by, for example, accommodating master/sub-documents, and so on. Thoughts?
Last edited by frabjous (2010-11-04 22:41:21)

OK, I've uploaded a PKGBUILD to AUR. Since I've changed how it handles recognizing when it's safe to recompile, it no longer needs to have a weird name. The name is now:
vim-live-latex-preview
It comes with a very short vim help file, which I'll copy here.
*live-latex-preview.txt* For Vim version 7.3. Last change: 2010 Oct 27
*live-latex-preview*
A plugin for creating a live-updating PDF
preview for a LaTeX file in MuPDF
Default key bindings:~
\p = Begin auto-compilation and launch MuPDF preview.
\o = End auto-compilation and close MuPDF preview.
\s = Check the result of the last compilation;
jump to first error in case of errors.
\f = Forward search to page in PDF matching cursor
position in source.
\r = Reverse/inverse search to position in source
matching active page in MuPDF. (Very approximate.)
\<PageUp>, \<PageDown>, \<Up>, \<Down>, \<Right>, \<Left>, \G
\m, \t, \-, \+, \= = Send the corresponding keystrokes
to the MuPDF preview without losing focus on vim Window
The '\' can be changed by changing <LocalLeader>.
Be aware that your file is saved whenever the cursor moves. Be sure
to take the appropriate measures to keep back-up saves and undo files
so you can undo changes if need be.
To compile with XeLaTeX rather than PDFLaTeX, include the string
'xelatex' somewhere in the first five lines of your file (e.g., in a
comment). Currently only PDFLaTeX and XeLaTeX are supported. (Support
for LuaLaTeX and/or LaTeX > dvips > ps2pdf may be added in the future,
but they may be too slow for the live updating process anyway.)
The plug-in does not currently support master- and sub-documents
via LaTeX's \input{...} and \include{...} mechanisms. This may be
added in the future.
vim:tw=78:ts=8:ft=help:norl:
This is a new version; pretty much completely rewritten from the above. In particular, I've tried to incorporate keenerd's ideas; in particular some changes:
Rather than grepping the active processes, when it begins a compilation, it records the process ID of the compilation script, and will not begin a new compilation until that process finishes.
When it first launches MuPDF, it records the Window ID and sends it back to vim, so vim knows which instance of MuPDF to refresh or work with.
I've added a \s quick key which provides a one-word summary of the effects of the last compilation and jumps to the line number of the first error, if there were errors.
The script is located in a separate file in the main $VIMRUNTIME/ftplugin folder, rather than a user's tex.vim file.
I'm sure there's still plenty of room for improvement. I'd still like to get it to handle master/sub-documents well, for example. All comments welcome.

Acrobat Pro X PDF previewing not working in Windows 7 64-bit

Greetings, all,
The organization I work for recently purchased a volume license for Acrobat Pro X. We uninstalled Adobe Reader from all of our machines and installed Acrobat Pro X on them. After the move, the PDF preview handler stopped working. People commonly link to the URL below, but it has not worked for us. It appears it only works for the PDF preview handler packaged with Adobe Reader, not the one packaged with Acrobat Pro.
http://www.pretentiousname.com/adobe_pdf_x64_fix/index.html
Users are unable to preview PDFs in Windows Explorer and Microsoft Office Outlook 2007. When attempting to preview in Windows Explorer, the following appears:
This file can't be previewed.
What can we do to get the preview handler working in Windows Explorer (Windows 7 64-bit) and Office Outlook 2007?
Thanks in advance!

Bill@VT wrote:
OK. Then do you mean the thumbnails in Windows Explorer? I don't have a solution for that, but there have been several posts about the issue.
Well, thumbnails in Explorer don't work either, but we're not concerned about it. The preview pane is what we're worried about. There is a button in the top-right that turns the pane on. Previewing in Outlook does not work either.
Sabian Zildjian wrote:
Check the value for AppID in this registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{DC6EFB56-9CFA- 464D-8880-44885D7DC193}]
What do you have?
{534A1E02-D58F-44f0-B58B-36CBED287C7C}
DisplayName is set to "@C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\pdfprevhndlr.dll,-101".

How to open report.pdf file? getting error message file cannot be previewed pdf preview handler

how can I open a report.pdf file that shows error: file cannot be previewed because of an error w/ pdf preview handler

Hi pfmercerville,
If you are running the 64-bit version of Windows 7 (or Vista), you will find that your PDF files do not preview in Windows Explorer as they do in the 32-bit versions. Instead, all you see is a message stating that This file can’t be previewed. To enable this functionality on your 64-bit operating system, follow these steps.
1. Click the Orb (Start Button).
2. Go to the Search programs and files textbox and input regedit.
3. Select regedit.exe from the results.
4. When the UAC prompt appears, click the Yes button.
5. In the left pane of the Registry Editor, go to (and select): 
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{DC6EFB56-9CFA-464D-8880-44885D7DC193}
6. In the right pane, locate AppID.
7. Change AppID value to {534A1E02-D58F-44f0-B58B-36CBED287C7C}.
8. Restart your computer for the change to take affect.
Regards,
Rave

All my Adobe Reader (PDF) files are opening only in the secondary monitor by default, as I am workin

I am using Adobe 8 Professional and working on Windows XP. I have been facing an issue lately with opening files in a dual-monitor environment. All my Adobe Reader (PDF) files are opening only in the secondary monitor by default. There are times when I work only in one monitor and when I open a PDF file and want to have a look at it, I have to connect another monitor to view that file, since this file is open in the secondary monitor. It is very disappointing with such instances happening with Adobe (a leading organization). Can you please help so that the Adobe Reader files open in the primary monitor by default?

On a Windows system disable the preview of Windows Explorer.

Office web apps service pack 1 pdf preview

Hello Experts,
I have successfully installed and configured OWA Service pack 1 for a sharePoint farm, All office document preview works perfectly only for PDF files not to show preview, are there any special configuration to get this working in SharePoint 2013.
Thanks

Hi,
from Wictor blog
Before you start fiddling with this, you need to make sure that you have the March 2013 update of Office
Web Apps Server 2013 (WAC) installed and connected to your farm – if you don’t know for sure, ask your admins – sometimes
http://www.wictorwilen.se/sharepoint-2013-enabling-pdf-previews-with-office-web-apps-2013-march-2013-update
Kind Regards,
John Naguib
Senior Consultant
John Naguib Blog
John Naguib Twitter
Please remember to mark this as answered if it helped you

White border in pdf preview of bleed doc

Hi,
As the attached image shows I get a thin white border on my pdf preview of a document that has a 3mm bleed. I have tried to increase the bleed to 5mm but with same result. I've also tried to exceed the black background outside the bleed marks in InDesign - no result. The pdf is exported with document is generated I'm stuck. Why do I get this annoying thin white border when previewing the pdf document? The people I'm sending this to thinks its something wrong and even if this should turn out to be in preview mode only its ruining my work as everyone else is asking about it when looking at the pdf. Use Document Bleed settings is ticked.

You mentioned trying to increase the bleed areas by dragging the black box larger, but are you actually specifying the larger bleed when exporting the PDF
Also, you mention Bleed Marks rather than Crop Marks.
Crop marks show where the page will be trimmed and this is what the printer needs to see.
Bleed marks are essentially useless. they only show the edge of the bleed, but give NO indication where the printer should trim to
Your black screenshots are hard to decipher, but the Magenta box in your 2nd screenshot only shows the margins on the inside of the page.
Unless you have set the margins to 0, the magenta margin box will always be smaller that the page (the final trim size which is what the Crop marks are for)
Have you accidently set a Slug area larger than the bleed? This is only way I can get the white space to show.
The example below used greatly exaggerated settings to better show some issues.I greatly increased the bleed area to swallow the Crop marks and then included the Slug area to show the white.(slugs are not always used or even needed)
The Magenta box are the margins inside the page.
The Red box is the bleed area.
The Crop marks in between these two are what the printer need to cut on to produce the final page size.
Click on the image below to see a larger version with more detail.
P,S, you mentioned about not being able to print the bleeds. If you have bleeds and crops that will make the final PDF size larger than your desktop printer can print, just select FIT or REDUCE OVERSIZE PAGE in the print dialog and it will print on your printer. Of course it will not be to 100 scale, but it will show all the elements in the PDF.

Adobe PDF Preview Handler Issue in WIndows 8 64 Bit Machine - After installing Adobe Pro 11.0.10

Hi Guys ,
We are facing a serious issue with Windows 8 and Adobe PDF Preview Handler . We are using the PDFPrevHndlr.dll from Adobe to show PDF Previews in our application. It is working fine in Windows 7 and Vista and for some reason it is not working in Windows 8.1 64 bit machines after upgrading to Adobe Pro 10.0.10 . Please help us figure out what is the root cause of this issue .
During a close analysis we have found that the PrevHost.exe( Windows component ) is failing soon after it is being invoked . Any help in this is much appreciated.
Regards
Sree

Hi Sree,
According to your description, your case related to Adobe PDF Preview Handler. This is third-party product. I am afraid this is out of our support. Please ask in their special forum
https://forums.adobe.com/community/adobe_reader_forums
By the way, after do some search, it seems not working for 64bit machine,
>> It is working fine in Windows 7 and Vista
Also work fine in win7/vista 64bit????
If your scenario is not working in 64bit machine, try to put "adobe pdf preview handler 64-bit fix" in search engine. Good luck.
Have a nice day!
Kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

No PDF Previews are appearing

Similar Messages

Maybe you are looking for