Error in job for connection to CUA System

I have a problem with the two jobs in the u2018AS ABAP - Initial loadu2019 for a CUA system. According to the log is seems to be a memory issue!!!!
Extract from the logfile:
u2026u2026u2026
26.03.2009 09:57:31 :I:Initializing custom pass FromSAP: ReadABAPRoles
26.03.2009 09:57:31 :I:Initializing MX SAP BAPI object
26.03.2009 09:57:31 :W:Filter not supported when Listing CUA Roles. Ignoring :*
26.03.2009 09:57:35 :E:Unhandled Error in DSERuntime
java.lang.OutOfMemoryError: Java heap space (failed to allocate 84038672 bytes)
u2026u2026u2026
This error is related to the both the jobs: ReadABAPRoles and ReadABAPProfiles.
Please note:
Setting the %$rep.CUA_MASTER% equal u2018falseu2019 using the repository constant works for the both jobs (only the roles and/or profile in u2018localu2019 system the is read meaning no data from the subsystems in the CUA is read )
Any suggestions for handling this problem??
Best Regards
Tom Svarre

The text you enter in the dispatcher script after JAVAOPTIONS= is passed on as one parameter to the java executable. When you set JAVAOPTIONS=-Xmx256M -Xmx256M the effect is like the commandline java "-Xmx256M -Xms256M" java interprets this as an illegal heap size and refuses to start.
If you want to specify more than one javaoption, you also have to set MXDISPATCHER_EXECSTRING=1
This option causes the dispatcher to pass the arguments to the java executable as one string instead of split into separate parameters.
The reason this option is not turned on by default, is that this can cause problems with paths and parameters containing special characters that causes the command line interpreter to fail.
In your case, only specifyng the -Xmx is probably the best solution. Specifying -Xms will cause heavier load on the system also for jobs thatdoes not need a large heap.

Similar Messages

E-Recruiting - Doubt about job for changes in HR system.

Hi,
We are on E-Rec 604 with seperated standlone e-rec system.
I did the initial transfer of the Org Management and employees data through PFAL from ECC to E-Recruit and all were ok.
Now we are planning the job for future changes.
The job in e-recruiting is ok, using RBDMIDOC and RBDAPP01.
But I have some doubts with the job in HR system. I think I have to use those steps in the job:
RBDMIDOC
RSEOUT00
RBDMOIND
RBDCPCLR
It´s true?.
And in this case, with those steps the new employees in HR system will be created as internal candidates in E-Recruiting without problems?.
Could somebody help me, please?.
Best Resgrads,
Esther

Dear Esther,
In HR system, you only need to schedule these reports to transfer HR data from change pointers :
RBDMIDOC to created idocs from change pointers
RSEOUT00 to send idocs to the target system
RHALESMD : is used to generate Idocs that have already been processed or failed when report RBDMIDOC was running so
still with change pointers unprocessed in table BDCPV
Hope it helps,
Kind Regards
Christine

Error when checking for layout in sap system.

Hi,
   We have downloaded the Adobe Life Cycle Designer 8.0 from service.sap.com.As in our system we have already installed the SAP GUI ,we only run the ALDsetup. exe to install the Adobe Life Cycle Designer 8.0 .When we checked in our backend SAP system in t-code SFP-> Select form-> Display ---> Layout ,then it is giving error below.
Error :
Error while opening document
Message no. SOFFICEINTEGRATION143
Diagnosis
An error occurred in the desktop application while opening a document.
Procedure
Check first whether you can insert a document from this desktop application as an embedded object in another application. The necessary menu item is usually 'Insert --> Object'. The application then lists all of the OLE document types. Choose the type corresponding to the desktop applciation. If the insertion fails, the error is in the desktop application itself.
This error has various causes. Often, it is caused by activating certain add-ins. Sometimes, the desktop application is wrongly installed. The error should not recur once you have disabled any add-ins or reinstalled the desktop application.
Procedure for System Administration
If you cannot solve the problem as described above, enter a problem message. There are notes relating to how to generate the log file using the program SAPROFFICEINTEGRATIONTRACE.
Please check it & reply to it soon.
Regards
Nilesh

Hi Nilesh,
Refer the Below links, may be you will get some ideas,
http://help.sap.com/erp2005_ehp_04/helpdata/EN/45/2fbd67361003c3e10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/2c/241a427ff6db2ce10000000a1550b0/content.htm
Refer the Notes:
886572            ADS: Central Patch Note for SAP NetWeaver 7.0
834573            SAP Interactive Forms by Adobe: Acrobat/Adobe Reader Version
894009            Adobe document services: Configuration Guide (NW 7.0)
By
Parthi

Error in ise for a embedded processor system

Hello,
I added a .xmp file from xps to ISE-14.2 , it is having a peripheral attached with the microblaze.
While translating it is giving error like :
ERROR:EDK - :EDK:4110 - IPNAME: mesh3, INSTANCE: mesh3_0 - cannot find MPD for
the
pcore 'mesh3_v1_00_a' in any of the repositories -
C:\Users\mnit\Documents\noc\final_noc\system.mhs line 523
version not verified on hardware for architecture 'kiERROR:EDK - :EDK:4110 - IPNAME: mesh3, INSTANCE: mesh3_0 - cannot find MPD for
the
pcore 'mesh3_v1_00_a' in any of the repositories -
C:\Users\mnit\Documents\noc\final_noc\system.mhs line 523
Running UPDATE Tcl procedures for OPTION TESTBENCHGEN_SYSLEVEL_UPDATE_PROC...
ERROR: xps 'run memgen' call failed
ERROR: XPS process failed to run memgen.
ERROR: Generating the mem file for block ram initialization for C:/Users/mnit/Documents/noc/final_noc/system.xmp failed.
Please help.
Thank you.

I have seen a similar issue in 13.x and 14.1 version of XPS/ISE.
This is seen because platstudio run targets(including stubgen, memgen, testbenchgen) was not inserting library paths(global, project specific ). But memgen do accepts -lp path, so if running from command line it will work.
Since you are running in ISE flow this may not be an easy workaround.
Can you try open XPS project and select Project options and un-check generate test bench template and see if that helps?
These issues are seen moslty in the design migrated from older version to the newer version.
Regards,
Achutha

JCO Connect Exception for connecting to ABAP system

Hey Guys,
When running the program
[code]import com.sap.mw.jco.*;
public class TutorialConnect1 extends Object {
   JCO.Client mConnection;
   public Connect1() {
     try {
       // Change the logon information to your own system/user
       mConnection =
          JCO.createClient("100", // SAP client
            "RFCUSER2"// userid
            "RFCUSER2", // password
            null, // language
            "LABR3", // application server host name
            "00"); // system number
       mConnection.connect();
       System.out.println(mConnection.getAttributes());
       mConnection.disconnect();
    catch (Exception ex) {
      ex.printStackTrace();
      System.exit(1);
public static void main (String args[]) {
    Connect1 app = new Connect1();
[/code]
I get the exception
[code]java.lang.NoClassDefFoundError
     at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:836)
     at com.sap.mw.jco.JCO$Client.connect(JCO.java:3159)
     at com.ids.jco.JCOUtil.getClient(JCOUtil.java:37)
     at com.ids.jco.JCOUtil.main(JCOUtil.java:23)[/code]
My program in the developer studio compiles just fine, I have added all the libraries in the developer studio. In the "set additional libraries" context menu of the project I have included all the libraries.
In the Debug/Run settings I see all the libraries included when I test the program.
I am running the program on Netweaver Developer Studio SP15
Any help is appreciated.
Regards
Sumit.

Hi Sumit,
the exact problem is discussed in this forum..just check this....
Re: Some problems about JCo >.<
let me know...
                       Regards
                       Kishor Gopinathan

Getting Error in webIDE for connecting to destination NorthWind

Hi Experts,
I have added Northwind Data service as a destination in my account. But now when I am creating SAPUI5 master detail application it's not getting reflected in Service URL.
I am using this post for adding destination: How to use Northwind OData service with SAP Web IDE
Could anyone of you suggest waht I am missing?
Thanks,
Dhiraj More

Hi Dhiraj,
Whenever you are adding a new destination you have to refresh Web ide to reflect the changes.It is a default behaviour.
Regards,Midhun
SAP Technology RIG

Job for alert data reorganisation is not release or running -ERROR BPM

Hi
I am trying to set up BPM in solution manager EHP1 .
I ahve created a business process and also added teh required job,When i try to generate and activate the BPM i get an error as
"Job for alert data reorganisation is not release or running"
kindly suggest what i need to do to resolve this issue, which job to be scheduled and also all details and also any relevant document for the same
i have a project dead line to be met kindly help me ASAP
Thanks
Michael

Hi Michael
Was it show red alert ?
Do you still get same alert if you generate and activate
the BPMon session ?
If yes, there seems some problem on job "BPM_ALERT_REORG".
Maybe it is scheduled but not released.
(do you see scheduled job in SM37 ?)
1st, according to your description, you use ehp1.
In that case, as described in note 521820, do you already have
required note. Especially related to ST-SER like following.
1273127
1275225
1298310
1319473
1332197
1355132
1390111
I quickly checked description of each note, but could not find out
correction related to alert reorganization job. But it is better to
implement above notes if you do not have yet.
And if you still have problem (try generation and activation again)
even with above note, I recommend you to create SAP customer message
for component "SV-SMG-MON-BPM".
Best Regards
Keiji

Failure to connect to backend system in Portal

Hi Experts,
I was hoping someone could help, quickly!!
We are having an issue with transporting our VC model. We are on VC 7.0 SP17
I created a model in our development environment using a variable input form and adding the value help feature. After we deploy in our dev environment the model looks perfect!!!
We transported the VC model as an iview through the portal and we get a Failure to connect to back end system error. We ruled out that it is not a transport problem using the portal.
Can someone help!!
Thanks so much, Anna

Hi Again,
Thanks for both of your response, however, there is nothing in the log files andt we still have the Application error message, failure to connect to backend system.
We were able to bypass the error and the model starts to "semi-function" - but we cannot access the characteristic through value help, we just get empty drop downs. We all have the proper authorization in BI....
Do you think there is a permission problem in the back end portal?
Hopefully you can help.
Thanks so much, Anna

Error when trying to connect in synch manager

Hi there,
When trying to connect to an administration in synch manager, an error appears: SBO Error #-111: Failed to Connect to SBOCommon
System:
SAP Business One 2007A PL42
SQL Server 2005
SAP Webtools 2007 PL 13
Kind regards,
Andy Grootens

Hello Andy,
Can you log in to this instance of business one normally?
Did you set the username and password to connect in the synch manager?
Have you recently changed the users password?
James

Why is SLD necessary for connecting backend?

Hi, all.
Let me ask one basic question.
When the WD Java application connects to Backend, what is the role of
SLD? i know that SLD is necessary when runtime but all the necessary info
for connection is set in the JCo connection settings!
What is happening between WD Java and SLD when runtime?
Best Regards.
Sejoon

Hi,
All the technical systems are available to the portal and provide the associartion to the differenet technical systems and provide portal as a single point of access.
There is no direct assosiation between the java system to R/3 system for we are going to use the one connecter for connecting r/3 system from the java system.for this we are using the JCo(Java connector) by this connector only we are communicating R/3 system when you needt to connect the R/3 system that system should be available in your portal then by usin SLD we can add r/3 system as new technical sytem and by using JCo name(two logical destination systems Meta, Model systems) we are directly connecting to avail r/3 and get the data at the runtime.
The System Landscape Directory of SAP NetWeaver (SLD) serves as a central information repository for your system landscape. A system landscape consists of a number of hardware and software components that depend on each other with regard to installation, software updates, and demands on interfaces
Go thru this link you know all the details
http://help.sap.com/saphelp_erp2005vp/helpdata/en/31/f0ff69551e4f259fdad799a229363e/frameset.htm
Thanks,
Lohi.
Message was edited by:
Lohitha M

Background Processing? how schedule job for "System Error" Message .

Hello everyone,
in sap help i have read.
http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/frameset.htm
PCK> Monitoring>Message Monitoring-->Background Processing
you can schedule jobs for various background processing:
●     Archiving of messages processed successfully
●     Deletion of messages that are not to be archived
●     Restarting of messages with errors
●     Rescheduling of lost messages
can anyone understand this docu?
give me some introduction, how can i define and schedule these jobs ?
thx in advance!!
best regards
Yaning

Background Processing
Prerequisites
You have started the message monitor on the initial screen of the PCK and are in Background Processing.
Features
Archiving
You require two archiving sessions to archive messages:
●     One session to write the messages to the archive
●     One session to delete the persisted messages that have been archived
To do this, you schedule an archiving job, which implicitly schedules the sessions to write to the archive and delete the archived messages.
You can define one or more rules for each archiving job; these rules contain conditions that a message must meet in order to be archived by the job. At least one of the defined rules must be met for archiving to take place.
All information that is displayed for a message in message monitoring is archived, in addition to the audit log for each message.
Deleting
A standard delete job is created automatically. It runs once a day. You can schedule additional delete jobs; however, you cannot define rules for them.
Restarting
Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the system error status).
You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.
Rescheduling
A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.
Thx Aamir.
But I mean the messages with errors in Adapter Engine , not in Intergrations Engine.
the situation is like Naveen Pandrangi's WebLog
II. Errors in Adapter Engine [XI : How to Re-Process failed XI Messages Automatically|XI : How to Re-Process failed XI Messages Automatically]
I
Till now we have seen how to resubmit/restart message that failed in Integration Engine. One a message makes it from Integration Engine to Adapter Engine, the message is flagged as checked in Integration Engine. The status of the message in Adapter engine does not effect the processed state in Integration Engine. Now if this message was asynchronous, XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error .
*how can i schedule a job to automatically restart these messages with errors?
best regards
Yaning
Edited by: Yaning Liu on Aug 18, 2008 1:43 PM

Error saving job to database for standard jobs scheduling

Hi,
In IDES server when iam goto Tr.code -- SM36 -- Standard Jobs -- Default Scheduling iam getting below error.
Error saving job to database
Message no. BT117
Diagnosis
The SAP system was unable to save the current job in the database. This failure suggests that there is a problem with the database system or with the network connections between the SAP application servers and the database system.
System Response
Job not saved and not scheduled.
Procedure
To analyze this problem, start by checking the system log for messages about network or database problems. You can also use the computing center management system to check your system for problems.
Guide me for the same.
Thanku

HI,
Sometimes this error will come.
Try to schedule jobs manually using SM36 instead of using standard job button.
Also you can check this thread
Re: Error saving job SAP_REORG_JOBS to database
Which seems to report same problem.
Its nothing to take with database conenctivity as SAP is up and running .
Try this and revert.
Regards,

Trying to setup new iCloud in system preferences and get error message: "iCloud encountered an error while trying to connect to the server."

Here's the sequence of events:
Setting up a new iMac.
Migration Assistant was aborted during setup and a normal setup was completed.
Then ran Migration Assistant from the newly setup account.
It ran fine, but put all the data in a new account called "user".
Renamed "user" to a new name, renamed the home folder to a new name following these instructions: OS X: How to change your account name or home directory name
Delete the account we originally created, so just have one account with the name we want and all the data, email. Works fine.
Sign into the App Store with the account we share for purchases.
Now, the problem:
Go to System Preferences to setup iCloud with a new Apple ID
Get this error: "iCloud encountered an error while trying to connect to the server."
So I'm unable to setup iCloud for photo stream, FaceTime, etc.
Internet works fine, we can get mail, etc.
Rebooting doesn't help
Ideas?

never mind the problem is gone this morning.

Regarding mountain lion server: clients experience intermittent service connections. the server system log has the following error- Client handshake failed (6):113: Server not accepting client connections (any ideas???)

regarding mountain lion server: clients experience intermittent service connections. the server system log has the following error- Client handshake failed (6):113: Server not accepting client connections. any suggestions would be greatly appreciated - thank you

Hi Jason
I was getting the same behavior after Apple support had me delete some plist files to get Airplay going. I was also getting the following error:
the error occurred while processing a command of type 'writesettings' in the plug-in 'server vpn'
I went into ~/Library/Preferences/ and /Library/Preferences/ and deleted every plist contating the word server. I had to re-set up my server (meaning walk through some intial steps) but all of my settings were still there after that and everything started working again.
Just a thought, obviously try at your own risk but it worked for me.
Kellen

Error while creating jco connection for metadata?

Hi all,
we are using ep 6 sp 16.
I could create the JCO connection for application data but i am not able to create the jco connection for metadata for the same r3 server .
while creating the the connection
system name and logon group and disable
and when i click finish
it is giving following error
Failed to create new JCO client connection testmetadata: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java: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(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanking.
Rajendra

Hello Rajendra,
Good to hear from u. Let me try to give a soln for this problem of yours.
I think probably the logon group has not been specified in the backend.If thats the case then do the following:
Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
When you create the JCO connection, it should now show the logon group 'PUBLIC'.
Regards,
Prathamesh.

Error in job for connection to CUA System

Similar Messages

Maybe you are looking for