Problem in AD Integration with WLS
Hello,
I have successfully integrated Active directory with weblogic server. And i am able to see user list in security Realm -> myrealm -> Users and Groups. I am also able to login to webcenter spaces and also to content server.
In my active directory there are different OUs. so i have created different Authentication Providers in Security Realms >myrealm >Providers depending upon the OUs. I have set control flag of all the providers to SUFFICIENT*. Even same for DefaultAuthenticator. And my sequence is
DefaultAunthenticator*
ADAuthenticatorOU1*
ADAuthenticatorOU2*
I am able to login with users from all the three providers.
But whenever i tried to create a group space in webcenter spaces or even any other activity with AD users it throws error like User: XXXXXXXXX not found in identity store.
When i tried to login using DefaultAuthenticator(Weblogic) I was able to create group spaces but not able to search users from AD. However i was able to search users from DefaultAutherticator.
I have tried reordering the sequence and also changing the control Flag but it didn't work.
What should be the sequence and what should be the control flag status ?_
Please Help.
Thanks
Edited by: Navin K on Jan 20, 2011 11:50 AM
Thanks for the reply.
In my case both Webcenter spaces and UCM are part of the same domain. But still i'm getting the error.
I'm able to login usnig AD user, Do i still need to configure JPS provider for webcenter spaces? Please help me what changes to be made to be able to search users while adding them to any newly created group space.
Please help.
Thanks
Similar Messages
-
Problem about BIEE Integration with LDAP
Hello,
I have a problem in OBIEE11.1.1.6
I do BI EE 11g Security Integration with OPENLDAP follow below link,
http://www.rittmanmead.com/2010/11/oracle-bi-ee-11g-security-integration-with-microsoft-active-directory/
It works well using user that store in OPENLDAP ,
now I want to realize this function,
that user roles store in external db table,then get roles by init block,
but I faced a problem, If I use session system variable 'WEBGROUPS' to get some value in db,when user login BIEE,it can get values of 'WEBGROUPS'
but If I use session system variable 'ROLES' ,when user login BIEE,it can't get values of 'ROLES' that store in db,
the value will always show 'BIConsume;Authenticated User',It is default value in OBIEE11.1.1.6,
so I doubt way I can't user variable 'ROLES' to get value???
init block lik follow,
SQL: select T.att1,T.att2 FROM USER_ACCESS T
T.att1 is for variable 'WEBGROUPS'
T.att2 is for variable 'ROLES'
the value of 'WEBGROUPS' is correct.
but 'ROLES' not got the values that stored in db.
anyone know???
thank you in advance!VITAS wrote:
that user roles store in external db table,then get roles by init block,
but I faced a problem, If I use session system variable 'WEBGROUPS' to get some value in db,when user login BIEE,it can get values of 'WEBGROUPS'
but If I use session system variable 'ROLES' ,when user login BIEE,it can't get values of 'ROLES' that store in db,
the value will always show 'BIConsume;Authenticated User',It is default value in OBIEE11.1.1.6,
so I doubt way I can't user variable 'ROLES' to get value???
init block lik follow,
Go to Enterprise Manager and create the ROLES named the same as the one you named in DB values. Now you should see them magically appear when you click on My account > Roles and Catalog Groups. :)
SQL: select T.att1,T.att2 FROM USER_ACCESS T
T.att1 is for variable 'WEBGROUPS'
T.att2 is for variable 'ROLES'
the value of 'WEBGROUPS' is correct.
but 'ROLES' not got the values that stored in db.Hope you did you enable Row Wise Init here ?
Let us know. Mark if helps.!
Thanks,
SVS -
A problem about Portal integration with R/3 ?
Hi everyone :
We want implement that many Portal users(vendor user) mapping one R/3 user(vendor user),and the the Portal user(vendor user)could query R/3 report via Portal ,and everyone vendor user can query his data only,they can't query the other vendor's data.
Of course ,we must do some develop.
I think this problem is general, and most of Portal project would meet this problem.
Is it possible ?
Is there somebody had solved this problem ?
Any discuss is welcome!
Best Regards,
Jianguo ChenHi Chen,
If u r going to call RFM ,u can pass the portal userid as a parameter in the function call and maintain a ztable on R/3 side having fields Portal user id and Vendor id.
Based on that u can get the vendor id and filter the report data accordingly ,u may also display the Vendor id on the portal iview by passing the same from the R/3 side. I think this is possible u may try this out.
Best Regards
Anand -
Problem in MI integration with RFID
Hi All,
We are trying to integrate MI with RFID. For that we are using
WorkAboutPRO, PSION TEKLOGIX PDA with RFID reader.
on that we have installed-
CrEme 3.27a
MobileEngine jsp 2.5
DB2E 8.24
prifpsiwp_wm50_xsl_crm Driver Addon
connector_wm50_xsl_crm Connector
and our simple MI application which reads all tags in range.
When we are executing it in PC using Peripheral i/o emulator RFID2 its working fine.
But when we are trying to execute it on the RFID device its showing an exception as follows-
Error: 500
Location: /MIAPPLICATION/startInternal Servlet Error:
java.lang.NullPointerException
at miProjectPackage.MiProjectClass.readTag()
at miProjectPackage.MiProjectClass.doHandleEvent()
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe()
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet()
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doPost()
at javax.servlet.http.HttpServlet.service()
at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service()
at javax.servlet.http.HttpServlet.service()
at org.apache.tomcat.core.ServletWrapper.doService()
at org.apache.tomcat.core.Handler.service()
at org.apache.tomcat.core.ServletWrapper.service()
at org.apache.tomcat.core.ContextManager.internalService()
at org.apache.tomcat.core.ContextManager.service()
at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection()
at org.apache.tomcat.service.TcpWorkerThread.runIt()
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run()
at java.lang.Thread.run()
Kindly help.
Thanks & Regards,
SahidurThanks for the reply.
In my case both Webcenter spaces and UCM are part of the same domain. But still i'm getting the error.
I'm able to login usnig AD user, Do i still need to configure JPS provider for webcenter spaces? Please help me what changes to be made to be able to search users while adding them to any newly created group space.
Please help.
Thanks -
Problems installing Axis with WLS 8.1
I'm having problems installing Apache Axis with WLS 8.1.
I'm totally new to WLS, so this may be at the heart of the problem.
I install Axis as per the installation instructions.
These are the steps I followed:
1. Installed the axis directory to
C:\bea\weblogic81\samples\domains\examples\applications\axis2. Added xml-apis.jar and xercesImpl.jar to the AXISCLASSPATH ( the complete AXISCLASSPATH is
C:\axis-1_2RC2\lib\wsdl4j.jar;C:\axis-1_2RC2\lib\axis-ant.jar;C:\axis-1_2RC2\lib\commons-discovery.jar;C:\axis-1_2RC2\lib\commons-logging.jar;C:\axis-1_2RC2\lib\jaxrpc.jar;C:\axis-1_2RC2\lib\log4j.properties;C:\axis-1_2RC2\lib\log4j-1.2.8.jar;C:\axis-1_2RC2\lib\saaj.jar;C:\axis-1_2RC2\lib\axis.jar;C:\javasoft\javamail-1.3.2\mail.jar;C:\javasoft\javamail-1.3.2\lib\smtp.jar;C:\javasoft\javamail-1.3.2\lib\mailapi.jar;C:\javasoft\javamail-1.3.2\lib\pop3.jar;C:\javasoft\javamail-1.3.2\lib\imap.jar;C:\javasoft\jaf-1.0.2\activation.jar;C:\javasoft\Xerces\xerces-2_5_0\xercesImpl.jar;C:\javasoft\Xerces\xerces-2_5_0\xml-apis.jar)3.Added weblogic.xml file to C:\bea\weblogic81\samples\domains\examples\applications\axis\WEB-INF\weblogic.xmlas per instructions with <prefer-web-inf-classes>true</prefer-web-inf-classes> 4. Started the examples server.
5. I then tried to validate the installation as per intructions using <a href="http://localhost:7001/axis"></a>
Everything looks OK with the Axis start page displayed.
6. I then tried happyaxis.jsp . All needed components are present with saaj.jar being picked up from :
Found SAAJ API (javax.xml.soap.SOAPMessage) at C:\bea\weblogic81\samples\domains\examples\examplesServer\.wlnotdelete\extract\examplesServer__appsdir_axis_dir_axis\jarfiles\WEB-INF\lib\saaj.jar7. I'm missing optional component xmlsec.jar
8. Now the trouble starts!!!
pretty much anything I try now comes back with:
AXIS error
Sorry, something seems to have gone wrong... here are the details:
Exception - java.lang.NullPointerExceptionI get this if I try:
<a href="http://localhost:8080/axis/services/Version?method=getVersion"></a>
or
<a href="http://localhost:7001/axis/services/AdminService?wsdl"></a>
or
<a href="http://localhost:7001/axis/services/Version?wsdl"></a>
So, what's going wrong? I cant think what to do next. Please help! I need this to work fairly urgently.
Nigel
PS. here's the NP exception in detail
java.lang.NullPointerException
at weblogic.xml.jaxp.ChainingEntityResolver.popEntityResolver(ChainingEn
tityResolver.java:61)
at weblogic.xml.jaxp.RegistryDocumentBuilder.setEntityResolver(RegistryD
ocumentBuilder.java:168)
at org.apache.axis.utils.XMLUtils.releaseDocumentBuilder(XMLUtils.java:2
35)
at org.apache.axis.utils.XMLUtils.newDocument(XMLUtils.java:312)
at org.apache.axis.utils.XMLUtils.StringToElement(XMLUtils.java:485)
at org.apache.axis.AxisFault.addFaultDetail(AxisFault.java:654)
at org.apache.axis.AxisFault.addHostname(AxisFault.java:888)
at org.apache.axis.AxisFault.addHostnameIfNeeded(AxisFault.java:877)
at org.apache.axis.AxisFault.initFromException(AxisFault.java:280)
at org.apache.axis.AxisFault.<init>(AxisFault.java:181)
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.server.AxisServer.generateWSDL(AxisServer.java:487)
at org.apache.axis.transport.http.QSWSDLHandler.invoke(QSWSDLHandler.jav
a:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.axis.transport.http.AxisServlet.processQuery(AxisServlet.j
ava:1132)
at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:233
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBas
e.java:301)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1006)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:419)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:315)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6718)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3764)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2644)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)I'm doing exactly the same thing (adding the xerces jars to my web-inf/lib), but happyaxis.jsp is saying the jar I'm using is invalid as follows:
Error: Invalid version of SAAJ API found in D:\bea\weblogic81\server\lib\webservices.jar. Make sure that Axis' saaj.jar precedes D:\bea\weblogic81\server\lib\webservices.jar in CLASSPATH.
Axis will not work.
Maybe this worked in a previous release/SP? I'm using 8.1SP3. I've read some other post saying you cannot override stuff in the weblogic.jar, so I've tried to add the jars to the pre_classpath, which resolves the issue but I get a soap fault related to this thread. Any ideas?
Thanks,
Lou
My weblogic.xml looks as follows:
<weblogic-web-app>
<jsp-descriptor>
<!-- Comment the jspServlet param out to go back to weblogic's jspc -->
<jsp-param>
<param-name>jspServlet</param-name>
<param-value>weblogic.servlet.WlwJSPServlet</param-value>
</jsp-param>
<jsp-param>
<param-name>debug</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
<url-match-map>
weblogic.servlet.utils.SimpleApacheURLMatchMap
</url-match-map>
</weblogic-web-app> -
Hi all,
How to integrate cFolder with Microsoft Windows File Explorer Practically.
I used transactions CFI01 , CFE01 for Back-end Integration since i don't know how to create a cProject and cFolder i cant proceed can anyone help me to come out of this problem.
Thanks in advance.Hi Shounak
As I have a problem regarding the integration with windows explorer and C folders, I have taken this chance to enter this conversation.
First of all I have done the acticities that you have stated:
1. Activate the SOAP handler in the SAP Web Application Server, by activating the
/sap/bc/soap/rfc node in transaction SICF.
2. Execute the Specify URLs for Windows File Explorer Integration activity in Customizing
for Collaboration Projects.
The activity is also relevant to cFolders.
3. Assign the users who are to work with the Windows File Explorer the appropriate RFC
authorization in the user profile.
Function group CPRO_API
Authorization object S_RFC
4. Activate the function in your personal settings as the user and execute the installation
file:
The only thing, that I haven't been able to do os to assign the function group CPRO_API. I have asked my authorization contacts, but they couldn't help me.
Can you tell me how to do this?
Furthermore I have a problem when trying to upload a document from my windows explorer. Even though it says that the upload has been succesfull, no update is happening when I look in the C folders application.
Thanks for your help in advance
Maria -
Problem in submit button on adobe form integrated with web dynpro
Hello,
I'm facing prob in triggering web dynpro event onSubmit for Interactive form.
I've created a submit button from web dynpro activex pallete on adobe form (integrated with web dynpro) to send the form as email.
Then in the web dynpro view where this form is embedded i have created an action against onSubmit event and called a method within this.
However, on clicking Submit button this event is not getting triggered.
Please let me know what is lacking in this process?
Thanks.Hi,
I am also facing the same problem. i have developed a simple scenario under which user have to input his/her details and on submit button it will be updated to database.
I have tried the above solution but after adopting this solution all the editable fields become non-editable.
so the above solution is not working for me could you help me out.
I think ... try this....
When you create the Adobe Form from WebDynpro, you need to follow one step in SFP Transaction or inSE80 transaction. Open the Adobe Form in any one the transaction and now in SAP menu bar "Utilities" in that you will find the "INSERT THE WEBDYNPRO SCRIPT" just click on that one. Then you will see a new Script Object is being created with the name "ContainerFoundation_JS" under the "Variables" in the Heirarchy of the Object Pallete of the Adobe Form.
This step is mandatory to use the SUBMIT Button of the "WebDynpro Native", to trigger the OnSubmit event of the WebDynpro.
Thanks
Edited by: shailendra2sap on Mar 6, 2009 12:24 PM -
ConnectionPool problems with WLS 7.0 and Oracle 9.2
Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
application on the productive system (and only there) we constantly encounter
a whole set of SQLExceptions which have all in common that the Connection from
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSet
- Connection has already been closed
- Closed Statement
- Transaction is no longer active - status committing
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()
There are no special Statements which create these errors. They are spread at
random across practically every query the application creates, and the same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSets are
closed immediately after use. As an example, I attached a code snippet and a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrent usern,
since in the approval tests on an almost identical test system these errors never
occurred.
I also followed the advice from Oracle and installed the latest Oracle JDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in the application
classpath (via a reference in the Manifest file of the application jar), not in
the system classpath? There has never been a problem with that, but in a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script creates for the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath? If
it is possible, why is it necessary?
Best regards,
Andreas Zehrt
[CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]Andreas Zehrt wrote:
Hi Joe,
Your hint that there is a threading problem was right:
On further investigation of the code I found out that the class that passes the
Connection to the DAO not only stores it as a member at some point (which is not
a good idea anyway) but is also a singleton - then, of course, it's no surprise
that the Connection gets invalid in a incalculable way when concurrent threads
share it.
The singleton instantiation was not so obvious because the way of instantiation
is controlled by a configuration parameter that can be overridden at different
levels.
I changed it and the productive logfiles indicate that the SQLExceptions related
to that class have disappeared.I am happy to have helped.
So, thanks a lot for the advice.
But I am still wondering why this code has worked for so long a time with WLS
5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
it was multi-user environment.Mo idea.
I still believe that there is a difference between WLS 5.1 and 7.0 in the way
it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
a little more explicit about those changes and possible version incompatabilities
beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
effect in this case, I will certainly do what I can to see that our documentation
is explicit about changes.
Joe
Best regards, Andreas
Joe Weinstein <[email protected]> wrote:
Hi Andreas.
Andreas Zehrt wrote:
Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
application on the productive system (and only there) we constantlyencounter
a whole set of SQLExceptions which have all in common that the Connectionfrom
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSetThat is typically if the statement that created it is either re-executed
or closed.
- Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
would show
where it was originally closed.
- Closed Statementsame as above.
- Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
datasource,
and then later trying to use it after the transaction which it was associated
with,
is finished.
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
There are no special Statements which create these errors. They arespread at
random across practically every query the application creates, andthe same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSetsare
closed immediately after use. As an example, I attached a code snippetand a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrentusern,
since in the approval tests on an almost identical test system theseerrors never
occurred.
I also followed the advice from Oracle and installed the latest OracleJDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in theapplication
classpath (via a reference in the Manifest file of the applicationjar), not in
the system classpath? There has never been a problem with that, butin a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script createsfor the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath?If
it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
We also ship
an oracle thin driver, which becomes obsolete soon...
I am concerned that your code creates pool connections to be used later.
The problems
can arise if more than one thread ever gets the same connection, or if
the connection
is used in the same thread, spanning transactions. It does also seem
that there may
be a threading issue, because if two threads each call the code to create
a connection,
and two connections are made, but one over-writes the other, the two
threads can
end up using the same connection, and closing it. The over-written one
never gets closed,
resulting in that leak message you got...
Joe
The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
several classes in the business layer, but not used, until the DAOtakes it to make the query.
So, the Connection is closed where it was opened, not in the DAO class.
public class ConcernDAOImpl extends BaseDAO {
public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
throws DataAccessException, ConstraintException, ComaParseException{>
sqlMessage.append(")");
String sqlStmt = sqlMessage.toString();
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
pstmt = conn.prepareStatement(sqlStmt);
rs = pstmt.executeQuery();
while (rs != null && rs.next()) {
final Concern concern =
new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
return concerns;
} catch (SQLException sqle) {
// Wrapps real SQL exception
String[] message = new String[]{sqle.getMessage(), sqlStmt};
throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
sqle);
} finally {
closeAll(rs, pstmt);
_logger.exitDebug(method);
Here, the Connection is acquired and finally closed
public class ComaServiceProviderClassicImpl {
public void updateComplaint(
final Request updateRequest,
final ResponseSingleElement response,
final Principal principal)
throws SystemException {
try {
logger.info("updateComplaint", "store incident");
// store the incident in the database
incidentManager.storeIncident(getConnection(), updateIncident);
// reload the incident from Cache and / or the databaseto get the ContactReferences.
Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
getConnection(), updateIncident.getOID());
} catch (RemoteException rex) {
// remote exceptions
rollbackIfNecessary();
CoreUtils.unwrapRemoteException(rex, logger);
} catch (SystemException e) {
// all other exceptions --> rollback if necessary and rethrow
rollbackIfNecessary();
throw e;
} finally {
removeConnection();
logger.exitDebug("updateComplaint");
This is the resulting StackTrace:
sql exception: [Closed Statement: next] - sql statement: [select *
at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
was detected. A Connection leak occurs when a connection obtained from
the pool was not closed explicitly by calling close() and then was disposed
by the garbage collector and returned to the connection pool. The following
stack trace at create shows where the leaked connection was created.
Stack trace at connection create:
at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210) -
MeetingPlace Video Integration with 3515MCU problem
Hi,
I am trying to setup MeetingPlace Video Integration with a Cisco 3515 MCU and cannot get it to work. The eventlog for MeetingPlace Gateway is giving me errors about the initialization problems. A couple of such errors are:
MPAgent (0x0150) Warning: Conference technology provider initialization failed (0x80040201). err=1
MPVidSvc MPVideo 11:05:52-> CMcuController::processCmdRegAuthorize() Register as administrator failed. UNregistering....
MPVidSvc MPVideo 11:06:02-> CMcuController::uninitialize() Uninitializing CMcuController.......
Both MeetingPlace and MCU conferencing are working as they should, but I can't get the Video Integration working. From what I can tell by these messages, MeetingPlace cannot talk to the MCU to administer conferences. I have setup and configured a user on the MCU for MeetingPlace to use.
Has anyone got MeetingPlace working with a 3515 MCU?
Thanks,
Richard.Richard,
I'm having the same problem but with MCU 3540. This problem begin occur after I change the service number 70. My scenario is 2 sites. Each site have 1 cluster?s CCM, 1 MCU?s 3540 and the main site I have 1 MP system with 1 MP IP gateway and web conference in the same server. What the version of MP and MCU you are using ? I'm using MP V 5.3.333.0 and MCU V 4.2.10. -
Integration with Websphere 5.0 (EJB 2.0) problems
Hello all,
Although a bit new to JDO, I have been trying to integrate Kodo 2.4 with
Websphere 5.0 (using EJB 2.0).
I have been basically binding a PersistenceManagerFactory into JNDI via
start-up servlet, however got the exception bellow when I tried to create
PersistenceManagerFactory (in setSessionContext of the EJB).
<i>JDOFatalInternalException: Could not perform automatic lookup of EJB
container's javax.transaction.TransactionManager implementation. Please ensure
that you are running the application from within an <b>EJB 1.1</b> compliant
EJB container, and then set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties property to the appropriate
value to obtain the TransactionManager.</i>
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with WSAD
5.0?
Thank you,
PetrPetr-
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?Yes, we do have reports of people using Kodo successfully from within
Websphere. However, it should be noted that it is not as rigorously
tested internally at SolarMetric as some other application servers (E.g.,
JBoss and WebLogic). In short, integration is known to work, but it
might be a little more rough around the edges than for other application
servers (as shown in our misspelling of Websphere's TransactionManager
implementation name).
How do I tell Kodo to use existing Datasource managed by app server?You can have Kodo use a named DataSource by specifying the
javax.jdo.option.ConnectionFactoryName property (see
http://www.solarmetric.com/docs/2.4.0/docs/manual.html#javax.jdo.option.ConnectionFactoryName).
This is often more appropriate for applications server usage, since it
allows you to configure pooling and other information from within the
application server's centralized configuration.
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snetWhat kind of driver is COM.ibm.db2.jdbc.app.DB2Driver? The DB2
configuration we use for testing with IBM's drivers is:
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.net.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2://SERVER_NAME/DATABASE_NAME
They shouldn't behave differently (I am guessing that the app driver is
a type 2 driver or something), but it might be worth a shot to try using
the net driver. If this fixes the problem, please let us know, because
it will indicate that Kodo has a deficiency with one of IBM's drivers
that we should look into resolving.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.The binding code looks fine, and you are obviously able to retrive the
PM and start persistence operations. Note that you should also be able
to deploy Kodo as a Resource Adapter (which allows Kodo configuration
through the centralized Websphere configuration interface). However, I
doubt this is part of the issue.
So, in short, I recommend trying the following things:
1. Using the ConnectionFactoryName to use the DataSource defined for the
appserver, on the off chance this will fix it.
2. Using the net driver instead of the app driver.
3. Seeing if it will work with javax.jdo.option.Optimistic set to false
If none of these work, please let us know, and we will continue to
investigate other possible solutions.
In article <[email protected]>, Petr Bulanek wrote:
Hello Marc,
Very good guess. Pretty much the same code worked well without App server.
In that case, there obviously was no magic related to
TransactionManagerFactory initialization (see bellow).
Is the integration with Websphere 5.0 application server officially
supported? Has anobody (that you know of) done it successfully yet?
How do I tell Kodo to use existing Datasource managed by app server?
Here is the basic configuration (URL, class, etc):
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory
javax.jdo.option.ConnectionDriverName=COM.ibm.db2.jdbc.app.DB2Driver
javax.jdo.option.ConnectionURL=jdbc:db2:snet
javax.jdo.option.Optimistic=true
javax.jdo.option.RetainValues=true
javax.jdo.option.NontransactionalRead=true
We use DB2 Version 7.2/Version 7.1 FixPak 3 for Windows, in case it helps.
Since I have been trying to integrate with App server, this is the
initialization code that I use to bind PersistenceManagerFactory to JNDI.
You may find some funny stuff there.
The new EESimpleConfiguration(true) construct seems to (by default) read
the kodo.properties file that is part of the project.
EEConfiguration conf = new EESimpleConfiguration(true);
conf.setManagedRuntimeProperties(\"TransactionManagerMethod=com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\");
conf.setManagedRuntimeClass(\"com.solarmetric.kodo.ee.InvocationManagedRuntime\");
EEPersistenceManagerFactory pmf =
new EEPersistenceManagerFactory(conf);
InitialContext ic = new InitialContext();
ic.rebind(\"KodoPMF\", pmf);
Thank you,
Petr
Marc Prud\'hommeaux wrote:
Petr-
It looks like DB2 doesn\'t like our attempt to close the connection
without a rollback or commit. This is odd, since we have never
seen this happen in our stand-alone DB2 tests. Can you let us know
the connection details (driver, connectionURL, etc)?
In the meantime, one possible workaround may be to turn off
optimistic transactions (since this will cause the PM to
only use a single Connection); can you try to specify:
javax.jdo.option.Optimistic=false
Also, have you tried to run this code in a non-managed environment
(e.g., outside the application server)? I would be interested
to know if it is related to running within an appserver.
In article <[email protected]>, Petr Bulanek wrote:
Hi Abe,
Thank you for a speedo reply. You guys really are on the ball!!!
As you suggested, the
\\\'com.ibm.ejs.jts.jta.TransactionManagerFactory.getTransactionManager\\\'
did the job (for others, please note that the proper package name should
contain \\\'jts.jta\\\', not \\\'jts.jts\\\').
Unfortunately, I got another problem. When running a method containing
query (code bellow),
I get SQLException complaining about \\\'Invalid transaction state\\\'.
The method that executes the query is a stateless transactional Session
bean.
Thank you for your help,
Petr
--------------------------- DB2 - transaction state description
CLI0116E Invalid transaction state.
Explanation: There was a transaction in progress when SQLDisconnect was
called.
User Response: Call SQLTransact before calling SQLDisconnect.
--------------------------- Exception ------------------------------------
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] preparing statement <369367952>: SELECT DISTINCT
PARENTX.JDOCLASSX FROM PARENTX
[2/01/03 16:34:19:050 EST] 563ddb8a SQL I
com.solarmetric.kodo.impl.jdbc.SQL [ C:336042896; T:1446894474;
D:118283149 ] executing statement <369367952>: [reused=1;params={}]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close:
com.solarmetric.datasource.PoolConnection@14079b90[[requests=6;size=6;max=70;hits=0;created=6;redundant=0;overflow=0;new=6;leaked=0;unavailable=0]]
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC I
com.solarmetric.kodo.impl.jdbc.JDBC [ C:336042896; T:1446894474;
D:118283149 ] close connection
[2/01/03 16:34:19:061 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC [ C:null; T:1446894474; D:118283149 ]
exception when closing connection
[2/01/03 16:34:19:541 EST] 563ddb8a JDBC W
com.solarmetric.kodo.impl.jdbc.JDBC TRAS0014I: The following exception
was logged COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0116E
Invalid transaction state. SQLSTATE=25000
atcom.solarmetric.datasource.ConnectionWrapper.close(ConnectionWrapper.java:243)
atcom.solarmetric.datasource.DataSourceImpl$AbstractPool.close(DataSourceImpl.java:690)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:373)
atcom.solarmetric.datasource.DataSourceImpl.close(DataSourceImpl.java:347)
at com.solarmetric.datasource.PoolConnection.close(PoolConnection.java:70)
atcom.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.close(SQLExecutionManagerImpl.java:885)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.release(JDBCStoreManager.java:654)
atcom.solarmetric.kodo.impl.jdbc.ormapping.SubclassProviderImpl.getSubclasses(SubclassProviderImpl.java:274)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.addSubclassConditions(ClassMapping.java:1239)
atcom.solarmetric.kodo.impl.jdbc.ormapping.ClassMapping.selectPrimaryMappings(ClassMapping.java:1218)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.executeQuery(JDBCStoreManager.java:717)
atcom.solarmetric.kodo.impl.jdbc.runtime.JDBCQuery.executeQuery(JDBCQuery.java:92)
at com.solarmetric.kodo.query.QueryImpl.executeWithMap(QueryImpl.java:792)
atcom.solarmetric.kodo.query.QueryImpl.executeWithArray(QueryImpl.java:668)
at com.solarmetric.kodo.query.QueryImpl.execute(QueryImpl.java:609)
at com.testkodo.ejb.ControllerBean.observeHumans(ControllerBean.java:66)
--------------------------- Failing code sample
try {
PersistenceManager pm = factory.getPersistenceManager();
Extent ex = pm.getExtent(Parent.class, false);
Query q = pm.newQuery(ex, \\\"name==parName\\\");
q.declareParameters(\\\"String parName\\\");
Collection col = (Collection) q.execute(\\\"James\\\");
Iterator iter = col.iterator();
Parent pp;
Collection ch;
while (iter.hasNext()) {
pp = (Parent) iter.next();
System.out.println(pp);
ch = pp.getChildren();
Iterator it= ch.iterator();
while (it.hasNext()) {
System.out.println(it.next());
q.closeAll();
pm.close();
} catch (Exception e) {
System.out.println(e);
throw new EJBException(e);
Abe White wrote:
The reference to EJB 1.1 actually scared me a bit. Does this imply that
Kodo (2.4) does not support J2EE 1.3?
EJB 2.0 is also supported. Sorry for the confusing error message.
Would you know how to set the
com.solarmetric.kodo.ee.ManagedRuntimeProperties to make it work with
WSAD
5.0?
Try these settings:
com.solarmetric.kodo.ee.ManagedRuntimeClass=\\\\
com.solarmetric.kodo.ee.InvocationManagedRuntime
com.solarmetric.kodo.ee.ManagedRuntimeProperties=\\\\
TransactionManagerMethod=\\\\
com.ibm.ejs.jts.jts.TransactionManagerFactory.getTransactionManager
Marc Prud\'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com -
The problem with forecast reports in SCOM 2012 after integration with VMM 2012
Hello.
I have problem with forecast reports in SCOM 2012 after integration with VMM 2012. All other reports (not forecasting) works fine. For example, report “Host Group Forecasting” don’t work. The report is generated, but I have error: “Subreport
could not be shown”. I find only errors in SQL Server Reporting logs like this:
library!ReportServer_0-13!1758!06/26/2012-18:26:23:: i INFO: RenderForNewSession('/Microsoft.SystemCenter.VirtualMachineManager.2012.Reports/Microsoft.SystemCenter.VirtualMachineManager.2012.Report.ForecastHostGroup')
processing!ReportServer_0-13!1758!06/26/2012-18:26:28:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Не удалось выполнить
запрос для набора данных "DiskSpaceUsageForecasting". ---> Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: Execution of the managed stored procedure GetTimeSeriesForecast failed with the following error: Exception has been thrown by
the target of an invocation..
Query (5, 58) Parser: The syntax for '6' is incorrect.
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteTabular(CommandBehavior behavior, ICommandContentProvider contentProvider,
AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.DataExtensions.AdoMdCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.OnDemandProcessing.RuntimeDataSet.RunEmbeddedQuery(Boolean& readerExtensionsSupported, Boolean& readerFieldProperties, List`1 queryParams, Object[] paramValues)
--- End of inner exception stack trace ---;
The Russian string “Не удалось
выполнить запрос для набора данных "DiskSpaceUsageForecasting"” is translated to “Could not execute query for data set "DiskSpaceUsageForecasting"”.
I have clean installation SCOM 2012 RU1, VMM 2012 RU1. Integration SCOM with VMM work fine.
SQL collation for all SQL DB instances (SCOM and VMM and SCOM reporting) – “SQL_Latin1_General_CP1_CI_AS”
SQL Analysis service: SQL collation – “Latin1_General” ; language for the server – English (United States)
I think the problem in regional settings. By my opinion there are two possible mistakes:
SQL collation for all SQL DB instances. May be need use “Latin1_General_CI_AS”
as provided by
http://blogs.technet.com/b/momteam/archive/2012/05/25/clarification-on-sql-server-collation-requirements-for-system-center-2012.aspx
Need change regional setting. Question is for what (OS regional setting, SQL Analysis service settings,…) ?Error: Subreport could not be shown
Opening a report for Client Security might result in the following error being displayed in one or more areas of the report: "Error: Subreport could not be shown."
Background
There are two possible reasons for this error:
1. Wrong location The reporting server is pointing to the wrong computer running SQL Server or a SQL Server instance.
2. Insufficient permissions The account configured (in SQL Server Reporting Services) to connect to the reporting database does not have appropriate permissions for the database.
Solution
To determine which reason is causing the error, attempt to directly open the subreport reporting the error, by clicking the name of the subreport.
If the reporting server is pointing to a wrong location, the report displays an error similar to the following:
Error message
An error has occurred during report processing.
Cannot create a connection to data source 'SystemCenterReporting'. Cannot open database "SystemCenterReporting" requested by the login. The login failed. Login failed for user username.
To verify the correct SQL Server computer and instance path
In Report Manager, navigate to the report generating the error and click the Properties tab.
Click Data Sources and under a Shared data source, note the path.
Open the reporting Web site. If you chose the default virtual directory for reports, the URL is: http://hostname/Reports/
If you chose to secure the viewing of reports with HTTPS, the URL is: https://hostname/Reports/
Click SCDW.
In the Connection type list, ensure that Microsoft SQL Server is selected.
In the Connection string box, ensure that the correct SQL Server computer and instance name are entered.
Note:
A period (.) denotes the local computer.
If the account has insufficient permissions, the report displays an error similar to the following:
Error message
An error has occurred during report processing. (rsProcessingAborted) Query execution failed for data set 'DSDashboardComputersTrend'. (rsErrorExecutingCommand) EXECUTE permission denied on object 'prSAS_UX_DashboardComputersTrend', database 'SystemCenterReporting',
schema 'dbo'.
To determine if you are experiencing the SQL Server permissions issue
Open the reporting Web site. If you chose the default virtual directory for reports, the URL is:http://hostname/Reportserver/
If you chose to secure the viewing of reports with HTTPS, the URL is:https://hostname/Reportserver/
Click Microsoft Operations Manager Reporting, click Microsoft Forefront Client Security, and scroll to DashboardComputersTrend.
Click DashboardComputersTrend.
If you are experiencing a SQL Server permissions issue, an error similar to the preceding error appears.
To grant permissions to the SQL Server computer
1. In Report Manager, click SCDW and note the account in the Connect using section. This is the account under which the database is contacted.
2. On the server with the System Center Reporting database, start SQL Server Management Studio.
3. In the tree, expand Security, and then expand Logins. Do one of the following:
If the user account is listed, right-click the account, click Properties, and then go to step 5.
If the user account is not listed, right-click Logins and choose New Login.
4. In the Login name box, enter the user account (domain\username).
5. In the Login Properties dialog box, click User Mapping, and then under Users mapped to this login, select the System Center Reporting check box.
6. Under Database role membership for: System Center Reporting, select the db_owner check box, and then click OK.
Thanks,
Yog Li
TechNet Community Support -
Performance problem with Integration with COGNOS and Bex
Hi Gems
I have a performance problem with some of my queries when integrating with the COGNOS
My query is simple which gets the data for the date interval : "
From Date: 20070101
To date:20070829
When executing the query in the Bex it takes 2mins but when it is executed in the COGNOS it takes almost 10mins and above..
Any where can we debug the report how the data is sending to the cognos. Like debugging the OLEDB ..
and how to increase the performance.. of the query in the Cognos ..
Thanks in Advance
Regards
AKHi,
Please check the following CA Unicenter config files on the SunMC server:
- is the Event Adapter (ea-start) running ?, without these daemon no event forwarding is done the CA Unicenter nor discover from Ca unicenter is working.
How to debug:
- run ea-start in debug mode:
# /opt/SUNWsymon/SunMC-TNG/sbin/ea-start -d9
- check if the Event Adaptor is been setup,
# /var/opt/SUNWsymon/SunMC-TNG/cfg_sunmctotng
- check the CA log file
# /var/opt/SUNWsymon/SunMC-TNG/SunMCToTngAdaptorMain.log
After that is all fine check this side it explains how to discover an SunMC agent from CA Unicenter.
http://docs.sun.com/app/docs/doc/817-1101/6mgrtmkao?a=view#tngtrouble-6
Kind Regards -
General install and deployment problem with WLS clustering on two boxes
Hi,
I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
Any help appriecated.
Surfbum.Hi I think I've found the answer. You can build a managed server template using the pack command.
http://e-docs.bea.com/common/docs90/pack/tasks.html -
Any recomdations for B2B integration product to work with WLS?
Hi, any recomdations for B2B integration product to work with WLS?
Thanks
Wasiq Hasan
[email protected]Yes:
http://www.beasys.com/press/releases/2000/0607_collaborate_eap.html
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Globalink" <[email protected]> wrote in message
news:3978d8f8$[email protected]..
Hi, any recomdations for B2B integration product to work with WLS?
Thanks
Wasiq Hasan
[email protected] -
Apache-soap Problem with WLS 5.1sp9
I have problem with WLS 5.1sp9.
My environment is the following :
jaf-1.0.1
javamail-1.2
soap-2.2
xerces-1.4.4
and I want to call EJB.
So, I write some EJB and deploy it.
And rpcrouter work!!
Success to deploy the Service.
But I run into problem with calling this ejb.
This error is the following.
SOAP-ENV:Server.BadTargetObjectURI
Unable to resolve target object: BC2_BoardSync
please, help me.
here's my example..
ps.
sorry for my poor English..T_T
[ws5.10.zip]
[vb.zip]I have problem with WLS 5.1sp9.
My environment is the following :
jaf-1.0.1
javamail-1.2
soap-2.2
xerces-1.4.4
and I want to call EJB.
So, I write some EJB and deploy it.
And rpcrouter work!!
Success to deploy the Service.
But I run into problem with calling this ejb.
This error is the following.
SOAP-ENV:Server.BadTargetObjectURI
Unable to resolve target object: BC2_BoardSync
please, help me.
here's my example..
ps.
sorry for my poor English..T_T
[ws5.10.zip]
[vb.zip]
Maybe you are looking for
-
Multiple transactions in Call Transactions
Hi All, Can i use the below code to do multiple transactions in call transaction using the Below code. Call Transction for XK01 using BDCDATA1 Call Transction for MM01 using BDCDATA2 Call Transction for VA01 using BDCDATA3 Please advise. Regards Kr
-
Slider not rendering font size of text on another page
I am using a slider to control the font size of the text. On one page, I have the slider setup as follows: <Grid Grid.Row="3" Margin="10,4.5,0.667,0"> <Slider x:Uid="FontSlider" x:Name="FontSlider" Header="Select font size" HorizontalAlignment="L
-
Lookin for a mp3 player... freakin out a
hey y'all i'm looking for micro dri've mp3 player and I'm checking out products such as ipod mini, creative zen micro and others as well. After checking out each player i see flaws such as mini have no battery replaceable, have to buy adapter and USB
-
I can not get the program to reset the factory defaults, enough to open the mini bridge tab...... I have tried numerous times and it does not open and it is needed to be able to view two files in the application window and to be able to work on them
-
Hello ! I want to send the data seen in tcode /SAPAPO/ODL Order Due List to an external warehouse management system via a websphere broker. How do I approach this ? I have never worked with APO before. / Tom