Opening Document Error

Hi
I am unable to open any of the pdf documents on my desk top - I get this error message:
There was an error opening this document. The file is damaged and could not be repaired.

Hi
I am on a Mac air.. OS7 I believe and I have the most rent version of Adobe Reader. Unfortunately the pdf won't open at all if saved but I have been able to open pdfs that have been emailed to me. Any ideas??
Thank you!

Similar Messages

  • Cannot open document (Error: INF)

    We have migrated reports from version Business Objects 6.5.1 to Business Objects XI 3.1 SP2. We have been receiving sporadic 'Cannot open document (Error: INF)' now and again whenever you open Desktop Intelligence reports using Infoview. Have any other users come across this issue using BOXI 3.1 SP2. I do not believe that this issue occurred on SP1.
    This error is very frustrating.
    I have browsed various forums and implemented changes which have had no effect whatsoever including the SAP Marketplace.
    We are also receiving SetPrompts Failed errors. When a report is opened in Infoview and you refresh a report, a blank dialog appears with a red cross. if you refresh the report again then the SetPrompts Failed error appears. I have evene made changes according to article 1364437 based on this error and this has not resolved the issue.
    Regards
    Dipendra

    We're on BOXI3.1 SP2 aswell and we have had the same sporadic issue - Cannot open document for Deski reports. This is causing some serious concern amongst our users over system stability.
    You can recreate the situation by shutting down the InputFileRepository server and you get the same message. I've noticed that when this happens there is a mesage in the fcproc log file 'm_repFileMgr.Download failed'
    My theory is that there may be some congestion in linking between the desktopintelligence server and the inputfilerepository. In addition, we had some logging on the fileserver and at the time of the error there was no mention of the report that failed or any error. We contacted SAP about this but did not get a satisfactory response. There were some heavily utilised DESKi reports which we managed to convert to Webi to take the load off and we also dropped the timeout to 20 minutes (not brilliant but it did mean that if we got the message the users wouldn't have to wait too long before it was resolved in case they couldn't get hold of IT).
    I also upped the parameter for Maximum Retries for File Access in case it was having problems getting the file.
    The result of this was that the error appeared to go away... until yesterday!!!
    Any further insights welcome.

  • Cannot open document (Error: INF) / Session is closed (Error: INF )

    SAP BO XI3.1
    last time I face this one but suddenly disappear during testing, now we once again face this issue. As all users are member of group 'EveryOne' if we add any user membership to administrator group / master group this error resolved for this user.but that is not proper solutions, so far i m unable to find the rights which is lacking to all user for these report which are available in each user infoview and causing these errors while viewing.
    Open Document error message:
    While viewing Web Intelligence reports
    [Session is closed (Error: INF )|http://yfrog.com/0cwebirightsp|Session is closed (Error: INF )]
    While viewing Desktop Intelligence reports
    [Cannot open document (Error: INF )|http://yfrog.com/mjdeskirightsp|Cannot open document (Error: INF )]

    You might need to give read rights to the folder and category this report belongs to???
    If the problem is fixed when the user who is viweing is an administrator, this means there is insufficient privileges for the other users.

  • Flash5.5 "failed to open document" error message

    Yesterday I worked on two files both worked fine.  I saved my work and a backup. This morning I got the dreadful message "failed to open document" followed by the path to the file. The output panel gave me this message:
    The following JavaScript error(s) occurred:
    In file "/Users/lucilarios/Library/Application Support/Adobe/Flash CS5.5/en_US/Configuration/Javascript/ObjectFindAndSelect.jsfl":
    Cannot find file /Users/lucilarios/Desktop/Trabajo_Macondo3/ProjectAlgebra09/TutorialsAlgebra/Integers/Law sOfAddition/NewProject/AssocLawAdd.fla.
    The info on the file size shows 0 bites
    Both the file and its backup were corrupted.
    Are there compatibility issues betweenAdobe CS5.5 Programs and Mac OX Lion?  Lion has crashed my computer several times and other programs like Photoshop and Adobe Bridge have also misbehaved.  Has anybody experienced any issues with Lion and Flash?

    Hi ,
    I'm sorry for the inconvience . We are actively working on with customers in resolving this issue . 
    Please help us answer the following question below so we can reproduce this issue and provide some solution .
    About      the location where .fla file is being saved
    To a local drive? (eg. hard drive, SSD drive, USB key,       SD card, opened as email attachment, opened from a zip archive, etc)
    …or over a network? (eg. shared Windows folder across       Active Directory network, SMB share between OSX machines, symbolic       link/junction points to path) If so, do they have full file permissions       to write to that folder?
    The      .fla file before corruption/crash
    Reproducible from a new document?
    File history. eg. originally created in CS4, saved in       CS5 and re-saved in CS5.5
    3. Where was the backup copy saved ?
    4. Did flash crash y'day while you were saving your Fla file ?
    Can you please  email me your corrupt fla as well as any previous version of a working  backup copy if any to [email protected] .
    Thanks
    Sukhbir
    Flash Authoring

  • Error in Opening Document - error messgae as "First Define Numbering Series

    Dear All
    With new financial year starting one of our customer define new posting periods (12 periods for each month) and assigned one period indicator for all the periods. They also defined some user groups and assigned this groups to document numbering series for that user. Now while opening the document (e.g. Sales Order) for that user system displays the following message:
       "To generate this document, first define the numbering series in the Administration module"
    Therefore user can not open the document. Same procedure was followed in previous period also without any error.
    Please suggest procedure to be followed.
    Thanks & with regards
    Aloke Bandyopashyay

    Hi
    PLs find this link takes to you to authorization Document, as you said cant be given full authorization to all, But you should know proper knowledge before giving authorization bcoz all modules are interlinked. SO pls go through the document first :
    https://websmp208.sap-ag.de/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=701100035871000529280&_SCENARIO=01100035870000000183
    https://websmp208.sap-ag.de/~sapidb/011000358700001216762007E/HowTo_DefAut_2007A_B.pdf
    For to access Both u should have S user Id.
    Giridharan V

  • Pages 5.5.1 - Failure to create/open documents - Error message/App shutdown - Help

    Had this problem after updating to the new version.
    I've deleted and re-instaleld the app but the problem still exists.
    Any help would be greatly appreciated.

    Since you have Pages '09 documents it is safe to assume that you own Pages '09.  If you bought it from the App Store you should be able to download it again to your new machine.  If you have the install disks, you can install it on the new machine and the find the updater for it.
    Or you can go to the Apple Store (make an appointment) and get them to install iWork '09 on your machine.  They will do this for free if you can provide any proof that you owned it on your older machine.  They may do it for free anyway.
    As others said, your '09 files should open, so perhaps they were '08 files.  In which case you must open with '09 first.  For this reason Apple will sometimes give you a free version of iWork '09.  If you are not near an Apple Store try phoning them.  No guarantees, but others have reported that Apple sent them a free DVD.
    Worse comes to worse, look to buy it on Amazon or eBay, but try Apple first.

  • Getting "Cannot open document: error during import (DX0005" on DESKI report

    These reports use free-hand SQL and universe-based data providers. I'm thinking that a permission isn't set properly that is interfering w/ the import of the universe at execution time - any ideas where that might be?
    We use BObj XIr2 SP4
    Edited by: Jim Chickering on Aug 27, 2008 4:42 PM

    Hello Jim,
    Please post this query to the [BusinessObjects Desktop Intelligence |SAP BusinessObjects Desktop Intelligence;  forum:
    That forum is monitored by qualified technicians and you will get a faster response there.
    Also, all BusinessObjects Desktop Intelligence queries remain in one place and thus can be easily searched in one place.
    Thanks a lot,
    Falk

  • Discoverer Error - "Failed to open document"

    Hi,
    I'm having this wierd problem. Sometimes, I get a message "
    Failed to open Document" error on Discoverer 4 User edition. I
    cannot open the worksheet I create. It does not display any
    error code or message.
    Please advice

    I assume that you created the workbook in Discoverer Desktop and it does not work in either Plus or viewer. Does recreating the workbook under a new name correct the problem? IF not can you recreate the workbooks through Discoverer Plus and format the layout through the Discoverer Desktop. Does this fix the problem?
    Christopher
    www.iloveapple.com/disco/

  • Can't open document in InfoView, Rights not set properly?

    Hi Experts
    I think somewhere in one of BO's security layers I'm missing something...
    As a general user, with access level: Full Control, I cannot open a document in infoView...
    I get a Cannot open document (Error: INF)
    In the logs i find stuff like:
    .\kbolapp.cpp:1239:long __thiscall BOLApp::OpenDocument(const char *,struct _BOOpenDocStructure &,class BOString &,class BOString &,class BOString &): TraceLog message 1
    2011/09/08 08:16:22.054|>>|E| | 4984|7120| |||||||||||||||Document not yet opentd - open it
    SessionFacade.cpp:400:void __thiscall SessionFacade::checkAppViewRight(const class IRepoAccessTypes::SessionInfo &) throw(class RepoAccessException): TraceLog message 10
    2011/09/12 12:13:54.262|>>|E| | 4984|2836| |||||||||||||||in SessionFacade::checkAppViewRight at SessionFacade.cpp:400: sessInfo.isSystemRightGranted() failed for view right
    SessionFacade.cpp:379:void __thiscall SessionFacade::openSession(class IRepoAccessTypes::SessionSpec &,class IRepoAccessTypes::SessionInfo &) throw(class RepoAccessException): TraceLog message 11
    2011/09/12 12:13:54.293|>>|E| | 4984|2836| |||||||||||||||in SessionFacade::openSession at SessionFacade.cpp:379: got exception: [repo_proxy 13] Application has no view rights
    SessionFacade.cpp:84:void __thiscall SessionFacade::openSession(class IRepoAccessTypes::SessionSpec &,class IRepoAccessTypes::SessionInfo &) throw(class RepoAccessException): TraceLog message 12
    2011/09/12 12:13:54.293|>=|E|X| 4984|2836| |||||||||||||||Uncaught Exception in SilentScope: cdzSessionFacade:openSession: 0.266
    .\kbolapp.cpp:1045:long __thiscall BOLApp::InternalLogon(struct _BOOpenDocStructure &): TraceLog message 13
    2011/09/12 12:13:54.340|>>|E| | 4984|2836| ||||||||||||||| BOLApp::InternalLogon() failed!
    SessionFacade.cpp:400:void __thiscall SessionFacade::checkAppViewRight(const class IRepoAccessTypes::SessionInfo &) throw(class RepoAccessException): TraceLog message 14
    2011/09/12 12:13:54.481|>>|E| | 4984|2836| |||||||||||||||in SessionFacade::checkAppViewRight at SessionFacade.cpp:400: sessInfo.isSystemRightGranted() failed for view right
    SessionFacade.cpp:379:void __thiscall SessionFacade::openSession(class IRepoAccessTypes::SessionSpec &,class IRepoAccessTypes::SessionInfo &) throw(class RepoAccessException): TraceLog message 15
    2011/09/12 12:13:54.481|>>|E| | 4984|2836| |||||||||||||||in SessionFacade::openSession at SessionFacade.cpp:379: got exception: [repo_proxy 13] Application has no view rights
    SessionFacade.cpp:84:void __thiscall SessionFacade::openSession(class IRepoAccessTypes::SessionSpec &,class IRepoAccessTypes::SessionInfo &) throw(class RepoAccessException): TraceLog message 16
    2011/09/12 12:13:54.496|>=|E|X| 4984|2836| |||||||||||||||Uncaught Exception in SilentScope: cdzSessionFacade:openSession: 0.156
    .\kbolapp.cpp:1045:long __thiscall BOLApp::InternalLogon(struct _BOOpenDocStructure &): TraceLog message 17
    2011/09/12 12:13:54.496|>>|E| | 4984|2836| ||||||||||||||| BOLApp::InternalLogon() failed!
    .\kbolapp.cpp:1525:long __thiscall BOLApp::InternalOpenDocument(struct _BOOpenDocStructure &,bool): TraceLog message 18
    2011/09/12 12:13:54.512|>>|E| | 4984|2836| |||||||||||||||BOLApp::InternalOpenDocument ERROR1
    SessionFacade.cpp:400:void __thiscall SessionFacade::checkAppViewRight(const class IRepoAccessTypes::SessionInfo &) throw(class RepoAccessException): TraceLog message 19
    2011/09/12 12:13:54.653|>>|E| | 4984|2836| |||||||||||||||in SessionFacade::checkAppViewRight at SessionFacade.cpp:400: sessInfo.isSystemRightGranted() failed for view right
    SessionFacade.cpp:379:void __thiscall SessionFacade::openSession(class IRepoAccessTypes::SessionSpec &,class IRepoAccessTypes::SessionInfo &) throw(class RepoAccessException): TraceLog message 20
    2011/09/12 12:13:54.668|>>|E| | 4984|2836| |||||||||||||||in SessionFacade::openSession at SessionFacade.cpp:379: got exception: [repo_proxy 13] Application has no view rights
    SessionFacade.cpp:84:void __thiscall SessionFacade::openSession(class IRepoAccessTypes::SessionSpec &,class IRepoAccessTypes::SessionInfo &) throw(class RepoAccessException): TraceLog message 21
    2011/09/12 12:13:54.668|>=|E|X| 4984|2836| |||||||||||||||Uncaught Exception in SilentScope: cdzSessionFacade:openSession: 0.156
    .\kbolapp.cpp:1045:long __thiscall BOLApp::InternalLogon(struct _BOOpenDocStructure &): TraceLog message 22
    2011/09/12 12:13:54.668|>>|E| | 4984|2836| ||||||||||||||| BOLApp::InternalLogon() failed!
    As an administrator I can open the document in InfoView... Bot the general user and teh administrator have Full Controll access level on the folder containing the document...
    Any Ideas ?
    Thanks in advance !
    P
    By the way, when i create a report and I try to open it as the general user, I get a Session is closed message... Again, it works as administrator... What am I doing wrong?
    Edited by: PGeudens on Sep 12, 2011 4:54 PM

    Its definitely a rights issue... Migrated security is a spiderweb...
    I've re-imported everything without the security settings... Where do I start, giving people rights to the reports they need to see??? Don't have any knowledge on Universe security and I think that is the problem...
    Can someone post me all necesary rights one must have to refresh data in a report? It would be nice if you also mention the collection and the type besides the right name...
    Thanks in advance !!
    P

  • Document Creation error - "We're sorry. We can't open document name because we found a problem with its contents"

    Morning Friends,
    I have created a SharePoint 2010 "Site Workflow" that is designed to take information from a form and create a Word doc with the gathered information and store this Word doc in a document library.
    I am using Sharepoint 2013 with Office 2013 
    I understand there are a lot of steps (19) outlined below and I can provide more information as needed but the bottom line is this, workflow successfully takes info from an initiation form, uses the info to create a Word doc. Places this Word doc in a library.
    When attempting to open / edit doc, receive error
    "We're sorry. We can't open <document name> because we found a problem with its contents"
    Details - No error detail available.
    Any info or advice would be greatly appreciated. 
    Very high level view of what I have done:
    1 - Created content type called "Letters"
    2 - Added site columns " First Name" and "Last Name"
    3 -  Created and saved to my desktop a very basic Word document (Letter.docx) that says "Hello, my name is XXXX XXXX"
    4 - In the advanced settings of the "Letters" content type I uploaded this "Letter.docx" file as the new document template.
    5 - Created a new document library called "Letters"
    6 - In Library Settings - Advanced Settings, clicked "Yes" to enable the management of content types.
    7 - Then I clicked "Add from existing content types" and added the "Letters" content type
    8 - Back in the advanced settings of the "Letters" content type I selected "Edit Template" and replaced the first XXXX with the Quick Part "First Name" and the second XXXX with the Quick part "Last Name"
    9 - Created a new 2010 Site workflow called "Create a Letter"
    10 - To the workflow I added the action "Create List Item"
    11 - Configured the action to create Content Type ID "Letters" in the document library "Letter" 
    12 - For the "Path and Name" I gave it a basic name of "Letter to"
    13 - The next step was to create the Initiation Form Parameters and added to form entries "First Name" and "Last Name"
    14 - I then linked the initiation form fields to the data source "Workflow Variables and Parameters" to their respective Field from Source parameters
    15 - Went back to the "Path and Name" and modified the basic name of "Letter to" to include the first and last name parameters.
    16 - Saved - published and ran the work flow.
    17 - As expected, Initiation Form prompts for First and Last Name. ("John Doe") Then click "start
    18 - Go to document library "Letters" and see a new Word document created titles "Letter to John Doe" 
    19 - Go to open / edit the Word document and receive the following error
    thoughts? Any info or advice would be greatly appreciated. 

    See this MS support article for SP2010 workflows and generating Word docs:
    https://support.microsoft.com/kb/2889634/en-us?wa=wsignin1.0
    "This behavior is by design. The Create
    List Item action in the SharePoint
    2010 Workflow platform can't convert Word content type file templates to the correct .docx format."
    I've had success in using SP 2013, Word 2013 (saving a .docx as the template instead of .dotx for the document library content type), and an SP 2010 workflow using SP Designer 2013.

  • Web Analysis 9.3.1: Error occured while opening document. Document ID = {0}

    Hi Experts,
    I am having an issue while opening a web analysis dashboard report. When I try opening it, web analysis runs for about 15 mins & then throws following error:
    Error occured while opening document. Document ID = {0}
    The report opens with its header having company log & two buttons, but data grid remains empty.
    The source of Grid is Essbase. The tunning parameters in Essbase.cfg file are in place.
    Could anyone please through more observation on this issue. Let me know if any further information is needed!.
    Kindly suggest me any way to resolve it.
    Thanks,
    Krishan

    The isapi (if you use one) timeout setting might be smaller than the time essbase needs to retrieve te information.
    but most probably the analysis applicationserver jre heapsize is either to small or needs to much time to allocate it. Be sure to increase heapsize and set max equal to min (try 800mb, if your hardware has that resource)

  • WebAnalysis Error: Error occured while opening document. Document ID = {0}

    Hi Experts,
    I am having an issue while opening a web analysis dashboard report. When I try opening it, web analysis runs for about 15 mins & then throws following error:
    Error occured while opening document. Document ID = {0}
    The report opens with its header having company log & two buttons, but data grid remains empty.
    Kindly suggest me any way to resolve it.
    Thanks,
    Krishan

    Hi Natesh,
    Thanks for your reply to my query posted in this forum. Please find my inline answers between asterisk to your questions:
    Whatz the source of your Grid? Relational SQL Query (OR) A spreadsheet with Essbase database connection file?
    * Yes, the source is Essbase.*
    If source is Essbase, it seems- Outline might've got altered when you're trying to refresh the report.
    * The outline was in tandem when we tried running this report in WebAnalysis. This outline & WebAnalysis report which is in Dev Server is a replica of the one in Test Server where it runs fine. *
    If source is based on a Relational SQL query, chances are that- Query is no longer valid.
    * NA as this statement is NOT applicable to our source.*
    If it's Essbase, it's also likely that- It ran out of time while fetching the data from Essbase. You may try playing around with the parameters in Essbase.cfg file.
    * This might be one of the causes, but I double checked the all the tunning parameters in Essbase.cfg file in place.*
    Could you please through more observation on this issue. Let me know if any further information is needed!.
    Thanks for your time.
    Regards,
    Krishan
    Edited by: user10475612 on Nov 8, 2009 1:07 PM
    Edited by: user10475612 on Nov 8, 2009 1:09 PM
    Edited by: user10475612 on Nov 8, 2009 1:12 PM

  • Error with single quotes in open document function

    Hi all,
    I have an issue with the special characters using the open document function. I'm passing a name, and I'm using the URLEncode function, but it doesn't work for single quotes, it shows a javascript error. I tried with HTMLEncode and it works for single quotes, but not for the other special characters like @,+. I tried with both functions at the same time but it doesn't work either.
    Please let me know if you know how to solve it.
    Thanks,
    Marcela

    Hi Prashant,
    I did not work it works for single quotes only, but not for other special characters.
    This one doesn't work for single quotes
    ="<a href='../../scripts/openDocument.aspx?sType=wid&sDocName=Report_Name&sWindow=NEW&sReportName=Company Details&lsSPartner Id=" + [Partner Id] +"&lsSPartner Name=" + URLEncode([Partner Name]) +"'>View catalog</a>"
    This one doesn't work for special characters
    ="<a href='../../scripts/openDocument.aspx?sType=wid&sDocName=RP-DSPP-Company_Catalog_CORETEAM&sWindow=NEW&sReportName=Company Details&lsSPartner Id=" + [Partner Id] +"&lsSPartner Name=" + [Partner Name] +"'>View catalog</a>"
    Thank you,
    Marcela

  • While trying to open document getting error msg

    Hi
    While i am trying to open document thru cv03n it sending error messsage please help.
    File c:\temp\_10097601.doc cannot be created
    Message no. 26172

    Hi,
    IF the issue is user specific: Please check the access rights in C:\ folder.
    If the issue is common: Check the RFC connection and ensure the test results are in green.
    If the PROD system was working properly earlier and you face the issue suddenly: Check the port setting (Check with the server team-They may lock the port some times during upgrade/Maintenance).
    If your issue not solved send the connections screen shots.
    Rgds,
    Nayeem.

  • "...not a valid Photoshop document" error when opening Mac cc file on PC

    I get a "Could not complete your request because it is not a valid Photoshop document." error message whenever I try to open up a PSD file created on a Mac using Photoshop CC on my PC using CC. Other people have been able to open the file from the same location, so the files aren't corrupted. Anyone know how to fix this?

    I know this thread is a bit old, but I wanted to share my experience and solution in case anyone else runs into this.
    The other day, I spent many hours editing some photos for a client. I saved them all and closed Photoshop. When I tried to open the .PSDs, they all came up with this "Not a valid Photoshop document" error. I was freaking out. I could see the thunmbnails and previews with the MacOS Finder and could see the images just fine in Lightroom, but couldn't open them in Photoshop CC.
    Finally, I remembered that these were NOT supposed to be .psd files! They were supposed to be TIFFs. What happened was, when I edited them from within Lightroom into Photoshop, they opened as TIFFs. However, when I did "save as", I wanted to name them similarly to some other files I had. I clicked on one of the existing files to copy the file name in the Save As dialog to make it easier to name the new file I was saving, but I didn't realize it was changing the file extention from ".tif" to ".psd" as well. The older MacOS (version 9 and earlier) didn't rely on file extensions fo identifying file types, so it didn't hit me right away that this would be the problem. When I changed the incorrect .psd file extension to .tiff, the files opened in Photoshop just fine.
    SO... if you run into this "Not a valid Photoshop document" error, try figuring out if it's actually another file type (.jpg, .tif, .png, etc) by either getting the file info from another program or just experimenting with different file extensions. Chances are good that your file isn't actually corrupt, but just named improperly!

Maybe you are looking for