Impact of Hardware Change on SSO tickets

Hi Experts,
We are carrying out a hardware refresh of our production EP database server. Hardware refresh involves changing the server on which the EP database & application servers are residing with no change in the Hostname and IP addresses for the EP servers.
We use SSO tickets to connect our EP system to our ECC6 system for accessing ESS/MSS functionality & are doing an impact analysis before the hardware refresh & would like to check if there can be any impact to the single sign on setup between our EP & ECC6 system.
Appreciate any comments. Thanks.
Regards,
Murali

Hi,
There should be no effect at all unless and until Hostname and IP address does not change.
With Regrads,
Saurabh

Similar Messages

RFC_ERROR_LOGON_FAILURE: System received an expired SSO ticket

Hi All,
We installed NW 7.0 SP 14 with EP 7.0; All the post-installation steps were completed and JCo's configured with SSO to backend ECC 6.0 system.
Since morning we are getting he below mention error when trying to test the JCo's for all the users.
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: System received an expired SSO ticket.
Tried many variations and also changed the Ticket expiration time(to 24 from 8) restarted the server but the problem still remains. Can any one suggest any more ideas on how to sole this?
Is this problem any where related to CR Content? If so can you suggest how to check the current veriosn and how to find out the exact level which would be supported for our NW system.
Thanks in advace for you help.
Thanks,
Sravanthi

Hi,
Your portal certificate has expired.
To renew - you need to generate a new one in the ticket keystore using Visual Admin.
Next you export the new updated ticket to the trusting system (in yoru case ECC) using tcode STRUSTSSO2.
You then import the ticket and assign it to the ACL.
Issue should then be resolved.

Multiple SSO Tickets Cause Problem

Dear SAP Fellas,
Our customer implemented NWBC based travel management into ECC6 based HR system.
It uses its own SSO tickets, when users log on via webbrowser, it is working fine.
In this landscape there is an Enterprise Portal used for other purposes, but also issues its own SSO tickets.
When this portal is also used at the same time or was used before (so an 'alien' SSO ticket is in the browser's cache), ECC6 changes logon style, username and password fields are greyed out and asks user to press a button for an additional popup window, where username and password can be typed in. This behavior breaks NWBC's operation internally, every clicks on menuitems invokes this password window.
Do you know any way to teach this ECC6 system to process only its own SSO ticket and ignore others?
Thank you for answers in advance.

Dear SAP Fellas,
Our customer implemented NWBC based travel management into ECC6 based HR system.
It uses its own SSO tickets, when users log on via webbrowser, it is working fine.
In this landscape there is an Enterprise Portal used for other purposes, but also issues its own SSO tickets.
When this portal is also used at the same time or was used before (so an 'alien' SSO ticket is in the browser's cache), ECC6 changes logon style, username and password fields are greyed out and asks user to press a button for an additional popup window, where username and password can be typed in. This behavior breaks NWBC's operation internally, every clicks on menuitems invokes this password window.
Do you know any way to teach this ECC6 system to process only its own SSO ticket and ignore others?
Thank you for answers in advance.

Error:System rejects all logons using SSO tickets:RRMX

Hi,
I have created a System in my portal which connects to the BW system.I am able to execute the transaction RSA1 by creating a transaction iview which connects to the system created above but when i try to execute RRMX in a transaction iview i get an error displaying a message : System rejects all logons using SSO tickets.
The transaction iview uses WinGUI.
Please let me know if anyone has the solution for this.
ThanksInAdvance,
Varma.

Hi Rajendra,
I guess you need rrmx access to change the queries ? i that is the case did you guys try role "com.sap.ip.bi.business_explorer_showcase" which has Bex web analyzer, where in you can create or modify queries in Java built in iviews. Have a look at that and hope it might be useful.
Thanks,
Praveen
PS.Dont forget to reward points

My MacBook Pro is running very hot after lion install. Are there any hardware changes that will help? What can I do to get it back to normal?

My MacBook Pro is running very hot after lion install. Are there any hardware changes that will help? What can I do to get it back to normal?

I get the impression that most of the users on older hardware experiences similar temperature issues on Lion for a long time now. Awaiting for confirmation from the original poster.
In the meantime I'm just cautious with regards to pushing the machine to such extreme temps, since something tells me such behaviour which includes monitor flickering and the likes is nothing but abnormal for any type of use...
Any clues if 10.7.5 does anything on this? If not I'm afraid i see myself going back to SL for good...

Unable to Interpret SSO Ticket Recieved.

Hai ,
While working in ESS , I tried to create travel request. While creating i recieved Error message.
Error: System is Unable to Interpret SSO ticket recieved.
Kindly Help me out.
Regards
ArunRajan,
Hosur

Hi,
Please check tha SSO is configured correclty & test is fine from both Portal & Back-end side.
Please refer to
[http://help.sap.com/saphelp_nw70/helpdata/EN/4d/dd9b9ce80311d5995500508b6b8b11/content.htm|http://help.sap.com/saphelp_nw70/helpdata/EN/4d/dd9b9ce80311d5995500508b6b8b11/content.htm]
In case you still face an issue, then please let me know.

What are the changes to be done on BW end during hardware change of source system?

Hello Gurus,
There is some hardware changes happening and I need help in certain things which I need to do from BW point of view. First of all, I have attached a figure showing my system landscape. I would kindly request you to go though the fig first.
For QA, initially we were using AG3 as the source system, now they have made the hardware changes, made a system copy of AG3 into the new system AEQ. We have connected our BW QA system to this new system AEQ. Now when I check the system, there are no data in set up tables (I am using SD and MM), but there are data in tables. But when I replicate data sources from AEQ to BW QA, the existing transformations and DTPs will disappear. So, that left me with 2 options-
1. Either transport old transformation and DTP from BW DEV to BW QA
2. Or create new transformation and DTP in BW QA system.
Can you experts please suggest me what should be the solution?
Also, please note that, the basis team started the hardware changes with ECC QA system for some reason. Once ECC QA is fine, they are planning to make the changes in ECC DEV system (from AG2 to AED). Currently, AG2 is connected to BW DEV and AEQ is connected to BW QA.
Can you please suggest me whether there will be any issue if we opt to transport transformation and DTP from BW DEV to BW QA when BW DEV is still connected to old source system? Or, is there any other easy way to sort this out? Please suggest?
Thanks a lot
Rakesh

Hi,
1. Either transport old transformation and DTP from BW DEV to BW QA?
Yes, better to transport from bw dev to bw qa
2. Or create new transformation and DTP in BW QA system?
at BW Quality, creation may not be possible. Better to transport from bw dev to bwq.
or use standard abap program to activate transformations and dtp.
When changes are applying at source then you just need to take care the delta queues
clear all queues by running related V3 jobs and delta info packs. make them as 0 count.
once basis team was done changes later try to check your delta loads at bwq .
Thanks

A failure occured while importing Java SSO ticket certificate in ABAP stack Exception : FOREIGN_ENQUEUE_LOCK

Dear All,
We have completed the fresh installation of Soman7.1.
Now , We are doing the "Configuration of the Solman" and we are in the Step "Basic configuration ".
SID: SMI
Hostname: Solmantrg
Solman version: 7.1
The SSO Setup is failing with below error.
Message :
A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null. Details : 'user' missing
Details of the Log
Found SID for SSO ACL entry : SMI
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg.thetimes.co.in (client 001)
The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
A failure occured while importing Java SSO ticket certificate in ABAP stack
!! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
A failure occured while connecting to ABAP stack on solmantrg.thetimes.co.in sys=01 client=001 user=null
!! Exception : 'user' missing
The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
Exception
com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
========================
com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:518)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1087)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3310)
at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:773)
at com.sap.sup.admin.setup.CommonServices.getJcoClient(CommonServices.java:722)
at com.sap.sup.admin.setup.SolManRfcAdapter.getJ2eeSsoSettings(SolManRfcAdapter.java:649)
at com.sap.sup.admin.setup.ManagingServices.updateSSOfromURLrepository(ManagingServices.java:790)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:773)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
In strustsso2, cerficate date is valid only.
kindly help us to fix this SSO_Setup issue
Thanks and Regards,
Gayathri.K

Hi ,
Thanks for the above reply.
I have executed the Step 2.3 AND 2.4 and i started the SSO Setup again. Still i am getting below error
Message
A failure occured while importing Java SSO ticket certificate in ABAP stack
Details Of the Log
Found SID for SSO ACL entry : SMI
Found login.ticket_client for SSO ACL entry : 000
The Read entry permission on TicketKeystore/SAPLogonTicketKeypair-cert was given to sap.com/tc~webadministrator~solmandiag/servlet_jsp/smd/root/WEB-INF/lib/SetupLib.jar
The TicketKeystore/SAPLogonTicketKeypair-cert was succesfully read (619 bytes)
ABAP SSO ticket certificate of SMI was imported in ABAP PSE of solmantrg (client 001)
The ABAP SSO ticket certificate was successfully imported in ABAP System PSE, and the ACL updated accordingly (SID=SMI LoginTicketClient=001)
A failure occured while importing Java SSO ticket certificate in ABAP stack
!! Exception : FOREIGN_ENQUEUE_LOCK(Abap cause=SOLMAN_ADMINE_TABLEE)
The ABAP instance profile contains the parameter : login/accept_sso2_ticket=1
The SSO ticket Certificate <CN=SMI> has been successfully imported into Java Keystore
The com.sap.security.core.server.jaas.EvaluateTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/SQLTrace*OpenSQLMonitors was already set to ticket
The Authentication template for component sap.com/SQLTrace*SQLTrace was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*monitoring was already set to ticket
The Authentication template for component sap.com/tc~monitoring~systeminfo*sap_monitoring was already set to ticket
The Authentication template for component sap.com/com.sap.security.core.admin*useradmin was already set to ticket
The Authentication template for component sap.com/tc~webadministrator~solmandiag*smd was already set to ticket
The Authentication template for component sap.com/tc~smd~e2etraceupload*E2EClientTraceUploadW was already set to ticket
The com.sap.security.core.server.jaas.EvaluateAssertionTicketLoginModule already contained the entry : trustedsys=SMI, 001 trustediss=CN=SMI trusteddn=CN=SMI
The Authentication template for component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1 has been set to evaluate_assertion_ticket
The Login Module BasicPasswordLoginModule was added to the security component sap.com/tc~smd~EemAdminGateway*EemAdmin_Config1
The ABAP instance profile contains the parameter : login/create_sso2_ticket=2
Exception
com.sap.mw.jco.JCO$AbapException: (126) FOREIGN_ENQUEUE_LOCK: FOREIGN_ENQUEUE_LOCK
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1512)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3937)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3570)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:276)
at com.sap.sup.admin.setup.AbapSysRfcAdapter.addTrustedIssuer(AbapSysRfcAdapter.java:249)
at com.sap.sup.admin.setup.ManagingServices.setupDualStackSSO(ManagingServices.java:752)
at com.sap.sup.admin.setup.SetupStep.runExec(SetupStep.java:564)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:445)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:674)
at com.sap.sup.admin.setup.ws.SetupWrapper._diagSetup(SetupWrapper.java:279)
at com.sap.sup.admin.setup.ws.SetupWrapper.diagSetup(SetupWrapper.java:21)
at sun.reflect.GeneratedMethodAccessor2202.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:331)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:76)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:174)
at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:81)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:90)
at SoapServlet.doPost(SoapServlet.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1060)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Also , i have checked the note # 1008474 Diagnostics Setup Wizard uses wrong ABAP client.
As mentioned in above note, i have checked in visual admin all settings are maintained correctly.
RFC destination WEBADMIN & SOLMANDIAG is also working fine.
please tel why i am getting Foreign Enquelock
Regards,
Gayathri.K

Problem accessing R/3 with SSO ticket from the EP6.0

Hi all,
I have seen this thread: Problem accessing R/3 with SSO ticket from the EP6.0
I know that it is possible to read SSO ticket from the Cookie in WebDynpro application.
Now we are at the first step, we don't know how to read SSO ticket from the Cookie in WebDynpro application with java code.
So anyone can help us?

Hi,
This has been discussed in a previous forum.Check this link.A code snippet is also there to read a cookie in webdynpro with this question
How to implement SSO between Portal, Webdypro and ABAP system?
I am not able to send the link exactly.
Regards,
Sowjanya.
Message was edited by: Sowjanya Chintala

Need help for finding objects impacted by size change for an infoobject

hi all,
need help for finding objects impacted by size change
for xxx infoobject, due to some requirements, the size to be changed from
char(4) to char(10), in the source database tables as well as adjustment
to be done in BI side.
this infoobject xxx is nav attribute of YYY as well as for WWW
infoobjects. and xxx is loaded from infopkg for www infoobject load.
now that i have to prepare an impact analysis doc for BI side.
pls help me with what all could be impacted and what to be done as a
solution to implement the size change.
FYI:
where used list for xxx infoobject - relveals these object types :
infocubes,
infosources,
tranfer rules,
DSO.
attribute of characteristic,
nav attribute,
ref infoobject,
in queries,
in variables

Hi Swetha,
You will have to manually make the table adjustments in all the systems using SE14 trans since the changes done using SE14 cannot be collected in any TR.
How to adjust tables :
Enter the table name in SE14. For ex for any Z master data(Say ZABCD), master data table name would be /BIC/PZABCD, text table would be /BIC/TZABCD. Similarly any DSO(say ZXYZ) table name would be /BIC/AZXYZ00 etc.
Just enter the table name in SE14 trans --> Edit --> Select the radio button "Save Data" --> Click on Activate & adjust database table.
NOTE : Be very careful in using SE14 trans since there is possibility that the backend table could be deleted.
How to collect the changes in TR:
You can collect only the changes made to the IO --> When you activate, it will ask you for the TR --> Enter the correct package name & create a new TR. If it doesn't prompt you for TR, just goto Extras --> Write transport request from the IO properties Menu screen. Once these IO changes are moved successfully, then the above proceduce can be followed using SE14 trans.
Hope it helps!
Regards,
Pavan

RFC_ERROR_LOGON_FAILURE: This system rejects all logons using SSO tickets

hello again,
i manage to restart my server and applications
but now when i try to start :
http://host:port/b2b/b2b/init.do
and i can't
the logs show these line which i don't understand :
1}#2#parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
Properties: {lang=en, passwd=?, sysnr=01, client=300, user=$MYSAPSSO2$, ashost=192.168.1.14, jco.client.type=A, maxcon=0, jco.client.trace=1, codepage=1100}
Client not connected#com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mysapsso2' missing
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:456)
     at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:922)
     at com.sap.mw.jco.JCO$Client.connect(JCO.java:3171)
     at com.sap.isa.core.eai.sp.jco.JCoConnectionStateless.getInternalJCoClient(JCoConnectionStateless.java:118)
     at com.sap.isa.core.eai.sp.jco.JCoConnectionStateless.isValid(JCoConnectionStateless.java:479)
     at com.sap.isa.user.backend.crm.IsaUserBaseCRM.loginViaTicket(IsaUserBaseCRM.java:1677)
     at com.sap.isa.user.backend.crm.IsaUserBaseCRM.loginForBPRole(IsaUserBaseCRM.java:127)
     at com.sap.isa.user.backend.crm.UserBaseCRM.login(UserBaseCRM.java:248)
     at com.sap.isa.user.businessobject.UserBase.login(UserBase.java:308)
#1.5#000423A6E1B400640000002E0000169C00041D66DC92778B#1158227531375#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_17##0#0#Debug##Plain###[actionxecution]='end' [actionclass]='com.sap.isa.user.action.LoginBaseAction' [path]='/login' [forward]='/base/error_ume.jsp' [exectime]='32'#
#1.5#000423A6E1B400480000000F0000169C00041D66DCE4AE38#1158227536750#tracing.advisor.method#sap.com/crm~b2b#tracing.advisor.method#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###AdvisorBusinessObjectManager:<constructor>#
#1.5#000423A6E1B40048000000120000169C00041D66DCE4B676#1158227536765#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###[actionxecution]='begin' [actionclass]='com.sap.isa.isacore.action.IsaCoreInitAction' [path]='/b2b/coreinit'#
#1.5#000423A6E1B40048000000130000169C00041D66DCE4C261#1158227536765#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###[actionxecution]='end' [actionclass]='com.sap.isa.isacore.action.IsaCoreInitAction' [path]='/b2b/coreinit' [forward]='/user/performLogin.do' [exectime]='0'#
#1.5#000423A6E1B40048000000140000169C00041D66DCE4C607#1158227536765#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#ABAHMANE#466##crm_CRM_15121750#ABAHMANE#a4727b3043d611dbc03b000423a6e1b4#SAPEngine_Application_Thread[impl:3]_8##0#0#Debug##Plain###[actionxecution]='begin' [actionclass]='com.sap.isa.core.action.SetReloginCookieAction' [path]='/relogin/setcookie'#
#1.5#000423A6E1B4004800000
many thnx if you can help me

it doesn't work ..
i need to understand the meaning of SSO ticket in sap logon..
i still have the error :
parameters: [client]='null' [user]='null' [language]='null' [ashost]='null' [systemnumber]='null' [mshost]='null' [gwhost]='null' [gwserv]='null' [group]='null' [systemid]='null'
Properties: <u>{lang=en, passwd=?, sysnr=01, client=300, user=$MYSAPSSO2$, ashost=192.168.1.14, jco.client.type=A, maxcon=0, jco.client.trace=1, codepage=1100}</u>Client not connected#com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'mysapsso2' missing
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:456)
why does it replace the user i mapped in XCM JCO setting with the user 'mysapsso2' ?
plz help me

Kernal panic fixed by hardware change??

Hello,
I have a G4 that I've upgraded quite a bit* and during the last month it has been randomly** suffering from kernel panics, sometimes when I'm using it, sometimes when it's left on its own. When I reboot (as the screen instructs me), the computer gets as far as the grey apple logo (but no spinning loader) and goes into kernel panic again.
Previously I had had to leave the machine for several hours before I could successfully reboot again. Recently, however, I've discovered that if I say unplug the DVD drive or swap a stick of RAM the machine will reboot successfully immediately.
So I'm wondering why, when I alter the hardware attached, should the machine boot up immediately as opposed to me having to leave it for several hours if I don't? Could this be a screwed motherboard (pls say no)? What goes on during the early stages of boot that would in effect reset the system preventing the kernel panic?
I've reinstalled the OS and have recently started to check the hardware, which I will continue to do. I write now because I believe if I can find out why hardware changes temporarily fix it I should arrive at answer sooner.
NOTES
* - Upgraded 2 months ago with Sonnet Encore 1.6GHz cpu and ATI 9000 graphics card. Machine run for about a month with absolutely no problem. Sonnet say its not the CPU.
** - Can be anything from 2 days to a week between crashes.

I have a similar problem with kernel panics and freezes but the computer will restart again afterwards and I don't have to shift my hardware around to get it to do so. However it has stopped chiming at start-up which I know is bad. It is a little more stable if I stay in the log in screen and access from my other computer on the network but it will freeze even then at times. The error log for my panics is:
panic(cpu 0 caller 0x000A8A00): Uncorrectable machine check: pc = 0000000098DE2660, msr = 000000004000F030, dsisr = 42000000, dar = 00000000E02FE000
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 0000000000000000
Latest stack backtrace for cpu 0:
Backtrace:
0x000952D8 0x000957F0 0x00026898 0x000A8A00 0x000A8148 0x000AB980
Proceeding back via exception chain:
Exception state (sv=0x38165780)
PC=0x98DE2660; MSR=0x4000F030; DAR=0xE02FE000; DSISR=0x42000000; LR=0x00000058; R1=0xF0305840; XCP=0x00000008 (0x200 - Machine check)
Kernel version:
Darwin Kernel Version 8.9.0: Thu Feb 22 20:54:07 PST 2007; root:xnu-792.17.14~1/RELEASE_PPCModel: PowerMac3,5, BootROM 4.3.3f2, 2 processors, PowerPC G4 (2.1), 1 GHz, 1.5 GB
Graphics: NVIDIA GeForce4 MX, GeForce4 MX, AGP, 64 MB
Memory Module: DIMM0/J21, 512 MB, SDRAM, PC133-333
Memory Module: DIMM1/J22, 512 MB, SDRAM, PC133-322
Memory Module: DIMM2/J23, 512 MB, SDRAM, PC133-333
Modem: Spring, UCJ, V.90, 7.0F, APPLE VERSION 0007, 7/31/2000
Network Service: Built-in Ethernet, Ethernet, en0
PCI Card: usb, usb, SLOT-3
PCI Card: usb, usb, SLOT-3
PCI Card: pci1735,e0, SLOT-3
PCI Card: pci9004,7850, sppciscsibus, SLOT-4
Parallel ATA Device: ST380021A, 74.53 GB
Parallel ATA Device: ST3120026A, 111.79 GB
Parallel ATA Device: PIONEER DVD-RW DVR-104, 2.64 GB
USB Device: Hub, Up to 480 Mb/sec, 500 mA
USB Device: C-Media USB Headphone Set, Up to 12 Mb/sec, 500 mA
USB Device: HP ScanJet 6300C, Hewlett-Packard, Up to 12 Mb/sec, 500 mA
USB Device: Hub in Apple USB Keyboard, Alps Electric, Up to 12 Mb/sec, 500 mA
USB Device: Nostromo SpeedPad2, Honey Bee, Up to 1.5 Mb/sec, 100 mA
USB Device: Microsoft Trackball Explorer®, Microsoft, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple USB Keyboard, Alps Electric, Up to 1.5 Mb/sec, 250 mA
USB Device: USB Device, Up to 1.5 Mb/sec, 500 mA
USB Device: iMic USB audio system, Griffin Technology, Inc, Up to 12 Mb/sec, 500 mA
I would really appreciate some ideas on how to resolve this. I will look over that Resolving Kernel Panics article as well.
Thanks

Lens correction filter doest work after hardware change

Hello,
Since I reinstalled my computer from scratch after a hardware change (went from AMD GPU to an NVIDIA GPU) lens correction filter doesn't work anymore.
I can open the tool, do the corrections but when I pusch apply, the tool is closed but the corrections are not applied to the picture in the editor screen.
No layer is added.
When I close PSE multiple temp files are left in the root directory of my secundary drives.
This happened with PSE 7 so I bougth PSE 9, de-installed PSE 7 and installed PSE 9. Guess what: same problem, no corrections applied.
Is this Nvidia related since everything worked nice in PSE 7 with amd catalyst drivers ?
I'm running Vista32 sp2, with latest directx and latest nvidia geforce drivers.
mda97

1) The problem with the Delete Cropped Pixels option is that it essentially eliminates the nicest functionality of the new crop tool.....My suggestion to Adobe would be to enable some way of having the screen view imported into the lens correction filter but leaving the cropped information intact for future adjustments once the image was returned to the main PS window....
2) The Camera RAW preferences setting adjustment was what I needed, thank you!
3) The problem with the saving to PSD option, is that even when I do NOT have layers, it seems to default to saving as PSD. Essentially, any adustment I make, except the most basic, even if I do not have any layers as a result, gets interpreted as needing to be saved as a PSD. This is categorically different than in all prior editions of Photoshop. (For instance, whenever I worked on JPGs and I would save a file on older versions, it would simply default to JPG unless I actually had visible layers in the layers window. On this one, if I do anything like content-aware fill, or use the patch tool or healing brushes, it then saves to PSD by default, even though there are NO visible layers that need flattening. It seems as if the program is interpreting those kinds of adjustments internally as layers and selecting PSD as the necessary file type to save to as a result.)
Thanks for your help; if you have any other suggestions for work arounds for the third problem, I would greatly appreciate them.
-Janet

Usually this system rejects access using SSO tickets exception

Hi,
I'm facing a problem when trying to access to some tasks in the UWL.
It appears an error message saying "Usually this system rejects the access using SSO tickets" (it's not an accurate translation, the message in spanish says "Generalmente este sistema rechaza el acceso mediante ticket SSO").
The same happens when I try to access to the backend system (R/3 Release 4.6C) using an iView.
At first I thought it was a problem related with the certificate between the backend and the portal, but we have reimported the certificate in the backend and the problem still happens. And the certificate doesn't expire until 2012.
I have restarted the J2EE Engine too, but it continues the same.
What is extrange is that all the WebDynpro applications that call RFCs in the backend system work fine and get the information.
Anybody knows what can I do to solve this problem? Yesterday all worked fine and this morning I saw all this.
The release is Enterprise Portal 6.0 SP18.
Thank you very much! All help would be highly appreciated (and rewarded)!

You can check the following
- the following profile parameters are set
login/create_sso2_ticket = 2
login/accept_sso2_ticket = 1
- if the corresponding R3 user is not locked or expired
- if the portal certificate is added to the ACL list of the R/3 System (using STRUSTSSO2)
Regards,
Abhishek

UWL config-S ystem received an expired SSO ticket not found in system

Hi All,
We are getting following erro while configuring UWL.
Exception type:com.sap.netweaver.bc.uwl.connect.ConnectorException Message:uwlExceptionID: 1179143938021 :uwlExceptionID: 1179143938021 JCO Function template USER_NAME_GET:SAPR3CLNT900WF:com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: System received an expired SSO ticket not found in system
Please HELP.
Rgds
Ganga

hi ganga,
may be there is problem with uwl configuration. u try with this link....
hope ur error will clear........
<b>How configure UWL in Portal 7.0,
Problem configuring UWL,</b>
regards
bhargava

Impact of Hardware Change on SSO tickets

Similar Messages

Maybe you are looking for