Failed to create new Authentication Context

Hi guys!
Any idea why i'm getting the following error?
Caused by: com.sun.identity.authentication.spi.AuthLoginException: Failed to create new Authentication Context: {0}
at com.sun.identity.authentication.AuthContext.login(AuthContext.java:620)
at com.sun.identity.authentication.AuthContext.login(AuthContext.java:524)
at com.sun.identity.authentication.AuthContext.login(AuthContext.java:383)
Thanks a lot

There could be various reasons for this. You need to provide more details.

Similar Messages

Failed to create new JCO client connection WD_FLIGHTLIST_RFC_METADATA_DEST:

I tried the demo in SDN, but failed .
Why?

Sorry I forget posting the msg:
for WD_FLIGHTLIST_MODELDATA_DEST:
nnection for 'WD_FLIGHTLIST_MODELDATA_DEST' was sucessfully tested with user 'ZZHZHU'
But :
for WD_FLIGHTLIST_RFC_METADATA_DEST:
Failed to create new JCO client connection WD_FLIGHTLIST_RFC_METADATA_DEST: 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:140) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:286) 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:252) 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:100) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:299) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:640) 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:391) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:265) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:345) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:323) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:865) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:240) 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:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:321) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_FLIGHTLIST_RFC_METADATA_DEST at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:138) ... 31 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:474) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 36 more

JCo client connection Failed to create new JCO client connection

hi All
I am trying to create a new JCO destination ion CE7.1 webdynpro content Admin. but I am getting following error.
Exception while creating JCo client connection Failed to create new JCO client connection weter: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_ACCESS_DENIED: User is not in role LcrInstanceWriterLD at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120) at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53) at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:220) at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:148) at com.sap.lcr.api.cimclient.CIMOMClient.createInstanceImpl(CIMOMClient.java:669) at ......
SLD is Up and running
CIM data is imported
Solution tried :
1) As no role wtih name LcrInstanceWriterLD was existing in the server ,hence created a new role with same name and assigned the LCR related action . Assigned the role to the user through which we are creating JCOs.
But we still getting the same error.
regards
Poonam

Hi Poonam!
Got to dig in the past a bit, I remember Users being able to create SLD object have to have certain permissions set in the J2EE UME. Simple Admin rights do not suffer, if I recall right.
Unfortunately I cannot go further in detail because this issue has been solved by a long gone collegue of mine.
Good luck anyway!
Jürgen

Win8RP: Failed to create new process "...javaw.exe" - Invalid argument

Hi all,
we have a huge Java (JRE 6.0.310.5) app that works fine on the Win 8 CTP, but on RP:
Failed to create new process "C:\Program Files (x86)\...\jre\bin\javaw.exe" - Invalid Argument
Thanks for any insight
G.

Hi,
Based on the error message 'Caused by: com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, only role administrators is allowed to access JMX' , this note shall solve this issue:
948970 - Caller J2EE_GUEST not authorized, only role administrators
Also check if the ADSUSER and ADS_AGENT have the correct password and the respective roles.
944221 - Error analysis for problems in form processing (ADS)
Which is your NW version?
Regards,
Lucas Comassetto.

Any workaround to CDG-00071 SYSTEM ERROR: Failed to create Forms API context

Hi all,
Is there a workaround to "CDG-00071 SYSTEM ERROR: Failed to create Forms API context" other than re-installing designer, then forms builder on the same ORACLE HOME directory? To do this will cause considerable downtime to our systems.

Hi Diego,
Do you have the correct, corresponding version of
Developer installed? You must install Developer to
be able to generate and run the Forms correctly.
If so, is it in the same <ORACLE_HOME>?
You normally get this error if you don't have Developer
installed in the same ORACLE_HOME as Designer. Please
see the relevant Designer installation guides for full details.
Regards,
Dominic
Designer Product Management
Oracle Corp

Failed to create new user null

All Experts
I am getting the following error message when I am trying to start Java Engine. I am trying to add Java Add on to the ABAP Stack. This was taken from security.0.log .
#1.5#001143312344001E00000003000006B400044C1E4BBCD4E7#1209592910253#/System/Security/UserStoreUME##com.sap.security.core.server.userstore.UserContextUME#######SAPEngine_System_Thread[impl:5]_14##0#0#Error#1#com.sap.security.core.server.userstore.UserContextUME#Plain###
Failed to create new user null#
#1.5#001143312344001E00000005000006B400044C1E4BBCFE64#1209592910253#/System/Security/UserStoreUME##com.sap.security.core.server.userstore.UserContextUME.engineCreateUser(String)#######SAPEngine_System_Thread[impl:5]_14##0#0#Info#1#com.sap.security.core.server.userstore.UserContextUME#Java###Created new user #1#<null>#
#1.5#001143312344001E00000006000006B400044C1E4BBCFFBA#1209592910253#/System/Security/UserStoreUME##com.sap.security.core.server.userstore.UserContextUME#######SAPEngine_System_Thread[impl:5]_14##0#0#Error#1#/System/Security/UserStoreUME#Java###Error during creation of default users or role assignments: #1#
Could not create user null: LOGONID_IS_NULL#
#1.5#001143312344001E00000008000006B400044C1E4BBD03D0#1209592910253#/System/Security##com.sap.engine.services.userstore.UserContext.<init>(UserContextSpi, Properties)#######SAPEngine_System_Thread[impl:5]_14##0#0#Fatal#1#com.sap.engine.services.userstore#Plain###Can not instantiate UserContext with given properties.#
#1.5#001143312344001E0000000B000006B400044C1E4BBD5C7C#1209592910284#/System/Security##com.sap.engine.services.security#######SAPEngine_System_Thread[impl:5]_14##0#0#Error#1#com.sap.engine.services.security#Java#security_0001#com.sap.engine.services.security.exceptions.SecurityResourceBundle#Unexpected exception:##
Please suggest

Hi Prasanna
I am getting this error while installing the Java Add-on. The installation was in the last stage and there it got struck when it tried to reboot the java engine. I am using SAPJSF user to communicate with ABAP stack and it has the full authorizations. I even checked and see that SAPJSF user is not locked. I also tried with another user and still the same issue. As per the log it the java engine is able to login with the user, but it is trying to create a user and fialing there. I am not sure why it is creating this user.
Regards,
Mahesh

Can not create newer OpenGL contexts with bumblebee

I have an Asus UX32VD with an Nvidia 620M. I am using bumblebee with virtualgl.
optirun glxinfo | grep OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 620M/PCIe/SSE2
OpenGL core profile version string: 4.3.0 NVIDIA 325.15
OpenGL core profile shading language version string: 4.30 NVIDIA via Cg compiler
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.3.0 NVIDIA 325.15
OpenGL shading language version string: 4.30 NVIDIA via Cg compiler
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
for example if I try to create a 3.0+ context in GLFW I always get
$optirun ./gltestrust
libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
[VGL] ERROR: glXCreateContextAttribsARB symbol not loaded
$LIBGL_DEBUG=verbose optirun ./gltestrust
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/swrast_dri.so
libGL: Can't open configuration file /home/maik/.drirc: No such file or directory.
libGL error: failed to load driver: swrast
libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/tls/i965_dri.so
libGL: OpenDriver: trying /usr/lib/xorg/modules/dri/i965_dri.so
libGL: Can't open configuration file /home/maik/.drirc: No such file or directory.
[VGL] ERROR: glXCreateContextAttribsARB symbol not loaded
I think swrast is a fall back mechanism because my GPU can't create the correct context.
Any help is appreciated.

Sorry for not updating the status of this question. I have solved this issue.
This was due to use of jsp:include tag. I really don't know the exact problems with the use of jsp:include on WLS 10.3. It works well on WLS 8.1.
However, I solved this by copying the content of my include page on jsp:include tag into the main page itself.
Thanks

NoSuchMethodException thrown when creating new authentication provider via console

I am trying to implement a custom authentication provider in WLS 7.0. I have started
with the
SimpleSampleAuthenticationProvider from the BEA code samples and followed the
instructions
to create an MBean type. When I try to create the new authentication provider
(MyAuthenticator) from the console, I get a NoSuchMethodException with the following
message:
[java.lang.NoSuchMethodException: couldn't find getter for 'Name' on com.ba.security.authentication.MyAuthenticatorMBean].
Sure enough, there is no "getName"
method in this interface, but the documentation doesn't say anything about creating
a "Name"
attribute in the MDF, only the ProviderClassName, Description and Version.
Despite the exception the provider is created; however, the console doesn't display
any information for the Name, Description or Version. In fact "Name" doesn't even
appear as a label (just a colon). Also, it can't be deleted by clicking on the
trash can icon. It says it has been deleted, but it hasn't. The platform is Solaris
2.7.
Thanks for any help,
David

David,
We had a similar issues initially and although nobody could tell us why
(and we didn't have the time to investigate further) it was resolved
when the classes from the M-Bean JAR were removed from the server
classpath (just the JAR file is in lib/mbeantypes directory of the server).
I have a support case and BEA support should have opened a documentation
CR to correct the documentation to inform for this issue (the CR is
094803 and the support case number is 376218)
HTH,
Dejan
David wrote:
I am trying to implement a custom authentication provider in WLS 7.0. I have started
with the
SimpleSampleAuthenticationProvider from the BEA code samples and followed the
instructions
to create an MBean type. When I try to create the new authentication provider
(MyAuthenticator) from the console, I get a NoSuchMethodException with the following
message:
[java.lang.NoSuchMethodException: couldn't find getter for 'Name' on com.ba.security.authentication.MyAuthenticatorMBean].
Sure enough, there is no "getName"
method in this interface, but the documentation doesn't say anything about creating
a "Name"
attribute in the MDF, only the ProviderClassName, Description and Version.
Despite the exception the provider is created; however, the console doesn't display
any information for the Name, Description or Version. In fact "Name" doesn't even
appear as a label (just a colon). Also, it can't be deleted by clicking on the
trash can icon. It says it has been deleted, but it hasn't. The platform is Solaris
2.7.
Thanks for any help,
David

[Application Insights] Fail to create new application using REST API

Hi,
I'm trying to create new application in Application Insights using the REST API.
I followed the instructions on
this page, but keep getting '404 Not Found', with the following error stream:
"{"error":{"code":"InvalidResourceType","message":"The resource type could not be found in the namespace 'microsoft.insights' for api version '2014-04-01'."}}"
The http method I'm using is: PUT
The request URI is:
"https://management.azure.com/subscriptions/some_real_subscription_id/resourceGroups/yonisha-new-rg/providers/microsoft.insights/component/yonisha-new-app?api-version=2014-04-01".
Can you please advice what am I doing wrong?
Few things:
I tried both with existing/non-existing resource group.
I set the Content-Length header to '0' (otherwise the server returns an error the the length is required).

Try the API Version "2014-08-01" and also make sure you are sending a location of "Central US" (its the only location available right now). An example of a PowerShell call that works is below. I would also suggest checking
out the new https://resources.azure.com/ which can help you construct the REST call.
New-AzureResource -Name TestAppInsights -ResourceGroupName TestRG -ResourceType "Microsoft.Insights/Components" -Location "Central US" -ApiVersion "2014-08-01"

Failed to create new JVueAXLib.JVueAXControlClass in Visual Studio 2008 C#

I installed the Oracle AutoVue Desktop Version 20.0.3.
Created an VS2008 C# COM DLL , added the jVueAX.ocx as reference, build as x86 32 bit dll.
In my AutoVueControl class, in the class Initialize method, will create a new Active X class.
JVueAXLib.JVueAXControlClass _jvueCtr = new JVueAXLib.JVueAXControlClass(); The COM dll build successfully, I register the dll as TLB.
The place I am using this dll is VB6 project, added COM dll as reference.
After I create object of AutoVueControl, then call it's Initialize method, create an new JVueAXControlClass always failed.
ExternalException: External component has thrown an exception.
ExternalException: Retrieving the COM class factory for component with CLSID {18287F19-E0CB-47E3-BB29-C28F8D805313} failed due to the following error: 80040111.
The CLSID {18287F19-E0CB-47E3-BB29-C28F8D805313} is JVueAXLib.JVueAXControlClass and is registered in my machine.

Which AutoVue are you using?
Desktop Version uses "AutoVueX Control" (AutoVueX.ocx)
Desktop Deployment uses "AutoVue ActiveX Control" (jVueAX.ocx)
Is it possible that the ActiveX controls are mixed due to both AutoVue flavors installed?

ISW fail to create new user in AD

I have a working version of iSW up and running ( SP1 on solaris 10) and am successfully syncing passwds and individual attributes from a DS > AD but am not able to get new user creation to succeed on the AD end. I have iSW configured to have Object creation flow from the LDAP DS to the AD DS, such that when I create a new user in the LDAP DS an attempt is made to create it on the AD end as well. I believe the error I am getting is related to passwd policy settings in the AD but have failed to narrow it down. I have set min passwd length to 0 and disabled passwd complexity in AD per the info found here:
[http://download.oracle.com/docs/cd/E19561-01/817-6262/817-6262.html#wp64747]
I am still getting the following error in the iSW error.log when the new user is attempted to be created within AD. Any one with AD experience might be able to point me to some other things within AD that are causing this ??
Thanks ! -john
[27/Oct/2011:13:25:34.270 -0700] SEVERE 40 CNN101 meuse "Unable to create user "cn=atresalmas,ou=test,dc=education,dc=ucsb,dc=edu" at ldaps://ad-devel.education.ucsb.edu:636. LDAP add operation failed. Error code: 53, reason: 00002077: SvcErr: DSID-031907E9, problem 5003 (WILL_NOT_PERFORM), data 0 For more information, please reference the Microsoft error database by looking up error code 8311 at http://msdn.microsoft.com/library/en-us/debug/base/system_error_codes.asp or by executing 'net helpmsg 8311' at any Windows command prompt." (Action ID=CNN100-13322772892-5, SN=8)

Hello,
Microsoft Azure forums are over here:
https://social.msdn.microsoft.com/forums/azure/en-US/home
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Failing to create new SQL farm with FSconfig.exe for ADFS federation Services on an Azure SQL

I'm building ADFS in Azure. My plan is to use the Azure SQL. The problem is that FSconfig seams not to work with Azure SQL. Here's what i did untill now:
- I followed the documentation and created a new login and user (adfslogin, adfsuser) in a new
"adfsv21" database. Then i added the user to db_owner role.
- From c:\windows\adfs i run FSconfig: FSConfig.exe CreateSQLFarm /ServiceAccount mysa /ServiceAccountPassword ******** /SQLConnectionString "database=Adfsv21;server=[azureServer];User Id=mysa;Password=********" /AutoCertRolloverEnabled. I
tried it with both accounts, mysa and adfsuser with the same poor results.
The result is: "The following error occurred: The specified service account mysa is not valid. Specify
a different service account, and try again."
- I configured odbc and tested the connection. mysa can connect but adfsuser caanot. Why?
To be short, its not working. See this post with similar problems: google to "SQL server farm configuration error"...
So, is Azure SQL & ADFS not complatible? Really not?

My apologies for take a super long time to reply. Are you still having issues here? How can we help?
Thanks Guy

Exception while creating JCo client connection Failed to create

Hello all -
I am trying to create JCo metadata connections and I am getting the below error trace.
Exception while creating JCo client connection Failed to create new JCO client connection SAP_R3_HumanResources_Metadata: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to change password for key SAP_R3_HumanResources_Metadata in secure storage at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:149) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:299) 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:265) 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.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(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) Caused by: com.sap.security.core.server.securestorage.exception.ObjectStorageException at com.sap.security.core.server.securestorage.remote.RemoteSecureStorageClientContextImpl.storeObject(RemoteSecureStorageClientContextImpl.java:600) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SecureStorageWrapper.changePassword(SecureStorageWrapper.java:137) ... 33 more
Could anybody please suggest what is wrong with this creation?
Thanks much!!

Hi Maria,
Please update the host and sevice file first then check the SLD test and SLD Data supplier in visual admin.
Also check and verify the data using in the Jco destination creation.
Hope it will helps
Regards
Arun Jaiswal

Error On Creating New 2013 Workflow

Hi;
When i create a 2013 workflow on English site, everything is OK;
But on creating 2013 workflow on non-English site (with language pack installed), i get following error:
Server-side activities have been updated.You need to restart SharePoint Designer to use the updated version of activites.
i delete sharepoint designer cache but nothing changes.
any ideas?

Hi,
According to your post, my understanding is that you failed to create new 2013 workflow.
Please make sure you have downloaded the correct version of SharePoint Designer 2013. You can download it via the following link:
http://www.microsoft.com/en-us/download/details.aspx?id=35491
Please troubleshoot for Workflow Manager 1.0 publishing, management and execution. You can refer to
http://technet.microsoft.com/en-us/library/jj193529.aspx
Here is a similar thread for your reference:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/f255f4b4-1828-4ccb-983a-5efbf0e020ae/sharepoint-designer-2013-server-side-activties-have-been-updated-prompt?forum=sharepointcustomization
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Creating new site

I'm new to UCM/ Site Studio. I have the sample site installed which works fine, but when I use Site Studio to create a new site, the immediate error I get is:
Failed to create new site hierarchy "NewSite".
(Invalid metadata for 'SS_PROJECT_NewSite'. Virtual folder does not exist.)
What's going on here? I also tried to get around it by creating a different weblogic user project, but that gave Site Studio Is it just that buggy?

Grr.
I did indeed go to Set Default Project Document Info, but going in there again the "Folder" value was blank. So I clicked "Browse", then selected no folder (just "OK") and then the folder value was set to "/". After I clicked Save it worked and I could create a new site.
So it works now, but this seems like a bug that I needed to click Browse and Ok for it to work...

Failed to create new Authentication Context

Similar Messages

Maybe you are looking for