Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Invalid Session String error when trying to start a workflow
kk_aa_rf
We have a brand new install of 6.7.1 on Solaris 10.
All the users (both on ie & Firefox) get the following error while trying to submit a file to staging or trying to kick off a workflow.
TeamSite : Wrapper
Invalid Session String 52........(100 chars long)
Received.
The log files don't seems to contain any errors related to this.
We cleared our browser cache, did iwreset -a a couple of times and even did a stop and restart of the server.
Nothing seems to help.
We have another 6.7.1 install which seems to be working fine (we upgraded it from 6.5.)
Before doing a clean reinstall I wanted to know if any of you have encountered this issue and successfully solved it.
Any help would be highly appreciated
Thanks
Find more posts tagged with
Comments
nipper
The string is the IW_AUTH data, pretty meaningless and I thought they were going to remove that.
Is this a root install of TS or a non-root install ?
I have seen this before when some of the files that were supposed to be owned by root were not.
You can check your permissions of files in iw-bin, bin, etc. Compare them to the perms on the sys working.
Most should be owned by root.daemon, lots of 775 permissions. Obviously different if it is a non-root install.
HTH
Andy
Adam Stoller
Also - make sure that your OS is fully patched, especially with regard to Java, and that you are doing this in (what I believe is called) the global zone (or something like that).
kk_aa_rf
We tried the following steps in vain.
- Checked permissions of httpd/iw-bin files
- Recreated entity database
- Changed authentication from LDAP to PAM to unix
Finally did a clean re-install and that solved the problem.
However, we encountered another issue while reinstalling TS6.7.1 on solaris 10- Here is the solution for your reference.
After installing TeamSite, the servletd failed to come up. This was due to a security config issue.with cryptographic accelerator card.
Here is what you need to do to fix it.
To determine if you have one on your server, please run the cryptoadm list,
http://partneradvantage.sun.com/protected/solaris10/adoptionkit/general/cryptoadm1.txt
, on the system. A card is present if the output contains the following:
Kernel hardware providers:
ncp/0
We confirmed the cryptographic accelerator is present, performed the following steps:
Open the java.security file in iw-home/tools/java/jre/lib/security.
Replace the priority number of security providers. Make sure that the SunJCE provider has priority 1 as specified below:
security.provider.1=com.sun.crypto.provider.SunJCE
and changed the PKCS11 provider to a lower priority:
security.provider.5=sun.security.pkcs11.SunPKCS11 ${java.home}/lib/security/sunpkcs11-solaris.cfg
Saved the java.security file.
Restarted the TeamSite server.
That solved the issue.
kirthiraman
When I am calling factory.getClient( username, role,
password, Locale.getDefault(),
"mydemo", null );
as explained in CreateClient.java (example), why is it treating the function as if it is factory.getClient(String sessionString, Locale locale,
String appContext,
String server)
and giving com.interwoven.cssdk.access.CSInvalidSessionStringException: 52616e646f6d49561.....
What is wrong?