Forum Problems Installing LAMS: Problems configuring LAMS integration into .LRN


 
You may request notification for Problems configuring LAMS integration into .LRN.
Search: 

1: Problems configuring LAMS integration into .LRN
11/17/08 11:18 PM
[ Reply | Forward ]
Having finally found the configuration page, I'm at a loss as to how to identify and correctly input the following fields:
request_source
server_id
server_key

Any direction and help would be greatly appreciated.
Geoff

Posted by Geoffrey S Davidson

2: Re: Problems configuring LAMS integration into .LRN
In response to 1 11/18/08 06:57 AM
[ Reply | Forward ]
Hi Geoffrey,

Have a look at the animations and information on this page:

http://wiki.lamsfoundation.org/display/lamsdocs/dotLRN

Thanks,

Ernie

Posted by Ernie Ghiglione

3: Re: Problems configuring LAMS integration into .LRN
In response to 1 11/18/08 09:53 AM
[ Reply | Forward ]
Thanks Ernie, this has me closer - I now get to the page that allows me to try to add a LAMS lesson, but from that I get an error message (which fortunately tells me that you are the person I should be asking - I appreciate you including that authorship credit in the error code).

I appreciate any additional help you can give me to get past this latest hiccup.

Here's where I am now:

There was a server error processing your request. We apologize.

Take me back where I was (before the error)

error "syntax error" at line 1 character 49
Not Found
    while executing
"dom parse  $xml"
    invoked from within
"set doc [dom parse  $xml]"
    ("uplevel" body line 54)
    invoked from within
"uplevel {
          # packages/lams2int/www/admin/add.tcl

ad_page_contract {

    Adds a LAMS lesson

    @author Ernie Ghiglione (ErnieG@melcoe...";
    (procedure "code::tcl::/usr/local/dotlrn/packages/lams2int/www/admin/add" line 2)
    invoked from within
"code::tcl::$__adp_stub"
    invoked from within
"if { [file exists $__adp_stub.tcl] } {

      # ensure that data source preparation procedure exists and is up-to-date
      adp_init tcl $__adp_stub
..."
    ("uplevel" body line 3)
    invoked from within
"uplevel {

    if { [file exists $__adp_stub.tcl] } {

      # ensure that data source preparation procedure exists and is up-to-date
      adp_init t..."
    (procedure "adp_prepare" line 2)
    invoked from within
"adp_prepare"
    invoked from within
"template::adp_parse [file root [ad_conn file]] {}"
    (procedure "adp_parse_ad_conn_file" line 6)
    invoked from within
"$handler"
    ("uplevel" body line 2)
    invoked from within
"uplevel $code"
    invoked from within
"ad_try {
                $handler
            } ad_script_abort val {
                # do nothing
            }"
    invoked from within
"rp_serve_concrete_file [ad_conn file]"
    (procedure "rp_serve_abstract_file" line 60)
    invoked from within
"rp_serve_abstract_file "$root/$path""
    ("uplevel" body line 2)
    invoked from within
"uplevel $code"
    invoked from within
"ad_try {
            rp_serve_abstract_file "$root/$path"
            set tcl_url2file([ad_conn url]) [ad_conn file]
            set tcl_url2path_info..."

Posted by Geoffrey S Davidson

4: Re: Re: Problems configuring LAMS integration into .LRN
In response to 3 11/19/08 03:24 PM
[ Reply | Forward ]
Hi Geoffrey,

I think that might be because you are using an older version of the integration code. Did you get the code form the openacs repository?

You can get the code for the lams2int module by doing:

cvs -z3 -d :pserver:anonymous@lamscvs.melcoe.mq.edu.au:/usr/local/cvsroot co dotlrn_packages/lams2int

I don't think there has been any database changes, so the code tcl code is the only thing that has changed. replace the lasm2int director in your /usr/local/dotlrn/packages/ directory and that should do the trick (hopefully :-)

Otherwise, let me know.

Cheers,

Ernie

Posted by Ernie Ghiglione

5: Re: Re: Re: Problems configuring LAMS integration into .LRN
In response to 4 11/20/08 10:11 AM
[ Reply | Forward ]
Hi Ernie,
Finally we got to the LAMS login screen :D

But, none of my passwords, nor the default sysadmin password are working. We tried logging into the database directly, and with md5 encryption, but that didn't get us there.

And the mail server apparently still needs to be configured as we couldn't use the 'forgot password' feature.

Can you now tell me how to log in directly to the database to reset passwords?

Thanks,
Geoff

Posted by Geoffrey S Davidson

6: Re: Re: Re: Re: Problems configuring LAMS integration into .LRN
In response to 5 11/20/08 12:45 PM
[ Reply | Forward ]
Hi Geoff,

So you´re saying that you don´t have the sysadmin password to login into your LAMS server. Is that right?

The sysadmin password for LAMS should have been set when you installed LAMS. If you have installed LAMS in windows, most likely the syadmin username and password can be found in the Windows Registry. If you have installed it in linux/unix, have a look in /etc/lams2 as there should be a file with the details as well.

In addition, you can change the sysadmin password directly in the DB. It´s posted here in the community somewhere, let me have a look and give you the link.

Thanks,

Ernie

Posted by Ernie Ghiglione

7: Re: Re: Re: Re: Re: Problems configuring LAMS integration into .LRN
In response to 6 11/20/08 07:48 PM
[ Reply | Forward ]
Hi Ernie,

The file you referenced gives the sysadmin/sysadmin information. We've been there, tried that, no such luck.

Based on your note I did a search of the site for anything that might reference how to access it directly in the database but haven't found any link.

Have you had any luck finding a link for it?

Thanks,
Geoff

Posted by Geoffrey S Davidson

8: Re: Re: Re: Re: Re: Re: Problems configuring LAMS integration into .LRN
In response to 7 11/20/08 11:51 PM
[ Reply | Forward ]
Here is the error log being generated if that can help track down the problem with the password:

2008-11-21 05:41:14,493 [http-0.0.0.0-8080-7:] INFO
org.lamsfoundation.lams.security.UniversalLoginModule - initialize
2008-11-21 05:41:14,493 [http-0.0.0.0-8080-7:] INFO
org.lamsfoundation.lams.security.UniversalLoginModule - login
2008-11-21 05:41:14,499 [http-0.0.0.0-8080-7:] ERROR
org.lamsfoundation.lams.security.UniversalLoginModule - ===>
exception: org.springframework.jdbc.UncategorizedSQLException:
Hibernate operation: Cannot open connection; uncategorized
SQLException for SQL [???]; SQL state [null]; error code [0]; Could
not enlist in transaction on entering meta-aware
object!javax.transaction.SystemException: Could not get XAResource
from ManagedConnection!javax.transaction.RollbackException: Already
started rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141]; - nested
throwable: (javax.resource.ResourceException: Could not enlist in
transaction on entering meta-aware
object!javax.transaction.SystemException: Could not get XAResource
from ManagedConnection!javax.transaction.RollbackException: Already
started rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141]); nested
exception is or
g.jboss.util.NestedSQLException: Could not enlist in transaction on
entering meta-aware object!javax.transaction.SystemException: Could
not get XAResource from
ManagedConnection!javax.transaction.RollbackException: Already started
rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141]; - nested
throwable: (javax.resource.ResourceException: Could not enlist in
transaction on entering meta-aware
object!javax.transaction.SystemException: Could not get XAResource
from ManagedConnection!javax.transaction.RollbackException: Already
started rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141])
org.springframework.jdbc.UncategorizedSQLException: Hibernate
operation: Cannot open connection; uncategorized SQLException for SQL
[???]; SQL state [null]; error code [0]; Could not enlist in
transaction on entering meta-aware
object!javax.transaction.SystemException: Could not get XAResource
from ManagedConnection!javax.transaction.RollbackException: Already
started rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141]; - nested
throwable: (javax.resource.ResourceException: Could not enlist in
transaction on entering meta-aware
object!javax.transaction.SystemException: Could not get XAResource
from ManagedConnection!javax.transaction.RollbackException: Already
started rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141]); nested
exception is org.jboss.util.NestedSQLException: Could not enlist in
transaction on entering meta-aware
object!javax.transaction.SystemExcept
ion: Could not get XAResource from
ManagedConnection!javax.transaction.RollbackException: Already started
rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141]; - nested
throwable: (javax.resource.ResourceException: Could not enlist in
transaction on entering meta-aware
object!javax.transaction.SystemException: Could not get XAResource
from ManagedConnection!javax.transaction.RollbackException: Already
started rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141])
org.jboss.util.NestedSQLException: Could not enlist in transaction on
entering meta-aware object!javax.transaction.SystemException: Could
not get XAResource from
ManagedConnection!javax.transaction.RollbackException: Already started
rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141]; - nested
throwable: (javax.resource.ResourceException: Could not enlist in
transaction on entering meta-aware
object!javax.transaction.SystemException: Could not get XAResource
from ManagedConnection!javax.transaction.RollbackException: Already
started rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141])
at
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:107)
at
org.springframework.orm.hibernate3.LocalDataSourceConnectionProvider.getConnection(LocalDataSourceConnectionProvider.java:81)
at
org.hibernate.jdbc.AbstractBatcher.openConnection(AbstractBatcher.java:424)
at org.hibernate.jdbc.JDBCContext.connect(JDBCContext.java:162)
at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:97)
at
org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:86)
at
org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1129)
at org.hibernate.loader.Loader.doQuery(Loader.java:373)
at
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:210)
at org.hibernate.loader.Loader.doList(Loader.java:1561)
at org.hibernate.loader.Loader.list(Loader.java:1544)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:375)
at
org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:271)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:830)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:74)
at
org.springframework.orm.hibernate3.HibernateTemplate$31.doInHibernate(HibernateTemplate.java:853)
at
org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:366)
at
org.springframework.orm.hibernate3.HibernateTemplate.find(HibernateTemplate.java:844)
at
org.springframework.orm.hibernate3.HibernateTemplate.find(HibernateTemplate.java:840)
at
org.lamsfoundation.lams.dao.hibernate.BaseDAO.findByProperty(BaseDAO.java:215)
at
org.lamsfoundation.lams.usermanagement.service.UserManagementService.getUserByLogin(UserManagementService.java:422)
at
org.lamsfoundation.lams.usermanagement.service.UserManagementService$$FastClassByCGLIB$$aa86f00b.invoke()
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at
org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:685)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at
org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:623)
at
org.lamsfoundation.lams.usermanagement.service.UserManagementService$$EnhancerByCGLIB$$74a0082_2.getUserByLogin()
at
org.lamsfoundation.lams.security.UniversalLoginModule.validatePassword(UniversalLoginModule.java:100)
at
org.lamsfoundation.lams.security.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:151)
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:585)
at
javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at
javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at
javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at
javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at
javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at
org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:483)
at
org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:425)
at
org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:251)
at
org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:230)
at
org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:256)
at
org.lamsfoundation.lams.web.session.LoginFormAuthenticator.authenticate(LoginFormAuthenticator.java:51)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:391)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at
org.lamsfoundation.lams.integration.security.SingleSignOn.invoke(SingleSignOn.java:121)
at
org.lamsfoundation.lams.integration.security.LoginRequestValve.invoke(LoginRequestValve.java:67)
at
org.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAccessLogValve.java:481)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at
org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.resource.ResourceException: Could not enlist in
transaction on entering meta-aware
object!javax.transaction.SystemException: Could not get XAResource
from ManagedConnection!javax.transaction.RollbackException: Already
started rolling back. TransactionImpl:XidImpl[FormatId=257,
GlobalId=mastery.org/61141, BranchQual=, localId=61141]
at
org.jboss.resource.connectionmanager.TxConnectionManager.managedConnectionReconnected(TxConnectionManager.java:327)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2.reconnectManagedConnection(BaseConnectionManager2.java:583)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:450)
at
org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:874)
at
org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:103)
... 60 more
2008-11-21 05:41:14,500 [http-0.0.0.0-8080-7:] INFO
org.lamsfoundation.lams.security.UniversalLoginModule - abort

Posted by Geoffrey S Davidson

9: Re: Re: Re: Re: Re: Re: Problems configuring LAMS integration into .LRN
In response to 7 11/21/08 09:00 AM
[ Reply | Forward ]
Geoff,

At this stage you are better off reinstalling LAMS. Are you on Windows or Unix?

Thanks,

Ernie

Posted by Ernie Ghiglione

10: Re: Re: Re: Re: Re: Re: Re: Problems configuring LAMS integration into .LRN
In response to 9 11/21/08 12:30 PM
[ Reply | Forward ]
Ernie, we'll try that.

This is a Unix/FreeBSD installation - we're committed to enterprise open source solutions for everything we can get to meet our business requirements.

Geoff

Posted by Geoffrey S Davidson

11: Re: Re: Re: Re: Re: Re: Re: Problems configuring LAMS integration into .LRN
In response to 9 11/22/08 08:39 PM
[ Reply | Forward ]
Hi Ernie,
Absolutely no luck. We've tried reinstalling, changing directories, everything we can think of and are still having problems. Marc Fournier has posted a separate thread with the current login problem and status, hopefully someone can help us figure out why login isn't working.
Thanks,
Geoff

Posted by Geoffrey S Davidson

Reply to first post on this page
Back to Problems Installing LAMS