Difficulty configuring transport for 7.0.3 trial
I realize that there have been posts on this issue before, but I spent several hours yesterday searching the boards and never arrived at a complete solution.
I have installed the Netweaver 7.03 SP04 trial.
I have logged in as DDIC user and have executed the post-installation actions on SE06.
When I go to set up transport, however, I keep getting the error "TMS must be configured for 000". All the documentation I have found seems to suggest that I should get a popup window on first connect to STMS to configure the transport domain - this popup is never shown. I have tried Extras -> Delete TMS Configuration, but receive the error "TMS not configured for system NSP".
From reading some previous posts, I have confirmed that there is a "sapmnt" share available, and added the SYSTEM user with full permission roles to the share. This did not seem to have any effect - I still receive both errors as described above.
What are the next steps I should pursue to get the transport working?
Thanks for your help!
Hi Manu,
I foolishly was not logged into 000.
I've now done the following:
I've logged into 000 as DDIC
I ran txn SE06 successfully.
I ran txn STMS and received the popup. After entering the values I received the error "Errors during distribution of tp configuration."
I went to txn SECSTORE, highlighted the two erroring values and then deleted them.
I returned to txn STMS and selected extra -> Delete TMS Configuration.
I saved and then reentered the password. My STMS is now reporting that it's the domain controller.
Thank you for your help!
Similar Messages
-
Configuring transport for calendar
Hello together!
I have problems with my calender in portal. Error message occurred: "No transport has been configured for calendar".
Can anybody give me a hint to solve the problem?
I am looking forward for your comments!
Thanks a lot!
DominikHi,
Check the SAP notes here:
[805483|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_ep_km/~form/handler]
https://forums.sdn.sap.com/thread.jspa?threadID=72396
Regards,
Praveen Gudapati -
Problem configuring Email transport for business service
Hi,
I'm trying to configure an email transport for an outgoing business service and the General Configuration page is showing the error:
[WliSbTransports:381030]Neither SMTP nor mail session exists
and consequently the Email Transport configuration page has both the SMTP Server and Maill Session pull downs greyed out.
I presume there is some external configuration required so that OSB can discover the SMTP service but I can't find any reference to this. Can someone help?
regardsBlog at http://blogs.oracle.com/christomkins/2007/12/sending_an_email_from_oracle_s.html by Chris Tomkins should help. Did you configure SMTP server in OSB?
Cheers
Manoj -
Configuring SLD for ABAP trial version.
Hi,
I have installled ABAP trial version and 2004s Java trial version.I am facing error in configuring SLD for 2004s ABAP trial version . I am getting this below error.
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=aarya-3 GROUP=SPACE R3NAME=NSP MSSERV=sapmsNSP PCS=1 ERROR Group SPACE not found TIME Mon Apr 21 15:33:19 2008 RELEASE 700 COMPONENT LG VERSION 5 RC -6 MODULE lgxx.c LINE 4288 DETAIL LgIGroupX COUNTER 4
Has anybody configured the SLD for local ABAP server? please let me know where I am doing the mistake..I have read many threads regarding JCO error but my problem is not resolved yetHello Sam,
Yes it is. Check the documentation at
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/cc/bae93a2876a81ae10000000a11402f/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/cc/bae93a2876a81ae10000000a11402f/frameset.htm</a>
for further details.
Regards,
Klaus -
Step configuration guide for Shipping, Transportation & Shipment Cost Calcu
Hi Gurus,
Does anybody have the step by step configuration guide for Shipping, Transportation & Shipment Cost Calculation.Its very urgent.
My email id is [email protected]
Thanks in advance
Regards
Message was edited by:
Sumit Rayaguru<b>Hi
Pls don't post e mail id to share information . Make small search n sdn before posting the query.</b>
Help Me!!!!!!!!!!!!
Help Me!!!!!!!!!!!!
Please Follow below steps.
1)Create the transportation planning point for the company codes.
2) Maintain transp. relevance for the dly doc. type, item cat and routes
3) Define the shipment types
4) Define the shipment cost types
5) Define shipment cost item categories and assign
6) Define shipment cost relevance
7) Maintain pricing
8) Assign purchasing data
9) OBYC
10) OKB9
AND Please check the below:
Step1: T.Code: VL01N: Just Create Delivery Note here. Do not do the Picking and Packing.
(This is Client Specific)
Step 2: T.Code: VT01N: Create Shipment.
Here mention your Transportation Point and Shipment Type you Configured for this and Click on deliveries ICON.
GO to W.ref to
Outbound Delivery : Give your Delivery Number that you created earlier for this shipment and F8( Excute)
Then Select the Delivery and Click on OverView
Here Click on Planning then automatically Route( If route determination is done) and Vendor Number get generated and Save the Data.
Step.3: T.Code: VL02N: Change Delivery.Here give the Delivery no and
Do picking, Packing (If necessary) and PGI.
Message was edited by:
SHESAGIRI.G -
I am trying to install iTunes in my 64 bit Windows 7 PC. My PC runs normal. But when I try to install Itunes from Apple website, I get a message "The Configuration data for this product is Corrupt contact your support personneI" I
am so disgusted,please help!!!Hey madnest,
Thanks for the question. After reviewing your post, it sounds like you are having difficulty installing iTunes in Windows. I would recommend that you read this article, it may be able to help you resolve or isolate the issue.
Issues installing iTunes or QuickTime for Windows
Thanks for using Apple Support Communities.
Have a nice day,
Mario -
How to configure rescheduling for sale order quantities
kindly explain how to configure rescheduling for sale order quantities that are created last month. kindly explain. i am in urgent.
regards,
g.v.shivakkumarHi,
Short text
Rescheduling sales and stock transfer documents: by material
Description
The 'Rescheduling' program (SDV03V02) processes sales document items that are contained in the item directory for the material. It takes into consideration open items and schedule lines from stock transfer items, stock transfer scheduling agreements and purchase order requests (items only), referred to hereafter as stock transfer documents, for the materials.
All sales documents for the material that are still open are selected. This means that the material index must be activated for at least all sales document types, whose items may have requirements. All stock transfer documents or items for the material that are still open are also selected. Open in this case means for example, that there is no deletion indicator, that the item from a stock transfer purchase order request cannot be labeled as completed or that the quantity delivered and posted to goods issue for the item in a stock transfer purchase order is the same as the amount ordered. An availability check can only be carried out if a checking rule is assigned to the document type - if this is not the case, the document or document item is not checked.
Checking rule 'A' is used as a basis for rescheduling sales orders (exceptions to this are rush orders they use checking rule B, and orders with individual customer stock; they use checking rule AE). Stock transfer documents use the checking rule that is assigned in Customizing for Purchasing. It is important that the scope of checks is consistent for both the stock transfer documents and the sales documents and that they do not exclude each other, as this can lead to incorrect test results. An example of an incorrect setting would be: The scope of check for checking rule 'A' checks delivery schedules for stock transfer purchase orders and stock transfer purchase requests, however the scope of check for the checking rule for the stock transport scheduling agreement does not.
The items and schedule lines found in the selection are sorted according to 'Priorities' - document category, delivery priority, creation date of the item or schedule line (for stock transfer purchase orders and delivery plans) entered on the selection screen or according to the schedule line date of the earliest schedule line with order quantity, document number and item number and then transferred to the availability check. Priority 1 is highest priority and priority 5 the lowest. Stock transfer purchase order requests are sorted after stock transfer purchase orders and scheduling agreements, as they are less binding. This means that when you have identical sort criteria such as delivery dates, the stock transfer purchase order item is checked first and then the item from the stock transfer purchase order request.
The preset option 'Unconfirmed documents required' only carries out rescheduling for materials for which there is at least one unconfirmed transaction.
You can use the parameters 'Sorting criteria delivery date' to define whether sorting is carried out with the order quantity after the creation date of the item or the delivery date of the earliest schedule line.
If you mark the 'Simulation' field, the checked documents are not saved. Instead a results list is generated and saved. However, the availability check for the corresponding documents continues as if saving has taken place already, that is, that the simulated list corresponds to the actual one.
Under 'Options' on the selection screen, specify whether sales documents and/or stock transfer documents should be processed. For stock transfer documents you can enter whether stock transfer purchase orders and scheduling agreements should be processed at item or schedule line level:
Processing at item level:
All open schedule lines for the item are read and collected, then transferred to the availability check. To sort and prioritize documents, you do not need each individual schedule line. It is sufficient to have the item or data from the first schedule line. All open schedule lines for the item are processed and checked.
Example of processing at item level:
Sorting: Date (Delivery date first schedule line) - Document number - Document item
Doc. cat. Doc. number Doc. item Doc. schedule line Delivery date PO 4500000012 10 0001 26.01. PO 4500000012 10 0002 26.02. PO 4500000025 20 0001 28.01. PO 4500000025 20 0002 02.02.
You can see that the second schedule line for document 4500000025/20 from 02.02 was processed after the second schedule line for document 4500000012/10 from 26.02. This is because all open schedule lines for an item are read and processed. The first schedule line from 4500000012/10 has the earliest delivery date, therefore it has priority.
Processing at schedule line level:
Each open schedule line for an item is entered in document sorting in accordance with the values entered under 'Priorities'. The availability check is carried out for each individual schedule line.
Example for processing at schedule line level:
Sorting: Date (delivery date first schedule line) - document number -document item
Doc. cat. Doc. number Doc. item Doc. sched. line Del. date PO 4500000012 10 0001 26.01. PO 4500000025 20 0001 28.01. PO 4500000025 20 0002 02.02. PO 4500000012 10 0002 26.02.
Here you can see that each schedule line was sorted according to its delivery date. Note that this type of processing requires more runtime due to the individual checks and more frequent saving.
The results of rescheduling are saved, as long as the program was not started in simulation mode. When calling up from the 'Sales' area menu or when directly starting via the development environment, the iniator is informed via a dialog box that he has just started a process that changes data. He can then decide whether or not he wants to continue.
Checking procedure for stock transfer documents:
An availability check of stock transfer documents in rescheduling is carried out in accordance with the check carried out when manually creating a document. If, however, the required quantity for a schedule line is not available on a particular date and will not be ready until later, new schedule lines are created for the stock transfer purchase orders and scheduling agreements, containing the relevant data. New items are created in this case for stock transfer purchase order requirements. The total sum of schedule line quantities for a processed schedule line corresponds to the schedule line quantity of the original schedule line.
First example: Using a stock transfer purchase order item with a schedule line:
a) Status of item before rescheduling run:
Del. date PO quantity Confirmed quant Confirmed del. date 23.07. 50 items 0 items -
==> This now affects the stock/requirement situation:
- Goods issue is posted for the material in the delivering plant on the 23.07.
- A purchase order of 10 items was created for the material in the delivering plant. Delivery is expected on the 29.07.
b) Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity Confirmed quant Confirmed del. date 23.07. 40 items 40 items 23.07. 29.07. 10 items 10 items 29.07.
==> The first schedule line was changed in accordance with the results of the rescheduling availability check. Only 40 of the 50 original items could be delivered on the 23.07. Therefore, a new schedule line is created for the rest on the 29.07. for 10 confirmed items.
Second example: Same output situation as the above example.
==> There is now a change in the requirement/stock situation:
A purchase order for 10 items is created for the material in the delivering plant. Delivery is expected on the 29.07. A further purchase shows another 40 planned items on the 30.07.
Status of stock transfer purchase order item after rescheduling run:
Del. date PO quantity Confirmed quant Confirmed del. date 29.07. 10 items 10 items 29.07. 30.07. 40 items 40 items 30.07.
==> The first schedule line was changed in accordance with the result of the availability check for rescheduling. The original delivery date is set to the date confirmed in the ATP check. A new schedule line is created for the remaining 40 items, that are available on the 30.07.
Note:
Any set fixed delivery date and quantity indicators and creation indicators for schedule lines or items are 'inherited' by newly created schedule lines. Assuming that the original schedule line was fixed in the above example (since it is created manually), this indicator is also set for the newly created schedule line.
If shipping scheduling is activated for a stock transfer document type, this is also implemented for newly created schedule lines, with the exception of route schedule determination. This means that in the current version of the program no route schedule has been determined for a schedule line containing a route schedule for which new schedule lines may need to be created.
The results of the run are issued in the form of a list, which is also saved, so that the results can be controlled at a later date. This is done using the function 'Evaluate rescheduling', but it is only a good idea to do this after the first rescheduling has taken place. You can restrict selection requirements but these can however affect the runtime. You can use this function to analyze the saved list until the next rescheduling run, which writes over the result. If you start rescheduling in the background, a spool file with the result list referred to will be created in the corresponding setting. You can see this in spool management.
Output
A list of changed documents, a list of documents in which an error occurred during processing and as a result were not changed, can be called up via the menu 'Edit - Error log'. If in a subsequent evaluation a restricted selection is carried out, a note appears at the end of the list to say that not all document items are displayed.
You can set the scope of the list under the menu option 'List' in the list display. You can view improvements, deteriorations and the whole list. Before the documents can be included in one or either of the restricted lists, the date or quantity has to have changed so that the item can be contained in both the list of improved or deteriorated documents.
You can use the interface for changing transactions and the order list to navigate. Use 'Back' to exit the list and 'New selection' to return to the selection screen.
Recommendation
You should only start this program occasionally and use very restricted selectin criteria during working hours as it requires enormous system resources.
Note
The columns for 'New date' and 'New confirmed qty' only contain entries if the dates or quantities have changed.
As the system only runs the change check (dates/quantities) per line in the original list, an item whose backlog has increased in the list of improvements. This occurs, for example, if the whole quantity can be delivered at once but at a later date. In this situation, the system determines an increase for the line when it compares quantities.
Regards,
Amrish Purohit -
How to Configure Transport MAnagement system in CHARM
Hi
How to Configure Transport MAnagement system in CHARM? Here our requirement is when ever a change request approved in the background Transport request should be created automatically. We have configured all the Transport Routes in our lanscape.
Can any one tell me the detailed process? If you have any Configuration document please share it to me
Points will awarded for helpful answer
Thanks
BhaskarIn a two system landscape is it necessary to make development the domain controller always?
No such compulsion as such exist(correct me if wrong),however why you want to make production your domain controller?
This is not recommended.
Regards,
Ashutosh -
Configuring RMAN for dataguard.
Hi all,
Here we have a dataguard environment with db1(db_unique_name) as primary and db2(db_unique_name) as physical standby database. For both primary and secondary the ORACLE_SID is 'oracledb'.We configured dataguard in 10g environments and we are not using grid control. And now we want to configure rman for incremental backups. We are using a third catalog database to which we registered from primary db successfully. During primary rman configuration it is showing conflicts. Even the changes made in primary RMAN configuration are applied on to the standby too which i think shouldn't happen in this scenario. How to resolve this issue? Is this happening because of the same ORACLE_SID for both primary and secondary? I'm attaching the link of the doc that we followed also the errors and configuration in rman. Can anyone help?
http://docs.oracle.com/cd/B28359_01/server.111/b28294/rman.htm#BAJFBBBB
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
new RMAN configuration parameters:
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
new RMAN configuration parameters are successfully stored
starting full resync of recovery catalog
full resync complete
RMAN-08591: WARNING: invalid archivelog deletion policy
RMAN> CONFIGURE DB_UNIQUE_NAME db1 CONNECT IDENTIFIER 'db1';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "db_unique_name": expecting one of: "archivelog, auxiliary, auxname, backup, channel, controlfile, clonename, compatible, datafile, device, default, exclude, encryption, maxsetsize, retention, snapshot"
RMAN-01007: at line 1 column 11 file: standard input
RMAN> show all;
starting full resync of recovery catalog
full resync complete
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_NIOS.f'; # default
Thanks.RMAN> show db_unique_name;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "db_unique_name": expecting one of: "all, archivelog, auxiliary, auxname, backup, channel, controlfile, datafile, device, default, exclude, encryption, maxsetsize, retention, snapshot"
RMAN-01007: at line 1 column 7 file: standard input
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01007: at line 1 column 21 file: standard input
But on this i'm getting response
SQL> select db_unique_name from v$database;
DB_UNIQUE_NAME
db1
same and db2 as db_unique_name for standby....
Edited by: 954758 on Sep 3, 2012 3:41 AM -
How to Configure Adapter for different environments?
Hi
I wanted to know solution to a pratical problem. If a communication channel is created by configuring a adapter, how is the configuration managed for different phases of the life cycle i,e when it goes from development to QA to Production. A adapter may need to be configured differently depending upon the environment it is in. I hope one doesn't have to change it every time it is taken from one environment to another. Is there any concept like properties file in XI?
VijayHI,
In general the Same evironment should be in both Dev and QA and also in Prod .
Whatever we developed in Dev environment , if you transport it to QA , the same should work, similarly in Prod also.
We have certain fecilities like cutomising the Communication channel with the Communication Channel Template.With this we can configure as per our needs.
Eventhough it is not sufficient to meet your BS requirement , then we need to have
Dynamic configuration see the below link for more details
Dynamic configuration in adapter modules - /people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules
Dynamic Configuration of Some Communication Channel Parameters using Message Mapping -
/people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
Regards
Chilla -
Configurations necessary for using EDI.
Dear All,
Kindly Give some light on configurations necessary for using EDI. I mean What is the use of EDI, How to use, what are the steps involve in that...
Regards
San Rao.Dear San,
EDI (Electronic Data Interchange) The transmitting of documents from one computer application to another computer application using a standardized format.
Why implement EDI?
Improves data accuracy: You can eliminate the need to re-enter data from paper documents and thus prevent potential data entry errors. It is estimated to be one-tenth the cost of handling its paper equivalent.
Reduces technical complexity: With EDI, companies use standardized data formats to exchange documents. EDI allows companies using different systems to achieve computer-to-computer electronic exchange of business documents.
Lowers personnel needs: EDI can help companies reduce the need for personnel involved in paper business transaction processing.
Accelerates information exchange: The lead time between start and completion of order processing is greatly reduced. By timeous scheduling companies can plan production more accurately and thus reduce stock inventories.
EDI technologies have evolved as a data carrier replacing the paper document. It is not a new concept or a new practice. EDI has existed for more than 2 decades in Europe and North America.
Early electronic interchanges used proprietary formats agreed upon between two trading partners requiring new programs each time a new partner was added to the existing system. Lateron some industry groups began a cooperative effort to develop industry EDI standards for purchasing, transportation, and financial applications. Many of these standards supported only intra-industry trading, which led to a large number of EDI formats.
In 1979, the Accredited Standards Committee (ASC) X12 was formed to develop a generic EDI standard. In 1993, Version 3, Release 4 contained 192 standards. There are over 100 additional standards in development. In the U.S., the most commonly used standard is ANSI X12, coordinated by the American National Standards Institute (ANSI). While in Europe, it is the Electronic Data Interchange for Administration, Commerce, and Transportation (EDIFACT) standard. SAP maps it message types by EDIFACT naming conventions
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh -
Hi All
I have created new layout set
I want to transport it to QA , please let me know the steps to transport the newly created layout set
Thanks
Karthi D.Hi Karthi,
In this blog series, Gopala Krishan explains how to transport KM Configurations.
Link: [KM Transports Part I|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4163]
Link: [KM Transports Part II|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4171]
Link: [KM Transports Part III|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/4177]
I'm on Portal 7.0 SP20 and I know for sure that KM Configuration Transport procedures are all valid. (KM Content Transports changed since SP14).
The only difference could arise if you are using CTS+ for transports (if you are not, ignore this sentence).
Hope it helps.
Best Regards,
Marcelo -
Configuring Transport workflow
Hi all
I am planning to configure transport workflow in the Solutioin Manager 4.0 box. It already has TMS configured on that.If I configure Transport workflows will the already existing TMS will be deteled?
Plz reply soon
JyotiHello,
each satellitesystem has his own domain controller.
The Solman is connected via domain link with these domain controller of each satellitesystem.
You can create this Links in two Steps:
1. - Logon in Solman system where the domain controller is located
- Tcode: STMS→Overview→Systems
- Mark the satellitesystem where the domain controller is located
- SAP System→Create→Domain Link execute
Now you only create the request for an domain link!
2. - Logon in satellitesystem where the domain controller is located
- Tcode: STMS→Overview→Systems
- Mark the satellitesystem where the domain controller is located
- There must be an option to answer the request from the Solman
You can check the domain link in Solman when you click in STMS on the button Legend.
The Typ Other Domain Controller has a special symbol.
You get detailed informations about domain link in the SAP Library SAP Solution Manager.
http://help.sap.com/saphelp_sm40/helpdata/en/ae/64c33af662c514e10000000a114084/frameset.htm
Please type in the search field "create domain link".
You will get some detailed documentations for domain link.
The transport workflow is realized in Solman with CRM and Solman actions.
Example:
If the status of service order SDHF (urgent correction) is changed from "In development" in status "To be tested".
there is an automatic transport into QAS system. Please be sure that you have realized the transport task, before.
You can create also a backround job for each system/mandant (except the productive system) for automatic import of all realized transport requests. We planed these backround jobs in all of our satellitesystems (except the productive system) every 10 minutes.
For you productive system you should start the backround job (Import Transport Request (Background) from the maintenance cycle manually. The report is called /TMWFLOW/SCMA_TRORDER_IMPORT.
This report imported all realized transport requests from the import queue of your system.
Hope it was helpful
Best regards
Thomas -
Error trying to configure ADS for printing from BW reports
hi all,
i am trying to configure ADS for printing off reports from the BW portal. I am using BI 7.0 (BW Portal version 7.0 SP10) and am getting the following error i nthe default trace file.
#1.5#00187177BCAA008D000000DD0000144C00043EE522456586#1195053750220#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.base.exception.BIBaseRuntimeException#PASS.TEST#1678##BWD#PASS.TEST #B373727691C24C2FADD8534371BB536E#SAPEngine_Application_Thread[impl:3]_28##0#0#Fatal#1#/Applications/BI#Plain###Exception thrown: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:216)
at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)
at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0.processFunction(PRTRFCRemoteObjectImpl0.java:118)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy145.processFunction(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:419)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.createExportResult(PageExport.java:157)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getPdfForPage(PageExport.java:166)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getExports(PageExport.java:183)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.processPage(PrecPageAssembler.java:271)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.run(PrecPageAssembler.java:195)
at com.sap.ip.bi.broadcasting.runtime.impl.ProducerPrecalculation.produce(ProducerPrecalculation.java:415)
at com.sap.ip.bi.broadcasting.runtime.RfcListenerRSRD_X_PRODUCE.handleRequest(RfcListenerRSRD_X_PRODUCE.java:130)
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:181)
... 28 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
... 42 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
... 44 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 46 more
#1.5#00187177BCAA008D000000E00000144C00043EE522456FA1#1195053750220#com.sap.ip.bi.base.application.message.impl.MessageBase#sap.com/com.sap.prt.application.rfcframework#com.sap.ip.bi.base.application.message.impl.MessageBase#PASS.TEST#1678##BWD#PASS.TEST #B373727691C24C2FADD8534371BB536E#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#/Applications/BI#Plain###A message was generated:
ERROR
Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
com.sap.ip.bi.base.exception.BIBaseRuntimeException ERROR
com.sap.ip.bi.base.exception.BIBaseRuntimeException
Log ID: 00187177BCAA008D000000DD0000144C00043EE522456586
Initial cause
Message: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
Stack trace: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.createExportResult(PageExport.java:157)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getPdfForPage(PageExport.java:166)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getExports(PageExport.java:183)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.processPage(PrecPageAssembler.java:271)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.run(PrecPageAssembler.java:195)
at com.sap.ip.bi.broadcasting.runtime.impl.ProducerPrecalculation.produce(ProducerPrecalculation.java:415)
at com.sap.ip.bi.broadcasting.runtime.RfcListenerRSRD_X_PRODUCE.handleRequest(RfcListenerRSRD_X_PRODUCE.java:130)
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:181)
at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)
at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0.processFunction(PRTRFCRemoteObjectImpl0.java:118)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy145.processFunction(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 46 more
Message: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
Stack trace: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error: com.sap.ip.bi.base.exception.BIBaseRuntimeException
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:216)
at com.sap.ip.bi.portalrfc.services.BIRfcService.handleRequest(BIRfcService.java:247)
at com.sapportals.portal.prt.service.rfc.RFCEngineService.handleEvent(RFCEngineService.java:341)
at com.sapportals.portal.prt.service.rfc.PRTRFCBean.processFunction(PRTRFCBean.java:37)
at com.sapportals.portal.prt.service.rfc.PRTRFCRemoteObjectImpl0.processFunction(PRTRFCRemoteObjectImpl0.java:118)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy145.processFunction(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156)
at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7785)
at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2405)
at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1728)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:8145)
at com.sap.mw.jco.JCO$Server.work(JCO.java:8265)
at com.sap.mw.jco.JCO$Server.loop(JCO.java:8212)
at com.sap.mw.jco.JCO$Server.run(JCO.java:8128)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:419)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.createExportResult(PageExport.java:157)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getPdfForPage(PageExport.java:166)
at com.sap.ip.bi.webapplications.pageexport.broadcasterapi.PageExport.getExports(PageExport.java:183)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.processPage(PrecPageAssembler.java:271)
at com.sap.ip.bi.broadcasting.runtime.impl.precalculation.PrecPageAssembler.run(PrecPageAssembler.java:195)
at com.sap.ip.bi.broadcasting.runtime.impl.ProducerPrecalculation.produce(ProducerPrecalculation.java:415)
at com.sap.ip.bi.broadcasting.runtime.RfcListenerRSRD_X_PRODUCE.handleRequest(RfcListenerRSRD_X_PRODUCE.java:130)
at com.sap.ip.bi.portalrfc.dispatcher.services.BIServicesRfcDispatcherService.doHandleRequest(BIServicesRfcDispatcherService.java:181)
... 28 more
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
... 42 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
... 44 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 46 more
com.sap.ip.bi.base.exception.BIBaseRuntimeException ERROR
com.sap.ip.bi.base.exception.BIBaseRuntimeException#
#1.5#00187177BCAA0084000000120000144C00043EE523772516#1195053770252#com.sap.ip.bi.export.xfa.impl.PDFConverter#sap.com/irj#com.sap.ip.bi.export.xfa.impl.PDFConverter#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Plain###EXPORT XFA calcTemplate=Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out#
#1.5#00187177BCAA0084000000130000144C00043EE523772FEE#1195053770252#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/irj#com.sap.ip.bi.base.exception.BIBaseRuntimeException#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Plain###Exception caught: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:403)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:97)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:217)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:2735)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:2478)
at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:2432)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2054)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:931)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:873)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:324)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
... 51 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 53 more
#1.5#00187177BCAA0084000000140000144C00043EE523773518#1195053770252#com.sap.ip.bi.base.exception.BIBaseRuntimeException#sap.com/irj#com.sap.ip.bi.base.exception.BIBaseRuntimeException#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Fatal#1#/Applications/BI#Plain###Exception thrown: com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
com.sap.ip.bi.base.exception.BIBaseRuntimeException: Unknown Error
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:419)
at com.sap.ip.bi.export.xfa.widthcalc.WidthCalculator.<init>(WidthCalculator.java:55)
at com.sap.ip.bi.export.xfa.impl.SizeCalculator.calc(SizeCalculator.java:88)
at com.sap.ip.bi.export.impl.ExportController.calculateAndSetSizes(ExportController.java:569)
at com.sap.ip.bi.export.impl.ExportController.doExportPrep(ExportController.java:454)
at com.sap.ip.bi.export.impl.ExportController.convert(ExportController.java:368)
at com.sap.ip.bi.export.controller.ExportResult.createExport(ExportResult.java:58)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.createPDF(PageExportRenderingRootNode.java:403)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.doExport(PageExportRenderingRootNode.java:97)
at com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode.processRendering(PageExportRenderingRootNode.java:217)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRenderingRootNode(Page.java:2735)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRendering(Page.java:2478)
at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:2432)
at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2054)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:931)
at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:873)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:324)
at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:21)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:405)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:334)
at com.sap.ip.bi.export.xfa.impl.Document.writeWidthsAsXmlToStream(Document.java:413)
... 49 more
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
java.net.SocketTimeoutException: Read timed out
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:89)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:99)
at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:382)
... 51 more
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:806)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:341)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:250)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:362)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:551)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:82)
... 53 more
#1.5#00187177BCAA0084000000170000144C00043EE5237744D3#1195053770252#com.sap.ip.bi.base.application.message.impl.MessageBase#sap.com/irj#com.sap.ip.bi.base.application.message.impl.MessageBase#PASS.TEST#1642##triombwd01.corp.net_BWD_9280250#PASS.TEST#45ddd21092c511dc9cbf00187177bcaa#SAPEngine_Application_Thread[impl:3]_58##0#0#Error#1#/Applications/BI#Plain###A message was generated:
ERROR
Error while generating PDF
com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode PageExportRenderingRootNode_0001
Error while generating PDF
com.sap.ip.bi.webapplications.pageexport.PageExportRenderingRootNode PageExportRenderingRootNode_0001#Hi Glenn,
i faced the same problem
did you solve yours meanwhile ?
regards,
Carsten -
The boot configuration data for your Pc is missing or contains errors: error code 0x000014c
Hello,
See if any body may help here... I get this blue screen:
RECOVERY
Your PC needs to be repaired:
The Boot Configuration Data for your PC is missing or contains errors.
file:\\EFI\Microsoft\Boot\BCD
Error code: 0xc000014c
You'll need to use the recovery tools on your installation media. If you don't have any installation media (like a a disc or USB device), contact your system administrator or PC manufacturer.
Press Esc for UEFI Firmware Settings
First I was able to get into the option 11 and run the whole factory reset, i was so happy because I tought it will be easy.. but then after I did the factory reset.. I keep getting this blue screen. if I press ESC I get into this next screen:
F1 System Information
F2 System Diagnostics
F9 Boot Device Options
F10 BIOS Setup
F11 System Recovery
ENTER - Continue Startup.
this is what happen when I click any of this options:
F1 I get into the System Information with no problems, then I click <ESC> to continue and get back to the last screen... then I press F2 and super, I am able to run Memory Test and Hard Drive Check 100% with no problems in any of those, after I am done with my teste I press exit and I am back to the F1,F2, ETC menu... now I want to try F9, F10 or F11. bummer.. in this 3 options I get back to the blue screen described at the beggining of this post. (I already connect a USB with an boot loader, which works perfectly)
so I can't do anything, nothing at all!! crazzines.
So what I did to check why I can't get into the BIOS or at least to boot from my USB... I removed the botton cover of my laptop and removed the hard drive and that's how then I was or I am able to Log into the BIOS, - I did the changes to boot first from the USB and then from the HD and this is how I was able to boot from the USB - BUT If I connect back the Hard drive, I am not able to get into the BIOS or boot from the USB - so basically I am stuck in this blue screen and I can't boot from a USB if I have the HD connected.. I can't use any option.. no BIOS, nothing.. only if again, i disconnect the HD.
This is an:
HP ENVY TS Sleekbook 4
PRODUCT NUMBER D1A99UA#ABA
SYSTEM BOARD ID: 1894
Bios F.25
**** I though that by updating the BIOS I may be able to get help, nothing. What I did is, I removed the HD and then and boot from the USB and with a DOS command propmt I excecuted the Bios Update from F.21 to f.25... but again, when I installed the hard drive back, BUMMER, nothing I can't do nothing but this silly blue screen.
Any idea of what should I do?
Thanks in advance.
This question was solved.
View Solution.If you can't access BIOS with the hard disk connected, you certainly won't be able to boot to the usb recovery flashdrive. That is indicative of a failed hard disk.
Install a new hard disk and then boot to the recovery flashdrive.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer
Maybe you are looking for
-
I just updated today, and now a project I had been working on for weeks (my first real project) won't open in CC anymore. The only reason I wanted to open it back up in CC - NOT Adobe Edge Animate CC (2014), was because this updated Edge Animate IS M
-
Where do i insert a cd into my new iMac?
I just setr up my new mac. I can't find a place to insert a CD or DVD?????
-
How can I activate an old version of Adobe Encore (1.5)?
I am trying to re-install my purchased version of Adobe Encore 1.5. I realize this program is several years old and no longer supported, however, it still suits my needs and I would like to continue using my purchase. Since the activation site is n
-
Hi All, I have a problem of these iPhoto and iMovie, I have bought my Mac more than 8 months, but I launch my iPhoto and iMovie less than 5 times because I have completely no ideas how it works, so, does anyone know about iPhoto and iMovie and do yo
-
Any chance someone can help me please? An error message keeps coming up along the lines of "not enough space to receive SIM messages. Delete some data first". I've deleted all of my messages, including sound files etc. I can make calls and receive th