Problems with SLD
Hello,
I have two interfaces, the first is a file to bapi interface and the other is a file to IDOC interface. How many products, software components, technical system and business system I need?
Thanks.
Hi,
its depend on the system and the landscape ur using.
if ur sending to two different system, then u have to create two different technical and business system.
The specified item was not found.
Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak
XI Software Logistics 1: SLD Preparation
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
Configuring SLD in Sneak Preview SAP NetWeaver '04 Sneak - SLD preview
SLD - http://help.sap.com/saphelp_nw04/helpdata/en/6e/fba1c735e0b44496072595092d924c/frameset.htm
Error while reading ID of own business system from the SLD
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30f8bd90-0201-0010-dd9a-c8a7f52c47aa
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
Regards,
Phani
Similar Messages
-
Problem with SLD and Creation of JCo
Hello everyone!
I have a problem with the SLD and the Creation of JCo on the Portal, in trying to create the JCo always tells me that the name used there in the SLD, being that the facility is new.
Who performs the installation, set in the SLD the ECC 6 PRD, delete it to see if I could create a JCo but still the error again when creating the ECC 6 PRD in the SLD I said that already exists and can not create it.
I found a forum which recommended re-import the cimsap .... .... zip and zip CR_Content which would clean everything, I managed to import the zip cimsap ... but in trying to raise CR_Content gives me the following message "All incremental updates of the selected aggregate import for export SAP_CR line have already been loaded before. You require a newer import to update your current content SAP_CR version 4.11." .
I recommend, do the installation again, reload the cimsap.zip and CR_Content.zip a copy homogeneous.
from already thank you very much
Text of error to create JCo destination
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
at at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
at at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
at at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionGoForward(ButtonBar.java:505)
at at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:280)
at at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
... 28 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; InfoPath.1)
Version null
DOM version null
Client Type msie7
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0017.20081210091801.0000 (release=NW04S_17_REL, buildtime=2009-01-12:09:43:27[UTC], changelist=52884, host=pwdfm114), build date: Tue Apr 28 19:28:39 CLT 2009
J2EE Engine 7.00 patchlevel 48199.450
Java VM IBM J9SE VM, version:2.2, vendor: IBM Corporation
Operating system Linux, version: 2.6.18-92.el5, architecture: amd64
Session & Other
Session Locale en
Time of Failure Fri Aug 28 11:43:53 CLT 2009 (Java Time: 1251474233677)
Web Dynpro Code Generation Infos
sap.com/tcwdtools
No information available null
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionGoForward(ButtonBar.java:505)
at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:280)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)Hello!!
The "SLD" with which I am working up to Portal, the "ECC" installs itself as "ABAP.
Who did the installation and initial configuration, do not leave any documentation about it.
Now I need to create the systems and "JCo" necessary to enable them to implement the "ESS", but errors are presented above.
Some days ago I managed to update the CR_Content, which allowed me to create the "JCo" but at the time of the test, says' com.sap.mw.jco.JCO $ Exception: (103) RFC_ERROR_LOGON_FAILURE "name or password incorrect .
I managed to also create the portal systems, "System Administration -> System Configuration -> Content Portal" and to test it fails on "Test Connection with Connector", which as noted is associated with the connectors "JCo".
For the creation of the system, I think I should create something in the Visual Administrator ", but within the documentation that I do not see anything about it.
thanks for your help! -
PI 7.1 - Problem with SLD and Runtine WorkBench
Hi All,
I have installed PI 7.1 on Solaris with Oracle DB.
When i go to http://<hostname>:54600/dir/start/index.jsp and click on System Landscape Directory its opening the following link:
http://54600:54600/sld/index.html (Instead of hostname its taking 54600 where 46 is our instance Number).
Could you please suggest me whether the above error is due to any parameter wrongly set? i have checked all the exchange profile parameters and everything is fine.
If this is the problem with configuration of SLD, Can I re-configure SLD? if so please guide me how to do that.
Even when i login into Runtime Work Bench and clcik on any option like Component Monitoring or Message Monitoring its taking long time stating "Query being Processes", i waited for long time and then the same error unable to reach "http://54600:54600 "
Could you please suggest me how to proceed further?
Thanks,
SubbuHi,
Please check the following configurations:
ABAP stack:
1. SLDCHECK - check the error.
2. SLDAPICUST - check the 'Host name'
Then, in browser;
http://<hostname>:54600/exchangeProfile
click and expand 'connections' -
com.sap.aii.connect.cr.name - fully qualified host name
com.sap.aii.connect.integrationserver.sld.name - is.<instancenumber>.<Hostname>
com.sap.aii.connect.landscape.httpport - 5 <instancenumber> 00
Use fully qualified host name where ever the host name is asked.
Once you edit the exchange profile, not necessary to restart J2ee Engine. Just refresh and check the value are changed.
Hope this will fix the issue.
Sunil Shetty. -
Problem with SLD in XI Configuration
Hi,
I am getting the error like "Role Assignment Failed" while trying to do post installation activities in XI.when we go to SLD Data Supplier Bridge and required inputs are provided in the fields and click on "assign application roles to user groups" .
thanks in advance........
Regards
RamHi Ram,
See these...
role assignment failed on sld data supplier
Role assignment failed
cheers,
Prashanth
P.S Please mark helpful answers -
PI 7.1 Problem with Fully Content Syncronization of SLD
Hi All,
I am trying to implement the fully content Syncronization of SLD. My two SLDs are of 7.1 and 7.0 version and i am trying to perform a sync (unidirectional one)
I have fullfilled the criterias required
1. The two sld model version are same 1.5.41
2. The SLD with version 7.0 is of Support pack 15
I have configured the Syncorization by adding a new connection and used SLDDSUSER for connection to the source system SLD on PI 7.0
while running the full sync option . All the contents like technical system etc has been pulled but the sync fails @ 94% saying
Error: CIM_ERR_FAILED: Can not remove method scope for qualifier EmbeddedObject (namespace: sld/active)
In SLD logs this is the details
#4 05/05/2009 19:59:03.214 [SLD ContentSync sld/active] ERROR com.sap.sld.contentsync.ContentSyncerIncremental: Sync failed, SLD entries may not be fully synchronized as expected.
CREATE QUALIFIER_DECLARATION
EmbeddedObject
Id 1,243,945,900,000,044,000
Rank 1
ForeignOrigin null
ForeignId 0
Connection source: http://<targethostname>:50000/sld/cimom, namespace sld/active, target: <local>, namespace sld/active
<?xml version="1.0"?>
<QUALIFIER.DECLARATION NAME="EmbeddedObject" TYPE="boolean">
<SCOPE PROPERTY="true"/>
<VALUE>FALSE</VALUE>
</QUALIFIER.DECLARATION>
Thrown:
com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: Can not remove method scope for qualifier EmbeddedObject (namespace: sld/active)
at com.sap.cim.objmgr.requests.WBEMSetQualifier.modifyQualifier(WBEMSetQualifier.java:120)
at com.sap.cim.objmgr.requests.WBEMSetQualifier.execute(WBEMSetQualifier.java:77)
at com.sap.cim.objmgr.requests.WBEM_WriteRequest.execute(WBEM_WriteRequest.java:71)
at com.sap.cim.objmgr.core.CIMObjectManager.executeWriteRequest(CIMObjectManager.java:1719)
at com.sap.cim.objmgr.core.CIMObjectManager.executeImpl(CIMObjectManager.java:1645)
at com.sap.cim.objmgr.core.CIMObjectManager.execute(CIMObjectManager.java:1591)
at com.sap.cim.objmgr.core.CIMObjectManager.setQualifier(CIMObjectManager.java:1463)
at com.sap.cim.service.WBEMLocalServiceClient.setQualifierDeclarationImpl(WBEMLocalServiceClient.java:685)
at com.sap.sld.api.wbem.client.WBEMAbstractClient.setQualifierDeclaration(WBEMAbstractClient.java:778)
at com.sap.sld.contentsync.CSP_SetQualifier.process(CSP_SetQualifier.java:29)
at com.sap.sld.contentsync.ContentSyncerIncremental.processAndResolveConflicts(ContentSyncerIncremental.java:520)
at com.sap.sld.contentsync.ContentSyncerIncremental.processEntry(ContentSyncerIncremental.java:399)
at com.sap.sld.contentsync.ContentSyncerIncremental.incrementalSyncImpl(ContentSyncerIncremental.java:285)
at com.sap.sld.contentsync.ContentSyncerIncremental.incrementalSync(ContentSyncerIncremental.java:194)
at com.sap.sld.contentsync.SyncRunner.runIncrementalSync(SyncRunner.java:180)
at com.sap.sld.contentsync.SyncRunner.run(SyncRunner.java:245)
at com.sap.sld.contentsync.SyncRunner.run(SyncRunner.java:336)
at java.lang.Thread.run(Thread.java:606)
Can anyone who has done this explain me what is the problem with this. I am sure that we can configure it with PI 7.0 in unidirectional atleast
Rgds
AdityaI will be trying this senario with two 7.1 SLDs hope so it works
Rgds
aditya -
[SLD] Problems with Export
Hi,
I have to move from development to test-system, so I did an export
of design objects and the admin import this file into the new system.
He didn't create the Business Systems, Technical System, SWK or
Product in SLD, so I thought I could do this manuelly. I created all
object with same name as in development system, but in directory
he couldn't find all interfaces while defining determination and agreements.
So I found in another thread, that I have to export the SLD objects because
of an ID they have, is this correct?
Is it normal, that I can't edit design objects after import in new system or is
it because of authorisation?
The manual "How To Handle the SLD for SAP XI" describes how to export
objects from SLD, but when I try to download the export file a error occurs:
"The requested resource does not exist." But only with BS and TS. The product
and SWK could be download normally. Any ideas why?
The correct way of exporting is:
-Export/Import technical system
-Export/Import business system
-Export/Import product
-Export/Import SWK
-Export/Import design objects
-Create configuration objects (communication channel and so on)
Correct??
Thanks
chrisHi,
I didn't create transport targets. As far as I understood, these are necessary
to connect groups of Business Systems within ONE SLD. I have to
tranpsort those objects from one server to another. Correct?
Your are right. Normally I shouldn't develop on a test system. I was just
curious why it wasn't editable anymore.
But I still got this problem with my export. An idea why I can't download the
file?
@Prashanth
I've seen this before, but I'm not sure if I'm able
to install this on all systems (authorization). And
is this really necessary, if I normally can simple export
the objects as file?
thanks
Message was edited by:
Christian Riekenberg -
SLD problem with transaction SLDCHECK
Hi,
I am configuring XI 3.0Sr1 to worK with SLD on Netweaver 04 stack 10, everything is good until I come to test the connection with the transaction SLDCHECK.
What happens is that a browser window is displayed with the SLD server address in the address bar, but no content. The XI check passes successfully.
Having debugged the transaction the prblem seems to lie within the call to a function module "SLDJAVA_ACCESSOR_REQUEST" at RFC destination "SAPSLDAPI".
the function module returns with a sy-subrc of 8 and the following message in the s-msgv1 - 4 parameters.
"AbapSLDRequestHandler.execEnumerateInstances(): Invalid begin of response [expected: 'HTTP', found:'´###############ö###9Packet length (1347375956) bigger than the max specified!ö####ö###Yjavax.jms.J尀倀爀"
The SLD communicates correctly using RZ10 and I have set up the connection in SLDAPICUST.
Does anybody have any idea what the problem might be as I am running out of ideas.
Thanks in advance
Ed.Hi,
I managed to get the full java error (by using a different browser). The following now appears in the browser window when you rin SLDCHECK.
´?ö9Packet length (1195725856) bigger than the max specified!ööYjavax.jms.JMSException: Packet length (1195725856) bigger than the max specified! at com.sap.jms.protocol.MultiPacketImpl.createPackets(MultiPacketImpl.java:160) at com.sap.jms.protocol.MultiPacketImpl.getNotCompletePacket(MultiPacketImpl.java:106) at com.sap.jms.server.protocol.manager.PacketManagerImpl.processData(PacketManagerImpl.java:77) at com.sap.jms.dispatcher.JMSDispatcherFrame.parseRequest(JMSDispatcherFrame.java:512) at com.sap.engine.core.manipulator.TCPRunnableConnection.sleepRead(TCPRunnableConnection.java:726) at com.sap.engine.core.manipulator.TCPRunnableConnection.run(TCPRunnableConnection.java:527) at com.sap.engine.frame.core.thread.Task.run(Task.java:60) at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:72) at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:142)
Hope somebody know what it means.
Ed -
Problem with IDoc scenario - IDocs do not aarive to XI
Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM -
Integration Engine does not connect with SLD
Hi all,
We have an XI 3.0 system that acts as QUA system in our track. This XI 3.0 system is connected to a central SLD installed on a PI 7.1 system that acts as our DEV system.
Everything seems to be OK in the Java part. We refresh the caches successfully and enter the SLD in DEV system.
We have a problem, though with the SXI_CACHE transaction. It shows the following message:
"Unable to refresh cache contents.Error during last attempt to refresh cache"
And the detail of the error is: "LCR_GET_OWN_BUSINESS_SYSTEM - NO_BUSINESS_SYSTEM"
We have checked in the SLD and the Business system is created.
In transaction SXMB_ADM when checking the Integration Engine connection with SLD we get the following error: "No access to system landscape at present"
In the Runtime Workbench of the system, when checking the Cache Connection, the Integration Engine part shows a warning. In the RWB also the Self Status Check of the Integration Engine gives errors:
"Are roles in SXMS_CONF_ITEMS and SLD consistent?"
We have already followed all the post installation guides, and the cache checks, and SLD checks guides.
Do you know which the soltion could be for our error??
Thanks!Hi,
We have checkes
SM59: TCP/IP Destination: LCRSAPRFC y SAPLSDAPI. check the program ID is correct.--> connection test goes OK
HTTP destination: INTEGRATION_DIRECTORY_HMI: do a test connection: result=500--> connection test gives us 500 result
SLDAPICUST: Check the user and password and the server defined. the PI server should be the main server.--> checked, OK
SXMB_ADM>Integration Engine Configuration: Check if the destination is properly defined. should be dest://http://<server><port>/sap/xi/engine?type=entry> checked. OK
Check RZ70: wich configuration you have there?--> The configuration in the RZ70 for the SLD is pointing to the DEV system, so it is correct
SLDCHECK results:
"Properties of RFC destination SAPSLDAPI
RFC host: %%RFCSERVER%%
program id: SAPSLDAPI_XXX
gateway host: XXXX
gateway service: XXXXX
Testing the RFC connection to the SLD java client...
RFC ping was successful
SLD server access settings:
host name: XXXXX
port number: 50000
user : XIAPPLUSER
Use transaction SLDAPICUST if you wish to maintain the SLD server access data
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call terminated sucessfully
List of business systems maintained in the SLD:
(...more...)
Calling function LCR_GET_OWN_BUSINESS_SYSTEM
Retrieving data from the SLD server...
No corresponding business system found for system XXX client 450
=> Check and maintain the SLD content for the current client
Summary: Connection to SLD works technically, but the SLD content may need maintenance
=> Check and maintain the SLD data content
*Unable to refresh cache contents.Error during last attempt to refresh cache" * this error is related with the RFC destination type HTTP. ( HTTP destination: INTEGRATION_DIRECTORY_HMI: do a test connection: result=500) -
We are getting the following error when the XI stack starts up. It seems to point to a problem in the Exchange Profile. However, I am not sure whether it is complaining because of incorrect parameters or because it is unable to access it. This instance of XI has been running just fine for the last few months and we have had no problems with it. All the J2EE services are shut down as the exception shows. Any insight into what the problem might be is well appreciated.
FYI, We haven't added any patches for the last couple of months. It was working fine during that time.
Included is the output from the log.
stdout/stderr redirect
node name : server0
pid : 4500
system name : XID
system nr. : 00
started at : Thu Jan 20 14:57:26 2005
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude iaik/security/md/SHA a
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
SAP J2EE Engine Version 6.40 PatchLevel 87037.313 is starting...
Loading: LogManager ... 4687 ms.
Loading: PoolManager ... 16 ms.
Loading: ApplicationThreadManager ... 142 ms.
Loading: ThreadManager ... 158 ms.
Loading: IpVerificationManager ... 126 ms.
Loading: ClassLoaderManager ... 78 ms.
Loading: ClusterManager ... 1558 ms.
Loading: LockingManager ... 724 ms.
Loading: ConfigurationManager ... 5647 ms.
Loading: LicensingManager ... 47 ms.
Loading: ServiceManager ...
Loading services.:
Service cross started. (47 ms).
Service memory started. (47 ms).
Service file started. (173 ms).
Service timeout started. (126 ms).
Service userstore started. (31 ms).
Service runtimeinfo started. (31 ms).
Service tcsecvsi~service started. (362 ms).
Service p4 started. (1541 ms).
Service trex.service started. (692 ms).
Service jmx_notification started. (865 ms).
Service classpath_resolver started. (126 ms).
Service tcsecwssec~service started. (661 ms).
Service deploy started. (10662 ms).
Service log_configurator started. (11997 ms).
Service locking started. (16 ms).
Service apptracing started. (424 ms).
Service http started. (533 ms).
Service naming started. (816 ms).
Service ts started. (203 ms).
Service javamail started. (298 ms).
Service failover started. (220 ms).
Service licensing started. (47 ms).
Service appclient started. (282 ms).
Service jmsconnector started. (455 ms).
Service connector started. (204 ms).
Service configuration started. (16 ms).
Service webservices started. (2887 ms).
Service dbpool started. (9428 ms).
Service com.sap.aii.af.svc started. (942 ms).
Service com.sap.security.core.ume.service started. (4048 ms).
Service security started. (5083 ms).
Service applocking started. (486 ms).
Service shell started. (675 ms).
Service tceCATTPingservice started. (189 ms).
Service classload started. (549 ms).
Service telnet started. (220 ms).
Service keystore started. (1789 ms).
Service ssl started. (156 ms).
Service ejb started. (2322 ms).
Service servlet_jsp started. (2400 ms).
Service tcsecsecurestorage~service started. (753 ms).
Service dsr started. (2150 ms).
Service jmx started. (2730 ms).
Service webdynpro started. (2526 ms).
Service tcsecdestinations~service started. (753 ms).
Service pmi started. (392 ms).
Service basicadmin started. (894 ms).
Service adminadapter started. (659 ms).
Service sld started. (2824 ms).
Service rfcengine started. (5098 ms).
Service monitor started. (4032 ms).
Service tc.monitoring.logviewer started. (7608 ms).
Service com.sap.aii.af.ms.svc started. (7640 ms).
Service jms_provider started. (11437 ms).
Service com.sap.aii.af.cpa.svc started. (11718 ms).
Service com.sap.aii.adapter.marketplace.svc started. (188 ms).
Service com.sap.aii.adapter.xi.svc started. (282 ms).
Service com.sap.aii.af.security.service started. (204 ms).
Service com.sap.aii.adapter.bc.svc started. (361 ms).
Service com.sap.aii.adapter.mail.svc started. (94 ms).
Service com.sap.aii.adapter.jms.svc started. (644 ms).
Service com.sap.aii.adapter.jdbc.svc started. (612 ms).
Service com.sap.aii.adapter.file.svc started. (659 ms).
Service com.sap.aii.af.ispeak.svc started. (706 ms).
Service com.sap.aii.adapter.rfc.svc started. (1882 ms).
ServiceManager started for 69917 ms.
Framework started for 84184 ms.
SAP J2EE Engine Version 6.40 PatchLevel 87037.313 is running!
PatchLevel 87037.313 October 19, 2004 19:52 GMT
>### Excluding compile: iaik.security.md.SHA::a
Jan 22, 2005 3:03:51 AM com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Jan 25, 2005 10:17:28... ...utilxi.prop.api.PropertySourceFactory [SAPEngine_Application_Thread[impl:3]_0] Fatal: XI properties could not be initialized. Check ExchangeProfile (or aii.properties).
Thrown:
java.lang.Throwable: dummy Throwable for stack trace
at com.sap.aii.utilxi.prop.api.PropertySourceFactory.getPropertySource(PropertySourceFactory.java:55)
at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:528)
at com.sap.aii.utilxi.misc.api.AIIProperties.<init>(AIIProperties.java:301)
at com.sap.aii.utilxi.misc.api.AIIProperties.getInstance(AIIProperties.java:328)
at com.sap.aii.ib.server.util.perf.TimerFactory.<clinit>(TimerFactory.java:86)
at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:73)
at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
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 $Proxy30.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.handleRequest(RFCDefaultRequestHandler.java:95)
at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
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:94)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Jan 29, 2005 7:37:28 AM com.sap.engine.core.configuration [SAPEngine_Application_Thread[impl:3]_23] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Jan 31, 2005 4:11:19 PM ...l.cache.WebResourceCache.startService [Thread[Thread-1140,5,SAPEngine_Application_Thread[impl:3]_Group]] Fatal: Tried to save: ~wd_key0_1107205757104
Feb 5, 2005 3:07:25 AM com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Feb 5, 2005 3:02:56 PM com.sap.engine.core.configuration [SAPEngine_System_Thread[impl:5]_78] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Feb 6, 2005 3:03:13 PM com.sap.engine.core.configuration [SAPEngine_System_Thread[impl:5]_77] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
Feb 19, 2005 3:15:45 AM com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error
SAP J2EE Engine Version 6.40 PatchLevel 87037.313 is shutting down! PatchLevel 87037.313 October 19, 2004 19:52 GMT
Stopping services.
Service com.sap.aii.adapter.rfc.svc stopped. (439 ms)
Service com.sap.aii.af.ispeak.svc stopped. (78 ms)
Service com.sap.aii.adapter.marketplace.svc stopped. (15 ms)
Service com.sap.aii.adapter.jdbc.svc stopped. (79 ms)Hi Sunit,
Did you figure out what happened? We're seeing the same issue.
Thanks,
Jay -
Hello,
I would like to thanks all SDN members to complete my PI installtion . Though i am new to this installation, with guides and you, i could able to manage.
Below are the steps i followed:
1. Installtion done with SAPinst ( PI70, 2004s SR1)
2. followed NW70 SR1 abap+java guide with MaxDB on windows guide.
3. Done local SLD configuration step 5.19 as per as guide <b>before running template installter.</b> to assign PIAPPLUSER ro sld* assing role in visual admin.
I believe this step for the PI instance to communicate with SLD.
Now i tried to login to --> host:port/nwa with IE7
here i got problem, it is giving error.
Is PI7 is not compatible with IE7. or do i have to do any security settings for this.
But i can able to access with IE6 from other XP machine and manage to run template installer.
Thanks in advance for ur help,
SrinivasNot just Template Installer but all WebDynpro based applications, up to NW 7.0 SP9, had this problem. From SP10, it has been corrected. Just so you know, SR1 is based on SP6 .
https://service.sap.com/sap/support/notes/991449
My sugestion is: finish your installation with IE6 from another machine and, once you're finished, patch your system up to SP12 or SP13.
Regards,
Henrique. -
Connector problem with access enforcer
Hi Guys,
I am facing a really strange problem with my connectors.
We have a test installation of GRC which was down for about 3 months.
During this time we migrated our central SLD to another system so I needed to change the connection after getting the system up again.
Anyhow I still can't modify, test or even create a new connector for access enforcer.
The only error I get is "Action failed".
I tried to analyze the logs but found no help there too.
2007-06-18 20:41:56,833 [SAPEngine_Application_Thread[impl:3]_4] ERROR java.lang.NullPointerException
java.lang.NullPointerException
at com.virsa.ae.dao.sqlj.SAPConnectorDAO.iterToDTO(SAPConnectorDAO.sqlj:75)
at com.virsa.ae.dao.sqlj.SAPConnectorDAO.findByConnectorName(SAPConnectorDAO.sqlj:15)
at com.virsa.ae.configuration.bo.ConnectorsBO.findSAPConnectorDetails(ConnectorsBO.java:76)
at com.virsa.ae.configuration.actions.ManageConnectorsAction.testConnection(ManageConnectorsAction.java:163)
at com.virsa.ae.configuration.actions.ManageConnectorsAction.execute(ManageConnectorsAction.java:66)
at com.virsa.ae.commons.utils.framework.NavigationEngine.execute(NavigationEngine.java:229)
at com.virsa.ae.commons.utils.framework.servlet.AEFrameworkServlet.service(AEFrameworkServlet.java:412)
at javax.servlet.http.HttpServlet.service(HttpServlet.java(Compiled Code))
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java(Compiled Code))
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java(Compiled Code))
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code))
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))
Did anybody here face a problem like that?
Kind regards,
Bastian
Message was edited by:
Bastian Schneider
Message was edited by:
Bastian SchneiderI had a simular problem with CC and I had to contact SAP. They gave me a script to run against the database that remove the connector. The problem seemed somewhat common for CC 5.1. Not sure if this applies to AE.
-
Problems with Personnel Cost Planning
Hi all,
i have problems with the Personnel Cost Planning specifically with the Quota planning (infotype 1019).
i save data in the infotype 1019, Quota planning, for a organizational unit and in the infotype 1005, Planned Compensation, i save data for a job (i also tried with positions), but i can't value the cost for the organizational unit.
maybe I'm missing some setting or I'm doing something wrong.
ThanksJoanne,
Are you still having issues with BI-IP? I have been troubleshooting with the basis folks in getting BI-IP up on a new system over the last few day to a week and have now gone through the process myself whereas before I had been given a system already set up. I have enclosed some troubleshooting feedback with my counterpart in getting the system up.
What type of issue are you having?
Can the basis folks start the planning modeler or planning wizard in RSPLAN even if you can't?
1. The note mentioned above 919850 and the help documentation in SPRO under
SAP NETWEAVER->Business Intelligence->BI Integrated Planning
are very helpful. They have to set the following Jco Destinations in Web Dynpro Content Administrator:
BI_MODELDATA
BI_METADATA
WD_ALV_MODELDATA_DEST
WD_ALV_METADATA_DEST
And the problem was the connection to the message server. It was not possible to connect without having a Logon group assigned. This had to be done in WI4 ABAP as well as in the SLD for this system. After that assignment connection was no problem.
2. make sure you have the portal ips in your host file.
3. have they have created an account for you in client 001 of the NW04S?
4. Have they created a portal id for you and assign the portal role com.sap.ip.bi.business_planning_showcase to you?
5. have they configured the setting for starting the planning modeler (also under SPRO)..
Hope this helps. If you have more specific questions, feel free to e-mail me directly.
Mary -
Problems with Receiver Determination
Hi everybody.
I have started as XI developer 2 weeks ago.
I'm trying to replicate de tbit40 exercises in our company system. when i try to make the 'Receiver Determination' somethings happen. It doesn't appear the part to write the system receiver.
This is my scenario : file->XI->IDOC.
I've defined in the SLD the hardware, including one PC, the XI server and the SAP 4.6c server.
This is only a test in order to check the connectivity between the PC and SAP R3. I haven't configured yet the part of the IDOC in the R3 system. Is this necesary to view the 'subwindow' of system receiver?
Thanks.Hi everybody,
I'm having some problems with the sender agreement and the receiver determination, let me explain you the scenario: i'm trying to translate inbound plain text files to XML to a outbound interface for MDM.
An XI consultant (expertise) has successfully created the inbound - outbound interface mappings for vendors catalog, it has worked good since he set it up, but now that i'm trying to create the materials mapping according to the manuals step by step, and when i try to create the receiver determination settings, i can't find my interface mappings, the pop-up window return 0 objects for interface mappings (that i have already created and linked with msg types).
So what can i do? Do you have any idea?
Regards.
Gerardo. -
Problem with starting j2ee stack
We have Netweaver 2004s ABAP+J2EE (Add-in). ABAP stack starts ok, but j2ee stack not :(.
dev_jcontrol:
[Thr 6040] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
[Thr 6040] INFO: Invalid property value [javaVMPath=C:\j2sdk1.4.2_09]
[Thr 6040] INFO: Invalid property value [javaVMVersion=1.4.2_09-b05]
[Thr 6040] INFO: Invalid property value [javaVMVendor=Java HotSpot(TM) Server VM (Sun Microsystems Inc.)]
[Thr 6040] INFO: Invalid property value [javaVMCpu=x86]
[Thr 6040] INFO: Invalid property value [javaVMLibPath=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin]
[Thr 6040] INFO: Invalid property value [javaVMExePath=C:\j2sdk1.4.2_09\bin]
[Thr 6040] *** ERROR => Main class not specified [jstartxx.c 2592]
[Thr 6040] *** ERROR => node [bootstrap] not found [jstartxx.c 1593]
[Thr 6040] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = -18)
[Thr 6040] JControlCloseProgram: started (exitcode = -18)
[Thr 6040] JControlCloseProgram: good bye... (exitcode = -18)
instance.properties
#bootstrap. : -
#bootstrap. : generated VM parameters
#bootstrap. : Thu Apr 20 14:36:35 2006
#bootstrap. : -
bootstrap.javaVMPath=C:\j2sdk1.4.2_09
bootstrap.javaVMVersion=1.4.2_09-b05
bootstrap.javaVMVendor=Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
bootstrap.javaVMType=server
bootstrap.javaVMCpu=x86
bootstrap.javaVMLibPath=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin
bootstrap.javaVMExePath=C:\j2sdk1.4.2_09\bin
And I can't understand what can be problem with java props. Any suggestion?
Thanks in advance,
Aliaksandr KucharThank you Vladimir for your replies, it's very helpful.
Actually we managed to restore properties file on our files system. And now sap mmc shows that j2ee server starts well. But we cann't connect it by http neither deafult page of server nor any other (portal f.e.), but can connect Visual Admin.
std_server0.out
SAP J2EE Engine Version 7.00 PatchLevel is starting...
Loading: LogManager ... 1782 ms.
Loading: PoolManager ... 15 ms.
Loading: ApplicationThreadManager ... 141 ms.
Loading: ThreadManager ... 31 ms.
Loading: IpVerificationManager ... 47 ms.
Loading: ClassLoaderManager ... 31 ms.
Loading: ClusterManager ... 453 ms.
Loading: LockingManager ... 110 ms.
Loading: ConfigurationManager ... 8281 ms.
Loading: LicensingManager ... 47 ms.
Loading: CacheManager ... 125 ms.
Loading: ServiceManager ...
Loading services.:
Service DQE started. (0 ms).
Service runtimeinfo started. (32 ms).
Service memory started. (188 ms).
Service cross started. (172 ms).
Service file started. (250 ms).
Service timeout started. (219 ms).
Service cafeuodi~mnuacc started. (0 ms).
Service trex.service started. (31 ms).
Service p4 started. (969 ms).
Service classpath_resolver started. (78 ms).
Service cafeucc~api started. (2922 ms).
Service jmx_notification started. (93 ms).
Service userstore started. (47 ms).
Service log_configurator started. (8000 ms).
Service locking started. (15 ms).
Service naming started. (1187 ms).
Service failover started. (78 ms).
Service appclient started. (140 ms).
Service javamail started. (641 ms).
Service ts started. (609 ms).
Service http started. (1469 ms).
Service licensing started. (31 ms).
Service jmsconnector started. (562 ms).
Service connector started. (546 ms).
Service iiop started. (656 ms).
Service webservices started. (3625 ms).
Service deploy started. (15578 ms).
Service configuration started. (47 ms).
Service MobileSetupGeneration started. (47 ms).
Service MigrationService started. (79 ms).
Service MobileArchiveContainer started. (63 ms).
Service bimmrdeployer started. (0 ms).
Service dbpool started. (2266 ms).
Service cafeugpmailcf started. (62 ms).
Service com.sap.security.core.ume.service started. (2578 ms).
Service security started. (1296 ms).
Service classload started. (156 ms).
Service applocking started. (344 ms).
Service shell started. (328 ms).
Service tceCATTPingservice started. (78 ms).
Service telnet started. (78 ms).
Service webdynpro started. (859 ms).
Service cafummetadata~imp started. (937 ms).
Service ejb started. (2219 ms).
Service servlet_jsp started. (2937 ms).
Service dsr started. (1500 ms).
Service developmentserver started. (2687 ms).
Service keystore started. (3593 ms).
Service ssl started. (78 ms).
Service tcsecsecurestorage~service started. (562 ms).
Service cafumrelgroups~imp started. (3297 ms).
Service tcsecwssec~service started. (235 ms).
Service tcsecdestinations~service started. (703 ms).
Service pmi started. (500 ms).
Service sld started. (2875 ms).
Service cafruntimeconnectivity~impl started. (28656 ms).
Service cafeugp~model started. (375 ms).
Service tcsecvsi~service started. (1797 ms).
Service tceujwfuiwizsvc started. (16 ms).
service tcdisdic~srv ================= ERROR =================
Service jmx started. (6110 ms).
Service cafeuer~service started. (1781 ms).
Service tc.CBS.Service started. (9578 ms).
Service prtbridge started. (5954 ms).
Service CUL started. (5703 ms).
Service com.adobe~DataManagerService started. (6047 ms).
Jun 7, 2007 3:08:03 PM ...utilxi.prop.api.PropertySourceFactory [SAPEngine_System_Thread[impl:5]_43] Fatal: XI properties could not be initialized. Check ExchangeProfile (or aii.properties).
Thrown:
java.lang.Throwable: dummy Throwable for stack trace
at com.sap.aii.utilxi.prop.api.PropertySourceFactory.getPropertySource(PropertySourceFactory.java:55)
at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:548)
at com.sap.aii.utilxi.misc.api.AIIProperties.<init>(AIIProperties.java:319)
at com.sap.aii.utilxi.misc.api.AIIProperties.getInstance(AIIProperties.java:346)
at com.sap.aii.af.service.sld.SLDAccess.syncExchangeProfile(SLDAccess.java:43)
at com.sap.aii.af.service.cpa.impl.util.SLDReader.run(SLDReader.java:89)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Service apptracing started. (3125 ms).
Service basicadmin started. (7422 ms).
Service com.adobe~LicenseService started. (531 ms).
Service com.adobe~DocumentServicesConfiguration started. (859 ms).
Service adminadapter started. (3531 ms).
Service com.sap.portal.pcd.gl started. (156 ms).
Service com.adobe~DocumentServicesBinaries2 started. (4156 ms).
Service com.adobe~DocumentServicesDestProtoService started. (4250 ms).
Service com.adobe~DocumentServicesLicenseSupportService started. (3391 ms).
Service com.adobe~TrustManagerService started. (2906 ms).
Service jms_provider started. (14734 ms).
Service monitor started. (6047 ms).
Service com.sap.portal.prt.sapj2ee started. (93 ms).
Service com.sap.aii.af.cpa.svc started. (18157 ms).
Service com.sap.aii.af.svc started. (1640 ms).
Service com.sap.aii.af.security.service started. (515 ms).
Service com.sap.aii.af.ms.svc started. (672 ms).
Service com.sap.aii.adapter.marketplace.svc started. (437 ms).
Service com.sap.aii.adapter.jms.svc started. (765 ms).
Service com.sap.aii.adapter.xi.svc started. (734 ms).
Service com.sap.aii.adapter.bc.svc started. (1016 ms).
Service com.sap.aii.adapter.mail.svc started. (610 ms).
Service com.sap.aii.adapter.jdbc.svc started. (640 ms).
Service com.sap.aii.adapter.rfc.svc started. (1063 ms).
Service com.sap.aii.adapter.file.svc started. (766 ms).
Service com.sap.aii.af.ispeak.svc started. (437 ms).
Service com.adobe~FontManagerService started. (19078 ms).
Service com.adobe~PDFManipulation started. (18281 ms).
Service com.adobe~XMLFormService started. (4468 ms).
Service tc.monitoring.logviewer started. (32672 ms).
Service rfcengine started. (43672 ms).
ServiceManager started for 81656 ms.
Framework started for 93172 ms.
SAP J2EE Engine Version 7.00 PatchLevel is running!
PatchLevel October 23, 2006 07:41 GMT
Could it be forced by absence of aii.property or by service tcdisdic~srv ================= ERROR =================? How could I indicate problem in more exact way?
Maybe you are looking for
-
How to unassign handling unit in outbound delivery?
(Don't Want to delete HU onlu unassign it from delivery: WM requirement) I would like to unassign HU in an outbound delivery. code i'm using make the handling unit disappear in the overview of HU. but corresponding line in the "item overview" are sti
-
How to add a button in the child node of the Tree Table?
Hi All, I am having a requirement to create a tree table and it should have a delete button to each child node (screenshot attached). Can anyone provide me a sample for how to implement this. Thanks in Advance Aravindh
-
I am sorry if thie is republished-My first time doing this and I am not sure what goes where and where to hear feedback. Have published iweb site for five years with no problems and just opened a new site and get - 404: Page not found This error is
-
How to view thumbnails in Windows XP ??
How do I view a page of ,psd thumbnails in Windows XP Pro ?? I'm using PSE 7.
-
I am able to see facebook on the share options if there are few pictures (on photos on Mac with Yosemite latest edition). Previously on iphoto you could just click on the album and upload/share to facebook and it would. now I have to do it in group