On file open: "This document contains JavaScript code for a widget that no longer exists."

I had an existing, functional datepicker in a web page.
Recently I downloaded the UI Datepicker in the Widget Browser and installed it in DW CS5. Now every time I load the file that calls the datepicker that I added myself, a warning opens with the following text:
This document contains JavaScript code for a widget that no longer exists. If you don't remove the code, the browser might display JavaScript errors when loading the page. Would you like Dreamweaver to find all instances of this code for you?
Widget: $("#reservDateBegin").datepicker();
Widget: $("#reservDateEnd").datepicker();
Clicking "Yes" opens the file and shows the search box at the bottom of the window with [current document] in File and $("#reservDateEnd").datepicker(); in Matched Text. Clicking "No" just opens the file.
The error is wrong, since installing the widget is what caused the error in the first place!
How can I get DW to stop showing this message?
Thanks for any help.

I do understand you're trying to be helpful. I was just hoping providing the relevant code snippets would be sufficient so I didn't have to take the time to provide a "cleaned" version of the files and upload those to a public-safe location.
Zabeth69 wrote: If you don't understand what 'code at the bottom of the page' means, you have not used one of those systems. I don't know what causes the error code to come up (besides removing a Spry widget, I mean). So if it doesn't apply to you, ignore it.
This is exactly my point: I haven't used any of the DW "systems". I've always manually coded in DW, so I can't have removed a Spry widget in the first place. It wasn't until I installed the Widget using the Widget Browser that I started getting the error (I don't mean adding the datepicker widget to the code using the DW Insert menu - I mean installing the Widget into DW itself). Ignoring such an erroneous/incorrect error seems kind of silly, since every time I open the file I get the error message.
Anyway, as requested, the following are links to the contactUsCleaned.php page, and the php included headerCleaned.php file. Since these use php includes to complete the rendered HTML, they won't look right in the browser, but as you know viewing the source will show the relevant html, javascript, and jquery code. I didn't see any way to upload the files in this forum, which, due to the php code, would be preferable to see exactly what my code looks like...
http://www.eventidewebdesign.com/public/contactUsCleaned.php
http://www.eventidewebdesign.com/public/headerCleaned.php
The footer.php file the contactUs page includes is simply a set of HTML links to the pages on the site, copyright info, and the Google Analytics script. There is no other code in the footer.php file.

Similar Messages

Security code sent to email that no longer exists

Hi
I have recently moved jobs and my email address no longer exists - I cannot log onto my SKYPE account without a new password which is being sent to my old email address - please help urgently!
THANK YOU!

please contact Skype customer service

Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example,\ /).

I recently upgraded to a new Macbook Air running Lion, from my 2007 white Macbook running Snow Leopard. I had Office for Mac 2004 on the 2007, but had to upgrade to Office for Mac 2011 to be compatible with Lion on the Air. Now when I try to open my documents on the Air that were saved under Office 2004 on the old computer, I get the following message: Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example,\ /).
Any suggestions? Thank you.

Ha,ha,ha.....I figured it out. But for anyone else who's having this problem, it seems that while Office 2004 allowed dates in this format: 00/00/00, Office 2011 doesn't like it at all. I just changed the format in the document names to 00-00-00 and all is well. Documents are opening beautifully!

Opening an external file containing javascript code

I'm trying to develop a PDF in two languages. When pushing a button, all questions and list-of-values for possible answers should be translated.
I created and initialized several variables with the two language phrases with javascript. Everything is inside my code.
Is there anyway that when a button is pressed an external file is read, bringing that javascript code for questions ans list-of-values? My concern is that currently I have a duplicated code, but if I want to implement three, four languages it will grow without control.
This is an example I wrote in my code:
var TxtAuxL1ESP = new Array();
var TxtAuxL1ING = new Array();
TxtAuxL1ESP[0]=", como ";
TxtAuxL1ING[0]=", such as ";
TxtAuxL1ESP[1]=": el último año ha obtenido ";
TxtAuxL1ING[1]=": last year it obtained ";
TxtAuxL1ESP[2]="%, en los últimos tres años ";
TxtAuxL1ING[2]="%, in the last three years ";
TxtAuxL1ESP[3]="% y en los últimos cinco años ";
TxtAuxL1ING[3]="% and in the last five years ";
if (P1.BtnIdioma.border.edge.stroke == "raised") {
    var TxtAuxL1=TxtAuxL1ESP;
    var TxtAuxL2=TxtAuxL2ESP;
    var TxtAuxL3=TxtAuxL3ESP;
else {
    var TxtAuxL1=TxtAuxL1ING;
    var TxtAuxL2=TxtAuxL2ING;
    var TxtAuxL3=TxtAuxL3ING;
What I was thinking is to store TxtAuxL1ING in one file, TxtAuxL1ESP in another file and read them from my javascript code inside the PDF. Is it possible?
Regards
JC

Hi,
maybe this solution ist interesting for you.
It populates form fields with data read from an attached XML file.
http://thelivecycle.blogspot.de/2011/01/populate-data-from-attachment.html

Another "there was an error opening this document. this file cannot be found"-question

Hello people, as the title suggests, i have another question regarding the "there was an error opening this document. this file cannot be found" error. I have searched on Google and on these forums but i havent found an answer to my particular case (sorry if i overlooked it).
I work at a supportdesk for a company that uses Windows XP with Adobe Reader version 8.1.3.
Users are getting this error when they access a PDF file placed on a (mapped) networkdrive. Contrary to some other cases i have found on this forum, spaces are handled without a problem. But a comma in the name of one of the folders that contain the PDF file are what causes this error.
i.e.:
Opening the following path results in the error:
L:\X, Y & Z\adobe.pdf
Removing the comma so the path becomes:
L:\X Y & Z\adobe.pdf
works just fine.
So far our workaround has always been to simply remove the comma and move on, but I've been wondering why this comma is such a problem for Adobe Reader. As far as i know Adobe Reader is the only program we use that has this issue, M$ Word works just fine with it to name an example.
To sum my questions up:
- Why is comma (,) a problem for Adobe Reader?
- Have i missed any patches/new versions where this issue has been addressed?
- What is Adobe's stance on this, and are there any plans to "fix" this?

Ok, nevermind, we just found the problem
It's not Adobe Reader that is causing this, but another program the company uses to manage/distribute/authorise programs that users are allowed to access (Scense). I had never even considered another problem could have caused this for Reader.

SSRS PDF Export. There was an error opening this document. This file is damaged and could not be repaired

Hello,
I just experienced this problem, and was able to successfully mitigate. I wanted to share my experience and Solution.
The problem started with the following error after succesfully exporting a PDF Document. "There was an error opening this document. This file is damaged and could not be repaired."
This is only applicable if you can still export and open SSRS Reports to other formats. Go to the Log files of the SQL Instance. In my particular case I used the Default MSSQL instance: C:\ Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting
Services\LogFiles
The Folder will begin with MSRS (SRS is for SQL Reporting Services)
Sort the files by date modified and check for the most recent log file: ex. SQLDmpr0000.log The 0000 will be the incremental amount of errors you have experienced in SRS. Check for the following error:
"System.DllNotFoundException: Unable to load DLL 'T2Embed': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"
Below is a sample from the log.
reportrendering!ReportServer_0-1!1b78!02/07/2012-11:56:03:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: , Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException:
An error occurred during rendering of the report. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.DllNotFoundException: Unable to load DLL 'T2Embed': Access
is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
   at Microsoft.ReportingServices.Rendering.ImageRenderer.FontPackage.TTGetEmbeddingType(Win32DCSafeHandle hdc, UInt32& status)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.FontPackage.CheckEmbeddingRights(Win32DCSafeHandle hdc)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFWriter.ProcessFontForFontEmbedding(PDFFont pdfFont, Dictionary`2 embeddedFonts)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFWriter.EndReport()
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFRenderer.Render(Report report, NameValueCollection deviceInfo, Hashtable renderProperties, CreateAndRegisterStream
createAndRegisterStream)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo,
NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
   --- End of inner exception stack trace ---
   at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo,
NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderFromOdpSnapshot(IRenderingExtension newRenderer, String streamName, ProcessingContext
pc, RenderingContext rc)
   --- End of inner exception stack trace ---;
If you notice the error states that T2Embed.dll access is denied. In my case this due to a hotfix installed by Microsoft:
MS11-087: Vulnerability in Windows kernel-mode drivers could allow remote code execution: December 13, 2011
Be advised, in order to fix your problem and render pdf's, a vulnerability shall be created.
To fix this issue and allow the export to PDF work correctly, you must give the system Read/Execute Permissions, and Built-in\Administrators Full Control.
Go to Windows\System32 and find the T2Embed.dll Go to Security and modify the permissions as listed above. Do the same to the T2Embed.dll in the SysWow64 folder.
Restart Reporting Services and you will be able to export to PDF.
Best Wishes!
Mariano
www.lucontech.com

I'm not convinced this is the exact cause of the issue. I will check my log files to see if I find anything like what you described. However, I get this error when a particular user tries to do a "print preview" from a custom button. The
code builds a ReportViewer object, sets the ReportPath, etc.
The reason I'm not convinced is because we have a separate reports page that has the report viewer embedded into it. If the user generates the report that way and exports to PDF, Word, etc...the user can generate the file and be on their way. As
soon as the user clicks our "Print" button on the page without the ReportViewer embedded, the above mentioned error occurs.
UPDATE: Perhaps we have a different problem since my issue is from a custom button. I found the solution
here and confirmed the solution with the customer. It had to do with the code using Response.Flush() instead of Response.End().
One thing I noticed before I implemented the change: When you would close the PDF, it would ask you to save changes to the PDF. After implementing Response.End() instead, that prompt went away. No doubt it has to do with the differences between
how Response.Flush() and Response.End() handle the stream returned.
Anyway, posting in case someone has the same issue.

When I attempt to open a PDF file I saved from a website, I get the message "There was an error opening this document. The file is damaged and could not be repaired." Is there any way to correct this problem?

When I attempt to open a PDF file I saved from a website using Safari, I get the message "There was an error opening this document. The file is damaged and could not be repaired." When I save the same PDF file using FireFox it opens up immediately. Is there any way to correct this problem with Safari?

Back up all data.
Triple-click the line of text below to select it, the copy the selected text to the Clipboard (command-C):
/Library/Internet Plug-ins
In the Finder, select
Go ▹ Go to Folder
from the menu bar, or press the key combination shift-command-G. Paste into the text box that opens (command-V), then press return.
From the folder that opens, remove any items that have the letters “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari, and test.
The "Silverlight" web plugin distributed by Microsoft can also interfere with PDF display in Safari, so you may need to remove it as well, if it's present.
If you still have the issue, repeat with this line:
~/Library/Internet Plug-ins
If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari again.

With OSX10.7.5 and Adobe Reader 11.0.02 when I try to open a PDF downloaded from the web I get 'There was an error opening this document. This file is damaged and could not be repaired. Preview will not open either. Older PDFs OK.

I am running OS X 10.7.5 and Adobe Reader 11.0.02. In the last few days I have been unable to open PDF's downloaded from the web. Reader gives the error message 'There was an error opening this document. The file is damaged and could not be repaired'. Removing Reader and trying to use Preview to open these files give the error 'Preview cannot open this file. It may be damaged or use a file format that Preview doesn't recognise' (or something like that). Downloading the same files with Reader removed from my Mac Preview opens the files OK.
I was recently prompted to update Adobe software but did not note exactly what the update was nor when it was done.
Reader and Preview will both open PDFs I downloaded a week ago. Reader will also open files downloaded on another Mac running OS X 10.0.0 and copied to my Mac. Any ideas?

Back up all data.
Triple-click the line of text below to select it, the copy the selected text to the Clipboard (command-C):
/Library/Internet Plug-ins
In the Finder, select
Go ▹ Go to Folder
from the menu bar, or press the key combination shift-command-G. Paste into the text box that opens (command-V), then press return.
From the folder that opens, remove any items that have the letters “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari, and test.
The "Silverlight" web plugin distributed by Microsoft can also interfere with PDF display in Safari, so you may need to remove it as well, if it's present.
If you still have the issue, repeat with this line:
~/Library/Internet Plug-ins
If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari again.

Some files in "DOCUMENTS" icon in dock won't open. Get msg saying You need a newer version of Pages to open this document." Have Pages 4.1 installed. Same files will open ok from Finder, Pages App. Recently sync'd with ipad2 (Pages) after iOS5 installed.

Some files in "DOCUMENTS" icon in dock won't open. Get msg saying "You need a newer version of Pages to open this document." Already have Pages 4.1 installed. Same files will open ok from Finder/Pages App./selected file. Prob not noted until recently after sync'd with ipad2 (Pages) when I installed iOS5. Anyone-- please?!

You have 2 versions of Pages on your Mac.
Pages 5.2 is in your Applications folder.
Pages '09/'08 is in your Applications/iWork folder.
You are alternately opening the wrong versions.
Pages '09/'08 can not open Pages 5 files and you will get the warning that you need a newer version.
Pages 5.2 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
Older versions of Pages 5 can not open files from later versions of Pages 5.
Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
Anything that is saved to iCloud and opened in a newer version of Pages is also converted to Pages 5 files.
All Pages files no matter what version and incompatibility have the same extension .pages.
Pages 5 files are now only compatible with themselves on a very restricted set of hardware, software and Operating Systems and will not transfer correctly on any other server software than iCloud.
Apple has removed almost 100 features from Pages 5 and added many bugs:
http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
Rate/review Pages 5.2 in the App Store.
Peter

Message'there was an error opening this document.The file cannot be found'

Using xp home and when I click to download the pdf file, it will give 3 options been 'open'/'save'/?. When I choose the 'open' option, it will give me the above message "there was an error opening this document.The file cannot be found"
owever if I choose to "save" and I will be able to open the file and read it. In this pc its using Adobe Reader 8.1.2 with a patch. It was working fine prior to this sudden occurance of the error.
Strangely I have another pc with the same specification, I was able to choose "open" and be able to read the file. Can anyone help to resolve the issue by using the "open' option instead of "save, then open". Greateful for your prompt response.

Fyi, in addition to my earlier post, the other pc is using Adobe 8.1.1 and no other patch. I was trying to find 8.1.1 version but could not find a trust worthy site to load from. Do you think the error caused by using the 8.1.2 version? Thanks

There was an error opening this document. This file cannot be found

An automation script on one of our QA environments kept tripping on the error: "There was an error opening this document. This file cannot be found". The same script ran fine against our Production servers (hint, which were "whitelisted").
It took a little time to resolve/trace what was happening (but with the aid of ProcessMonitor and tracing all "pdf"-related file activity...)
The problem lies squarely between McAfee (75%), Adobe (20%) and Microsoft (5%):
NORMAL WORKFLOW. IE (Internet Explorer) when popping a PDF document, has to (1) write the document to the IE cache, then (2) launching and "handing off" the document reference to the Adobe viewer (which might then be able to open the document, et al) -- assuming largely a "synchronous" workflow.
BUT "WAIT", HOLD THE HORSES -- McAfee takes ownership and decides infact "wait for us" (during the workflow), it wants to first perform a virus scan on the document (ahead of writing the document to cache) involving potentially large latency (delay) before making the document available to the system. However, instead of "fessing up"-that their scan may be taking too long, McAfee appears to have taken their work "off-line" in violation of the sychronous interface above. I'm guessing the developers at McAfee might have been trying to hide any extra processing overhead being incurred by assuming they could somehow convert this to an "asychronous" event. (This may also have more reach than just PDF's.)
Unfortunately, the browser's "PDF OPEN"-dialog box pops allowing Adobe to launch-and-open the "as-yet-not-virus-scanned-and-thus-not-yet-cached"-document. Thus clicking the OPEN-button will cause the related "...FILE NOT FOUND"-error to be seen (because the file is still in McAfee "limbo").
Note: If you close the ADOBE reader (but don't yet close the popup-OPEN-dialog) you can click OPEN a second time and it will probably now open the document - which McAfee finally finished scanning!
You can observe all these interactions with ProcessMonitor, and use the monitored file states to adjust the timings of events to reproduce both the failure and non-failure scenarios.
- Best Regards, Ziggy
ps. My assessed distribution of "ownership" of the problem is because ALL these parties should be aggressively resolving this for the customer-base!

What, exactly, were you trying to do when you got it, and how?

There was an error opening this document. The file is damaged and could not be repaired.

Good Day all
When busy doing internet banking on www.absa.co.za and I try to print a confirmation, I get the following error message: "C:\Documents and Settings\%user profile%\Local Settings\Temporary Internet Files\Content.IE5\%folder name%\%file name%.pdf
Could not open file.
File not found."
I've managed to locate the actual file that it's looking for, but when I try and open the file using either Adobe or Foxit Reader, I get the following error message: "There was an error opening this document. The file is damaged and could not be repaired."
I've un-installed Adobe and installed version 9.1 for this particular user. This happened a while ago and then an un-installation and re-installation of Adobe solved the issue. This time, unfortunately, it didn't. I then un-installed Adobe and tried again, UNSUCCESSFULLY. So I loaded Foxit Reader, also without any success.
If there's anyone out there who could possibly help, please do so... It's extremely urgent.
Please find the errors attached as well.
Regards,
ME

I contacted the company and they asked me to try using another browser, which I did... and using FireFox worked
thanks for the help ʇɐb ɹəuəllıʍ
cheers!

I cannot re-open files that have been saved in Numbers version09 - it states "You need a newer version of numbers to open this document". This is the latest version

I cannot re-open files that have been saved in Numbers version09 - it states "You need a newer version of numbers to open this document". This is the latest version & also the one I have created/saved???

Jules,
You may delete Numbers 08 if you wish, but some folks like keeping it around. Close all your Numbers docs and Quit the Numbers app, and the other Numbers app if necessary.Then click the Numbers icon on your doc. Then select Numbers > About Numbers, and in the window that pops up, see which version it is. If the Dock icon started Numbers 08, you can cure that by dragging that icon off the Dock and letting it go in a puff of virtual smoke.
Now, to put the Numbers 09 icon on the Dock, double-click one of those known Numbers 09 documents so that Numbers 09 starts up. Verify by checkig Numbers > about Numbers.
Now click and hold the Numbers Dock icon and select the Option for Keep in Dock.
Jerry
Message was edited by: Jerrold Green1 -- I inadvertently posted about Pages rather than Numbers. Just corrected it.

Went to open a file in words and got message. "You need a newer version of Pages to open this document." I have latest version. All other files open w/o a problem. Please help.

Went to open a file in words and got message. "You need a newer version of Pages to open this document." I have latest version. All other files in words open w/o a problem. Please help.
Thank you.
<Email Edited by Host>

You have 2 versions of Pages on your Mac.
Pages 5.2 is in your Applications folder.
Pages '09/'08 is in your Applications/iWork folder.
You are alternately opening the wrong versions.
Pages '09/'08 can not open Pages 5 files and you will get the warning that you need a newer version.
Pages 5.2 can open Pages '09 files but may damage/alter them. It can not open Pages '08 files at all.
Older versions of Pages 5 can not open files from later versions of Pages 5.
Once opened and saved in Pages 5 the Pages '09 files can not be opened in Pages '09.
Anything that is saved to iCloud and opened in a newer version of Pages is also converted to Pages 5 files.
All Pages files no matter what version and incompatibility have the same extension .pages.
Pages 5 files are now only compatible with themselves on a very restricted set of hardware, software and Operating Systems and will not transfer correctly on any other server software than iCloud.
Apple has removed almost 100 features from Pages 5 and added many bugs:
http://www.freeforum101.com/iworktipsntrick/viewforum.php?f=22&sid=3527487677f0c 6fa05b6297cd00f8eb9&mforum=iworktipsntrick
Peter

Adobe reader: there was an error opening this document. this file cannot be found.

Windows XP Professional sp2 machine
512 memory
ie sp2
when opening two pdfs from a website links receive the error, "there was an error opening this document. this file cannot be found"
If you save the file to the pc, then open the .pdf it opens ok
other pdfs open ok from browser from same website and different websites
had customer try on another's machine; the two pdfs opened ok
tried Adobe Reader 8.1, 9.0, and Adobe Professional 8.0
uninstalled reader and professional; deleted directories; reinstalled reader and professional(placed into a separate directory); same error
On the machine tried admin accounts, under customer's profile made admin account, renamed the customer's account so that another account was freshly generated, all generated the same error.
Ran ccleaner to clean up files in the registry and temporary internet files, then repaired adobe - same error
repaired internet explorer - same error
scoured web for same error but most were applications trying to open the pdfs, a few errors were for programming php, a lot of questions but few answers in context of current issue. the ccleaner and repairing ie were resolutions i found on the web.
nothing was listed in msoft's ie knowledgebased searched.
any help would be appreciated.

I get the same message when I try to open a pdf attachment in my free AOL e-mail account. This problem just started today for some unknown reason. I have Adobe Reader 9 and never had a problem before. If I forward e-mails with a pdf attachment to my Road Runner account, I can open it with no problem. I can't seem to find any answers to this problem. Frustrating! HELP!!!

On file open: "This document contains JavaScript code for a widget that no longer exists."

Similar Messages

Maybe you are looking for