Skip to end of metadata
Go to start of metadata
This resource outlines some common issues encountered by implementers and their solutions for CM 2.0. Regularly contributing members of the IUG make every attempt to keep this space updated.  If you need additional assistance, please contact the Implementation User Group (IUG).

 

 

Calling Service on Rice KSB returns HTTP 200 status code instead of XML

ISSUE

When trying to call a security-enabled service published on the service bus, receive an XML parsing error which shows HTTP status code 200 in the return page 

SOLUTION

Try setting rice keystore parameters in your umd-rice-config.xml

config.xml

Links on CM landing page are broken

ISSUE

You changed the URL where the application is running, but the links on the landing page still point to localhost: e.g. http://localhost:8081/ks-with-rice-bundled/kew/ActionList.do resulting in the action list panel being blank (or other bad links).

SOLUTION

Try setting the following parameters in your ks-with-rice-bundled-config.xml (replace the IP address with your URL).

ks-with-rice-bundled-config.xml

 

KRIM tables are missing from KSBUNDLEDDB schema / Impex not dropping tables

ISSUE
  • You are trying to get the quickstart working, but the KRIM tables are missing from your KSBUNDLEDDB schema. You reimpex, but they still don't appear.
  • Re-impexing sends output to the screen, but doesn't appear to drop/rebuild the tables
SOLUTION

If the KRIM tables are missing then there is likely something wrong when you impexed (or are reimpexing) the database.  Here is a troubleshooting procedure.

1.  Disconnect everything from the DB.  Close SQL developer and the application.  Manually drop the entire KSBUNDLEDDB schema using web interface in Oracle XE.  Verify it is gone.
2.  When you checkout from SVN, instead of using the command ' svn co http://svn.kuali.org/repos/student/enrollment/ks-deployments/tags/ks-deployments- 2.0.1-cm/ks-cfg-dbs/', checkout the entire project using ''svn co http://svn.kuali.org/repos/student/enrollment/ks-deployments/tags/ks-deployments- 2.0.1-cm/' and then cd into the ks-cfg-dbs/ks-bundled-db/ directory.  I recommend checking out the entire project as opposed to partial paths.
3. Re-run your impex command while in the ks-cfg-dbs/ks-bundled-db/ directory.
4. Go back and look at your DB.  The new schema should be created and the KRIM tables should be there.

What may have happened is that you impexed using embedded or standalone, as these modes place the KRIM tables in a different schema.  Then, you probably have an application that is open/locking the schema.  Every time you impex it may be giving you an error that says the user is still connected to the DB, but then it scrolls by on the screen too quick and you don't see it.  So do 1-5 above to be 100% sure nothing has a lock on the tables.

 

Application fails to start - Tomcat stdout log shows Cannot get connection for URL jdbc:oracle:thin:@localhost:1521:XE : ORA-28000: the account is locked

ISSUE

This error means the oracle account is now locked, probably from passing it the wrong password too many times. 

SOLUTION

1. Attempt to login to the DB account using a 3rd party product such as DBVizualizer or SQLDeveloper.  Use the user/pass you are using in your Kuali config file. It should also give you an error saying the account is locked by Oracle.
2. Follow these instructions to unlock the account:
https://blogs.oracle.com/rajeshthekkadath/entry/resolving_oracle_error_ora_28000
3. Again do step #1 above.  The account should now be unlocked and you should be able to see the tables.

 

Application fails to start - Tomcat log shows java.net.BindException: Address already in use: JVM_Bind

ISSUE
  • You have a tomcat instance that is running on the same port (it failed to shut down correctly - this happens sometimes)
  • Another application is using that port
SOLUTION
  1. You need to kill the duplicate tomcat process and try to start tomcat again OR identify the other application using that port (on unix you can use lsof -i :8887 to see what process is using the port, on windows you can use the free process explorer tool)  
  2. If you are on windows, open the task manager and kill any Java processes, then try to start again.  On unix, you can use "kill -9 PID" to terminate the process.  
  3. Once all the java processes are cleared, delete or rename your log files (so we don't get confused with previous errors), then try to start up tomcat again, see if the error is gone.

Where do I find information on the Course Approval Workflow?

ISSUE

I found this link very useful in helping with doing reviews and was wondering if a similar document is available for approval.

I'm trying to take a course through the entire process. We stood up a sandbox using war file with rice bundled so I figured it would be there somewhere?
SOLUTION

We made a page Course Approval Workflow Help to help answer this question...

Sample: Include the Title of your issue as a Heading 2

ISSUE

Description of the issue goes in a panel like this - you can edit this wiki page and copy this set of panels to accomplish this.

SOLUTION

How to accomplish the solution goes in a panel like this.

codeblock title