I have a weird problem with viewing PDF files.
I have a menu button on a windows forms application that opens up a form with a PDF viewer. This works absolutely perfectly in the majority of cases, however I have one user who is experiencing problems.
It seems to work but them it will suddenly refuse to load the document and just shows a grey screen. She also has problems when printing from this form.
I have investigated this issue and I cant reproduce this is the dev environment.
The only possible reason I can see is that she is using something called "Nitro reader" rather than the standard Adobe viewers which we tested on.
Could this be the cause of this intermittent error or are there other known issues with the PDF viewer in C#?
I know this question is a long shot but I am hoping someone else will have come across a similar issue.
I am using .net 4 with VS2010 and I am using PDF sharp to generate the document.
Thanks
Related
I have this popup window showing on my website in Firefox.
It is indeed a system window displayed by the browser, not by the page.
There is no useful information in the console.
What may cause it and what can I do about it?
I encountered this today. It came from window.Muse.assets.check being unable to verify some script in a list of those required. I believe that this is Adobe Muse, which appears to be a library of widgets (like slideshows and effects).
Last week I tried to update my Notes client installation from 9.0.1 FP9 to FP10 IF 3. For technical reasons I had to roll back which proved to be quite difficult, and I ended up completely uninstalling Notes and doing a fresh installation of 9.0.1 (standard) then FP9 IF 2.
Everything's fine (and much more responsive than before, too) with one serious exception:
Within the client help popup window for Notes client and Domino Designer help is hardly usable now; obviously there's no CSS style or whatever applied to the nav page / frame:
As you can see in the screenshot styling of the main window part (green frame) is fine. But everything that is releated to navigation (red frames) appears to be raw html. Javascript calls are apparently working but it's really hard to navigate the "chapters". Same applies to Designer help, of course.
Here's what I tried to solve that riddle:
uninstalled and re-installed full client 3 times; sometimes I ran the
installation as local Admin other times I didn't (no difference)
just installed plain Notes 9.0.1 from scratch then tested Client help before updating to FP9IF2 (no difference)
restored the entire [Notes-Programm]\framework directory from a
backup I took when Notes help still was working as expected (no difference)
copied over the entire \Notes\ folder from a different PC where popup help is still working fine (no difference)
Problem with that is: being a Developer I need to have a functioning help window in my Domino Designer. The navigator as it is right now however is plain useless. And designer_help.nsf isn't of help at all when it comes to Java, LotusScript etc. objects and classes.
One of my co-workers has the same phenomenon while another one hasn't.
Question: did anyone else experience something like that? Where you able to solve it? How?
This seems to be related to an issue with the embedded browser windows that Domino Designer uses to open the Help website.
Try to open following link in a modern browser (such as Chrome or Firefox) and the navigation should be fine.
http://localhost:50970/help/index.jsp?topic=%2Fcom.ibm.notes.help.doc%2Ffram_getting_started_c.html
Bookmark it and use it when you need it.
Try using the IBM Nice tool to see if it can fix your issue
https://www-01.ibm.com/support/docview.wss?uid=swg21459714
Meanwhile I restored my entire Windows system partition from a backup created just before all that began (lucky me that I have both regular local backups plus a separate system partition). And that finally helped resolve the problem.
Meanwhile I'm 99% sure that this is due to a rather new registry and/or firewall setting not yet known to IBM's NICE tool.
Firstly let me state that I have zero experience with Sharepoint so this may be a pretty stupid question.
I started a new job yesterday and part of the induction is viewing the company literature via their Sharepoint portal. I've noticed that whenever I try to access an embedded PDF link via Chrome it seems like it's a broken link and appears to do a Google search instead. Yet when I try the exact same steps using IE all works as expected.
I don't want to raise this with my boss if it's going to make me look a little stupid! Is there some cross browser issue with PDF links?
Thanks.
Darren, try flushing the cache in Chrome, and if necessary, log off and log back into your computer. We've had the same problem with Chrome and Google doesn't seem to be fixing the problem (although they might point the finger back at Microsoft).
Yes I have the same issue with Chrome and Firefox
Sharepoint is optimized for IE and vice versa
You also can't open Files with the "Check in and Check out" functionality because only IE is able to do that from Sharepoint (Other Browsers will just Download the File)
You can try using AddOns like IE-Tab
(simply uses the IE algorithms within FF and Chrome for specific Sites)
But its better to use Sharepoint with IE
I have two servers with virtually identical setups (the second that is working has been around longer than the other). For my newer server when I just put an address to a PDF in the browser it launches a download dialog. If I put the same address (just changing the server name) in the browser to my older server it displays in the browser just fine. There is no difference between the files themselves. The issue is I want to display these pdfs in an iframe on a page and the same thing is happening with the iframe (the new server launches a download instead of the pdf just showing in the frame).
Any ideas would be most appreciated!
Once I started looking into SP 2010 as being the cause I found that there is a default setting for all new 2010 sites that causes this issue. The following blog post had the most complete information on the subject:
http://nerdtastictips.blogspot.com/2010/08/sp2010-forces-users-to-save-pdfs.html
Please indicate web server your are using
Initial suggestion may be this has to do with MIME-TYPE setup
Sometimes the style sheet disappears when naviguating on our WSS 3.0 sites (white background on the site, no colors, no formatting, etc.). This has mainly happened with IE6 (corporate browser for the majority of our computers). The fixes were :
clean up temporary internet files
if it still doesn't work, upgrade to IE 7
However, this time, the upgrade to IE 7 hasn't worked, the style sheet isn't applied. When we clean up temporary internet files, things go back to normal, but after a while the css disappears again.
Here are a few ideas on what you could try:
Fiddler should be able to tell you if there is a network problem.
Check the HTML for anything unusual. Is it malformed in any way? Can you save a copy and run it through an online validator (although this is limited in use as SharePoint's default markup isn't compliant).
If some users are having the issues but others aren't, check their permissions on the server.
You could also try using the SharePoint "Log in as another user" feature to see if the problem can be reproduced on your machine when logged in as them. You may also want to try running Internet Explorer as that user.
Check the Event Viewer on both client and server for anything unusual.
Check the IIS logs on the server for any errors.
Check the SharePoint ULS logs on the server in the "12 Hive" for errors that might be related to this problem.
Try running Process Monitor on the client and reproduce the problem. Search for keywords such as FAIL or ERROR to see if anything appears. Make a note of the time the problem occurs and see if the Process Monitor logs give any additional information.
Is there some javascript that's involved as well? Could it be a virus scanner that is set way to strict? As you pointed out in one of the comments, the CSS isn't even being requested (at IIS log level, which is as basic as you get, not even in SHarePoint yet), so it HAS to be something on the client PC.