Rnage.insertHtml() works well on Word Application, and worked well before on Word Online.
But it seems that there is a new release recently for Word Online, it doesn't work any more on Word Online with following error:
Uncaught (in promise) RichApi.Error: Cannot read property 'XWa' of null
at new RuntimeError (https://appsforoffice.microsoft.com/lib/1.1/hosted/word-web-16.00.debug.js:11720:22)
at RequestContext.ClientRequestContext.processRequestExecutorResponseMessage (https://appsforoffice.microsoft.com/lib/1.1/hosted/word-web-16.00.debug.js:14496:12)
at https://appsforoffice.microsoft.com/lib/1.1/hosted/word-web-16.00.debug.js:14403:29
Related
Our Add-in for MS Word failed validation again. They cited that it didn’t work in the Word 2016 Client on Windows 10. But I developed and tested it in W10/O16 and it works for me. I've had several other people test using W10/O16 and it works for them. What could be so different about MS's testing setup?
They informed me they are testing using Azure VM's and provided a snapshot of the console errors they are seeing
POST https://word-edit-officeapps.live.com/we/RemoteUls.ashx?build=16.0.12231.32656&waccluster=IE3 500 MicrosoftAjax.js: 5
I've never seen this error before. They also showed another error I've never seen in any of my tests...
Uncaught TypeError: Converting circular structure to JSON -->
starting at object with constructor 'a' | Property
'bindings' -> object with constructor 'OSF.DDA.BindingFacade'
--- property 'document' closes the cricle
at JSON.stringify (<anonymous>)
at HTMLDocument.<anonymous> (Home.js:229)
at blah blah blah
at blah blah blah
at office.js:41
I look at line 229 in Home.js and it's
228: Office.onReady(function (info) {
229: log("Office.onReady info: " + JSON.stringify(info));
230: isJqready(); // run other functions
231: });
232:
233: Office.initialize = function () {}; // empty initialize function
I was wondering if it is possible that their environment doesn't support ES6? I've coded Home.js in vanilla JavaScript ES6, not TypeScript.
As a test, I've converted my ES6 code to ES5. But I'm hesitant to resubmit not knowing exactly why it failed.
Does anyone have any pointers?
I'm actually working on something similar. I can tell you the POST error is happening on OfficeOnline, not the desktop client so apparently they misreported that. Try running it on Office Online in various browsers.
It definitely needs to be either transpiled to ES5 or written natively in it because earlier versions of Word 2016 (before ~May this year) and in fact Word 2013 in general will need to run it in IE11 which does not support ES6.
I am trying to use the Amatic Font from Google in my PDF File but it gives me an Error like below. Could that be because the Font Type? I have tested with Open Sans and it is working.
AH01071: Got error 'PHP message: PHP Fatal error: Uncaught exception
'Zend_Pdf_Exception' with message 'Unable to read version 4 table' in
/var/www/vhosts/httpdocs/main/zend/library/Zend/Pdf/FileParser/Font/OpenType.php:555\nStack
trace:\n#0
/var/www/vhosts/httpdocs/main/zend/library/Zend/Pdf/FileParser/Font/OpenType.php(121):
Zend_Pdf_FileParser_Font_OpenType->_parseOs2Table()\n#1
/var/www/vhosts/httpdocs/main/zend/library/Zend/Pdf/FileParser/Font/OpenType/TrueType.php(83):
Zend_Pdf_FileParser_Font_OpenType->parse()\n#2
/var/www/vhosts/httpdocs/main/zend/library/Zend/Pdf/Font.php(701):
Zend_Pdf_FileParser_Font_OpenType_TrueType->parse()\n#3
/var/www/vhosts/httpdocs/main/zend/library/Zend/Pdf/Font.php(615):
Zend_Pdf_Font::_extractTrueTypeFont(Object(Zend_Pdf_FileParserDataSource_File),
0)\n#4 /var/www/vhosts/httpdocs/main/zend/invoice.php(27):
Zend_Pdf_Font::fontWithPath('/var/www/vhosts...')\n#5 {main}\n\nNext
exception 'Zend_Pdf_Exception' wi...\n'
I am using this Script for my tests https://github.com/phpmasterdotcom/GeneratingInvoicesWithZendPdf/blob/master/public/invoice.php
What's happening is this: The Zend Framework code in OpenType.php explicitly checks the OS/2 table version of the font. Is it higher than 3, an exception is thrown. Your font has an OS/2 table version of 4 (which is the fifth version, there are at least 6 versions as far as I know).
Unfortunately, recent versions of the ZendPdf module (like here on GitHub) still don't seem to support version 4 or higher. So apart from looking for another pdf generator - that does support version 4 - I fear there's no clean solution.
You could try editing the framework code, but of course that's a bit shady. As an alternative, apparently it should be able to change that version and regenerate the font. See this post on the Tex forum (the post AFTER the accepted answer). If you choose that path, probably you'll find better guidance on that forum.
Sorry I can't offer a better solution, but maybe it helps you understanding what's going on.
I am using Crystal reports in my WPF application to generate reports, getting below error
"the system cannot find the path specified error" on ExportToDisk.
irptDocument = new ReportDocument();
rptDocument.InitReport += new EventHandler(this.OnReportDocInit);
irptDocument.Load(astrReportName);
irptDocument.SetDataSource(adtbResult);
irptDocument.ExportToDisk(ExportFormatType.PortableDocFormat,lstrReportFullName);
Path where to save as pdf is a valid path, still I am getting above error.
This is very common error while we something missing or not set (even for runtime). If you getting error in win7, then also check second link.
While searching answers of your question, someone resolved this error by
I found out the problem; the auto-generated file name seems to have
been too long for the app-server. I changes the name of the class to
PCWS and it worked fine. It's a shame Sun One Studio (which creates
these massive file names doesn't warn you
Please check this links :
https://scn.sap.com/thread/3689925
http://answers.microsoft.com/en-us/windows/forum/windows_7-update/the-system-cannot-find-the-path-specified-error/dae5f759-b053-4a4a-87af-42e79f517631?auth=1
Been successfully using Orbeon 4.4CE for a long time, but today the Form Editor seems to have suddenly broken. Creating a new form (or editing an existing form) shows a partial toolbox missing most of the controls.
Log file reveals this:
INFO ProcessorService - /fr/service/custom/orbeon/builder/toolbox - Received request
ERROR XSLTTransformer - Error at line 32 of oxf:/forms/orbeon/builder/service/toolbox.xsl:
An empty sequence is not allowed as the value of variable $resources-property
ERROR PageFlowControllerProcessor - error caught {controller: "oxf:/apps/fr/page-flow.xml", method: "GET", path: "/fr/service/custom/orbeon/builder/toolbox"}
Configuration is Orbeon 4.4, MySQL persistence layer with MySQL 5.6, Java 1.7.67 and Tomcat 7.0.52 on Ubuntu 14.04. This was working fine as of late last week, and now seems broken on several systems all at once. Nothing in the configuration has changed in several months (as verified by a scan looking for files having recent modification times).
UPDATE: The problem is actually worse than I suspected...I copied an existing, working form from the MySQL orbeon_form_definition table to another Orbeon instance, and the form does not run. The Orbeon log file shows: "An empty sequence is not allowed as the value of variable $captcha" (the form does not use Captcha codes in any way).
We also tried installing a copy of Orbeon 4.7.0CE, and it appears to have similar symptoms.
The same problem is now occurring on three completely independent (but similarly configured) systems - we do not have a way to edit or create new forms using Form Builder, or even to move existing forms around between systems by updating the database definitions.
Any suggestion how to fix this, or even to diagnose where the problem might be?
Today I had a very similar problem.
I created a new form and didn't saw the toolbox controls:
Looking in the log there was the following error:
2018-03-16 10:33:26,212 ERROR XSLTTransformer - Error at line 32 of oxf:/forms/orbeon/builder/service/toolbox.xsl:
An empty sequence is not allowed as the value of variable $resources-property
2018-03-16 10:33:26,239 ERROR PageFlowControllerProcessor - error caught {controller: "oxf:/apps/fr/page-flow.xml", method: "GET", path: "/fr/service /custom/orbeon/builder/toolbox"}
2018-03-16 10:33:26,411 ERROR PageFlowControllerProcessor -
The reason was the name I had chosen for the form: reset-password. I changed the name in something else and the problem wasn't any more.
It seems that the form name must not contain the string "password".
In the last 2 weeks or so, I've suddenly started getting reports of users getting an error in our application saying "Expected response code 200, got 400. Unable to convert document." This is code that has been in place for years without any issue. We are using Zend Framework (GData) in conjunction with Google Docs (AuthSub).
We are logging the issue to a text file when it happens. When it gets logged, the user often tries multiple times (sometimes separated by a few seconds, other times separated by longer times) and it continues to fail. The code in question just creates a new Google document in the user's account and gives it a title (no body content).
Originally, I used this code:
// Create new document
$data = new Zend_Gdata_Docs_DocumentListEntry();
$data->setCategory(
array(new Zend_Gdata_App_Extension_Category(
"http://schemas.google.com/docs/2007#document",
"http://schemas.google.com/g/2005#kind"
)));
$data->setTitle(new Zend_Gdata_App_Extension_Title($title, null));
// Add document to your list
$test = $sharedocs->insertDocument($data, Zend_Gdata_Docs::DOCUMENTS_LIST_FEED_URI);
To experiment and see if there was an issue with that particular function, I tried creating a blank word doc and changing the code to:
$test = $sharedocs->uploadFile('/mypath/empty.doc', $title, null, Zend_Gdata_Docs::DOCUMENTS_LIST_FEED_URI);
However, I'm still seeing the "Unable to convert document" errors. They are relatively infrequent, and I am not able to reproduce the issue on my own computers here. The $title variable does not contain anything unusual (special characters, etc.).
This code was all working fine before -- is there a known issue with the Google Docs API right now? What else can I try?
NOTE: Please see my follow-up comments below, where I have identified the reproducible scenario in which this error occurs.
I had exactly the same problem, but I noticed that I could use the api to save a presentation if not a document... so, it is a terrible hack, but I try to save the document (works if the account has already been accessed)... if that fails, I save and delete a presentation and retry to save the document, which then works. Horrible, horrible, horrible hack