Cannot connect to security domain

security Supervisor (4.x - 6.x)
1

This ever returning problem is driving me crazy. Currently there are hardly any user using BO in our organisation. I’m working on the proper installation of the DAS to publish reports on the intranet on a regular basis (every hour, every day etc.) I cannot be that the security domain is locked (nobody is using it). How do I prevent this error from happening?

************************************************************* Hans Kingma
Unisource Carrier Services
Industriestrasse 21
8304 Wallisellen
Switzerland
Phone: +41 1 839 32 11
Fax: +41 1 839 32 95

Listserv Archives (BOB member since 2002-06-25)

2

Hans,

I’m having the same problem with DAS (assuming the actual error you’re getting is ‘User xxxxx Cannot connect to Security Domain’. According to the ‘DAS Bible’ I quote

" This can happen if a timestamp is created for the user that sent the document. This can also happen if too many tasks are starting at the same time. All of them are trying to update the objects.lsi file at the same time. (This file is used in offline mode). Tell the customer to reduce the number of concurrent tasks in the DAS options".

We’re getting this error anytime more than one task is running at the same time depite changing the options to the default 4 concurrent tasks or any other setting. The only way more than one doc runs succesfully if their ‘scheduled’ time is close to each other is to allow them to fail and then allow the auto rerun to be set for 1 retry say 20 mins later (unless this overlaps with another waiting report!).

Anyone know of a solution? (We’re running 4.1.3).

Regards

Jonathan

Project Leader
Global Medical, Regulatory and Product Strategy (GMRPS) IS

Listserv Archives (BOB member since 2002-06-25)

3

Jonathon

You reported a problem described as:
I’m having the same problem with DAS (assuming the actual error you’re getting is ‘User xxxxx Cannot connect to Security Domain’. snip…

We’re getting this error anytime more than one task is running at the same time depite changing the options to the default 4 concurrent tasks
or any other setting.
snip…

I had a similar problem with Doc Agent 4.1.3 as well. I also found that if I tried to logon to the user module on the doc agent machine that I would get a “cannot access local security file” message.

I called Business Objects Tech support and logged a case, their response was to rename the objects.bak to objects.lsi on the Doc Agent server or reduce the number of concurrent tasks to one. We tried the first suggestion and it worked for a while but we are still running into the problem intermittently.

The other option might be to reduce the number of concurrent tasks that you allow in Doc Agent (this was the second suggestion from Tech support) - we did not follow-up on this suggestion because we need to have 4 concurrent tasks running in order to get through our production work.

One additional note, we have 2 servers configured exactly the same running DAS except that one is running doc agent 4.1.1 and one is running 4.1.3. I found that if I place the production load on the 4.1.1 server I don’t have the problems described above, but if I place the production load on the server running 4.1.3 I run into the problem you described about once every two weeks.

Regards

Dan Consolati

From: Cirkel, Jonathan D [SMTP:jc14547@GLAXOWELLCOME.CO.UK] Sent: Friday, October 02, 1998 9:00 AM

Hans,

Anyone know of a solution? (We’re running 4.1.3).

Regards

Jonathan

Project Leader
Global Medical, Regulatory and Product Strategy (GMRPS) IS

Web archives (9am-5pm ET only): listserv.aol.com/archives/busob-l.html
OR search: Mail to listserv@listserv.aol.com, ‘search a_phrase in BUSOB-L’
Unsubscribe: Mail to listserv@listserv.aol.com, ‘unsubscribe BUSOB-L’

Listserv Archives (BOB member since 2002-06-25)

4

“Cannot Connect To the Security Domain” has to do with the following reason:

  1. Either your objects.lsi file is corrupted.
  2. You have more then one task write to the objects.lsi or
    objects.ssi at the same time.
  3. You had a Dr.Watson error on the Document Agent Machine.
    The fixes:
    For 1) Replace the objects.lsi ( I always keep a backup of the Objects.lsi file in the same folder. We have the file getting corrupted everyday). When you log into Business Objects from the document agent machine, you get the error “CANNOT ACCESS Security file” which means your objects.lsi or ssi file is corrupted. 2) CSP22 was suppose to fix this problem. It works only with
    4.1.3. We have not tested it yet, but will be good to know if any one has.
  4. I cannot think of any way you can stop this. A user submits a
    bad query which results in a Dr. Watson error. Unless the GPF is cleaned up all the jobs continue to fail. Business Objects cannot reproduce it, so it is still a mystery.
    Reducing the Number of Tasks on the document agent machine has nothing to do with this error. I have a machine with 200MG of RAM and only one document agent. I can reproduce the error with just two tasks if they are schedule to run at the same time. Dilip

Listserv Archives (BOB member since 2002-06-25)

5

Jonathan,
I am not sure if this is the same problem as we were having, but we had situations in which we had multiple tasks trying to run at the same time on Doc Agent. The problem was that every one of the tasks tried to write to the LSI file at once, thereby corrupting it. The net result was that one task would run and the others failed.

The solution we got from BusinessObjects was to upgrade to 4.1.3 (which you mentioned you are already running under) and install Customer Service Patch #22. We got the patch by requesting BusinessObjects to send it to us. I am not sure if it is available out on the Web. I hope this might help.

Sincerely,
Kevin Smith
GE Capital Railcar Services

Listserv Archives (BOB member since 2002-06-25)

6

I’m having the same problem with DAS (assuming the actual error you’re getting is ‘User xxxxx Cannot connect to Security Domain’.

Jonathan,

We too had this problem. We worked with Business Objects to solve the problem. You are right, when more than one task is started at the same time only one is able to update the objects.lsi file which causes all the other tasks to fail. Business Objects provided us with a patch, CSP22, to correct this problem.

Mike

Listserv Archives (BOB member since 2002-06-25)

7

We installed CSP22. It did fix the 'User XXXX cannot connect to the security domain" error when the DAS tries to launch more than one report at a time.

Unfortunately, it did not fix the “Cannot access the security domain” error that we get daily from the Doc Agent. I’m still working with Business Objects support on that.

Larry Rosenblum
Saama Technologies, Inc.

Agarwal, Dilip (DK) wrote:

“Cannot Connect To the Security Domain” has to do with the following reason:

  1. Either your objects.lsi file is corrupted.
  2. You have more then one task write to the objects.lsi or
    objects.ssi at the same time.
  3. You had a Dr.Watson error on the Document Agent Machine.

…

  1. CSP22 was suppose to fix this problem. It works only with
    4.1.3. We have not tested it yet, but will be good to know if any one has.

Listserv Archives (BOB member since 2002-06-25)