Transaction /TMWFLOW/MAINTINST doesn't work
Hi experts,
I'm trying to launch the /TMWFLOW/MAINTINST transaction in my SM but it isn't recognized. I receive the error: '<i>This function is not possible</i>' .
The reference for the transaction is here:
http://help.sap.com/saphelp_sm40/helpdata/en/45/51fbdbd4941803e10000000a1553f7/frameset.htm
Does anybody knows why that happens?
Regards
Gonzalo
Hi Gonzalo,
Have you tried with /n/tmwflow/maintinst ?.Which version and service pack you are using?
Please give the version,support pack information.
Regards,
Avinash.
Similar Messages
-
Call transaction in Workflow doesn't work
Hi all,
I'm a strange problem.
I built a call transaction in a FM. If I test the FM the call transaction works fine.
if I put this FM in a workflow (in a class I build ad hoc for the WF) it doesn't work,
I check in degub the import partameters and it is ok.
I try to execute the FM also in UPDATE or in BACKGROUND task, or the call transaction in different MODE or UPDATE ways, but nothing.
any idea?
thanks
enzoHi,
Whether your BDC code in your function module is requesting any input from user?. If yes, make sure to pass values since you are calling through Workflow which dont popup BDC screens?.
Let me know your scenario is different than I told here.
Regards
Krishna -
PPCI transaction doesn't work perfectly....WHY??
Hi experts!!!
I'm following the steps of OMINFOTYPES docuemntation that I've found in this forum, but transaction PPCI doesn't work, I've created the structure of my new infotype and the table associated to this HRI, after I execute PPCI transaction, and I only received a message, that say... "Infotype 9010 cannot be created. Please look at the following log" and then it shows me the log and I don't have created PT9010 structure, either table HRPT9010, HRP9010 created in the database, Modulpoool....etc,.
Can anybody explain me why I need to use PPCI transaction? Is this working properly?
thanlks a lot,
Regards
rebecaHello Rebeca.
I'm getting exactly the same message in PPCI (ECC 6.0)
Were you able to solve PPCI problem?
Thank you,
Irina -
Com.sap.portal.appintegrator.sap doesn't work
Hi all,
I needed to change the file 'WinGuiRenderLayer.properties'
I found the par under 3 locations:
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
d:\usr\sap\SPD\jc00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\temp
I changed the file in those locations (I removed the bak extension and restarted the server).
Also, I made sure that the pars/directory contains the jar files.
After I restarted the server the application integrator iviews doesn't work (Web Dynpro, Transaction...).
Before I did the changes, I backed up the original pars/directory.
Copying the original pars didn't help.
How can I solve this?
Portal is EP6.16
Attched exception details:
Date : 10/25/2007
Time : 13:56:51:765
Message : [PortalNode.fireEventOnNode.toEventListener] event=onNodeReadyEvent, target=com.company.Orders, operation failed
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
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: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: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.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
not registered!
Resources:
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 45 more
Severity : Warning
Category : /System/Server
Location : com.sap.portal.portal
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_27
Datasource : 6397450:D:\usr\sap\SPD\JC00\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 000E7F3049DE005C0000002100001C4000043D4FEE02FB46
Source Name : com.sap.portal.portal
Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
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: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: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.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
not registered!
Resources:
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 45 more
Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in init method
Component : com.sap.portal.appintegrator.sap.WebDynpro
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)
at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)
at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)
at com.sapportals.portal.navigation.workAreaiView.doOnNodeReady(workAreaiView.java:238)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.navigation.workAreaiView.handleEvent(workAreaiView.java:356)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:178)
at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:391)
at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:234)
at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:576)
at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:725)
at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:685)
at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:545)
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: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: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.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent of Portal Component com.sap.portal.appintegrator.sap.WebDynpro because: Linkage error while loading implementation class
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)
at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)
at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)
at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)
... 41 more
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/appintegrator/AbstractIntegratorComponent
Loader Info -
ClassLoader name: [com.sapportals.portal.prt.util.ApplicationClassLoader@72f155]
Parent loader name: [sap.com/com.sap.portal.appintegrator.sap]
References:
not registered!
Resources:
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\classes
D:\usr\sap\SPD\JC00\j2ee\cluster\server0\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\private\lib\com.sap.portal.appintegrator.sap_core.jar
The error occurred while trying to load "com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:389)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:219)
at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)
... 45 more
Dsr Component : <Server Name>
Dsr Transaction : 5a4c6ec082f111dccf17000e7f3049de
Dsr User : <User>
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 44
Source : com.sap.portal.portal
ThreadObject : SAPEngine_Application_Thread[impl:3]_27
Transaction :
User : <User>
Thanks,
OmriSolved it.
This is what I did:
1) Took par from my production environment (same SP level)
2) Clear the par (by using 'Archive Remover')
3) Clear the pcd cache
4) Upload the par (redploy)\
5) Restart the portal
Thanks,
Omri -
Wired connection doesn't work if cable is not plugged in at boot time
Hey all,
I started using arch a few days ago and I simply love it, but I have a problem. The wired connection doesn't work if the cable is not plugged in at boot time, or if it was plugged in at boot time, then plugged out and in again. Switching it off and on again via the gui has the same effect. I am using NetworkManager with dhcpcd, NetworkManager is started via systemd, dhcpcd is not, I let NetworkManager do that. When I started investigating this problem there were some remnants of netctl, but now NetworkManager is the only networking-related service started at boot time. When the cable is plugged back in, NM-applet shows that it's connected, and an IP address is assigned, but the connection doesn't work.
Here's some information regarding the system:
It's a lenovo G50-70 laptop, it uses the r8169 driver for ethernet. (I dualboot it with windows 8.1, but arch is default and all this stuff happens also if i only use arch)
The router is a Linksys EA2700/N600
journalctl -u NetworkManager
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> NetworkManager (version 0.9.10.1) is starting...
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> Read config: /etc/NetworkManager/NetworkManager.conf
aug 26 19:14:33 arch_daboka NetworkManager[527]: <info> WEXT support is enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> Loaded plugin keyfile: (c) 2007 - 2013 Red Hat, Inc. To report bugs please use the NetworkMan
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/Bokros
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/1. vezetékes kapcsolat
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> new connection /etc/NetworkManager/system-connections/UPC1838142
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> monitoring kernel firmware directory '/usr/lib/firmware'.
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0/iee
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC20
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WiFi hardware radio set enabled
aug 26 19:14:35 arch_daboka NetworkManager[527]: <info> WWAN hardware radio set enabled
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wifi.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-wwan.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-adsl.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Loaded device plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiFi enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WWAN enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> WiMAX enabled by radio killswitch; enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> Networking is enabled by state file
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): link connected
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): carrier is ON
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): new Generic device (driver: 'unknown' ifindex: 1)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (lo): exported as /org/freedesktop/NetworkManager/Devices/0
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): carrier is OFF
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): new Ethernet device (driver: 'r8169' ifindex: 2)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): exported as /org/freedesktop/NetworkManager/Devices/1
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka systemd[1]: Started Network Manager.
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (enp1s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): using nl80211 for WiFi device control
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): driver supports Access Point (AP) mode
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): exported as /org/freedesktop/NetworkManager/Devices/2
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> (wlp2s0): preparing device
aug 26 19:14:36 arch_daboka NetworkManager[527]: <info> use BlueZ version 5
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> wpa_supplicant started
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: starting -> ready
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: ready -> disconnected
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0) supports 4 scan SSIDs
aug 26 19:14:37 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: disconnected -> inactive
aug 26 19:14:42 arch_daboka NetworkManager[527]: <info> startup complete
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Auto-activating connection 'Bokros'.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) starting connection 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTING
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless): connection 'Bokros' has security, and secrets exist. No new sec
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'ssid' value 'Bokros'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'scan_ssid' value '1'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: added 'psk' value '<omitted>'
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> Config: set interface ap_scan to 1
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: inactive -> authenticating
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: authenticating -> associated
aug 26 19:15:00 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: associated -> 4-way handshake
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): supplicant interface state: 4-way handshake -> completed
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireles
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 3599
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:01 arch_daboka dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: version 6.4.3 starting
aug 26 19:15:01 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:01 arch_daboka dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: IAID 65:59:c9:b5
aug 26 19:15:01 arch_daboka dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:01 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: soliciting an IPv6 router
aug 26 19:15:02 arch_daboka dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:02 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: rebinding lease of 192.168.1.137
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: leased 192.168.1.137 for 86400 seconds
aug 26 19:15:07 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: adding route to 192.168.1.0/24
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> address 192.168.1.137
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> (wlp2s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Policy set 'Bokros' (wlp2s0) as default for IPv4 routing and DNS.
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:07 arch_daboka NetworkManager[527]: <info> Activation (wlp2s0) successful, device activated.
aug 26 19:15:14 arch_daboka dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:14 arch_daboka NetworkManager[527]: dhcpcd[3599]: wlp2s0: no IPv6 Routers available
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): link connected
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 4
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Auto-activating connection '1. vezetékes kapcsolat'.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) starting connection '1. vezetékes kapcsolat'
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) scheduled...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 1 of 5 (Device Prepare) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) starting...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: prepare -> config (reason 'none') [40 50 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) successful.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) scheduled.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 2 of 5 (Device Configure) complete.
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) started...
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: config -> ip-config (reason 'none') [50 70 0]
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> dhcpcd started with pid 4322
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 3 of 5 (IP Configure Start) complete.
aug 26 19:15:34 arch_daboka dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: version 6.4.3 starting
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: DUID 00:01:00:01:1b:7c:0d:d6:28:d2:44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: IAID 44:7f:89:66
aug 26 19:15:34 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed nbi -> preinit
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: soliciting an IPv6 router
aug 26 19:15:34 arch_daboka dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:34 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: rebinding lease of 192.168.1.138
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: leased 192.168.1.138 for 86400 seconds
aug 26 19:15:39 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: adding route to 192.168.1.0/24
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): DHCPv4 state changed preinit -> reboot
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> address 192.168.1.138
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> plen 24 (255.255.255.0)
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> gateway 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> server identifier 192.168.1.1
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> lease time 86400
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> hostname 'arch_daboka'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> nameserver '192.168.1.1'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> domain name 'chello.hu'
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) started...
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) Stage 5 of 5 (IPv4 Commit) complete.
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_GLOBAL
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Policy set '1. vezetékes kapcsolat' (enp1s0) as default for IPv4 routing and DNS.
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Writing DNS information to /usr/bin/resolvconf
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> Activation (enp1s0) successful, device activated.
aug 26 19:15:47 arch_daboka dhcpcd[4322]: enp1s0: no IPv6 Routers available
aug 26 19:15:47 arch_daboka NetworkManager[527]: dhcpcd[4322]: enp1s0: no IPv6 Routers available
ping -c 10 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.38 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=2.79 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.89 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=5.30 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=1.59 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1.61 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=4.37 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=2.40 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=6.47 ms
--- 192.168.1.1 ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 9014ms
rtt min/avg/max/mdev = 1.599/3.759/6.471/1.627 ms
ping -c 100 8.8.8.8 - it's not completely disconnected, but it's always 8 packets at once that are received
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=20 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=21 ttl=46 time=40.0 ms
64 bytes from 8.8.8.8: icmp_seq=22 ttl=46 time=38.8 ms
64 bytes from 8.8.8.8: icmp_seq=23 ttl=46 time=39.3 ms
64 bytes from 8.8.8.8: icmp_seq=24 ttl=46 time=41.8 ms
64 bytes from 8.8.8.8: icmp_seq=25 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=26 ttl=46 time=38.4 ms
64 bytes from 8.8.8.8: icmp_seq=27 ttl=46 time=38.0 ms
64 bytes from 8.8.8.8: icmp_seq=56 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=57 ttl=46 time=49.8 ms
64 bytes from 8.8.8.8: icmp_seq=58 ttl=46 time=40.2 ms
64 bytes from 8.8.8.8: icmp_seq=59 ttl=46 time=44.3 ms
64 bytes from 8.8.8.8: icmp_seq=60 ttl=46 time=38.5 ms
64 bytes from 8.8.8.8: icmp_seq=61 ttl=46 time=43.4 ms
64 bytes from 8.8.8.8: icmp_seq=62 ttl=46 time=39.2 ms
64 bytes from 8.8.8.8: icmp_seq=63 ttl=46 time=40.5 ms
64 bytes from 8.8.8.8: icmp_seq=92 ttl=46 time=38.3 ms
64 bytes from 8.8.8.8: icmp_seq=93 ttl=46 time=43.7 ms
64 bytes from 8.8.8.8: icmp_seq=94 ttl=46 time=42.3 ms
64 bytes from 8.8.8.8: icmp_seq=95 ttl=46 time=46.6 ms
64 bytes from 8.8.8.8: icmp_seq=96 ttl=46 time=44.9 ms
64 bytes from 8.8.8.8: icmp_seq=97 ttl=46 time=42.9 ms
64 bytes from 8.8.8.8: icmp_seq=98 ttl=46 time=41.7 ms
64 bytes from 8.8.8.8: icmp_seq=99 ttl=46 time=37.8 ms
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 24 received, 76% packet loss, time 99062ms
rtt min/avg/max/mdev = 37.886/41.455/49.829/3.000 ms
cat /etc/dhcpcd.conf - I tried clientid instead of duid and disabling IPv6, but neither of those helped.
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.
# Inform the DHCP server of our hostname for DDNS.
hostname
# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
duid
# Persist interface configuration when dhcpcd exits.
persistent
# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU.
# Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu
# A ServerID is required by RFC2131.
require dhcp_server_identifier
# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
#noipv4ll
#Disable IPv6
#noipv6rs
#noipv6
cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=keyfile
dhcp=dhcpcd
## Set static hostname
#[keyfile]
#hostname=foobar
## HTTP-based connectivity check
#[connectivity]
#uri=http://nmcheck.gnome.org/check_network_status.txt
I couldn't find anything else to append, but if there are other log or conf files or anything else, which would help solving the problem, I should put here, please tell me.Try to use dhclient perhaps? Might I also suggest letting systemd deal with the dhcp issue and not NM. That may seem incongruous but it is possible NM is mis-handling the dhcp hand-off to the network card. I'm no guru but I got thinking about this when I saw this in your output:
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
aug 26 19:15:39 arch_daboka NetworkManager[527]: <info> (enp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
aug 26 19:15:40 arch_daboka NetworkManager[527]: <info> NetworkManager state is now CONNECTED_LOCAL
It is very possible that I'm mis-interpreting this information so please take it with a boulder of salt. -
Delta Download from ISU BP to CRM BP doesn't work
Hi Experts,
We are currently new implementing a CRM7.0 system which is connected to an existing ISU system. We now have an issue about the BP delta download from ISU -> CRM.
Replication Scenario:
ISU BP -> CRM BP, NOT SD Customer -> CRM BP. As ISU is the leading system to create BPs and in ISU a MKK BP will be created first then a SD customer will be generated based on a template. So the change of a BP is via BP transaction for MKK role, not via XD02 SD Customer.
Issue:
The middleware setting is done and initial download from ISU BP -> CRM BP is done and successful. However when I trying to change a BP (change a MKK BP via BP transaction) in ISU, the change is not replicated to CRM (no queues, no BDOCs). It seems the delta download is not triggered at all.
However, I have maintained all the settings based on the ISU Specifics on the Set-Up-and-Load Guide for BP. So the followings are maintained:
- ISU: COM_BUPA_CALL_FU maintained based on the Guide
- CRM: CRMC_BUT_CALL_FU maintained based on the note 757955
- CRM: V_SMOFEVOB maintained based on the Guide
- ISU: BTE table (T-code: BF31) maintained based on the Guide
After setting above, the initial load is working (necessary table like CRMCONSUM, CRMRFCPAR etc. are maintained otherwise the initial download won't successful). However, the delta download from ISU BP (MKK) to CRM BP doesn't work.
The only uncertain thing for me is the setting for ISU : CRMC_BUT_CALL_FU. In the Guide only one sentence saying CRMC_BUT_CALL_FU needs to be maintained both in CRM and ISU and details refer to note 757955. However, the note 757955 only talks about FMs for CRM not for ISU/ECC. So in ISU/ECC the table CRMC_BUT_CALL_FU I activated for the following entries:
BPOUT BUPA 0100000 COM_BUPA_MWX_CREATE_MAIN
X
BPOUT BUPA 1000000 BUPA_OUTBOUND_MAIN
X
BPOUT BUPA 2000000 BUPA_CREATE_CHANGE_POINTER
X
BPOUT BUPA 3000000 BUPA_OUTBOUND_ALE_MAIN
X
BPOUT BUPX 1000000 MDS_BUPA_OUTBOUND
X
CLEAR BUPA 0100000 COM_BUPA_MWX_CLEAR_FLAGS
X
CLEAR BUPA 1000000 BUPA_OUTBOUND_CLEAR_FLAGS
X
CRMIN BUPA 1000000 BUPA_INBOUND_MAIN_CENTRAL
X
CRMIN BUPA 2000000 ABA_FSBP_INBOUND_MAIN
X
CRMOU BUPA 1000000 BUPA_OUTBOUND_BPS_FILL_CENTRAL X
CRMOU BUPA 1000010 ABA_FSBP_OUTBOUND_BPS_FILL
X
CRMOU BUPA 2000000 ABA_FSBP_OUTBOUND_BPS_FILL
X
MERGE BUPA 1000000 MERGE_BUPA_CENTRAL
X
MERGE BUPA 2000000 MERGE_BUPA_FINSERV
X
MERGE BUPR 1000000 MERGE_BUPR_CENTRAL
X
PXYIN BUPA 1000000 BUPA_INBOUND
X
XIIN BUPA 1000000 ABA_BUPA_MAP_PROXY_TO_DDIC
X
XIIN BUPA 2000000 ABA_FSBP_MAP_PROXY_TO_DDIC
X
XIIN BUPA 2100000 ABA_FSBP_MAP_PROXY_TO_DDIC_1 X
XIIN BUPA 3000000 ABA_FSBP_MAP_PROXY_TO_DDIC_1 X
XIIN BUPR 1000000 ABA_BUPR_MAP_PROXY_TO_DDIC
X
XIOUT BUPA 1000000 ABA_BUPA_MAP_DDIC_TO_PROXY
X
XIOUT BUPA 9000000 ABA_FSBP_MAP_DDIC_TO_PROXY
X
XIOUT BUPA 9000010 ABA_FSBP_MAP_DDIC_TO_PROXY_1 X
XIOUT BUPR 1000000 ABA_BUPR_MAP_DDIC_TO_PROXY
X
Not sure if the above setting is correct or not (some of the setting may not necessary, is that will impact the delta download from ISU to CRM)
Also what's the purpose of maintain two tables in ISU/ECC (COM_BUPA_CALL_FU and CRMC_BUT_CALL_FU)?
Also I have read some notes that the ISU BP -> CRM BP delta download is not triggered by above tables, it is triggered by BADI PARTNET_UPDATE, is this true, a bit confused.
I am looking forward a solution from you experts.
Thanks,
LaurenceAny inputs experts?
-
RFC Sender (XI 3.0, SP14) Load Balancing doesn't work
Hi all,
We're "desperately" trying to use the Load Balancing option of RFC Sender Adapter (XI 3.0, SP14). It doesn't work.
The Adapter can not register to the sender SAP server. But when we do not use the "Load Balancing" option, everything works well.
We did follow the XI guidelines step-by-step. All necessary configurations in XI and in SAP sender system (TA: SM59) are "properly" done and reviewed by different experts several times.
Do you have, by chance any running scenario using "Load Balancing" within a RFC Adapter? If yes, I would appreciate if you can share it with me.
Thanks a lot!
Regards,
KhaledHello Khaled,
the RFC sender adapter registers a program at the SAP Gateway. Load Balancing for the Sender Adapter means, that you have at least two J2EE server nodes within your XI installation. On all these server nodes the same RFC sender adapter is started and register the same program at the same gateway. The load balancing is then handled by the gateway. That means, that for the sender adapter the settings are the same, even if you use load balancing or not.
The settings are, e.g.
- SID=ABC
- hostname=abchost (central instance, message server)
- hostname=xyzhost (additional dialog instance of ABC)
- instance nr=00
application server (gateway): xi1host
application server service (gw-service): sapgw00
programm id: could be freely choosen
The Metadata Repository could be connected using load balancing. Here a user need to log on to the system.
The settings here must be:
Message-Server: abchost
Message-Server-Service: sapmsABC
System-ID: ABC
Logon-Group: e.g. PUBLIC; this logon group need to be created in system ABC using transaction SMLG
For the RFC-Receiver Adapter the same settings as for the Metadata could be used.
Keep in mind, that for the RFC Sender Adapter a RFC connection of type T must be created in transaction SM59 in system ABC.
Rgds.,
Andreas -
Leave to list-processing doesn't work
Hi 2 all!
I have a problem with LEAVE TO LIST-PROCESSING. I have developed a module pool (type M) and screen with the screen painter of type Normal. Now I want to go to the report from my screen with LEAVE TO LIST-PROCESSING, but it doesn't work. I am trying to do this when the button is pressed ( at my application status). The operation is performed but then the Init_screen_xxxx module is called again. Highly appreciate your help.Hi Nata
Yes U can do it.
We go from module pool program to report program and vice-versa.
1. From report to screen (transaction)
Call transaction
Leave to list-processing and return to screen
2. From screen to list (report)
we can write a report program for fuction key available in the screen.
for example.
case sy-ucomm.
when 'fctcode'.
select .......... from tabl into ..
write:/.........,
endcase.
reward if useful. -
Live Auction has been installed, but doesn't work
Hi experts!
I've got a lot of errors - LAC doesn't work - Need your help!
1: (SmokeTest):
Make sure the Live Auction initiator's applet JAR file has been properly deployed. This file should be located at H:\usr\sap\SRN\DVEBMGS02\j2ee\cluster\server0\apps\sap.com\com.sap.srm.la\servlet_jsp\srm\root\srm\nullsrmlaInitiator5.10.0.jar.
If you are accessing this page outside of the firewall and via a web dispatcher or reverse proxy, then make sure you can download the JAR file using the "Download" button below. Alternatively, you can try accessing this page inside the firewall to verify that the JAR file is deployed properly.
URL=http://serverzzz.zzz.zz:8002/srm/nullsrmlaInitiator5.10.0.jar
2: Process Bid Invitation -> Action -> Bid Comparison
Error when processing your request
What has happened?
The URL http://serverzzz.zzz.zz:8002/sap/bc/gui/sap/its/BBP_BID_EVAL/! was not called due to an error.
Note
The following error text was processed in the system SRM : Screen output area too small
The error occurred on the application server serverzzz_SRM_zz and in the work process 0 .
The termination type was: ABORT_MESSAGE_STATE
The ABAP call stack was:
SYSTEM-EXIT of program SAPLBBP_BID_EVAL
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SRN in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server serverzzz_SRM_zz in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server serverzzz_SRM_zz . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 100 -u: PURMANAGER -l: E -s: SRN -i: serverzzz.zzz.zz -w: 0 -d: 20081031 -t: 091757 -v: ABORT_MESSAGE_STATE -e: Screen output area too small
HTTP 500 - Internal Server Error
3: Process Auction -> Display Company Bid -> Live Auction
Service cannot be reached
What has happened?
URL http://serverzzz.zzz.zz:8002/sap/bc/gui/sap/its/_accessibility=0 call was terminated because the corresponding service is not available.
Note
The termination occurred in system SRM with error code 404 and for the reason Not found.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:R-i:serverzzz_SRM_zz-v:0-s:404-r:Notfound
HTTP 404 - Not found
So, first of all as far I understand path to JAR files is misconfigured. Where and how can I fix it?
Any help will be appreciated!
Edited by: Maxim Pak on Oct 31, 2008 4:44 AMI cannot explain it other than to tell you the current recommendations are to keep java turned off and there are no other posts like yours that claim they need it on (at least that I have seen). Also I have it off on my system and flash plays with no problems in all the sites I go to (modulo some buffering problems sometimes with certain hi-res videos on only youtube).
Did you install the latests flash player downloaded directly from the adobe site?
Maybe you have a flash storage or cookie problem. Those can be cleared and deleted with the Flash Player system preferences.
It's your decision on whether you want to take your chances with Java on rather than find the root of the problem. If you do that then at a minimum make sure you have latest apple java updates, I recommend you install and learn about Little Snitch, and use OpenDNS DNS servers (208.67.222.222, 208.67.220.220). -
Hi All
Rif t.code S_ALR_87012177. This report requires, for working, the flag in th filed "Payment history record" in the tab "payment transactions" of customers master data.
I've adjourned the master data of the customers putting in the field "Payment history record". But the report doesn't work for histories. Is there a program which make the report working for histories too?
Thanks
GandalfHi Pankaj,
We canu2019t see document currency in this report; better u can see document currency in T. Code u2013 FBL5N.
Thanks -
Hi All
Rif t.code S_ALR_87012177. This report requires, for working, the flag in th filed "Payment history record" in the tab "payment transactions" of customers master data.
I've adjourned the master data of the customers putting in the field "Payment history record". But the report doesn't work for histories. Is there a program which make the report working for histories too?
Thanks
Gandalf
Edited by: Umberto Gandalf on Mar 23, 2009 12:02 PMHi Suresh,
I have one issue with same report
when i seen the report there are two arrears days are showing to corresponding to the months Feb
as per the Report S_ALR_87012177 help following below
Arrears in days
The average days in arrears are determined as follows: Every
incoming payment in the periods concerned is multiplied by its days
in arrears. These amounts are added together and then divided by the
total amount from all the incoming payments. This process ensures
that the days in arrears are weighted by the payment amount
but for February month there are 9 payments on one customer and when checked in FBL5N report
there are no Arrears days on each payment document but in the report "customer history ' there showing 2 days as arrears under " payments with Cash discount .Arrears"
User has doubt how this report is working to show the Arrears days
Are there any Formula , can you please advise me
if you knows well about this
Regards
Ranamka -
Function adobeDPS.libraryServices.folioMap.sort doesn't work
Hi, I'm working with custom storefront and until yesterday the function folioMap.sort works fin, I get all folios published with this function, but today it doesn't work, I get always a empty array and my library looks like this:
And if i debugger it I found that my folios is always an empty array:
What am I doing wrong?Hi Neil, Thank you four your answer.
Yes, I'm updating library. This is my code:
adobeDPS.initializationComplete.add(function(){
Store.init();
Store.init = function(){
var transaction = adobeDPS.libraryService.updateLibrary();
transaction.completedSignal.addOnce(Store.updateLibraryHandler, this);
Store.updateLibraryHandler = function(transaction){
Store.folios = [];
// Sort the folios descending.
var list = adobeDPS.libraryService.folioMap.sort(function (a, b) {
if (a.publicationDate < b.publicationDate)
return 1;
else if (a.publicationDate > b.publicationDate)
return -1;
else
return 0;
//HERE Store.folios always is empty
Thank you very much. -
Synchronization of tasks and interaction logs with Outlook doesn't work
Dear SAP Experts,
I'm workink on CRM 7.0 (release 7.7.06.010).
We are trying to make the synchronization of activities, contacts and tasks from our CRM system to Microsoft Outlook.
It's working fine for the contacts and for the Apointment BP visit (transaction type Y020).
But no synchronization made for others activities (interaction log Y007 and telephone calls PCAL) or BP Tasks (Y030) we created in the system.
We just applied today SAP Note 1415263 and Groupware Integration 3.057.
I made the settings in the CRM Calendar tab in Outlook (with synchronization from CRM to Outlook), and checked apointment, contacts and tasks.
In customizing (CRM > Transactions > Basic settings > Define transaction types), I flagged for the following transaction types the little 'Calendar' box: Y020, Y030, Y007 and PCAL.
In another entry (CRM > CRM Middleware and related components > Settings for client-based synchronization), I indicated the transaction type Y020 for DEFAULT_APPT_PROC_TYPE and Y030 for DEFAULT_TASK_PROC_TYPE.
Any idea about what is missing or not already done?
Any help will be apppreciated.
Thanks in advance for your help,
Kind regards,
Grégory KREMSER
Edited by: Grégory Kremser on Feb 3, 2010 3:13 PMWe don't have a CAS array set up. We want the fail over to be fully manual and only fail over to another server when mb1 is in a completely failed state and won't be back up and running withing a set time frame. We can get everything working
on MB3 and only Outlook doesn't work when everything is on MB2. Outlook also doesn't work if databases are on another server and DNS is pointing Outlook to MB2 (again MB3 works fine). -
Authorization Variable doesn't work in Workbook
Hi all,
I have defined authorization variable for a characteristics in Query. When I run the query, the variable's value can be derived from user's authorization. But when running in workbook, it doesn't work. The value is empty and workbook shows "No Authorization". Does anyone have the same problem?Dear Eric,
Are you sure that you have enabled the authorization object for your InfoProvider? This is something that has to be done in transaction RSSM after an authorization object as been created.
Greetings,
Stefan -
Buckup SQL Script doesn't work
Hi all,
In ECC i want schedule ASE jobs to dump transaction logs,i do it fellow the note 1588316 step by step . In schedule jobs my sql script doesn't work,but it works in sql command line.
sql script :
dump transaction DEV using config= 'DEVLOG'
Anybody can give me some advise to face this issue? Thanks in advance.
David LvHi all,
My problem sloved, it's JSagent problem.
sp_dumptrans not working at dbacockpit @Alcino Melo
use sybmgmtdb
go
sp_js_wakeup "start_js",1
go
after start JSagent my sql script can run
Thanks all
David Lv
Maybe you are looking for
-
Mixing Ram Sizes in Triple-Channel
I would like to install 10 GB of RAM in the following configuration on my 2009 Mac Pro (flashed to 5,1): Slot 1: 4GB Slot 2: 4GB Slot 3: 2GB All 3 dimms are Apple OEM Hynix brand. All are 1333MHz. Will this arrangement take advantage of the tripl
-
Mailbox and Library Size Limits and Reporting
I have seen quite a few postings on size limits. I have a system that has two Post Offices - one for mail and one for doc mgt. Users log into the e-mail PO and get redirected to the doc mgt PO when they need to access files in the libraries ( there a
-
Is iWork soon to be the same for iOS and Mac
I have a Macbook White 2009. I was looking in the MacApp Store and I noticed that iWork and Microsoft apps cost the same. I wanted to know which are better? I also noticed that iWork has different prices for a Mac and for an iPad because they don't h
-
PS won't recognize "default" printer
This is an annoyance rather than an emergency-I'm on a Mac, I have three printers, and I want to use one in particular for a PS printing task. I fill up the printer with the right paper, then call up the flle and hit "print", forgetting to notice tha
-
All App downloads stop at 42%
I have been usung CC for over a year with no issues. Then yesterday none of my apps would not update. I had to reformat my mac for other reasons but now it will not download any program. They all stop at 42%. I am on on a 64 bit mac running 10.9.2 -