Unable to convert imported document to WSDL
Hi all, we're excperienced with a problem during the creation of an external definition with this WSDL file:
<?xml version="1.0" encoding="utf-8" ?>
- <!-- Generated by WSDLDefinitionsParser
-->
- <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="urn:java/lang" xmlns:ns0="http://www.w3.org/2001/XMLSchema" xmlns:ns3="urn:java.lang" targetNamespace="urn:WSCatalogoServiceWsd/WSCatalogoServiceVi/rpc_enc" xmlns:ns2="urn:ws.catalogo.dto" xmlns:tns="urn:WSCatalogoServiceWsd/WSCatalogoServiceVi/rpc_enc">
- <wsdl:types>
- <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java/lang" xmlns:tns="urn:java/lang" elementFormDefault="qualified">
- <xs:complexType name="ArrayOfString">
- <xs:complexContent>
- <xs:restriction xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" base="soapenc:Array">
<xs:attribute ref="soapenc:arrayType" wsdl:arrayType="xs:string[]" nillable="true" />
</xs:restriction>
</xs:complexContent>
</xs:complexType>
</xs:schema>
- <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java.lang" xmlns:tns="urn:java.lang" elementFormDefault="qualified">
- <xs:complexType name="Exception">
- <xs:complexContent>
- <xs:extension base="tns:Throwable">
<xs:sequence />
</xs:extension>
</xs:complexContent>
</xs:complexType>
- <xs:complexType name="Throwable">
- <xs:sequence>
<xs:element name="message" type="xs:string" nillable="true" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:schema>
- <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:meli.org.ngc.common.model" xmlns:tns="urn:meli.org.ngc.common.model" elementFormDefault="qualified">
- <xs:complexType name="Titolo">
- <xs:complexContent>
- <xs:extension base="tns:ModelInfo">
- <xs:sequence>
<xs:element name="autore" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="collana" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="collana_num_interno" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="committente" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="copieGratuite" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="copieGratuiteAmmesse" type="xs:boolean" />
<xs:element name="copieOrdinate" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="disponibilita" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="ean" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="editore" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="editoreId" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="formatoPrezzo" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="fornitureBloccate" type="xs:boolean" />
<xs:element name="isbn" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="nota" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="pagamentoOccasionale" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="pagamentoOccasionaleGiorni" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="prezzo" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="qtaDisponibile" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="riga" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="rispostaEditore" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="rispostaEditoreDesc" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="sovraScontoOccasionale" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="statoVendita" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="statoVenditaDesc" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="tempoInserimento" type="xs:long" />
<xs:element name="titolo" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="vendibilita" type="xs:string" nillable="true" minOccurs="0" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
- <xs:complexType name="ModelInfo">
<xs:sequence />
</xs:complexType>
- <xs:complexType name="ArrayOfTitolo">
- <xs:complexContent>
- <xs:restriction xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" base="soapenc:Array">
<xs:attribute ref="soapenc:arrayType" wsdl:arrayType="tns:Titolo[]" nillable="true" />
</xs:restriction>
</xs:complexContent>
</xs:complexType>
</xs:schema>
- <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ws.catalogo.dto" xmlns:tns="urn:ws.catalogo.dto" elementFormDefault="qualified" xmlns:s0="urn:meli.org.ngc.common.model">
<xs:import namespace="urn:meli.org.ngc.common.model" />
- <xs:complexType name="InfoTitoli">
- <xs:sequence>
<xs:element name="codErrore" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="paramErrore" type="xs:string" nillable="true" minOccurs="0" />
<xs:element name="titoli" type="s0:ArrayOfTitolo" nillable="true" minOccurs="0" />
</xs:sequence>
</xs:complexType>
</xs:schema>
</wsdl:types>
- <wsdl:message name="autenticaUtenteIn">
<wsdl:part name="userName" type="ns0:string" />
<wsdl:part name="password" type="ns0:string" />
</wsdl:message>
- <wsdl:message name="autenticaUtenteOut">
<wsdl:part name="Response" type="ns0:boolean" />
</wsdl:message>
- <wsdl:message name="leggiTitoliDaArrayCodiciIsbnEanIn">
<wsdl:part name="codiciIsbnEan" type="ns1:ArrayOfString" />
<wsdl:part name="userName" type="ns0:string" />
<wsdl:part name="password" type="ns0:string" />
</wsdl:message>
- <wsdl:message name="leggiTitoliDaArrayCodiciIsbnEanOut">
<wsdl:part name="Response" type="ns2:InfoTitoli" />
</wsdl:message>
- <wsdl:message name="leggiTitoliDaArrayCodiciIsbnEan_java.lang.Exception">
<wsdl:part name="leggiTitoliDaArrayCodiciIsbnEan_java.lang.Exception" type="ns3:Exception" />
</wsdl:message>
- <wsdl:message name="leggiTitoliDaAttachmentIsbnEanIn">
<wsdl:part name="inputFile" type="ns0:base64Binary" />
<wsdl:part name="userName" type="ns0:string" />
<wsdl:part name="password" type="ns0:string" />
</wsdl:message>
- <wsdl:message name="leggiTitoliDaAttachmentIsbnEanOut">
<wsdl:part name="Response" type="ns2:InfoTitoli" />
</wsdl:message>
- <wsdl:portType name="WSCatalogoServiceVi_Rpc_enc">
- <wsdl:operation name="autenticaUtente">
<wsdl:input message="tns:autenticaUtenteIn" />
<wsdl:output message="tns:autenticaUtenteOut" />
</wsdl:operation>
- <wsdl:operation name="leggiTitoliDaArrayCodiciIsbnEan">
<wsdl:input message="tns:leggiTitoliDaArrayCodiciIsbnEanIn" />
<wsdl:output message="tns:leggiTitoliDaArrayCodiciIsbnEanOut" />
<wsdl:fault name="java.lang.Exception" message="tns:leggiTitoliDaArrayCodiciIsbnEan_java.lang.Exception" />
</wsdl:operation>
- <wsdl:operation name="leggiTitoliDaAttachmentIsbnEan">
<wsdl:input message="tns:leggiTitoliDaAttachmentIsbnEanIn" />
<wsdl:output message="tns:leggiTitoliDaAttachmentIsbnEanOut" />
</wsdl:operation>
</wsdl:portType>
</wsdl:definitions>
The error is:
Unable to convert imported document to WSDL
Reason: Attribute nillable=true is not permitted at position <wsdl:definitions><wsdl:types><xs:schema><xs:complexType><xs:complexContent><xs:restriction><xs:attribute>
Check the selected category
Can anyone help us ?
Thanks in advance
Best regards
Gianfranco Bello
Hi Gianfranco Bello
Can you try and remove atrribute <b>nillable</b>=true from your wsdl
It may sound awkward but it worked for me i had a same problem with my wsdl
Regards
Mitesh
Similar Messages
-
When I sign in to the Adobe Reader XI (which is the only option that I have to open a pdf document, I will sign in to the Adobe ID sign-in page. After I do this, the "Convert To" box goes "gray" and I am unable to convert the document I have selected. It was working great for the first week that I used it, but now it doesn't give me the converting option. I am very frustrated as I have done nothing to change anything, and I was thinking this was so great...now I am just pulling out my hair and do not have the option of calling anyone since no phone numbers are listed. I am VERY busy and do not have time to sit and wait over a half an hour to "chat", which I tried to do yesterday. All I want to do is very simply, convert pdfs to Word. I have paid for this and am not getting any help. I am not very savvy when it comes to Adobe this program and Adobe that program...I feel I am being scammed as I do not get simple answers for something that appeared was going to be simple. You can't even call customer service to talk to someone live to help walk you through.
Hello Kathie,
Sorry for the inconvenience that has caused to you.
Please let me know if you have tried converting any other PDF to word with Reader.
Alos, please sign up at "https://cloud.acrobat.com/" using your Adobe ID credentials. Click on 'ExportPDF' tab and upload the PDF that you want to convert to Word.
Let me know if this converts fine.
Hope to hear from you.
regards,
Anubha -
Hello!
I currently implement a RFC -> RFC adapter -> XI -> SOAP adapter -> Web Service scenario. I have imported the WSDL of the Web Service as External Definition into the Integration Repository to use it for the RFC <-> Web Service mapping within the graphical mapping tool.
Until now I only have imported document-style WSDL and there never have been any problems. Now the WSDL is RPC-style which means that the messages described by the <wsdl:types>...</wsdl:types> part should be enclosed by an additonal structure describing the Web Service operation to be executed.
However, in the graphical mapping tool the structure for the Web Service operation is missing and thus the Web Service call cannot be executed. How can I solve this problem without changing the WSDL or creating an additional XLST or Java mapping?
It seems that there is no problem with the WSDL. When I loaded it with the Web Service Navigator test tool of the SAP Web Application Server the structure describing the Web Service operation has been generated in the request message.
Regards, Tanja SchättlerHi Tanja
Check this note 856597, it even has some examples of WSDL documents and sample SOAP messages that illustrate how one can write an equivalent WSDL in another style.
A snippet from the note,
"Q: Can I convert an RPC styled WSDL to a document styled WSDL?
A: It is difficult to answer yes or no because the answer depends on the WSDL instance and the implementation of the code that binds the XML instance to some native object. The problem comes from the fact that these two styles describe web services in different layers. The document style WSDL describes how one can bind an XML document to the SOAP message format. In contrast, the RPC style WSDL describes how one can bind an object to the SOAP message format. One can imagine that this works in two steps: first representing the object as an XML document and then binding this XML document to the SOAP message format. How this first step works is controlled by the SOAP encoding name. For the standard encoding specified in the SOAP specification, most objects can be easily described in an equivalent XML schema. Some special objects such as references and arrays must be represented by some special rules and some additional meta information in XML. This implies that these additional attributes and elements must also be described in the XML schema and the document style based proxy must set these values in the instance appropriately.
One must however note that even if one has an equivalent document style WSDL, this does not automatically guarantees the interoperability. Some RPC styled service implementations have significant interoperability problems such as requiring the xsi:type attribute for every element or the SOAP encoding attribute at some particular element. If one has to call such non conformant SOAP service, one must adjust the message accordingly.
Attachment wsdl_style_samples. zip contains some examples of WSDL documents and sample SOAP messages that illustrate how one can write an equivalent WSDL in another style.
Related Questions "Does the RPC or Document style in WSDL play a role in the SOAP adapter?"
cheers
Sameer -
Error converting Word document to .pdf
Hi,
The office staff here has a couple of custom templates that they've been using for several years now to generate company letters. The company was bought by another firm, and about two weeks ago this office's network was attached to the new company's domain; login scripts were changed, security permissions, desktop settings, and so forth. Since that time, staff has been unable to convert their documents. Monday I started digging into the problem and found an Adobe Knowledgebase article referencing corrupted .icc files at this link:
http://kb.adobe.com/selfservice/viewContent.do?externalId=328791
The error referenced was not exactly the same, but it was the closest thing I've been able to find, so I decided to give it a shot.
Late Monday I went through the steps in the article on one of the problem workstations, and the error went away - was able to do seven or eight conversions successfully, so I saved the files and instructions for use the next day. Yesterday I started to do the same process on the other three workstations, but it had no effect on them, and in the middle of this, I was notified that now the first workstations has stopped working again, also - it was neither turned off nor rebooted overnight, but the same error is appearing again. Repeating the process from the day before does nothing now to correct the error, nor can I convert the *same test document* that I converted successfully multiple times the day before. Hopefully someone can point me in a direction to start looking.
Machines: Dell and HP, various hardware.
Example: Dell Pentium 4, 3.20 GHz, 3.00 GB RAM
OS: Windows XP Pro, v2002, SP2
MS-Word 2003 SP2
Adobe Acrobat 6.0 Standard, v6.0.6
Adobe Distiller v6.0.1
Inside Word, Adobe Conversion Settings:
Use prologue.ps and epilogue.ps
Conversion Settings file: Custom template settings (standard doesn't work, either)
Enable accessibility & reflow with tagged PDF is checked
Compatibility - Acrobat 5.0
Color settings file - "None" (some machines have Web Standard selected, which also doesn't work.)
Color management policies - Leave color unchanged
Imbed fonts - checked on two W/S, one has several fonts excepted
- unchecked on two W/S
Process:
Letter template has macros which insert a logo in the document at print time, check tables, do calculations, check for "forbidden words". Template also contains a TOC. To test this, I simply open Word, make sure the macros are loaded (since the login scripts changed, this has to be done manually,) and create a new document from the proper template. There is a startup macro that can be simply bypassed (all it does is allow operator to change the office location, otherwise just leave the default,) and then from the "Adobe PDF" option on the Word menu bar, select "Convert to PDF". If the complete conversion runs, this may take up to a couple of minutes to finish, then the converted document is opened in Acrobat. What happens now is that the conversion process starts, then the process bar hangs for a few seconds and we get a messagebox stating: "Adobe pdf printer failed to create the pdf file"
Most of the time, it doesn't seem to produce an errorlog, but if it does, this is what I see in the log:
%%[ ProductName: Distiller ]%%
%%[ Error: undefined; OffendingCommand: pdfmark ]%%
Stack:
[{FMSMColorLogo}]
[{FMSMColorLogo}]
-mark-
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%Try printing to the Adobe PDF printer. That may give a work around. I noticed that there was a pdfmark error. PDFmarks are added to the output file by PDF Maker prior to being sent to Distiller. That is how all of the links and such are transferred with PDF Maker. It is worth trying to take that out of the loop and see what happens. It almost seems like the folks that took over wiped out some of your logos and such, but there may be something much simpler at work.
Don't you just love corporate takeovers! I guess you can't comment though. Your link seems to discuss some related issues. It may be that access to specific settings files that may have been customized may have been lost or those profiles were deleted.
So much for my ranting with guesses. Hopefully I gave you some useful thought items. Bill -
Please inform me why I am unable to convert my PDFs to Word Documents anymore. I've been signed up and paid forever now and no problems until today, Please inform me of what the problem is? Thanks bunches! :- @(
Hi vtbabyof8,
I just took a look at your account and see that it expired on June 14. I'll send you a private message with more information.
Best,
Sara -
Unable to create web service from wsdl that contains xsd as import
I have written a WSDL and tried to create the web services by weblogic workshop.
Prior to that I have created the war file and able to deploy them properly. Also able to access any wsdl by hitting the server.
But when I am trying to create the web services by weblogic workshop its throwing error as "URL is not well formed" for those XSDs which I have imported in my WSDL. I have kept all my XSDs and WSDLs in the same folder.
The WSDL has given below :
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:intf="http://soapheader.ibm.com" xmlns:impl="http://soapheader.ibm.com" xmlns:MessageContext="MessageContext" xmlns:AlertUpdateRequest="AlertUpdateRequest" xmlns:AlertFetchResponse="AlertFetchResponse" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://soapheader.ibm.com">
<import namespace="MessageContext" location="http://localhost:7001/WebApplicationWeb/gss/xsd/MessageContext.xsd"/>
<import namespace="AlertUpdateRequest" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertUpdateRequest.xsd"/>
<import namespace="AlertFetchResponse" location="http://localhost:7001/WebApplicationWeb/gss/xsd/AlertFetchResponse.xsd"/>
<wsdl:types>
<schema elementFormDefault="qualified" targetNamespace="http://ggg.com" xmlns="http://www.w3.org/2001/XMLSchema">
</schema>
</wsdl:types>
<wsdl:message name="alertUpdateRequest">
<wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
<wsdl:part name="request_header" element="MessageContext:MessageContext"/>
</wsdl:message>
<wsdl:message name="alertUpdateResponse">
<wsdl:part name="parameters" element="AlertUpdateRequest:AlertUpdateRequest"/>
<wsdl:part name="request_header" element="MessageContext:MessageContext"/>
</wsdl:message>
<wsdl:message name="alertFetchRequest">
<wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
<wsdl:part name="request_header" element="MessageContext:MessageContext"/>
</wsdl:message>
<wsdl:message name="alertFetchResponse">
<wsdl:part name="parameters" element="AlertFetchResponse:AlertFetchResponse"/>
<wsdl:part name="request_header" element="MessageContext:MessageContext"/>
</wsdl:message>
<wsdl:portType name="AlertUpdateService">
<wsdl:operation name="getAlertUpdate">
<wsdl:input name="alertUpdateRequest" message="intf:alertUpdateRequest"/>
<wsdl:output name="alertUpdateResponse" message="intf:alertUpdateResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="AlertFetchService">
<wsdl:operation name="getAlert">
<wsdl:input name="alertUpdateRequest" message="intf:alertFetchRequest"/>
<wsdl:output name="alertUpdateResponse" message="intf:alertFetchResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AlertUpdateServiceSoapBinding" type="intf:AlertUpdateService">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="getAlertUpdate">
<wsdlsoap:operation/>
<wsdl:input>
<wsdlsoap:header message="intf:alertUpdateRequest" part="request_header" use="literal"/>
<wsdlsoap:body parts="parameters" use="literal"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:header message="intf:alertUpdateResponse" part="request_header" use="literal"/>
<wsdlsoap:body parts="parameters" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="AlertFetchServiceSoapBinding" type="intf:AlertFetchService">
<wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="getAlert">
<wsdlsoap:operation/>
<wsdl:input>
<wsdlsoap:header message="intf:alertFetchRequest" part="request_header" use="literal"/>
<wsdlsoap:body parts="parameters" use="literal"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:header message="intf:alertFetchResponse" part="request_header" use="literal"/>
<wsdlsoap:body parts="parameters" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="AlertUpdateServiceService">
<wsdl:port name="AlertUpdateService" binding="intf:AlertUpdateServiceSoapBinding">
<wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertUpdateService"/>
</wsdl:port>
</wsdl:service>
<wsdl:service name="AlertFetchServiceService">
<wsdl:port name="AlertFetchService" binding="intf:AlertFetchServiceSoapBinding">
<wsdlsoap:address location="http://localhost:9080/SOAPHeaderWeb/services/AlertFetchService"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>Hi,
From your description I am assuming that you are using JAX-WS, if not get back to me as I might have another bug to look at.
The problem is that the annotation @Oneway needs to be added to the methods in java files for this to work correctly. You can either do this manually or use the PI in the code editor. I have raised bug 6266513 to track the fact this annotation is not written out properly. I have logged bug 6266556 to track the nillable=true and extranious elements you will see when you do add @Oneway.
Thanks for the quality of your bug report, and we would of course welcome any other feedback good or bad you would like to give us.
Gerard Davison
JDeveloper Web Services Team -
Unable to convert PDF file into word document
I just signed up with Adobe in order to convert a PDF file into a word document and it continues to fail. Any suggestions.
If you have adobe X, simply go to "File" -> "Save-As" and Microsoft Word is an option. Also, there is a download (paid) called Able2Extract that will allow you to convert pdfs to word, excel, etc. but the formatting is often lost. If you get the premium package, you can even convert scanned documents. I've used Adobe X to do the conversion, and it retains headers, footers and all formatting.
And i personally share you with a article about how to converting PDF files to Word(.doc), you just need to follow the easy guide.
Hope it can help you a lot. -
Unable to convert PDF to word docuement
just bought adobe program to convert PDF file to word docuemet, when i export and follow direction to convert, program come back stating failed to convert the file, why?????
Hi MaryFran246,
I'm terribly sorry for the inconvenience this has caused you.
Could you try these steps to alleviate the access issue you're having:
Choose Edit > Preferences (Win) or Adobe Reader > Preferences (Mac)
Click 'Online Services' on the left-hand side
Sign out of our Adobe ID and sign back in.
Try to convert your document again.
If you continue to have trouble, please verify that you can access the service via the web interface. To do this:
Open a browser and navigate to http://exportpdf.acrobat.com/signin.html
Try to log in with your Adobe ID (email address) and password
Once logged in, follow the on-screen prompts to convert a file
Let us know if you're still having trouble and we'll try to help!
-David -
PDF: Unable to print a document as PDF from APEX when using the BI Publishe
Hi,
From an APEX application, I am unable to print a document in a PDF format when using the Oracle BI Publisher.\
Here is the configuration:
1) Server A is W2K3 and hosts the Oracle BI Publisher server, with IP address ip01.
2) Server B is a OEL5.2 and hosts the database server of the APEX application, with IP address ip02.
3) Machine C is a W7 desktop from which through an URL both the APEX applicationn and the BI server are accessed, with IP address ip03.
4) The APEX application is configured with the following to use the Oracle BI Publisher:
- Printer server: Advanced (requires Oracle BI Publisher)
- Printer server protocol: HTTP
- Printer server host address: ip01
- Printer server port: 9704
- Printer server script: /xmlpserver/convert
- Network services are enabled (at least I did get any warning/error message)
From C, I access the the APEX application through its URL, if I try to download a page by selecting PDF in the download section of the interative report section for that page, I am unable to open if and get the error:
<file>. pdf file can not be opened because the file type is not supported or because it is damaged (because, for example as an e-mail attachment is not sent and correctly decoded)
Yet, still from C, I am able to open any other PDF document.
The same way, still from C, acessing the APEX application through its URL, I have a query report defined with a PDF output format. Then, when I test the report (Test Report in the Report query) for that query, I get the error:
ORA-20001: The printing engine could not be reached because either the URL specified is incorrect or a proxy URL needs to be specified.
At first sight this could be a wong entry in the priinter configuration for APEX. But with this address, through the URL I can log in to the Oracle BI Publisher server.
Does someone has an idea what the problem could be?
Thanks for any tips.How are you trying to print to pdf?
Don't go via PostScript or Acrobat Distiller, which are old deprecated technology.
You use:
Menu > File > Print > PDF (button bottom left) > Save as PDF…
Peter -
Unable to convert a postscript file on c3180
hp photosmart c3180 printer
printing from windows 8 64-bit ms word on a mountain lion mac using parallels 7
unable to convert a postscript file
unable to use after installing windows 8 64-bitIf I understand what it is you want, open the PDF file in Preview and from the File Menu select Export as PDF. In the file selector there's a button labeled Show Details. Click it. Select encrypt, enter a password, and save using a different name. The new document will show a lock indicated it is passworded. Delete the original version.
-
Adobe Acrobat XI Pro. Unable to process the document in the module Save As.File not created
On the ultrabook Asus (System Settings: WIN 8.1 64-bit, Core I5-3317U CPU @ 1.70 Ghz, Memory 4 Gb), set Adobe Acrobat XI Pro 11.0.09
When you convert to any format via SaveAs in WORD, EXCEL, or via the Export file in ... throws the error "Unable to process the document in the module Save As. File not created"
http://youtu.be/l0a0lWexfNQ.Hi,
Please post your query in Adobe Acrobat Thread:Acrobat
Regards,
Florence -
Unable to process the document in the module Save As
Good day!
On the ultrabook Asus (System Settings: WIN 8.1 64-bit, Core I5-3317U CPU @ 1.70 Ghz, Memory 4 Gb), set Adobe Acrobat XI Pro 11.0.09
When you convert to any format via SaveAs in WORD, EXCEL, or via the Export file in ... throws the error "Unable to process the document in the module Save As. File not created"Hi,
You are posting on Acrobat.com online service forums.
Please post your query on the Acrobat forums.
https://forums.adobe.com/community/acrobat/creating__editing_%26_exporting_pdfs
Regards,
Florence -
I am unable to convert certain files to pdf with Adobe Acrobat 8 Professional
I am unable to convert Word & PowerPoint files to pdf. (I am able to convert image files & excel)
I have enable macros in Word and still cannot convert the file.
I am getting the error popup:
Unable to open the document
Please check to see if you have read permission for the above file
I am running:
Windows XP Professional Ver 2002 SP 3
Adobe Acrobat 8 Professional
Microsoft Office 2007Open the document in WORD or PPT and print to the Adobe PDF printer. With PPT, you will have to select the fill page option. You may also be able to use PDF Maker in WORD or PPT. From your post I am assuming you are trying to open directly in Acrobat and all of these other things have to be working properly before the latter will work. If they work and you still can not open directly in Acrobat, then try a repair on Acrobat.
-
IDOC Receiver - Unable to convert sender service to ALE
Hi!!!
I am trying to configure the following scenario: FILE - XI - IDoc to R/3.
A business service called IDOC_Demo recovers from the server the file, and after mapping it, it tries to send it to IBP, the R/3 system using a IDOC Receiver comunication channel.
IBP is configured in SLD.
I have in XI System the RFC conexion, and I have define the port via TCODE IDX1.
But it does not work, I am geting the following error:
"Unable to convert sender service IDOC_Demo to an ALE logical system"
I have checked the adapter specific identifiers, but I can not see anything wrong...
I do not know what can I check! Could someone help me?! What can I do?
Thank a lot!!
Araitz.Thank you very much, but I still get the error message! Of course, I read your blogs Michal before posting the question, and they have been very useful, but still...
In SLD I only have the R/3 system, the name is IBP and the business landscape and the logical system name (I do not know if this could cause a problem ).
The connexion is IBP, and it works, and in idx1 I have configured a port, and its name is SAPIBP, using the IBP connexion.
Design I have imported the CREMAS.CREMAS03 IDOC, and I have done a mapping interface, I have disabled the EDI_DC40, and set begin and segment to 1.
Configuration I have created a business service, IDOC_Demo, that has a communication channel, sender, file type.
And I have the IBP service. In adapter specific I can see: logical system IBP, and R/3 System IBP, client 100. If I push the Compare with SLD button, nothing happens what should happen?
IDOC_Demo receives the file, and via an Outbound, async interface, calls IBP, that receives the IDoc using a receiver IDoc type adapter
Now the receiver agreement has information in the header mapping, sender service, IDOC_Demo, receiver service, IBP.
And I do not know why, but it does not work any idea?
Than you!
Araitz. -
Unable to convert the sender service to an ALE logical syst
Hi,
My scenario is IDOC to File.
SLD:Configured Correctly ,ABAP Business System.
Imported the same in ID,under Adapter specific Identifiers gava the Logical system as in WE20.
In the Receiver Agreement,Header mapping tried giving the sender service,Receiver service.
Still the Error "Unable to convert the sender service to an ALE logical syst" is seen in SMQ2.
The file is getting generated at receiver directory mentioned in the receive CC.
There is no error seen in SXMB_MONI.
Did any one had a problem as this.
Thanks,
SrinivasaHi,
You need to specify the Logical Name of Business System under Adapter specific identifiers for your Receiver Business System.
The specified item was not found.
Secondly you can use Header Mapping in Receiver Agreement. Or
If you are taking your control records from payload then tick the check box "Apply Control Records from Payload".
Regards,
Maybe you are looking for
-
For Christmas 2012 my son bought me my first iPad when up in Scotland on business. So from 25th December until last Tuesday evening, September 3rd, this had worked fine and was my pride and joy. It's an amazing piece of technology. Imagine my horror
-
Error during deploying SOA Composite
I have created a SOA Composite in which I am trying to access an External Web Service. The compilation goes fine but its failing at the time of deployment to Soa Server. My BPEL consists of following activities-> RecieveInput-> Assign -> Invoke -> As
-
I have an external hard drive. How do i put stuff on it?
Yes i have an external hard drive a iomega. I have stuff already on it , from when i used to have windows. I have tried to put some files onto it but it wont accept. I tried doing it through the Time machine option but it is saying it will wipe out a
-
Error while fetching data from CRM system to BW
I am extracting data (BP ID) from CRM system. I have upgraded the BI 7.0 system from patch 12 to patch 14. After upgrading when i execute the infopackage to fetch the data from the CRM system. The request is coming in yellow and is not fetching the d
-
Hello all, I have a Flex app that loads in a swf using 'SWFLoader' tag. the SWFloader and the swf being loaded in are the same height and width (see attached code) Now, the SWF getting loaded in is also 468 X 351 however the designers that made it ha