Call failed, call failed

I bought an iPhone 4 from ebay. The seller said he was not quite sure about whether the phone was locked or not, but vodafone's micro-sim card is OK. I bought a vodafone pay as you go micro-sim card and insert it, but neither making or receiving a phone call nor sending or receiving a message is available. I was confused. I am recovering the filmware and I am not sure whether it will work or not. Please help me.

The problem is reproducable.
On a "Core" installation,
+with the following added:
Documentation Tools
Lint Libs (usr)
Live Upgrade Software (dependency; why?)
On-Line Manual Pages
Secure Shell
SunOS Header Files
Solaris Zones
-and the following excluded:
FTP server (root and usr)
PCMCIA support
Sendmail
Solaris Desktop /usr/dt
Xinside Xserver driver
I do get zones working on a full "end user" install -- but then I also get sh*tloads of stuff I really don't want on a server (GNOME, CDE, StarOffice, Evolution, Mozilla, X11, OpenWin, ...). Removing the spurious fluff won't work; some packages removal scripts seem to be broken, and dependency checking is, well, living hell on Solaris 10.
I would like a simple thing, which is: a very basic, bare-bones installation of a Solaris 10 server -- WITH zones.
Perhaps this is an impossible dream. Is it?

Similar Messages

My iphone 5 won't make a call when i fail to connect to the internet via 3g

My iphone 5 won't call when i fail to connect to the internet via 3g.
At work i dont have wifi i have 3g, if i launch say the sky go app,or the iplayer, sometimes they work and everything is fine...sometimes they wont load as 3g for whatever reason cant get a connection at that particular time........ if i then try and make a call the call will fail. I've experimented 25 + times and this is definately the cause.
(note: when the 3g connection does work, the phone has absolutely no problem calling people)
Anyone had this problem?
Even better has anyone got a solution?
Thanks,
Nick.

Are you sure that the carrier's signal is strong where you are having this problem? Certain building structures and locations have poor cellular signal strength and this often results in the "No Service" indication. Are other users able to get service in the same locations where you have problems?

When my iPhone 4S (with ios7) experiences a failed call while connected to my Bluetooth hands free in my car(screen locked) the failed call appears on the locked screen, as it should, then when I unlock the phone it automatically redials the failed call,

When my iPhone 4S (with ios7) experiences a failed call while connected to my Bluetooth hands free in my car(screen locked) the failed call appears on the locked screen, as it should, the problem arises whenever I unlock the phone, it automatically redials the last failed call, it doesn't do this with missed calls that are on the locked screen, if any. It is really annoying as sometimes the phone doesn't respond to attempts to end the call before it connects to the number. I then have to explain that it was my phone and not me, I look like an idiot, which I don't really need any extra help with!! Does anyone have any ideas? I don't want to stop missed call from showing in the locked screen but it might be associated with the failed calls and therefore be the only resolution

I have had the same issue which was driving me mad but think I have just found a way around it. In iOS 7 if you swipe up on the lock screen to access quick settings and go into timer then click the home button you get into the phone without calling the person back. Not a great 'fix' but hope it works for you. Come on Apple this isn't good enough, fix this bug otherwise you will lose your customers.

UPGRADE : RFC call to subst_save_upgeval_db failed with key UPDATE_ERROR

Hello.
We are upgrading our NW 7.01 to NW 7.3 ABAP.
In Postprocessing phase MAIN_POSTP/CREATE_UPGEVAL we encounter the following error:
ERROR: RFC of "subst_save_upgeval_db" failed
key: ERROR UPDATE
message: EXCEPTION UPDATE_ERROR RAISED
Here is the troubleshooting ticket:
This trouble ticket was created by SAPup on 20111125120155
SAPup broke during phase CREATE_UPGEVAL in module MAIN_POSTP / Post Processing
Error Message: RFC call to subst_save_upgeval_db failed with key UPDATE_ERROR (UPDATE_ERROR): EXCEPTION UPDATE_ERROR RAISED
Summary of SAPup:
SAPehpi Release:        lmt_002
SAPehpi Version:        SAPup release lmt_002 version 41.001
Start Release:          701
Target Release:         730
Summary of host system details:
SID:                    TA1
Host:                   sapta1
MS Host:                sapta1
GW Host:                sapta1
Start Path:             /usr/sap/TA1/DVEBMGS02/exe
Kernel Path:            /usr/sap/TA1/DVEBMGS02/exe
Summary of operating system details:
OS Type:                Linux X86_64
OS Version:             2.5
Summary of database details:
Database Type:          ora
Database Version:       11.2.0.2.0
Summary of RFC details:
Host:                   sapta1
GW Host:                sapta1
Client:                 000
Destination:            TA1
Language:
System No.:             02
here is the PHASES.LOG:
1 ETQ201 Entering upgrade-phase "CREATE_UPGEVAL" ("20111125120352")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '02', GwService = 'sapgw02'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPSR3
4 ETQ399   auth_shadow_upgrade=0
1 ETQ200 Executing actual phase 'MAIN_POSTP/CREATE_UPGEVAL'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'STORE_DB'
4 ETQ359 RFC Login to: System="TA1", Nr="02", GwHost="sapta1", GwService="sapgw02"
4 ETQ232 RFC Login succeeded
Do you have anu ideas ?

Here is the dev_rd log:
Fri Nov 25 14:07:04 2011
***LOG S23=> GwIDisconnectClient, client disconnected (020) [gwxxrd.c     10423]
***LOG S74=> GwIDisconnectClient, client disconnected ( sapta1) [gwxxrd.c     10434]
***LOG S0R=> GwIDisconnectClient, client disconnected () [gwxxrd.c     10451]
***LOG S0I=> GwIDisconnectClient, client disconnected ( SAPCPIC) [gwxxrd.c     10464]
LOCATION    SAP-Gateway on host sapta1.sap.fr.alten.com / sapgw02
ERROR       connection to partner 'localhost.localdomain:0' broken
TIME        Fri Nov 25 14:07:04 2011
RELEASE     720
COMPONENT   NI (network interface)
VERSION     40
RC          -6
MODULE      nixxi.cpp
LINE        4850
DETAIL      NiIRead: 127.0.0.1:0
SYSTEM CALL recv
COUNTER     58

RFC call to spda_get_stack_info failed.

Hi All,
When carry out the system upgrade from 47x200 to 701 EHP4 SR1,
has a error in get stack info in the preparation step.
From windows 2003 x32 MSsql 2000 upgrade to windows 2008 R2 and MS sql 2008 R2.
Error message set: 'RFC call to spda_get_stack_info failed with key
RFC_ERROR_SYSTEM_FAILURE (SYSTEM_FAILURE): Error ST_MATCH_FAIL occured.
P1=element-start P2=sp-stacks P3= P4=element-start P5=SMSDXML P6='
Thanks.

Hello,
this error is happening because you're using an old version of SAPup and/or an old version of the Upgrade FIX file. Please make sure you're running the very last version of these files and repeat the process from the beggining.
Also the file ../EPS/in/SMSDXML.xml is actually not the XML file you want to use, it is a for R/3 release with
SAP_BASIS 4.x, the EHP stack configuration for start releses 6.20 and higher, these text files do not match anymore.
This can contribute for EHP_INCLUSION phase failing. Have you renamed it? It usually is a long file name, for example: SMSDXML_EP1_20111002154601.221.xml. Please make sure you or someone have not made manual changes in this xml.
I hope this information helps.
Best regards,
Tomas Black

[Solved] Pacman errors: "call to execv failed", system not booting

Recent upgrade (yesterday) - problems went like this:
1) pacman -Syu attempted "filesystem" upgrade and threw errors about some directories in /usr/local being 775 not 755.
2) that was because I had a non-standard package in there. I changed just those relevant directories to 755.
3) reattempted pacman -Syu but got a bunch of errors: "call to execv failed"
4) system was immediately borked. Reboot now throws me into a shell.
This is a 32 bit system.
Any ideas and help would be greatly appreciated.
Last edited by lagagnon (2013-01-30 19:10:24)

Solved my problem with the following method:
1) used Arch LiveCD. Mounted boot and / partitions
2) pacman -r /path/to/root -Syyu glibc filesystem
3) reboot gave "Unable to find root device error"
4) ran LiveCD again following these instructions: https://wiki.archlinux.org/index.php/Pa … onger_boot

RFC Sender Adapter error " Call to messaging failed"

Hi,
I have been trying the RFC-> XI->File scenario.When I execute RFC using se37 transaction
on R/3 box,it gives the error " Call to messaging failed:
com.sap.aii.af.ra.ms.api.DeliveryException".
I have looked at msg in XI server using SXMB_Moni transaction.I found that,program is unable
to find the interface mapping function (Mapping between RFC and Inbound interface).
I have done the following settings:
For Sender :
1.RFC is being used as outbound Interface.
2.Imported RFC from R/3.
3. The R/3 functionality is to retrieve records.
For Receiver:
1.Defined Inbound ,Async. Interface.
2.Defined Data Type and Msg type
3.Defined Fault Message type
Mappings:
1. Message Mapping is defined for Inbound Message(From RFC) and Outbound Message
2. Source Interface(ZRFC) and target Interface(Inbound Interface) mapping is defined.In this mapping I am unbale to defined Mapping for Response and Fault.I have just deifned for Request as tabs are not gettting enabled after click of 'Read Interface'.
All necessary configurations have been done in Intergration Directory.
I am getting XML message at receiver at without data where rfc retireves two records.Why this is not being done?
As there is no mapping for Fault message of Inbound interface with RFC interface,I think mapping no found error is coming.
PS. I have not done the message mapping between ZRFC.Response and Inbound Message.
Please comment,where I have gone wrong.
Thanks & Regards,
HImanshu

Hi,
I don't know if the info below will solve your problem. Your scenario is an asynch scenario, therefore, the RFC must be executed as a qRFC. SE37 executes the RFC as synch.
To execute the RFC as asynch, you must tested with a report (se38):
The RFC must be executed as a qRFC.
data: DEST LIKE RFCDES-RFCDEST VALUE 'MY_RFC_DEST'.
CALL RFC
     IN BACKGROUND TASK
     DESTINATION DEST
     EXPORTING
COMMIT WORK.
The COMMIT WORK is required to send the RFC.
Regards,
Bill

JCA - Failed calling get method getThreadSecurity on the ManagedConnectionF

Hi All,
This is my first post with the SDN, hope I could see and extend helping hands in form of technology and solutions
My problem
=============
I am new to JCA.I am trying to deploy the helloworldra.ear provided by the IBM site.I deployed the resoource adapter and created a connectionFactory named "HelloWorld"(jndi).I get the below mentioned exception when I do
ConnectionFactory cxFactory = (ConnectionFactory) context.lookup("java:comp/env/HelloWorld");
Kindly chek into the exception and provide me with the solution.
Thanks in Advance
KABA
Exceptions Snapshot
==================
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O Populating Context
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O #################### JNDI Context Contents ####################
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.hostname.normalizer ---:-- com.ibm.ws.naming.util.DefaultHostnameNormalizer
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O java.naming.factory.initial ---:-- com.ibm.websphere.naming.WsnInitialContextFactory
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.name.syntax ---:-- jndi
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.namespace.connection ---:-- lazy
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.ws.naming.ldap.ldapinitctxfactory ---:-- com.sun.jndi.ldap.LdapCtxFactory
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.jndicache.cacheobject ---:-- populated
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.namespaceroot ---:-- defaultroot
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.ws.naming.wsn.factory.initial ---:-- com.ibm.ws.naming.util.WsnInitCtxFactory
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.jndicache.maxcachelife ---:-- 0
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.jndicache.maxentrylife ---:-- 0
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O com.ibm.websphere.naming.jndicache.cachename ---:-- providerURL
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O java.naming.provider.url ---:-- corbaloc:rir:/NameServiceServerRoot
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O java.naming.factory.url.pkgs ---:-- com.ibm.ws.runtime:com.ibm.ws.naming
[7/7/06 14:38:27:624 EDT] 5a004128 SystemOut O #################### JNDI Context Contents END ####################
[7/7/06 14:38:28:718 EDT] 5a004128 ConnectionFac E J2CA0066E: Failed calling get method getThreadSecurity on the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jca/HelloWorld with the value <null>. Exception is java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
     at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1747)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1188)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
     at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
     at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1762)
     at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1615)
     at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1525)
     at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1225)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
     at javax.naming.InitialContext.lookup(InitialContext.java:359)
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:293)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:144)
     at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:127)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
     at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
     at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:135)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1227)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
     at javax.naming.InitialContext.lookup(InitialContext.java:359)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldBean.execute(HelloWorldBean.java:81)
     at org.apache.jsp._HelloWorldResults._jspService(_HelloWorldResults.java:105)
     at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:357)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:675)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:773)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.dispatch(HelloWorldController.java:101)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.performTask(HelloWorldController.java:66)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.doPost(HelloWorldController.java:88)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
[7/7/06 14:38:28:812 EDT] 5a004128 ConnectionFac E J2CA0009E: An exception occurred while trying to instantiate the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jca/HelloWorld : java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
     at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1747)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1188)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
     at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
     at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1762)
     at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1615)
     at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1525)
     at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1225)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
     at javax.naming.InitialContext.lookup(InitialContext.java:359)
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:293)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:144)
     at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:127)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
     at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
     at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:135)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1227)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
     at javax.naming.InitialContext.lookup(InitialContext.java:359)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldBean.execute(HelloWorldBean.java:81)
     at org.apache.jsp._HelloWorldResults._jspService(_HelloWorldResults.java:105)
     at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:357)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:675)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:773)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.dispatch(HelloWorldController.java:101)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.performTask(HelloWorldController.java:66)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.doPost(HelloWorldController.java:88)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
[7/7/06 14:38:28:859 EDT] 5a004128 Helpers W NMSV0605W: A Reference object looked up from the context "localhost/nodes/localhost/servers/server1" with the name "jca/HelloWorld" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows:
Reference Factory Class Name: com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl
Reference Factory Class Location URLs: <null>
Reference Class Name: HelloWorld
Type: connectorName
Content: HelloWorld
Type: classpath
Content: C:\Program Files\IBM\WebSphere Studio\Application Developer\v5.1\runtimes\base_v5/lib/rsadapter.rar
Type: FactoryJndiName
Content: jca/HelloWorld
Address Type: dd
AddressContents: ffffffac ffffffed 0 5 73 72 0 25 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 52 65 73 6f 75 72 63 65 ...
Address Type: poolProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 27 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f ...
Address Type: configProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 23 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f ...
Address Type: mmProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c 2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a ...
Address Type: mbeanProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 1a 63 6f 6d 2e 69 62 6d 2e 65 6a 73 2e 6a 32 63 2e 4d 42 65 61 6e 50 72 6f ...
Exception data follows:
java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
     at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1747)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1188)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
     at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
     at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1762)
     at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1615)
     at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1525)
     at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1225)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
     at javax.naming.InitialContext.lookup(InitialContext.java:359)
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:293)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:144)
     at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:127)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
     at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
     at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:135)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1227)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
     at javax.naming.InitialContext.lookup(InitialContext.java:359)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldBean.execute(HelloWorldBean.java:81)
     at org.apache.jsp._HelloWorldResults._jspService(_HelloWorldResults.java:105)
     at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:357)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:675)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:773)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.dispatch(HelloWorldController.java:101)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.performTask(HelloWorldController.java:66)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.doPost(HelloWorldController.java:88)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
[7/7/06 14:38:28:953 EDT] 5a004128 Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl
Context method: lookup
Context name: localhost/nodes/localhost/servers/server1
Target name: jca/HelloWorld
Other data:
Exception stack trace: com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object. Root exception is java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
     at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionFactoryBuilderImpl.java:1747)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getObjectInstance(ConnectionFactoryBuilderImpl.java:1188)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
     at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
     at com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextImpl.java:1762)
     at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1615)
     at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1525)
     at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1225)
     at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
     at javax.naming.InitialContext.lookup(InitialContext.java:359)
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory$1.run(IndirectJndiLookupObjectFactory.java:293)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.ibm.ws.naming.util.IndirectJndiLookupObjectFactory.getObjectInstance(IndirectJndiLookupObjectFactory.java:144)
     at com.ibm.ws.util.ResRefJndiLookupObjectFactory.getObjectInstance(ResRefJndiLookupObjectFactory.java:127)
     at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:313)
     at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.java:884)
     at com.ibm.ws.naming.urlbase.UrlContextHelper.processBoundObjectForLookup(UrlContextHelper.java:135)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1227)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
     at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
     at javax.naming.InitialContext.lookup(InitialContext.java:359)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldBean.execute(HelloWorldBean.java:81)
     at org.apache.jsp._HelloWorldResults._jspService(_HelloWorldResults.java:105)
     at com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:357)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(JspServlet.java:675)
     at com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:773)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.dispatch(HelloWorldController.java:101)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.performTask(HelloWorldController.java:66)
     at com.ibm.ssya.helloworldra.servlets.HelloWorldController.doPost(HelloWorldController.java:88)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
     at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
     at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
     at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
     at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
     at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:948)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:530)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:610)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:431)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
[7/7/06 14:38:29:031 EDT] 5a004128 ConnectionFac E J2CA0066E: Failed calling get method getThreadSecurity on the ManagedConnectionFactory class com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl used by resource jca/HelloWorld with the value <null>. Exception is java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
     at com.ibm.ws.rsadapter.spi.WSManagedConnectionFactoryImpl.getThreadSecurity(WSManagedConnectionFactoryImpl.java:612)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getThreadSecurity(ConnectionFactoryBuilderImpl.java:2520)
     at com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.createMCFandPM(ConnectionF

PersianKamran wrote:
folks.. i am sending my class object on Sockets from client to Server (i am implementing Seriablizable Interface).
No your aren't.
You are sending the data in the class.
That is what serialization does. (And actually not all data can be sent either.)
When i get the object on server, i am able to print all its fields and methods... But i have one problem. I want to invoke a simple static method that just prints "hello".. The method on client that i am trying to invoke is....You probably either need stop attempting that or re-architect the solution.
It is possible to send a class (not data) to another computer and that computer runs it. That is how applets work.
But for that to work you must send the class. And deal with how the VM loads and unloads classes (not data) as well.

How to avoid redialing failed calls when unlocking an iphone

when using my iphone 4 with ios7 in my car via bluetooth, i have the issue that when a call drops for one or other reason; the iphone wants to recall that failed call when unlocking my iphone at arrival.
This is new since i upgraded my phone to ios7. with earlier versions i never had this issue.
it looks to me to a mistake in the software statemachine where missed calls are kept in a buffer, even when i redialed the person using my car kit just some minutes later.

And the worst and most stupid thing happens when that person already called you back. And while talking with them again you take your phone and try to unlock it to go to home screen (for ex to reply to a message you just received), and it starts calling a person you speak right now)). And they are asking: we are talking already, how did you just call me????

Error: Call to utl_http failed (WWS-32136)

Error: Call to utl_http failed (WWS-32136)
ORA-1: User-Defined Exception (WWC-36000)
I get this error when trying to add a second item to a subfolder in a content area. I want (nothing is ever needed in software) to have a "Links" link in a content area that is displayed in a portlet that opens a separate window of pre-defined links that users can not change or add to. Apparently, subfolders don't work. I would like to keep the Links information managed in the content area.
Also, after adding the first item to a subfolder the edit folder page is not displayed properly. Broken images are all over the page and the browser never stops loading. These are links that are displayed directly in the folder (subfolder). We are using 3.09 with 8.1.7.1.1.

I solved this problem.
There is a table called wwv_things (portal30) where u can modify the column 'inplace' to '0' where the value is '1', then all works.

Kdm call to inusertemp failed - related to vfat partition type

i received the message
kdm call to inusertemp failed (temp directories full?) check your installation
upon a fresh arch/kdm installation after trying to change permissions to the /tmp directory
# chmod -R 1777 /tmp
i noticed that one file was still 700, it was the file that contained the error message that led to the problem. the file is
/tmp/xerr-[username]-:0
this file clearly states that its unable to create home/[username]/.kde4 among other directories, permission denied.
then i check permissions on my user directory, and it was owned by user:group root:root. so somehow when the directory it received root permissions to the directory.
upon further inspection, i am realizing, since this is a vfat partition type, its related to the way vfat partitions mount i guess. Can somebody tell me what i might need to do so that when i create the next user the permissions are set correctly in the first place?
when trying to change the permissions
# chown -R [username]:users /home/[username]
results in an error
chown: changing ownership of ./home/wolfdogg/.bash_profile.: Operation Not permitted
i was looking into this post https://bbs.archlinux.org/viewtopic.php … 58#p562358 and it looks like it might be part of the solution, can anybody help me make sense out of this? do i need to mount the vfat partition differently in order for it to work properly as a home directory? Is there another partition type i can use to share it with windows 7? i wanted to set it as an ntfs partition type initially but i didnt see that as an option in either gparted, or fdisk, and couldnt figure any other way than making it a vfat.
Last edited by wolfdogg (2012-07-14 19:32:02)

I just did a new installon one of my systems. Everything up to date. My account I made during installation works perfectly. However, I'm getting this error when I create a new user account and try to login to KDE. I've started doing some searching, but so far nothing I have found has fixed it. I'm new to Arch myself so I'm doing as much reading as I can. Hopefully, an answer will present itself.

"Call to SQLExecDirect failed with %1"

Cross post from Windows Server 2008 Forums (MSFT Suggestion). Original Post:
I am trying to set up Perfmon to log directly to a SQL 2008 Server
(trying to avoid binary file + relog). The SQL server is running
locally on the same server I am trying to record perf counters from.
Note that I am NOT using SQL 2008's data collection features, and I am
trying to log non-sql related counters.
I set up a SQL 2008
Native Client System DSN with Windows Authentication, but when I try
and start my data collecter set I get an error message that "Call to
SQLExecDirect failed with %1", and the in event viewer I get "Call to
SQLExecDirect failed with .". The set is running as System, which has
rights to the database. SQL does not log any errors or a failed logon
attempt.
The ODBC DNS 'Test' button says it connected successfully, and I am
able to connect to the same database via Management Studio and ASP.Net. I don't think its a SQL problem, but its hard to say when the error message is blank.
Any help fixing this, or ruling out SQL as the problem, would be appreciated.
Joe

Trying to figure this out, I dumped a binary log and tried using relog.
I get "Error: A SQL failure occurred. Check the application event log for any errors." It does create the three tables in the SQL database, so it is connecting with a sucessful logon. Checking the app log, I see "Call to SQLExecDirect failed with Ȁ." The raw view has "02000x800000000000007433Application<ServerFQDN>Ȁ0000".
This is a Server 2008 box connecting to a local SQL 2008 server using a System DSN with the SQL 2008 Native Client provider.

My Iphone 4 keeps getting failed calls

Good morning.
I can´t get a single call to work on my iphone 4. There´s plenty of signal, but when I try to make a call, the call is terminated and the "Call failed" message is displayed.
Reading some of the forums online, I managed to make a call when I turn off my 3G network.
As soon I turn 3G back on, I can´t get a single call to work.
So, to sum up, I bought a really good looking phone that won´t work with 3G ?
And, by the way, I could use some work on my country´s website support, where it offers only the "Iphone Assistant".
Thank you.

Me too
other reports on the message board here
Help!!!

CNTService:Install, Failed call to open SCM, Error:5 : need solution

Hi,
I created the database using dbca. First time i deleted the database using dbca and again i created with help of dbca.
The database, dbconsole is working fine.
When i issue the isqlplusctl start in command prompt,the following error is displaying..
"CNTService:Install, Failed call to open SCM, Error:5, Access is denied"
and
"Failed to start the service, Error:0, The operation completed successfully"
This is the error i get when i run 'isqlplusctl start' frm command prompt:(
please give solution
thanks
feiroz.

Hi,
Using Vista Home premium edi.
thanks

CONC-SM TNS FAIL Call to PingProcess failed for IEMDPDEV

Concurrent manager internal log file showing error CONC-SM TNS FAIL Call to PingProcess failed for IEMDPDEV after application startup and showing status "System Hold or Fix Manager" in system administrator> administer. When ICM Fixed from administer Concurrent manager its start works and no error found in manager log file.
We have a RAC based environment and getting cold backup of application & database everyday after a shutdown of application and database.
This is our production environment we only face this issue in our production environment and no recent changes made or patch applied on environment.
Internal manager log file
Shutting down Internal Concurrent Manager : 13-OCT-2014 01:31:32
13-OCT-2014 01:31:32
The ICM has lost its database connection and is shutting down.
Spawning reviver process to restart the ICM when the database becomes available again.
Spawned reviver process 30597.
List of errors encountered:
_ 1 _
Routine AFPCMT encountered an ORACLE error. ORA-03114: not connected
to ORACLE
Review your error messages for the cause of the error. (=<POINTER>)
_ 2 _
Routine AFPSMG encountered an ORACLE error. ORA-03114: not connected
to ORACLE
Review your error messages for the cause of the error. (=<POINTER>)
_ 3 _
Routine FDPCRQ encountered an ORACLE error. ORA-03113: end-of-file on
communication channel
Review your error messages for the cause of the error. (=<POINTER>)
APP-FND-01388: Cannot read value for profile option FND_MGR_STRTUP_THRES_TIME in routine &ROUTINE.
List of errors encountered:
_ 1 _
Routine AFPCAL received failure code while parsing or running your
concurrent program CPMGR
Review your concurrent request log file for more detailed information.
Make sure you are passing arguments in the correct format.
The PROD_1004@PROD internal concurrent manager has terminated with status 1 - giving up.
========================================================================
Starting PROD_1004@PROD Internal Concurrent Manager -- shell process ID 8210
          logfile=/u01/oracle/inst/apps/PROD_prodapps/logs/appl/conc/log/PROD_1004.mgr
          PRINTER=noprint
           mailto=oracle
          restart=N
             diag=N
            sleep=30
             pmon=4
           quesiz=1
          Reviver is ENABLED
+---------------------------------------------------------------------------+
Application Object Library: Concurrent Processing version 11.5
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
Internal Concurrent Manager started : 13-OCT-2014 08:02:25
+---------------------------------------------------------------------------+
                   Process monitor session started : 13-OCT-2014 08:02:25
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
13-OCT-2014 08:02:26 - Node:(PRODAPPS), Service Manager:(FNDSM_PRODAPPS_PROD) currently unreachable by TNS
                     Process monitor session ended : 13-OCT-2014 08:02:26
                   Process monitor session started : 13-OCT-2014 08:04:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:04:26
                   Process monitor session started : 13-OCT-2014 08:06:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:06:26
                   Process monitor session started : 13-OCT-2014 08:08:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:08:26
                   Process monitor session started : 13-OCT-2014 08:10:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:10:26
                   Process monitor session started : 13-OCT-2014 08:12:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:12:26
                   Process monitor session started : 13-OCT-2014 08:14:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:14:26
                   Process monitor session started : 13-OCT-2014 08:16:26
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:16:27
                   Process monitor session started : 13-OCT-2014 08:18:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:18:27
                   Process monitor session started : 13-OCT-2014 08:20:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:20:27
                   Process monitor session started : 13-OCT-2014 08:22:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:22:27
                   Process monitor session started : 13-OCT-2014 08:24:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:24:27
                   Process monitor session started : 13-OCT-2014 08:26:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:26:27
                   Process monitor session started : 13-OCT-2014 08:28:27
CONC-SM TNS FAIL
Call to PingProcess failed for IEMDPDEV
                     Process monitor session ended : 13-OCT-2014 08:28:27
                   Process monitor session started : 13-OCT-2014 08:30:27
                     Process monitor session ended : 13-OCT-2014 08:30:28
                   Process monitor session started : 13-OCT-2014 08:32:28
                     Process monitor session ended : 13-OCT-2014 08:32:28
                   Process monitor session started : 13-OCT-2014 08:34:28
                     Process monitor session ended : 13-OCT-2014 08:34:28
                   Process monitor session started : 13-OCT-2014 08:36:28
                     Process monitor session ended : 13-OCT-2014 08:36:28
                   Process monitor session started : 13-OCT-2014 08:38:28
                     Process monitor session ended : 13-OCT-2014 08:38:28
                   Process monitor session started : 13-OCT-2014 08:40:28
                     Process monitor session ended : 13-OCT-2014 08:40:28
                   Process monitor session started : 13-OCT-2014 08:42:28
                     Process monitor session ended : 13-OCT-2014 08:42:28
                   Process monitor session started : 13-OCT-2014 08:44:28
                     Process monitor session ended : 13-OCT-2014 08:44:28
                   Process monitor session started : 13-OCT-2014 08:46:28
                     Process monitor session ended : 13-OCT-2014 08:46:28
                   Process monitor session started : 13-OCT-2014 08:48:28
                     Process monitor session ended : 13-OCT-2014 08:48:29
                   Process monitor session started : 13-OCT-2014 08:50:29
                     Process monitor session ended : 13-OCT-2014 08:50:29
                   Process monitor session started : 13-OCT-2014 08:52:29
                     Process monitor session ended : 13-OCT-2014 08:52:29
                   Process monitor session started : 13-OCT-2014 08:54:29
                     Process monitor session ended : 13-OCT-2014 08:54:29
                   Process monitor session started : 13-OCT-2014 08:56:29
                     Process monitor session ended : 13-OCT-2014 08:56:29
                   Process monitor session started : 13-OCT-2014 08:58:29
                     Process monitor session ended : 13-OCT-2014 08:58:29
                   Process monitor session started : 13-OCT-2014 09:00:29
                     Process monitor session ended : 13-OCT-2014 09:00:29
                   Process monitor session started : 13-OCT-2014 09:02:29
                     Process monitor session ended : 13-OCT-2014 09:02:29
                   Process monitor session started : 13-OCT-2014 09:04:29
                     Process monitor session ended : 13-OCT-2014 09:04:29
                   Process monitor session started : 13-OCT-2014 09:06:29
                     Process monitor session ended : 13-OCT-2014 09:06:30
                   Process monitor session started : 13-OCT-2014 09:08:30
                     Process monitor session ended : 13-OCT-2014 09:08:30
                   Process monitor session started : 13-OCT-2014 09:10:30
                     Process monitor session ended : 13-OCT-2014 09:10:30
                   Process monitor session started : 13-OCT-2014 09:12:30
                     Process monitor session ended : 13-OCT-2014 09:12:30
                   Process monitor session started : 13-OCT-2014 09:14:30
                     Process monitor session ended : 13-OCT-2014 09:14:30
                   Process monitor session started : 13-OCT-2014 09:16:30
                     Process monitor session ended : 13-OCT-2014 09:16:30
                   Process monitor session started : 13-OCT-2014 09:18:30
                     Process monitor session ended : 13-OCT-2014 09:18:30
                   Process monitor session started : 13-OCT-2014 09:20:30
                     Process monitor session ended : 13-OCT-2014 09:20:30
                   Process monitor session started : 13-OCT-2014 09:22:30
                     Process monitor session ended : 13-OCT-2014 09:22:30
                   Process monitor session started : 13-OCT-2014 09:24:30
                     Process monitor session ended : 13-OCT-2014 09:24:30
                   Process monitor session started : 13-OCT-2014 09:26:30
                     Process monitor session ended : 13-OCT-2014 09:26:30
                   Process monitor session started : 13-OCT-2014 09:28:30
                     Process monitor session ended : 13-OCT-2014 09:28:30
                   Process monitor session started : 13-OCT-2014 09:30:30
                     Process monitor session ended : 13-OCT-2014 09:30:31
                   Process monitor session started : 13-OCT-2014 09:32:31
                     Process monitor session ended : 13-OCT-2014 09:32:31
                   Process monitor session started : 13-OCT-2014 09:34:31
                     Process monitor session ended : 13-OCT-2014 09:34:31
                   Process monitor session started : 13-OCT-2014 09:36:31
                     Process monitor session ended : 13-OCT-2014 09:36:31
13-OCT-2014 09:38:31
Request : 1393181
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:31
Starting FNDCRM Concurrent Manager                 : 13-OCT-2014 09:38:31
                     Process monitor session ended : 13-OCT-2014 09:38:31
13-OCT-2014 09:38:31
Request : 1393182
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:31
Starting FNDCRM Concurrent Manager                 : 13-OCT-2014 09:38:31
Starting AMSDMIN Concurrent Manager                : 13-OCT-2014 09:38:31
                     Process monitor session ended : 13-OCT-2014 09:38:31
13-OCT-2014 09:38:31
Request : 1393183
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:31
Starting C_AQCT_SVC Concurrent Manager             : 13-OCT-2014 09:38:31
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393184
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:32
Starting DownloadProcessorMigrationMode Concurrent Manager : 13-OCT-2014 09:38:32
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393185
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:32
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393186
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:32
Found dead process: spid=(10691), cpid=(282513), ORA pid=(39), manager=(0/4)
Found dead process: spid=(10694), cpid=(282514), ORA pid=(40), manager=(0/4)
Starting FFTM Concurrent Manager                   : 13-OCT-2014 09:38:32
Starting FNDCRM Concurrent Manager                 : 13-OCT-2014 09:38:32
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393187
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:32
Starting FFTM Concurrent Manager                   : 13-OCT-2014 09:38:32
Starting FNDCPOPP Concurrent Manager               : 13-OCT-2014 09:38:32
                     Process monitor session ended : 13-OCT-2014 09:38:32
13-OCT-2014 09:38:32
Request : 1393188
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting FTE_TXN_MANAGER Concurrent Manager        : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393189
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting IEU_SH_CS Concurrent Manager              : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393190
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting IEU_WL_CS Concurrent Manager              : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393191
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting INVMGR Concurrent Manager                 : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393192
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting INVTMRPM Concurrent Manager               : 13-OCT-2014 09:38:33
Starting INVMGR Concurrent Manager                 : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393193
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting INVTMRPM Concurrent Manager               : 13-OCT-2014 09:38:33
Starting OAMCOLMGR Concurrent Manager              : 13-OCT-2014 09:38:33
                     Process monitor session ended : 13-OCT-2014 09:38:33
13-OCT-2014 09:38:33
Request : 1393194
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:33
Starting OAMGCS_PRODAPPS Concurrent Manager        : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393195
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting PASMGR Concurrent Manager                 : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393196
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting PODAMGR Concurrent Manager                : 13-OCT-2014 09:38:34
Starting PASMGR Concurrent Manager                 : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393197
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting RCVOLTM Concurrent Manager                : 13-OCT-2014 09:38:34
Starting PODAMGR Concurrent Manager                : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393198
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting RCVOLTM Concurrent Manager                : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
                     Process monitor session ended : 13-OCT-2014 09:38:34
13-OCT-2014 09:38:34
Request : 1393199
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:34
Starting WFALSNRSVC Concurrent Manager             : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:34
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
Starting STANDARD Concurrent Manager               : 13-OCT-2014 09:38:35
                     Process monitor session ended : 13-OCT-2014 09:38:35
13-OCT-2014 09:38:35
Request : 1393200
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:35
Starting WFMLRSVC Concurrent Manager               : 13-OCT-2014 09:38:35
                     Process monitor session ended : 13-OCT-2014 09:38:35
13-OCT-2014 09:38:35
Request : 1393201
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:35
Starting WFWSSVC Concurrent Manager                : 13-OCT-2014 09:38:35
                     Process monitor session ended : 13-OCT-2014 09:38:35
13-OCT-2014 09:38:35
Request : 1393202
Priority : 0
Program : 0/3
State    : Q
                   Process monitor session started : 13-OCT-2014 09:38:35
Starting WMSTAMGR Concurrent Manager               : 13-OCT-2014 09:38:35
                     Process monitor session ended : 13-OCT-2014 09:38:35
                   Process monitor session started : 13-OCT-2014 09:40:05
                     Process monitor session ended : 13-OCT-2014 09:40:05
                   Process monitor session started : 13-OCT-2014 09:42:05
Regards
Usman

Below is the solution provide by the SR Team its works perfectly our enviorment.
Please perform the following steps:
1. Stop all middle tier services including the concurrent managers. Make sure no FNDLIBR, FNDSM, or other dead processes are running.
    (restart application and database OS (i have done this step additionally))
2. Stop and then restart the database.
3. Connect to SQLPLUS as APPS user and run the following :
EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;
4. Reference Note.260887.1 regarding the Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES.
5.. Run AutoConfig on all tiers, firstly on the DB tier and then the APPS tiers and Web tiers to repopulate the required system tables.
6. Connect to SQLPLUS as APPS user and run the following statement :
select CONCURRENT_QUEUE_NAME
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME like 'FNDSM%';
If the above SQL does not return any value please do the following:
cd $FND_TOP/patch/115/sql
Connect to SQLPLUS as APPS user and run the following script :
SQL> @afdcm037.sql;
Reference Note 218893.1 How to Create The Service Manager 'FNDSM' on Oracle Applications
to create libraries for FNDSM and create managers for preexisting nodes.
Check again that FNDSM entries now exist:
select CONCURRENT_QUEUE_NAME
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME like 'FNDSM%';
7. Please run the Concurrent Manager Recovery feature to address any Concurrent Manager / Concurrent Processing issues within the Oracle Application Manager.
8. Start the middle tier services including your concurrent manager.
9. Retest the issue.
Regards
Usman

CALL TO SYSLIB FAILED ERROR WHILE SAP 4.7 DATABASE INSTANCE INSTALLATION

I am trying to install SAP 4.7 with Oracle 9.2.0.1 on W2k SP3. I have installed central instance successfully. While installing Database instance, almost at the end of installation, i am facing problem with error message call to system library failed. i am attaching the log. Please help
PHASE 2007-06-25 00:53:53
SAP R/3 Enterprise 4.70 for Oracle
PHASE 2007-06-25 00:53:53
SAP Web Application Server
PHASE 2007-06-25 00:53:53
Request common parameters of SAP System
PHASE 2007-06-25 00:53:54
Create operating system accounts
PHASE 2007-06-25 00:53:55
Request operating system user information
PHASE 2007-06-25 00:53:55
Request operating system user information
PHASE 2007-06-25 00:53:55
Request operating system user information
PHASE 2007-06-25 00:53:55
Request operating system user information
PHASE 2007-06-25 00:53:55
Request operating system user information
PHASE 2007-06-25 00:53:55
Request operating system user information
PHASE 2007-06-25 00:53:56
Request operating system user information
PHASE 2007-06-25 00:53:56
Request operating system user information
PHASE 2007-06-25 00:53:56
Request operating system user information
PHASE 2007-06-25 00:53:56
Request operating system user information
PHASE 2007-06-25 00:53:56
Request operating system user information
PHASE 2007-06-25 00:53:56
Request operating system user information
PHASE 2007-06-25 00:53:56
Request operating system user information
PHASE 2007-06-25 00:53:57
Request operating system user information
PHASE 2007-06-25 00:53:57
Request operating system user information
PHASE 2007-06-25 00:53:57
Request operating system user information
PHASE 2007-06-25 00:53:57
Request operating system user information
PHASE 2007-06-25 00:53:57
Request operating system user information
PHASE 2007-06-25 00:54:00
Adapt filesystem
PHASE 2007-06-25 00:54:00
Prepare check/adapt SAP instance filesystem
PHASE 2007-06-25 00:54:00
Extract archives
PHASE 2007-06-25 00:54:01
Extract SAP System kernel archives
PHASE 2007-06-25 00:54:02
Create service ports
PHASE 2007-06-25 00:54:02
Generate instance profiles
PHASE 2007-06-25 00:54:02
Versionize default profile, instance profile and start profile
INFO 2007-06-25 00:54:07
Copying file E:/SAPinst ORACLE KERNEL/keydb.xml to: E:/SAPinst ORACLE KERNEL/keydb.3.xml.
INFO 2007-06-25 00:54:07
Creating file E:\SAPinst ORACLE KERNEL\keydb.3.xml.
WARNING 2007-06-25 00:54:11
Error 1314 (A required privilege is not held by the client.
) in execution of a 'CreateProcess' function, line (276), with parameter (E:\oracle\ora92/bin/sqlplus.exe /NOLOG @ora_scr_tmp.sql).
ERROR 2007-06-25 00:54:11
MDB-06029 Caught exception while trying to start script executing application: [E:\oracle\ora92/bin/sqlplus.exe].
ERROR 2007-06-25 00:54:11
MDB-06030 A call to the system library failed. System error message: [Unknown error].
ERROR 2007-06-25 00:54:11
MUT-02011 Internal error: A call to syslib failed. System error message: Unknown error.
ERROR 2007-06-25 00:54:11
FJS-00012 Error when executing script.

What do mean with administrative priviledges? there is no administrativ priviledge on Windows. We only have a local group administrators.
in 4.7 sapinst will put erpadm and sapserviceerp to the local administrators group. There is no need to do it manually.
But this will not help in this case, because local Administrators did not have the rights
- replace process level token
- act as part of the operating system
if you don't believe me have a look at gpedit.msc Local Computer Policy - Computer Configartion - Windows Settings - Security Settings - Local Policy - User Rights Assignemt.
But as I already told you, log on and log off will fix this rights problem.
2. regarding memory: RAM is physical Memory
did I read right you are trying to install 4.7 on a 256 MB box?
forget that! 256 MB is often too less for office application. Enterprise Style applications and database will need at least ten times 256 MB (and even that is too small).
By the way Pagefile needs to be at least 4-8 GB.
Peter
Peter

Call failed, call failed

Similar Messages

Maybe you are looking for