We have a user trying to access a WebFocus reporting object that we have built and is getting an error message that says, 'ibi.webfoc.wfutil.WEErrorException:Invalid Session Cookie' It is an error creating content. I have a feeling the users account is corrupted but not sure. When I try to view his Shared Reports, I get a message that says, 'Error Unable to perform WORP_GetsharedUserContentsAction Caused By: ibi.webfoc.wfmre.mrutil.WFMREerror: The reference to the user directory is not in adykstra.htm.
We are running WebFocus 7.7.0.3. Anyone have any ideas? Do I need to kill his profile and reset him back up? He had a lot of reports he has not shared so he will lose them all if I have to delete his account.
Thank you.

This message has been edited. Last edited by: <Emily McAllister>,

Hi,

You may want to open a case with IBI. They can usually help you with a corrupted user account, with out deleting it and starting over.
I've had to do it a few times.
Good luck

We resolved it by pulled their profile off from a backup prior to the issue occurring and restoring just this particular teammate.

I have another situation where we have a few users who can build reports through a Reporting Object but can no longer save any changes to them or create new ones. I have resolved this issue with a few people by deleting their account and setting them back up. They had to share all their reports they had built first so they could pull them back in after their account was fixed. I have two people which this did not work for. Any suggestions on this one?

Bob,

A long time ago when I was on 7.6.7, the HTM files for the users would get corrupted. Essentially all this was, was that that the value would get written at the top of the file, instead of nested in the correct spot in the file. We would then just go and grab the line of code that was saved in the wrong spot and move it. Took a few minutes to resolve and the user was back up and running. If you still have the old file from before you restored the backup, it might be worth seeing what the difference was so that you could just fix the file next time instead of having to restore from backup.