Persistence exception when creating UME users

Hello,
I'm encountering a persistence exception while attempting to create users in the Portal using ABAP as my UME store. The exception indicates that a user name is too long to be valid (e.g. 1Z8uN8K0JUdBbS~Z1WN8). This name is apparently generated since it is different in each error message in the log.
I've read the Help files throughly and have configured the SAPJSF user to be in the proper role for writing (SAP_BC_JSF_COMMUNICATION) and made sure that the authorizations for that role are properly generated and assigned. The values for the ume settings in configtool are configured to connect properly and everything tests fine in the portal (except creating users, of course). I'm running everything on SPS09.
The detailed error message is below. TIA for your thoughts.
Rob
Date : 12/11/2006
Time : 17:07:09:486
Message : An exception was thrown in the UME/ABAP user management connector. Message: Not a valid SAP user ID:
"1Z8uN8K0JUdBbS~Z1WN8". Reason: SAP user ID must contain at least 1 and at most 12 characters.
[EXCEPTION]
com.sap.security.core.persistence.datasource.PersistenceException: Not a valid SAP user ID: "1Z8uN8K0JUdBbS~Z1WN8".
Reason: SAP user ID must contain at least 1 and at most 12 characters     at
com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178
)     at com.sap.security.core.persistence.datasource.imp.R3Persistence.getPrivateIDPart(R3Persistence.java:2532)
at
com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.bindNewPrincipalDatabag(DataSourceBaseI
mplementation.java:340)     at
com.sap.security.core.persistence.datasource.imp.R3Persistence$Transaction.bindNewPrincipalDatabag(R3Persistence.java
:8727)     at
com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.bindNewPrincipalDatabag(PrincipalDatabagFactory
Instance.java:4640)     at
com.sap.security.core.persistence.imp.PrincipalDatabag.getIDParts(PrincipalDatabag.java:1034)     at
com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.isPrincipalDatabagAttributeModifiable(Principal
DatabagFactoryInstance.java:2331)     at
com.sap.security.core.imp.PrincipalFactory.isPrincipalAttributeModifiable(PrincipalFactory.java:255)     at
com.sap.security.core.imp.PrincipalFactory.isPrincipalAttributeModifiable(PrincipalFactory.java:215)     at
com.sap.security.core.jmx.impl.CompanyPrincipalFactory.isPrincipalAttributeCreateable(CompanyPrincipalFactory.java:24
71)     at com.sap.security.core.jmx.impl.JmxLayoutHelper.getAttributeLayoutInformation(JmxLayoutHelper.java:67)
at com.sap.security.core.jmx.impl.JmxServer.getAttributeLayoutInformation(JmxServer.java:304)     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:324)     at
com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)     at
javax.management.StandardMBean.invoke(StandardMBean.java:286)     at
com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)     at
com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)     at
com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)     at
com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)     at
com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)     at
com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)     at
com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at
com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)     at
com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)     at
com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at
com.sap.security.core.jmx._gen.IJmxServer$Impl.getAttributeLayoutInformation(IJmxServer.java:1695)     at
com.sap.security.core.wd.jmxmodel.JmxModelCompInterface.getAttributeLayoutInformation(JmxModelCompInterface.java:485)
at
com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface.getAttributeLayoutInformation(InternalJmxModelCom
pInterface.java:441)     at
com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface$External.getAttributeLayoutInformation(InternalJm
xModelCompInterface.java:712)     at
com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.getAttributeLayoutInformation(UmeUiFactoryCompInterfa
ce.java:675)     at
com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.getAttributeLayoutInformation(InternalUme
UiFactoryCompInterface.java:519)     at
com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface$External.getAttributeLayoutInformation(In
ternalUmeUiFactoryCompInterface.java:856)     at
com.sap.security.core.wd.maintainuser.WriteableDetailInterfaceView.onPlugCopyIn(WriteableDetailInterfaceView.java:179
)     at
com.sap.security.core.wd.maintainuser.WriteableDetailInterfaceView.onPlugCreateIn(WriteableDetailInterfaceView.java:1
11)     at
com.sap.security.core.wd.maintainuser.wdp.InternalWriteableDetailInterfaceView.wdInvokeEventHandler(InternalWriteable
DetailInterfaceView.java:110)     at
com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.invokeEventHandler(DelegatingInterfaceView.java:85)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)     at
com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)     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:299)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)     at
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)     at
com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)     at
com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProx
y.java:879)     at
com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java
:77)     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1291)     at
com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)     at
com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:831)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)     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:299)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)     at
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)     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: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(ApplicationSessionMe
ssageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at
java.security.AccessController.doPrivileged(Native Method)     at
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)----
caused by
com.sap.security.core.persistence.datasource.imp.r3persistence.SapUidFormatException: Not a valid SAP user
ID: "1Z8uN8K0JUdBbS~Z1WN8". Reason: SAP user ID must contain at least 1 and at most 12 characters     at
com.sap.security.core.persistence.datasource.imp.r3persistence.Util.assertSapUidLength(Util.java:73)     at
com.sap.security.core.persistence.datasource.imp.R3Persistence.getPrivateIDPart(R3Persistence.java:2512)     at
com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.bindNewPrincipalDatabag(DataSourceBaseI
mplementation.java:340)     at
com.sap.security.core.persistence.datasource.imp.R3Persistence$Transaction.bindNewPrincipalDatabag(R3Persistence.java
:8727)     at
com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.bindNewPrincipalDatabag(PrincipalDatabagFactory
Instance.java:4640)     at
com.sap.security.core.persistence.imp.PrincipalDatabag.getIDParts(PrincipalDatabag.java:1034)     at
com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.isPrincipalDatabagAttributeModifiable(Principal
DatabagFactoryInstance.java:2331)     at
com.sap.security.core.imp.PrincipalFactory.isPrincipalAttributeModifiable(PrincipalFactory.java:255)     at
com.sap.security.core.imp.PrincipalFactory.isPrincipalAttributeModifiable(PrincipalFactory.java:215)     at
com.sap.security.core.jmx.impl.CompanyPrincipalFactory.isPrincipalAttributeCreateable(CompanyPrincipalFactory.java:24
71)     at com.sap.security.core.jmx.impl.JmxLayoutHelper.getAttributeLayoutInformation(JmxLayoutHelper.java:67)
at com.sap.security.core.jmx.impl.JmxServer.getAttributeLayoutInformation(JmxServer.java:304)     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:324)     at
com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)     at
javax.management.StandardMBean.invoke(StandardMBean.java:286)     at
com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)     at
com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)     at
com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)     at
com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)     at
com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)     at
com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)     at
com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at
com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)     at
com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)     at
com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at
com.sap.security.core.jmx._gen.IJmxServer$Impl.getAttributeLayoutInformation(IJmxServer.java:1695)     at
com.sap.security.core.wd.jmxmodel.JmxModelCompInterface.getAttributeLayoutInformation(JmxModelCompInterface.java:485)
at
com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface.getAttributeLayoutInformation(InternalJmxModelCom
pInterface.java:441)     at
com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface$External.getAttributeLayoutInformation(InternalJm
xModelCompInterface.java:712)     at
com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.getAttributeLayoutInformation(UmeUiFactoryCompInterfa
ce.java:675)     at
com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.getAttributeLayoutInformation(InternalUme
UiFactoryCompInterface.java:519)     at
com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface$External.getAttributeLayoutInformation(In
ternalUmeUiFactoryCompInterface.java:856)     at
com.sap.security.core.wd.maintainuser.WriteableDetailInterfaceView.onPlugCopyIn(WriteableDetailInterfaceView.java:179
)     at
com.sap.security.core.wd.maintainuser.WriteableDetailInterfaceView.onPlugCreateIn(WriteableDetailInterfaceView.java:1
11)     at
com.sap.security.core.wd.maintainuser.wdp.InternalWriteableDetailInterfaceView.wdInvokeEventHandler(InternalWriteable
DetailInterfaceView.java:110)     at
com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.invokeEventHandler(DelegatingInterfaceView.java:85)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)     at
com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)     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:299)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)     at
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)     at
com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)     at
com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProx
y.java:879)     at
com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java
:77)     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1291)     at
com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)     at
com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:831)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)     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:299)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)     at
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)     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: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(ApplicationSessionMe
ssageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at
java.security.AccessController.doPrivileged(Native Method)     at
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Severity : Error
Category : /System/Security/Usermanagement
Location : com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.getPrivateIDPart()
Application : sap.com/tcwddispwda
Thread : SAPEngine_Application_Thread[impl:3]_49
Datasource : 19184150:D:\usr\sap\PTD\JC01\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 000C29F20933005300000AB9000006580004245B630B0BAC
Source Name : com.sap.security.core.persistence.datasource.imp.R3PersistenceBase
Argument Objs : Not a valid SAP user ID: "1Z8uN8K0JUdBbS~Z1WN8". Reason: SAP user ID must contain at least 1 and at
most 12 characters,com.sap.security.core.persistence.datasource.PersistenceException: Not a valid SAP user ID:
"1Z8uN8K0JUdBbS~Z1WN8". Reason: SAP user ID must contain at least 1 and at most 12 characters     at
com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178
)     at com.sap.security.core.persistence.datasource.imp.R3Persistence.getPrivateIDPart(R3Persistence.java:2532)
at
com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.bindNewPrincipalDatabag(DataSourceBaseI
mplementation.java:340)     at
com.sap.security.core.persistence.datasource.imp.R3Persistence$Transaction.bindNewPrincipalDatabag(R3Persistence.java
:8727)     at
com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.bindNewPrincipalDatabag(PrincipalDatabagFactory
Instance.java:4640)     at
com.sap.security.core.persistence.imp.PrincipalDatabag.getIDParts(PrincipalDatabag.java:1034)     at
com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.isPrincipalDatabagAttributeModifiable(Principal
DatabagFactoryInstance.java:2331)     at
com.sap.security.core.imp.PrincipalFactory.isPrincipalAttributeModifiable(PrincipalFactory.java:255)     at
com.sap.security.core.imp.PrincipalFactory.isPrincipalAttributeModifiable(PrincipalFactory.java:215)     at
com.sap.security.core.jmx.impl.CompanyPrincipalFactory.isPrincipalAttributeCreateable(CompanyPrincipalFactory.java:24
71)     at com.sap.security.core.jmx.impl.JmxLayoutHelper.getAttributeLayoutInformation(JmxLayoutHelper.java:67)
at com.sap.security.core.jmx.impl.JmxServer.getAttributeLayoutInformation(JmxServer.java:304)     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:324)     at
com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)     at
javax.management.StandardMBean.invoke(StandardMBean.java:286)     at
com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)     at
com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)     at
com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)     at
com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)     at
com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)     at
com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)     at
com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at
com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)     at
com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)     at
com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at
com.sap.security.core.jmx._gen.IJmxServer$Impl.getAttributeLayoutInformation(IJmxServer.java:1695)     at
com.sap.security.core.wd.jmxmodel.JmxModelCompInterface.getAttributeLayoutInformation(JmxModelCompInterface.java:485)
at
com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface.getAttributeLayoutInformation(InternalJmxModelCom
pInterface.java:441)     at
com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface$External.getAttributeLayoutInformation(InternalJm
xModelCompInterface.java:712)     at
com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.getAttributeLayoutInformation(UmeUiFactoryCompInterfa
ce.java:675)     at
com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.getAttributeLayoutInformation(InternalUme
UiFactoryCompInterface.java:519)     at
com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface$External.getAttributeLayoutInformation(In
ternalUmeUiFactoryCompInterface.java:856)     at
com.sap.security.core.wd.maintainuser.WriteableDetailInterfaceView.onPlugCopyIn(WriteableDetailInterfaceView.java:179
)     at
com.sap.security.core.wd.maintainuser.WriteableDetailInterfaceView.onPlugCreateIn(WriteableDetailInterfaceView.java:1
11)     at
com.sap.security.core.wd.maintainuser.wdp.InternalWriteableDetailInterfaceView.wdInvokeEventHandler(InternalWriteable
DetailInterfaceView.java:110)     at
com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.invokeEventHandler(DelegatingInterfaceView.java:85)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)     at
com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)     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:299)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)     at
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)     at
com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)     at
com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProx
y.java:879)     at
com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java
:77)     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1291)     at
com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)     at
com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:831)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)     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:299)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)     at
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)     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: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(ApplicationSessionMe
ssageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at
java.security.AccessController.doPrivileged(Native Method)     at
com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)     at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)----
caused by
com.sap.security.core.persistence.datasource.imp.r3persistence.SapUidFormatException: Not a valid SAP user
ID: "1Z8uN8K0JUdBbS~Z1WN8". Reason: SAP user ID must contain at least 1 and at most 12 characters     at
com.sap.security.core.persistence.datasource.imp.r3persistence.Util.assertSapUidLength(Util.java:73)     at
com.sap.security.core.persistence.datasource.imp.R3Persistence.getPrivateIDPart(R3Persistence.java:2512)     at
com.sap.security.core.persistence.datasource.imp.DataSourceBaseImplementation.bindNewPrincipalDatabag(DataSourceBaseI
mplementation.java:340)     at
com.sap.security.core.persistence.datasource.imp.R3Persistence$Transaction.bindNewPrincipalDatabag(R3Persistence.java
:8727)     at
com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.bindNewPrincipalDatabag(PrincipalDatabagFactory
Instance.java:4640)     at
com.sap.security.core.persistence.imp.PrincipalDatabag.getIDParts(PrincipalDatabag.java:1034)     at
com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.isPrincipalDatabagAttributeModifiable(Principal
DatabagFactoryInstance.java:2331)     at
com.sap.security.core.imp.PrincipalFactory.isPrincipalAttributeModifiable(PrincipalFactory.java:255)     at
com.sap.security.core.imp.PrincipalFactory.isPrincipalAttributeModifiable(PrincipalFactory.java:215)     at
com.sap.security.core.jmx.impl.CompanyPrincipalFactory.isPrincipalAttributeCreateable(CompanyPrincipalFactory.java:24
71)     at com.sap.security.core.jmx.impl.JmxLayoutHelper.getAttributeLayoutInformation(JmxLayoutHelper.java:67)
at com.sap.security.core.jmx.impl.JmxServer.getAttributeLayoutInformation(JmxServer.java:304)     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:324)     at
com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)     at
javax.management.StandardMBean.invoke(StandardMBean.java:286)     at
com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)     at
com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)     at
com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)     at
com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)     at
com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)     at
com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)     at
com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at
com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)     at
com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)     at
com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)     at
com.sap.security.core.jmx._gen.IJmxServer$Impl.getAttributeLayoutInformation(IJmxServer.java:1695)     at
com.sap.security.core.wd.jmxmodel.JmxModelCompInterface.getAttributeLayoutInformation(JmxModelCompInterface.java:485)
at
com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface.getAttributeLayoutInformation(InternalJmxModelCom
pInterface.java:441)     at
com.sap.security.core.wd.jmxmodel.wdp.InternalJmxModelCompInterface$External.getAttributeLayoutInformation(InternalJm
xModelCompInterface.java:712)     at
com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.getAttributeLayoutInformation(UmeUiFactoryCompInterfa
ce.java:675)     at
com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.getAttributeLayoutInformation(InternalUme
UiFactoryCompInterface.java:519)     at
com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface$External.getAttributeLayoutInformation(In
ternalUmeUiFactoryCompInterface.java:856)     at
com.sap.security.core.wd.maintainuser.WriteableDetailInterfaceView.onPlugCopyIn(WriteableDetailInterfaceView.java:179
)     at
com.sap.security.core.wd.maintainuser.WriteableDetailInterfaceView.onPlugCreateIn(WriteableDetailInterfaceView.java:1
11)     at
com.sap.security.core.wd.maintainuser.wdp.InternalWriteableDetailInterfaceView.wdInvokeEventHandler(InternalWriteable
DetailInterfaceView.java:110)     at
com.sap.tc.webdynpro.progmodel.generation.DelegatingInterfaceView.invokeEventHandler(DelegatingInterfaceView.java:85)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:826)     at
com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)     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:299)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:731)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:667)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)     at
com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)     at
com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)     at
com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProx
y.java:879)     at
com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java
:77)     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1291)     at
com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)     at
com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:831)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)     at
com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)     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:299)     at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)     at
com.sap.tc.webdynpro.clientserver.session.ClientSessio

I found the solution to my own problem. My guess that the generated ID was causing problems was correct. The fix was to change the ume.logon.security_policy.
useridmaxlength to 12 instead of the default of 20.
After I did that and restarted, UME users were working properly. SAP help does describe this issue at the bottom of http://help.sap.com/saphelp_nw04/helpdata/en/b5/16c43bdd3da244a1d3372a77b5f83f/content.htm which I found after the issue had been fixed.
<rant>This is another case of a sub-optimal default value in NW2004s. Why not make it 12 to match the limitation in ABAP by default? There are way too many little things like this in the current stack.</rant>
Rob

Similar Messages

Persistence error when creating New User

Hi All,
I just installed NW2004s SP7, both the J2EE as well as the ABAP stack, with user management configured such that the users in the ABAP stack.
When I log into the portal and try to create a new user, or change existing users, I get the following error on the screen "An error occurred in the persistence; contact your system administrator".
I looked in the logs and I have the following error.
#1.5#0015F2539C5C007600000015000003080004198837026C13#1153972736062#com.sap.security.core.wd.maintainuser.MaintainUserComp#sap.com/tc~wd~dispwda#com.sap.security.core.wd.maintainuser.MaintainUserComp.public void saveModifications( )#SAP*#25222#SAP J2EE Engine JTA Transaction : [0fffffffdffffff917a001168]#labnxi_NXI_16617850#SAP*#f481f4e01d2311dbb0d30015f2539c5c#SAPEngine_Application_Thread[impl:3]_18##0#0#Error##Java###Error in the persistence
[EXCEPTION]
{0}#1#com.sap.security.core.wd.exception.UmeUiPersistenceException: The UME/ABAP user management connector is set to read-only mode and therefore rejects the creation request for user SAGARWAL
 at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.handleThrowable(UmeUiFactoryCompInterface.java:2065)
 at com.sap.security.core.wd.umeuifactory.UmeUiFactoryCompInterface.createEntity(UmeUiFactoryCompInterface.java:380)
 at com.sap.security.core.wd.umeuifactory.wdp.InternalUmeUiFactoryCompInterface.createEntity(InternalUmeUiFactoryCompInterface.java:440)
 at
Can anybody tell me how I can change the UME/ABAP user management connector so I can create users from the Portal.
Thank you for your help.
Sumit.

HI,
check <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/44/23f128dac25cf8e10000000a155369/frameset.htm">the SAP Help page</a> for details...
Hth,
Michael

Error when creating a user - IAM-3010183 : An error occurred while checking if a user already exists with the Common Name generated.

Error when creating a user - IAM-3010183 : An error occurred while checking if a user already exists with the Common Name generated.

in OIM 11g R2
Message was edited by: 2b3c0737-074f-48d0-a760-e24e3ed9a37c

Syntax error when creating a user-defined table type in SQL Server 2012

Why am I getting a syntax error when creating a user-defined table type in SQL Server 2014?
CREATE TYPE ReportsTableType AS TABLE
( reportId INT
, questionId INT
, questionOrder INT );
Results:
Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'AS'.

Hope these posts could help,
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/37a45a9a-ed8c-4655-be93-f6e6d5ef44be/getting-incorrect-syntax-while-creating-a-table-type-in-sql-server-2008-r2?forum=transactsql
Regards, Dineshkumar,
Please Mark as Answer if my post answers your question and
Vote as Helpful if it helps you

Exception - when create a new factory by Persistence class

Hey,
I need to create factory in run time because i dont know the shema names.
A new schema is allocated to the user after he register to the system.
I am working in Jboss 4.2.
I have a stateless session bean with the following method:
public void createEntityManagerFactoryWithPersistenceAPI() {
try {
Hotel h = new Hotel("Bla","Bla");
//****************** Map configuration
Map configOverrides = new HashMap();
configOverrides.put("javax.persistence.jtaDataSource", "java:/TestDS");
configOverrides.put("hibernate.hbm2ddl.auto", "create");
configOverrides.put("hibernate.connection.driver_class", "com.mysql.jdbc.Driver");
configOverrides.put("hibernate.dialect", "org.hibernate.dialect.MySQLDialect");
configOverrides.put("hibernate.default_schema", "Test");
EntityManagerFactory programmaticEmf =
Persistence.createEntityManagerFactory("Demo",configOverrides);
new InitialContext().rebind("java:/TestEMF", programmaticEmf);
}catch(Exception e){
I get an exception when i try to create the factory:
19:14:49,492 ERROR [STDERR] javax.persistence.PersistenceException: org.hibernate.HibernateException: The chosen transaction strategy requir
es access to the JTA TransactionManager
19:14:49,492 ERROR [STDERR] at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:720)
19:14:49,492 ERROR [STDERR] at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:121)
19:14:49,492 ERROR [STDERR] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:51)
19:14:49,492 ERROR [STDERR] at service.impl.HotelServiceBean.createEntityManagerFactoryWithPersistenceAPI(HotelServiceBean.java:83)
if i set to the following to the properties:
configOverrides.put("javax.persistence.transactionType", "RESOURCE_LOCAL");
the factory is created, but when i try to use it i get an exception:
18:36:54,138 ERROR [JDBCTransaction] JDBC commit failed
java.sql.SQLException: You cannot commit during a managed transaction!
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.jdbcCommit(BaseWrapperManagedConnection.java:543)
My DS:
<datasources>
<local-tx-datasource>
<jndi-name>TestDS</jndi-name>
<connection-url>jdbc:mysql://localhost:3306/</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>root</user-name>
<password>1234</password>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>



My persistence.xml file:
<persistence>
<persistence-unit name="Demo">
<jta-data-source>java:/InsiteDS</jta-data-source>
<properties>
<property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver" />
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect" />
</properties>
</persistence-unit>
</persistence>

<metadata>
<type-mapping>mySQL</type-mapping>
</metadata>
</local-tx-datasource>
</datasources>
Thank you!!!!!

Check whether you are providing the correct login credentials while importing the RFC.

Runtime Error when creating SUS user

Hi All,
I started configuring SUS demo for my client, but when i created user with role "SAP_BC_BASIS_MONITORING" and "SAP_EC_SUS_ADMIN_VENDOR",
i am getting:
Runtime Errors: DBIF_RSQL_INVALID_REQUEST
Short text: Invalid call of database interface.
Do i need to configure anything before creating SUS users with this roles? Please help me?
Regards,
Ravi
Message was edited by:
Ravi Varma Nadimpalli

Hi
Which SUS Verson are you using ? Are you using SUS on the same system, where EBP is installed ?
You can create users and assign role to respective users in SUS for creating
Bids in Bidding starting form SUS. But you must replicate users from SUS to EBP.
Then only systems will identify each other while logging.
Meanwhile, Please go thrugh the following pointers and SAP OSS Notes ->
Re: Clarifications on EBP-SUS and MM-SUS Scenario
Note 893714 - SUS30: Replication of bidding users from SUS to EBP
Related Notes
1060329 - Mandatory check of form of address during user creation SUS
895217 - SUS30: SUS not integrated with CUA currently
880735 - UME/SUS: error with administrational user creation
779658 - SRM40/SUS/BP: Error during change of employee
Note 778483 - SRM-SUS: Force a user to change password on initial logon
Note 1060329 - Mandatory check of form of address during user creation SUS
Note 946159 - SRM-SUS 4.0: Termination when users are created
Regards
- Atul

IdM: Automatically assign a privilege when create a user

Dear all,
I want automatically assign a privilege to a user, when a create this user. How I have to do this? Must I use dynamic group?
My idee is: All of our people need a account in the SAP portal, so I want to assign automatically the privilege PRIV:PORTAL:ONLY to the user.
Best regards,
Hans

Lot of options depending your requirements..
Dynamic group is one option but it requires small configuration effort.
If it's all users, maybe then an add event task for MX_PERSON where you grant the privilege? Takes 5 minutes to do.
Are there any exceptions? Do you have also non-dialog users in your IdM?
Any requirements for deprovsioning?
Where do you get the users? If it's SAP HCM-integration case and no users are created in the UI, then add the privilege in the job that moves the identities from staging Id Store to your master Id Store.
regards, Tero

JCO$Exception when creating RFC model

Hi all,
I'm getting this fatal error when creating an RFC model in Web Dynpro for Java (connecting to a BW system):
com.sap.mw.JCO$Exception: Missing R3NAME=... or ASHOST=... in connect_param in RfcOpenEx
I have absolutely no clue what's going wrong...
The RFC model gets created, but when running the application it doesn't work...
Any help appreciated!
Jeroen

Raj,
Thanks for your reply.
I had already solved the problem... After a long time I found out it was due to the language: when creating an RFC model one should use the language of SLD.
kind regards,
Jeroen

Exception when creating instance of a class with native method by JNI

I am trying to use JNI - I want to have a Java class Foo have a
method, that is a native C function.
I follow the Sun's tutorial
http://java.sun.com/developer/onlineTraining/Programming/JDCBook/jnie...
exactly, and everything compiles fine, and I have compiled my C .dll
as well (on Win XP). So I am ready to run - ...
Now when I finally try to run the Java application, it throws this
exception when it tries to create the Foo instance:
at Foo.<init>(Foo.java:11)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:
513)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at sun.applet.AppletPanel.createApplet(AppletPanel.java:786)
at sun.applet.AppletPanel.runLoader(AppletPanel.java:715)
at sun.applet.AppletPanel.run(AppletPanel.java:369)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.security.AccessControlException: access denied
(java.lang.Runtim
ePermission loadLibrary.Foo)
Why would this be so??? Thank you for your insights

Mark_Galeck wrote:
I am trying to use JNI - I want to have a Java class Foo have a
method, that is a native C function.
I follow the Sun's tutorial
http://java.sun.com/developer/onlineTraining/Programming/JDCBook/jnie...
exactlyNot quite exactly. Yours is an applet, theirs is an application.
Applets are not allowed many things that applications can do.
Among them, loading native libraries.

How to avoid shut down BPELPM Server when creating a user?

Hi,
How to avoid shut down BPELPM Server when creating a JAZN user and after doing changes to user-properties.xml?
Thanks,
Jorge

this configuration is only supported on a midtier - there is a work around for a standalone install, nevertheless I would not recommend this for production ..
if this is NOT a production enviroment - I can try to get you the information .
/clemens

Adding object classes when creating ldap user in workflow

I'm creating ldap users in a workflow and when I assign the object classes in the workflow I get an object class violation. It seems that when I call check in view and when my break point stops in Update User the default object classes on the resource have been removed from the user.accounts[LDAP].objectClass attribute which I just set. Not sure what's going on here. Is there another way to assign more than just the default object classes to a new ldap user through the workflow? Thanks in advance.

Multiple things I can think of
1) put all the object classes you may be expecting with the user account in the resource configuration panel. LDAP is smart enough to assign the related object classes to the object based on the attributes assigned to the user.
2) Check if you have the object class in the schema of LDAP.

TS2529 there is no none option on payment option even when creating new user id

I was attemting to download free apps on iphone but itunes wouldnt let me because of past due balance of 6.00 dollars. Unfortunately my bank account is overdrawn right now and have no valid payment options. I tried to created to USER ID and password, and there is no "NONE" option when asking for paymnet method. All im trying to do is download free apps. Please help?!?

Hi brian,
You have to download the free app first, then create the new ID:
http://support.apple.com/kb/HT2534?viewlocale=en_US&locale=en_US
Cheers,
GB

Is there any difference between these cluster images when creating a user event?

I'm sure you experts will know instantly what I'm doing wrong.
I am trying to create a user message for TestStand communication in the LabVIEW UI (based on the simple example OI that comes with TestStand)
Perhaps it's just cosmetic but the trouble is I can't get the image of my cluster constant to look the same as the one in the example.
I'm right clicking on the 'Create User Event' icon on the User Event Data Type connection and selecting Cluster - Cluster Constant, then adding a numeric constant to it.
You can see the result here. The top one is the good one from the example, and the bottom one is my attempt - but I just can't get it.
I'd appreciate your thoughts (I know the event number can't be the same - but I made it the same for the comparison). I have LabView 8.6.1.
Thanks,
Ronnie
TestStand 4.2.1, LabVIEW 2009, LabWindows/CVI 2009
Solved!
Go to Solution.

Use the color tool and right click on the lable of the numeric. I guess you will see that the Background Color of the one is black, of the other is white.
But this is really just cosmetic's of the code.
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

Error When Creating New User in UME - GRC 5.3, but works via Backend

All,
When I try to create a new user in the User Management (UME), I get a very generic error message: "An error occurred; contact your system administrator". However, if I create the new user in the ABAP - backend first then he/she will show up in the UME and I can add Java roles to the user in the UME and he/she can work without issues. Therefore: do you always have to create GRC administrator users in the backend first or should it work when first creating in the UME as well?
Thanks, Joerg

Hi,
Is your system a dual stack (ABAP+JAVA)? In that case the ABAP stack will be the master. You can check if it's an ABAP data source if you go to UME >> Configuration >> Data Sources
Regards,
Vit
More info in thread: How to create Roles in UME (ABAP+JAVA stack)
Edited by: Vit Vesely on Apr 10, 2010 9:28 PM

How to avoid duplicate DN exception when creating Active Directory Account

I am using OIM 9.1.0.2 to provision Active Directory accounts.
I run into issues when the DN of the user to be created already exists and I would like to know if anyone has some logic I can use to generate a different DN for new user by adding a number or something like that to the DN
Here is an example.
User 1 exists already and their DN: cn=john smith, cn=users, dc=company,dc=org
New user joins the company and his name is also john smith and he has no middle name: so system attempts to create his account as cn=john smith, cn=users, dc=company,dc=org
how can I accomplish this by making the account say cn=john smith_1, cn=users, dc=company,dc=org

855640 wrote:
I run into issues when the DN of the user to be created already exists and I would like to know if anyone has some logic I can use to generate a different DN for new user by adding a number or something like that to the DN
There are two different questions:
1. How to generate a sequence of candidates for the name attribute
2. How to check if a record with the given name candidate already exists in the Active Directory, and hence try the next candidate from the sequence.
The answer for the first part is usually defined by the policy existing in your organization, in the simplest case you can append sequential integer numbers to the end of the original name.
The answer for the second question is not so simple if you use are provisioning with MSAD connector.
There are two places you can put the check:
-- in the pre-populate adapter for the UD_ADUSER_COMMONNAME field
-- in the adpADCSCREATEUSER event handler, which is responsible for new AD user record creation.
Both cases need some coding, since you have to obtain the AD connection and search AD for matching records.
Pros & cons
Placing check code in the pre-populate adapter:
Pros:
the result is visible in the form, administrator can change the pre-calculated value if he wishes
Cons:
you need to have all access to connection parameters, and establish one extra connection
this is not the way OIM is supposed to work :-(
Placing check code in the AD user creation task:
Pros:
you have all access to connection parameters, and open a connection here anyway
Cons:
the result is not present in the form, so no way for manual interaction by administrator here
BTW: this problem is not only related to DN generation, some other AD attributes (e.g. sAMAccountName, mailNickName, userPrincipalName, mail) should be unique in the AD domain scope.
Edited by: madhatter on Sep 7, 2012 12:02 AM

Persistence exception when creating UME users

Similar Messages

Maybe you are looking for