Home › Blogs › ma_isaura's blog

Updated to 4.1.22 - Complications

Thu, 2008-07-03 20:18 — ma_isaura
0
No votes yet

Hi everyone!

I am killing myself here with an open ticket since two days ago and nobody has answer back... I have upgraded my TEST environment from 4.0.2 to 4.1.22 and my calendar stopped working is not doing SSO and for some reason not even the UID nor the userid are able to log in... the only user able to login is lumadmin curiously this user has UID=lumadmin instead of the terrible immutable ID. has anyone have problems with the calendar?... also my banner channels changed... I no longer have the INB link from a Banner Links the only one showing is the self-service channel... are there any other ways to link to INB to do SSO?

Thanks for reading!.. and more thanks for any comment or suggestion...

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Thu, 2008-07-03 20:34 — shiva

thats interesting..

Hi,
We just upgraded our test system from 4.0.2.0 to 4.1.0.15 (to support Enrollment Management) and the EM actually broke the portal. I had to uninstall 4.1 and get back to 4.0.2 and install the patches again.

It wasn't fun - anyway i am more than willing to help you. please post your specific issues or feel free to contact me.

Thank you

Wed, 2008-07-09 13:58 — ma_isaura

Calendar Issues on 4.1

Thanks for you response, the biggest issue is the calendar, started giving me this error messages thru the email:

From: Calendar Store Service
To: lumadmin@laredo.edu
Subject: Critical - Verification of current databases failed on mctestlum.lccnet.edu
X-Priority: 5

Critical - Verification of current databases failed on mctestlum.lccnet.edu

I have to rebuild the calendar DB's almost everyday, I have no info on the calendar is there a way to rebuild the whole thing?

Now I also got this error on the in the wcap.log

2008-07-03 16:53:40,875 Exception caught retrieving default calendar view
com.pipeline.security.authen.AuthenticationRuntimeException: [MISSING_SUBJECT, There is no subject associated with the current thread of exe
cution, ]
2008-07-03 16:53:55,113 WCAPInterface>>getUserInfo(542073449008732) failed with 29
2008-07-03 17:36:04,054 WCAPInterface>>getUserInfo(551701762833872) failed with 29
2008-07-03 17:52:04,504 WCAPInterface>>getUserInfo(551701762833872) failed with 29
2008-07-03 17:52:21,383 WCAPInterface>>getUserInfo(551701762833872) failed with 29
2008-07-03 18:07:48,411 WCAPInterface>>getUserInfo(551701762833872) failed with 29
2008-07-03 18:37:20,057 WCAPInterface>>getUserInfo(551701762833872) failed with 29
2008-07-03 18:47:43,082 WCAPInterface>>getUserInfo(551701762833872) failed with 29
2008-07-03 19:56:04,552 WCAPInterface>>getUserInfo(551701762833872) failed with 29
2008-07-03 19:56:30,117 WCAPInterface>>getUserInfo(551701762833872) failed with 29
2008-07-03 19:57:28,602 WCAPInterface>>getUserInfo(551701762833872) failed with 29
2008-07-08 11:52:57,771 WCAPInterface>>getUserInfo(allusers-lo) failed with 29
2008-07-08 11:53:10,817 WCAPInterface>>getUserInfo(allusers-lo) failed with 29
2008-07-08 11:54:11,190 WCAPInterface>>getUserInfo(allusers-lo) failed with 29
2008-07-08 11:54:16,469 WCAPInterface>>getUserInfo(allusers-lo) failed with 29

I also reviewed the 99user.ldif that was suggested on the other response but the one on the backup and the one on the server are the same, we haven't done any type of customization on this file.

Any Ideas?...

Isaura

Sat, 2008-07-05 18:23 — mculey

We experienced this issue

but it may have been unique to our enviornment. The issue we encountered is that the 99user-cp.ldif schema file gets over written with the 4.1 patch. Since we had implemented the custom PRU in III.3.3 we had modified that file. Without the modifications our ldap accounts were not modifiable so user accounts could not login to calendar. We verified this by creating a new user in our luminis system. This user could get into Calendar just fine. You might check your ldap error log file and see if there's anything in there.

-michael

---
Knowledge is power, power corrupts.
Study hard, be evil.

Thu, 2008-08-07 12:36 — ma_isaura

Finally the answer.... version 4.1 and calendar.

Finally after almost one month we found what was the problem, on release notes 4.1 page 14 where you add the patch for the mail server on point # 15 you have to set up two properties:

local.service.proxy.admin -v (admin username)
local.service.proxy.adminpass -v (password)

I assumed that the admin user was my luminis admin user which i call lumadmin so I used lumadmin as the (admin username) and that started the rest. You have to specifically use the word "admin" as (admin username) and you luminis admin password as
for this configuration to work properly.

I hope this helps... you know Sungard and their knowledge base... totally unbearable.

Isaura